[jaclaz]

robekia, on Nov 5 2009, 09:41 PM, said:

i still insist (THERE IS ALWAYS A SOLUTION).

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

[cdob]

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.

robekia, on Nov 5 2009, 08:05 AM, said:

i have 5 labtops at my home (AsusEee, HP500, HP530, Acer1640 and Acer5738)

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

[robekia]

ilko_t, on Nov 6 2009, 05:13 AM, said:

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?

Exactly.

[robekia]

cdob, on Nov 6 2009, 12:12 PM, said:

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

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

[robekia]

jaclaz, on Nov 6 2009, 11:52 AM, said:

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

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

This post has been edited by robekia: 06 November 2009 - 07:15 AM

[cdob]

robekia, on Nov 6 2009, 07:27 AM, said:

The answer for all is "Acer5738"

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

[robekia]

Quote

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

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.

Quote

Do you use a external USB Card reader?

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

Quote

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

They are always the same as i attached previously the Generated files
i'm attaching them again for reference:
 usb_history.txt (1.57K)
Number of downloads: 2  MIGRATE.INF (722bytes)
Number of downloads: 4

Quote

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

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

[jaclaz]

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

This post has been edited by jaclaz: 06 November 2009 - 07:27 AM

[robekia]

jaclaz, on Nov 6 2009, 04:26 PM, said:

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

Exactly

Quote

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)

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

Quote

You still have the 2Gb stick, do you?

yes i still have

Quote

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

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

Quote

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.

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

[jaclaz]

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:

 
@ECHO OFF
::migrate2txt.cmd rudimental batch to extract ParentIdPrefix from migrate.inf file
::by jaclaz ALPHA 0.01 Release 6th November 2009
SETLOCAL ENABLEDELAYEDEXPANSION
SETLOCAL ENABLEEXTENSIONS

SET TEXT=
FOR /F "skip=7 tokens=* delims=" %%A IN (MIGRATE.INF) DO (
SET UNICODE=%%A
)
SET UNICODE
ECHO.
SET SPACESUNICODE=%UNICODE:,= %
FOR %%? IN (%SPACESUNICODE%) DO (
IF NOT %%?.==00. (
CALL :bin2txt %%?
SET /P Var=!s!<NUL
SET TEXT=!TEXT!!s!
)
)
CLS
SET UNICODE
ECHO.
SET TEXT="%TEXT:@=&%"
SET TEXT=%TEXT:§=?%
SET TEXT
ECHO.
SET Prefix="\??\STORAGE#RemovableMedia#"
SET BEGIN=%TEXT:~0,28%"
IF %BEGIN%==%Prefix% SET ParentIdPrefix="%TEXT:~28,11%"
SET ParentIdPrefix
GOTO :EOF

:bin2txt
Set s=%1

For %%A In (
23# 26@ 2D- 300 311 322 333 344 355 366 377 388 399
3A: 3B; 3D= 3F§ 41A 42B 43C 44D 45E 46F 47G 48H 49I
4AJ 4BK 4CL 4DM 4EN 4FO 50P 51Q 52R 53S 54T 55U 56V
57W 58X 59Y 5AZ 5B[ 5C\ 5D] 61a 62b 63c 64d 65e 66f
67g 68h 69i 6Aj 6Bk 6Cl 6Dm 6En 6Fo 70p 71q 72r 73s
74t 75u 76v 77w 78x 79y 7Az 7B{ 7D}
) Do Call :DoPairs %%A
GOTO :EOF

:DoPairs
Set _=%1
Call Set s=%%s:%_:~0,2%=%_:~2,4%%%
Goto :EOF 

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

jaclaz

This post has been edited by jaclaz: 06 November 2009 - 10:30 AM

[robekia]

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
 Results1.jpg (121.3K)
Number of downloads: 13

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

This post has been edited by robekia: 06 November 2009 - 11:14 AM

[jaclaz]

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

[robekia]

jaclaz, on Nov 6 2009, 08:39 PM, said:

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.

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?

[jaclaz]

robekia, on Nov 6 2009, 06:52 PM, said:

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

This post has been edited by jaclaz: 06 November 2009 - 12:09 PM

[robekia]

jaclaz, on Nov 6 2009, 09:09 PM, said:

Since you keep doing the three card shuffle:
http://en.wikipedia....hree-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

This post has been edited by robekia: 06 November 2009 - 02:31 PM

[jaclaz]

robekia, on Nov 6 2009, 09:31 PM, said:

beleive me i was confused

I do believe you, rest assured.

PRELIMINARY STEPS:

• Open a drawer.
  
• Put inside the drawer the 2G stick AND the SD card.
  
• Close the drawer.
  
• Lock it.
  
• 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 :

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

jaclaz

[robekia]

SORRY.
I WROTE THIS REPLY BEFORE READING YOUR LAST REPLY


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?

This post has been edited by robekia: 06 November 2009 - 03:01 PM

[jaclaz]

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:

Quote

::migrate2txt.cmd rudimental batch to extract ParentIdPrefix from migrate.inf file

(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

[ilko_t]

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.

[robekia]

@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?

This post has been edited by robekia: 06 November 2009 - 03:23 PM