pipster

[SOLVED] USBstick take letter D and not U

98 posts in this topic

@pipster

Does the new PC have any card readers?

As far as I remember you tried the USB stick on other computers, did any of them have USB card reader or any similar USB mass storage device- USB MP3 player, printer with card reader, phone connected via USB etc. etc. ?

Do you have on the old computer an USB hub or PCI USB card? Where do you connect the USB stick to?

The new pc has no card reader. Just the USB on top of the case, connected on the mb. As you can see here: http://techgage.com/article/cooler_master_cm_690/

But on the old notebook I connected an external Hama multi card reader, maybe it is the culprit.

On my father PC there's another external multi card reader but I didn't look at registry..

...

We also learned something new, so I guess we are even. :)

jaclaz

Di questo non posso che essere contento :yes:

So how do you think I can fix that usb entries on the notebook?

I have to use DriveCleanup?

What command I have to use?

-h only USB hubs

-u only USB mass storage devices

-d only Disk devices

-c only CDROM devices

-f only Floppy devices

-v only Storage Volume devices

Maybe -h -u -v ??

0

Share this post


Link to post
Share on other sites
Yep, but the "ID" is not the "ParentIDPrefix".

I would say that the issue at hand is not related to Serial (or lack of it) :blink: or maybe by something connected to it but not really "it".

Sorry, my bad, a lot of information after midnight...
0

Share this post


Link to post
Share on other sites
So how do you think I can fix that usb entries on the notebook?

I have to use DriveCleanup?

What command I have to use?

-h only USB hubs

-u only USB mass storage devices

-d only Disk devices

-c only CDROM devices

-f only Floppy devices

-v only Storage Volume devices

Maybe -h -u -v ??

drivecleanup -t

(list all devices that will be "affected" by the command - just to be sure)

then

drivecleanup

(without parameters), that will get rid of:

- USB mass storage devices

- Disk devices

- CDROM devices

- Floppy devices

- Storage Volumes

:hello:

jaclaz

0

Share this post


Link to post
Share on other sites
drivecleanup -t

(list all devices that will be "affected" by the command - just to be sure)

then

drivecleanup

(without parameters), that will get rid of:

- USB mass storage devices

- Disk devices

- CDROM devices

- Floppy devices

- Storage Volumes

:hello:

jaclaz

Thanks

Did it. It removed a lot of things..

Then I plugged the Nano stick and... it gets parentID similar to the previous one (8&141a0a73&0):

8&141a0a73&1

With 1 at the end but always starting with 8&

I have to format this notebook when I have some time... :yes:

0

Share this post


Link to post
Share on other sites
Thanks

Did it. It removed a lot of things..

Then I plugged the Nano stick and... it gets parentID similar to the previous one (8&141a0a73&0):

8&141a0a73&1

With 1 at the end but always starting with 8&

I have to format this notebook when I have some time... :yes:

