Sorry to open a new Topic for the subject mentioned (and it might be a stupid question also) but actually, i'm looking for this facility since the time i read the Topic of CDOB.

I was looking for his solution "How to install multi operating system by the use of USB Flash and finally i got it from his Topic (thanks CDOB).

i Bought a new Labtop (Acer Aspire 5738) whitch has a built in SD Card reader.

When i used Flash memory 2GB to simulate his solution, the Flash seen as Preffered Boot Drive U:

My problem is:
1 - When i used Flash memory > 2GB to simulate his solution, the Flash seen as Drive D:
2 - When i used SD memory Card, the SD always seen as Drive D:

the above results is not suitable for me as i always needs the Windows Setup Drive to be HIGHER than H:

Is it possible? How??

Have a look:
http://www.msfn.org/board/2-t137508.html
http://www.msfn.org/board/2-t131770.html

Try latest MkMigrateInf.cmd:
http://www.msfn.org/board/index.php?act=at...st&id=27356

What is ParentIDprefix of this SD card on the computer you prepare it on, and on the computer you are installing from it?

Where i can find ParentIDprefix ?

i'm using the SD in the same Labtop right now (Acer ASPIRE 5738).

do i have to use this file instead of the one included in multiboot_10_usb?

I Found that reference in REG:

7&d7f206a&0


This is the results when i run the CMD:

[Version]
Signature = "$Windows NT$"

[Addreg]
HKLM,"SYSTEM\MountedDevices",,0x00000010
HKLM,"SYSTEM\ControlSet001\Control\StorageDevicePolicies","WriteProtect",0x00010001,1
HKLM,"SYSTEM\MountedDevices","\DosDevices\U:",0x00030001,\
5C,17,5C,17,00,5E,C6,52,07,00,00,00

Did you run the script against your drive letter of the sd card?
Replace G: with whatever letter the SD card is.





Or http://sourceforge.net/projects/usbhistory/

Please attach this file, it's quite interesting to dig deeper into this.

Yes, replacing the one in ~BT folder.
Clarification- migrate.inf is generated by older version of MkMigrateInf.cmd from your local registry, usb_multiboot does not have a 'generic' migrate.inf included.

the previous "MkMigrateInf_c.cmd" run wasn't with any parameters.

When i run "MkMigrateInf_c.cmd H: migrate_inf.txt" --> i got the attached.
Click to view attachment

I run "usbhistory.exe > c:\usb_history.txt" --> i got the attached.
Click to view attachment
Number (3) is my drive (H:) Built in Card reader



please tell me what to do right now? and whether the procedure that you'll tell me can be applied to any Labtop?

Which one is a typo and which one is correct?

Are contents of the previous migrate.inf similar, the one which did NOT work properly and gave you letter D during setup?

Did you produce migrate_inf.txt on the laptop in question, with freshly installed Windows?

We need to compare what prefix was used where you prepared the SD card, and the prefix used on the machine where Windows is being installed onto.

Sorry, My Internet connection dropped down yesterday.

No typo, both cases happened
Mainly, any (Flash or SD) used over 2GB causes the problem.


Both contents similar except the OLD one has extra fields as folow:
[Strings]
;Handy macro substitutions non-localizable
REG_SZ = 0x00000000
REG_BINARY = 0x00000001
REG_DWORD = 0x00010001
REG_MULTI_SZ = 0x00010000
REG_SZ_APPEND = 0x00010008
REG_EXPAND_SZ = 0x00020000


NO, i need to prepare the Fresh Setup first before re-build my system.
BTW, i have 5 labtops at my home (AsusEee, HP500, HP530, Acer1640 and Acer5738) and all giving the same

I tried just now, and got Drive (D:)

Do you suggest to use the newly generated migrate.inf although they are almost the same?

Did you use RAM loaded setup in this case too, not USB_multiboot.cmd/WinSetupFromUSB?

In RAM loaded setup there is no reference so far for preserving USB drive letter, I wonder how you made it appear as U in the case above?

i already try "RAM LOADED ISO" by cdob since days but unfortunately, windows seems to hang at the step of identifing the Hard disks "SETUP LOADING WINDOWS" and a blank screen appear for long long time till i shutdown the Labtop.
this is for both types (flash memory and SD), nothing success with me

