There is some experience in using USB under NT4. This page accumulates all related info published in News before. Also, new knowledge shall be published here.

• update IONetworks 4.10
  must be installed over 4.06. Is extracted by KtP from
  Edgeport/Rapidport Drivers for Windows NT 4.0 Release 3.60
• IONetworks 4.06
  supports USB 2.0.
• IONetworks 4.04
  
• IONetworks 4.03
  
• IONetworks 4.02
  
• IONetworks 3.20
  Have real USB stack implementation, support numerous USB device classes, e.g. USB Storage (Flash, HDD), keyboards, mice, hubs and some other devices those I don't know.
• IONetworks 3.10
• IONetworks 2.90
• IONetworks 2.80
• IONetworks 2.70
• Woodhead's USB drivers
  Author says that drivers support USB 2.0. USB 1.1 works fine. Supports USB Storage devices only (e.g. Flash, HDD), but works faster than IONetworks Is open source.
• bsquare_usb_nt4.rar/tgz (730 Kb/760.5 Kb) - BSquare USB.
• aksnt4usb.rar/tgz (264 Kb/278.8 Kb)
  Native home page - http://www.aladdin.com/support/hasp/hasp4/enduser.asp You can get the file from local copy. Do not download from original site since it requires password. Is mainly used with AladdinHasp's on USB. (e.g. in 1c Enterprise 8.x under NT4, this driver is even included in 1Cv8 setup).

Note: When using these drivers you should sync disk cache before USB Flash hot removal with dsync.exe.

N1

I've tried version 4.06. My PCI USB 2.0 card made by VIA doesn't work. The problem is originated by unassigned interrupt vector. BIOS didn't make IRQ assignment.

Btw, thanks to --irt option of PCI Dump v0.2 I've understand why. For some reason when this card is inserted into PCI slot 6, it gets DeviceNumber=0x0c. The same time BIOS PCI IRQ Routing table says that it should have DeviceNumber=0x07 in this slot. I don't know yet how to fix this problem, but when I inserted card into different slot, the card got proper DeviceNumber, BIOS assigned IRQ to it and USB drivers did their work :)

N2

In vesion 4.06 USB 2.0 support appeared to be buggy. If at least one USB 2.0 controller is present in system the following problem comes. After disconnecting USB Flash (even if it was connected to some other controller, e.g. onboard USB 1.1) special record about this connection is left in registry. It includes port, USB device name and assigned drive letter. After reboot system hangs after logging in. If you wait long enough, login screen shall be displayed again. Debugger shows that USBD.SYS falls into dead loop. It reads some I/O port(s) and waits for something. This happens when USB management app is started.

If you boot to another OS (or with Hardware Profile with all USB drivers disabled), mount SYSTEM Registry Hive and remove this record, everything will work again.

N3

USB 2.0 support appeared to be even more buggy. If at least one USB 2.0 controller is present in system, then after running WinXP the same problem with hang happens. Power off is the only remedy. This bug is experienced with 4.10, 4.06 and 3.20 versions. Previous versions are not tested yet. Used hardware - VIA USB 2.0 PCI Card, onboard USB 2.0 controllers on my notebook.

N4

Author says that drivers support USB 2.0. But while my PCI USB 2.0 Card didn't get interrupt vector, they crashed.

N5

When I installed aksnt4usb nothing happened. They just did nothing. But when I instelled IONetworks together with them, IONetworks could not work. Also did nothing.