Installing Ethenet card fails causing VXD tbl and loss of connectivity

Running Window 98 SE:

I have been attempting to install new D-LinkDFE 530 TX Ethernet card
which would replace my existing PCI card that has a faulty cable
connector. The old card has been working fine, no problem save for the
connector which won't hold the cable connector in place. In fact my
system has no problems save this installation thing.

Per instructions first run the installation CD, then install the card,
Windows recognizes the card and begins to install. Near the end of the
install sequence Windows says it has found a version conflict with
VIP.386 (A file being copied is older than the file currently on your
computer, which is version 4.10.2224. It is recommended that you keep the
existing file, which I do). I say use the existing file but the damage
appears to have been already done. An instant before the conflict message
appears I start to get a series of illegal operation messages that seem
to indicate that access to virtual drivers are a problem. From this point
on I can no loner communicate on the Ethernet. I then resort to restoring
my system from and image to get back to normal.

Things I have done without success:

1. Left the original card in and installed the new card in an other slot.
2. Attempted to install an usb to Ethernet adapter to circumvent
installing a PCI card.
3. Tried to locate the out of date VIP.386 file. I searched for vip.386
found two Instances. One in Windows/System and one in
Windows/Options/CABs. The vip file in CABs was 4.10.2002; the one in
System was version 4.10.2224.I changed the CABs vip file to vip.OLD and
copied the System vip file to the CABs folder. Windows still said I was
trying to replace the existing VIP.386 with an out of date one when I
attempted to install the USB to Ethernet adapter.
4. Uninstalled the old Ethernet Card in Device manager. Then installed
the new drivers and card.
5. Came up in safe mode to look for bogus network cards or duplicates -
nothing there.

In each and every case, just as the VIP.386 old version window appears, I
get the first illegal operation message (typically associated with a
start menu program) and others follow including rundll32s. At that point
I don't have connectivity either.

I initially sought help in the Windows.public.win98.setup group. Had a
good response but had no success. This problem seems to be related to a
corrupt TCP/IP data or file or installation leg or implementation
sequence. I don't know anything about how Windows goes about installing a
network card using TCP/IP internally. I'm looking for help to find the
trouble, which for now precludes installation of any network related
hardware on my computer.

TIA

Sorry if I repeat anything you may have already done, but here's what I
would do:

Remove the card, first. Then uninstall the software that came with it. Now
try to undo any file replacement and other setting that you attempted
before.

Now, download the following:
ftp://ftp.dlink.com/NIC/dfe530tx/Dri...r_10152001.exe
Extract it to some new folder created before extracting, not to TEMP (the
default). The important one is the WIN98 folder containing NETDLFET.INF.

Check out my Clean Boot article at www.grystmill.com. Set up a clean boot.
Next, boot into Safe Mode and make sure everything to do with networking is
gone in Device Manager. Restart in Normal Mode, remove *everything* in the
Network applet (Control Panel). Next, use Windows Setup in Add/Remove
Programs to remove Dial-Up Networking, restart, then reinstall DUN. (I know
it doesn't make sense, just trust me: It seems to do a good job of
rebuilding the TCP/IP stack, just for good measure.)

Now that everything is cleaned up, shut down, reinsert the card, then start
up. If prompted for the INF file, browse to the location. Otherwise, you'll
have to use Add New Hardware and the "Have Disk" method.

Good luck!

--

Gary S. Terhune
MS-MVP Shell/User