I already post a message in http://www.msfn.org/board/install-xp-ram-l...ge-t137714.html
but guys there says that it is a strange bios.

i assure that SATA drives are slipstreamed with the ISO file and a correct IMG and GRUB deffinition are there and everything is ok but the ISO file hangs when reach that step.

i prefere Loading ISO RAM Setup because there is no need for many customization but i got no luck.

i still insist (THERE IS ALWAYS A SOLUTION).

I'll try to summarize:
- you are using USB_multiboot10
- with USB flash stick 2GB you can get letter U: of it during setup on all machines
- with USB flash stick > 2GB or SD card of any size it does NOT get U: during setup, on all machines

Did I get it right?

Well, NO.

I INSIST that "there is always a solution" IF the asking member PROVIDES a clear, detailed, report of what he did.

Look, we are at post #10 in this thread and not ilko, not myself have a clear idea of what the heck is the problem.
You seem to jump back and forward from USB_multiboot10 to cdob's RAM based method completely faling to properly report the steps you have taken.

They may be very clear in your mind , but rest assured they are not in ours, possibly because wre are a bit thick , but maybe also because you failed to explain the issue.

Why don't you forget anything you've posted till now and make a new post reporting in order all the steps you taken, the problems you had, etc., etc., I am sure you already did so in fragments, but we seem unable to put all the fragments together properly.


jaclaz

Given a 4GB SanDisk SD Plus USB, this is both a SD card and a USB stick.

USB SD card reader, no card inserted: XP assign a drive letter F:
The drive letter goes to the card reader, not the SD card itself.
ParentIdPrefix: 7&776bc3a&1

USB SD card reader disconnected.
SD card inserted to another USB SD card reader.
XP assign a drive letter F:, however MountedDevices is changed.
ParentIdPrefix: 7&524fc66&0

USB SD card reader disconnected.
Flash card connected as USB stick:
XP assign a drive letter F:, MountedDevices is changed again.
ParentIdPrefix: 7&3157a48c&0

The same SD card may use different ParentIdPrefix.
Migrate.inf goes to the SD card storage controller, not to the SD card.


Which laptop do you use to prepare the SD card?
Which laptop do you like to install XP to?

Exactly.

The answer for all is "Acer5738"

I have the folowing labtops and thier preferred installation type:
1 - AsusEee --> Need to Use either Flash Memory (DataTraveler 8GB) or (scandisk SDHC 4GB using internal Card reader).
2 - HP500 --> Need to Use either Flash Memory (DataTraveler 8GB) only.
3 - HP530 --> Need to Use either Flash Memory (DataTraveler 8GB) only.
4 - Acer1640 --> Need to Use either Flash Memory (DataTraveler 8GB) only.
5 - Acer5738 --> Need to Use either Flash Memory (DataTraveler 8GB) or (scandisk SDHC 4GB using internal Card reader) this is the important one and this is the Labtop that used to Create/Install the image

@jaclaz
i'm not jumping back and forward

please find hereunder the whole story (please be Patient):

I have the folowing labtops and thier preferred installation type:
1 - AsusEee --> Need to Use either Flash Memory (DataTraveler 8GB) or (scandisk SDHC 4GB using internal Card reader).
2 - HP500 --> Need to Use either Flash Memory (DataTraveler 8GB) only.
3 - HP530 --> Need to Use either Flash Memory (DataTraveler 8GB) only.
4 - Acer1640 --> Need to Use either Flash Memory (DataTraveler 8GB) only.
5 - Acer5738 --> Need to Use either Flash Memory (DataTraveler 8GB) or (scandisk SDHC 4GB using internal Card reader) this is the important one and this is the Labtop that used to Create/Install the image

in order to acheive that, i tried MULTIBOOT_USB_10 with another Flash Memory (Kingston Data Traveler 2GB).
as i'm using the Acer5738 for developing and building, the MUTIBOOT_USB_10 using 2GB is doing Great for all of the rest Labtops.
i was happy to be able to install my Nlited Windows XP SP3 on all these Labtops with one flash memory.

