Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1110
  • Last Modified:

Win98 SE - can't load TCPIP???

Has anyone had trouble loading TCPIP for Win98 SE?

It seems to load just fine until I go to reboot it.  Then I get 0E followed by a 0D error.  At this point, I need to shut it down hard, usually, though occasionally I can ctrl-alt-del it (twice - won't "shut down").

Upon booting, I get a stacks overflow problem, until I go to safe mode and remove TCPIP.

Knowing that 0E and 0D errors can often be caused by faulty memory, I swapped memory chips around, but the errors stayed at the same addresses, suggesting it's not hardware related - unless something's wrong with the CPU, which, if it were, would be wreaking all sorts of havoc, not just with TCPIP.

I'm stumped.  Big points for the right answer!

Bill
0
billko
Asked:
billko
  • 7
  • 4
  • 3
  • +8
1 Solution
 
kurinaCommented:
I have seen a similar problem with IBM net adapter. The solution was as the following:

1. Remove the LAN adapter from ControlPanel / Device Manager

2. Shut Down the computer and take the LAN adapter out from the slot.

3. Power on the computer asnd check that everything is OK.

5. Shut Down the computer, swith it off and put the LAN adapter into the slot.

6. Have a manufacturers driver disk ready.

7. Power on the computer - DO NOT LET WINDOWS install the default driver - use the driver from the manufacturers disk.

Is that OK?

Regards
0
 
PCGuruCommented:
Billko, more info pls, network card type, and model(if being used), what exactly are doing to *load* tcp/ip? Win98SE is usually a breeze with networking but I do need as much info as you can supply to be able to help. Actually, the main reason you are installing tcp/ip as well, I'm not pointing fingers saying you need it because you sound like you know what your about, I just want to know, ie, is it newly going onto either a network or the internet. Just to get a mental picture so to speak.

Cheers,
Guru
0
 
billkoAuthor Commented:
Sorry, here's more info:

The reason why I am installing it in the first place was because upon installing Win98 SE, it bombed the same way the manual TCPIP install did.

Installing it with only a dial up adapter didn't work, nor did installing it only with the NIC (Linksys Etherfast 10/100).  Installing it in safe mode avoided the shutdown errors, but still produced the stacks overflow.  (I think the stacks overflow is caused by a corrupt TCPIP install, but I added "stacks=64,512" just to make sure.)

I used two different procedures to install TCPIP.  The first was through Networking Properties, where I added the protocol and let Win98 SE load it from CD.  When that method did not work, I tried installing it in safe mode, which produced the results listed above.  When that failed, I tried loading it through AT&T Startup, which I'm sure just does the same thing as me manually installing TCPIP.

I don't think the CD is damaged - I copied the whole win98 directory locally (my "Safe Mode" doesn't have a CD), and didn't get any complaints.

I actually bought this copy of Win98 SE, so I don't see a problem with possible duplication errors.

<Sigh>

Bill
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
billkoAuthor Commented:
Oh, oops...

I just need it for dial-up internet connection, but may upgrade it using a router and a DSL connection (for easy sharing with multi-platform computers).

Bill
0
 
PCGuruCommented:
have you installed "Dialup Networking" ? I can't think of any reason why "Add protocol - TCP/IP" would fail.

Cheers,
Guru
0
 
Ginger_EdCommented:
what are the errors you are getting?

Ed
0
 
scottemCommented:
You can type- SFC -in the file run box under start menu. This will system file checker, don't know if you have used it before or not, but it will scan files and check for corrupted ones, then prompt for location to get new files from and you have to point to install files for win98. You can write down names of any corrupted files found, this might help you track down problem. The other thing I would try is to remove everything from communications, take check mark out and say okay, then reboot and reinstall what you need. You can try it with original win98 if you have one, instead of second edition. It could be that the part of the registry on networking/Tcp-ip was corrupted from original install of win98 SE
0
 
jjcontactCommented:

