1.) Password can only be 7 chars or less
2.) Dynalias option is not functioning properly.
3.) Connection forcibly closed error when using a repeater [topic=9609]Workaround[/topic]
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
Known Problems with PCHW Rel 1.0
Known Problems with PCHW Rel 1.0
Last edited by bevtech on 2009-05-31 09:18, edited 2 times in total.
Bevtech
Windows XP Home, Pro SP2, Windows 2003 SBS server SP2(EN), Windows Media Center Editon 2005,Windows Vista Home Prem.,Fedora Core 6,Win9X, PChelpware Rel 1.0,
UVNC V 1.0.8.2
User not developer..
Windows XP Home, Pro SP2, Windows 2003 SBS server SP2(EN), Windows Media Center Editon 2005,Windows Vista Home Prem.,Fedora Core 6,Win9X, PChelpware Rel 1.0,
UVNC V 1.0.8.2
User not developer..
-
- 8
- Posts: 9
- Joined: 2007-03-13 11:52
- Location: Almaty, Kazakhstan
Re: Known Problems with PCHW Rel 1.0
If connection is lost after gone into chat mode, chat windows are staying visible on both server and viewer sides. Writing to any of them has no effect, there is no even an error.
However, you can reconnect and start chat again in new windows.
However, you can reconnect and start chat again in new windows.
Last edited by oxygene.core on 2007-03-25 08:02, edited 1 time in total.
Re: Known Problems with PCHW Rel 1.0
1. Office 2003 menu problem. (It's impossible to see an any menu. E.g in Outlook)
2. Often the screen remain dirty and you need to refresh manually.
Ciao
L.
2. Often the screen remain dirty and you need to refresh manually.
Ciao
L.
Last edited by lupick on 2007-04-02 16:01, edited 1 time in total.
Re: Known Problems with PCHW Rel 1.0
Initializing problems with some
- Windows 2003 Server R2
- Windows Vista
- Maxdata Computers
- Windows 2003 Server R2
- Windows Vista
- Maxdata Computers
Re: Known Problems with PCHW Rel 1.0
from what I've seen on a Win98SE machine, the chat window scrolls text from bottom to top, (the last chat text appears at the top of the chat window, which then scrolls off the screen)
Makes chatting kind of useless, anyone see this?
Makes chatting kind of useless, anyone see this?
Re: Known Problems with PCHW Rel 1.0
I encountered a problem with Retrospect Express HD 2.0 being invisible, similar to what was described above about the Office 2007 button/menu being invisible.
Also, I think the program has crashed EVERY time I've ever tried to change the "Quality" radio button to anything other than "High" (on the technician side). There have been a few times where I was working with a customer who had "slow DSL" and I wanted to sacrifice some quality in favor of speed, but this option didn't seem to work. Has anyone else been able to do this?
Also, I think the program has crashed EVERY time I've ever tried to change the "Quality" radio button to anything other than "High" (on the technician side). There have been a few times where I was working with a customer who had "slow DSL" and I wanted to sacrifice some quality in favor of speed, but this option didn't seem to work. Has anyone else been able to do this?
Re: Known Problems with PCHW Rel 1.0
I found an issue w/ the server side.
If you create a client, not require a password and let the end user type the id in, it works fine for the first round, but if they shoudl time out, not connect to repeater for some reason, etc.. Unless you close the program, if you change the ID, it still sends the old id to the server.
for instance, I connect, enter '1234' as the login, auto send password.
if it times out/can't connect/force it to stop/etc. if I enter 6789, it still makes a connection to repeater at 1234.
Between that, and lack of a regularly working linux/unix/repeater (if they get rid of UUID out of the SVN, it compiles w/o additional libs, but even then, that one tanks.)
Using the latest DLL's that were available for download. Will be going back to uvnc sc probably.
If you create a client, not require a password and let the end user type the id in, it works fine for the first round, but if they shoudl time out, not connect to repeater for some reason, etc.. Unless you close the program, if you change the ID, it still sends the old id to the server.
for instance, I connect, enter '1234' as the login, auto send password.
if it times out/can't connect/force it to stop/etc. if I enter 6789, it still makes a connection to repeater at 1234.
Between that, and lack of a regularly working linux/unix/repeater (if they get rid of UUID out of the SVN, it compiles w/o additional libs, but even then, that one tanks.)
Using the latest DLL's that were available for download. Will be going back to uvnc sc probably.