Best Way for driver update

sepp · Post by **sepp** » 2005-03-31 12:49

I wan`t to update a lot of clients with different versions of vnc and uvnc.
I modifey the fastpush script to transfer all the files of the Ultravnc dir.
It would be more then nice if the client`s (some are servers) haven`t to be restartet after thr update.

Now my question: What`s the best way to upgrade the driver (4)?
It have to be sure that the new driver is installed on w2k too!

1. I stop the winvnc.exe
2. remove registry settings
HKLM/software/ORL
HKCU/software/ORL
3. copy all files of new version to %Programm files%/ultravnc
(overwrite old ones)
4. Driver UPDATE ???
a) Setupdrv uninstall
b) Setupdrv install
OR
a) overwrite files in windows\system32\ and
windows\system32\drivers
b) pherhabs delete registy key for driver... and set new registry key which one ?

5. Set registry key`s like desired for HKLM/software/ORL and
HKCU/software/ORL
6. start winvnc

Thanx for help !

lizard · Post by **lizard** » 2005-03-31 14:36

since the driver includes device driver "Winvnc video hook driver" and kernel-mode service "vncdrv," it is not possible to upgrade it without rebooting your system.
as far as i know, there has never been a better way than below.

setupdrv uninstall
(driver "scheduled" to be uninstalled on next reboot)

shutdown -r -t 0
(windows restarts and driver gets uninstalled)

setupdrv install
(the new version of driver is installed)

good luck

redge · Post by **redge** » 2005-03-31 17:24

It is possible to use script force deleting even is locked with software like below without many update step.
That make possible only 1 step update for UltraVNC and hook driver or any VNC flavors ?

http://www.nuage.ch/projets/ForceDelete.zip

You can see source code of the programmer if there code can help you to do only 1 step update of any vnc flavor

I don't know use scripting..., sorry, i can't try for you.

lizard · Post by **lizard** » 2005-03-31 19:43

thanks to redge for the info.
it seems the tool you've just shown is to schedule file/directory deletion on next boot, by editing certain registry entry.
for one-step driver update, you have to be able to
*uninstall kernel-mode service without system reboot
*uninstall device driver from current hardware profile without system reboot
and i don't think WindowsNT is capable for such action.

redge · Post by **redge** » 2005-03-31 20:30

lizard

Thank you very much for the very clear information

Scripting stay to much complex to do and risky for my end-user level skill and can't connect after vnc server updating remotely.

so, I can wait for this nice feature v2 was wrote Rudi

Post by **Rudi De Vos** » 2005-03-31 21:00

What is the current driver version.
If you are lucky and have RC18, you don't need to update it.
RC18 driver is compatible with RC20

Only the vncdrv.dll has changed.(removed some debug info
and added a buffer overrun protection"lost updates").

Because both vncdrv.dll are compatible you can easy replace
on reboot (xcopy).