Hi There list people ... I was just searching to see how my program "Gencontrol" was doing on google, and spotted this list. Nice to see that someone's using it :) "Evan Mann" wrote: > however, I've had it leave the c:\vnctemp folder with vnchooks.dll in it > (tested against win2003 machine). And when I tried to re-connect to > that machine, it failed because the directory already existed and it > said it can't create a directory that already exists. This is kind of a known issue. Basically what happens is, VNC itself uses windows global hooks in order to capture paint messages and updates the screen. This causes vnchooks.dll to get loaded into some other processes than winvnc.exe, and runs some of its code inside other processes' paint routines. Normally this works ok, but for some reason, under some circumstances, some of these processes don't "let go" of the .dll in time, or at all. This means the DLL is still locked, which prevents Gencontrol from cleaning it up. If you try to connect again while it's still locked, it attempts to write over a new version of vnchooks.dll and fails - thus causing this error. I don't actually have a windows2003 box here to test it with unfortunately - so it may not get fixed. Also this is really a VNC issue not Gencontrol itself. Gencontrol is more of a glorified loader. -- "Monahan, Thomas" Spotted that > Doesn't work too well with re-mapped drives tho. :-( No, it doesn't. This is a known issue. At the moment it relies on the C$ share being present and writeable. On nearly all machines, this is the case. However, if this is not the case, it won't work. I hope to for the next version - Remove the dependency on C$ share (Will create its own temporary share, and remove it again afterwards) - Automatically detect system root drive letter, and use that instead of C: Unfortunately I looked at both of these things and they seemed non-trivial, but possible. -- "Turman, David C." noted: > But if Remote Registry is not running on the remote PC you can't get > in. It modifies the registry. Temporarily. True. It will probably always need remote registry. -- "Ryan Lambert" commented (regarding the source code): > It was hard to tell because I only have a plain text viewer and it's > showing strange characters... so parsing was a pain. It's possible that you're using a text editor which doesn't understand Unix format. I do a lot of work in Linux, and even though this is a Windows program, it is highly likely that I've saved the source code (or some of it) in Unix format. Having said that, none of *MY* tools have a problem :) In my experience, most Windows text editors (Notable exception: Notepad) don't have a problem reading Unix text files. -- Hope that clears a few things up Enjoy, Mark Robson Technical Consultant Gensortium Limited ******************************************************** This Week's Sponsor - RTO Software / TScale What's keeping you from getting more from your terminal servers? Did you know, in most cases, CPU Utilization IS NOT the single biggest constraint to scaling up?! Get this free white paper to understand the real constraints & how to overcome them. SAVE MONEY by scaling-up rather than buying more servers. http://www.rtosoft.com/Enter.asp?ID=147 ********************************************************** Useful Thin Client Computing Links are available at: http://thethin.net/links.cfm New! Online Thin Computing Magazine Site http://www.OnDemandAccess.com For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link: http://thethin.net/citrixlist.cfm