Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Dream Machine ( Build your own PC ) -- Ignore unavailable to you. Want to Upgrade?

To: Sean W. Smith who wrote (6301)	2/15/1999 10:38:00 AM
From: Spots	Respond to of 14778

>>If your familar with NDIS configuration files look at the protocol.ini file. Yeah, some. I used to have to fiddle with them to hand config some old tcp/ip stacks on wfw 3.11 and dos. I hoped I had forgotten them. I always had to work through it painfully. Pings of everything died with unreachable, including myself. Close enough to your guess to make me believe you're right. In the end I did what you said more or less by accident, though it is part of a general methodology (remove and restore bits, that is). What I'm really interested in is what caused it in the first place. The only serious difference would be mac id. I had just not 5 minutes before booted the disk on a virtually identically configured machine with absolutely zero problem. Diffs were 256mb memory and scsi card vs 128mb mem and no scsi card. And, of course, different NIC but identical type. Scsi driver failed as expected. Network bye-bye as not expected. Matter of fact I forgot to reinstall SP4 after fixing this. So far no problem, though I know well enough to do it in general. Boot loader said SP4 which I noted in passing as unusual, then I forgot about it. I better go reinstall it; somethings going to break sooner or later I expect.