Hi,
OS: Windows 2000 pro SP4
I was using RC20.5 and working fine. I uninstalled it. And I installed V1.0.0. The installation goes without error.
The mirror driver is installed but when someone connected it doen't get activated and everything is slow and also I got a very high CPU. I tried everything (uninstalled,install,registry flush,delete,boot... any order you like I did it). I ran into a post talking about the registry key with the value Attach.ToDesktop that should be to 1. I put that value to 1 and it always reverting to 0. And also it is the only value there the ...BitsPerPel and ...Xresolution are not there.
I also ran into some post stating that the files of the driver should have the same version to be valid otherwise the driver will not get activated.
The file version I get with the check video driver are:
C:\winnt\system32\vncdrv.dll Version: 1.00.19
C:\winnt\system32\Drivers\vnccom.SYS Version: 1.0.0.17
C:\winnt\system32\Drivers\vncdrv.SYS Version: 1.00.17
Notice the numbering of the version is not consistant the number of dot in 1.0.0.17 and 1.00.17 is different. I dont know if it's matter. And the version of vncdrv.dll and vncdrv.sys are different but the number of dot is matching.
I hope someone could find the solution for my problem.
Thanks a lot.
[mod=494,1123520762]moved from fix 1.0.0 to General help[/mod]
Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: https://forum.uvnc.com/viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
Can't activate Mirror Driver
Can't activate Mirror Driver
Last edited by Fontaine on 2005-08-08 17:06, edited 1 time in total.
If you have a look in your system32 folder you can find that the version number are correct : 1.0.0.19, 1.0.0.17, etc.
The problem is out there ...
I post the problem here : [post=13348][/post]
The problem is out there ...
I post the problem here : [post=13348][/post]
Last edited by AssurJur on 2005-07-07 06:49, edited 1 time in total.
- Rudi De Vos
- Admin & Developer
- Posts: 6863
- Joined: 2004-04-23 10:21
- Contact:
Rel1.00 can use
C:\winnt\system32\vncdrv.dll Version: 1.00.19 or 1.00.18
C:\winnt\system32\Drivers\vnccom.SYS Version: 1.0.0.17
C:\winnt\system32\Drivers\vncdrv.SYS Version: 1.00.17
+ 15 and 24 bit are not supported by the driver
+Check device manager (w2k) sometimes keep the old driver
installed -->only 1 mirror driver installed ?
Activate logging.
Possible this file contain some info why the driver does not start.
What was the previous version of the driver installed (RC18 ?)
C:\winnt\system32\vncdrv.dll Version: 1.00.19 or 1.00.18
C:\winnt\system32\Drivers\vnccom.SYS Version: 1.0.0.17
C:\winnt\system32\Drivers\vncdrv.SYS Version: 1.00.17
+ 15 and 24 bit are not supported by the driver
+Check device manager (w2k) sometimes keep the old driver
installed -->only 1 mirror driver installed ?
Activate logging.
Possible this file contain some info why the driver does not start.
What was the previous version of the driver installed (RC18 ?)
- Rudi De Vos
- Admin & Developer
- Posts: 6863
- Joined: 2004-04-23 10:21
- Contact:
Try 16 bit.
The problem is the vnc translate 24bit in 32bit and internal use a 32bit buffer.
The driver framebuffer follow the video card -> 24bit..
The high speed and low cpu is done by letting vnc direct access the driver framebuffer, we can not swap the 32bit by a 24bit buffer --> BSOD
Perhaps for Beta2, but we need to break compatibility with other versions
to do it.
The problem is the vnc translate 24bit in 32bit and internal use a 32bit buffer.
The driver framebuffer follow the video card -> 24bit..
The high speed and low cpu is done by letting vnc direct access the driver framebuffer, we can not swap the 32bit by a 24bit buffer --> BSOD
Perhaps for Beta2, but we need to break compatibility with other versions
to do it.
Hi all,
Same problem here ...
It sure works with 16 bits, but we've thousands of machines using Intel Graphics Chipsets with 24 bits coulour depth ... so switching to 16 bits is a non-issue for us ...
Using Ultr@VNC without the mirror driver is so painfull for these targets that it's not an issue either ...
Can we hope to see a 24 bits version of the video driver (even if it breaks compatibility with other VNC flavours) comming next ?
Anyway, the Ultr@VNC team is doing a realy nice work !
This is the best VNC flavour I ever used & customized ...
Regards,
Eric.
Same problem here ...
It sure works with 16 bits, but we've thousands of machines using Intel Graphics Chipsets with 24 bits coulour depth ... so switching to 16 bits is a non-issue for us ...
Using Ultr@VNC without the mirror driver is so painfull for these targets that it's not an issue either ...
Can we hope to see a 24 bits version of the video driver (even if it breaks compatibility with other VNC flavours) comming next ?
Anyway, the Ultr@VNC team is doing a realy nice work !
This is the best VNC flavour I ever used & customized ...
Regards,
Eric.