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. 


robekia

SD Card (4GB) - Boot as preffered Drive U: Possible?

Recommended Posts

USB\VID_0BDA&PID_0159\20071114173400000

Name: Realtek Card Reader(0159)

Driver installed from c:\windows\inf\oem10.inf [RSUSBSTOR]. 3 file(s) used by driver:

C:\WINDOWS\System32\Drivers\RTS5121.sys

C:\WINDOWS\system32\rts5121.dll

C:\WINDOWS\system32\rts5121icon.dll

A NON windows default driver is used. This driver cause a ParentIdPrefix.

A windows default driver may cause a different ParentIdPrefix. Or the same.

Currently at textmode setup default drivers are used.

Can you confirm: open device manager, change view per connection.

Is the SD card connected to this Realtek Card Reader(0159)?

Can you make another XP installation?

Remove the Realtek Card Reader(0159) driver (rename RTS5121.inf RTS5121.inf.txt). Install XP again.

Which driver and ParentIdPrefix goes now to USB\VID_0BDA&PID_0159 ?

I'm writing this now from another windows installed on Acer5738 without Card Reader drivers.

1- set Hard disk mode to IDE (not sata mode).

2- create a nLite setup files not included any TXT drivers.

3- injected all drivers required with nLite except Card reader PNP drivers.

4- prepare ISO from the nLite output setup files.

5- purn the ISO file to DVD.

6- Remove any sticks/SD from USB/Built in card reader.

7- Reboot the Acer5738 from DVD.

8- Setup windows normaly on drive D: (Second partition).

zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz

9- once windows setup successful, i put the two batch files on the SD and run them from there........

10- GOT ANOTHER "ParentIdPrefix" (7&24e8d74f&) without 0 at the end (attachment1).MIGRATE.INF

11- I run the usbhistory (attached results1). usb_history.txt

zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz

12- I put the two batch files on the 8GB stick and run them from there (attachment2).

13- GOT ANOTHER "ParentIdPrefix" (7&d825748&0)(attachment2).migrate1.inf

14- I run the usbhistory (attached results2).usb_history1.txt

15- I run "devcon.exe driverfiles * > devcon.txt" attached. devcon.txt

do i have to use this migrate.inf (attachment2) from now on for any setup run from stick?

do i have to use this migrate.inf (attachment1) from now on for any setup run from SD?

then, can i re-inject the realtek drivers to the windows setup again then copying the suitable migrate without any problem or i have to forget about them for ever?