"T. Duprex" <tduprexATlandmark.net> wrote in message
news:Xns98DAE5B258087pinger@207.46.248.16...
> Running Window 98 SE:
>
> I have been attempting to install new D-LinkDFE 530 TX Ethernet card
> which would replace my existing PCI card that has a faulty cable
> connector. The old card has been working fine, no problem save for the
> connector which won't hold the cable connector in place. In fact my
> system has no problems save this installation thing.
>
> Per instructions first run the installation CD, then install the card,
> Windows recognizes the card and begins to install. Near the end of the
> install sequence Windows says it has found a version conflict with
> VIP.386 (A file being copied is older than the file currently on your
> computer, which is version 4.10.2224. It is recommended that you keep the
> existing file, which I do). I say use the existing file but the damage
> appears to have been already done. An instant before the conflict message
> appears I start to get a series of illegal operation messages that seem
> to indicate that access to virtual drivers are a problem. From this point
> on I can no loner communicate on the Ethernet. I then resort to restoring
> my system from and image to get back to normal.
>
> Things I have done without success:
>
> 1. Left the original card in and installed the new card in an other slot.
> 2. Attempted to install an usb to Ethernet adapter to circumvent
> installing a PCI card.
> 3. Tried to locate the out of date VIP.386 file. I searched for vip.386
> found two Instances. One in Windows/System and one in
> Windows/Options/CABs. The vip file in CABs was 4.10.2002; the one in
> System was version 4.10.2224.I changed the CABs vip file to vip.OLD and
> copied the System vip file to the CABs folder. Windows still said I was
> trying to replace the existing VIP.386 with an out of date one when I
> attempted to install the USB to Ethernet adapter.
> 4. Uninstalled the old Ethernet Card in Device manager. Then installed
> the new drivers and card.
> 5. Came up in safe mode to look for bogus network cards or duplicates -
> nothing there.
>
> In each and every case, just as the VIP.386 old version window appears, I
> get the first illegal operation message (typically associated with a
> start menu program) and others follow including rundll32s. At that point
> I don't have connectivity either.
>
> I initially sought help in the Windows.public.win98.setup group. Had a
> good response but had no success. This problem seems to be related to a
> corrupt TCP/IP data or file or installation leg or implementation
> sequence. I don't know anything about how Windows goes about installing a
> network card using TCP/IP internally. I'm looking for help to find the
> trouble, which for now precludes installation of any network related
> hardware on my computer.
>
> TIA
>
>
>
>

Gary,

Thanks for the response. I will do exactly as you say. First I will
thoroughly reviewing your Clean Boot procedure this morning before
proceeding. I'm on unchartered turf here and have a few questions on your
instructions that I need clarification or verification on so that I am
sure I am doing what is asked.


1."Make sure everything to do with networking is gone in Device Manager".

In Device Manager the only entries I have and would remove are under
NETWORK ADAPTERS. They are: Dial-Up Adapter and Realtek RTL8139C PCI
Fast Ethernet Adapter. Is that correct? Is there anything other
category in Device Manager that related to networking that I should
review?

2. "remove *everything* in the Network applet (Control Panel)".

I just have to confirm that you mean everything? On my system that would
be: Client for Microsoft Networks, Microsoft Family Logon, Dial up
Adapter, Realtek RTL8139C PCI Fast Ethernet Adapter, TCP/IP -> Dial-Up
Adapter, and file and printer sharing for Microsoft Networks.

3. "Use Windows Setup in Add/Remove Programs to remove Dial-Up
Networking",

In my Windows Setup Tab there is no Dial-Up Networking component. Should
there have been? Or is this something that I don't have to worry about?

4. "Then reinstall DUN"

If I didn't have DUN in the Windows Setup Tab, how do I go about
installing DUN?

5. "If prompted for the INF file, browse to the location"

Are you talking about the NETDLFET.INF file?

6. "Now that everything is cleaned up, shut down, reinsert the card, then
start up."

Instead of reinserting the old Realtek card. Should I begin installing
the new D-Link card per their standard procedure?


Really appreciate the help. Looking forward to your reply.


TD




