this may also help
http://support.microsoft.c
Main Topics
Browse All TopicsI've just changed motherboard, processor, and SCSI card. On boot up to windows (Windows 98, original
version), I get a windows protection error, which windows reports resulted from windows attempt to initialize
"device NDIS". Using MSconfig, and choosing not to load NDIS.vxd, the system boots up. However, that
results in no dial-up networking and no ability to connect with the internet through my modem. I even
formatted an extra hard drive that I had and did a clean install of Windows 98, and I got the same error
message. My config. and the parts that were replaced are as follows:
P4 2.2 ghz Northwood processor (replaced a P3 800MHZ)
Abit TH7 II Intel 850 motherboard (replaced Abit BE6 II)
512 MB Rambus RDRAM (replaced 256k SDRAM)
Adaptec 29160N SCSI Adapter (replaced a 2940UW)
Seagate Cheetah 9.1 GB hard drive
Quantum Atlus 10K II 36 GB hard drive
GeForce 3 video adapter
2 Plextor SCSI CDROM drives
SCSI internal zip drive
3Com 56k external modem
There is no sound card installed yet.
Any help would be appreciated.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
this may also help
http://support.microsoft.c
Thanks for the suggestions. I have already uninstalled all networking components and re-installed them a couple times, both on the original hard drive and on the clean install of Win 98. I cannot find evidence of a resource conflict. When I choose not to load the NDIS.vxd, and boot to normal windows, the Device manager reveals no conflicts. If I have instructed the computer not to load NDIS, would the computer be able to report a conflict involving NDIS?
I believe that NDIS is responsible for loading the Dial-Up Adapter drivers and probably more; I saw a reference to NDIS in conjunction with the Dial-Up Adapter in the Device manager. So I changed the extensions of those drivers temporarily so they couldn't load. I still got the same error on bootup. I don't know of a way to determine what other files are loaded by NDIS. Knowing that might help. Also, I tried to do a logged startup so I could review bootlog.txt on restart from the command prompt. But, on restart from the prompt, I didn't see bootlog.txt in the root directory where I understand it's supposed to be. I tried that several times with no success.
I'm increasing the points on this question to 200.
this may help
http://support.microsoft.c
but I think this is it
from M$
Windows Protection Error in NDIS with a CPU That Is Faster Than 2.1 GHz (Q312108)
http://support.microsoft.c
Steven, thanks for locating that article. It says it was posted on Dec. 27, 2001, but a few days ago I did a search of Microsoft articles with NDIS in the title or text, and while that revealed a few articles, this one wasn't among them. Apparently, I need MS support to send me the file. I'll let you know if that fixes the problem, but it looks to be right on point. ( I wish I could have the 20 or so hours back that I've spent troubleshooting drivers, installing and uninstalling hardware, and losing hair the last 10 days.) Thanks again for responding.
Steven, last night I scored...desktop! The fix was written for my problem, and I think I even see a few shafts of new hair coming through this morning. (Of course, it took 90 minutes on the phone convincing 4 different MS techs that I shouldn't have to pursue the original OEM from 4 years ago to try to get the patch from MS for me or to pay MS $35 for it, but they finally e-mailed it.) For my own peace of mind, I searched the MS knowledge base again to see why I didn't discover this article several days ago. It took 3 searches to retrieve it. Lesson learned about the quirkiness of their search system and the need for persistence when you have a problem that might implicate a windows file. For your ingenuity and persistence in weaving your way through the search-engine morass over at Bill's place, you definitely get all the points. Thanks again. Laurie
Hey Laurie, i am having same problem aswell :( stupid M$ are wanting to charge me for a fix i shouldnt have to pay for. Was wondering, if u could by any chance lighten me in wat this fix is ? maybe i can come up with a solution rather than sheding out the bills they ask for , the fix. thanks.
-Stephan
Business Accounts
Answer for Membership
by: stevenlewisPosted on 2002-02-11 at 12:22:09ID: 6794971
try unistall8ing and reinstalling dialup networking theu the add/remove progerams, windows setup
also go to network in the control panel, remove all networking components, beboot and reinstall