after they success, i decided to do the same for the main Labtop (Acer5738).
i decided to re-partition the hard disk and install the same windows using the Flash Memory 8GB not the 2GB in order to have one Flash having multiboot with deferent types of Nlited setup, so i rebuilt the 8GB and start to use the Acer 5738.
(I'M STILL IN MULTIBOOT_USB_10)
after booting the Acer5738 using the new 8GB and reach the step of getting the drive letter in text mode, i got it (D: even when i used the option 0 "usb stick") which is not prefered to me as i may need to install windows later on the second partition of any labtop.

i took the 8GB flash and re-try for the previous success labtops, then i found usb flash drive in all is seen as (D:) also.

then i tried to look for another solution to have one 1 way for all labtops and i found the "RAM_LOAD_ISO"

i built the ISO from the same source that used earlier using 2GB and 8GB flash memory for all the mentioned labtops, then i got the mentioned problem.
i tried with the SDHC memory card using the built-in card reader for (AsusEee and Acer5738), i got the same problem.


i hope that clarify the issue and sorry to waste your time jaclas.

i'm not intened to let people get confused, i'm trying to be always clear for descriping any problem and i feel that there is a solution (maybe it is not discovered yet) but with tries and well reading, we will have a solution not only to fix my problems but to help all people that may fail in my situation in the future, hence i said (THER IS ALWAYS A SOLUTION).


so finaly here is a clear fast track description:


1 - Using MULTIBOOT_USB_10 and 2GB Flash Memory:
A - for AsusEee --> Flash Memory seen as Drive U: --> whole story Success --> OK
B - for HP500 --> Flash Memory seen as Drive U: --> whole story Success --> OK
C - for HP530 --> Flash Memory seen as Drive U: --> whole story Success --> OK
D - for Acer1640 --> Flash Memory seen as Drive U: --> whole story Success --> OK
E - for Acer5738 --> Flash Memory seen as Drive U: --> whole story Success --> OK

2 - Using MULTIBOOT_USB_10 and 8GB Flash Memory:
A - for AsusEee --> Flash Memory seen as Drive D: --> Not OK
B - for HP500 --> Flash Memory seen as Drive D: --> Not OK
C - for HP530 --> Flash Memory seen as Drive D: --> Not OK
D - for Acer1640 --> Flash Memory seen as Drive D: --> Not OK
E - for Acer5738 --> Flash Memory seen as Drive D: --> Not OK

3 - Using MULTIBOOT_USB_10 and 4GB SDHC in built-in card reader:
A - for AsusEee --> SDHC Memory Card seen as Drive D: --> Not OK
B - for Acer5738 --> SDHC Memory Card seen as Drive D: --> Not OK

4 - Using RAM ISO LOADED and 4GB SDHC in built-in card reader:
A - for AsusEee --> Blank screen (Mentioned problem) --> whole story Failed.
E - for Acer5738 --> Blank screen (Mentioned problem) --> whole story Failed.

Do you use always the internal Card reader?
How is the internal Card reader connected?
Does this internal Card reader use a USB connection?

Do you use a external USB Card reader?

Which ParentIdPrefix does current windows use at Acer5738?
Which ParentIdPrefix does exist at migrate.inf?
Which ParentIdPrefix does ùse a freshly installed windows?

BTW: to enhance the confusion.
There is a new firadisk 0.0.1.14 http://www.boot-land.net/forums/index.php?...ost&p=83637

No, please read the previous post that i replied to jaclaz, i clearly descripe my proccess in there.
it is Built-in Card Reader in Acer5738.

I inserted the SDHC card in External Card reader and connect it to one of the normal 4 USB
in the labtop with the same problem

They are always the same as i attached previously the Generated files
i'm attaching them again for reference:
Click to view attachmentClick to view attachment

Thank you for this information, i'm gonna try it nowwwwww

So, if I get it right:

• everything goes well with the 2 Gb stick
• everything goes wrong with the 8 Gb stick
• everything goes wrong with the SD card

Let's for the moment FORGET about the SD card, we will get there later (or if you prefer, please talk with me about the sticks and talk with cdob about the SDcard, everyone has his own "specialities" - or at least sometimes different approaches)

You still have the 2Gb stick, do you?

If yes it would be interesting to have the output of Chipgenius:
http://www.boot-land.net/forums/index.php?showtopic=4661
http://www.mydigit.cn/chipgenius.htm

for both sticks AND the result of running mkmigrateinf.exe:
http://www.msfn.org/board/profiles-directo...819-page-9.html
http://www.msfn.org/board/forcing-system-d...973-page-7.html
on a system with BOTH sticks connected.

jaclaz

Exactly


I agree for now........thanks

yes i still have

I downloaded the program.
for 2GB hereunder the results:
Device Name: ?[J:]?USB Mass Storage Device(Kingston DataTraveler 2.0 USB Device)

PnP Device ID: VID = 0951 PID = 1607
Serial Number: 5B82050053DD
Revision: PMAP

Device Type: Standard USB device - USB2.0 High-Speed

Chip Vendor: phison
Chip Part-Number: PS2232

Product Vendor: (N/A)
Product Model: (N/A)



for 8GB, here is the results:
Device Name: ?[K:]?USB Mass Storage Device(Kingston DataTraveler 120 USB Device)

PnP Device ID: VID = 0951 PID = 1623
Serial Number: 00137297175CF971862F0A39
Revision: 1.00

Device Type: Standard USB device - USB2.0 High-Speed

Chip Vendor: skymedi
Chip Part-Number: SK6211

Product Vendor: (N/A)
Product Model: (N/A)


for SDHC Card:
Device Name: ?[H:]?Realtek Card Reader(0159)(Generic- Multi-Card USB Device)

PnP Device ID: VID = 0BDA PID = 0159
Serial Number: 20071114173400000
Revision: 1.00

Device Type: Standard USB device - USB2.0 High-Speed

Chip Vendor: (No match record)
Chip Part-Number: (No match record)

Product Vendor: Generic-
Product Model: Multi-Card


I'll do it and get back to you soon.......

OK, the 2 Gb is a Phison (and you don't want to touch it since it works allright), the 8 Gb is a Skymedi.

Both are re-branded with Vid 0951 (Kingston) and Pid 1607 and Pid 1623 respectively (Kingston internal model designation).

If you go to a machine where the sticks were connected and open with Regedit the key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USBSTOR\

You are likely to find keys named something like:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USBSTOR\Disk&Ven_Kingston&Prod_Data_Traveler&Rev_1.00
or
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USBSTOR\Disk&Ven_Kingston&Prod_Data_Traveler&Rev_

and in a sub-key with the name of the serial number, most probably, and respectively:
\5B82050053DD&0
\00137297175CF971862F0A39&0
(the above is pretty much unuseful, as we already know this data from the USBhistory.txt you posted, but now you know how it works, more or less)
2Gb ParentIdPrefix=7&1554d726&0
8Gb ParentIdPrefix=7&d825748&0

The migrate.inf you posted is for a ParentIdPrefix=7&d7f206a&0 which corresponds to the drive H:\ (Generic- Multi-Card USB Device) in the USBhistory

This may be of use:


Cannot say why the migrate.inf resulted for another device.

jaclaz

Good News , but not for everything.

i newly installed a fresh windows and did a new test as per the above cases with the below status:

Using BOOT_ISO_LOADED:
SDHC Memory Card Finally success on Asus but still failed on Acer5738.
Flash Memory Success on all labtops except Acer5738
Click to view attachment

So, I still have 7 scenarios Failed using "MULTI_BOOT_10" against 3 scenarios Failed using "BOOT_ISO_LOADED"
I think, it is logic trying to kill the three instead of 7


the last one is the important one to me......

You are still going for "statistical results" instead of trying to pinpoint (and hopefully solve) a single problem at the time....:whistling:

However the Acer5738 appears as troublemaker.

The info you posted however is incomplete without knowing which info is in the migrate.inf that you used with each device, quite obviously you managed to produce a "right" migrate.inf for the 2G stick, that gets U: on all systems but apparently failed with the 8G one.

jaclaz

Do i have to save your code as MKMigrateInf2.cmd and replace the one in "makebt" folder and run the "USB_MultiBoot_10.cmd" against the build for each labtop, then attach here the MIGRATE.INF resulted?

Surely NO.

The code I posted was just a quick and dirty hack to show what ParentIdPrefix is written into a given EXISTING migrate.inf file.

You posted:

• "a" USB_history.txt
• "a" migrate.inf file

Each migrate.inf file (as made by mkmigrateinf.cmd mkmigrateinf2.cmd) contains one and one only ParentIdPrefix.

Rather obviously the migrate.inf that goes on a device MUST use the ParentIdPrefix of that device if you want the device to get letter U:.

What I suspect, and that till now you completely failed to help finding out, is that you have on the 8G stick a WRONG (i.e. with a different ParentIdPrefix) migrate.inf.

Since you keep doing the three card shuffle:
http://en.wikipedia.org/wiki/Three-card_Monte

with sticks and methods, it is very easy that files were exchanged.


What you should do is to make sure that the migrate.inf on the 2G sticks uses the ParentIdPrefix of 7&1554d726&0 and that the 8G uses the ParentIdPrefix of 7&d825748&0 (as resulting from the USB_history.txt file you posted).

The small batch migrate2txt.cmd I posted should be copied to the same directory on the stick where migrate.inf is, then you open a command prompt and run it from there.
The result should be the actual ParentIdPrefix that is inside the actual migrate.inf on that stick.

Hope the above is clearer.

jaclaz

Realy i'm not as this.

the idea is i wasn't understand what you were requesting me to do unless you descripe above, and here i'm doing it.

i'm not profesional like you, that's why i didn't got you at the first time.

what i did now is:
1 - i put "migrate.inf" on the root of the 8GB Stick along with your code.
2 - i ran the code and it was writting the results too slow to the screen.
3 - the results are "7&d7f206a&0" which i beleive is for the SDHC

Now, -after i understand - please please be patient with me and correct me if i'm wrong
if i want to generate the correct migrate.inf, i have to run some .exe files from the stick that i want it to be U: Correct?
if yes, how?

beleive me i was confused

I do believe you, rest assured.

PRELIMINARY STEPS:

1. Open a drawer.
2. Put inside the drawer the 2G stick AND the SD card.
3. Close the drawer.
4. Lock it.
5. Put the drawer key in a self addressed envelope and send it via snail mail to yourself.

The above are to avoid confusion.

REAL STEPS :

1. get latest mkmigrateinf.cmd
   http://www.msfn.org/board/index.php?act=at...st&id=27356
2. copy it somewhere
3. insert the 8G stick (you should have not any other ones around)
4. take note which drive letter it gets
5. open a command prompt and run mkmigrateinf.cmd <driveletter_of_the_stick>, example: mkmigrateinf.cmd G:
6. it should produce a migrate.inf file
7. verify (using my batch or whatever) the ParentIdPrefix within it
8. replace the existing migrate.inf on the 8G stick with the one produced IF it matches what was said before

jaclaz

SORRY.
I WROTE THIS REPLY BEFORE READING YOUR LAST REPLY[size="4"][/size]


I think NOW I GOT YOU.

i have to do the following (am i right)?

1 - Chech the "usb_history.txt" for the ParentIdPrefix of the stick that i want it to be U: at installation time e.g. "7&d825748&0".
2 - Copy the "MkMigratgeInf_c.cmd" and "MkMigrateInf2.cmd" to the root of the needed stick.
3 - Run the "MkMigratgeInf_c.cmd" on the stick to generate the "MIGRATE.inf".
4 - In order to be sure that this is the correct "MIGRATE.inf", i have to run the "MkMigrateInf2.cmd".
5 - The result from step 4 must match the "7&d825748&0".
6 - When matched, then this is the file "MIGRATE.inf" that should be copied to the stick under I386 directory for the installation.

Correct?

Almost.

You need only one "mkmigrateinfxx.cmd" either the one that is in the original topic or the latest version linked to.
The small batch I posted should be called migrate2txt.cmd as in:

(again to avoid confusion)

If you copy the mkmigrateinf.cmd to the stick you do not need to specify the drive letter of the tick itself, otherwise (as an example if you put it in C:\batches\) you need to specify the USB stick drive letter.

All the rest is OK.

jaclaz

4- compare output of the 2 batch files, the newest one may give slightly different result, the older one is not necessarily the suitable one.
6- migrate.inf goes to $WIN_NT$~BT folder on the USB stick.

@jaclaz

Excellent.

You are totaly RIGHT.

Finaly, I DID IT

I knew where was my mistake but now, i have a solid procedure to do the correct work in order to use the stick for installation to get the correct Drive U:

thanks a lot for this help.

@ilko
Thanks a ton to you too, that greately Help.

@cdob
is there still any chance to discuss the blank screen when using SDHC Card on Acer5738?

As for the blank screen- try the newer version of Firadisk. It helped in one case with similarly freezing screen when using 2003 source:
http://www.boot-land.net/forums/index.php?...ost&p=83680

OK, do i have to extract the contents to the "firadisk" directory of the XB_inst.ima?

One of the many possible ways:

1) Extract contents of the new Firadisk somewhere
2) Install ImDisk:
http://www.ltr-data.se/opencode.html#ImDisk
3) Right click on XB_INST.IMA and select "Mount as ImDisk virtual disk", do NOT select read-only on the next screen, say you use drive letter X:
4) Rename existing firadisk.sys to firadisk.sys.old in X:\firadisk\
5) Copy the new firadisk.sys to X:\firadisk\. You may have to rename firadisk32.sys to firadisk.sys if file names do not match.
6) Right click on X: in explorer and select "Unmount ImDisk virtual disk" or go to control panel-->ImDisk and unmount it from its control panel.

