I have this problem on a PIII 450. I heard to try opening regedit and deleting the reference to ndis2sup.vxd. I'm going to try it, but I don't have much confidence in this fix. I will check the microsoft page and see if that helps! Thanks everyone!

0

I am having exactly the same problem with ndsi2sup.vxd. This comes from my Ethernet-card ! As a solution I defined a second hardwareprofile and there disabled my network-card. After this all is fine ! But this will only work, if I'm using my computer with no link to ohter workstations.

0

same problem here too, causes my sys to randomly reboot right before the desktop displays. blue

0

The above mentioned Knowledge BAse articale does explain the problem. I have it also, I do not however, think microsoft should have had those drivers just say. LoadFailed. Maybe Loaddecidednotto. Anyways, You should leave the references to these files in your registry. They are there for a reason.

0

First I would like to tell you, I am french, so excuse me about mistakes I could do. It exists a shareware : RegRepair2000 on the site http://www.easydesksoftware.com/down.htm which allows to avoid these error messages. Filou

0

Found this on web page http://support.microsoft.com/support/kb/articles/Q127/9/70.asp Load Failures Listed in the Bootlog.txt File -------------------------------------------------------------------------------- The information in this article applies to: Microsoft Windows 95 Microsoft Windows 98 -------------------------------------------------------------------------------- SYMPTOMS When you review the Bootlog.txt file in the root folder on your hard disk, you may see the following lines even though your computer seems to function properly: LoadFailed = dsound.vxd LoadFailed = ebios LoadFailed = ndis2sup.vxd LoadFailed = vpowerd LoadFailed = vserver.vxd LoadFailed = vshare InitCompleteFailed = SDVXD NOTE: The following lines may appear only in the Windows 98 Bootlog.txt file: Deviceinitfailed = MTRR SysCritInitFailed = JAVASUP DeviceInitFailed = MTRR CAUSE These load failures do not necessarily mean that there is a problem. It is common for some, if not all, of these to fail, depending on your system configuration. DSOUND Many sound drivers are DirectSound enabled. DirectSound is part of Microsoft DirectX, a set of libraries used by most newer Windows-based games. When a DirectSound-enabled sound driver is loaded, it attempts to register with the DirectSound library so that games can use it. If no DirectX-based games are installed on your computer, the DirectSound library fails to load. This is normal. EBIOS The extended BIOS driver did not find an extended BIOS, so it does not load. Ndis2sup.vxd The NDIS 2 support driver did not find any NDIS 2 drivers to support, so it does not load. VPOWERD The Advanced Power Management (APM) driver determined that your computer does not support APM, so it does not load, or APM support may be disabled. To determine if you have inadvertently disabled APM in Device Manager, follow these steps: In Control Panel, double-click System. Click the Device Manager tab. Double-click the System Devices branch to expand it. Double-click the Advanced Power Management Support branch. (If this branch does not exist, your computer does not support APM.) Click the Settings tab. Verify that the Enable Power Management Support check box is selected. Vserver.vxd Vserver.vxd does not load statically so that it can save memory by loading later in the boot process only if it is needed. For example, Vserver.vxd might not be needed when you start a laptop computer while it is out of its docking station. VSHARE If you examine the Bootlog.txt file, you will notice that VSHARE loaded successfully earlier in the boot process. The second copy of VSHARE detects that VSHARE is already loaded and does not load. Font Failures After the first boot of Windows 95/98, the Bootlog.txt file may list many font load failures. This is a normal occurrence. When Font Manager searches the hard disk for fonts, it may find them in several folders. After it finds them, it records the information so that future attempts to locate a font proceed more quickly. InitCompleteFailed=SDVXD Windows 95/98 automatically loads a miniature disk cache to increase the speed of the boot process. When the boot process is complete, the miniature disk cache is unloaded from memory. When it is unloaded, the above line is added to the Bootlog.txt file to indicate that the miniature disk cache has been removed from memory. This is normal behavior. SysCritInitFailed=JAVASUP The Java Support driver is not needed on your computer, so it did not load. Java is a programming language used on the World Wide Web (WWW). Microsoft Internet Explorer versions 3.0 and later include a Java subsystem. DeviceInitFailed=MTRR Memory Type Range Registers (MTRR) is a .vxd file responsible for manipulating memory ranges. This file is loaded with DirectX 5.0, however, none of the DirectX core components use the service provided by MTRR. Also, NTKERN and some display drivers do use the service provided by MTRR to change memory ranges. Additional query words: loadfail Keywords : kbtool win95 Version : 95 Platform : WINDOWS Issue type : kbprb

