I've tried searching the list archives and the FAQs, but haven't found
the answer. I'd be grateful if someone points me in the right direction
if the answer is publicly available.
I regularly use TightVNC to control a PC running Windows 2000
Professional. This PC has been set to show a specific wallpaper bitmap
("Wallpaper A") when it's sat at the login box waiting for someone to
sign in. This wallpaper is set in the Registry value
HKEY_USERS\.Default\Control Panel\Desktop\Wallpaper
When I connect to the PC via VNC the wallpaper vanishes, like it's
supposed to. When I sign into the PC (also over VNC) my normal
wallpaper ("Wallpaper B") appears for a few seconds and then reverts
back to Wallpaper A. I don't mind terribly since Wallpaper A is just
some text warning any nosy parker that use of my machine is restricted
and that they should leave well alone. Windows policies which restrict
login to just me, and VNC disabling of local inputs help to enforce
that. :-)
If I disconnect from VNC while logged in to the PC the wallpaper
reverts to Wallpaper B again. If I reconnect the wallpaper vanishes
altogether, but when I disconnect again then Wallpaper A flashes for a
second before reverting to Wallpaper B.
I think my question is this: how does TightVNC manage to *change* the
wallpaper, as opposed to merely blanking it? Does TightVNC use
HKEY_USERS\.Default\Control Panel\Desktop\Wallpaper, expecting a null
value? If it then finds a non-null value does it then blank the
wallpaper? If that is the case then why bother checking the value in
the first place; why not just blank the wallpaper regardless?
This happens regardless of whether I use my web browser or the VNC
Viewer application.
Can anyone help?
---------------------------------------------------------------------
To unsubscribe, mail [EMAIL PROTECTED] with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
