[CATSDOGS]

thank for reply
I'll do a complete backup using hdd cloning software by seagate acronis,as these other bootable cloning apps,are way too advanced for me :]

[dencorso]

Acronis is fine. The important thing is to make the full backup. Then you're safe.

[bizzybody]

"Foolproof" instructions for this driver? I'm fixing up an olde Compaq Armada 7380DMT* (I don't have a USB card for it) and writing what I hope are user-proof instructions for various things. Here's what I did for this USB driver.

Feel free to copy, modify, add to, remove from, fold, spindle, mutilate, translate into Farsi...

*This laptop dates from 1999, quite possibly the last laptop series ever *without* built in USB. Strange of Compaq to not have USB on these when others had it at least as early as 1997.

Quote

1. Obtain a Cardbus USB card with Windows 98 Second Edition drivers.
2. Follow its instructions for installing its drivers.
3. DO NOT install any drivers for your USB Mass Storage devices.
3. Run nusb33e.exe to install universal USB Mass Storage drivers.

All USB Mass Storage devices such as external hard drives, thumb/pen drives, floppy drives, audio/video players, digital cameras and cell phones with drive/disk/mass storage mode should work, as long as the filesystem is FAT16 or FAT32.

In other words, if you can plug it into WinMe, 2000, XP or Vista and use it like a disk drive *without* having to install a driver, it *should* work in 98SE with this driver.

If not, go here. http://www.msfn.org/board/maximus-decim-na...ers-t43605.html

This driver DOES NOT SUPPORT non-storage devices such as scanners, printers, tablets, cameras/phones that *don't* have a drive/disk/mass storage mode, or any other device that doesn't act like a disk drive.

If it is a storage device and requires a driver for WinMe, 2000, XP or Vista, it won't work with this driver in 98SE. (Note that some storage devices may have drivers/utilities for features other than basic storage support that does not require a driver to be installed.)

This USB driver is only for the ENGLISH version of 98SE. See the above forum link for versions for other languages. If there's not one for your 98SE's language, ask nicely and someone there may be able to fix you up.

Why this driver instead of installing individual drivers for every camera, drive and phone? Multiple USB Mass Storage drivers use up room on your hard drive, use more RAM, add more bloat to the Registry and can cause conflicts with each other.

Additional note for media with a formatted capacity of less than 32 megabytes (includes media with exactly 32 meg unformatted capacity). Windows 2000 and XP will format such media as FAT12. Windows Me and 98SE with this driver will format such media as FAT16. It's best to never format 32meg or smaller media with 2000 or XP, especially when it's the non-removable memory in a device.

[snuz2]

I am looking for info on whether it is possible to get the device names to appear in Explorer instead of just "Removable Disk". I tried to edit the obvious .inf but nothing has changed. Any info on how to do this?

I ask because some devices mount as multiple disks and it's hard to distinguish them. Thanks.

[fortcollins]

What is a "native USB driver," as opposed to any other kind of USB driver?

[lightning slinger]

fortcollins, on Oct 28 2009, 08:49 AM, said:

What is a "native USB driver," as opposed to any other kind of USB driver?

Native means, as the name implies, built-in USB driver support without the the need for installation of additional drivers for each type of USB device being used.

[jrronimo]

I've run into a problem with this wonderful driver package.

After I install it, my USB network adapters stop working.

I have a Win98 FE machine that has all of its PCI slots full. Installing the USB Driver makes usb flash drives work, but the ntkern.vxd included doesn't work with either my linksys usb200m or a d-link of similar fashion. Neither device loads and the problem goes away when I use sfc to restore ntkern.vxd... but then flash drives don't load.

Is there a solution to this? Thanks for the support over the years! Just having this ability is awesome.

Oh yeah -- as a note, this machine is connected to a domain, if that makes a difference.

This post has been edited by jrronimo: 19 November 2009 - 07:02 PM

[lightning slinger]

jrronimo, on Nov 20 2009, 01:01 AM, said:

I've run into a problem with this wonderful driver package.

Have you installed the correct package for Win98FE?

NUSB3.3 is for 98SE and NUSB3.2 is for 98FE. See post#350 in this thread by PassingBy, the creator of the 98FE version.

Direct download at http://www.mdgx.com/spx/NUSB98FE.EXE
HTH

This post has been edited by lightning slinger: 20 November 2009 - 03:03 PM

[jrronimo]

lightning slinger, on Nov 20 2009, 01:48 PM, said:

jrronimo, on Nov 20 2009, 01:01 AM, said:

I've run into a problem with this wonderful driver package.

Have you installed the correct package for Win98FE?

NUSB3.3 is for 98SE and NUSB3.2 is for 98FE. See post#350 in this thread by PassingBy, the creator of the 98FE version.

