I'm at least glad to hear I am not the only one. I get by by clicking the controls whenever I restart the system, but I need a more solid solution.
_Ron ----- Original Message ----- From: "Chris Gillard" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, March 02, 2002 2:59 PM Subject: Re: VNC Enables/Causes Windows Apps to Crash : Ron, : : I see the same problem with some of our Delphi 5 apps running on : NT4/SP6a servers and VNC 3.3.3R9. : : We have had this problem for a year or so, but have always doubted : our own Delphi work. : : Literally in the last few days we had pinned it down to the use of : VNC & certain mouse movements. You have got this in more detail. : : We had tried different video drivers, to no avail. : : My next move is to try Tight VNC to see if it is any different. : : A real shame as VNC has been a great tool for us. : : If anyone else has any bright ideas ?? : : Regards : : Chris : : -- Chris Gillard, [EMAIL PROTECTED] on 02/03/2002 : : On Sat, 2 Mar 2002 11:30:11 -0500, Ron Struempf wrote: : >Several of my Windows apps, written in CBuilder and Delphi, crash : >when : >WinVNC is running. I saw the FAQ Q39, but it says "disable any : >screen : >savers" of which I have none. I've been using Procomm Rapid Remote : >for a : >very long time to access these servers, but switched to WinVNC : >because Rapid : >Remote is the only app I've seen so far that crashes XP. : > : >We are running WinVNC 3.3.3 R9 in App Mode on NT 4.0 Server. : > : >What I've found is: : >- The app crashes in one of several mouse events (such as : >CM_NCHITTEST) : >- In my debugging, it appears as though the associated : >WM_NCHITTEST : >message never appeared : >- The crash happens when the mouse cursor passes over the : >statusbar : >- The crash happens whether I am connected via VNC or Rapid Remote, : >and : >probably local as well : >- I believe that the crashes continue to happen even after I close : >VNC, : >but apparently at a much lower : >frequency. : > : >I have also found that if I physically click on each focusable : >control on : >the app, that the crash does not occur again until the app is : >restarted. : > : >My theory is that WinVNC is absconding with some of the WM_???? : >messages, : >but not suppressing the CM_???? messages they generate. Thus, when : >the app : >processes the control message (CM_???), it expects initialization to : >have : >been performed when the Windows message (WM_???) was received. By : >clicking : >on each of the controls, I force it to do that initialization, so : >the crash : >doesn't happen. : > : >_Ron : >--------------------------------------------------------------------- : : >To unsubscribe, mail [EMAIL PROTECTED] with the line: : >'unsubscribe vnc-list' in the message BODY : >See also: http://www.uk.research.att.com/vnc/intouch.html : >--------------------------------------------------------------------- : --------------------------------------------------------------------- : To unsubscribe, mail [EMAIL PROTECTED] with the line: : 'unsubscribe vnc-list' in the message BODY : See also: http://www.uk.research.att.com/vnc/intouch.html : --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html ---------------------------------------------------------------------
