Mark, jus to fill you in: compatibility is _not_ the reason that the registry setup is such a mess. It's because the final version of the registry work done by ORL was actually about version 1.1 of the attempt to integrate it into the Windows registry. They have notes in the documentation [ ;) ] that come down to "this should probably be changed eventually".
I think your remarks are dead on about the fixups. It's just like a cordless drill; if you can make one that works right for a construction guy every day, all day, and doesn't break when he throws it in the back of his truck at the end of the day, it will probably work OK for home use, too. ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, 2002-06-10 11:26 Subject: Re: remembering to set user and default passwords > On 08/06/2002 00:08:53 "Alex K. Angelopoulos" wrote: > > > One good way to do this might be to have the installer prompt you for both > > service-mode default passwords and an individual user password. I'm playing > > with a couple of methods for password configuration; the best method is probably > > a post-install script to configure it and import the password set in HKCU to the HKLM key. > > OK and worthwhile, but the one time the documentation is fresh in your memory is during install (isn't it ;-)) > > I note (and I'm referring to Windows version here), when an operationally stable system has been long established, > and in-house VNC-skills decay or are dispersed, one's memory isn't exactly jogged by such things as: > > a) the User and Admin dialogue for password settings is disjoint (and you can't show both at once even if you bother to go there) > > b) the app has to be running in order to obtain/set these values which are in the registry so often featuring in vnc-list replies. > > I appreciate there are probably arguments to do with Unix/Windows compatibility > and abstracting from the notions of dot files and registry (loathe it or loathe it ;-}); > so, addressing this regularly-raised issue warrants extensive e-discussion on usage patterns before the end-user confusion can > be engineered-out of a future VNC build. > > I feel that the target recipient for re-vamped admin dialogues ought to be the VNC para-sysadmin or fire-fighter > and then it will just fall-out that the problems are solved for the regular VNC installers. > > > > ------------------------------------------------------------- --- > Visit our Internet site at http://www.reuters.com > > Any views expressed in this message are those of the individual > sender, except where the sender specifically states them to be > the views of Reuters Ltd. > _______________________________________________ > VNC-List mailing list > [EMAIL PROTECTED] > http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
