I have WinXp SP2 and I'm still limited to 32GB

Eidenk
I wish.
Win 95 Retail FAT16 2GB same for NT4
Win 95 OSR2x FAT32 32GB
Win 98 Retail FAT32 64GB
Win 98 SE FAT32 127GB
Win ME FAT32 127GB (I assume, I never used it)
Win 2000 FAT32 32GB create only Can mount larger partitions
Win XP FAT32 32GB create only Can mount larger partitions
see other comments above
Theoretical limit 2TB and MS only got to 127GB (I know, this was also the limit of the disk tools) still I don't think they really tried.

BenoitRen
USB HD drivers are different, but we were talking retro fitting in W95OSR2 and how to get it to work. MD's files can't be used there.

Thanks Galahs for your information (I will try a fresh W98SE install this weekend and see if I can get it to work) and the link to swissknife - I had not heard off it.

FAT32 my bad I wasn't thinking of FAT32...

are you sure about 95b not supporting 32gb hdd im sure there was stuff about this before
http://www.msfn.org/board/index.php?s=&...st&p=540811



btw you can have allmost 4gb fat16 partitions on nt4

French Version 3.3:

http://rapidshare.com/files/73490201/NUSB33f.rar

German Version v 3.3
http://www.nandlstadt.com/downloads.htm

Mirror, mirror...

* Unofficial Windows 98 SE Native USB Drivers (NUSB) 3.3 (free):
http://www.msfn.org/board/?showtopic=43605
- NUSB 3.3 [756 KB, English]:
http://www.mdgx.com/spx/NUSB.EXE
- NUSB 3.3 [762 KB, French]:
http://www.mdgx.com/spx/NUSBFR.EXE
- NUSB 3.3 [766 KB, German]:
http://www.mdgx.com/spx/NUSBDE.EXE
- NUSB 3.1 [751 KB, Italian]:
http://www.mdgx.com/spx/NUSBIT.EXE
NUSB in languages other than English:
http://www.technical-assistance.co.uk/kb/usbmsd98.php

... on the wall...

* Unofficial Windows 98/98 SP1 Native USB Drivers (NUSB98FE) 3.2 (free):
http://www.msfn.org/board/?showtopic=43605&st=349
- NUSB98FE 3.2 [999 KB, English]:
http://www.mdgx.com/spx/NUSB98FE.EXE
- NUSB98FE 3.2 [999 KB, French]:
http://www.mdgx.com/spx/NUSBFRFE.EXE
- NUSB98FE 3.1 [768 KB, Italian]:
http://www.mdgx.com/spx/NUSBITFE.EXE
NUSB in languages other than English:
http://www.technical-assistance.co.uk/kb/usbmsd98.php

... who's the fairest one of all?

HTH

_NUSB.INF in English version -
Note the "Lang" value... (?)

