Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


maximus-decim

Maximus-Decim Native USB Drivers

Recommended Posts

I understand that, after disabling USB emulation in the BIOS, just one letter is assigned to each drive, albeit the order changes depending on whether the pendrive is inserted in one of the USB connectors or not. So, IMO, nothing further needs to be done, at the moment... am I mistaken?

Share this post


Link to post
Share on other sites

I have now followed jumper's suggestion to disable USB emulation in the bios. That solves the problem: It now comes up in a perfectly normal amount of time even with a flash drive installed. If the flash drive is in place then it comes up with that drive at D and the CD at E -- the reverse of what happens if the flash drive is installed after booting. Again, many thanks!

Maybe useful, maybe not, something now lost in the midst of time, Letter Assigner:

http://www.msfn.org/board/topic/118623-how-to-create-easily-a-second-win98xp-in-the-same-computer/?p=826574

jaclaz

Share this post


Link to post
Share on other sites

First -- dencorso -- the problem I had (couldn't leave a USB flash device plugged in and bring up Win 98) was fully solved by disabling 'USB Controllers' in the BIOS and nothing more needs to be done for that. I can live with the fact that the CD drive gets a different letter depending on whether the flash drive is installed or not.

I did not know about Letter Assigner; I found and downloaded a copy by following the Wayback link. Don't need it now, but I long ago gave up trying to decide what software I would never ever need. That's why I have NUSB, actually, and from fairly early days -- 3.0 at least. That one is on my 98SE2ME laptop and I think I have 2.x saved somewhere.

On to the NEXT problem on this DELL 2400/Win 98SE machine. Since this machine was never supported by Dell for Win 98 this has been interesting and I may write it up as member project if no one else has done so.

(Now that 98SE is fully working the next step on that machine is getting a truly awful -- but interesting -- game card to play, 'just because.' This is a Riptide 90079-2 -- sound, joystick, MIDI, and modem in one PCI slot, apparently only OEM in a bunch of Win 98 HP machines. I have all the drivers but my first attempt was killed by an excess of IRQ conflicts and I have a lot to learn about solving those. One thing I learned from this thread was the use of Safe Mode to get complete reporting from Device Manager.)

I very much appreciate the educational material, especially rloew's tutorial which clarified much. I was aware that having two views of the same device could be fatal so I did nothing to cause a write to that device.

I am curious about exactly what was going on during the near-hour long process of Windows coming up (when the BIOS USB support was enabled). If I understand correctly, DOS takes the BIOS info but Windows still discovers the device on its own and with no coordination, you get two routes to the same one. But -- why did this take so long? For some reason this brings to mind:

"But they argued all night,

o'er which had the right

to do what with which,

and to whom."

As I see things I now have ONLY the Windows view, which on this machine is plenty quick.

Edited by waltah

Share this post


Link to post
Share on other sites

I am curious about exactly what was going on during the near-hour long process of Windows coming up (when the BIOS USB support was enabled). If I understand correctly, DOS takes the BIOS info but Windows still discovers the device on its own and with no coordination, you get two routes to the same one. But -- why did this take so long?

I suspect it was reading the whole FAT table using slow USB 1.1 protocol. Or something like that. When my Windows 98 computer with USB 1.1 worked, it always froze when I accessed USB drive the first time after boot, and USB drive light blinked meaning that the read operation was performed. The time of the freezing depended on the size of the drive. 4 GB usb flash stick froze my computer for less than a minute, 16 Gb flash stick froze it for about 3.5 minutes, and 320 GB USB HDD - for about 10 minutes or more. I didn't overcome this problem. What is the size of your drive?

Share this post


Link to post
Share on other sites

HELP!!! All was working great with the Win98SE2ME patches until I tried to connect an external SATA drive. (SATA -> USB 2.0)

First, I got "MSGSRV32 caused an error in SETUPX.DLL" which then occurred when connecting any device.

The last time that happened I re-installed Win98SE from scratch.

This time, I just restored the last working copy of the registry and the device driver for one of my generic USB flash drives.

Now all FLASH devices work (Generic Sticks, PNY Attache, BENQ JoyBee, etc.)

BUT... When I connect *any* external hard drive I get "RUNDLL32 has caused an error in COMMCTRL.DLL"

After that happens, I cannot access *any* file on *any* drive from Explorer; it just hangs until I reboot (OK from DOS prompt)

I have tried restoring the COMMCTRL.DLL from Win98SE but the same thing happens.

Please advise ASAP!

Here is the error message:

MSGSRV32 caused a general protection fault

in module COMMCTRL.DLL at 0001:00000239.

Registers:

EAX=1c470090 CS=1c47 EIP=00000239 EFLGS=00000246

EBX=00000000 SS=1e87 ESP=00007136 EBP=80f27146

ECX=00000090 DS=1c07 ESI=00030058 FS=0000

EDX=00003b76 ES=3b76 EDI=00030000 GS=018f

Bytes at CS:EIP:

8e c1 8b 46 06 26 39 47 12 0f 87 03 00 e9 cf ff

Stack dump:

00581c07 1a530000 3b760021 00000090 07e0715a 000c1c47 1c070000 00000058 000140f7 0886716a 00001c47 40f70064 00010058 9ebe717a 00003ab7 00580000

Also, the same thing happens when I delete *any* device from the device list and then 'Add new hardware'

After that, the system will not boot properly. (USB device hangs before drawing desktop, LPT1 gets to desktop, gives error message and hangs)

So, definitely a problem with 'Adding Hardware'...

 

 

FYI - I just deleted the contents of Windows/inf/other and got past the error.

 

On one of my machines I also had the above mentioned "RUNDLL32 has caused an error in commctrl.dll" error.

Renaming the folder "other" fixed it but I am wondering what is causing the error ?

If there is a bad inf-file in it is there an easy way to find the culprit or is it necessary to test every one of it ?

Are these files needed anyway ?

 

Thx, MiKl

Share this post


Link to post
Share on other sites

Are there so many inf files in the 'other' folder? My system only has four of them: a bluetooth device, a printer, a webcam and a monitor.

 

The infs only tell the system which driver file(s) to use (although some of them could be malformed and create troubles) but I'm afraid you'll have to work it out by trial and error.

 

Just move or rename all of them, remove the associated devices from Device Manager and then on each reboot add/rename back one file, reboot again, let the system redetect the device and see which one breaks the system. It may be the inf or it may be the actual vxd/sys driver causing the problem.

Share this post


Link to post
Share on other sites

Hi Drugwash, thank you for your reply !! As this system was not broken - in fact it is rock solid - I will go after this issue when I have more time in the way you suggested.

 

@ all.

This may not be the best thread to ask, but the last couple of days I tried to get a cloned-win98se running on a USB-stick and after a couple of trial-and-errors I indeed reached the desktop.

I was, of course, not surprised to see that all drives were in ms-dos-compatibility mode but am wondering if there is a patch around like RLoew's for SATA ??

Share this post


Link to post
Share on other sites

I actually have a question, what does:

[uSBSTOR_BULK.AddReg]
HKR,,DriverFlags,0x00010001,0x00000001

do in USBSTOR.inf?

 

On other USB Mass Storage drivers for 98SE, this registry key is missing.

 

The flashdrives work correctly with and without this registry, so why it is there?

Edited by MrMateczko

Share this post


Link to post
Share on other sites

I actually have a question, what does:

[uSBSTOR_BULK.AddReg]

HKR,,DriverFlags,0x00010001,0x00000001

do in USBSTOR.inf?

 

On other USB Mass Storage drivers for 98SE, this registry key is missing.

 

The flashdrives work correctly with and without this registry, so why it is there?

That entry (along with USBSTOR CB and USBSTOR CBI if present) is to be used for specific Mass Storage Devices that do not correctly report which Mass Storage Protocol they are using. This is most likely a non-issue for any modern device and only a leftover form when the protocol was being developed. I don't know of any devices that actually require it.

You will also find these sections along with a short description of them inside my XUSBSUPP for Windows 95.

Share this post


Link to post
Share on other sites

Is there any reason why this usb package installs the Windows ME version of sysdm.cpl? I'm not too crazy about the system properties displaying "Microsoft Windows Me" when I'm actually using Windows 98 SE.
 

Share this post


Link to post
Share on other sites

Using the ME SYSDM.CPL allows USB Storage Devices to be "autoinstalled" without prompting you to choose the driver and click though the dialog boxes, similar to Windows XP and up. It does however have some unresolved bugs under 98SE. (See this thread where I tried, unsuccessfully, to fix it.)

 

I recommend using NUSB 3.5, as it doesn't change the CPL. You can always manually put back the 98SE version with 3.6 though, as it only affects the specific issue I mentioned.

Share this post


Link to post
Share on other sites
On 17/3/2016 at 5:06 AM, LoneCrusader said:

Using the ME SYSDM.CPL allows USB Storage Devices to be "autoinstalled" without prompting you to choose the driver and click though the dialog boxes, similar to Windows XP and up.
It does however have some unresolved bugs under 98SE. (See this thread where I tried, unsuccessfully, to fix it.

Hi,
This has been solved since 'Unofficial Win98SE SP 3.22': http://www.htasoft.com/u98sesp/
when SYSDM.CPL was updated to version 4.90.0.3002:

http://www.msfn.org/board/topic/163198-it-works/#comment-1041806
https://www.techtalk.cc/viewtopic.php?p=566#p566

Share this post


Link to post
Share on other sites
12 hours ago, CharlesF said:

Hi,
This has been solved since 'Unofficial Win98SE SP 3.22': http://www.htasoft.com/u98sesp/
when SYSDM.CPL was updated to version 4.90.0.3002:

http://www.msfn.org/board/topic/163198-it-works/#comment-1041806
https://www.techtalk.cc/viewtopic.php?p=566#p566

If it has been solved, then it was solved without changing the CPL file. The 4.90.0.3002 one in USP 3.51 is still the same one that I created in the thread I linked to.

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.

×