From Jeff Shipman, Fri Feb 22 11:01:07 2002
It's true that Win95 requires some sort of login name to enable the 'Save Password' option as Perri says. Also, if you do not enter a password when you create a username, it shouldn't ask you for it anymore. So, my suggestion would be
Jeff Shipman Systems Programmer NMIMT Computer Center
In article <2002022205351085168@zetnet.co.uk> you write:
The message <5oW68.41424$E4.1460657@e3500-atl2.usenetserver.com> from PMorgan <pmorgn.nospam@bellsouth.net> contains these words:
I've been working on this problem for a week or so and things seem to be going from bad to worse. To further complicate matters, I don't have Win95, so I can't duplicate the problem on my own computer (I'm trying to coach my mother, long-distance, on her Win95 computer).
She changed ISP's and needed to set up a new DUN connection, which we did successfully; however, Win 95 won't save her password (I remember this problem from when I had Win 95, but don't remember the solution).
I received a couple of websites from these groups and tried the suggested fixes (regedit, deleting .pwl files) without success. The process of trying the .pwl solution caused her computer to ask her for a Win 95 password upon booting up, and now it asks her every time.
So now I have two questions, as follows:
- Can anyone provide me with a simple, step-by-step fix to her "Save Password" problem in DUN? I'm not a computer pro and found the websites confusing, but I can follow simple directions.
- How do I get Win 95 to stop asking her for a password to boot up?
Sorry to be a pest, and thanks in advance.
Perri
If the machine does not need to talk to other machines over a lan and the only network connection limited to a DUN to the internet, then the microsoft client can be left out. The trouble is, that then disables the 'save password' option in the DUN connectoid window. Sadly, although microsoft client isn't strictly required, if you want to keep the save password option, you'll have to add it to your network components list. In short, this *might* be the cause of your problem.
--
John Stigter
jcs.computers@zetnet.co.uk