By-the-by,
Result after installing 98SE using UBCD (latest) without NUSB3.1 (version currently used in UBCD), then installing NUSB3.3 (after above correction to "EN") -
- correctly does NOT overlay pre-existing components also in NUSB (UBCD versions newer)
- DOES cause EXPLORER.EXE Icons on desktop to change to older EXPLORER.EXE of NUSB
- deleting ShellIconCache or using TweakUI to Repair Explorer Desktop Icons corrects this
So, is this just an ideosyncracy of just "attempting to overlay" as found in "_NUSB.INF"? (I don't know how the INF/QFECheck stuff would prevent inadvertant overlay of newer modules but screw up icons.) Any ideas?

Also noted install places all files in OPTIONS\CABS... Rationale? Some official/unofficial in UBCD don't do this, eg Unofficial Q891711 (User.exe/User32.dll) and Unofficial ExplorUp (EXPLORER.EXE). And if they did, would it "hose" anything? Sigh... so confused!

Hmmm .....

Nusb98fe versions have been corrected since 3.12 ... can anyone confirm whether it should be ENG or ENU ? or something else ? or its a minor thing ?

Rgds

Hi, PassingBy!
Check the language code at VS_FIXEDFILEINFO structure (version resource as seen by eXeScope, for instance) and I bet you'll find most, if not all, files are 0x0409. Then, as "American English" = "ENU" = 0x0409 and "British English" = "ENG" = 0x0809, IMHO "ENU" is the best choice.

Hello,
Does anybody know whether this generic driver work with: USB Crucial, GizmoJr 1Gig ?? (I do not have this key, I am trying to help somebody..)
Thanks and Happpy new year from Belgium !

Hmmm .....

Get the correct (language specific) version and it should work just fine ...

Rgds

Well well interesting...do you mean that the driver is "language specific" ?? could you give me some details??
EDIT: ok great! I did it with the 95 driver, I just had to add the good line (VID etc..), fantastic! a 'driver' with less than 100K

Did you pay for the patch? 'cause I can't upload it
Sansa says it can't be done but I'm still trying!

Having read the 21 pages of this very informative thread I wonder if I can clarify and confirm the following points please.

1. The main difference between NUSB v2.x and v3.x is as follows:
a- v2.x contains just the mass USB storage driver.
b- v3.x contains the mass USB storage drive AND the USB2.0 controller driver.

2. If v2.x is already installed on a system can the existing USBSTOR.INF file version (c:\windows\INF) be replaced by the updated USBSTOR.INF file from v3.x (ie just a cut and paste).

3. If v2.x is already installed on a system, is it not possible to upgrade to v3.x by installing v3.x over (so need to ghost partition prior to any NUSB install).

Have I understood all this correctly please?

Many thanks for your help

Cheers

Does this driver support PTP (Picture Transfer Protocol) cameras?

Hi, risk_reversal!

1.) Yes, but NUSB v. 3.3 also has some additional important files. See below.

2) Yes, I've done that without problems, but USBSTOR.INF bay itself is not enough. So, if you install NUSB 2.4, you should substitute its USBSTOR.INF by that in NUSB 3.3, AND also substitute, at least, DISKTSD.VXD and CDVSD.VXD from your %windir%\system\vmm32 directory by those found in NUSB 3.3. DISKTSD.VXD is fundamental for using USB Floppy Disk Drives without getting a BSOD. Both VxDs are the last versions compatible with Win 9x, so they improve overall performance by preventing crashes.

3) I think you can upgrade flawlessly. But I never had the opportunity to test this approach, because the two machines having NUSB 2.4 that I have worked on had no USB 2.0 hardware, so I did what I described above, instead of doing a full upgrade.

HTH. Best wishes.

I'm still waiting for a fix that will make it play nicely with an integrated 1394 controller that can't be disabled. (Compaq Presario 5610)

Many thanks for the info dencorso. I have noted your comments in respect of the USBSTOR.INF file.

I have been testing v2.4 on a USB2.0 enabled mobo (VIA K8T800Pro VT8237 southbridge) and did not want to disturb the existing USB2.0 driver. I just wanted to add mass usb storage capability hence my interest in v2.x.

So far all seems well with no issues. NUSB 2.4 has detected the drives that I connected (Corsair 1Gb & 4Gb) a digital camera Sony DSC (usb1.1) and a Sandisk SD reader. The remove hw icon in the system tray has ejected all drives (& reader) correctly.