Simple?

So Simple.
i'm gonna give it a try and report here tomorrow.

Thanks you All

Overwrite old files with the new ones.
This was the hint at Post #16.

ilko_t explained this already.

To clarify, can clarify again? I like to know the reason, may be a fix is required.
How did you prepared the 2GB, 4GB and 8GB drive?
Did you copy files from 2GB to 4GB drive?
Did you run MULTIBOOT_USB_10 to each drive? A correct migrate.inf should be added that way?

I'm So Sorry, FAILED

Hi cdob,


How did you prepared the 2GB, 4GB and 8GB drive?
I always prepare the disks using the Batch file "USB_MultiBoot_10.cmd" option 2

Did you copy files from 2GB to 4GB drive?
NO, for every stick, i'm doing the whole procedure from scratch.

Did you run MULTIBOOT_USB_10 to each drive?
Yes, i'm doing the tests separately.

A correct migrate.inf should be added that way?
this is what i'm going to test also tomorrow as i failed in BOOT_ISO_LOADED.

Well, NOW you should see WHY:
1 problem=1 thread=1 method=1 solution (hopefully ) would have been faster and is advised.

Happy this one is solved.

jaclaz

@jaclaz

today, i tried again with the same solution againest two labtops and is the results:

1 - I run the "usbHistory.exe" again with the below result for the SD card.
(3) --- Generic- Multi-Card USB Device

