I used filemon to monitor my hard drive activity.
I noticed that the ultravnc.ini file is red every 5 seconds.
That is slowing down my system.
So the following sequence repeats forever:
23:03:16 winvnc.exe:1844 OPEN C:\Program Files\UltraVNC\ultravnc.ini SUCCESS Options: Open Access: Read
23:03:16 winvnc.exe:1844 LOCK C:\Program Files\UltraVNC\ultravnc.ini SUCCESS Excl: No Offset: 0 Length: -1
23:03:16 winvnc.exe:1844 QUERY INFORMATION C:\Program Files\UltraVNC\ultravnc.ini SUCCESS Length: 1218
23:03:16 winvnc.exe:1844 READ C:\Program Files\UltraVNC\ultravnc.ini SUCCESS Offset: 0 Length: 1218
23:03:16 winvnc.exe:1844 UNLOCK C:\Program Files\UltraVNC\ultravnc.ini RANGE NOT LOCKED Offset: 0 Length: -1
23:03:16 winvnc.exe:1844 CLOSE C:\Program Files\UltraVNC\ultravnc.ini SUCCESS
23:03:16 winvnc.exe:1844 OPEN C:\Program Files\UltraVNC\ultravnc.ini SUCCESS Options: Open Access: Read
23:03:16 winvnc.exe:1844 LOCK C:\Program Files\UltraVNC\ultravnc.ini SUCCESS Excl: No Offset: 0 Length: -1
23:03:16 winvnc.exe:1844 QUERY INFORMATION C:\Program Files\UltraVNC\ultravnc.ini SUCCESS Length: 1218
23:03:16 winvnc.exe:1844 READ C:\Program Files\UltraVNC\ultravnc.ini SUCCESS Offset: 0 Length: 1218
23:03:16 winvnc.exe:1844 UNLOCK C:\Program Files\UltraVNC\ultravnc.ini RANGE NOT LOCKED Offset: 0 Length: -1
23:03:16 winvnc.exe:1844 CLOSE C:\Program Files\UltraVNC\ultravnc.ini SUCCESS
23:03:16 explorer.exe:188 QUERY INFORMATION C:\Program Files\UltraVNC\winvnc.exe SUCCESS Attributes: A
23:03:16 explorer.exe:188 OPEN C:\Program Files\UltraVNC\winvnc.exe SUCCESS Options: Open Access: 00100020
23:03:16 explorer.exe:188 QUERY INFORMATION C:\Program Files\UltraVNC\winvnc.exe SUCCESS Length: 1590216
23:03:16 explorer.exe:188 CLOSE C:\Program Files\UltraVNC\winvnc.exe SUCCESS
23:03:21 winvnc.exe:1844 OPEN C:\Program Files\UltraVNC\ultravnc.ini SUCCESS Options: Open Access: Read
23:03:21 winvnc.exe:1844 LOCK C:\Program Files\UltraVNC\ultravnc.ini SUCCESS Excl: No Offset: 0 Length: -1
23:03:21 winvnc.exe:1844 QUERY INFORMATION C:\Program Files\UltraVNC\ultravnc.ini SUCCESS Length: 1218
23:03:21 winvnc.exe:1844 READ C:\Program Files\UltraVNC\ultravnc.ini SUCCESS Offset: 0 Length: 1218
23:03:21 winvnc.exe:1844 UNLOCK C:\Program Files\UltraVNC\ultravnc.ini RANGE NOT LOCKED Offset: 0 Length: -1
23:03:21 winvnc.exe:1844 CLOSE C:\Program Files\UltraVNC\ultravnc.ini SUCCESS
23:03:21 winvnc.exe:1844 OPEN C:\Program Files\UltraVNC\ultravnc.ini SUCCESS Options: Open Access: Read
23:03:21 winvnc.exe:1844 LOCK C:\Program Files\UltraVNC\ultravnc.ini SUCCESS Excl: No Offset: 0 Length: -1
23:03:21 winvnc.exe:1844 QUERY INFORMATION C:\Program Files\UltraVNC\ultravnc.ini SUCCESS Length: 1218
23:03:21 winvnc.exe:1844 READ C:\Program Files\UltraVNC\ultravnc.ini SUCCESS Offset: 0 Length: 1218
23:03:21 winvnc.exe:1844 UNLOCK C:\Program Files\UltraVNC\ultravnc.ini RANGE NOT LOCKED Offset: 0 Length: -1
23:03:21 winvnc.exe:1844 CLOSE C:\Program Files\UltraVNC\ultravnc.ini SUCCESS
23:03:21 explorer.exe:188 QUERY INFORMATION C:\Program Files\UltraVNC\winvnc.exe SUCCESS Attributes: A
23:03:21 explorer.exe:188 OPEN C:\Program Files\UltraVNC\winvnc.exe SUCCESS Options: Open Access: 00100020
23:03:21 explorer.exe:188 QUERY INFORMATION C:\Program Files\UltraVNC\winvnc.exe SUCCESS Length: 1590216
23:03:21 explorer.exe:188 CLOSE C:\Program Files\UltraVNC\winvnc.exe SUCCESS
Is it a bug or a feature ?
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
reading ultravnc.ini indefinitely
Re: reading ultravnc.ini indefinitely
I don't know, but I find it kind of funny that it can do that every 5 seconds but <b>never</b> checks for new local NIC card IP addresses to bind to.
Re: reading ultravnc.ini indefinitely
At least somebody can confirm this behavior on his PC, Please ? At least I just want to know whether it is only a problem with my PC ?
You can check with process monitor or Filemon:
Filemon:
http://en.utilidades-utiles.com/downloa ... ows-xp.php
Process monitor :
http://technet.microsoft.com/en-us/sysi ... 96645.aspx
I can see in the log RANGE NOT LOCKED errors.
No idea what is the meaning.
Thank you
You can check with process monitor or Filemon:
Filemon:
http://en.utilidades-utiles.com/downloa ... ows-xp.php
Process monitor :
http://technet.microsoft.com/en-us/sysi ... 96645.aspx
I can see in the log RANGE NOT LOCKED errors.
No idea what is the meaning.
Thank you
Re: reading ultravnc.ini indefinitely
I can repeat exactly the same result.
During this process, I even try to:
1. Change the password -- I edit the ultravnc.ini directly
 However, the Ultravnv server not implementing the change I made, working as before, but keep on reading the ultravnc.ini every 5 seconds.
