[Mathwiz]

dencorso, on 13 August 2010 - 04:29 PM, said:

Post a photo (easier) or a screenshot (harder... can it be done?) of the BSOD or copy its text *in full* and post it here. Without all the info available, it's hard to say anything.

And when I press Enter, here's a (blurry but legible) pic of the BSOD.

When I "press any key," the desktop reappears but Windows is locked up.

Attached File(s)

•  IMG_0003.JPG (198.1K)
  Number of downloads: 6

This post has been edited by Mathwiz: 19 August 2010 - 02:48 PM

[dencorso]

Are you using NUSB 3.3? If not, update to it (just install the newer one over the older). What is the VIP and PID of the BlackBerry?

[Mathwiz]

dencorso, on 19 August 2010 - 02:26 PM, said:

Are you using NUSB 3.3? If not, update to it (just install the newer one over the older).

Yes, it's version 3.3 (the latest).

dencorso, on 19 August 2010 - 02:26 PM, said:

What is the VIP and PID of the BlackBerry?

Sorry, but I'm a bit ignorant about USB. How do I determine these?

Wait: I found the following registry key on my XP machine:
My Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\Vid_0fca&Pid_0004&MI_01\6&1b9c87ee&0&0001

The description in the registry is USB Mass Storage Device. So if I'm reading that right, the VID is 0FCA and the PID is 0004.

One problem might be that the BB is a composite device. Is that what the &MI_01 is for? There's another key with &MI_00 which I assume is the other device (that I don't expect to work on Win98SE).

This post has been edited by Mathwiz: 19 August 2010 - 03:26 PM

[dencorso]

Use Microsoft's own USBView (v. 5.1.2600.2180, from Win 2k DDK) works under Win 9X and provides useful information about the USB ports in a computer and the devices therein attached. Note that VID = Vendor Id and PID = Product Id. Note also that USBView will give you a duplicate entry for each of your physical USB connectors since it sees each as both a USB 1.1 and a USB 2.0 connectors, which it lists under the appropriate controller. Since your device is 2.0, it should be one of the entries under the EHCI (Enhanced Host Controller Interface = USB 2.0), OK?

[Mathwiz]

dencorso, on 19 August 2010 - 02:53 PM, said:

Use Microsoft's own USBView (v. 5.1.2600.2180, from Win 2k DDK) works under Win 9X and provides useful information about the USB ports in a computer and the devices therein attached. Note that VID = Vendor Id and PID = Product Id. Note also that USBView will give you a duplicate entry for each of your physical USB connectors since it sees each as both a USB 1.1 and a USB 2.0 connectors, which it lists under the appropriate controller. Since your device is 2.0, it should be one of the entries under the EHCI (Enhanced Host Controller Interface = USB 2.0), OK?

Copied from the USBView screen on my Win98SE machine with the BB attached:
idVendor: 0x0FCA (Research In Motion, Ltd.)
idProduct: 0x0004

This matches the registry key from the XP machine.

I have NUSB 3.3 installed, but not the USB 2.0 stack.

[dencorso]

Mathwiz, on 19 August 2010 - 08:39 PM, said:

I have NUSB 3.3 installed, but not the USB 2.0 stack.

How so? Does the motherboard not support USB 2.0 or are you using VIA's USB 2.0 stack?

In any case, please do install IOSYS98 and see whether the BSOD goes away.

[bristols]

Mathwiz, on 19 August 2010 - 02:38 PM, said:

One problem might be that the BB is a composite device.

Without wanting to sidetrack you from your investigations (and provide irrelevant information): is the file usbccgp.sys present in your system (in %windir%\SYSTEM32\DRIVERS)? RetroOS found that he required that file from XP Service Pack 3 in order for composite devices to work:

Windows 98SE (with 98SE2ME) and a recent USB composite device

The file can be found in the USB 2.0 Stack installer at MDGx's site:

http://www.mdgx.com/files/USB20DRV.EXE

This post has been edited by bristols: 20 August 2010 - 07:27 AM

[Mathwiz]

dencorso, on 19 August 2010 - 10:03 PM, said:

How so? Does the motherboard not support USB 2.0 or are you using VIA's USB 2.0 stack?