instanceID: 00000
ParentIdPrefix: 7&d7f206a&0
Last Mounted As: \DosDevices\H:
Driver:{4D36E967-E325-11CE-BFC1-08002BE10318}\0002
Disk Stamp: 10/17/2009 00:43
Volume Stamp: 11/08/2009 02:54

instanceID: 20071114173400000&0
ParentIdPrefix: 7&24e8d74f&0
Driver: {4D36E967-E325-11CE-BFC1-08002BE10318}\0001
Disk Stamp: 10/17/2009 00:43
Volume Stamp: 10/17/2009 00:46
2 - I run the "MkMigratgeInf_c.cmd" and generate MIGRATE.INF
3 - I run your batch file against the generated MIGRATE.INF and i got "7&d7f206a&0"
4 - I copied the Assured "MIGRATE.INF" to the "$WIN_NT$.~BT" folder over the SD.
5 - I tested the windows setup using the "AsusEee" and i successfully got Drive U:
6 - When i tried the same for "Acer5738" unfortunately, i got drive D:

What you think?

again, the blank screen

The Acer5738 does map the drive different, e.g. as a USB floppy.
Or the BIOS set a fixed drive to the SD card at boot.
Hence the blank screen at ISO RAM load approach too.

Does exist a BIOS option to force USB hdd to the SD Card?