2. Delete the ultravnc.ini
 The Filemon reflects the Ultravnv server realizing this fact, and reporting "Not Found". Again, the Ultravnv server still working normally but keep on trying to read the ultravnc.ini every 5 seconds.
Your discovery is really interesting!
During this process, I even try to:
1. Change the password -- I edit the ultravnc.ini directly
 However, the Ultravnv server not implementing the change I made, working as before, but keep on reading the ultravnc.ini every 5 seconds.
2. Delete the ultravnc.ini
 The Filemon reflects the Ultravnv server realizing this fact, and reporting "Not Found". Again, the Ultravnv server still working normally but keep on trying to read the ultravnc.ini every 5 seconds.
Your discovery is really interesting!
Last edited by YY on 2010-06-16 03:05, edited 1 time in total.
- Rudi De Vos
- Admin & Developer
- Posts: 6863
- Joined: 2004-04-23 10:21
- Contact:
Re: reading ultravnc.ini indefinitely
Every 5 seconds there is a timer that update the tray icon.
Possible some parameter is read from the ini file, normal this shouldn't be needed... and cached value should be used.
Possible some parameter is read from the ini file, normal this shouldn't be needed... and cached value should be used.
Re: reading ultravnc.ini indefinitely
Thank you all for your answers.
Actually, this is prevently my hard-drive to spin down when PC is idle (most f the time when I not home), and makes unexpected accesses to the disk which are interrupting other reading tasks.
Should I submit this to some "requests/bugs" section of the forum ?
Again thank you for having checked this issue with me.
Actually, this is prevently my hard-drive to spin down when PC is idle (most f the time when I not home), and makes unexpected accesses to the disk which are interrupting other reading tasks.
Should I submit this to some "requests/bugs" section of the forum ?
Again thank you for having checked this issue with me.
Re: reading ultravnc.ini indefinitely
Really? It spins up the drive instead of reading ultravnc.ini from disk cache? That stinks. I guess you could always run the whole thing from a virtual RAMDisk or something.
To me this does sound like something that should be addressed in the long term. (What if, for example, the drive that started WinVNC is removable; will a running WinVNC crash when that drive is eventually removed?)
You've got Rudi's attention, so that's a good thing. Honestly I'm not sure whether you're supposed to post in Requests/Bugs too, but I guess it couldn't hurt.
To me this does sound like something that should be addressed in the long term. (What if, for example, the drive that started WinVNC is removable; will a running WinVNC crash when that drive is eventually removed?)
You've got Rudi's attention, so that's a good thing. Honestly I'm not sure whether you're supposed to post in Requests/Bugs too, but I guess it couldn't hurt.