[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

[ilko_t]

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

[robekia]

ilko_t, on Nov 7 2009, 12:33 AM, said:

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?

[ilko_t]

One of the many possible ways:

1) Extract contents of the new Firadisk somewhere
2) Install ImDisk:
http://www.ltr-data....ode.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?

[robekia]

ilko_t, on Nov 7 2009, 12:50 AM, said:

Simple?

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

Thanks you All

[cdob]

robekia, on Nov 6 2009, 04:36 PM, said:

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

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?

[robekia]

robekia, on Nov 7 2009, 12:56 AM, said:

ilko_t, on Nov 7 2009, 12:50 AM, said:

Simple?

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

Thanks you All

I'm So Sorry, FAILED

[robekia]

cdob, on Nov 7 2009, 01:08 AM, said:

robekia, on Nov 6 2009, 04:36 PM, said:

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

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?

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.

This post has been edited by robekia: 06 November 2009 - 05:36 PM

[jaclaz]

robekia, on Nov 6 2009, 10:20 PM, said:

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

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

[robekia]

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

[robekia]

ilko_t, on Nov 7 2009, 12:33 AM, said:

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

again, the blank screen