Hey, before you get all crazy replacing tapi.dll, try just doing the get-rid-of-DUN-and-rebuild-it part. I recall solving some DUN problems (back when I *had* to use Windows) by just doing that much....didn't have to get a clean copy of tapi.dll, whatever was broke was broke in the shortcut itself.

Try just defining a new connection and see if that's good enough.

Sycamore,

MaggieLs right. Your best bet is to uninstall and reinstall dialup networking. its been a while, and i cant get to a win95 machine right now, but you should be able to go to start>settings>control panel>add/remove programs.

in there you should see a tab called windows setup. in there you should see an item called communication. double click on that and youll see dialup networking. uncheck it, choose ok, let it do its thing and reboot. once rebooted, follow the same process, this time adding a checkmark to dialup networking. upon reboot, you should be okay.

also, if you want to follow microsofts instructions, you should be able to boot to safe mode and rename the file. cold boot, and when you see a black screen with white text saying 'starting windows 95', press f8. if all goes well, youll be presented with a menu. option 3 is safe mode.

good luck!

~james

Just to clarify: start by just creating a new connection definition, see if that works. I've seen *just doing that* fix some DUN problems....although they weren't actually blue-sceening, as I recall.

The next level is uninstall and reinstall DUN. Depending on the patch level of your Windows, that may or may not actuallt replace your tapi.dll, although if you delete it *while* DUN is not installed, that pretty much ensures that you're getting a fresh copy.

If neither of those approaches works, follow the full-monty procedure in the MSKB articles. While you're doing that, remind yourself that Windows is popular because it's so easy to use...