|
|
| Post Number: 1
|
EB1000 
Group: Members
Posts: 93
Joined: Oct. 2009
|
 |
Posted on: Jun. 01 2010,16:19 |
|
   |
@ balder
I want to load an image I've created with ETboot. I'ts a universal XP image called myxp.img. I was able to discover a nice trick to load it myself. I've compressed the image as a CAB archive and renamed it XP.CA_ I cipied this image into hiren HBCD folder. replacing the original minixp also stored as XP.CA_, booted using the usual bcdw /hbcd/isolinux.bin command, and now when I select minixp from Hiren's menu, my universal image loads into ram instead of Hiren's. I assume there if a direct way of of loading and *.img image file using ezboot and a grub4dos image. Do know how? also, could i load a compressed image like myxp.zip or myxp.gz ?
Thanks
|
 |
|
|
| Post Number: 2
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Jun. 02 2010,16:11 |
|
 |
@ EB1000
Quote: “It's a universal XP image”
If I understand you right – this is a kind of “Live-XP” – like BartPE. Am I correct?
But it’s created as an “Image-file”. Correct? And it is run from RAM
To make it simple I have created “attachment” for download HERE
Extract downloaded zip-file and you get a folder “myiso” 
Copy your “XP image” (XP.CA_) into folder i386 in “myiso\iso_root”
Note1: you can also use my script “easyboot-cab” to make cab to image files (highly recommended) as this reduce size to image.
Note2: check that name to reduced image-file is the same as in path in text-file winnt.sif (winnt.sif in folder “myiso”):
OsLoadOptions="/noguiboot /fastdetect /minint /rdexportashd /rdpath=\i386\xp.ca_"
As you can notice in this case: “xp.ca_”
Double-click to “create_iso.bat” in folder myiso” and a new ISO-file is created in folder “myiso” with the name “my_iso.iso” 
Quote: “could i load a compressed image like myxp.zip or myxp.gz”
Basically – No you cannot. You need setupldr.bin and Ntdetect.com and winnt.sif to launch image to RAM. However my solution above works fine.
Note: You can use easyboot-iso.script to directly launch created ISO-file (my_iso.iso). You even don’t need to check “Run from RAM” – it works anyway, as this kind of file is launched from RAM internally 
Regards balder
--------------
Download complete set of scripts including help file HERE
Note: Script collection updated 2019-05-19. Scripts mainly support EasyBoot_6.5 or later
|
|
|
|
| Post Number: 3
|
EB1000
Group: Members
Posts: 93
Joined: Oct. 2009
|
|
Posted on: Jun. 02 2010,20:20 |
|
|
thank you so much for finding the time to do this. I have not tried it yet, I will tomorrow and let you know. But bare in mind that the myxp.img is not an ordinary live xp that load from ram. It was created using the ETboot project:
http://www.boot-land.net/forums/?showtopic=3890
which means that the ram loaded image is actually a modified image of windows xp that do not have a i386 folder inside, it has a Windows folder along with program files and the usual documents and settings, etc.. it is a full Windows installation booted from cd... Will your attached script still work on an image that does not contain i386 folder inside it? (system32 is found inside the usual windows folder)
many thanks for the help!
Edited by EB1000 on Jun. 02 2010,20:20
|
|
|
|
| Post Number: 4
|
EB1000
Group: Members
Posts: 93
Joined: Oct. 2009
|
|
Posted on: Jun. 02 2010,21:48 |
|
|
OK i tried your script, windows started to load the image to ram during boot, but them i got the error that \i386\system32\biosinfo.if was not found.. of course, this inside my image is located at windows\system32\ on i386. I only guess that SETUPLDR.BIN needs some hex editing/patching to change some i386 into "windows"
Remember, my XP.IMG is an actual real life windows xp pro sp3 disk image with many software installed and windows was modified to become "universal" it knows to load drivers during boot, it knows that it is being run from ram...
here is some more info:
inside the XP.IMG there are the following:
i386 - with only txtsetup.sif inside it that has the line : DefaultPath=\WINDOWS
a windows folder with many sub folders and files
a program files folder with all installed software
file named modelram.exe in the root of xp.img
the size of xp.img is 1.8GB
Thanks
|
|
|
|
| Post Number: 5
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Jun. 03 2010,04:54 |
|
|
@ EB1000
Quote: “needs some hex editing/patching”
I don’t think we need to do any hex edit. It did launch.
In fact - I’m getting more and more unsure what this is for kind of “Live-system” 
It looks to be created using “Winbuilder”.
Test this:
Test this:
1. Copy folder i386, the “windows folder” and finally ”modelram.exe” to easyboot\disk1
2. Copy setupldr.bin and Ntdetect.com to inside of folder i386
3. Use menu command in easyboot: run W2ksect.bin
Create this huge ISO and see what’s happening
We need to do this to figure out what this is.
I tested using “Mini-XP” from Hiren and that works greate
Note: I cannot help you with this type of large files anyway – my computer doesn’t have that “power” 
Regards balder
Edited by balder on Jun. 03 2010,07:04
--------------
Download complete set of scripts including help file HERE
Note: Script collection updated 2019-05-19. Scripts mainly support EasyBoot_6.5 or later
|
|
|
|
| Post Number: 6
|
EB1000
Group: Members
Posts: 93
Joined: Oct. 2009
|
|
Posted on: Jun. 03 2010,09:23 |
|
|
Thanks, I will give it a try. did you check the link I gave you about ETboot? it is very interesting and useful.. imagine that you can boot your entire xp system with all the drivers for your hardware and the installed software + setting into ram from a dvd-rom.. This is just like booting a Ghost image of your system drive..
Regards
EB
Edited by EB1000 on Jun. 03 2010,09:23
|
|
|
|
| Post Number: 7
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Jun. 03 2010,09:27 |
|
|
@ EB1000
Quote: “imagine that you can boot your entire xp system with all the drivers”
I’ll take a look into it
Regards balder
--------------
Download complete set of scripts including help file HERE
Note: Script collection updated 2019-05-19. Scripts mainly support EasyBoot_6.5 or later
|
|
|
|
|
|