> Sorry if I repeat anything you may have already done, but here's what
> I would do:
>
> Remove the card, first. Then uninstall the software that came with it.
> Now try to undo any file replacement and other setting that you
> attempted before.
>
> Now, download the following:
> ftp://ftp.dlink.com/NIC/dfe530tx/Dri...r_10152001.exe
> Extract it to some new folder created before extracting, not to TEMP
> (the default). The important one is the WIN98 folder containing
> NETDLFET.INF.
>
> Check out my Clean Boot article at www.grystmill.com. Set up a clean
> boot. Next, boot into Safe Mode and make sure everything to do with
> networking is gone in Device Manager. Restart in Normal Mode, remove
> *everything* in the Network applet (Control Panel). Next, use Windows
> Setup in Add/Remove Programs to remove Dial-Up Networking, restart,
> then reinstall DUN. (I know it doesn't make sense, just trust me: It
> seems to do a good job of rebuilding the TCP/IP stack, just for good
> measure.)
>
> Now that everything is cleaned up, shut down, reinsert the card, then
> start up. If prompted for the INF file, browse to the location.
> Otherwise, you'll have to use Add New Hardware and the "Have Disk"
> method.
>
> Good luck!
>

I'm an inveterate top-poster, <g>. Thanks for the numbered questions!

1. Nope. That's it.

2. Everything!

3. It's in the "Communications" section, I believe. (Don't have a 98 machine
here in front of me.)

4. You uninstall by un-checking the item, restarting, then going back,
rechecking the item and then restarting again.

5. That's the one. But be sure to get the downloaded version of the
software. Probably newer.

6. Yes, that's what I meant. Put in the new card. I'm 99% sure you'll get
prompted to install during startup. Only modems and a very few other items
tend to not get detected during startup in a 98/98SE machine.

--

Gary S. Terhune
MS-MVP Shell/User

"T. Duprex" <tduprexATlandmark.net> wrote in message
news:Xns98DB50F6488B5pinger@207.46.248.16...
> Gary,
>
> Thanks for the response. I will do exactly as you say. First I will
> thoroughly reviewing your Clean Boot procedure this morning before
> proceeding. I'm on unchartered turf here and have a few questions on your
> instructions that I need clarification or verification on so that I am
> sure I am doing what is asked.
>
>
> 1."Make sure everything to do with networking is gone in Device Manager".
>
> In Device Manager the only entries I have and would remove are under
> NETWORK ADAPTERS. They are: Dial-Up Adapter and Realtek RTL8139C PCI
> Fast Ethernet Adapter. Is that correct? Is there anything other
> category in Device Manager that related to networking that I should
> review?
>
> 2. "remove *everything* in the Network applet (Control Panel)".
>
> I just have to confirm that you mean everything? On my system that would
> be: Client for Microsoft Networks, Microsoft Family Logon, Dial up
> Adapter, Realtek RTL8139C PCI Fast Ethernet Adapter, TCP/IP -> Dial-Up
> Adapter, and file and printer sharing for Microsoft Networks.
>
> 3. "Use Windows Setup in Add/Remove Programs to remove Dial-Up
> Networking",
>
> In my Windows Setup Tab there is no Dial-Up Networking component. Should
> there have been? Or is this something that I don't have to worry about?
>
> 4. "Then reinstall DUN"
>
> If I didn't have DUN in the Windows Setup Tab, how do I go about
> installing DUN?
>
> 5. "If prompted for the INF file, browse to the location"
>
> Are you talking about the NETDLFET.INF file?
>
> 6. "Now that everything is cleaned up, shut down, reinsert the card, then
> start up."
>
> Instead of reinserting the old Realtek card. Should I begin installing
> the new D-Link card per their standard procedure?
>
>
> Really appreciate the help. Looking forward to your reply.
>
>
> TD
>
>
>
>
>> Sorry if I repeat anything you may have already done, but here's what
>> I would do:
>>
>> Remove the card, first. Then uninstall the software that came with it.
>> Now try to undo any file replacement and other setting that you
>> attempted before.
>>
>> Now, download the following:
>> ftp://ftp.dlink.com/NIC/dfe530tx/Dri...r_10152001.exe
>> Extract it to some new folder created before extracting, not to TEMP
>> (the default). The important one is the WIN98 folder containing
>> NETDLFET.INF.
>>
>> Check out my Clean Boot article at www.grystmill.com. Set up a clean
>> boot. Next, boot into Safe Mode and make sure everything to do with
>> networking is gone in Device Manager. Restart in Normal Mode, remove
>> *everything* in the Network applet (Control Panel). Next, use Windows
>> Setup in Add/Remove Programs to remove Dial-Up Networking, restart,
>> then reinstall DUN. (I know it doesn't make sense, just trust me: It
>> seems to do a good job of rebuilding the TCP/IP stack, just for good
>> measure.)
>>
>> Now that everything is cleaned up, shut down, reinsert the card, then
>> start up. If prompted for the INF file, browse to the location.
>> Otherwise, you'll have to use Add New Hardware and the "Have Disk"
>> method.
>>
>> Good luck!
>>
>

