Hi Scott, Thanks much for the reply. The machine I'm working with has only one user and it's the admin. I neglected to mention the OS info ... I'm running XP Pro SP2.
One note ... I never saw the message before I installed 2.33 but I only used 2.32 for a day or so before updating to 2.33 following your email instructions. I'll try wiping my install and re-installing 2.32 to see what happens. Best Regards, Mike Allton ASU Service, Inc. http://www.ARP-Dedicated.com 877-576-8055 - U.S.A. Toll Free 208.323.0203 - Direct Phone & Fax -----Original Message----- From: Scott Best [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 06, 2008 10:43 AM To: ASU Service Cc: echovnc-users@lists.sourceforge.net Subject: Re: [Echovnc-users] Small thing with EchoVNC 2.33 Mike: Hello! I am unsure about the "preconfigured" message; never saw that, not sure why it would happen. :) Am guessing that the user account you installed EchoVNC with did not have sufficient privilege to create the registry entry that EchoVNC uses for storing passwords. I believe errors like this is why UltraVNC finally gave up on using the Windows registry, and now writes all config information into a file in the install folder. Maybe we should consider that ... for whatever reason, MSFT is intent on changing the security model of their registry use ever service pack.... As for connecting at the login screen, you should simply need to install (register and start) EchoVNC as a standard Windows service. Of course, this requires that you run the installer as an admin-level user. cheers, Scott On Feb 6, 2008, at 8:26 AM, ASU Service wrote: > Hi All, > Long time EchoVNC user . first time poster. > > I have installed 2.33 and it seems to work great but I have one > small problem and a question. > > Problem: > When first booting up I get the following message: > > "no password has been set & this machine has been preconfigured to > prevent users from setting their own. You must contact a System > Administrator to configure echovnc properly." > > I can't seem to find a setting that will alter the "preconfigured" > item. I close that alert box and start EchoVNC and it works fine. > > Question: > Way way back in the day I used to be able to connect to VNC even if > the computer was sitting at the Windows login screen but not any > more. Is there a way to enable something like that? I have a long > road trip planned for later this year and access to my main office > PC is imperative. IF for whatever reason the system ends up > rebooting I can't log into it. > > Thanks in advance for your time. > > Best Regards, > Mike Allton > ASU Service, Inc. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Echovnc-users mailing list Echovnc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/echovnc-users