Although this board has a VIA SATA controller, I have my HDD connected to the on-board Promise SATA controller since I o/c the cpu. It is because of this slightly more complex set up (ie on-board Promise controller runs on the PCI bus) that I did not want to use NUSB v3.x but may wish to use updated USBSTOR.INF files (although don't think I will be using usb floppy drives, prefer the normal variety).

Many thanks again for the info

Cheers

Well, you can just rename the USBSTOR.INF from NUSB 2.4 to, say, USBSTOR.024 and copy the USBSTOR.INF from NUSB 3.3 to the %windir%\INF dir, and then either delete USBSTOR.024 or just let it lie there, without ever leaving windows. Provided you never ever plug an USB Floppy Disk Drive, this will work just fine. And add a lot more definitions to your system, so it can potentially recognize even more devices. HTH.

Many thanks again dencorso. That works for me.

I've found another board that NUSB 3.3 DOES NOT WORK WITH. It's the TriGem/HP "Cognac" socket 370 micro ATX. This board has nothing 'funky' about it. It's an ordinary Intel 810 chipset, NO built in 1394 controller like the Compaq Presario 5610, which NUSB 3.3 doesn't work with either.

Clean install of 98SE, all the hardware drivers, reboot, install NUSB 3.3, reboot and BLAM. Stick a fork in it, Windows is done. Won't even go into Safe Mode because Explorer.exe commits digital seppuku.

Fortunately I made a copy of c:\Windows before installing NUSB 3.3 so I can just connect the drive to another PC and copy it all back.

I have six other old boxen, all are going to get 98SE installed. They're all different boards and CPUs. It'll really be a PITA if some or all of them have this same problem.

What'd be nice to have is a DOS bootable disk that can REPAIR a system that this blows up so people don't end up having to completely reinstall Windows. What'd be even better is if it worked instead of causing this problem.

How about an installer option that asks if the computer has a floppy drive, then doesn't install the stuff to support USB floppy drives? Who is going to plug a USB floppy drive into a PC that has a normal one already?

How do you know the problem is with USB FDD support? Does NUSB 3.1 work and 3.3 break the system?
Or are you just guessing? Why don't you track down the problem? It sure is much better to light a candle than keep cursing the darkness. Since you have the board that exhibits the problem and most of us don't, you are in a unique position to help make NUSB even better than it is. Please, go ahead and do it!
BTW, I do have both a 3.5 and a 5.25 internal FDD drives in the machine, yet I went ahead and found the way to add USB FDD support to NUSB. While doing it, I did plug one, even two USB FDDs to the same machine. It is pointless to ask "who is going to do something?" because someone will always find a reason to do so... it's part of being human.

I got this one figured out. I copied the Win98 folder from an original CD-ROM to one of my XP computers and had copied that same folder to hard drives before installing the drives in old computers.

Apparently something went funky with that folder on the XP system- not enough to prevent 98SE from installing, but it'd make it screw up after installing NUSB. So I copied the win98 folder directly from the original CD-ROM to the PC with the "Cognac" motherboard, did a fresh install and no problems. I just installed NUSB 3.3 and still no problems.

Next I'll go back to the Compaq Presario 5610 with a fresh-fresh, right off the original CD-ROM install and see if that one still has a problem with NUSB. That was the first time this had caused a problem for me. If it doesn't this time around, then I'll know when something happened to the 98SE install files, but not what.

Looks like that needs to be added to the NUSB readme, "If you have any problems after installing NUSB, do a clean install from an original 98SE CD-ROM."

I didn't suspect a problem with the install files because it had ALWAYS WORKED until that Compaq, and that didn't make me think it might be the install files because of the built in 1394 controller that can't be disabled in BIOS.

Kinda off-topic but related to your issue, I could confirm that certain applications/drivers/etc. at install time may be searching for %windir% to deploy some of their files and in doing that, they're probably searching for specific Windows file(s). When the Windows installation kit (clear copy of the CD-ROM) is found on the (active) drive, it probably contains the respective file(s), which tricks those applications into thinking that they found %windir%, so they deploy their files there instead of the real %windir% folder.

I've had such behavior with my Lexmark 1150 combo while having the Win98SE kit on drive C: for testing the UBCD project, when I found dozens of Lexmark-related files in the Win98 folder, wondering how they ended up in there.

Basically what I'm saying is that some original Windows installation file may be overwritten by other from another application while the kit is on the HDD, so it'd be recommended for the Windows installation kit to be zipped or saved as an ISO image, mountable in Daemon Tools, Nero Virtual Drive, etc. or quickly browsable through Total Commander's ISO plug-in or similar.

I've got a Stratitec USB card in my 98SE box. It came with the orangeware drivers, version 2.06 I think. I upgraded these to version 2.3, which seems to be the best overall version for my PC. Version 2.41 didn't work nearly as well. The USB that's on the motherboard is 1.0, 98FE hardware.

I removed all the orangeware drivers, installed NUSB 3.3, and rebooted. After rebooting, Windows still tries to install PCI USB drivers. It doesn't accept anything from NUSB 3.3, wants OUSB2HUB.SYS and OUSBEHCI.SYS. Without them, device manager says "drivers not installed". Are the NUSB drivers supposed to replace/substitute for the orangeware drivers?

When plugged into the USB card, the external HD works but is much slower than with the orangeware drivers. When using the USB plugs on the motherboard, there's also a long delay in the opening of folders, extracting archives, etc in addition to the overall slowness.
Rick

Romoved = Removed from Add/Remove Programs ?
It may not be enough. I think the .inf file was left behind. Delete it.

I just wanted to say thank you for the native usb drivers. Not only did I get both my USB hard drive working on 98SE, but I also got my external dvd burner working as well...and both are working more efficiently than they were on XP Pro! It's a shame the 98 user base has reduced so much that not that many people would even be willing to try it anymore with all of the new fixes. Keep up the good work!

Hell, I'd even throw in a donation for the work you've put into it. (And that's saying something considering that I absolutely refuse to even consider paying for most modern software).

Czech build Maxim Decimus NUSB v. 3.3a (correct bug in inf files and replace DLL) (only for czech version Windows 98 SE)
(Česká verze ovladače USB od Maxim Decimus verze 3.3a (oprava inf souboru a náhrada "zlobících" knihoven DLL) pouze pro české Windows 98 Druhé vydání)

Nusb33a_cs.exe

Phone Sony K800i - with NUSB not properly. I try this (in inf note win98): http://www.nxtg.net/files/sony-ericsson-k-series-drivers.zip

Result: error. Help? (I need only USB cable support => transfering digital photo)

You might have the same problem as I have with stupid Huawei U1220S phone. They just don't want to offer Win9x drivers for their hardware and NUSB can't do anything about it.

Memory card storage may be available but other phone-related functions will not.

I tried to use nusb3.3 on my system and it won't let explorer start or run. This is explorer from 95 running on SE. SE was patched with SP2.1a from this site. Reverting to 98 explorer allows the system to start, but it seems kind of shaky so far.
MOBO is intel D815. Two questions for anyone who can help:

1. Do I need to further patch this system to get it to work well? Will it ever work with 95 explorer?

2. If not, can someone tell me how to remove it? Otherwise, I have a long journey to reinstall everything.

Thanks all.

i have a box i used 98lite on with the 95 shell, when i installed nusb3.3 i found that it installed a newer explorer.exe so i referted to the 95 one and it worked fine after that

Thanks awergh! The problem was a reinstall of explorer.exe.

There was some weirdness of it BSOD after 2nd insertion of device, but that went away, pretty sure I didn't change anything either...I suspect my system is not up to date with the correct patches.

Still would like to know how to remove nusb as well, in case I can't get it to work.

Thanks .

Just FYI, regarding the problems several of you report with the Mitsumi/IBM FDD. Be aware that FDD is one of the current industry standards. It is designed specifically as a laptop/desktop boot drive (besides being a super speed drive). For example, I am obsessed with the EePC now, so much that I haven't used my "big cumbersome" laptop in months. The Mitsumi is the ONLY "recommended" FDD for the EeePC. Why? Because the driver is contained in BIOS. Therefore, even before USB is detected, the Mitsumiit is automatically installed in Windows desktop (even if USB has not yet been installed)! This is a boot function, only true if it was plugged in BEFORE post/BIOS. Most newer laptops have the Mitsumi FDD resident in BIOS. Check that by deselcting BIOS "quiet boot". If the Mitsumi shows up, you have newer BIOS that already supports the FDD. So it doesn't need a "driver". Otherwise, if you add a "generic/universal" that includes Mitsumi, then desktop/kernel adds ANOTHER driver (like GenGuide) the drive will have TWO registries, thus TWO processes trying to command its IO. That always results in a problem. Like Colon Powell and Rumsfeld, two "bosses" tring to run a show... recipe for failure. So if your Mitsumi/IBM is to be used with a "universal" USB driver, containing multiple storage devices, then you should NOT have it connected at boot! That way, only the "universal driver" will load, and all will be fine. Myself, I just strip the Mitsumi from all my USB .inf files/registry, so that it is ONLY controlled by BIOS. The performance is MUCH better that way. Maximus is a great solution, but let your "universal" or "Maximus" control everything EXCEPT the Mitsumi. That is your best arrangement, since BIOS controlled devices have more powerful friends "higher up in the kernel" (earlier in the load).

I have recently bought Zaapa USB card reader/writer for SD mini SD and MMC cards.
My computer is DELL XPS D300Mhz PII. My OS is Win98 English.
The dealer of Zaapa sent me Maximum Decim Native driver V3.2 for Win98FE.
I installed the driver to C:\Windows directory.
During the installation I notice an error message INF File "\_nusb.inf" not found.
But the installation proceeded successfully.
Although the USB green light stays on lighting, I cannot see the icon of the USB in MyComputer.
It looks that the system still doesn't recognize the USB card reader/writer.
Could you advise if there is anyhting which can be done to rectify this problem?
Thanks

hi,everyone
How to make it run under Chinese evironment?my system is Chinese language.
today i tried to setup it(English ver),but my system was dead after that......re-setup....
so,what can i do?should i replace user.exe and user.dll?where can i download them?
thanks a lot

Why are you so angry when you where the one that tried an english patch on a chinese os?

what should i do?

you might want to update your pack with this

Unofficial MS-DOS 5/6/7/8 + Windows 3.1x/9x/ME Panasonic native DOS USB driver USBASPI.EXE (USBASPI.SYS) 2.24 Fix

Links? Thx.

See the top post in the updates sticky... it's findable at MDGx's now.

I have an Olympus C3030 Zoom digital camera. To get images off of the camera I supposedly need to install Olympus's Camedia software. I ran across this recently:

http://groups.google.com/group/de.alt.rec....4eca67343d36ab1

It's for XP, mentions opening srusbusd.inf in notepad and removing some semicolons. It looks to me you could fix more than Olympus cameras. Are these cameras supported using your native USB drivers? If not could they be added?

Hi PassingBy. The link to "post $350" is no longer working.

I've just received my cousin's old eMachine computer that has built-in USB ports [one in front and one in the back of the PC] and will test out your NUSB98FE package I obtained from MDGx's web site. I'll have to install the Win98 FE OS and the Intel chipset drivers before I proceed with NUSB98FE.

Why the explorer.exe 4.72.3612.1700 is included in NUSB 3.3
and what is patched ?????

Hmmm .....

Hey there erpdude8 ,

I'm in a bit of a tight schedule right now ... and away from my dev systems ...

If you could hold out just for another couple of days or so, I'll post an updated pack to match the latest NUSB by Maximum-Decim ... It's already been tested for months now on several W98FE systems but I haven't gotten round to include an un-install routine yet ... That's on the to-do-list ...

I apologise for being lame and not having the updated pack posted much earlier ...

@barbarien:

The explorer is the pretty much the same used in nusb33e (maybe some resource is different here and there but definitely no code patches were done). So, no major differences there. It's there to handle usb insertion messages correctly ...

Rgds

what is when i overwrite these explorer.exe with the one from
dr.hoiby 4.72.3612.1710 ?? explor98 patch


and i found another version of 4.72.3612.1700
here --- http://support.microsoft.com/kb/246073/de


im now a bit confused

the original win 98se is 4.72.3110.1

nusb v3.3 is entered in Win98SE Add/Remove as "Remove Unofficial Universal USB 2.0 Stack". What does uninstall exactly do and not do?

It just removes the Universal USB 2.0 Stack (cf post #1), probably to give people the chance to uninstall it before installing either Sis or VIA USB 2.0 Stack. It does not remove the core NUSB files. You can remove NUSB from DOS by hand. But most of the files not directly related to USB don't need to be removed in any scenario I can envisage. Then again, YMMV.