Thanks James. I'm trying to get the Microsoft guy to troubleshoot this issue (which, as you know is not limited to ActiveX's interactions with VNC). Would you by any chance have a list of the windows messages which seemed to throw ActiveX into hysterics in 3.3.7?
Dan -----Original Message----- From: James Weatherall [mailto:[EMAIL PROTECTED] Sent: March 22, 2005 11:19 AM To: Dan Chernin; [email protected] Subject: RE: VB error in 4.3.7 (really 3.3.7) Dan, Any messages that the ActiveX application is not expecting will cause it to misbehave, in our experience. This is clearly a problem with ActiveX, since it effectively means that it is impossible to broadcast a message to all windows in the system, which is functionality used by the operating system itself (although presumably only with messages that ActiveX is able to cope with, otherwise half the OS would fail...) :) Cheers, Wez @ RealVNC Ltd. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Dan Chernin > Sent: 22 March 2005 13:08 > To: James Weatherall; [email protected] > Subject: RE: VB error in 4.3.7 (really 3.3.7) > > James--- > > Could you be a little more specific about the types of > messages which trigger > problems in ActiveX exe's, and what precisely they are. > (Best yet if you > could point me to a MSDN knowledgebase article explaining the > problem). THeir > possition appears to be: "VB has no problems here; its a > problem with all > those other application which don't do what ActiveX expects." > > Dan > > > ________________________________ > > From: James Weatherall [mailto:[EMAIL PROTECTED] > Sent: Tue 3/22/2005 4:41 AM > To: Dan Chernin; [email protected] > Subject: RE: VB error in 4.3.7 > > > > Dan, > > Most ActiveX applications (most notably Microsoft one) are > poorly behaved > and cannot cope with unknown messages arriving in their > message queues. > This is a known issue with Microsoft's ActiveX that the older > vnchooks.dll, > amongst others, could trigger. > > The VNC 4 series hooks are designed not to trigger this bug > in Microsoft's > ActiveX. > > Regards, > > Wez @ RealVNC Ltd. > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of Dan Chernin > > Sent: 22 March 2005 02:45 > > To: [email protected] > > Subject: VB error in 4.3.7 > > > > In certain situations, when trying to create an object from a > > "Thread Per > > Object" VB ActiveX Exe, I get error 462: "The remote server > > machine does not > > exist or is unavailable"; on closer examination, it turns out > > that the exe > > just suddenly "vanished". I can reproduce this consistently > > in VNC 4.3.7, but > > it occurs on other machines which are not even running VNC. > > Further I can no > > longer reproduce it (at least not yet) when running VNC > > 4.1.1. Microsoft is > > claiming that it must have been a bug in the VNC 4.3.7 > > vnchooks.dll that has > > been fixed. Was there such a bug? And if it's a bug in VNC, > > why does the > > problem occur on non-VNC machines: Microsoft's "explanation" > > is that it must > > be a problem with other apps which inject hook DLL's into > > running processes. > > Does this sound plausible? > > > > Thanks... > > > > Dan > > _______________________________________________ > > VNC-List mailing list > > [email protected] > > To remove yourself from the list visit: > > http://www.realvnc.com/mailman/listinfo/vnc-list > _______________________________________________ > VNC-List mailing list > [email protected] > To remove yourself from the list visit: > http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
