Update Clients from real vnc, ultravnc old releases to 19_11

[sepp]

Hello,

first of all great job.

I want to modify fustpush to update all my clients.

I)
Is this the following the right way?

1. stop or kill winvnc.
2. delete the directory (ultravnc or orl ...)
3. delete the driverfiles (windows\system32\vnc*.* windows\system32\dirvers\vnc*.*)
4. copy the files to %progfiles%\Ultravnc\
5. setupdrv install /s

So far I understand the new dirver will be active after next boot?
But I can work without problems until then (just slower)?

II)
Or have I to:
1. unistall the drivers (setupdrv unistall) boot !
2. install (setupdrv install)

III) Are the registry entries which fastpush sets enough, or are there some extra for ultravnc needed?
1. Or should I export from an RC18 and import on them on the new or updatet machine.

IV) Are there extra registy entries for the driver needed, or is everything ok when done like I) 3 - I) 5.

V) Something special on windows 2000 (dirver and so on) ?

I KNOW A LOT OF QUESTIONS

but in the end I hope a can share the result for all !!!

Bye, Sepp

[Rudi De Vos]

TEST19 is still in progress.
Don't roll it out on a bunch PC, only testing.

TEST19 use driver version detection.
No special things are needed to upgrade vnc.
1. stop or kill winvnc. OK
2. delete the directory (ultravnc or orl ...) NOT NEEDED
3. delete the driverfiles (windows\system32\vnc*.* windows\system32\dirvers\vnc*.*) NOT NEEDED
4. copy the files to %progfiles%\Ultravnc\ OK
5. setupdrv install /s OK (installs, not /s)
setupdrv install perform install or update, ths is handles by the MS device manager.
Upgrades are usual active after reboot.
TEST19 should detect an old driver version and temporal disable the driver option until reboot

TO CHECK:
If an upgrade is done, does the device manager copy the new dll before or during the reboot. If before, vnc could be tricked that the new driver is already present.

III) Only the MS-logon has special regs, not in ORL
(groups and group setting)

IV) No

V) No, but i have noticed that on w2k the uninstall gives sometimes problems.
setupdrv Uninstall on w2K does 2 things
1) remove vncdrv.sys (needed, to be able to remove a video driver on w2k)
2) add runonces in reg (setupdrv uninstall2)
uninstall2 does the actual removing after reboot.
This is almost the same what XP does when you remove a video driver

[sepp]

I) 3)

I have to delete the drivers first and start "setupdrv.exe installs" to update the drivers. At the next reboot the new drivers are active, otherwise the old dirvers stay active.
testet witch rc11 and test19_11

Or is there another way?