Gary:

I found DUN. Have several more questions.

>
> 3. It's in the "Communications" section, I believe. (Don't have a 98
> machine here in front of me.)
>

Yes it is, have to click "Details". Is DUN the only one I uncheck?


“Now that everything is cleaned up, shut down, reinsert the card, then
start up. If prompted for the INF file, browse to the location."

1. I'm not sure I've ever seen an installation disk/program specifically
ask for an INF file. Is this what Windows looks for on a normal
installation and gets from the installation CD?

(In this is the case I would direct Windows to the Win98 folder and it
would pick it up. Right?)

2. When I insert the new D-Link card, there will have been no drivers
installed. Just so I'm clear here, the Installation Guide accompanying the
card instructs you to run the setup cd rom (I assume installing drivers),
powering down then installing the card and powering up. Then when Windows
detects the card it completes integration of the card.

My question is; Instead of shutting down, reinserting the card, then
starting up, should I first run the installation CD, then power down
install the card, then power up?

Or does it make a difference?

"T. Duprex" <tduprexATlandmark.net> wrote in message
news:Xns98DB8AF299675pinger@207.46.248.16...
> Gary:
>
> I found DUN. Have several more questions.
>
>>
>> 3. It's in the "Communications" section, I believe. (Don't have a 98
>> machine here in front of me.)
>>
>
> Yes it is, have to click "Details". Is DUN the only one I uncheck?

Yes. Only that one, then reinstall it. I don't think it's your main problem,
but as I said, it was long ago discovered that this trick rebuilds the
TCP/IP stack properly, so we even recommend it to people who don't even have
DUN installed, only a NIC that they're having problems with. I thank Steve
Cochran, MS-MVP, for turning me onto that, actually quite recently. I've
generally kept as far from networking as I can during my MVP career, <s>.

>
> “Now that everything is cleaned up, shut down, reinsert the card, then
> start up. If prompted for the INF file, browse to the location."
>
> 1. I'm not sure I've ever seen an installation disk/program specifically
> ask for an INF file. Is this what Windows looks for on a normal
> installation and gets from the installation CD?

Yup. That's what almost all hardware uses. It's simply instructions for
which files to use, what settings, Registry entries, etc. In most cases,
there's also one or a few other files, SYS files, mostly, that need to be
put into the system, but most NICs already have everything they need in the
system. That's why I had you uninstall whatever software you installed.
99.999% of it was unnecessary crap.

> (In this is the case I would direct Windows to the Win98 folder and it
> would pick it up. Right?)

Yes, to the WIn98 folder that belongs to THAT piece of hardware.

> 2. When I insert the new D-Link card, there will have been no drivers
> installed. Just so I'm clear here, the Installation Guide accompanying the
> card instructs you to run the setup cd rom (I assume installing drivers),
> powering down then installing the card and powering up. Then when Windows
> detects the card it completes integration of the card.

