Forum: EasyBoot
Topic: Live XP as wim file
started by: EB1000
Posted by EB1000 on May 25 2010,06:30
@Dear balder

I came across a very useful and robust version of windows xp live sp3. The iso root includes grun4dos grldr and menu.lst and a text file named root.TAG, along with drivers.wim and legacy.vmdk image files. also there is a folder named IMAGES. inside this folder there are the following files:

1. the main live xp image named XP.WIM (inside there is I386 etc..)

2. SETUPLDR.BIN

3. XPBOOT.IMG

the menu.lst loads live xp using the following commands:

find --set-root /ROOT.TAG
chainloader /IMAGES/SETUPLDR.BIN


I tried to load it using the map iso grub method, just like with Acronis boot disk, but it did not work. is there a way to boot this using ezboot? There is one more problem. in this multiboot cd I'm trying to make, there is already a I386 folder in th root that contains another live xp version that boot using ezboot by run xpboot.bin command. This new WIMed xp live could be the best addition to my ultimate multi-live cd

Thanks

EB

Posted by balder on May 25 2010,08:09
@ EB1000

As far as I know file vmdk image files is loaded and run from “virtual harddisk” (in RAM) ???

Test this:
Copy everything from ISO-file to folder disk1 and delete grldr and menu.lst
Download compressed floppy image from < HERE >and put file as it is in folder ezboot
Use menu command in EasyBoot: memdisk xp_live.zip

Note: this is an experiment to see if it works. It’s possible that you may need to also check “Allow lower case” - but probably not needed.

You can also test to integrate ISO-file using easyboot-iso.script :;):

Regards balder
Posted by EB1000 on May 25 2010,12:55
Thank you very much for you dedicated help. Unfortunately it did not work (keep getting errors about missing txtsetup.sif, although no such file exists in the original ISO. Any way, I found different ISO packing for the same Live XP mentioned. This one uses alternative boot method (boot SDI i assume). This ISO contains the following structure:

Files:

1. BOOTSECT.BIN
2. WINNT.SIF (see sif setup at the end of this post)
3.PE_DRIVE
4.Legacy.vdmk (yes it is a VM image with many wim files inside that contain various programs that loads into a ramdisk by live xp)

The root has 2 folders:

1. Drivers (with drivers.wim inside)
2. I386 (with LiveXP.wim, NTDETECT.COM, and SETUPNTLDR.BIN)

The Winnt.sif in the root folder contains the following info:

[SetupData]
BootDevice="ramdisk(0)"
BootPath="\i386\System32\"
OsLoadOptions="/fastdetect /minint /rdimageoffset=8192 /rdimagelength=3161088 /rdpath=\I386\LiveXP.wim"

OK, this ISO will not load directly using the standard grub map-hook method. Please bare in mind that my multiboot cd already have a I386 folder with miniXP created by winbuilder by me.

Any chance to add this new live XP Wim version to my mulltiboot?

Thank you very much sir

EB

Posted by balder on May 25 2010,14:25
@ EB1000

Are you sure on the name  “SETUPNTLDR.BIN”? I guess you mean “setupldr.bin” :cool:

We can hex edit and change folder name I386 to something different.
To make sure you can hex edit correctly start with checking size of  “setupldr.bin”.
If size to file is 298096 we most likely need to patch file.
If size to file is 260784 you don’t need to patch file.
To patch file (if needed) - Make a copy of setupldr.bin to work with.
Use my scripts like (if you need to patch file): Start easyboot-aio.script and in “Manually section” push the blue button “Manually patch setupldr.bin” and just follow instructions in script.

Launch Easyboot>>Tools>>Replace text
Scroll to the file you patched (setupldr.bin)
In “Text to find” you put in i386 and in “Replace with” you put in I387 - push replace
Do the same again but in “Text to find” put in I386 (keep I387 in “Replace with”) - push replace. Now you have hex edit setupldr.bin to work in a folder with the name I387.
Note: you can use a folder name like BOOT if you find this more convenient

Make a copy of W2ksect.bin (you should have this file in folder ezboot) and rename W2ksect.bin to something more logical – like launch387.bin (or whatever)
Again Launch Easyboot>>Tools>>Replace text
Scroll to the file launch387.bin (or whatever name you use)
In “Text to find” you put in I386 and in “Replace with” you put in I387 - push replace
Now you changed launch387.bin to point to a folder I387

Rename folder I386 to I387 and change Winnt.sif to this:

[SetupData]
BootDevice="ramdisk(0)"
BootPath="\i387\System32\"
OsLoadOptions="/fastdetect /minint /rdimageoffset=8192 /rdimagelength=3161088 /rdpath=\I387\LiveXP.wim"

In Easyboot menu use command:  run launch387.bin

Regards balder
Posted by EB1000 on May 25 2010,17:18
Thanks. yes you are right it's setupldr.bin file. But non of your suggestion worked. Because it is a boot sdi loading method the file setupldr.bin is non standard file; the size of file is 318576 bytes, bigger that usual. If I try to patch and or rename, boot fails with ntldr corrupt error... maybe I should modify the other i386 folder, but this one also have txtsetup.sif and winnt.sif.. maybe more files that depend on the original i386 folder name... Is the a way to patch the setupldr.bin of the boot sdi? It seems that someone else has asked but did not get an answer at bootland:

< http://www.boot-land.net/forums....ic=2310 >

Any other suggestions will be welcomed.

Many thanks
Posted by balder on May 26 2010,02:46
@ EB1000

Quote: “the file setupldr.bin is non standard file”
Okay I understand :)
But you have created a LiveXp I quote: ”cd already have a I386 folder with miniXP created by winbuilder by me”
How about instead hex edit this one using method above. Then you have place for another folder I386 on the root – the odd one in post nr:3 ???

Regards balder
Posted by EB1000 on May 27 2010,02:52
@balder

Thanks. I discovered that I can boot directly from this Wim based ISO live xp, using Aerostudio with the following command:

grub4dos ls /ISO/LIVEXP.ISO || find --set-root /ISO/LIVEXP.ISO; map /ISO/LIVEXP.ISO (0xff) || map --mem /ISO/LIVEXP.ISO (0xff); map --hook; root (0xff); chainloader (0xff)
boot


I never tried Aerostudio before; simply because I was used to easyboot, which I already pained for.. But now I am quite disappointed, as Aerostudion seems 10 times more powerful and useful than Easyboot, and i'ts totally free... Anyway, thank you so much for the support. i was wondering, are you familiar with Aerostudio? It seems like a very easy to use software, that truly deserves the name EASYBOOT, unless there are some limitations to Aerostudio that I am not aware of... And one last question: do you work for EZB systems?

Regards

EB

Posted by balder on May 27 2010,03:37
@ EB1000

If you can use that command, you can use my script ”easyboot-iso.script” to integrate ISO-file as it is :O  
Test check and not check “Run from RAM”, to see which works the best.

Quote: “And one last question: do you work for EZB systems?”
No I’m just a humble user as you :)
And yes I’m very much familiar with AeroStudio :;):

Regards balder