do i have to generate separate "migrate.inf" for each "stick/SD" or for each USB port (i.e. when connecting stick to usb(1) --> i have to generate a "migrate.inf", when connecting the same stick to usb(2) --> i have to generate another "migrate.inf"?

Edited by robekia

Share this post


Link to post
Share on other sites

P.S.: Attaching migrateinf2txt.cmd version ALPHA 003

It should now be much faster and able to parse also multi-device migrate.inf's, both in the "plain" format MkMigrateinf.cmd does and in the "complex" one MakeMigrateInf.exe create.

Thanks jaclaz.

I used it now and gives me the same results as above:

7&d825748&0&

7&24e8d74f&0

but wondering, why the first generated has "&0&" at the end? i was expecting "&0" only

Share this post


Link to post
Share on other sites

****GENTS****

I TRIED IT NOW

SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS

Thanks cdob --> your idea wad ideal.

Thanks jaclaz --> your batch file was amazing tool.

Thanks ilko --> you are the first one who mentioned about the ParentIdPrefix

Thanks wimb --> Good explanation & tools.

Thanks MSFN --> i learn MANY THINGS NEW.

I think this is the time for MEM_ISO_LOADED, Why a blank Screen?

Edited by robekia

Share this post


Link to post
Share on other sites
Thanks jaclaz.

I used it now and gives me the same results as above:

7&d825748&0&

7&24e8d74f&0

but wondering, why the first generated has "&0&" at the end? i was expecting "&0" only

That is a glitch of the batch.

I assumed that a ParentIdPrefix would always be 12 characters long, with a central part always 8 characters long, I see this is not the case with that one.

I will find a way to "fix" the batch for this special case.

jaclaz

Share this post


Link to post
Share on other sites
10- GOT ANOTHER "ParentIdPrefix" (7&24e8d74f&) without 0 at the end (attachment1).
USB\VID_0BDA&PID_0159\20071114173400000

Name: USB Mass Storage Device

Driver installed from d:\windows\inf\usbstor.inf [uSBSTOR_BULK]. 1 file(s) used by driver:

D:\WINDOWS\system32\drivers\USBSTOR.SYS

This confirms: another driver usbstor.sys result another "ParentIdPrefix".

This knowledge is new.

12- I put the two batch files on the 8GB stick and run them from there (attachment2).

13- GOT ANOTHER "ParentIdPrefix" (7&d825748&0)

This is another surprise.

The Realtek driver does interfere a USB stick too. This is rather strange.

do i have to use this migrate.inf (attachment2) from now on for any setup run from stick?

do i have to use this migrate.inf (attachment1) from now on for any setup run from SD?

If need be, you may create one migrate.inf, use different letters for USB Stick and SD card.
can i re-inject the realtek drivers to the windows setup again then copying the suitable migrate without any problem or i have to forget about them for ever?
Why does Acer offer a USB SD driver at all?

You may intergrate the driver again as PNP driver, textmode setup use usbstor.sys ParentIdPrefix.

If you prefer a most confusing configuration:

Add the Realtek driver as a textmode driver.

You get very funny results again at different machines.

Avoid this driver!

do i have to generate separate "migrate.inf" for each "stick/SD" or for each USB port
No, the USB port dosn't matter.
SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS
Congratulations.

Share this post


Link to post
Share on other sites

It's interesting to follow:

Card reader/SD card:

Generic windows driver:

USB\VID_0BDA&PID_0159\20071114173400000
Name: USB Mass Storage Device
Driver installed from d:\windows\inf\usbstor.inf [USBSTOR_BULK]. 1 file(s) used by driver:
D:\WINDOWS\system32\drivers\USBSTOR.SYS
USBSTOR\DISK&VEN_GENERIC-&PROD_MULTI-CARD&REV_1.00\20071114173400000&0
Name: Generic- Multi-Card USB Device
Driver installed from d:\windows\inf\disk.inf [disk_install]. 1 file(s) used by driver:
D:\WINDOWS\system32\DRIVERS\disk.sys

USBSTOR\DISK&VEN_GENERIC-&PROD_MULTI-CARD&REV_1.00\20071114173400000&0

has hash/parentID "24e8d74f".

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

Realtek driver:

USB\VID_0BDA&PID_0159\20071114173400000
Name: Realtek Card Reader(0159)
Driver installed from c:\windows\inf\oem10.inf [RSUSBSTOR]. 3 file(s) used by driver:
C:\WINDOWS\System32\Drivers\RTS5121.sys
C:\WINDOWS\system32\rts5121.dll
C:\WINDOWS\system32\rts5121icon.dll
USBSTOR\DISK&VEN_GENERIC-&PROD_MULTI-CARD&REV_1.00\00000
Name: Generic- Multi-Card USB Device
Driver installed from c:\windows\inf\disk.inf [disk_install]. 1 file(s) used by driver:
C:\WINDOWS\system32\DRIVERS\disk.sys

USBSTOR\DISK&VEN_GENERIC-&PROD_MULTI-CARD&REV_1.00\00000

results in d7f206a hash.

I am rather confused to follow Kingston USB stick "transformations" with all the information scattered around the thread:

It this the same stick plugged?

USB\VID_0951&PID_1623\00137297175CF971862F0A39
Name: USB Mass Storage Device
Driver installed from d:\windows\inf\usbstor.inf [USBSTOR_BULK]. 1 file(s) used by driver:
D:\WINDOWS\system32\drivers\USBSTOR.SYS
...........
...........
USBSTOR\DISK&VEN_KINGSTON&PROD_DATATRAVELER_120&REV_1.00\00137297175CF971862F0A39&0
Name: Kingston DataTraveler 120 USB Device
Driver installed from d:\windows\inf\disk.inf [disk_install]. 1 file(s) used by driver:
D:\WINDOWS\system32\DRIVERS\disk.sys

This is hash 15c42460

USB\VID_0951&PID_1607\5B82050053DD
Name: USB Mass Storage Device
Driver installed from c:\windows\inf\usbstor.inf [USBSTOR_BULK]. 1 file(s) used by driver:
C:\WINDOWS\system32\drivers\USBSTOR.SYS
.............
.............
USBSTOR\DISK&VEN_KINGSTON&PROD_DATATRAVELER_2.0&REV_PMAP\5B82050053DD&0
Name: Kingston DataTraveler 2.0 USB Device
Driver installed from c:\windows\inf\disk.inf [disk_install]. 1 file(s) used by driver:
C:\WINDOWS\system32\DRIVERS\disk.sys

This is hash 2ba01341

@robekiaTo follow troubles with 8GB Kingston USB stick can you show me where is the output from devcon and usb_history for the following cases

1) Realtek card reader driver installed and used

2) Generic XP driver used

Need 2 pairs of those files, for the two cases above.

Share this post


Link to post
Share on other sites

@robekiaTo follow troubles with 8GB Kingston USB stick can you show me where is the output from devcon and usb_history for the following cases

1) Realtek card reader driver installed and used

2) Generic XP driver used

Need 2 pairs of those files, for the two cases above.

Actualy, i have two SD cards, 2gb and 4gb

also, i have 4 Sticks, 512mg, 1gb, 4gb and 8gb

all tests done using (SD 2 and 4gb)(Sticks 2 and 8gb)