Direct download at http://www.mdgx.com/spx/NUSB98FE.EXE
HTH

Thanks for the reply. I did make sure to download the FE package yesterday, so I'm pretty confident that I got the right one. Further, it did actually work -- it let me plug in a USB mass storage device which I could read/write to.

It's just that the USB network adapters stop working, and I need 'em.

[lightning slinger]

@jrronimo

This problem may have surfaced on a previous occasion with NUSB98FE3.2 if you read post #455 in this thread. Sadly no one then posted any suggestion on how to cure that problem.

There are a small number of 98FE users here, perhaps one of them may pick up on your problem.

[jrronimo]

lightning slinger, on Nov 21 2009, 01:58 PM, said:

@jrronimo

This problem may have surfaced on a previous occasion with NUSB98FE3.2 if you read post #455 in this thread. Sadly no one then posted any suggestion on how to cure that problem.

There are a small number of 98FE users here, perhaps one of them may pick up on your problem.

Ahh, thanks for the head's up.

It's definitely the ntkern.vxd file that is different between the two. The other thing I noticed is that it's like the computer can't load the drivers for the USB Network adapters with the patch in place. It's like that version of the .vxd doesn't contain the commands for talking to a network card or something strange like that. I should probably read through the rest of this thread to see if I can figure something out...

This problem is essentially going to go away in about 6 months, but it'd be nice to have a fix out there. The computer in question is attached to a Scanning Electron Microscope and has a lot of specialized cards installed, leaving us with only USB networking... but it'd be really nice if we could get data off the machine with a flash drive.

Thanks again! I'm glad to see that people still check this thread out.

[dencorso]

The discussion about Strange Problems with Pendrives, which was started by LoneCrusader, is now split into it's very own thread, and you all can find it here: link.

[xrayer]

Hi,
I was using happilly nUSB 3.3 more than year on my new system (P31+ICH7) and it worked fine.
But yesterday I found that it suddenly failed. I cannot use any of my USB devices that worked before.
I got this error in device manager: http://rayer.ic.cz/350d/usb.png
I mess near all night with it, I cleaned enum entries, reinstalled nUSB 3.3 but nothing helps. Under WinXP
and Linux all devices on all ports works fine. As a last resort I tried downgrade to nUSB 3.3a (with USBSTOR.SYS from WinME) and it works. But I got much worse performance now, only about 10MB/s instead ~25MB/s of my HDD box (but luckily it seems USB 2.0 is working). I cannot find explanation what happen. I didn't add any new USB device.
The only thing I did with hardware was that I tried borrowed GeForce 8800GTS few days ago. But It didn't worked
so I put back my 7900GT. After this experiment I delleted my win98 directory and restore from backup some weeks
old. That time in past I had nUSB 3.3 working now it fails. I found it is only sensitive to USBSTOR.SYS file.
When I replace it with older WinME version it works when replace Win2k version it didn't I can toggle it many times.
I also tried clear CMOS, clear DMI/ESCD, flash older BIOS but nothing helps to run nUSB 3.3 now. Any idea?
Why is ntkern.vxd failing?

[dencorso]

xrayer, on Dec 14 2009, 10:32 PM, said:

downgrade to nUSB 3.3a (with USBSTOR.SYS from WinME) and it works.

What downgrade are you talking about xRayeR? NUSB uses Win ME USBSTOR.SYS (v. 4.90.3000.1) since NUSB 3.1 and up to 3.3, so there's no downgrade in it (read again the 1st post in this thread). Check for yourself, here are direct download links to two bona fide sources for it: NUSB3.3 (at MDGx) and NUSB3.3 (at technical-assistance.co.uk). What version of USBSTOR.SYS were you using that suddenly stopped working? If you mean USBSTOR.SYS (v. 5.0.2195.6655) from NUSB 3.0, it also needs WDMSTUB.SYS, also from NUSB 3.0 to work. To install it, you might just drop WDMSTUB.SYS from NUSB 3.0 in your %windir%\Sytem32\Drivers directory and edit the line in USBSTOR.INF that reads:
HKR,,NTMPDriver,,USBSTOR.SYS
to read, instead:
HKR,,NTMPDriver,,"WDMSTUB.SYS,USBSTOR.SYS"
and redetect all USB devices.
You can get NUSB 3.0 (here). Observe that all the links in this post are for English versions of NUSB, but WDMSTUB.SYS is language neutral.

[xrayer]

dencorso, on Dec 15 2009, 02:28 AM, said:

What downgrade are you talking about xRayeR? NUSB uses Win ME USBSTOR.SYS (v. 4.90.3000.1) since NUSB 3.1 and up to 3.3, so there's no downgrade in it (read again the 1st post in this thread).

I use nUSB 3.3 Czech version which seems was modified to use w2k usbser.