No, there is no options in bios for such funtion.
the only thing available is to choose the periority boot and the SATA mode (SATA or IDE) for the Hard Disk.

realy i got mad with this Labtop, it is suppose to be a new bios because it is new.


also, why the same happened to Memory Stick (Flash Memory)?
may be it is dealing defferently for ISO loaded that way.

It seems like the SD card gets two Parent Id's.
The Migrate.inf (rightly) gets 7&d7f206a&0.
This ParentIdPrefix is "understood" by the "AsusEee" rightly, but evidently NOT by the "Acer5738".
My guess is that it's something BIOS related.
Or maybe the "Acer5738" uses a different way to enumerate devices.

What happens, once the XP - one way or the other - is installed on the "Acer5738"?
What ParentIdPrefix does the SD card gets on the "Acer5738" already running XP?
Still the same 7&d7f206a&0 ?

Use this "updated" batch:


Is the SD card partitioned, right?

If the "Acer5738" thinks that the SD card is a "Fixed" Hard Disk, INSTEAD of ParentIdPrefix it will use Disk Signature in the MBR to identify it.

It costs nothing to try adding to MIGRATE.INF a mapping for the Disk Signature as "V:\" and see what happens.

Read the thread that "started it all":
http://www.911cd.net/forums//index.php?showtopic=19663