0

Long pause at boot is the problem i was having; would stall for about a minute at a dos screen before continuing to load 98se. After reading some of this i suspected ndis2sup.vxd, thing is... i looked at a couple other computers & found the same message in the bootlog. after further troubleshooting i found that moving my 3c905 nic to the 4th pci slot cleared the problem up. i don't know why it does this but apparently, the abit be6 doesn't like the card in the 1st or 2nd pci slot. the card does function in those slots, it just has the side effect of the long pause at boot. hope this helps somebody. marty

0

Thanks Marty, I think you may have something here. I have an Abit BX6v2 and also have a long delay at startup with a blinking cursor in upper left of my screen - takes about a minute! Now that you mention it, I do believe that it occurred after I moved my nic to another slot. I'll give this a try and re-post my results. Thanks again

0

I am experiencing a similar problem, complicated by the fact that my netwok device is integrated into my motherboard. I get a blinking cursor at the bottom of my screen, then a blank screen & nothing. I am forced to reboot, in safe-mode, at which point I can do very little. I'm running an AM-K6 2/450 on a Super Socket-7 mb, Pt# M585LMR, by PCChips. Any thoughts?

0

Too bad. Moving the network card did nothing to help the prob, not even REmoving it! Help please!

0

There's a freeware tool called "Bootlog Analyzer" which you can use to analyze your bootup process and identify where the delays and failures are occurring: Download at: http://216.150.70.100/files/Bla.zip - or - http://www.dentalaw.com/freestuff/bla.zip Just make sure that before you run it, you reboot your system and from the Windows Startup Menu, choose option 2: Logged (\bootlog.txt) so windows builds a current bootlog, otherwise you'll be looking at outdated bootup information.

0

PC having difficulty during bootup; i.e., locks up at various bootup phases. Have to shut off power and reboot several times. Examined my bootlog--indicated ndis2sup.vxd, MTRR, and naapi.vxd failed to load. Errors suggested "file not found". Any ideas? Would simply trying to locate these files and install such help? MS tech support was a joke . . . no help at all.

0

MICROSOFT STINKS! Man I am pulling my hair out over this dumb problem. It lags my machine way tooo long. I hate this. If anyone finds a solution, it would be much appreciated. Linux RULES!

0

Dan said that if it's a failure loading ndis2sup.vxd then it's 'cause the NDIS 2 support driver did't find any NDIS 2 drivers to support, so it does not load. But how do I make it find a NDIS 2 driver? I know that it's there!

0

Come on!Don't Panic!It is only a shit.The answer is simple.Microsoft sucks!I bought Win 98 SE and seems that MS fixed the problem.Try it out!

0

Sorry I have Win98SE (pos2) and it is not fixed. I also don't have an Abit mobo. I have a HP pavilion 6545c (ASUS?) and it HANGS during bootup. http://marketwizz.net/windows95/win95a/index.html

0

In network properties make sure you have a address for tcp/ip if not it will hang at start.

0

I do believe that this problem comes from Win98 seeing the network card incorrectly. I suggest removing the drivers installed for the network card, and also making sure that all references to the network card are out of the network properties in control panel. Reboot the system, then go into control panel, add new hardware, do not let 98 detect the hardware. Put in the CD with the drivers for the card, and make sure to select the directory with the win98 drivers not the win95 drivers. Then, the most important step is to wait a bit. If you are not careful, you might mistakingly click on a previous window. Hopefully that should do it. I know it definitely will for that all in one board the 585lmr, because that is one of the boards that it most frequently happens on. If you do not have a 98 driver for the NIC, use a modem to go online, and pick one up from the maker of the card.

0

had the same problem, what helps (comes from candu): In network properties make sure you have a address for tcp/ip if not it will hang at start.

0

I would like to know every thing about cache memory. And what is the lastest knowledge in cache?

