\
8h (and 8i) properly go to the website, after password prompt, on XP Pro.

On Vista Ultimate 32-bit, 8i still works properly.

However note (Vista): When exiting the screensaver mode, a "black" window pops open for a moment. That seemingly occurs regardless of how I get out of the screensaver (move mouse, etc.), and regardless of whether the "password" option is turned on or off. [Not thoroughly explored, but it has happened enough times to be reported as an annoyance]

That's to prevent all the full-screen black flashes that everyone had been reporting a couple of months ago. By switching to windowed mode an instant before exiting, most of the drama in Vista is avoided.

...however, it also does that on XP, providing additional drama for XP.

I'm not sure it's worth fixing, but I did want to make sure it's known.

Ok, I have to ask: how does a process in the null session get a .js to launch in another session? It doesn't seem like that should even be possible under Windows' security rules.

~Ralph S.

Remember, Microsoft says, "If someone has physical access to your computer, then it is not secure". In other words, they won't fix bugs in their OS that someone can only take advantage of by being at your machine (i.e. accessing a Win XP machines users files by booting with a Windows 2000 Professional CD).

Their scripting engine called WScript has a method to impersonate the original user that ran the screensaver. Otherwise, I would have given up with the WebSite button for Vista.
What was weird is that in XP, it doesn't seem to matter that it came from a null session. I really did need the WScript but to make it work the same on all the Windows as possible, it calls the same script.