37 replies to this topic

[ktp]

@jaclaz, unfortunately the migrate.inf (taken from indicated link assigning drive letter U: to the stick) did not solve the problem.
I am really stuck; My idea was that bcdw 2.01 patches on the fly \i386\setupldr.bin, the \i386 is copied from an XP CD.
So on the USB key we need to patch statically \i386\setupldr.bin, but what to patch? I have to go by successive tries
(patch minint string, then $WIN_NT$.~BT stuff., now I run to the CD detection problem.

Unfortunately we don't have bcdw source code (no news from the author) to understand what bcdw does.
The direction taken in thread http://www.911cd.net...showtopic=14181 seems too complicated for me.

[Garfield]

@ktp

I have some time ago created a Multi OS CD containing 4 versions of windows XP loading from different folders (XPP2, XPH2, XPUP, XP) booting from BCDW and it works like a charm.

I only had to change \I386\ in both BOOTSECT.BIN and SETUPLDR.BIN to get it going. But in the relevant folders (XPP2, XPH2, XPUP, XP) you copy just the boot part of the bluescreen setup (4 boot stiffies) and create an i386 folder with the rest of the CD\i386 contents.

It was more than a year ago that i did this but if you want i will dig up the relevant documents...

[was_jaclaz]

Hmmm, what I can say is that if it were an easy to do thing, most probably it would have been already done.

What I would do:
1) Sleep a few nights over this, more often than not when you don't think too much to a problem, the solution comes up by itself.
2) If I were you, I would re-start from scratch along these lines:
a. forget for the moment the multibooting part, just try with a "standard" \I386 folder
b. try with a ntldr like the one gray suggested here:
http://www.911cd.net...o...3784&st=249
c. Also, check the report diddy made here (1st drive important?):
http://www.911cd.net...o...18031&st=34
3) I don't think that info in Dietmar's thread has any relevance when we are talking about installing, the only part that may come handy as I see it is the modified ntdetect.com, however the procedures by Dietmar (and others) are listed in this post of mine:
http://www.911cd.net...o...181&st=1988
besides the new one just posted:
http://www.nedprod.c...uff/BootWinUSB/
They are not too difficult, but if you try the "automated" way from
http://www.usboot.org/
it's a breeze.

jaclaz

[ktp]

@ktp

I have some time ago created a Multi OS CD containing 4 versions of windows XP loading from different folders (XPP2, XPH2, XPUP, XP) booting from BCDW and it works like a charm.

I only had to change \I386\ in both BOOTSECT.BIN and SETUPLDR.BIN to get it going. But in the relevant folders (XPP2, XPH2, XPUP, XP) you copy just the boot part of the bluescreen setup (4 boot stiffies) and create an i386 folder with the rest of the CD\i386 contents.

It was more than a year ago that i did this but if you want i will dig up the relevant documents...

OK thanks Garfield, I also have information on this by examining other Multiboot AIO DVD. The bootsect.bin technique unfortunately applies only for CD, so it is not applicable to USB boot. In fact we miss bcdw functionality for USB boot. If ever bcdw supports USB boot, it would be universal !

[was_jaclaz]

The bootsect.bin technique unfortunately applies only for CD, so it is not applicable to USB boot.

Just for the record, you can use grub4dos on USB sticks with the same results.

Title /I386

chainloader /I386/setupldr.bin



Title /XPP2

chainloader /XPP2/setupldr.bin



Title /XPH2

chainloader /XPH2/setupldr.bin



......

jaclaz

[Garfield]

Sorry what i was actually trying to say wasthat when it asks for the winXP CD it might be looking for an I386 folder inside your XXXX folder.

But in the relevant folders (XPP2, XPH2, XPUP, XP) you copy just the boot part of the bluescreen setup (4 boot stiffies) and create an i386 folder with the rest of the CD\i386 contents.

[ktp]

Thanks Garfield, I already did this before, I.e. I have \PRO1 and \PRO1\I386.. Even \PRO1 has all \I386 from CD and same for \PRO1\I386. All setupldr.bin have been patched !

My other failed experience was with \PRO1 content filled with XP boot diskettes (6 diskettes), and \PRO1\I386\ content from CD, with setupldr.bin patched. Same error.

@jaclaz
I already starting from scratch with \I386 without name patch, still same problem. In fact if you use XP recovery console, instead of pressing R to repair you press Enter = install, got same problem that setup require CD. The recovery console is similar to XP install but it does not allow running command ! so I cannot try winnt32.exe.

I wil however take your advice and try other things, starting from scratch with simpler objectives.

[Garfield]

Booting form USB HDD i got to WinXP Blue screen setup disk partitioning..
No need to hack anything yet...

EULA displays fine....

I don't have the GRUB loader to change my boot sequence so usb hdd is still seen as primary disk...

Some more testing...

What was the thing about Migrate.inf.... i am not a member of MSFN forum so i can't download the file

And i don't have online internet at home, only dial up, which is almost useless....

Can someone please get me some info on changing the boot sequence so i can test @ home over the weekend

[Garfield]

Blue screen setup passed successfully....

In gui setup got to a screen saying ASMS files needed

Just like in porear's post http://www.msfn.org/...s...1384&st=22#

[ktp]

Blue screen setup passed successfully....

In gui setup got to a screen saying ASMS files needed

Just like in porear's post http://www.msfn.org/...s...1384&st=22#

Wow, congratulations, I'm still at the dialog need the XP CD, press a key But this is USB key, which is different from USB hard disk.
Following is the migrate.inf I got if ever you need it :

[Version]

Signature = "$Windows NT$"

 

[Addreg]

HKLM,"SYSTEM\MountedDevices",,0x00000010

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,00,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,64,00,64,00,65,00,34,00,37,00,39,00,65,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,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

The more the merrier on the bandwagon of XP install from USB key

[Garfield]

Have a look at generating your source by booting from dos, loading cdrom driver, in XpSource CD\i386 run WINNT.EXE /s:%CDromDriveLetter:%, where %CDromDriveLetter:% is your cdrom drive letter

This should create $WIN_NT$.~BT and $WIN_NT$.~LS on your hdd...

Beware this might change your hdd bootsector and boot.ini so rather disconnect your hdd and do on an empty fat32 partition

Garfield signing off for the weekend

[ktp]

OK but this is method #1, already eplored. I am exploring method #3 (number after jaclaz).

[Elad Karako]

A very simple way to do this is by using WinImage:
(after install & run it:)

{under "Disk" Menu}

1. click "Disk" and choose your removable drive (a "v" will mark it from now).
2. click "Read Disk".

{wait till' it's over}

3. "File"->"Save As..."


default is ima / img
you can also make ISO file from it
{reopen and Search for "ISO SAVE" or somthing similar...}

Elad Karako