Georgie informened me that his fix is not intended for this type of problem. Below is where I am at with my problem. Where are you with yours?
I am wondering what config have you been using, no need for everyone to invent their own wheel. Lets find out what works and what doesn't and why.
What is your OS?
What is your NIC device?
Has it been working good for you?
If you had a problem what did you do to fix it?
Here are posting from another thread:
Georgie or anyone else,
Thanks for the time you put into the USB fix. I am sorry but it is not working for me. First of all I had to search for where to get this "PCI.EXE" program and at first I downloaded this 1.3MB file and tired it. Then I relised it was the wrong one. I found out that I could get it here (correct me if I am wrong):
Next I "assumed" that I was to put the command in the autoexec.bat file and stays there for every boot.
I have a USB network adapter that you can get at bestbuy, you know the really tiny one (USB100M) found here:
Now here is the funny thing. I was not able to get it to work at all on one of my IO systems (call it IO1). So a friend tried it on his and it worked and still works today. I am running 98lite from Win98SE and he is running full Win98SE, maybe that is it. Anywho, it Works great for him. So I tried it on my second system (IO2), 98lite again, and it worked great. I downlaoded 5GBs of MP3s over that night that I installed the OS and had no problems, so grabbed an image of it. I even tried it just now out in the car and it GREAT, I was even surfin via internet connection sharing.
I put that image from IO2 on IO1 (was not working right) and it WORKED! ... until the next day. It is funny because it is intermitten, those are a B*@#H. I just tired it again and it work but then eventually it quits. So I saw your patch and tried it and it dose nothing. Now I cannot get it to work again, it still doesn't work. :(
Any ideas? What could I have done to it?
I am sorry for the lack of the "how to" paragraph. It is updated and hopefully complete now. On another note, that your USB NIC worked on your IO prior to my USB fix means that you use TCP/IP as your network protocol. TCP/IP has built-in error correction. Try NetBEUI and you will understand, that this USB fix works. Most probably your LAN will be twice as fast with NetBEUI and the fix than with TCP/IP and without the fix. It sounds to me that your problem of not being able to use your USB NIC on one of your IOs is not related to this fix, or not directly. What differences are there between the two IOs in terms of hardware?
Looks like you have your hands full, I hope you knew what you were getting into. Again thanks for all your time.
I don't think it is a network problem but I could be wrong. I will try installing NetBEUI tonight. Otherwise my other IO2 still works great and IO1 still works every so often.
What I do see happen is that the LEDs on the adapter are off. It seems like the USB driver gets locked up. The LEDs are on for a moment during boot of windows then they turn off. Windows also will not shut down when the adapter is not working. Sometimes when the adapter is plugged in Windows wont even boot, it locks at the splash screen.
As for hardware differences there is only one, the other IO has two MAX205 chips to convert the RS232 signals on both comm ports. Otherwise everything else is the same, even the same HD part number. This includes:
-Heat sink mod
-IDE cable (badflash.com)
-Modem cards have been removed
-disabled Sandisk (cut two traces on the board)
-32mb ram (using seperate partition HD for swap file)
-the OS install was made from the same image
-BIOS Version (badflash.com)
Any other ideas would be apreciated. What could I have different in the BIOS settings to cause this?
Kind of off subject in the BIOS, why does the BIOS still need an ESC key in order to exit one submenu and go back to the main menu?
I tried installing NetBEUI and no difference. If anyone has any other ideas I am willing to try them.
Hotrod_nut any others reading this thread.....This latest USB fix from Georgie, so far as I understand, does only one thing: It corrects USB transfer problems over various LAN devices, and corrects outward USB transfers to disk drives, cdrws, etc.
It does not correct device driver problems, configuration problems, OS compatability problems, and other VIA MVP4 chipset problems ....which there are many. I have tried many different USB devices on my three different I-Openers, and on a Compaq computer of mine which has the same MVP4 chipset as the I-Opener. Many different USB problems show up for me. The worst, I guess, and it happens with both computers, is the chipset occasionally losing a device which previously worked ok. You boot up..the device is gone. Maybe it shows up in device manager as an "unknown" device, maybe not. Sometimes it will start working if you reload the driver, sometimes not. Other problems....sometimes either the I-Opener or the Compaq will not boot if an externally powered USB device is attached and powered up. This happens with several USB hubs I have. Sometimes the computers will not shutdown properly if this USB device is attached. I have a Cannon scanner...not externally powered....My compaq will not shutdown if this device is attached. In short, VIA chipsets, not only MVP4s, have all sorts of USB problems. Georgie's latest fix will not cure every USB/I-Opener problem you may have. I suspect the only way to fix some of these problems is to trash the offending device, try a different piece of hardware.
Georgie pulled off a great patch for I-Opener USB problems......but it will not fix every USB problem. By the way, if you can, try Windows XP. It completely fixed my USB problems with my Compaq, and my I-Opener.....so far anyway.
For USB help from VIA try here.......
You misunderstood what I wrote about NetBEUI. I just wanted to point out that you have been using TCP/IP as your network protocol, which is why you have actually never experienced the USB-out data corruption problem. TCP/IP has built-in error-correction, if a corrupted data packet arrives it will be retransmitted. Therefore, you never experience data corruption on TCP/IP, but all the retransmissions degrade network speed. NetBEUI has no error correction, thus it is perfect to demonstrate that the USB fix works: almost all your files will be corrupted without the fix. I just wanted to say that the fix does work and does what it is supposed to. It is your decision which protocol you use for your LAN.
On another note, if you write about the green LEDs, it is a serious problem. Yes, your driver seems to have communication problems to your hardware (NIC)? Have you tried it with another NIC? The one that is known to work on the other IO?
Yes, there may be a difference in the CMOS settings affecting your USB NIC. Make sure you have the exact same CMOS settings on the two IOs. One way to do it is with Charles Dye's cmos.com.
Just a question: have you updated your uhcd.sys driver? You can read about it again in my post in the techref area.
I see how I misunderstood your NetBEUI thing. I was thinking this was a good spot to discuss USB issues. Maybe someone else might have ran into the same issue and maybe found it to be a corrupt file that I would have to delete and reinstall or so on. I can see that I should make a new thread and not crowd Georgies Fix. Yes, I did update my uhcd.sys as instructed on your install notes. I will try compairing CMOS settings.
What NIC are you using?