Replace the E100bnt.sys with the Version of this File on Windows 98 (Not Windows 98 Second Edition

http://support.microsoft.com/support/kb/articles/Q244/8/70.ASP?LN=EN-US&SD=gn&FR=0


One possible difference between SE and regular Windows98.
0
 
PCGuruCommented:
>>>JJ, "billko" wrote -

*********************

 "Oh, oops...
 I just need it for *dial-up internet connection*, but may upgrade it using a router and a DSL connection (for easy sharing with multi-platform computers).

                      Bill

*********************

Am I jumping the gun this time? 8-)
Anyway, you've got the right idea, see you round the traps, this guru is of to meditate in dreamland.

Cheers,
Guru
0
 
oldgreyguyCommented:
0
 
sorgieCommented:
These type of stack overflows are usually related to device drivers not the stack line in config.sys

Also check your sys.ini file in the [386]Enh section. Add thhis line
MinSPs=12

See what happens. This fix suggestion is from MS
0
 
Asta CuCommented:
Should your DSL setup not include the PPPoE Protocol as well under Network Adapters?  I recall having problems With W98 and W98SE after my DSL was installed and sharing same IRQs as sound card, moving card as suggested, uninstalling all.  It was the order of things done that finally resolved; and required updated installation disk and CD from my DSL / ISP provider.  I'd say check also via SAFE MODE to ensure no resource conflicts or duplicates are listed in Device Manager for any component(s).


Asta
0
 
PCGuruCommented:
Billko, remove the NIC from device manage and remove it physically from the system after shutdown. Boot into safe mode and double check, make sure *all* network related software/hardware are removed from device manager and network properties. Reboot normally and then re-install MS Windows client, Dial up networking and finally TCP/IP. It is possible the unidentified "stack overflow and the failure of TCP/IP are caused by a hardware fault or conflict somewhere, my guess would be something to do with the network card. You should find that TCP/IP will install correctly now. At this point - if all is indeed well - reboot and go to BIOS. Go to PCI PNP Setup or equivalent (depending on BIOS type and revision) and manually set the IRQ for the PCI slot that the NIC will occupy to 10(if you have this option) leave all other settings on auto or where you already have them. Continue to boot as normal. If successful go to Device Manager and check for *any* hardware conflicts. If none and TCP/IP is okay (all is dependent on this of course) then shut down the system and fully and restart. Try to finish setting up for dialup networking with your ISP details etc, if this too is successful ie, can connect to ISP, browse internet, etc, shut down PC once more, cold, ie, usual stuff, power off etc. Now reinstall the NIC in the slot you chose for IRQ 10 and reboot, if the error comes back at this point (provided everything else is successful) you will have found your problem,ie, faulty hardware, if not you will also have found your problem, IRQ conflict. Either way if all this pans out you will be set to sail. We can always work on the next NIC if it does prove faulty.

All the best with this,
Guru
0
 
jjcontactCommented:
I don't know Guru. I am still screwed up with my modem over the changes Microsoft made between Windows98 and Windows98 SE.  Neither 3Com or Microsoft will change, so 3Com thinks I should get rid of Windows98 SE. Trouble is my Windows98 copy was a beta which just expired. I know how to get around this of course, but I have learned to like Internet Connection Sharing. The upshot is the equipment that was designed when Windows98 was the standard, may not work with Windows98 SE. This is the first time I have seen the suggestion that you extract the file from the other disk though.
0
 
scottemCommented:
They are the same files just possibly different versions of some, simply remove all your communication protocols etc. Then reinstall, when prompted for disk insert Windows 98 1st edition and see what happens.
0
 
scottemCommented:
They are the same files just possibly different versions of some, simply remove all your communication protocols etc. Then reinstall, when prompted for disk insert Windows 98 1st edition and see what happens.
0
 
PCGuruCommented:
>>>JJ, you still have a problem?? Where is the question?? How many points offered? 8-)

