Termination of any pgm causes Appl.Error when session active

[jeffw_00]

Hi - I am running 1.1.9.6 as a server on a WinXP machine. When a remote session is active (and only when a remote session is active). Terminating ANY running application produces an error box

<Application name> - Application Error
The instruction at 0x100020b4 referenced memory at "0x00000000". The memory could not be "read". Click on OK to terminate the program. [OK]

Clicking on the OK gets rid of the message and there is no other effect. When there is no remote session active, this does not occur. I could try an older version but not sure which one. Both the Server and Client machines run thoroughly updated WinXP SP3 with no other issues, and UltraVNC 1.1.9.6.

Any thoughts on how to debug are much appreciated - thanks!

[Rudi De Vos]

That's a new one. Does it happen on all XP PC's ?

Try without the hook dll's

[jeffw_00]

Hi Rudi -
1) "Try without hook DLLs" - I'm sorry - can you explain a little better what I should do? Sorry!

2) I have 3 PCs A,B,C. A and B are running XP. C is running W7, A,B,C are all running 1.1.9.6

B viewing A -> any apps closed on A give me an App error.
A viewing B -> refresh of sub-windows doesn't always happen as expected.

B viewing C, C viewing B - no problems whatsoever.

So A has something odd going on. I tried a complete uninstall/reboot/reinstall/reboot on A and no change. There's -very- little running on A (no TSRs, etc), so I'm not sure what I can provide to help, but the failure behavior is rock-solid-repeatable on A.

Should I try an older version on A? Which one?

Thanks!
/j

[jeffw_00]

does anyone know what "Try without hook DLLs" means?

/j

[Rudi De Vos]

options properties server
screen server update handling
[v]poll fullscreen
...
[v]system hookdll <<< try without
....

[jeffw_00]

[v]system hookdll <<< try without
===============
This appears to have fixed it.

THANKS!
/j

[B0ff1n]

I have had the same problem, both with v1.1.8.1 and v1.1.9.6, Windows XP is the remote PC, but only crashes the app if it displays a WPF window. If I run the same app and it only displays VB6 GUI it's ok, display any WPF window and it gives the application error dialog.
Unchecking the "System HookDll" option cures it. Hope this extra info helps, great product btw.

Yours,
Steve.