• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
pipster

[SOLVED] USBstick take letter D and not U

98 posts in this topic

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
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.

I meant I ran it on D:\Documents and Settings\....\Desktop :D

Anyway running this command:

MkMigrateInf_b.cmd H: migrate_inf_b.txt

produced this:

[Version]
Signature = "$Windows NT$"

[Addreg]
HKLM,"SYSTEM\MountedDevices",,0x00000010
HKLM,"SYSTEM\ControlSet001\Control\StorageDevicePolicies","WriteProtect",0x00010001,1
HKLM,"SYSTEM\MountedDevices","\DosDevices\U:",0x00030001,\
5C,00,3F,00,3F,00,5C,00,53,00,54,00,4F,00,52,00,41,00,47,00,45,00,23,00,52,00,65,00,6D,00,6F,00,76,0
0,61,00,62,00,6C,00,65,00,4D,00,65,00,64,00,69,00,61,00,23,00,37,00,26,00,31,00,35,00,37,00,61,00,64,
00,36,00,32,00,26,00,30,00,26,00,52,00,4D,00,23,00,7B,00,35,00,33,00,66,00,35,00,36,00,33,00,30,00,64
,00,2D,00,62,00,36,00,62,00,66,00,2D,00,31,00,31,00,64,00,30,00,2D,00,39,00,34,00,66,00,32,00,2D,00,3
0,00,30,00,61,00,30,00,63,00,39,00,31,00,65,00,66,00,62,00,38,00,62,00,7D,00

That's different from this, that actually works in the txtsetup:

[Version]
Signature = "$Windows NT$"

[Addreg]
HKLM,"SYSTEM\MountedDevices",,0x00000010
HKLM,"SYSTEM\ControlSet001\Control\StorageDevicePolicies","WriteProtect",0x00010001,1
HKLM,"SYSTEM\MountedDevices","\DosDevices\U:",0x00030001,\
5c,00,3f,00,3f,00,5c,00,53,00,54,00,4f,00,52,00,41,00,47,00,45,00,23,00,52,00,65,00,6d,00,6f,00,76,0
0,61,00,62,00,6c,00,65,00,4d,00,65,00,64,00,69,00,61,00,23,00,37,00,26,00,31,00,34,00,31,00,61,00,30,
00,61,00,37,00,33,00,26,00,30,00,26,00,52,00,4d,00,23,00,7b,00,35,00,33,00,66,00,35,00,36,00,33,00,30
,00,64,00,2d,00,62,00,36,00,62,00,66,00,2d,00,31,00,31,00,64,00,30,00,2d,00,39,00,34,00,66,00,32,00,2
d,00,30,00,30,00,61,00,30,00,63,00,39,00,31,00,65,00,66,00,62,00,38,00,62,00,7d,00

How do I know if it get or not 7& or 8& ??

Where is it written? Maybe is it coded in the 5c,00,3f,00,3f,0... string?

0

Share this post


Link to post
Share on other sites
I meant I ran it on D:\Documents and Settings\....\Desktop :D
There are a lot of desktops arround :)
MkMigrateInf_b.cmd H: migrate_inf_b.txt

\??\STORAGE#RemovableMedia#7&157ad62&0&RM#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}

That's different from this, that actually works in the txtsetup:

\??\STORAGE#RemovableMedia#7&141a0a73&0&RM#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}

That's two different USB devices: 7&157ad62&0 and 7&141a0a73&0

Did you mix tow USB devices?

Attach the proper USB stick first.

How do I know if it get or not 7& or 8& ??

Where is it written? Maybe is it coded in the 5c,00,3f,00,3f,0... string?

Yes, that's a hex values of the string.

Use Tiny Hexer, insert text. Compare http://www.msfn.org/board/index.php?s=&amp...st&p=738009

0

Share this post


Link to post
Share on other sites

Ok. Now (on the notebook) I get migrate.inf files with 7&, to summarize:

In bold are the strings coming from migrates produced by your MkMigrateInf_b.cmd script.

(1) --- Imation Nano USB Device

instanceID: 078B142D0BB2&0

ParentIdPrefix: 8&141a0a73&1 ---> 7&141a0a73&0

Driver:{4D36E967-E325-11CE-BFC1-08002BE10318}\0001

Disk Stamp: 04/27/2009 00:57

Volume Stamp: 04/27/2009 00:57