Package 3.3 CZ contains:

USBSTOR.SYS 5.0.2195.6655 (eng)
WDMSTUB.SYS 5.0.0.6

and 3.3a CZ contains:

USBSTOR.SYS 4.90.3000.0 (eng)
WDMSTUB.SYS 5.0.0.6

So 3.3a cz should equal to your oficial 3.3 eng.
WDMSTUB.SYS is also installed in my windows drivers directory so it's not the problem.
But the USBSTOR.INF doesn't have register entry for WDMSTUB.SYS is it necessary?
I'll try to fix the inf.

[xrayer]

Yeah, it works!
You pointed me right way! Many thanks.
I added wdmstub.sys to INF

[USBSTOR.AddReg]
HKR,,DevLoader,,*NTKERN
HKR,,NTMPDriver,,"WDMSTUB.SYS,USBSTOR.SYS"

And redetect the USB device (no restart needed) and it works now. So it seems to be a bug in 3.3 cz
I have installed some older versions before so wdmstub might be registered from old times and for
some reason it was lost from registry.

This post has been edited by xrayer: 15 December 2009 - 03:31 AM

[Philco]

xrayer, on Dec 15 2009, 04:30 AM, said:

Yeah, it works!
You pointed me right way! Many thanks.
I added wdmstub.sys to INF

[USBSTOR.AddReg]
HKR,,DevLoader,,*NTKERN
HKR,,NTMPDriver,,"WDMSTUB.SYS,USBSTOR.SYS"

And redetect the USB device (no restart needed) and it works now. So it seems to be a bug in 3.3 cz
I have installed some older versions before so wdmstub might be registered from old times and for
some reason it was lost from registry.

thx xrayer and dencorso, i create today corrected version, update.

[Philco]

dencorso, on Dec 14 2009, 08:28 PM, said:

xrayer, on Dec 14 2009, 10:32 PM, said:

downgrade to nUSB 3.3a (with USBSTOR.SYS from WinME) and it works.

What downgrade are you talking about xRayeR? NUSB uses Win ME USBSTOR.SYS (v. 4.90.3000.1) since NUSB 3.1 and up to 3.3, so there's no downgrade in it (read again the 1st post in this thread). Check for yourself, here are direct download links to two bona fide sources for it: NUSB3.3 (at MDGx) and NUSB3.3 (at technical-assistance.co.uk). What version of USBSTOR.SYS were you using that suddenly stopped working? If you mean USBSTOR.SYS (v. 5.0.2195.6655) from NUSB 3.0, it also needs WDMSTUB.SYS, also from NUSB 3.0 to work. To install it, you might just drop WDMSTUB.SYS from NUSB 3.0 in your %windir%\Sytem32\Drivers directory and edit the line in USBSTOR.INF that reads:
HKR,,NTMPDriver,,USBSTOR.SYS
to read, instead:
HKR,,NTMPDriver,,"WDMSTUB.SYS,USBSTOR.SYS"
and redetect all USB devices.
You can get NUSB 3.0 (here). Observe that all the links in this post are for English versions of NUSB, but WDMSTUB.SYS is language neutral.

Please, in uninstall file _nusb.inf (3.0):

;wdmstub
;HKLM,System\CurrentControlSet\Services\Class\System\0000,NTMPDriver,,"update.sys,wdmstub.sys"

Why REM (? It's OK?

[CharlotteTheHarlot]

@maximus-decim ...

I just Windiffed the latest Nusb (33e) to the previous I had installed (33) and found one minor difference in the USBSTOR.INF: see line 16 for an uncommented comment. Not sure if it breaks the INF or not. There are also a bunch of trailing spaces here and there which mean nothing (except to Windiff of course ;-)

@Everyone ...

Does anyone know if there is a Hoiby-like patch for the EXPLORER.EXE that comes in this NUSB distro (version is 4.72.3612.1700)?

[dencorso]

@Charlotte:
Please post both the different lines, and I'll tell you.
Update to explorer 4.72.3612.1710 from MDGx's and you'll have it all.

Philco, on Dec 15 2009, 10:07 PM, said:

Please, in uninstall file _nusb.inf (3.0):

;wdmstub
;HKLM,System\CurrentControlSet\Services\Class\System\0000,NTMPDriver,,"update.sys,wdmstub.sys"

Why REM (? It's OK?

@Philco:
It must be a leftover of Maximus-Decim first experiences with wdmstub.sys
If you add it to update.sys, it becomes permanently loaded, so there maybe would be unnecessary to add it to usbstor.sys... but afterwards MD decided to add it directly to usbstor.sys. So either adding it to update.sys doesn't work, or it does work, but MD preferred to use wdmstub.sys in the way it was originally intended for use by its author, Walter Oney. You may leave it there, or you may delete it.