[galahs]

Kelsenellenelvian, on Nov 28 2007, 01:46 AM, said:

SP1, SP1a and SP2 DOES allow that...

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

[niknak]

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.

This post has been edited by niknak: 29 November 2007 - 03:47 PM

[Kelsenellenelvian]

galahs, on Nov 28 2007, 04:34 AM, said:

Kelsenellenelvian, on Nov 28 2007, 01:46 AM, said:

SP1, SP1a and SP2 DOES allow that...

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

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

[awergh]

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

Quote

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

[WebMatze]

French Version 3.3:

http://rapidshare.co...201/NUSB33f.rar

[swgreed]

German Version v 3.3
http://www.nandlstad...m/downloads.htm

[MDGx]

Mirror, mirror...

* Unofficial Windows 98 SE Native USB Drivers (NUSB) 3.3 (free):
http://www.msfn.org/...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...kb/usbmsd98.php

... on the wall...

* Unofficial Windows 98/98 SP1 Native USB Drivers (NUSB98FE) 3.2 (free):
http://www.msfn.org/...ic=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...kb/usbmsd98.php

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

HTH

[submix8c]

_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!

This post has been edited by submix8c: 15 December 2007 - 04:46 PM

[PassingBy]

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

[dencorso]

PassingBy, on Dec 15 2007, 08:12 PM, said:

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.

[zonar]

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 !

This post has been edited by zonar: 06 January 2008 - 04:43 AM

[PassingBy]

Hmmm .....

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

Rgds

[zonar]

PassingBy, on Jan 6 2008, 11:03 AM, said:

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

This post has been edited by zonar: 07 January 2008 - 01:15 PM

[babybee]

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

[risk_reversal]

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

[Xeno86]

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

[dencorso]

risk_reversal, on Feb 18 2008, 01:42 PM, said:

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!

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.

This post has been edited by dencorso: 25 May 2009 - 10:18 PM

[bizzybody]

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)

[risk_reversal]

Quote

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

This post has been edited by risk_reversal: 19 February 2008 - 05:58 AM

[dencorso]

risk_reversal, on Feb 19 2008, 08:56 AM, said:

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.

This post has been edited by dencorso: 20 February 2008 - 12:28 AM