(2) --- Kingston DataTraveler 2.0 USB Device

instanceID: 2008012500000000000002E4&0

ParentIdPrefix: 8&207c63a1&1 ---> 7&207c63a1&0

Last Mounted As: \DosDevices\G:

Driver:{4D36E967-E325-11CE-BFC1-08002BE10318}\0003

Disk Stamp: 04/27/2009 01:39

Volume Stamp: 04/27/2009 01:39

(3) --- Verbatim STORE N GO USB Device

instanceID: 077A12160129&0

ParentIdPrefix: 8&157ad62&1 ---> 7&157ad62&0

Driver:{4D36E967-E325-11CE-BFC1-08002BE10318}\0002

Disk Stamp: 04/27/2009 01:17

Volume Stamp: 04/27/2009 01:17

So to build a working USBstick for Win setup I have to replace MkMigrateInf2.cmd with MkMigrateInf_b.cmd. Is it correct?

Edited by pipster
0

Share this post


Link to post
Share on other sites
So to build a working USBstick for Win setup I have to replace MkMigrateInf2.cmd with MkMigrateInf_b.cmd. Is it correct?

Yep. :)

But to summarize:

  • A few tens of thousands of people have used MkMigrateInf2.cmd successfully. :)
  • MkMigrateInf2.cmd did not work on 1 (one) - your - machine :( as it had a somehow defective setup/Registry.
  • cdob kindly modified the batch (MkMigrateInf_b.cmd) to (hopefully) insert a "correcting step" only needed on one machine out of several tens of thousands.
  • Once you have fixed the Registry entries, "normal" MkMigrateInf2.cmd would (should) work as well.

So, as I see it , it is a working workaround :thumbup, but it doesn't tell us WHY you are getting 8& and 9& instead of 7& like all the rest of the world. :w00t:

jaclaz

0

Share this post


Link to post
Share on other sites
...

  • A few tens of thousands of people have used MkMigrateInf2.cmd successfully. :)
  • MkMigrateInf2.cmd did not work on 1 (one) - your - machine sad.gif as it had a somehow defective setup/Registry.

...

So, as I see it , it is a working workaround :thumbup , but it doesn't tell us WHY you are getting 8& and 9& instead of 7& like all the rest of the world. :w00t:

jaclaz

"The mutation is the key to our evolution, enabled us to evolve from single celled organisms to the dominant species on the planet. This process is slow and normally takes thousands and thousands of years, but every hundred thousand years the evolution makes a leap ahead. (X-Men the movie, Xavier, voice-over)" :whistle:

:lol:

I've to find what is the problem, but I think it is time to "erase and rewind", and launch a format C: <_<

Edited by pipster
0

Share this post


Link to post
Share on other sites

Many thanks to cdob and pipster for revealing the truth behind these mysterious cases, when migrate.inf was not taken into account.

BTW- Pipster, I wish all the guys asking for support had your patience and returned in a similar manner the requested information, thanks.

0

Share this post


Link to post
Share on other sites

ilko_t, let me say I have to thank you, jaclaz and cdob for your precious and great help.

It's nice to know all of us learned something. :)

0

Share this post


Link to post
Share on other sites
"The mutation is the key to our evolution, enabled us to evolve from single celled organisms to the dominant species on the planet. This process is slow and normally takes thousands and thousands of years, but every hundred thousand years the evolution makes a leap ahead. (X-Men the movie, Xavier, voice-over)" :whistle:

But, on the other hand, it depends on the species you belong to ;):

http://tsanda.wordpress.com/tag/nature/

Sharks are so awesome that they have not needed to evolve in 65 million years. They were swimming around eating §@ç#ing dinosaurs back in the day, now they laugh at humans trying to surf and occasionally decide to take a limb to remind us all they are still around and still in charge.

:whistle:

However ilko_t is pefectly right, it's such a rare thing to find a good guinea pig! ;)

:thumbup

jaclaz

0

Share this post


Link to post
Share on other sites

Hi, I used the very useful program WinSetupFromUSB and successfully install windows xp SP3 on Dell mini 12. However, I have the same problem in this topic. I have read through but sorry I dont quite understand since it's a bit too complicated for me. Can some kind soul tell me what is the easy step to solve this issue? Thanks a million.

0

Share this post


Link to post
Share on other sites

