imported_Kiwi
Golden Member
Following a severe software crash, I ended up wiping the boot drive partition and starting over with a fresh reinstall of Win98se. Until I get this much running clean, I haven't yet done the reinstall of W2K on its own partition for dual boot capability. One thing I did while trying to trouble-shoot the system was to remove a generic modem and replace it with a USR modem that is supposed to be a real one, with all modem processing performed on that board, not via software.
I still don't have the sound card back in its slot, but I had to pull it out before either modem, old or new, could be properly installed (SB Live 5.1). Eventually, I got the Internet going, downloaded the most recent security updates to Win98 (beyond those on the Security CD of a year ago), and started wondering why I couldn't get the LAN working. Eventually, the NIC's install would work, but not in the first PCI slot I tried it in.
The upshot of the LAN's reluctance to connect was its need for a named IP for the NIC; this entry, however, conflicts with the ISP, and as long as there is a number, my connection is a DEAD one. No working communication there. I did try to remove the IP number, but it didn't seem to affect the dumbing-down of the Inet connection, even if it did kill the LAN.
There are three computers on the LAN, and the Laptop never has been set up for the Internet. Previously, the PC I'm having trouble with was my primary eMail and www-surf vehicle; I'd like to get back to that. I use WT-Net, in Houston, and their setup didn't always require a blank IP in the TCP/IP settings. At some point last fall, they changed over to use another backbone service, and I had to edit one or both of the desktop PC's that are on the LAN.
I made the IP configuration "automatic" then, and the LAN was *unaffected*. Seemingly, there is more than one place for the LAN to pick up the IP it needs, and some way to edit things to have both Internet and Local Net. I can't manage to hold on long enough to reach WT-Net's techs; with the new backbone, they are offering more services, and expanding things, but without adding more techs.
:brokenheart:
I still don't have the sound card back in its slot, but I had to pull it out before either modem, old or new, could be properly installed (SB Live 5.1). Eventually, I got the Internet going, downloaded the most recent security updates to Win98 (beyond those on the Security CD of a year ago), and started wondering why I couldn't get the LAN working. Eventually, the NIC's install would work, but not in the first PCI slot I tried it in.
The upshot of the LAN's reluctance to connect was its need for a named IP for the NIC; this entry, however, conflicts with the ISP, and as long as there is a number, my connection is a DEAD one. No working communication there. I did try to remove the IP number, but it didn't seem to affect the dumbing-down of the Inet connection, even if it did kill the LAN.
There are three computers on the LAN, and the Laptop never has been set up for the Internet. Previously, the PC I'm having trouble with was my primary eMail and www-surf vehicle; I'd like to get back to that. I use WT-Net, in Houston, and their setup didn't always require a blank IP in the TCP/IP settings. At some point last fall, they changed over to use another backbone service, and I had to edit one or both of the desktop PC's that are on the LAN.
I made the IP configuration "automatic" then, and the LAN was *unaffected*. Seemingly, there is more than one place for the LAN to pick up the IP it needs, and some way to edit things to have both Internet and Local Net. I can't manage to hold on long enough to reach WT-Net's techs; with the new backbone, they are offering more services, and expanding things, but without adding more techs.
:brokenheart: