[dencorso]

Yes, it is. There are some versions for languages other than English here, although no Swedish version that I know of, sorry.

[Svenne]

Oh
Can I translate it myself?

[M()zart]

I have a problem with my digital photo camera Canon Powershot SX120IS. It is detected when I plug it in, the system searches for the driver but does not find the proper one. After installing of NUSB 3.3, it always found the usbstor.inf for all USB devices except for this camera. Any suggestions?

This post has been edited by M()zart: 22 November 2010 - 07:40 AM

[MDGx]

Svenne, on 02 November 2010 - 04:22 AM, said:

Oh
Can I translate it myself?

I'm sure it's possible.
You may wish to contact Maximus-Decim, he is experienced in English + Russian patches, he can probably give you some pointers.

FYI:
You can also compare 2 files of same build but of different languages with a tool like:
- WinDiff [rather primitive] found on your Win98/98SE/ME install CD-ROM and on MS ftp server:
WINDIFF.EXE
GUTILS.DLL (required!)
WINDIFF.HLP
All 3 files above must reside inside the same folder.
- or WinMerge [better features] (free GPL).
to see the actual differences for different languages.
Then you can translate the text strings into the language of your choice [copy & paste from the file using a hex editor, or use Resource Hacker to save the text strings as separate files], and finally, you can replace those text strings into the file using Resource Hacker (freeware).
Make sure you update the version + language information in Resource Hacker so it will display the new language properly.
After finished with all changes, it is advised to re-check and re-build (if necessary) the file checksum (digital signature), using one if these tools [free(ware)].

That's it. ;-)
I know it's a lot of work, but it is probably the only way, for files that MS did not issue specific languages fixes for.

HTH

[Lipper]

I've installed the SP and driver for 98FE. All seemed to go well with the install but the system doesn't show the Maxtor 3200 drive in my computer, all I get is the Unplug/Eject Hardware indicator in the system tray.

Any thoughts where to start looking for problems?

[Lipper]

OK I figured it out. I needed Paragon NTFS for Windows 98 to see the NTSF volume.

Thanks for this site. After two weeks I'm finally getting somewhere with this 98FE system.

[M()zart]

I have two questions.

How can I completely uninstall NUSB (for example, to try older version)?
Does NUSB support any PCI USB 2.0 controller card or should I avoid some of them?

[LoneCrusader]

A Proposal/Suggestion for the Expansion of NUSB

Hello, maximus-decim!
My compliments on a great package for 98SE.

I have a suggestion for a small "expansion" of NUSB, and I'd appreciate your thoughts on it.

As some of you may know from other threads I have been working for a while now on building myself a "slipstreamed" installation of Windows 98SE. Over the past few days I have been working with getting NUSB integrated into my installation and I have made a couple of discoveries that I believe are relevant.

Other threads relevant to this discussion:
Some of you may also be familiar with RetroOS's thread about getting a USB Composite Device working in 98SE with NUSB (and in his case 98SE2ME.) And with Tihiy's thread that originated the USB2.0 stack for 9x.
Do not install the USB20DRV package from this thread, it is listed here for reference in this situation only!

After I had successfully integrated NUSB into my slipstream, I browsed through these threads for any relevant information about any further USB-related updates that I might integrate. After reading RetroOS's thread, I decided to take a look at USBCCGP.SYS. RetroOS stated that the Windows ME version of this file did not work for him. He searched for a 98SE and a Win2K equivalent of this file, and they do not use this file. Windows XP does, however. He went on to get various XP versions of this file to work on his system.

In his case, 98SE2ME had copied the Windows ME version of USB.INF to his system, renamed to USBME.INF. This Windows ME .INF file calls for USBCCGP.SYS, and the combination of the Windows ME .INF and the Windows XP USBCCGP.SYS allowed him to get his device working.

dencorso suggested in that thread that it might be possible to "merge" the 98SE and ME USB.INF's into a single file. In my case(for slipstreaming purposes), I needed to do this, so I did so. Now my custom USB.INF would call for and properly install USBCCGP.SYS.

The next step was to examine the various versions of USBCCGP.SYS available. Keeping in mind that:
1.) the ME version did NOT work for RetroOS
2.) rloew had also informed me that he had trouble with the ME version of this file

