[dencorso]

What we failed to say, though, is that User.exe 4.10.2231 - Q291362 and IOS.VXD 4.10.2225 - Q239696 are not fundamental for the correct functioning of NUSB, AFAIK, so that if sorbit4 makes a backup of his current Hungarian versions and then replaces, in DOS, those files added by NUSB by those Hungarian version backups, chances are it'll still work OK. It's not really quite a long shot.

[sorbit4]

LoneCrusader, on 22 April 2012 - 10:56 PM, said:

dencorso, on 22 April 2012 - 06:52 PM, said:

I did check that before replying.
The hotfixes are there, all right, but there simply are *no* Hungarian versions for those two.
I wouldn't have been as assertive as I did in my previous post, if I hadn't.

I figured that you had probably checked.
I was in the process of pulling that breakdown out of my slipstream notes when you posted, and once I had gone to the trouble of extracting it, I thought I would go ahead and post it, it may be of future use. Myself having never checked for other language versions, I figured sorbit4 could give it a shot...

I will try it. But before installing, I want know what is your opinion about R. Loew general USB Mass storage driver. Is it good for pendrives too? Is anybody tested it?
It is quite small Ithink it does not bother the system messages.

[LoneCrusader]

sorbit4, on 23 April 2012 - 01:22 AM, said:

I will try it. But before installing, I want know what is your opinion about R. Loew general USB Mass storage driver. Is it good for pendrives too? Is anybody tested it?
It is quite small Ithink it does not bother the system messages.

I have not personally used that particular package, but I have many other packages and updates created by R. Loew. You can rely on anything he distributes to be high quality.

This, combined with your Intel USB2 drivers you mentioned before, may be a working alternate solution if you are unable to localize NUSB.

This post has been edited by LoneCrusader: 23 April 2012 - 01:30 AM

[Foxbat]

sorbit4, on 23 April 2012 - 01:22 AM, said:

I want know what is your opinion about R. Loew general USB Mass storage driver. Is it good for pendrives too?

Yes, Rloew's very tiny USB Mass Storage Driver works on pen drives. It lacks the sophistication of NUSB, such as the ability to handle multi-card readers.

[sorbit4]

Foxbat, on 23 April 2012 - 09:49 PM, said:

sorbit4, on 23 April 2012 - 01:22 AM, said:

I want know what is your opinion about R. Loew general USB Mass storage driver. Is it good for pendrives too?

Yes, Rloew's very tiny USB Mass Storage Driver works on pen drives. It lacks the sophistication of NUSB, such as the ability to handle multi-card readers.

Thank for the info. I tried R.Loew tiny driver. It works altogh the pen drive recognition is quite funny. Every time when you plug in a new pendrive, you must point to the inf file.
It does not use the system tray, but it can be used so I will remain with it. But I was suprised that Intel did not make USB2.0 for Win98Se (only USB1.1). The data transfer is quite slow.

[dencorso]

Ofcourse it did, and all its SouthBridges, since ICH4 do include USB 2.0 hardware support. You, however, need an USB 2.0 stack to use it. I'm positive Intel did release drivers for USB 2.0 under 98SE. Were it a Via SouthBridge, I'd already have pointed you to the right package, but I'm much less familiar with older Intel drivers.

[LoneCrusader]

dencorso, on 24 April 2012 - 12:05 PM, said:

I'd already have pointed you to the right package, but I'm much less familiar with older Intel drivers.

Never fear, lol, almost all (95%+) of my hardware is Intel Chipset based. We will get to the bottom of this!

sorbit4, on 24 April 2012 - 11:20 AM, said:

But I was suprised that Intel did not make USB2.0 for Win98Se (only USB1.1). The data transfer is quite slow.

I thought you said you had Intel USB 2.0 Drivers, because you asked if you should uninstall them when you first asked about NUSB?

If your Intel USB2 driver package works like the one I have, when you run the "installer" it doesn't really install anything.
All it does is extract itself to C:\WINDOWS\DRIVERS\. This is, shall we say, less than helpful. If it extracted itself to C:\WINDOWS\INF\, it would be useful, but I digress.

Go into your Device Manager and see if your USB2 hubs are properly recognized. If they show up as unknown devices, remove them, and reboot. When asked for the location of the driver, point the installer to C:\WINDOWS\DRIVERS\ or wherever your package has extracted itself.

[sorbit4]

LoneCrusader, on 24 April 2012 - 04:30 PM, said:

sorbit4, on 24 April 2012 - 11:20 AM, said:

But I was suprised that Intel did not make USB2.0 for Win98Se (only USB1.1). The data transfer is quite slow.

