• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
maximus-decim

Maximus-Decim Native USB Drivers

804 posts in this topic

SP1, SP1a and SP2 DOES allow that...

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

0

Share this post


Link to post
Share on other sites

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.

Edited by niknak
0

Share this post


Link to post
Share on other sites
SP1, SP1a and SP2 DOES allow that...

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

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

0

Share this post


Link to post
Share on other sites

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=&amp...st&p=540811

The truth: Windows 95 supports hard disks of up to 137 GB in size, except on systems with a Phoenix BIOS using BitShift translation.

btw you can have allmost 4gb fat16 partitions on nt4

0

Share this post


Link to post
Share on other sites

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? :D

HTH

0

Share this post


Link to post
Share on other sites

_NUSB.INF in English version -

;Localizable strings
Lang = "RU"
LocaleID = "UPD"
UpdName = "Windows 98 Second Edition Q242975 Update"
AdvPackWarn = "You need a newer version of advpack.dll."
SrcDiskName = "Native USB-flashdisk for Windows 98 3.3 Eng include 242975"

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!

Edited by submix8c
0

Share this post


Link to post
Share on other sites

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

0

Share this post


Link to post
Share on other sites
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.

0

Share this post


Link to post
Share on other sites

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 !

Edited by zonar
0

Share this post


Link to post
Share on other sites

Hmmm .....

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

Rgds

0

Share this post


Link to post
Share on other sites
Get the correct (language specific) version and it should work just fine ...

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

Edited by zonar
0

Share this post


Link to post
Share on other sites

Did you pay for the patch? 'cause I can't upload it

Sansa says it can't be done but I'm still trying! :thumbup

0

Share this post


Link to post
Share on other sites

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

0

Share this post


Link to post
Share on other sites
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

Hi, risk_reversal! :hello:

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 by 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.

Edited by dencorso
0

Share this post


Link to post
Share on other sites

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)

0

Share this post


Link to post
Share on other sites
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.

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

Edited by risk_reversal
0

Share this post


Link to post
Share on other sites
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. Edited by dencorso
0

Share this post


Link to post
Share on other sites
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. :thumbup

0

Share this post


Link to post
Share on other sites

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?

0

Share this post


Link to post
Share on other sites
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. :blink: 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. :whistle:

Edited by dencorso
0

Share this post


Link to post
Share on other sites

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.

0

Share this post


Link to post
Share on other sites

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.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.