booting to Windows Family Logon, why?

[influent]

I have a Windows 98 computer in my office that boots up to the Windows Logon screen almost every time, even though it's supposed to boot to the Microsoft Networking screen. Sometimes it just goes right into Windows without stopping at any login screen. Once in a blue moon it will let you log in to the network, but I have no idea what's different those times. I know everything is set correctly in Network Neighborhood. Is there something in the registry I can change to force it to go to the network logon screen? Is it the old HP network card that's causing the problems?

 

[jeffbouldin]

1. Start
2. Control Panel
3. Network
4. In the middle of you screen will be a drop down box, make sure it says Client for Microsoft Networking.

 

[jasonboyes]

Also.. if you dont need family login delete it from the list of network resources

Jason Rich Cook -- "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."

 

[influent]

Thanks, Jason. Like I said, I know everything is set correctly in Network Neighborhood, meaning Windows Family is not selected in the dropdown, and not even set as a service. I'm now almost positive that the 16-bit network card is causing the problems.

 

[Win98User]

Hi,
It could be the card or it could be the cable and if you have a central box it could be the patch lead there.

All the best.

 

[jasonboyes]

Was this machine ever used with Family login (users created) if so go into the Windows directory and delete all file with the .pwl extension. These are password files (if I remember correctly) for family login.

Jason Rich Cook -- "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."

 

[influent]

I got it fixed. First I put in a 32-bit network card, which didn't do the trick, but then I changed a registry setting in Local Machine/Network and switched from Quick Logon to the other one, and then it worked.