I tested the following versions on my 98SE system with the WDMCHECK utility:

Windows ME (4.90.3000.1)
XP RTM (5.1.2600.0)
XP SP3 (5.1.2600.5512)
XP KB945436 (5.1.2600.5585)

ALL versions of USBCCGP.SYS have missing functions on Windows 98SE. BUT - they are missing DIFFERENT functions.

The Windows ME version is missing the following functions:
IoFreeWorkItem
IoAllocateWorkItem

The Windows XP versions are missing the following functions:
USBD_ParseConfigurationDescriptorEx
USBD_CreateConfigurationRequestEx


Now, the missing functions of the Windows ME version MAY POSSIBLY be corrected by adding WDMSTUB.SYS that was previously a part of this package in an earlier version. However, the Windows ME version is documented to have problems.


Here's where it gets interesting. The missing functions of the Windows XP USBCCGP.SYS can be solved by using the Windows ME version of USBD.SYS instead of the 98SE version. In RetroOS's case, as he had installed 98SE2ME, he had the ME USB.INF and the required ME USBD.SYS, so it worked.


So here's the proposal. I feel that it would be a good idea to add the Windows ME USB 1.1 Driver Stack to NUSB along with the XP USBCCGP.SYS to expand its capabilities. It would involve adding the following files:

ME RTM:
OPENHCI.SYS 4.90.3000.1
UHCD.SYS 4.90.3000.1
USBD.SYS 4.90.3000.1

ME Q278289:
USBHUB.SYS 4.90.3002.1

XP KB945436:
USBCCGP.SYS 5.1.2600.5585

And a "merged" USB.INF file combining the contents of 98SE's USB.INF and ME's USB.INF.
I have attached a copy of the one I made in case anyone wants to examine it.
If you plan to test this you must remove ALL USB devices from the Device Manager FIRST!
NOTE that to add it to a package it will need the "LayoutFile=" line removed and sections added for [SourceDisksNames] and [SourceDisksFiles] like USB2.INF in NUSB has.

I believe that this addition would provide the best USB 1.1 and 2.0 support available for 98SE.

I have tested installing these files in a VM, and everything goes smoothly, and WDMCHECK on that install reports no missing functions with any of those files. But I do not have a large selection of USB devices to test it more thoroughly.

I welcome any comments or questions, I'll try to answer them as best I can.

Attached File(s)

•  USBINF.ZIP (5.5K)
  Number of downloads: 19

This post has been edited by LoneCrusader: 01 August 2011 - 04:26 AM

[PROBLEMCHYLD]

LoneCrusader, on 31 July 2011 - 02:13 AM, said:

After I had successfully integrated NUSB into my slipstream

How did you do this?

I do think USB2.0 stack for 9x + NUSB should be combine as 1 updated usb pack for Win9X systems.

[LoneCrusader]

PROBLEMCHYLD, on 31 July 2011 - 06:31 AM, said:

How did you do this?

I have a special set of Slipstreaming Tools I purchased from RLoew. It allows me to Change/Add/Remove files in the CABs.

[dencorso]

LoneCrusader, on 31 July 2011 - 02:13 AM, said:

A Proposal/Suggestion for the Expansion of NUSB

Hi, Maximus-Decim!

This post is just to say I support LoneCrusader's proposal. I do think that, with the current widespreading of USB Mouse/Keyboard combos, USBCCGP.SYS is a needed addition to NUSB, and the USB Printer support is equally welcome.

[Drugwash]

Not yet. This needs further testing.

Today I made a second attempt at installing the USB 2.0 stack together with all other system files recommended in post #628. Upon reboot(s), the USB Root Hub entries for the on-board USB 1.1 failed to load the drivers (NTKERN.VXD could not load the drivers for this device). Tried reinstalling drivers, removing and rebooting, etc. to no avail.

Upon uninstalling USB 2.0 stack and restoring system files from backup, the machine locked up. Tried a couple reboots - same result. Safe mode did work but wouldn't fix anything, so after a few failed boots I had to restore the registry from the most recent valid backup, at which point the machine got back to a working state.

This 98SE installation is 5 years old and lived through countless alpha tests, crashes and other mishappenings but only once or twice was I forced to actually restore the registry to get it back afloat, so I'd say there might be something fishy with this package, since it breaks the 1.1 controller and then corrupts the registry upon uninstallation. Or am I Mr. BadLuck?

