If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
#11
|
|||
|
|||
Install new Ethernet Card causes VXD, and TCP/IP problems
With this trouble condition in I just noticed that in device manager under
network adapters, there are no TCP/IP entries. Install obviously is not completing and explains why I can't get on the network once I attempt to install the new card. |
#12
|
|||
|
|||
Install new Ethernet Card causes VXD, and TCP/IP problems
Download and run
ftp://ftp.dlink.com/NIC/dfe530tx+/Dr...river_5397.exe It contains "diag.exe", which is a DOS setup and diagnostic program. Put the card in the computer, remove all other unnecessary peripherals and start the computer. Tap the F8 key repeatedly during bootup and select "Command Prompt", then type the full path and file name to the program, for example: c:\windows\temp\diag\diag.exe Ben "T. Duprex" tduprexATlandmark.net wrote in message ... Running Windows98 SE. Attempting to install a new D-LinkDFE 530TX fast Ethernet card. I need to replace my old card because of a broken connector. The old card (unknown brand) works fine (just doesn't hold Ethernet plug in place, doesn't click in). The D-Link is the second brand of new card I've tried. I returned the first card because I thought that somehow either the PCI card or drivers might be the problem. The cards or install CDs are not the problem. There is something going on and I'm hoping you can help me out. Here is what happens: I install the drivers as per the instructions which warn not to install the PCI card until the drivers are loaded. Using the provided CD I install the drivers and as instructed I select "No, I will restart my computer later". . I then shut down and install the new card. When I turn on the computer Windows finds the new card, finds the driver and proceeds in time until it 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). At the same moment in time this is going on I start to get a series of messages that seem to indicate that virtual drivers are screwed up and I can no loner communicate on the Ethernet. For example I get a Message that my LogitecDeskManager has performed and illegal operation which is followed by several more Start up apps generating illegal operation messages. I attempt to use Outlook Express and Internet Explorer but cannot connect to the network. They want to report problems as does Firefox which says that an illegal operation has been performed and will shut down. I've tried removing the old card in Device manager, but in the process of removing, it too then creates the above scenario. I also tried installing the DFE 530 then doing the install CD, no change. In each case the only way I can get my system back is to do an image restore on my entire system (takes about 8 minutes). Then, I power off, reinstall the old card turn the system on and everything is fine, except for the faulty mechanical connector. I'd welcome suggestions as to what might be wrong, and how to resolve the problem. TIA |
#13
|
|||
|
|||
Install new Ethernet Card causes VXD, and TCP/IP problems
If I do have a more current version of VIP.386 already installed, where is Windows finding, or thinking I have an older version? Could this be a hint of where the problem is? snip try deleting vip.386 (to the recycle bin) then try installing your net card |
#14
|
|||
|
|||
Install new Ethernet Card causes VXD, and TCP/IP problems
"T. Duprex" tduprexATlandmark.net wrote in message
... snip Looking ahead, IF that works, do I just then unplug the old Ethernet card, go to safe mode and remove it (both the entries) from Device Manager? Doing a remove from normal boot caused the problem also. No! Once the new card is installed and working, you need to configure it as your network connection using the networking wizard. This associates the various protocols with the card and creates the actual connation between the OS and the network. Then you can unplug the old card and remove its drivers. -- Jeff Richards MS MVP (Windows - Shell/User) |
#15
|
|||
|
|||
Install new Ethernet Card causes VXD, and TCP/IP problems
Can you run this machine when you are not connected to the network? That
is, if you boot with the cable unplugged, does the machine then operate OK, and does the uninstall for the existing card change at all? Based on your description, it seems as if the machine is depending on the network connection in order to continue operating. -- Jeff Richards MS MVP (Windows - Shell/User) "T. Duprex" tduprexATlandmark.net wrote in message ... "Jeff Richards" wrote in : I do not have a spare PCI slot. I had thought about removing a modem card which I don't use, but I don't know if that would compound the issue. Can I just plug in the new card in place of the Modem card after loading the drivers? Or do I have to somehow uninstall/remove the modem? Failed Again: After installing the new D-Link Ethernet drivers, powered down removed modem card installed Ethernet card powered up. Windows found the new card and proceeded to install it. And at the moment it displays the message about finding that the VIP.386 file to be installed is older than the one on my computer I get that first "illegal operation" message. I then powered down, and removed the old Ethernet card. Powered up but the damage has apparently already been done. Same manifestation of messages and conditions. I then went to Control Panel/Network and removed the old Ethernet card. Rebooted, no change. If I do have a more current version of VIP.386 already installed, where is Windows finding, or thinking I have an older version? Could this be a hint of where the problem is? |
#16
|
|||
|
|||
Install new Ethernet Card causes VXD, and TCP/IP problems
My next move is to install the new Ethernet card drivers, power down, remove the modem card and insert the new Ethernet card. NO luck replacing modem card, same trouble. Additional test information: In order to circumvent the installation of a PCI card, I installed a USB to 10/100Mbps Fast Ethernet Adapter. Installation went fine until again Windows displayed that 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). At that point I got the first illegal operation message and I'm back in the same boat. It appears that at the instant the Older file message appears I get the trouble. It also appears that until I get at the root of this trouble I will not be able to install any alternative means to replace that defective connector. Restored an image of my computer then 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. I plugged in the USB to Ethernet adapter, WINDOWS recognized it and proceeded to install driver. AGAIN, all went well until Windows stated the VIP.386 being installed was older than what was on the computer. Do I want to keep the later version. As soon as I hit yes, I had the onset of illegal operation, Rundll failed etc. So either installation of a PCI card or USB adapter is the triggering the TCP/IP problems. Where is Windows finding the older vip.386 file? Registry? I could use a suggestion or two on how to isolate this problem. TYI Any idea where Windows is finding the old version of VIP.386 |
#17
|
|||
|
|||
Install new Ethernet Card causes VXD, and TCP/IP problems
"Jeff Richards" wrote in
: Can you run this machine when you are not connected to the network? YES. There are days at a stretch that I run "unplugged" because the connector is faulty. That is, if you boot with the cable unplugged, does the machine then operate OK. Yes and does the uninstall for the existing card change at all? No, the uninstall still causes the trouble condition. Based on your description, it seems as if the machine is depending on the network connection in order to continue operating. Until I attempted to change out the Ethernet card I didn't know I had a problem. As for the faulty connector, I would have to jury rig something to hold the cable in place, so at times I know I wasn't connected. It appears that in the installation of a network piece of hardware that involves TCP/IP something goes wrong when association of that hardware with TCP/IP drivers or something changes an address or something, takes wrong turn and starts misdirecting apps looking for VXDs, or the network. Again, I'd like to know where Windows is hiding the vip.386 old version that keeps cropping up. Could this be the key to the fault? I'm reluctant to change the network protocol on this machine to see if that goes around the problem. I'm not that proficient dabbling in that area. With the implementation/association of TCP/IP protocol I'm now thinking this problem should be shifted to Windows98.networking group. It is not hardware or driver related. |
#18
|
|||
|
|||
Install new Ethernet Card causes VXD, and TCP/IP problems
On Fri, 16 Feb 2007 14:02:09 -0800, "T. Duprex"
tduprexATlandmark.net put finger to keyboard and composed: Running Windows98 SE. Attempting to install a new D-LinkDFE 530TX fast Ethernet card. I need to replace my old card because of a broken connector. The old card (unknown brand) works fine (just doesn’t hold Ethernet plug in place, doesn't click in). The D-Link is the second brand of new card I've tried. I returned the first card because I thought that somehow either the PCI card or drivers might be the problem. The cards or install CDs are not the problem. There is something going on and I'm hoping you can help me out. Here is what happens: I install the drivers as per the instructions which warn not to install the PCI card until the drivers are loaded. MSWIN98.TXT tells you to do the opposite: Introduction: ------------- This document describes the procedure to install Windows 98 driver for D-Link DFE-530TX+ PCI Adapter. Location of Driver: \WIN98\DLKRTS.SYS Installing driver procedure on Microsoft Windows 98 : ----------------------------------------------------- Before you start with the installation process, make sure that your adapter should be properly installed in your PCI bus slot. Executing Windows 98, it will auto-detect your system configuration and find the adapter hardware. Using the provided CD I install the drivers and as instructed I select "No, I will restart my computer later". . I then shut down and install the new card. When I turn on the computer Windows finds the new card, finds the driver and proceeds in time until it 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. I have a Realtek RTL8139 chipped NIC. FWIW, my version of VIP.386 is 4.10.2226. It is recommended that you keep the existing file, which I do). At the same moment in time this is going on I start to get a series of messages that seem to indicate that virtual drivers are screwed up and I can no loner communicate on the Ethernet. For example I get a Message that my LogitecDeskManager has performed and illegal operation which is followed by several more Start up apps generating illegal operation messages. I attempt to use Outlook Express and Internet Explorer but cannot connect to the network. They want to report problems as does Firefox which says that an illegal operation has been performed and will shut down. I've tried removing the old card in Device manager, but in the process of removing, it too then creates the above scenario. I also tried installing the DFE 530 then doing the install CD, no change. In each case the only way I can get my system back is to do an image restore on my entire system (takes about 8 minutes). Then, I power off, reinstall the old card turn the system on and everything is fine, except for the faulty mechanical connector. I'd welcome suggestions as to what might be wrong, and how to resolve the problem. The easiest fix may be to have someone replace the broken connector. That would amount to about 15 mins worth of labour for any competent tech. Old NICs are basically free, so you should be able to get a replacement connector for nothing. TIA Does your original NIC use the same Realtek chip? - Franc Zabkar -- Please remove one 'i' from my address when replying by email. |
|
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Problems with standard Belkin network card and Win98 1st edition machine | Laphan | General | 0 | December 4th 05 09:58 PM |
Problems with standard Belkin network card and Win98 1st edition machine | Laphan | Setup & Installation | 0 | December 4th 05 09:58 PM |
Problems with standard Belkin network card and Win98 1st edition machine | Laphan | Networking | 0 | December 4th 05 09:58 PM |
Missing TCP/IP Protocol-Install USB to Ethernet Adapter | gramsay | Networking | 4 | December 3rd 05 06:43 PM |
View a logfile for TCP/IP ethernet | dk_ | Networking | 4 | November 1st 05 06:36 PM |