I thought you said you had Intel USB 2.0 Drivers, because you asked if you should uninstall them when you first asked about NUSB?
If your Intel USB2 driver package works like the one I have, when you run the "installer" it doesn't really install anything.
All it does is extract itself to C:\WINDOWS\DRIVERS\. This is, shall we say, less than helpful. If it extracted itself to C:\WINDOWS\INF\, it would be useful, but I digress.
Go into your Device Manager and see if your USB2 hubs are properly recognized. If they show up as unknown devices, remove them, and reboot. When asked for the location of the driver, point the installer to C:\WINDOWS\DRIVERS\ or wherever your package has extracted itself.

Now I know that I was failed. I never knew why was an unknown PCI USB controller device in the Device Manager list, altough there were normally listed the Intel USB controllers and hubs.Because the hardware is USB2.0 capable, I thought that the driver is too. I installed the R.Low driver and I detected the slow speed with a pen drive. Then I realised that the driver is only for USB1.1. Today I began to search for a USB2.0 (orange) driver and then installed it. Then the USB2 controller device is uppaered in the Dev. Man. list and the unknonwn device is disappeared. But the transfer speed does not changed. I thought that the R. Low driver connected itself with the USB1.1 driver because when it was installed, there was not USB2.0 controller driver. I do not know how to uninsta it, so I decided to uninstall the Win98SE then install again with the hardware drivers first (with the orange driver) and then the R. Low driver. Now is everithing is ok. The pendrive is identified as USB2.0 Mas Storage Device and the trasfer speed is sinificantly improved.
Ps. Now I read the readme of Intel. So you are right. I should delete the Unknown PCI to USB Host Controller. I was missed because I run the setup. Maybe Intel has USB2.0 driver for Win98SE?

This post has been edited by sorbit4: 25 April 2012 - 02:31 PM

[LoneCrusader]

sorbit4, on 25 April 2012 - 02:11 PM, said:

Now I know that I was failed. I never knew why was an unknown PCI USB controller device in the Device Manager list, altough there were normally listed the Intel USB controllers and hubs.Because the hardware is USB2.0 capable, I thought that the driver is too. I installed the R.Low driver and I detected the slow speed with a pen drive. Then I realised that the driver is only for USB1.1. Today I began to search for a USB2.0 (orange) driver and then installed it. Then the USB2 controller device is uppaered in the Dev. Man. list and the unknonwn device is disappeared. But the transfer speed does not changed. I thought that the R. Low driver connected itself with the USB1.1 driver because when it was installed, there was not USB2.0 controller driver. I do not know how to uninsta it, so I decided to uninstall the Win98SE then install again with the hardware drivers first (with the orange driver) and then the R. Low driver. Now is everithing is ok. The pendrive is identified as USB2.0 Mas Storage Device and the trasfer speed is sinificantly improved.
Ps. Now I read the readme of Intel. So you are right. I should delete the Unknown PCI to USB Host Controller. I was missed because I run the setup. Maybe Intel has USB2.0 driver for Win98SE?

I'm glad to hear you're up and running at USB2.0 speeds.

I'm not sure what you mean by this however

Quote

Maybe Intel has USB2.0 driver for Win98SE?

Do you mean the drivers you just installed, or do you mean a Mass Storage Device driver?

[PROBLEMCHYLD]

dencorso,

Whenever you have some free time can you update USBSTOR.INF with the updates from the link below?
Here are some new devices that can be added hopefully.
http://www.msfn.org/...post__p__985810

;
; EUIOSSM.INF --- SCM Microsystems Inc Win9x USB SmartMedia Port Driver INF
;
; Copyright (C) SCM Microsystems Inc 1998-1999
;

[Version]
signature="$CHICAGO$"
Class=SCMUsbMass
Provider=%SCM%

[ClassInstall]
AddReg=SCMUsbMass.AddReg

[SCMUsbMass.AddReg]
HKR,,,0,%SCMUsbMass%
HKR,,Icon,0,-20

[Manufacturer]
%SCM%=SCM

[SCM]
%USB_PDR.DeviceDesc% = euiossm, *PSCMEUSBSMPDR

[DestinationDirs]
DefaultDestDir = 12

[SourceDisksNames]
1=%DISK1%,,

[SourceDiskFiles]
euiossm.pdr=1

[euiossm]
AddReg = euiossm.AddReg
CopyFiles = euiossm.CopyFiles

[euiossm.CopyFiles]
euiossm.pdr

[euiossm.AddReg]
HKR,,DevLoader,,*IOS
HKR,,PortDriver,,euiossm.pdr