Yeah, but it didn't happen that way, did it? It's like ISPs that want to
install their own special browser, which in a few cases IS necessary (like
AOHell, for instance), but in most cases is unnecessary crap. Or EarthLink
that want's you to install Total Access, when all you need to know are a few
settings, nothing more. The software that came with the NIC probably
includes some kind of monitoring junk, and also drivers for other OSes and
other files *in_case* your system doesn't already have them like it normally
should, or updated files in case you've never updated your system. In your
case, my goal is to get you back to square one and THEN if still having
problems, we can look more closely, using a back and forth dialogue.

> My question is; Instead of shutting down, reinserting the card, then
> starting up, should I first run the installation CD, then power down
> install the card, then power up?

DO NOT run the installation CD. Use the downloaded version I gave you a link
to.
ftp://ftp.dlink.com/NIC/dfe530tx/Dri...r_10152001.exe
It will by default want to unpack everything into the TEMP folder. Tell it
to put everything into a special folder that's easy for you to find. Make
the folder ahead before running the EXE, name it something like C:\DLink. It
WILL NOT automatically "Install" anything, and all you want is the Win98
folder that's inside (you can actually delete the rest of the stuff when
you're finished and we're certain we don't want to look for some other file
in that mess.) Once you know the path to that folder, when asked for the
location of the "drivers files", browse to that location. Only if it sees an
INF file will it even show you anything in the upper pane, since if you'll
look at the bottom, you'll see that it's only looking for files of type
*.inf. When you click into the Win98 folder from the downloaded, unpacked
files, the correct file will automagically appear in the upper pane.

> Or does it make a difference?

Makes all the difference in the world. Installing that software is probably
what got you into trouble in the first place.

--

Gary S. Terhune
MS-MVP Shell/User

Gary:

some progress but I've hit a snag.


Got to the point that I powered down, installed the D-link DFE-5300TX PCI
card. Powered up got past the installtion windows that said You have an old
version of VIP/386, said use the one on the system then got to the New
Hardware Wizard.

I've had no illegal operations thus far, could be because of no startup
stuff.

THE PROBLEM NOW: the New Hardware Wizard asks for new drivers, I specify
the location of the unzipped file on my desktop C:\WINDOWS\Desktop
\Driver_File which was unzipped from:
ftp://ftp.dlink.com/NIC/dfe530tx/Dri...r_10152001.exe

Windows then says it was unable to locate a driver for this device.

Also when Windows found the card it identified it generically not as D-Link
....

Your thoughts?

Gary:

I did an explore on the install CD and there are no ini files. Apparaently
there are cab files used for each operation system.

Gary

More Success, different adapter, but still not there.

At this point it seems what ever was causing the illegal operations has,
for the time being looks like its been handled.

Because Windows didn't like the D-link ini file and I couldn't locate one
one on the installation CD I brought out the new Airlink 101 Fast Ethernet
Adapter I initially bought and thought might be the problem. It had a
floppy with an ini file on it for Windows98.

I got it to install without incident. However when I try to go out on the
internet, I am not getting out for some reason. However I can communicate
on my home network (after I went to Control Panel/Network/configuration and
turned on print sharing.)

What could be keeping me from going out on the network?

Gary:

Trouble has reappeared.

I hadn't touched any of the Clean Boot setup while doing the install. I
still can't go out on the internet but can indeed communicate on my home
network. I then went to MSCONFIG and turned on "Load startup group items"
and rebooted, the machine came up in a light blue low resolution screen (I
have my backgroud that color normally). I've never seen low resolution
comeup like this before. In retrospect it was coming up normally but in
this low resolution mode. Just for kicks I did a restart, hit f8 and said
Normal, again it came up in this very low resolution screen, this wasn't
the safe mode. While in this low resolution mode I went back to MS Config
and turned off Startup. rebooted and system came up okay.

While in the low resolution mode I began getting all the illegal messages
flow that was my initial problem.

It appears something startup is screwing up any new network hardward
additions.

What would you suggest?

Is the inablity to go out on the network a trouble or a setting issue?