On Wed, 2003-02-05 at 01:02, J.R. Gaulin wrote: > The nature of the failure is as follows. Under W2K, with an active VNC > connection established, when my app runs it instantiates a copy of the > ActiveX wrapper object (which loads an instance of the MSWINSCK control), to > this point all is okay. The the app then instantiates a second instance of > the ActiveX wrapper object, this works, however the previous instantiation > disappears. Attempting to access the first object generates a "Run-time > error '462': The remote server machine does not exist or is unavailable" > however accessing the second instance works fine. > > >From what I can tell is, ONLY under W2K, if VNC accepts a connection before > my object instantiates a copy of itself VNC forces the component to only > support a single instance of itself (how and why I don't know, its my just > observations) -- if no connection exists prior to the object instantiating, > or if connections are established after the first instance of my component, > eveything is fine and multiple instances of the socket wrapper can exist. > As long as one instance exists prior to a connection, after a connection I > can create/delete as many instances as I want.
This is an interaction with the Deferred updates scheme used by the VNC server. Under WinVNC 3.3.6, the default is not to use deferred updates, (which is partly why 3.3.6 has problems updating some parts of the display correctly.) The default was changed to allow ActiveX applications to behave properly. To turn off deferred updates, look in HKCU/Software/ORL/VNCHooks/Application_Prefs for a key with the name of the problem program. When you find it, sset use_Deferral to zero. Cheers, -- Wez @ RealVNC Ltd. - http://www.realvnc.com Open Source VNC - Commercial Support & Development _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
