|
Home > Archive > alt.certification.a-plus > January 2004 > Tech DOH! Win 98 SE keeps reinstalling the same NIC
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Tech DOH! Win 98 SE keeps reinstalling the same NIC
|
|
|
| Anyone had this problem? Windows will not stop seeing the NIC card as
a new one no matter how many times it has been installed.....
The NIC is an SMC 1244TX. LATEST drivers. Network is a one segment
five computers on a little Netgear autosensing 10/100 switch. Computer
is a white box Celeron A 333 with a SIS chipset.
MB is a cheapo combo AT-ATX board that a lot of the white box makers
were using when ATX was first coming in. A real cheapo - doesn't have
a mouse port or a dongle for a mouse port. Two ISA, four PCI slots,
one shared. It's set up as an AT.
Win 98 SE in a new, but not clean, installation. Installed it over
the old cause it had a gatekeeping (literally- it monitors use of
smart cards to enter a building) program from Checkpoint that I wanted
to look at, but didn;t have the install files.
First tried a Netgear ISA NIC that had been working well for years.
Wouldn't work in any slot or any, including real mode, configuration.
Put in the SMC following the recommended method - install driver first
(actually, just installs the inf file).
Worked.
Did some settings, rebooted.
Windows found a new PCI nic card. Cancelled. Working NIC no longer
worked. Rebooted. Windows found a new NiC card. Let it install it.
Worked. Settings. Reboot.
Now there were two NICs with the same MAC address. Wouldn't work.
Got rid of em. Reinstalled, rebooted, settings, rebooted, Windows
found yet another new NIC .
I let it go till it installed three of them. Then removed them all,
removed all protocols, searched the registry for references to the
NIC - all gone, unless it installs hidden ones (doubt it) and deleted
the two driver .bin files windows maintains to keep track of PnP
drivers. Searched the hard drive for .pol files. None. Took out the
nic. Rebooted. Re installed.
Worked. Copied some files over the network. Turned it off and went
away. Came back later and turned it on. SCREAMING CURSING
9&^%*%*%*%*. Windows found a new NIC and proceeded to put me on the
same merry go round.
MSfts suggestion is to delete the .bin files and re install. If no
joy, contact mfgr. Mfgr's suggestion is to try the second method of
installation, which is to install the card before installing the
drivers and let windows find it and step thru the wizard. Other
suggstion is that TCP/IP is corrupted, remove and reinstall protocol.
Tried all, no joy. )
Any suggestions?
Thanks!
Mike
| |
| Adam Leinss 2003-12-06, 9:23 pm |
| "MF" < wallacestevens54@removethisfir
styahoo.com> wrote in
news:q7mdncOxDdm-0k-iRVn-sQ@comcast.com:
> Anyone had this problem? Windows will not stop seeing the NIC
> card as a new one no matter how many times it has been
> installed.....
Good old Plug and Pray! Try toggling the "Plug 'n Play OS" option in
your BIOS. If it's set On, the BIOS will control setting up Plug and
Play devices; if it's set Off, Windows will control setting up Plug and
Play devices.
In terms of the ISA NIC not working: I think most of those are
configured in DOS. You download a specific program for your NIC and
configure it in DOS. You have to be very careful about what IRQ you
give it. Copy down the settings you pick, do a "Add New Hardware" in
Windows and match up the resources after it finds the device.
Adam
| |
|
|
"MF" < wallacestevens54@removethisfir
styahoo.com> wrote in message
news:q7mdncOxDdm-0k-iRVn-sQ@comcast.com...
> Anyone had this problem? Windows will not stop seeing the NIC card as
> a new one no matter how many times it has been installed.....
>
<snipped>
> Now there were two NICs with the same MAC address. Wouldn't work.
> Got rid of em. Reinstalled, rebooted, settings, rebooted, Windows
> found yet another new NIC .
I've had similar problems with hardware in the past. Did you try just
letting it install twice and then disabling one of them in the Device
Manager? I don't know why this works but sometimes it does.
| |
|
| Thanks! but keep thinking - responses in line......
"Adam Leinss" <aleinss@toughguy.net> wrote in message
news:Xns9449C79F258D0aleinssto
ughguynet@toughguy.net...
> "MF" < wallacestevens54@removethisfir
styahoo.com> wrote in
> news:q7mdncOxDdm-0k-iRVn-sQ@comcast.com:
>
>
> Good old Plug and Pray! Try toggling the "Plug 'n Play OS" option
in
> your BIOS. If it's set On, the BIOS will control setting up Plug
and
> Play devices; if it's set Off, Windows will control setting up Plug
and
> Play devices.
Tried it but forgot to mention it. No effect.
> In terms of the ISA NIC not working: I think most of those are
> configured in DOS. You download a specific program for your NIC and
> configure it in DOS. You have to be very careful about what IRQ you
> give it. Copy down the settings you pick, do a "Add New Hardware"
in
> Windows and match up the resources after it finds the device.
>
> Adam
The ISA NIC was ISA PnP. PCI/ISA systems have a connecting bridge, as
you know, that allows PCI IRQ steering to work on the ISA device if
the device is built for it. It usually works in 98 - in my
experience of about 250 win 98 installs, its PnP is pretty good, as
opposed to 95,s which was sort of 50-50 hit or miss.
This is wearing me out. I just went to install NT workstation on the
computer - forgetting that I hadn't converted the first (win98)
partion to FAT. tech DOH, indeed. I also ran Aida and Sandra Pro on
it and they showed no problems, except, of course, when they tried to
connect to the network.
I'm starting to suspect a problem in the PCI bus. Will find out when
a couple other OSs are installed.
Thanks again and post if you think of anything else/
Mike
| |
|
|
"JBS" <noone@thisdontwork.net> wrote in message
news:VDvAb.1900$Ho3.755@newsread1.news.atl.earthlink.net...
>
> "MF" < wallacestevens54@removethisfir
styahoo.com> wrote in message
> news:q7mdncOxDdm-0k-iRVn-sQ@comcast.com...
card as[color=blue]
> <snipped>
>
>
> I've had similar problems with hardware in the past. Did you try
just
> letting it install twice and then disabling one of them in the
Device
> Manager? I don't know why this works but sometimes it does.
>
Thanks for replying!
I have sometimes had the same good results by removing the second
one in device manager. Which I tried here, to no effect. Will try
disabling one....
Mike
| |
| Gordon Findlay 2003-12-07, 4:24 am |
| On Sat, 6 Dec 2003 16:50:40 -0500, "MF"
< wallacestevens54@removethisfir
styahoo.com> wrote:
>Anyone had this problem? Windows will not stop seeing the NIC card as
>a new one no matter how many times it has been installed.....
>
>The NIC is an SMC 1244TX. LATEST drivers.
Saw this once with a set of 25 3Com cards - not absolutely sure of the
number 3c509 I think. Did get one machine up to 11 cards installed
(none functioning) as a test.
NEVER found the reason. Did find, with the vendor, that replacing
- rev c of the card with rev d
- windows 98 with any other OS
made the problem go away. The vendor replaced all the cards, since
neither he nor 3com had any idea of what was happenng.
Bonne chance
Gordon
| |
|
|
"Gordon Findlay" <gordonf@xtra.co.nz> wrote in message
news:chq5tv0v4pf3t7fmmpiej7cbl
rrv13mc3e@4ax.com...
> On Sat, 6 Dec 2003 16:50:40 -0500, "MF"
> < wallacestevens54@removethisfir
styahoo.com> wrote:
>
as[color=blue]
>
> Saw this once with a set of 25 3Com cards - not absolutely sure of
the
> number 3c509 I think. Did get one machine up to 11 cards installed
> (none functioning) as a test.
>
> NEVER found the reason. Did find, with the vendor, that replacing
>
> - rev c of the card with rev d
> - windows 98 with any other OS
>
> made the problem go away. The vendor replaced all the cards, since
> neither he nor 3com had any idea of what was happenng.
>
> Bonne chance
> Gordon
That's funny; bonne chance is right. The same thing happened to me
with the same 3Com cards. Same C revision. I had ten computers; six
of them had the 3Com cards in 'em. They were for a class that would
start with A+ and then go thru half of the MCSE track and the 3Coms
were in the computers because they are PXE enabled and were to
facilitate the demos of RIS installation from W2K server. Well, the
class started with Win98 and you couldn't even demo the existence of
the network with those cards and Win 98. After fiddling and fiddling
with them, I announced to the class that they had just learned that
some things won't work with some things, period, and have to be
replaced.
So wouldn't you know, one guy announced "Well, MINE works."
He had sat there and installed it fifteen times, and it finally
started working. He couldn't think of anything he had done
differently. The rest never worked. We replaced them with C-Net Pro
200's, that famous card, which worked fine, then put them back in for
the Win2K part of the class. Win 2K had drivers for them and
installed them in the blink of an eye.
Mike
| |
| Jinkies 2003-12-08, 6:24 am |
| In article <mJidnVxmr5ruNE-iRVn-uA@comcast.com>,
wallacestevens54@remove
thisfirstyahoo.com says...
>
>This is wearing me out.
The computer and nic are worthless and you're wearing yourself out dicking
around with them. Something is wrong with this picture.
| |
|
| "Jinkies" <Jinkies@yahoo.com> wrote in message
news:neYAb.24993$d35.16043@edtnps84...
> In article <mJidnVxmr5ruNE-iRVn-uA@comcast.com>,
> wallacestevens54@remove
thisfirstyahoo.com says...
>
> The computer and nic are worthless and you're wearing yourself out
dicking
> around with them. Something is wrong with this picture.
I thought about this four or five days ago. Some people spend a lot
of time re-potting plants, doing crossword puzzles, or making
unhelpful posts to newsgroups
Have any other ideas?
| |
| Jinkies 2003-12-10, 10:24 pm |
| In article <mJidnVxmr5ruNE-iRVn-uA@comcast.com>,
wallacestevens54@remove
thisfirstyahoo.com says...
>
>This is wearing me out.
The computer and nic are worthless and you're wearing yourself out dicking
around with them. Something is wrong with this picture.
| |
| ganjamandog 2004-01-20, 10:24 pm |
| Feel free to ignore. Hadn't read the whole listing.
I just read your posting and thought I would stick in my tuppence
worth.
Were all the PCI slots in use when you tried the nic? Did you leave
the shared slot free? Have you tried closing all applications and
checking system information utility in system tools? Have you the
latest 98 se updates as you stated that they were the latest drivers?
Have you tried rolling back the driver or installing older drivers?
Have you tried the microsoft site to troubleshoot to see if there are
any known conflicts? Did the driver come with a setup program which
could be maintaining the previous settings? Are you trying to use the
same IRQ settings? The old nic will have used DMA bypassing the cpu
and using real mode drivers or is likely conflicting with another
device like a modem so these settings would have to be different. Do
you have a modem present? Is it using the same IRQ? Sorry if none of
this helps.
Graeme.[color=darkred:f37f54c1ad][/color:f37f54c1ad]
==============
For this group's frequently asked questions, check out www.CertFAQ.com
|
|
|
|
|