[Strings]
SCM="SCM Microsystems"
SCMUsbMass="USB Port driver"
DISK1="eUSB Driver Disk"
USB_PDR.DeviceDesc="eUSB MSD Adapter"


;
; EUSBSM.INF - INF file for SCM Microsystems Inc eUSB SM Products
;
; Currently defines eUSB SSFDC
; 
; Copyright (C) SCM Microsystems Inc. 1998-2000
;

[Version]
signature="$CHICAGO$"
Class=USB
ClassGUID={36FC9E60-C465-11CF-8056-444553540000}
Provider=%SCM%

[DestinationDirs]
DefaultDestDir = 11; // LDID_SYS
EUsbSm.CopyFiles = 11; // %windir%\system
UsbPdr.CopyFiles = 12; // %windir%\system\iosubsys
PdrInf.CopyFiles = 10, INF\OTHER;

[SourceDisksNames]
1=%DISK1%,,

[SourceDiskFiles]
eusbsm.sys=1
euiossm.pdr=1
euiossm.inf=1

[Manufacturer]
%SCM%=SCM.Section

[SCM.Section]
%USB\VID_04E6&PID_0003.DeviceDesc%=EUsbSm.Dev, USB\VID_04E6&PID_0003

[Start]
HKLM,Software\Microsoft\Windows\CurrentVersion\RunOnce\Setup,%Startup%,,"%01%\..\LAUNCH.EXE" 

[EUsbSm.Dev]
AddReg = EUsbSm.AddReg,Start
CopyFiles = EUsbSm.CopyFiles, UsbPdr.CopyFiles, PdrInf.CopyFiles

[EUsbSm.AddReg]
HKR,,DevLoader,0,*ntkern
HKR,,NTMPDriver,0,eusbsm.sys

[EUsbSm.CopyFiles]
eusbsm.sys

[UsbPdr.CopyFiles]
euiossm.pdr

[PdrInf.CopyFiles]
euiossm.inf

[Strings]
SCM="Microtech International"
USB\VID_04E6&PID_0003.DeviceDesc="ZiO SmartMedia Adapter"
DISK1="eUSB Driver Disk"
Startup="Installing"

[sorbit4]

LoneCrusader, on 25 April 2012 - 11:59 PM, said:

sorbit4, on 25 April 2012 - 02:11 PM, said:

Now I know that I was failed. I never knew why was an unknown PCI USB controller device in the Device Manager list, altough there were normally listed the Intel USB controllers and hubs.Because the hardware is USB2.0 capable, I thought that the driver is too. I installed the R.Low driver and I detected the slow speed with a pen drive. Then I realised that the driver is only for USB1.1. Today I began to search for a USB2.0 (orange) driver and then installed it. Then the USB2 controller device is uppaered in the Dev. Man. list and the unknonwn device is disappeared. But the transfer speed does not changed. I thought that the R. Low driver connected itself with the USB1.1 driver because when it was installed, there was not USB2.0 controller driver. I do not know how to uninsta it, so I decided to uninstall the Win98SE then install again with the hardware drivers first (with the orange driver) and then the R. Low driver. Now is everithing is ok. The pendrive is identified as USB2.0 Mas Storage Device and the trasfer speed is sinificantly improved.
Ps. Now I read the readme of Intel. So you are right. I should delete the Unknown PCI to USB Host Controller. I was missed because I run the setup. Maybe Intel has USB2.0 driver for Win98SE?

I'm glad to hear you're up and running at USB2.0 speeds.

I'm not sure what you mean by this however

Quote

Maybe Intel has USB2.0 driver for Win98SE?

Do you mean the drivers you just installed, or do you mean a Mass Storage Device driver?

Today I was learning some new things. Installing again the Win98SE. I tryed the method that Intell proposed, but only USB1.1 installed and there remained the Unknown PCI to USB Host Controller in the Dev. Man. list altough I tried to delete it and leaved the system to recognize it. When I installed the ECS Intel OrangeWare ICH5 USB 2.0 Driver (only this was good for USB2.0 speed), the USB2 Controller and Hub installed and everything was OK (there was no unknowed device). At last I installed the R.Loew's USB Mass Storage driver. It works at USB2.0 speed. So the aswer is: Intel has no Win98SE USB2.0 driver for his ICH5 chip (only for USB1.1).

This post has been edited by sorbit4: 26 April 2012 - 12:42 PM

[PROBLEMCHYLD]

Updated USBSTOR.INF

Sweex 16-in-1 card reader
Sony PSP
Myson-Century
Cypress Semiconductor
IOMagic Multicard Reader
Realtek USB 2.0 Card Reader

Removed obsolete Windows NT entries