I used them all now in this windows so the results will be FULL when i run "history" and "devcon"

now i'll attach the requested information

NEW Windows

history --> usb_history_NEW_.txt

devcon results --> devcon_NEW_.txt

migrate.inf for SD2 --> MIGRATE_NEW__SD2_.INF

ParentIdPrefix SD2 --> "7&24e8d74f&0"

migrate.inf for SD4 --> MIGRATE_NEW__SD4_.INF

ParentIdPrefix SD4 --> "7&24e8d74f&0"

migrate.inf for STICK2 --> MIGRATE_NEW__STICK2GB_.INF

ParentIdPrefix STICK2 --> "7&2ba01341&0"

migrate.inf for STICK8 --> MIGRATE_NEW__STICK8GB_.INF

ParentIdPrefix STICK8 --> "7&d825748&0&"

OLD Windows

will reboot using old windows, then attach the following

history --> usb_history_old.txt

devcon results --> devcon_OLD_.txt

migrate.inf for SD2 --> MIGRATE_OLD__SD2_.INF

ParentIdPrefix SD2 --> "7&d7f206a&0&"

migrate.inf for SD4 --> MIGRATE_OLD__SD4_.INF

ParentIdPrefix SD4 --> "7&d7f206a&0&"

migrate.inf for STICK2 --> MIGRATE_OLD__STICK2GB_.INF

ParentIdPrefix STICK2 --> "7&2ba01341&0"

migrate.inf for STICK8 --> MIGRATE_OLD__STICK8GB_.INF

ParentIdPrefix STICK8 --> "7&d825748&0&"

wondering why the "ParentIdPrefix" for SD2GB is always same as SD4GB

while the "ParentIdPrefix" for STICK2GB is not the same as STICK8GB although the STICKS are from the same vendor(KINGSTON) as the SDs?

Edited by robekia

Share this post


Link to post
Share on other sites
New Migrate2txt.cmd 004 Alpha "Fixed" version to remove the trailing "&" on "short" ParentIdPrefix.

Hi jaclaz,

it is OK now displaying the ParentIdPrefix without the trailing &

Share this post


Link to post
Share on other sites
Actualy, i have two SD cards, 2gb and 4gb

also, i have 4 Sticks, 512mg, 1gb, 4gb and 8gb

all tests done using (SD 2 and 4gb)(Sticks 2 and 8gb)

I used them all now in this windows so the results will be FULL when i run "history" and "devcon"

now i'll attach the requested information

Thanks, this was nice summary.

So both USB sticks did NOT change ParentID when Realtek driver was used.

wondering why the "ParentIdPrefix" for SD2GB is always same as SD4GB

while the "ParentIdPrefix" for STICK2GB is not the same as STICK8GB although the STICKS are from the same vendor(KINGSTON) as the SDs?

As cdob mentioned already- Windows assigns drive letter to the card reader's slots, not to the inserted sd/whatever card. ParentID is a hash of the same string in case of card reader, it does NOT come from the plugged in SD card, but from the reader itself.

Whereas these different USB sticks, although from the same manifacturer do have different discriptions, hence the different parentIDs generated from them.

Share this post


Link to post
Share on other sites
So both USB sticks did NOT change ParentID when Realtek driver was used.

No, they did change, i updated the post

you may mean the SDs

Share this post


Link to post
Share on other sites
NEW Windows:

ParentIdPrefix STICK2 --> "7&2ba01341&0"

ParentIdPrefix STICK8 --> "7&d825748&0"

...

OLD Windows:

ParentIdPrefix STICK2 --> "7&2ba01341&0"

ParentIdPrefix STICK8 --> "7&d825748&0"

It's the same prefix for the same stick when Realtek driver is used, or not.

Stick2 and Stick8 are NOT supposed to have same prefix, but Stick2was supposed to have the same prefix with and without Realtek driver, as it happens. Same for Stick8- its ParentIDPrefix does NOT change when Realtek drivers are used.

Hope it's clearer for you now, just in case again- no matter that both sticks are the same brand, they are different, and supposedly have different discription, hence different ParentIDprefix, derived from it.

Share this post


Link to post
Share on other sites
Hope it's clearer for you now, just in case again- no matter that both sticks are the same brand, they are different, and supposedly have different discription, hence different ParentIDprefix, derived from it.

Thanks a lot

realy all of you helped me so much......

Share this post


Link to post
Share on other sites

Sorry Again,

I don't know what is going on.

My Stick kingstone data traveller 120 8GB is giving blank screen with blinking cursor when used with HP530 and HP500 labtops just after choosing the TXT mode option from Boot.ini.

the Stick boots fine with GRUB, chainloading to NTLDR is OK, but once choosen to go with TXT mode, Blinking cursor appear.

i did many research and i got to know that HP equipment is the cause in this case. am I right? is there any solution or i have to create 2 partitions (2 & 6 GB)?

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...