Always an Unpleasant Sight...

[Kov-Ice]

While I have to see it often enough when dealing with one of my Win98 systems, this morning was the first time ever that XP gave me the ol' BSOD. It was a little unsettling because of that fact.

I clicked to dial out and walked away. When I came back, the BSOD was up with slnthal.sys listed as the culprit. Checked www.fileproperties.com to find it's a Soft Modem file by Smart Link.

I just installed a new Diamond SupraMax modem. Is this a case of needing an updated driver? Can that cause such a reaction?

[Statica]

Check this solution out: http://forums.scotsnewsletter.com/in...showtopic=9841

[EzyStvy]

Should have seen my BSOD this morning on my main office pc.

Registry Failure
The registry cannot load the hive file
It is corrupt, adsent or not writeable.....

Good old last known setup worked..

[Kov-Ice]

Thanks for the link, Statica. In it, they refer to the modem not playing nice with SP2. I've yet to install the free M$ SP2 disc I ordered and received. Is it time I did that?

I guess best bet would be to remove all Smart Link files as described, install SP2, then re-install modem. Correct?

[glc]

I'd personally get rid of your software modems and put a real hardware modem in it if you depend on dialup for your Internet access. It's just too easy for modem software to corrupt or be incompatible with something - and hardware modems use simple .inf file drivers, not a whole bunch of sys and vxd files.

http://www.newegg.com/app/ViewProduc...104-119&depa=0

http://www.newegg.com/app/ViewProduc...104-131&depa=0

The 5610B is a better bet for XP, but the 2976 works fine with the Win2K .inf file.

[Kov-Ice]

I've always wanted to get a USR modem, but I wound up with this thing through a gift card, a coupon, and a sale. I guess my next purchase will wind up being a hardware modem, but until then would you agree with my previous post? Remove all modem files, install SP2 (been too wary to do this), then re-install modem? Thx!