Which means obviously that the proggie did not remove the "something" that makes it get the "wrong" ParentID. :(

Can you do a Regedit search on that machine Registry for string:

8&141a0a73&

And post results, or better yet, get Regfind.exe

http://www.petri.co.il/download_free_reskit_tools.htm

and run:

regfind "8&141a0a73&">foundreg.txt

You should get something similar to this (I used "7&2c889678&"):

\Registry
Machine
SYSTEM
ControlSet001
Control
DeviceClasses
{53f5630a-b6bf-11d0-94f2-00a0c91efb8b}
##?#STORAGE#RemovableMedia#7&2c889678&0&RM#{53f5630a-b6bf-11d0-94f2-00a0c91efb8b}
DeviceInstance = STORAGE\RemovableMedia\7&2c889678&0&RM
#
SymbolicLink = \\?\STORAGE#RemovableMedia#7&2c889678&0&RM#{53f5630a-b6bf-11d0-94f2-00a0c91efb8b}
{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
##?#STORAGE#RemovableMedia#7&2c889678&0&RM#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
DeviceInstance = STORAGE\RemovableMedia\7&2c889678&0&RM
#
SymbolicLink = \\?\STORAGE#RemovableMedia#7&2c889678&0&RM#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
Enum
USBSTOR
Disk&Ven_Generic&Prod_USB_CF_Reader&Rev_1.01
058F312D81B&1
ParentIdPrefix = 7&2c889678&0

It is possible that the tool only clears the \USBSTOR\? :unsure:

jaclaz

0

Share this post


Link to post
Share on other sites

Thanks for testing.

A working windows may use:

RemovableMedia#7&*&0 (that's the default)

RemovableMedia#7&*&1

RemovableMedia#8&*&0

RemovableMedia#8&*&1

and so on

jaclaz found usbhistory.

http://nabiy.sdf1.org/index.php?work=usbHistory

Now, every USB Device might have more than one set of instance information in the registry. This may happen due to a difference in the ParentIDPrefix of the device. The ParentIDPrefix correlates to the mountpoint that is assigned to the device. So let's say thumbdrive A was initially assigned as F:\ but then you remove it and insert thumbdrive B, which is also assigned as F:\. If you insert thumbdrive A while you still have thumbdrive B mounted as F:\ then it will be assigned another ParentIDPrefix and a new Registry Key will be created to hold that instance information.
\Registry

Machine

SYSTEM

ControlSet001

Control

DeviceClasses

{53f5630a-b6bf-11d0-94f2-00a0c91efb8b}

That's nice. Site mention this too

In order to get the time that the thumb drive was last plugged into the machine we use the ParentIDPrefix and look under

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{53f56307-b6bf-11d0-94f2-00a0c91efb8b}

This may store previous settings.

@pipster

Can you delete above entries? Remove and attach USB stick again.

To summerize a idea:

A new installed windows use RemovableMedia#7&*&0.

This pattern should go to migrate.inf.

0

Share this post


Link to post
Share on other sites
Can you do a Regedit search on that machine Registry for string:
8&141a0a73&

And post results, or better yet, get Regfind.exe

http://www.petri.co.il/download_free_reskit_tools.htm

and run:

regfind "8&141a0a73&">foundreg.txt

Here's what I get:

\Registry
Machine
SYSTEM
ControlSet005
Control
DeviceClasses
{53f5630a-b6bf-11d0-94f2-00a0c91efb8b}
##?#STORAGE#RemovableMedia#8&141a0a73&0&RM#{53f5630a-b6bf-11d0-94f2-00a0c91efb8b}
DeviceInstance = STORAGE\RemovableMedia\8&141a0a73&0&RM
#
SymbolicLink = \\?\STORAGE#RemovableMedia#8&141a0a73&0&RM#{53f5630a-b6bf-11d0-94f2-00a0c91efb8b}
{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
##?#STORAGE#RemovableMedia#8&141a0a73&0&RM#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
DeviceInstance = STORAGE\RemovableMedia\8&141a0a73&0&RM
#
SymbolicLink = \\?\STORAGE#RemovableMedia#8&141a0a73&0&RM#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
Enum
USBSTOR
Disk&Ven_Imation&Prod_Nano&Rev_PMAP
078B142D0BB2&0
ParentIdPrefix = 8&141a0a73&0
ControlSet006
Control
DeviceClasses
{53f5630a-b6bf-11d0-94f2-00a0c91efb8b}
##?#STORAGE#RemovableMedia#8&141a0a73&1&RM#{53f5630a-b6bf-11d0-94f2-00a0c91efb8b}
DeviceInstance = STORAGE\RemovableMedia\8&141a0a73&1&RM
#
SymbolicLink = \\?\STORAGE#RemovableMedia#8&141a0a73&1&RM#{53f5630a-b6bf-11d0-94f2-00a0c91efb8b}
{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
##?#STORAGE#RemovableMedia#8&141a0a73&1&RM#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
DeviceInstance = STORAGE\RemovableMedia\8&141a0a73&1&RM
#
SymbolicLink = \\?\STORAGE#RemovableMedia#8&141a0a73&1&RM#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
Enum
USBSTOR
Disk&Ven_Imation&Prod_Nano&Rev_PMAP
078B142D0BB2&0
ParentIdPrefix = 8&141a0a73&1
ControlSet007
Control
DeviceClasses
{53f5630a-b6bf-11d0-94f2-00a0c91efb8b}
##?#STORAGE#RemovableMedia#8&141a0a73&0&RM#{53f5630a-b6bf-11d0-94f2-00a0c91efb8b}
DeviceInstance = STORAGE\RemovableMedia\8&141a0a73&0&RM
#
SymbolicLink = \\?\STORAGE#RemovableMedia#8&141a0a73&0&RM#{53f5630a-b6bf-11d0-94f2-00a0c91efb8b}
{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
##?#STORAGE#RemovableMedia#8&141a0a73&0&RM#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
DeviceInstance = STORAGE\RemovableMedia\8&141a0a73&0&RM
#
SymbolicLink = \\?\STORAGE#RemovableMedia#8&141a0a73&0&RM#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
Enum
USBSTOR
Disk&Ven_Imation&Prod_Nano&Rev_PMAP
078B142D0BB2&0
ParentIdPrefix = 8&141a0a73&0

Thanks for testing.

...

@pipster

Can you delete above entries? Remove and attach USB stick again.

To summerize a idea:

A new installed windows use RemovableMedia#7&*&0.

This pattern should go to migrate.inf.

Of course cdob but that key contains strings about IDE#DiskHTS541080G9AT00.

Is it safe to remove it?

Here is the reg export:

DeviceClasses.reg

0

Share this post


Link to post
Share on other sites

Coming from a guy that installed 2K in March 2003 and ran it 24/7/365 since without EVER reinstalling it may sound brutal, but you have some problems on that PC.

ControlSet005 :unsure:

ControlSet006 :ph34r:

ControlSet007 :w00t:

A "normal" Windows has just ControlSet001 and ControlSet002, in some rare occasions of failure of one ControlSet I have seen ControlSet003 and ONCE in my life ControlSet004!

Please check/post contents of key:

HKEY_LOCAL_MACHINE\SYSTEM\Select

jaclaz

0

Share this post


Link to post
Share on other sites
Coming from a guy that installed 2K in March 2003 and ran it 24/7/365 since without EVER reinstalling it may sound brutal, but you have some problems on that PC.

ControlSet005 :unsure:

ControlSet006 :ph34r:

ControlSet007 :w00t:

A "normal" Windows has just ControlSet001 and ControlSet002, in some rare occasions of failure of one ControlSet I have seen ControlSet003 and ONCE in my life ControlSet004!

Please check/post contents of key:

HKEY_LOCAL_MACHINE\SYSTEM\Select

jaclaz

Here's it:

Select.reg

Hey Jaclaz you make me laugh at every post! :D

I didn't know about growing ControlSet00X so I'm learning more post by post on this thread, Thank you.

What's ControlSet for? I see there are strings concerning HW Device driver and IDs.

Anyway yesterday I try to install Nod32 4.0 for 2-3 times but it is causing BSOD after reboot. So I had to start Win in Last Know Good Config to remove Nod 4.0 e reinstall 3.0. Maybe it messed up the drivers loaded with the OS...

PS. I'm sorry about my english... often me too don't understand what I'm writing.. :blushing:

PS2. I begin to feel myself like a guinea-pig from laboratory :huh:

0

Share this post


Link to post
Share on other sites

Basically 2K/XP/2003 use a "ControlSet".

When booting one of the available ControlSet's is chosen, based on the value of the Select key.

The chosen ControlSet is then "mirrored" (actually it is a kind of redirection/hard-link, but the effect is the same as it was a mirror) as CurrentControlSet and the latter "mirror" is actually used.

Your Select key :ph34r::

[HKEY_LOCAL_MACHINE\SYSTEM\Select]
"Current"=dword:00000006
"Default"=dword:00000006
"Failed"=dword:00000005
"LastKnownGood"=dword:00000007

A "normal" Select key :whistle: :

[HKEY_LOCAL_MACHINE\SYSTEM\Select]
"Current"=dword:00000001
"Default"=dword:00000001
"Failed"=dword:00000000
"LastKnownGood"=dword:00000002

In normal operation, ControlSet001 is always used, in case it fails due to corruption or whatever reason, you are given when booting the option to choose "Last Known Good" (or "Ultima configurazione sicuramente funzionante"), if you choose that, then try again booting normally and it doesn't boot, the key changes to:

[HKEY_LOCAL_MACHINE\SYSTEM\Select]

"Current"=dword:000000012 (read n+1 n+2)

"Default"=dword:000000012 (read n+1 n+2)

"Failed"=dword:000000001 (read n n+1)

"LastKnownGood"=dword:000000023 (read n+1 n+3)

And a new ControlSet, ControlSet00n+3, copy of the "last known good" or n+2 is created.

Usually when the above happens, it is time to understand what caused the failure and fix the Registry.

However his would be outside the scope of the thread, check these if you are interested:

http://www.pcreview.co.uk/forums/thread-3161118.php

http://support.microsoft.com/kb/102984/

http://support.microsoft.com/kb/302829/

http://www.geocities.com/nafiton/l_m_sys_set_services.html

Back to your guinea pig duties ;):

You can delete allright the keys:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet00n\Control\DeviceClasses\{53f5630a-b6bf-11d0-94f2-00a0c91efb8b}\##?#STORAGE#RemovableMedia#8&141a0a73&0&RM#{53f5630a-b6bf-11d0-94f2-00a0c91efb8b}

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet00n\Control\DeviceClasses\{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}\##?#STORAGE#RemovableMedia#8&141a0a73&0&RM#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}

in each 00n ControlSet you can find them.

DO NOT delete the whole:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet00n\Control\DeviceClasses\

DO NOT delete the whole:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet00n\Control\DeviceClasses\{53f5630a-b6bf-11d0-94f2-00a0c91efb8b}\

DO NOT delete the whole:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet00n\Control\DeviceClasses\{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}\

jaclaz

Edited by jaclaz
0

Share this post


Link to post
Share on other sites
but that key contains strings about IDE#DiskHTS541080G9AT00.

Is it safe to remove it?

Keep this nice testing machine. Don't remove settings.

There is a new MkMigratgeInf_b.cmd attached. Try this version.

This version use a pattern RemovableMedia#7&*&0

7 and 0 are fixed, if there another values.

Version outdated, removed. Update at http://www.msfn.org/board/index.php?s=&amp...st&p=880257

Edited by cdob
0

Share this post


Link to post
Share on other sites
Keep this nice testing machine. Don't remove settings.

And I was the one accused to use pipster as a guinea pig! :w00t:

:lol:

jaclaz

0

Share this post


Link to post
Share on other sites
...

Back to your guinea pig duties ;) :

You can delete allright the keys:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet00n\Control\DeviceClasses\{53f5630a-b6bf-11d0-94f2-00a0c91efb8b}\##?#STORAGE#RemovableMedia#8&141a0a73&0&RM#{53f5630a-b6bf-11d0-94f2-00a0c91efb8b}

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet00n\Control\DeviceClasses\{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}\##?#STORAGE#RemovableMedia#8&141a0a73&0&RM#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}

in each 00n ControlSet you can find them.

jaclaz

Ok deleted. Thanks for the lessons mate! :)

Keep this nice testing machine. Don't remove settings.

Ok. It's official. I'm a guinea pig... :unsure:

There is a new MkMigratgeInf_b.cmd attached. Try this version.

This version use a pattern RemovableMedia#7&*&0

7 and 0 are fixed, if there another values.

Are you saying to use it with WinSetupFromUSB to make a new USBstick?

I ran it on the desktop. It produce this MIGRATE.INF:

[Version]
Signature = "$Windows NT$"

[Addreg]
HKLM,"SYSTEM\MountedDevices",,0x00000010
HKLM,"SYSTEM\ControlSet001\Control\StorageDevicePolicies","WriteProtect",0x00010001,1
HKLM,"SYSTEM\MountedDevices","\DosDevices\U:",0x00030001,\
24,2C,38,DB,00,BE,3A,83,02,00,00,00

Keep this nice testing machine. Don't remove settings.

And I was the one accused to use pipster as a guinea pig! :w00t:

:lol:

jaclaz

You're an accomplice, I know! :yes:

:lol:

Edited by pipster
0

Share this post


Link to post
Share on other sites
I ran it on the desktop. It produce this MIGRATE.INF:

And, AGAIN :w00t:, you got the migrate.inf for a fixed drive.

You need to open a Command Prompt window and run it giving it a parameter, i.e. the drive letter that currently your USB sticks has.

Just as ilko_t made you run it before ;):

http://www.msfn.org/board/index.php?showto...31770&st=29

jaclaz

0

Share this post


Link to post
Share on other sites
Are you saying to use it with WinSetupFromUSB to make a new USBstick?

I ran it on the desktop.

No, don't run this at the desktop.

Run this at the nice testing machine: the notebook.

Remember the machine produced ParentIdPrefix

(13) --- Imation Nano USB Device

ParentIdPrefix: 8&141a0a73&0

(14) --- Kingston DataTraveler 2.0 USB Device

ParentIdPrefix: 8&207c63a1&0

Or

Nano stick and... it gets parentID similar to the previous one (8&141a0a73&0):

8&141a0a73&1

The new batch should convert this settings to 7&141a0a73&0 and 7&207c63a1&0.

Use the previous command as jaclaz pointed.

Or copy MkMigratgeInf_b.cmd to the USB stick and run MkMigratgeInf_b.cmd direct.

0

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.