Installing Ethenet card fails causing VXD tbl and loss of connectivity

"T. Duprex" tduprexATlandmark.net wrote in message
...
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

When you unzipped teh file into \Driver_File\, there should be another
folder inside that one called WIN98. THat is where the INF file is located.
You say something later about an INI file. That's not an INF file.


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?

Have you tried sharing a folder? Share one, at least, on each computer, then
see if you can find them in Network Neighborhood. If you can see files on
the network, but not get out on the problem machine, and you can get out on
the other computer(s), then I'd suspect that your router's not set up
properly. You should be using DHCP, which assigns internal addresses
automatically.

If you're not using a router, but only using a switch after the DSL/Cable
modem, then that may be the problem. What does the rest of your network look
like, starting at the connection that comes in, DSL or Cable? Describe each
piece of hardware.

--

Gary S. Terhune
MS-MVP Shell/User

"T. Duprex" tduprexATlandmark.net wrote in message
...
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?

Have you tried sharing a folder? Share one, at least, on each computer, then
see if you can find them in Network Neighborhood. If you can see files on
the network, but not get out on the problem machine, and you can get out on
the other computer(s), then I'd suspect that your router's not set up
properly. You should be using DHCP, which assigns internal addresses
automatically.

If you're not using a router, but only using a switch after the DSL/Cable
modem, then that may be the problem. What does the rest of your network look
like, starting at the connection that comes in, DSL or Cable? Describe each
piece of hardware.

--

Gary S. Terhune
MS-MVP Shell/User

"T. Duprex" tduprexATlandmark.net wrote in message
...
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?

Did you try raising the resolution to normal mode in Display Properties? If
that's not possible, then you have a problem app in your Startup queue. The
way to diagnose is to only enable half of the Startup Group, then restart.
If the problem returns, then you know it;s something in the half that you
enabled. If no return of problem, then it's in the half that's still
disabled. (Try switching the halves just to see if it's in the Startup Group
at all. Might be in Config.sys or Autoexec.bat.)

Assuming you the problem is in the Startup Group, based upon that knowledge
(keep lists!), re-enable all but half of the problem half. Again, if the
problem returns, you know it's in the quarter of the list that you just
re-enabled, or vice versa, in quarter that you left disabled (not part of
the half that was originally discounted as not containing the problem.)
Continue halving the list according to the above rules until you've located
the one item (or there may be more than one) that when enabled causes the
video problem, but when disabled causes the problem to disappear. You *can*
do this one by one, but the halving method is faster. I suspect something
that was installed by the danged D-Link software.

--

Gary S. Terhune
MS-MVP Shell/User

"T. Duprex" tduprexATlandmark.net wrote in message
...
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?

Did you try raising the resolution to normal mode in Display Properties? If
that's not possible, then you have a problem app in your Startup queue. The
way to diagnose is to only enable half of the Startup Group, then restart.
If the problem returns, then you know it;s something in the half that you
enabled. If no return of problem, then it's in the half that's still
disabled. (Try switching the halves just to see if it's in the Startup Group
at all. Might be in Config.sys or Autoexec.bat.)

Assuming you the problem is in the Startup Group, based upon that knowledge
(keep lists!), re-enable all but half of the problem half. Again, if the
problem returns, you know it's in the quarter of the list that you just
re-enabled, or vice versa, in quarter that you left disabled (not part of
the half that was originally discounted as not containing the problem.)
Continue halving the list according to the above rules until you've located
the one item (or there may be more than one) that when enabled causes the
video problem, but when disabled causes the problem to disappear. You *can*
do this one by one, but the halving method is faster. I suspect something
that was installed by the danged D-Link software.

--

Gary S. Terhune
MS-MVP Shell/User

"T. Duprex" tduprexATlandmark.net wrote in message
...
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?

"Gary S. Terhune" wrote in
:

Have you tried sharing a folder? Share one, at least, on each
computer, then see if you can find them in Network Neighborhood. If
you can see files on the network, but not get out on the problem
machine, and you can get out on the other computer(s), then I'd
suspect that your router's not set up properly. You should be using
DHCP, which assigns internal addresses automatically.

Yes I can share folders back and forth. I have tested this rigorously.


Network: cable modem to Linksys WRT54GL router. Both this Windows 98
computer and WindowsXP laptop cable directly to router. Three other
computers, Macbook, another Windows98 and another WindowsXP plus a prinrter
server are wireless.

Router is set up for DHCP: as I sit here now only two computers and the
print server are on line the machine we are working on , known as TOWER,
has an IP of 192.168.1.101 the wired XP laptop also on line is
192.168.1.100. The print server, wireless is on 192.168.1.205. I printed
from both a wired and wireless machine. I had two of the wireless machines
on line before and they shared with no problem. All the other machines can
go out on the internet.

"Gary S. Terhune" wrote in
:

Have you tried sharing a folder? Share one, at least, on each
computer, then see if you can find them in Network Neighborhood. If
you can see files on the network, but not get out on the problem
machine, and you can get out on the other computer(s), then I'd
suspect that your router's not set up properly. You should be using
DHCP, which assigns internal addresses automatically.

Yes I can share folders back and forth. I have tested this rigorously.


Network: cable modem to Linksys WRT54GL router. Both this Windows 98
computer and WindowsXP laptop cable directly to router. Three other
computers, Macbook, another Windows98 and another WindowsXP plus a prinrter
server are wireless.

Router is set up for DHCP: as I sit here now only two computers and the
print server are on line the machine we are working on , known as TOWER,
has an IP of 192.168.1.101 the wired XP laptop also on line is
192.168.1.100. The print server, wireless is on 192.168.1.205. I printed
from both a wired and wireless machine. I had two of the wireless machines
on line before and they shared with no problem. All the other machines can
go out on the internet.

I pointed to the Win98 folder which contained a README.TXT file and the
NETDLFET.INF file. I mis-spoke about the INI file, I was looking on the
installation CD to see if they had the INF file. If it was accessable I
would have tried it to eliminate a corrupter file.


When you unzipped teh file into \Driver_File\, there should be another
folder inside that one called WIN98. THat is where the INF file is
located. You say something later about an INI file. That's not an INF
file.

I pointed to the Win98 folder which contained a README.TXT file and the
NETDLFET.INF file. I mis-spoke about the INI file, I was looking on the
installation CD to see if they had the INF file. If it was accessable I
would have tried it to eliminate a corrupter file.


When you unzipped teh file into \Driver_File\, there should be another
folder inside that one called WIN98. THat is where the INF file is
located. You say something later about an INI file. That's not an INF
file.

Sorry, at this point, I'm not able to continue until I've had some rest. I'm
dealing with some insomnia, and my brain is on strike. I'll post back
tomorrow , latest (I'm on Pacific Time).

--

Gary S. Terhune
MS-MVP Shell/User

"T. Duprex" tduprexATlandmark.net wrote in message
...
I pointed to the Win98 folder which contained a README.TXT file and the
NETDLFET.INF file. I mis-spoke about the INI file, I was looking on the
installation CD to see if they had the INF file. If it was accessable I
would have tried it to eliminate a corrupter file.


When you unzipped teh file into \Driver_File\, there should be another
folder inside that one called WIN98. THat is where the INF file is
located. You say something later about an INI file. That's not an INF
file.