0

We just bought a Micron 500 Pentium III about 4 months ago. It took 3min and 20sec for Windows 98 to load. It hung at the windows screen and the next screen where the cursor sits and blinks in the upper right hand corner. I came looking for an answer because no way should it take that long for it to come up. After going into network properties and putting a fake address in, it now only takes 2 min for windows to load. It does not hang at all you can here the hardrive working all the time. Thank you for the answer.

0

Putting in an IP address is the fix. Don't have to use the network card, just have to have an address inserted. Thanks

0

I found this discussion through a search engine for "ndis2sup" as I was also having trouble as described in this forum. I was surprised that all the files mentioned were coming up as errors also in my bootlog. I used "confirmation mode" during startup and loaded everything but ndis2sup.vxd. The startup went fine this time, but my E drive was now F, and the E drive was ?. I concluded that an installation program may have corrupted the vxd file. I used a program called extract.exe along with a customized batch file to extract a new copy of ndis2sub.vxd. (It is embedded in the Net9.cab file and should be in your Windows\Options\Cabs folder) I think you may also be able to use Winzip to extract this file. I copied the newly extracted file into the Windows\System folder (where the original file resided) and that seemed to do the trick. I get a straight-up load with no more freezeups. (so far!) I'm sorry I don't remember where I got the extract.exe program from (I think from the Microsoft site) but I would be happy to send the extract.exe and customized batch file to anyone who requests it. (email me if you need it)

0

After reinstalling Win98, I noticed my system hung for 25 seconds before loading. Reading this site, I fixed the problem by supplying an IP address in the Network control panel. Also deleted and reinstalled the drivers just to be sure. My boot time is now back down to about 10-15 seconds.

0

My computer has the same demons in it. contacted microsoft, oh my, never again. i would get more sasy-faction sticking my head in a burlap sack filled with wet kittens. but anyway there is also other *.vxd errors. i run asus k7v w/600mhz amd slot athlon processor, stb velocity128, asound express sound. will keep ya'll posted on results of trying to exercise these demons. any prayers are greatly appriciated. i'm thinking taoism may be the answer....

0

For Win98: Add and remove your TCP/IP stack!!! Negation/Synthesis: (C.f. Response No 24 & 26 in this dialogue)-- One shouldn't have to hard code a static IP in any normal home-user circumstance. (Note: TCP/IP Stack = all the component protocols in your Network Control Pannel on the Configuration page which begin with TCP/IP...P.S. => You may have trouble restoring the correct settings once you have removed the protocols if you do not have a disk from your ISP which would reconfigure these settings in the correct fashion, and/or a record of your previous settings for each protocol component). Case Info: I was getting memory errors on boot roughly 10 Seconds AFTER the Client for Microsoft Networks logon appeared. The ndis2sup.vxd failure report occurred repeatedly in bootlog.txt, as well as a vxd error. So, I removed the static IP under the generic/base dial-up adapter's TCP/IP properties (how did it get there, anyway!!?), in order to reverse-test Candu's hypothesis (response No. 24), and sure enough, he was right: I hung on boot--except in safe mode. This should not happen, as using DHCP is a basic function of Windows (most ISPs and/or LANs want us to use DHCP, or the "obtain an IP address automatically" option...it is beneficial). I then removed my TCP/IP stack, and reinstalled my ISP. I am now 1) able to boot and connect normally, and 2) not forced to use a static IP. Sad fact is, TCP/IP stacks become corrupt sometimes. Anyway, Kudos to Candu for his/her research.

0

did any of you check to see if ipx/spx was loaded in you network stack? try removing it, rebooting, and then adding it back in. you shouldn't have to assign an IP to the NIC b/c of this error. If you're using windows 98, and you setup your nic to use dhcp, windows assigns a random IP to the device anyway.

0

That's it! The ndis2sup.vxd problem has beaten me to a pulp. I've tried everything suggested on this forum (except the "Bootlog analyzer" @ response # 18, nor removing the drivers for the NIC, nor deleting the registry entry for this driver) and nothing has worked. I have a netgear FA310TX card behind a Linksys BEFSR41 DSL router. Using TCP/IP and DHCP. Any other ideas?

0