SC and VISTA <-- Making it work!

[nerdygirl_ellie]

On Vista, by default, the singleclick application is clunky and takes 10-15 seconds to do a screen redraw.

Suffer no more, here is the fix!

Have the remote user right click on the uvnc icon on the taskbar, and go to properties. Then UN-check the "Poll full screen (fast)" box and click Apply.

Viola, Fast SC on Vista.

Elizabeth Greene
IT Manager, GlobalOptions Inc.

[nerdygirl_ellie]

We need a developer to step up and Automatically turn that off if Vista is detected as the host OS. Any Takers?

[bevtech]

Use pchelpware instead..

www.pchelpware.com works in vista now

subtopic pchelpware and please do not double post..

[nerdygirl_ellie]

Hi Bevtech. Sorry about the double post. After 3 weeks of click-n-wait I was a LOT excited about finding it.

How is that linux client for pchelpware coming? Kind of hard to port it with that closed source .dll in there. I am not griping about keeping it closed source, I understand why the author did it and he is well within his rights to do so but for those of us that run linux and support windows boxes, singleclick is the soup!

-ellie

[JaleXNet]

is true, but, it is necessary to install hook driver (Ultravnc_Addons_Setup_104RC4.exe).

works very fast in Vista Ultimate (Aero is automatically disabled).

Pd: Sorry my english

saludos desde Chile

[dburanen]

While PCHelpware works Bev, PCHelpware does not work in Linux where SC did. Here's hoping for an updated SC.

[pilotsnipes]

Yes - just adding my voice for an update SC for vista too please!!!

[Far-Far-Away]

One more vote for SC support for Vista.

We use both SC and PcHelpware and have found that SC is much lighter to use at HelpDesk end.

These are the main reasons why we like to use SC:

REASON 1: IF HelpDesk end is not running, SC is just one click away:

To initiate a connection with
SC:
1. Helpdesk just click shortcut on their desktop -> connection is made

PCHW:
1. Helpdesk clicks shortcut on their desktop
2. Selects his name "user.phw"
3. Enters pin (if not already appearing)
4. Clicks Start -> connection is made


REASON 2: Slow modem connection works faster on SC:

To make slow connection refresh screen faster
SC:
1. Connection options
2. Untick auto select best settings
3. tick 8 dark colors
4. Now screen is BW and refresh much faster on slow modem connections

PCHW:
1. I have not found how to reduce colors to BW



If you know solutions, please let me know.

[SuperTurtle]

One more vote for SC support for Vista.

PCHW:
1. Helpdesk clicks shortcut on their desktop
2. Selects his name "user.phw"
3. Enters pin (if not already appearing)
4. Clicks Start -> connection is made

There is no need to go through all of the above steps. If you create a client using PCHw, then the users will have the same number of clicks as SC. (and, PCHW works on vista).

Just change the connection line from:

-connect 192.168.1.1:80 -id 4567 -passwd 202CB96

To
- direct -connect 192.168.1.1:80 -id 4567 -passwd 202CB96

If you do the above, then you get a true single click connection.
(I am using the repeater, if not then get rid of “-id 4567 in the above). (so, just add the –direct to remove the prompts)

REASON 2: Slow modem connection works faster on SC:

PCHW:
1. I have not found how to reduce colors to BW

Try clicking on the “low” setting BEFORE you start the session. It will be black and white. It does help a lot. However, you can’t reduce the colors down to 4 bits like in SC.

However, PHCW does work on vista for its single click system. I will test it on a *known* slow machine later today to see how it works (and will post back here). If this fixes the speed problem I been experiencing on *some* vista machines, I will switch to PCHW

Super Turtle

[SuperTurtle]

I test on a known machine later today

Ok, I gave PCHW a try on a known Vista machine what was SLOW AS DOGS with SC (ultra VNC). The SC version was just simply un-useable, and screens would not re-plot (it is not a connect speed issue, but simply some repot, or polling issue).

With PCHW, it worked very well. Obviously, whatever the polling issue was, it been addressed in this new version. Thumbs up to the PCHW folks…you get a pat on the back. (so much so, I am now switching over to PCHW, and dropping SC).

I do missing some things in the change over. The lack of the file transfer window is an example. I assume the clipboard features can also be used to transfer a file (but I not been able to get the key sequences to work for cut/paste correctly (I obviously I am missing how the clip board and cut/paste keys work).

I also find that the start up in PCHW is better from a user point of view (no double click needed, but just a connect to press). Furthermore, I added the [DIRECT] to the helpdesk.txt file, so, users don’t even have to click anything.

I not sure I like the fact that users have to hit the “quit” button AFTER I already ended the session, (but, it very minor deal. And, I *can* hit that quit button for them DURING the session to end it. I also suspect some users feel better about hitting the quit button anyway. So, this is fine to me.

However, in the case of a dropped connection, or if I ended the session too soon, having that dialog remain on the screen with the connection button is 100 TIMES BETTER then the user re-loading, and re-running the SC program. So, in effect, I just was never used to having that dialog box remain AFTER the session (but, as I think about this…it is a GOOD decision, since is MUCH easer for users to re-connect during a session if need be.

I do miss the disabling of the wall paper, but again that was just by habit I had much trained my clients that the wallpaper is gone means I doing support, when I end, the return of wall paper signifies my leaving of the session. However, from a performance point of view, even very large wallpapers download and plot very fast (so, again, very minor..and likely some users are disturbed that wall paper goes away).

I certainly like the autoreconnet option of PCHW (in case of a flakey, or bad connection, having this option is really nice. Something that SC was badly missing (I think there might have been some edits that do autoreconnect).

I should note that I am not using the “–autoreconnect” feature of PCHW just yet, but I think having two versions ready in case of a problem connection is nice.

Other quirks in PCHW are very minor, and likely will be fixed over time (for example, the tray icon remains after the session is closed – if you hover your cursor over the try..the icon unloads).

However, since SC has rotten performance in Vista, I had to give up on SC…..

Hello PCHelpWare!! All in all….well done…and I am impressed.


Super Turtle

[ComputerConscript]

Have the remote user right click on the uvnc icon on the taskbar, and go to properties. Then UN-check the "Poll full screen (fast)" box and click Apply.

@nerdygirl...
Nice observation and this certainly does make SC at least usable on Vista. Although it is still a bit sluggish vs connecting to XP clients UNLESS you also select 'Low Accuracy (Turbo Speed)'. ALSO ...
Disabling Aero Theme on Vista also fixes the problem.

I just tested this again and it's important to note that after clicking 'apply', to have the user leave the vnc client user property window open. If they click OK and/or X out of the property window, the SC client settings revert back and the connection becomes sluggish again.

ALSO, there is still a bug with SC/Vista of being disconnected from the client when Vista "A program needs to continue" security alert pops upon launching certain apps (User Account Control).

Thanks!

P.S.
I also vote for an updated SC seeing it works with Linux.

[Shragel]

Also waiting for this update.