Cyberhawk crash

[likuidkewl]

Find attached the App_compat log from this crash.
I don't know what happened but this is not good that it crashed with minutes of install.... :(

Hopefully this can shed some light on the situation.

//EDIT//
Ok this was easy to recreate for me:
1. Open CH
2. Go to options -> rootkit scan
3. then try to go anywhere else and it crashes

//EDIT #2//
I added small video of what happens in CH_Error.zip

[djames]

Good info.

I will investigate this further, however could you give me more info as to what you are running and on what type of system?

Thank you

Dan

[likuidkewl]

Sure;
XP Pro SP2 all updates and VBA32 antivirus, no other security programs or anything in RT.
Pentium M 1.7/ 1GB / Seagate 5400.3 in a compaq v2000 series notebook

[hake]

Referring to my observations in another thread, the two problems I have with Cyberhawk are rootkit scans (which causes a crash termination of CHService.exe with Windows 2000 and a sort of hang in the scan on Windows XP) and the ungraceful termination of CHService.exe at system shutdown on one Windows 2000 machine though not the other.

This shutdown problem does not appear to cause any subsequent problems. I avoid rootkit scans and Cyberhawk works great in all other ways that I have so far been able to observe.

When the above little details are fixed, Cyberhawk will be excellent. It is already very good. :)

BTW, SpyBot Search and Destroy immunise works fine when I make spybotsd.exe a fully trusted process. I have also done this with Agnitum Outpost 4. I still do not know what the issue with Outpost could be since Cyberhawk and Outpost seem to work well together. I noticed that Outpost once grumbled that Cyberhawk tried to shut it down but it has not complained since. Outpost's self protection feature is enabled and obviously successfully resisted Cyberhawk's efforts to terminate it.

[djames]

Cyberhawk does not try and shut Outpost down, otherwise you would see an alert. I am guessing that this is caused because of the dll conflict.
Outpost stops one of Cyberhawks dlls from functioning. This dll is necessary for Cyberhawk to be fully functional.