Add to MIGRATE.INF these lines:

Replacing the ww,xx,yy,zz values with the ones you can get by peeking with a hex/disk editor in the MBR or using a tool like MBRfix to read the SD card signature.

jaclaz

Once again. It's rather confusing still.
Which laptop give this result?
Can you run usbHistory.exe at both laptops?

Is this (3) the internal USB card device? http://www.msfn.org/board/index.php?s=&...st&p=891644
Is this a external USB card device?


Did you used one SD card at two different Card devices?
Try one migrate.inf for the "AsusEee" and another migrate.inf for the "Acer5738".

Yes, a BIOS update is recommended http://customercare.acer-euro.com/customer...&IType=JV50

More strange, Acer offers Realtek Card Reader drivers. RTS5121.inf contain the string "USB Mass Storage Device".
Which OS do you use at "Acer5738" currently, XP, Vista or other?
Does you windows use a windows default driver or a realtek RTS5121.sys driver?

You can try Install XP from SD card without booting from SD card, but instead boot all the time from the same drive,
being your internal harddisk on which you want to install XP.

First prepare your SD-card with Make_USB.exe using Format Stick and FAT FileSystem.
Then after booting with LiveXP BootSDI.img RAMBOOT Image, you can prepare your internal HDD for Install of XP,
using USB_XP_Setup.exe of U_XP_SET package and where XP Setup will be able to use the XP Setup Source located on SD-card.

NOT booting from USB or SD has great advantage and can make quite a difference.
There is no confusion anymore, since your boot device in XP Setup is always the same, e.g. your internal HDD.

More Info:
http://www.msfn.org/board/install-xp-usb-a...sb-t121446.html

That's exactly what i'm thinking too.

1 - Yes still the same 7&d7f206a&0
2 - i installed another windows XP SP3 on Acer5736 in second partition (D:) using Stick 2GB in order to get a clean windows with Drive U: and the surprise for me is ParentIdPrefix still = 7&d7f206a&0 using both brevious batch files supplied.

I'll use it and get back to you

No, i'm just using the "MULTIBOOT_USB_10.cmd" with option (H) to format the whole stick and it boots fine.

I'll do this also and get back to you as i'm talking to you now using the HP500 labtop in order to have other labtops free for testing (Acer5738 and Asuseee).

Well, then WHAT DO YOU THINK the "MULTIBOOT_USB_10.cmd" with option (H) does?

jaclaz

I already did a similar case before in order for me to test more cases and to be ready for any time to install XP SP2/3 on any labtop/PC using different possible solution (Stick/SD).

So, your suggesion is acceptable and can help in case (IF I JUST WANT TO INSTALL A WINDOWS XP).
But what i wanted to do is to try a new way for having Setup files applicable from any where to any where, hence i got the 'MULTIBOOT_USB_10" and i was so happy to play with it on my all labtops, but unfortunately, when i tried to install using Sticks/SD with it, I chocked with the results and i'm trying with all of you to come over that.

I didn't went thru the code for this batch file yet, i'm currently prepare the reply for your Questions and the Questions for cdob along with testing the all possible cases on both (Acer5738 and AsusEee) because they are the only labtops having Built in card reader.

You don't need to go through the code.

I will rephrase once again

Given this:


WHAT DO YOU THINK the HP USB Disk Storage Format Tool V2.0.6 does?

jaclaz