General discussion

Locked

TCP/IP causes lockup under Windows 98SE

By cuttinge ·
I have a AMD K6-2 200 computer (32 Mb RAM, 3 Gb HDD with 2 Gb free, no modem, no sound, 1 Intel 10/100 NIC) that I upgraded from Win95 to 98 by reinstalling 98 over 95 (same subdirectory). It sits on a Windows 98 peer-to-peer network and worked just fine under 95 using TCP/IP, but I wanted some of the features of 98. Everything seems to work fine now except networking. I need to run TCP/IP (for internet sharing) but when I do the computer will not see the rest of the LAN, (sees itself) and will hang either when not used for at least a couple of hours or when trying to exit Windows. I get a msgsvr32 and/or rundll error when I try CTRL-ALT-DEL or (usually) the "Windows is now shutting down" screen freezes.

I have rounded up the usual suspects: regclean, remove all networking, including the NIC and reinstalling, tried different NICs, scandisc, msconfig, disable virus scan and running "fdisk /mbr"; checked the Cat 5 cables, hub, disabled any and all power management in both Windows and the BIOS, updated to the latest BIOS, and installed the latest video/NIC drivers. No change.

I would like to think that I could actually delete all files relating to networking and reinstalling them (rather than just "remove" in the networking properties) but I don't know what files need to be removed. Any other suggestions?

All help would be greatly appreciated as reformatting the drive would be quite painful at this point, as would reinstalling Windows in a new subdirectory.

Thanks.

This conversation is currently closed to new comments.

10 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

TCP/IP causes lockup under Windows 98SE

by donhuffman In reply to TCP/IP causes lockup unde ...

DHCP? Static IPs? File and Printer Sharing on? Check the bindings to make sure TCP/IP is bound to the NIC in question..I,m on 98SE on a laptop and connect with no problem wherever I go.(What ever system I'm on)

Collapse -

TCP/IP causes lockup under Windows 98SE

by cuttinge In reply to TCP/IP causes lockup unde ...

No DHCP, static IPs, share files, the NIC is the only device to bind to as no dialup services are installed (no modem).

Collapse -

TCP/IP causes lockup under Windows 98SE

by grantcom In reply to TCP/IP causes lockup unde ...

I recall seeing some info on problems with the Intel NIC drivers..if you loaded the most recent they are probably ok. I would uninstall all unnecessary protocols and manually set the NIC to the proper speed..i.e 10 half duplex or 100 half duplex. Also make certain you have the latest Win98 Service Pack installed. Is the NIC a PCI card or ISA? Have you checked for conflicts. Sound cards and Nic's don't get along well even in PCI. I have resolved similar problems by (1.) Not putting the NIC in PCI slot 1 (2.) force a free IRQ in BIOS preferably 9 or 11 if possible. Hope this helps.

Collapse -

TCP/IP causes lockup under Windows 98SE

by cuttinge In reply to TCP/IP causes lockup unde ...

I too have seen some problems with the Intel NICs, particularly in conjunction with Diamond MM video cards, but this system uses the S3 video, besides I have changed to Realtek 8139 NICs without any change. If I remove all NICs and setup Dialup networking with TCP/IP and a dynamic IP the system will shut down normally, but since there is no modem I cannot test the actual use of TCP/IP. I am using PCI NICs only, and can see no conflicts in device manager. The NICs have always been mounted in either Slot 2 or 3 with the video card mounted in 1, 2 or 3.

I will double check for the latest service pack from Bill.

Thanks for your suggestions.

Ken

Collapse -

TCP/IP causes lockup under Windows 98SE

by cuttinge In reply to TCP/IP causes lockup unde ...

I too have seen some problems with the Intel NICs, particularly in conjunction with Diamond MM video cards, but this system uses the S3 video, besides I have changed to Realtek 8139 NICs without any change. If I remove all NICs and setup Dialup networking with TCP/IP and a dynamic IP the system will shut down normally, but since there is no modem I cannot test the actual use of TCP/IP. I am using PCI NICs only, and can see no conflicts in device manager. The NICs have always been mounted in either Slot 2 or 3 with the video card mounted in 1, 2 or 3.

I will double check for the latest service pack from Bill.

Thanks for your suggestions.

Ken

Collapse -

TCP/IP causes lockup under Windows 98SE

by grantcom In reply to TCP/IP causes lockup unde ...

Sounds like you are on the right track. Before giving up or pulling my hair out I would try running the Diagnostic program that comes with the NIC. This is run from dos and therefore removes Windows and driver problems out of the loop. Run Host on one machine and Client on the other. If the diagnostics prove ok then it narrows it to a Windows configuration problem in all likelihood. BTW I suggest a Netgear TX card, inexpensive but a good card and Windows seems to like them.

Collapse -

TCP/IP causes lockup under Windows 98SE

by cuttinge In reply to TCP/IP causes lockup unde ...

Thanks for the suggestions: I have tried the Intel Diagnostic and, yes, it does point to a Windows problem, but I have still not located it. I'll look at the Netgear TX card, do you know what chipset it uses? I have tried Kingston and Realtek, both with the Realtek 8139 chip with varied sucess.

Collapse -

TCP/IP causes lockup under Windows 98SE

by grantcom In reply to TCP/IP causes lockup unde ...

Ok..lets have another go at it. I would go to Networking and remove the Adapter. Do a restart and enter BIOS. If the option is available tell BIOS it is "not" a PnP OS. Then go to PCI config and try to force the NIC to IRQ 9 or 11. Reboot into Safe Mode and click on each plus sign by each and every device and remove those that have duplicates. When I encounter duplicates I delete all the entries as Windows will set them back up on boot up. Now reboot to windows and reinstall the NIC drivers when prompted to do so. Be sure you provide the proper OS CD when prompted...do not let it load from the hard drive cab files if you have any. Make certain you use the proper OS CD (the one you used to load 9

Collapse -

TCP/IP causes lockup under Windows 98SE

by cuttinge In reply to TCP/IP causes lockup unde ...

Grant,

Ithink this is the right track. I've done this before, but was not agressive enough in removing the old driver files. I changed brands of cards and then, after making sure the BIOS was set to Manual, purposely picked the wrong card fromthe list supplied on the driver diskette. This forced a rewrite of the drivers. Reboot. Pick the correct driver. Rewrite. Reboot. Run RegClean (TWICE!!). It works.

I think the combination of rewriting the NIC drivers and running RegCleanhas solved the problem. I have learned that you MUST run RegClean TWICE, once right after the other in order for it to be effective.

Thanks,

Ken

Collapse -

TCP/IP causes lockup under Windows 98SE

by cuttinge In reply to TCP/IP causes lockup unde ...

This question was closed by the author

Back to Desktop Forum
10 total posts (Page 1 of 1)  

Related Discussions

Related Forums