But seriously, I've noticed some of my recent posts have confused *me* a bit as to why I haven't finished my comments properly and have to had to do second posts, I think I may have to take a break from the exchange for a while to give the grey matter a chance to recover. Have you visited the question from the guy that wants to run 4 sound cards, that's really got my brain churning.

Cheers.
0
 
Patricia Siu-Lai HoCommented:
billko, Try to re-inspect the installation of your NIC.
(1) BIOS settings for modem/(wake-on lan) in the power management page - PME
(2) Plug and Play OS in the BIOS. Disable it before installation of your NIC (both prior to plug in the NIC into the PCI slot and setup drivers in win98)
(3) Inspect if you have installed the NIC in PCI slot 1 (first nearest to the CPU) or in PCI slot with sharing (last slot shared with ISA bus).  Remove the NIC and install it into PCI slot 2 or slot 3.
(4) Remove the adapter from PCI slot 1 or shared slot (last PCI/ISA shared bus).  
      Boot into the Win98,
      Remove all devices of NIC in device manager and dialup networking and protocols.
      Shut down the PC with power off.
     
      Insert the adapter to PCI slot 2 or slot 3.

      Follow the win98 setup method of following URLs
      http://www.linksys.com/support/solution/LNE100TX.HTM#driverupdate

      with downloading most update drivers, if necessary.
     
      In win98se, install all protocols for NetBEUI, IPX/SPX, TCP/IP for compatibility of older 16bit ODI or NDIS and TCP/IP 16-stack drivers.

      Then remove away the NetBEUI, IPX/SPX protocols and left the TCP/IP there.

See if it works or not.
0
 
billkoAuthor Commented:
Hi, there!

I didn't abandon this thread!  Quite frankly, I didn't expect this swarm of responses, and I've been busy acting upon them.  I thank all who answered, because all solutions seemed quite reasonable.  Unfortunately, they didn't solve my problem... BUT...

They DID point me in the right direction.  Everyone who said, "unload all protocols and stuff," were on the right track.  I neglected to mention that I had the Win95 Novell client on there, too.  Maybe this is too old for Win98/SE because they have a new client dated 04-26-2000.

Anyways, I reloaded Win98/SE, and TCP/IP loaded right up.  As soon as I added the Novell client, guess what...

I'm gonna try loading up the new client and see what happens.  This is odd because the combo worked fine under Win95.

I'll keep you guys posted.  If this does seem to be the fix, I'll figure out some way to divvy up the points for you guys.

Bill
0
 
Asta CuCommented:
Once I placed the NIC card into the one and only dedicated (unshared) pci slot, all was smooth-sailing.  Hopefully you can have the same good results and can use a dedicated slot.

Asta
0
 
billkoAuthor Commented:
I changed this to 250 because I'll accept a comment here as an answer, and make a new question for the other guy who helped out.

I truly appreciate everyone's efforts on my behalf, but felt that these people's answers helped me the most.
0
 
PCGuruCommented:
Bilko, well, I see you've learned the importance of posting all "relevant" info with your question :-) Hey, don't worry too much, I was on a thread not long ago where we had to ask 3-4 times for *all* relevant info cause what what the person was asking and what they were giving didn't quite match up. Anyway, I'm sure I'm not the only one here who would probably say "Jeez!! Now he's got Novell Client 32 for Win 95 in there".(oh well) A lot of us work with these combo's on a daily basis, so I'm glad we could all be of help.

Cheers,
Guru
0
 
PCGuruCommented:
Oh, a word of warning, Client 32 v3.2 has a security bug, opt for Client 32 V3.1 SP! or SP2 in preference. Sorry, I only found this out today and I'd almost forgotten it.

Cheers again,
Guru
0
 
ianBCommented:
Community Support has reduced points from 500 to 0
0
 
ianBCommented:
Hi,

Since billko has already awarded points to the experts for this question, I am refunding the points and moving this question to the "closed list".

Ian
Community Support @ Experts Exchange
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 7
  • 4
  • 3
  • +8
Tackle projects and never again get stuck behind a technical roadblock.
Join Now