This post has been edited by Drugwash: 31 July 2011 - 06:43 PM

[dencorso]

You mean this: USB20DRV.EXE? Well, it's complicated... But it sure has problems.
But it does contain some really interesting executables, some of which I'm using right now. I think the problem still lies in the .inf.
Your machine has USB 2.0 and works OK with NUSB 3.3, is that right? If so, we can work it by hand at installing that update, without using the inf, and you'll see it does work. One more question however, is your machine's southbridge a Via chip? Or are you using a USB add-on card based on a Via chip?

[LoneCrusader]

Drugwash, on 31 July 2011 - 06:41 PM, said:

Not yet. This needs further testing.

Today I made a second attempt at installing the USB 2.0 stack together with all other system files recommended in post #628. Upon reboot(s), the USB Root Hub entries for the on-board USB 1.1 failed to load the drivers (NTKERN.VXD could not load the drivers for this device). Tried reinstalling drivers, removing and rebooting, etc. to no avail.

Upon uninstalling USB 2.0 stack and restoring system files from backup, the machine locked up. Tried a couple reboots - same result. Safe mode did work but wouldn't fix anything, so after a few failed boots I had to restore the registry from the most recent valid backup, at which point the machine got back to a working state.

This 98SE installation is 5 years old and lived through countless alpha tests, crashes and other mishappenings but only once or twice was I forced to actually restore the registry to get it back afloat, so I'd say there might be something fishy with this package, since it breaks the 1.1 controller and then corrupts the registry upon uninstallation. Or am I Mr. BadLuck?

Did you try to install USB20DRV directly on top of NUSB 3.3?

USB20DRV has some bugs (sorry MDGx )

USB20DRV downgrades USBHUB20.SYS, which should only be done on boards with VIA Chipsets. This should be a stand-alone installer for that one file.

The way USB20DRV handles WDMSTUB.SYS doesn't work either, it should only be loaded by USBSTOR.INF as described in that thread by dencorso, not loaded with the USB2.INF & drivers.


Also, did you remove ALL USB devices from the Device Manager before attempting this? This is a requirement, as we are changing both the INF and the driver.

I probably should have made a note of stating that, but as removing all USB devices is required for installing NUSB, and this was meant to be added to NUSB, I didn't think about it...

This post has been edited by LoneCrusader: 31 July 2011 - 08:16 PM

[Drugwash]

Sorry for the delay - just woke up minutes ago.

@dencorso: Yes, that's the package.I had downloaded it on July 22nd. Let's clear up the hardware:
- motherboard Soyo SY-6VBA 133
- chipset VIA VT82C693A (Apollo Pro 133)
- on-board USB 1.1 UHCI controller VIA VT82C596B
- PCI adapter with USB 2.0 EHCI controller VIA VT6202

Both USB controllers have been working correctly with NUSB33 (and previous versions, back at the time).