[maximus-decim]

Maximus Decim Native USB ver.3.6
------------------------------------------------------------------------
*Native (without installation of additional drivers for each type) support USB flash drives, digital photo
and videocameras and other similar devices.
*Universal Stack USB 2.0 (without installation of additional drivers for each chipsets) with uninstall.
1.Remove ALL drivers USB flash drives.
2.Remove ALL drivers USB 2.0 controllers.
3.Remove ALL USB 1.1 and 2.0 controllers and devices.
4.Remove ALL unknown devices.
5.Install NUSB 3.6 and reboot.
6.After detection new USB 1.1 and 2.0 controllers (if it will occur) too it is necessary to reboot.
Remember! You install it at own risk!
-----------------------------------------------------------------------------------------------------------------------
English: http://turbobit.net/tyu37wycpmde.html
https://rapidshare.c...514/nusb36e.exe
Russian: http://turbobit.net/dhgujel1bonm.html
https://rapidshare.c...231/nusb36r.exe
What's new?
* SYSDM.CPL 4.90.3001 - for auto install driver at insertion of the new flash devices
*USB.INF 01.02 (MD, exclude "CopyFiles" sections )
*USB2.INF 01.02 (MD, add new devices (Intel, ATI), exclude "CopyFiles" sections)
*NTMAP.INF 01.01 (MD, exclude "CopyFiles" sections )
*USBNTMAP.SYS 01.03 (MD, exclude "CopyFiles" sections )
*USBSTOR.INF 01.11a (MD, Problemchyld, add new devices, exclude "CopyFiles" sections )
*QV2KUX.SYS - (Problemchyld, for Casio)

This post has been edited by maximus-decim: 04 June 2012 - 12:33 PM

[Drugwash]

Nice to see you back!

Got one small issue: some of us have a customized Device Manager applet (mine dates back 2006 when I installed the system). There's no warning and/or backup option in the package about its replacement, if I'm not mistaken. Those who get the package from third-party sources (copied from a friend, whatever) will definitely miss the tiny mention in the changelog posted here at MSFN.

Therefore, could you please add to the package (at install time) a visible warning that the Device Manager applet will be replaced, so anyone installing the package could get a chance to backup the old one?

Other than that, thank you for the update!

[PROBLEMCHYLD]

I can't download the file. It says

Our service is currently unavailable in your country.
Sorry about that.

[bphlpt]

Try again PROBLEMCHYLD, maximus-decim added rapidshare links which work in the US just fine.

Cheers and Regards

[PROBLEMCHYLD]

Thanks

[PROBLEMCHYLD]

There is a typo in USB2.INF.

[WMVARE]
%PCI\VEN_15AD&DEV_0770.DeviceDesc%=EHCI,PCI\VEN_15AD&DEV_0770

It should read

[VMWARE]
%PCI\VEN_15AD&DEV_0770.DeviceDesc%=EHCI,PCI\VEN_15AD&DEV_0770

I have already fixed the issuse for SP3. Thanks for the update

This post has been edited by PROBLEMCHYLD: 08 June 2012 - 10:24 AM

[submix8c]

@PROBLEMCHYLD -

Vee know vhat vee are doing, don't vee? (BWAHAHAH!)

Thanks for the updates, all!

[PROBLEMCHYLD]

@ maximus-decim

To get the Casio USB devices to work, you need these two files.

USBDSC1.SYS 4.10.0.1998
USBDSC2.VXD 4.0.0.950

You can find the two files in a package googling

casio usb_win.exe

All you have to do is add the code below to your USBSTOR.INF.
You can remove QV2KUX.SYS 1.0.0.2000. Thanks again for the update.

[Manufacturer]
%Casio.Mfg%=Casio

[Casio]
%USB\VID_07CF&PID_1001.DeviceDesc%=USBDSC1,USB\VID_07CF&PID_1001

[USBDSC1.AddReg]
HKR,,DevLoader,,*NTKERN
HKR,,NTMPDriver,,USBDSC1.SYS
HKLM,"System\Currentcontrolset\Services\usbdsc1\Parameters","Install",0x10001,77
HKLM,"System\Currentcontrolset\Services\usbdsc1\Parameters","DiskMakeFirstInstallDelay",0x10001,3000
HKLM,"System\Currentcontrolset\Services\usbdsc1\Parameters","DiskMakeOtherDelay",0x10001,300

[Strings]
Casio.Mfg="Casio"
USB\VID_07cf&PID_1001.DeviceDesc="USB-CASIO DIGITAL CAMERA"

This post has been edited by PROBLEMCHYLD: 12 June 2012 - 02:35 PM