Sorry for the confusion. I meant I hadn't installed Tihiy's USB 2.0 stack (mentioned in Bristol's post).

dencorso, on 19 August 2010 - 10:03 PM, said:

In any case, please do install IOSYS98 and see whether the BSOD goes away.

bristols, on 20 August 2010 - 07:26 AM, said:

Mathwiz, on 19 August 2010 - 02:38 PM, said:

One problem might be that the BB is a composite device.

Without wanting to sidetrack you from your investigations (and provide irrelevant information): is the file usbccgp.sys present in your system (in %windir%\SYSTEM32\DRIVERS)? RetroOS found that he required that file from XP Service Pack 3 in order for composite devices to work:

Windows 98SE (with 98SE2ME) and a recent USB composite device

The file can be found in the USB 2.0 Stack installer at MDGx's site:

http://www.mdgx.com/files/USB20DRV.EXE

Thank you both. I've downloaded both files and will try installing them tonight. I'll let you know the results.

This post has been edited by Mathwiz: 20 August 2010 - 12:37 PM

[Mathwiz]

Thanks for the suggestions, but no joy.

I installed IOSYS98 but it didn't make any difference. Then I installed USB20DRV, but after that it wouldn't recognize my BB at all!

I opened up the control panel device manager and it reported a problem with the USB mass storage device driver. Looking at the driver files, I realized one (USBSTOR.SYS) was replaced by the USB20DRV update. So I rebooted into MS-DOS mode, restored the original USBSTOR.SYS, and rebooted. (I still have the new version in case I want to try it again sometime.)

That fixed the driver and Windows recognized my BB again, but it's back to the same problem: BSOD if I try to write to the BB.

So neither update helped, but (except for USBSTOR.SYS) they didn't seem to hurt anything, so I'll leave them installed for now.

FYI: the version of USBSTOR.SYS that (sort of) works is 4.90.3000.1. (I assume NUSB 3.3 installed this version.) The version that USB20DRV installed (that didn't work with the BB) is 5.00.2195.6773.

[dencorso]

Yeah, well... I was hesitating in suggesting you to try USB20DRV because I imagined you might end up having the usbstor issue. To use usbstor.sys v. 5.00.2195.6773, it must be loaded together with wdmstub.sys, which is also already present in the right place, since it's installed by USB20DRV, too. So, simply go to C:\WINDOWS\INF, open USBSTOR.INF and find this place in the file:

Quote

[USBSTOR.AddReg]
HKR,,DevLoader,,*NTKERN
;HKR,,NTMPDriver,,"wdmstub.sys,USBSTOR.SYS"
HKR,,NTMPDriver,,USBSTOR.SYS

... notice that the third line is commented (that is, has a semicolon which I marked in red before it) and fourth line is not commented. So move the semicolon from the third line to the fourth, thus:

Quote

[USBSTOR.AddReg]
HKR,,DevLoader,,*NTKERN
HKR,,NTMPDriver,,"wdmstub.sys,USBSTOR.SYS"
;HKR,,NTMPDriver,,USBSTOR.SYS

After doing it, you may put back usbstor.sys v. 5.00.2195.6773, and when you insert your USB devices they may be detected correctly straight away. If not, enter the device manager with the device connected (one at a time), delete the device with the yellow exclamation mark, then disconnect and reconnect the device, that it will be recognized and mounted correctly.

[Mathwiz]

dencorso, on 20 August 2010 - 11:28 PM, said:

Yeah, well... I was hesitating in suggesting you to try USB20DRV because I imagined you might end up having the usbstor issue. To use usbstor.sys v. 5.00.2195.6773, it must be loaded together with wdmstub.sys, which is also already present in the right place, since it's installed by USB20DRV, too. So, simply go to C:\WINDOWS\INF, open USBSTOR.INF and find this place in the file:

Quote

[USBSTOR.AddReg]
HKR,,DevLoader,,*NTKERN
;HKR,,NTMPDriver,,"wdmstub.sys,USBSTOR.SYS"
HKR,,NTMPDriver,,USBSTOR.SYS

... notice that the third line is commented (that is, has a semicolon which I marked in red before it) and fourth line is not commented. So move the semicolon from the third line to the fourth, thus:

Quote

[USBSTOR.AddReg]
HKR,,DevLoader,,*NTKERN
HKR,,NTMPDriver,,"wdmstub.sys,USBSTOR.SYS"
;HKR,,NTMPDriver,,USBSTOR.SYS

After doing it, you may put back usbstor.sys v. 5.00.2195.6773, and when you insert your USB devices they may be detected correctly straight away. If not, enter the device manager with the device connected (one at a time), delete the device with the yellow exclamation mark, then disconnect and reconnect the device, that it will be recognized and mounted correctly.

Well I'll be damned. It worked!

I just copied a file to my BB without that BSOD. Thanks!

[PROBLEMCHYLD]

I just bought a Dynex 2-Port USB 2.0 PCMCIA Notebook Card.
I have NUSB/Usb20drv installed. My card is detected but in the device manager I have
an exclamation mark for the USB 2.0 root hub. Here's a link to the win98 drivers.

http://www.dynexprod...202_Drivers.zip
Its says I'm already using the best drivers so it won't install.

This post has been edited by PROBLEMCHYLD: 27 November 2011 - 12:45 PM

[dencorso]

PROBLEMCHYLD, on 08 October 2010 - 08:28 PM, said:

Its says I'm already using the best drivers so it won't install.

Extract the subdirectory "windows" from the zip to a temporary directory and run U2v2_1_9.exe. It should work.

[PROBLEMCHYLD]

dencorso, on 09 October 2010 - 01:25 AM, said:

Extract the subdirectory "windows" from the zip to a temporary directory and run U2v2_1_9.exe. It should work.

None of them work.

U2v2_1_9.exe
U2v2_051.exe

[dencorso]

The try the following (full manual driver update):
Extract the contents of U2v2_1_9.exe to a folder, then go to the device manager, right-click on the device with the exclamation mark, select properties, update driver, don't search, have a disk, then point it to the folder you've extracted U2v2_1_9.exe to. And let me know whether it did work in this way.

[PROBLEMCHYLD]

dencorso, on 09 October 2010 - 02:47 PM, said:

The try the following (full manual driver update):
Extract the contents of U2v2_1_9.exe to a folder, then go to the device manager, right-click on the device with the exclamation mark, select properties, update driver, don't search, have a disk, then point it to the folder you've extracted U2v2_1_9.exe to. And let me know whether it did work in this way.

Thanks got it working.

[dencorso]

PROBLEMCHYLD, on 09 October 2010 - 08:19 PM, said:

Thanks got it working.

Great! Glad to hear it!

[dencorso]

ekeda, on 14 October 2010 - 01:25 PM, said:

Hi all, I found this thread on the web searching for how to remove my usb "safely remove hardware icon" from system tray. I use winXP and I don't want to hide the icon, but to remove it (I actually tried Icon Remover program, but it doesn't work good). I would be glad to hear any sort of ideas, thanks in advance!

This is the wrong place to ask for it. Win 9x/ME is an altogether different OS family than the one (the NT OS family) Win XP belongs to. Therefore I'm moving your post to the right forum (the Win XP forum) and transforming it into a new thread there.

[98SEUser]

Hi to all!
I have MB with i440bx chipset and tried to start using USB flash. I installed nusb 3.3 and got Kingston DT101 1 Gen 4 GB flash from friend of mine. Everything was OK but only with this flash. When I bought EMTEC 2 Gb - no luck, then Kingston DT102 2 Gen - fall again. I have unknown USB device and that's all. USBView says there is device at full speed, but all fields are zeroed (no PID, no VID etc.) I don't know what to do. Help pls!

[dencorso]

Are they working? And your original kingston still works? Have you access to a XP or later machine?

dencorso, on 11 December 2009 - 08:30 PM, said:

Before anything, apply KB240075 UHCD.SYS hotfix and see whether that solves your problem.
If that's not enough, post here the VID and PID of your Kingston pendrives, and we'll see what can be done.
ChipGenius http://www.mydigit.c.../ChipGenius.rar, run under Win2k/XP (not under Win98), is probably the easiest way to find out the VID and PID of your Kingston pendrives, BTW.