Prepare the stick as usual, if already prepared do not again.

Download the new MkMigrateInf_b.cmd and save it in a path without spaces in it.

http://www.msfn.org/board/index.php?showto...st&p=852822

Open up command prompt, cd to that directory and run:

MkMigrateInf_b.cmd H: H:\migrate.inf

Replace H: with the current USB stick drive letter. Copy H:\migrate.inf to H:\$WIN_NT$.~BT\ replacing the existing file.

edit: file names corrected

Edited by ilko_t
0

Share this post


Link to post
Share on other sites
Open up command prompt, cd to that directory and run:

The new batch is called MkMigratgeInf_b.cmd. Sorry for the confusion.

I wrote the batch MkMigratgeInf.cmd.

As far as I remember you or wimb adjusted this and used the name MkMigrateInf2.cmd in the past.

Hence my new file name is MkMigratgeInf_b.cmd.

@kisivotinh

MkMigratgeInf_b.cmd support one special case in addition:

the running windows did use a strange HardwareId. Reasons are unknwon so far.

If your condition match this, then MkMigratgeInf_b.cmd solve this.

And crossing fixed drive to removable drive or vice versa:

drive letter pre assignment fails.

There maybe other reasons. I've no further idea currently.

0

Share this post


Link to post
Share on other sites

Thanks for noticing, my bad.

Editing the post above.

0

Share this post


Link to post
Share on other sites

Just another brilliant work of cdob, thanks. :)

0

Share this post


Link to post
Share on other sites

It appears WIndows 7 (and most likely Vista) use other syntax for those keys in MountedDevices:

XP:

MountPoint        = G:\
Volume Label = ---
Volume Size = 1 GB (FAT)
Volume Serial = 90E4-5FE9
Volume Name = \\?\Volume{35703e27-2c34-11de-b2dc-005056c00008}\
Partition Name = \Device\Harddisk1\Partition1
Bus Type = USB
Drive Type = removable
Device Types = ---
NoMediaNoLetter = configure >= 3
INI Sections = ---
Volume DevID = STORAGE\REMOVABLEMEDIA\7&C0E6684&1&RM
Drive DevID = USBSTOR\DISK&VEN_JETFLASH&PROD_TS1GJF110&REV_0.00\5AD00F612A5447&0
Ctrl DevID = USB\VID_0457&PID_0151\5AD00F612A5447
Host Controller = Intel® 82801FB/FBM USB2 Enhanced Host Controller - 265C
Volume DosDevName = \Device\Harddisk1\DP(1)0-0+8
Disk DosDevName = \Device\000000c0
Removal Policy = surprise removal ('Optimize for quick removal')
Partition Number = 1 of 1
Friendly Name = JetFlash TS1GJF110
Requested Power = 98 mA (bus powered)
USB Version = 2.0 (high speed)
USB Friendl. Name = USB Mass Storage Device
USB Serial = 5ad00f612a5447
USB Port Name = 5-8

=========================================================

MountPoint = H:\
Volume Label = ---
Volume Size = 1 GB (NTFS)
Volume Serial = 9088-DFCD
Volume Name = \\?\Volume{35703e28-2c34-11de-b2dc-005056c00008}\
Partition Name = \Device\Harddisk2\Partition1
Bus Type = USB
Drive Type = removable
Device Types = ---
NoMediaNoLetter = configure >= 3
INI Sections = ---
Volume DevID = STORAGE\REMOVABLEMEDIA\7&16F722A4&1&RM
Drive DevID = USBSTOR\DISK&VEN_LEXAR&PROD_JD_LIGHTNING_II&REV_1100\AA04015900000158&0
Ctrl DevID = USB\VID_05DC&PID_A640\AA04015900000158
Host Controller = Intel® 82801FB/FBM USB2 Enhanced Host Controller - 265C
Volume DosDevName = \Device\Harddisk2\DP(1)0-0+a
Disk DosDevName = \Device\000000c3
Removal Policy = surprise removal ('Optimize for quick removal')
Partition Number = 1 of 1
Friendly Name = LEXAR JD LIGHTNING II
Requested Power = 500 mA (bus powered)
USB Version = 2.0 (high speed)
USB Friendl. Name = LEXAR MEDIA JD LIGHTNING II
USB Serial = AA04015900000158
USB Port Name = 5-7

Any ideas?

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.