@LoneCrusader: Yes, I did install the USB 2.0 Stack package on top of NUSB33, primarily because I was in a hurry and secondly - and most important, IMO - because such upgrade should be compeltely transparent to the user, that is it should require absolutely no prior uninstall/tweaking of other system services or whatnot, since not all potential users are knowledgeable.
As such, I have not removed any of the USB devices that appear in Device Manager, especially because I have other USB related problems (one USB stick doesn't get assigned a drive letter and the brand new bluetooth USB adapter got VID & PID zeroed out) that I probably will elaborate on some other occasion and I was afraid that particular stick wouldn't be recognized anymore (which happened previously).

The files I added manually right after installing USB20DRV were:
- openhci.sys 4.90.3000.1
- uhcd.sys 4.90.3000.1
- usbccgp.sys 5.1.2600.5512 (from XP-SP3)
- usbd.sys 4.90.3000.1
- usbhub.sys 4.90.3002.1
- usbser.sys 5.1.2600.5512 (from XP-SP3)

I believe the issue with Composite devices is deeper than it may seem, since the class doesn't appear to be registered on a normal 98SE system and probably other changes and system files may be required as well. But for the time being I'm not gonna dig into this, as I got other important work to do (dencorso knows).

[LoneCrusader]

Drugwash, on 01 August 2011 - 04:06 AM, said:

@LoneCrusader: Yes, I did install the USB 2.0 Stack package on top of NUSB33, primarily because I was in a hurry and secondly - and most important, IMO - because such upgrade should be compeltely transparent to the user, that is it should require absolutely no prior uninstall/tweaking of other system services or whatnot, since not all potential users are knowledgeable.
As such, I have not removed any of the USB devices that appear in Device Manager, especially because I have other USB related problems (one USB stick doesn't get assigned a drive letter and the brand new bluetooth USB adapter got VID & PID zeroed out) that I probably will elaborate on some other occasion and I was afraid that particular stick wouldn't be recognized anymore (which happened previously).

...

I believe the issue with Composite devices is deeper than it may seem, since the class doesn't appear to be registered on a normal 98SE system and probably other changes and system files may be required as well. But for the time being I'm not gonna dig into this, as I got other important work to do (dencorso knows).

I agree with you that the updates should be transparent, I didn't intend for anyone to grab the USB20DRV package and use it in this situation. I listed the thread as relevant because it had some further information not in the "Composite Device" thread. This was meant to be strictly an addition to NUSB.

As I stated above, 98SE and Win2K do not have an equivalent of USBCCGP.SYS. They use USBHUB.SYS or USBHUB20.SYS for composite devices. What I have done is based strictly on RetroOS's discovery (and the fact that he was using ME files enabled him to do it.)

It works perfectly here on a VM, but I don't have a bunch of USB devices to test it with. I was (and still am) a 95-lover for many years and as such had an extreme dislike for USB devices. Even now I only have flash drives.



Edit:
Added warnings to the previous post.

This post has been edited by LoneCrusader: 01 August 2011 - 04:27 AM

[PROBLEMCHYLD]

Is it possible to add this hotfix to the list?
WindowsXP-KB934428-v3-x86-ENU.exe

[dencorso]

Drugwash, on 01 August 2011 - 04:06 AM, said:

- usbser.sys 5.1.2600.5512 (from XP-SP3)

Well, Drugwash, IMO what blorked your system was the .inf inside USB20DRV. Of course the files it contains are OK for your system, provided USBSTOR.INF is edited to load WDMSTUB.SYS with USBSTOR.SYS. Now, adding the untested (AFAIK) USBSER.SYS from XP SP3 didn't help any, either. Fact is, I tested it with WDMCHECK.EXE, and it turns out to have the same 3 unsatisfied dependencies that the USBSTOR.SYS (v. 5.0.2195.6773) from USB20DRV has. On the bright side it means it should work, provided it's also loaded with WDMSTUB.SYS, and this means finding the .inf that sets its registry entry and editing it too. The downside is it may be more than one .inf... USBSER.SYS is for the USB virtual serial port, which is mostly used to support USB modems, AFAIK. Here's a screenshot of WDMCHECK's output:

Attached File(s)

•  USBSER.jpg (34.06K)
  Number of downloads: 24

[PROBLEMCHYLD]

The best thing to do, would be combine all the inf files + system files (the best stable files everyone agrees on)
from NUSB.EXE + USB20DRV.EXE and using the latest USBSTOR.INF in post #602 in this topic
then maybe we can go from there.

_NUSB.INF
_USB2UN.INF
1394.INF
NODRIVER.INF
NTMAP.INF
USB2.INF
USBNTMAP.INF
USBSTOR.INF
USB20DRV.INF

This post has been edited by PROBLEMCHYLD: 07 August 2011 - 02:58 AM

[maximus-decim]

Maximus Decim Native USB ver.3.5
------------------------------------------------------------------------
*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.5 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://www.zshare.ne...4510417a4f04d9/
Russian: http://www.zshare.ne...4510631daab5ad/

What's new?
*OPENHCI.SYS 4.90.3000.1
*UHCD.SYS 4.90.3000.1
*USBD.SYS 4.90.3000.1
*USBHUB.SYS 4.90.3002.1
*USBCCGP.SYS 5.1.2600.5585
*USB.INF 01.01 ( LoneCrusader)
*USBSTOR.INF 01.10dt (dencorso, add new devices)
*USB2.INF 01.01 (MD, add new devices)