Jump to content

Install XP from a RAM loaded ISO image

cdob

By cdob
in Install Windows from USB

 Share

Recommended Posts

laddanator

laddanator

Posted
Posted (edited)
Yes, the question was because the snippet you posted seems like a "badly" formed one (bad copy/paste, typo, random attempt?:w00t:).

Wasn't entirely random. We are also talking about it here

and I knew cdob would know what I was talking about but I guess that doesn't help anyone else much. :ph34r:

so that's why it seems random here. :wacko:

If you run that you get in Registry:

a key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FiraDisk

with in it a REG_SZ named "StartOptions" CONTAINING "StartOptions=cdrom,vmem=find:/images/winsetup.iso"

What you want INSTEAD is more probably:

a key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FiraDisk

with in it a REG_SZ named "StartOptions" CONTAINING ONLY "cdrom,vmem=find:/images/winsetup.iso"

Will give this a whirl. Thanks, jaclaz

Edited by laddanator

laddanator

laddanator

Posted
Posted (edited)

Registry.jpg

What you want INSTEAD is more probably:

a key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FiraDisk

with in it a REG_SZ named "StartOptions" CONTAINING ONLY "cdrom,vmem=find:/images/winsetup.iso"

I added the above as you suggested (this is just a test inside a running machine)

Just doesn't look right to me. Should there be more in the registry for firadisk to find the ISO after reboot on an install?

Edited by laddanator
jaclaz

jaclaz

Posted
Posted

Just doesn't look right to me. Should there be more in the registry for firadisk to find the ISO after reboot on an install?

Well, it does look BETTER to me. :angel

I have NO idea whether it will help you :ph34r: , or will ever do what you are trying to do :w00t: , or of if the contents are "right" or if anything else is needed, it is simply (now) compliant with existing examples, compare with:

http://diddy.boot-land.net/firadisk/files/disk4.htm

http://reboot.pro/8804/page__st__401

BTW, please notice what karyonix himself says in the above:

"file=find:\xxx" does not work, use drive letter.

jaclaz

laddanator

laddanator

Posted
Posted (edited)
Well, it does look BETTER to me.

Sorry, didn't mean to say what you suggested was wrong...just figured it would be a bigger add

BTW, please notice what karyonix himself says in the above:

Quote

"file=find:\xxx" does not work, use drive letter.

Yes but the reboot pro link you gave (will have to find exact post) some examples do not have the drive letter. Since DP sets drive letter as %CDDRIVE%, I also tried this

in the presetup.cmd 

reg add HKLM\SYSTEM\CurrentControlSet\Control\FiraDisk /v StartOptions /t REG_SZ /d "cdrom,vmem=find:%CDDRIVE%/XP/ISO/HOME.ISO"

but didn't accomplish my goal.

Edited by laddanator
laddanator

laddanator

Posted
Posted

Just notice my slashes are the wrong way

reg add HKLM\SYSTEM\CurrentControlSet\Control\FiraDisk /v StartOptions /t REG_SZ /d "cdrom,vmem=find:%CDDRIVE%/XP/ISO/HOME.ISO"

g4d uses the slashes that way. Should be

reg add HKLM\SYSTEM\CurrentControlSet\Control\FiraDisk /v StartOptions /t REG_SZ /d "cdrom,vmem=find:%CDDRIVE%\XP\ISO\HOME.ISO"

laddanator

laddanator

Posted
Posted

maanu, post 250 sums it up. Just have to expand your setup.exe and add it to the new IMA as described on the first page and use, cdob menu.lst from post 250

cdob

cdob

Posted
  • Author
Posted (edited)
I would add the chainloader line as below

chainloader (222)/I386/SETUPLDR.BIN

Thanks, this is a good idea at a default image.

What about a multi boot iso image without /I386/SETUPLDR.BIN ?

What about 

ls (222)BOOTFIX.BIN && chainloader (222)/I386/SETUPLDR.BIN
ls (222)/I386/BOOTFIX.BIN || chainloader (222)

map --mem /images/XP_INST.IMA (fd0)

map --mem /images/XP_INST.IMA (fd1)

write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/images/winsetup.iso;floppy,vmem=find:/images/firadisk.img;\n\0

At second glance this is broken: firadisk search firadisk.img at a disk, but there is RAM loaded floppy used too.

Should be:

write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/images/winsetup.iso;\n\0

Can you test this at real hardware?

Much simple menu.lst than mine.

But you have more testing hardware.

I'm used to one hard disk (read: BIOS maps target hard disk as hd1 at USB boot) and one usb drive. Any map (hd?) real experince is highly welcome.

FiraDisk StartOptions is in investigation.

Remember the name: a start option is valid at start: at firadisk driver start.

Firadisk is running after reboot already. A simple registry add won't work after driver is started.

And firadisk is marked as a boot driver: a net stop is rejected.

At a addional reboot there is a drive load order and drive intialization.

USB drivers has to be loaded, initialized, USB drive available. Next firadisk could find a file.

Unfortunately different hardware may gives different timing results. A solution may work at known hardware, but fail at other hardware.

At second glance: a driver pair firadisk/imdisk gives predictable timing. Should work at more machines.

Edited by cdob
laddanator

laddanator

Posted
Posted (edited)
Thanks, this is a good idea at a default image.

What about a multi boot iso image without /I386/SETUPLDR.BIN ?

What about

ls (222)BOOTFIX.BIN && chainloader (222)/I386/SETUPLDR.BIN

ls (222)/I386/BOOTFIX.BIN || chainloader (222)

That will work. I do my multiboot ISO a little different (don't use BOOTFIX.BIN). I hex edit my setupldr.bin to change the path of the boot folder(can only use 4 letters or number). I use the same mod setupldr.bin over and over..only has to be hexed once...I could do a whole write up on this but I will try not to go off-topic

Much simple menu.lst than mine.

But you have more testing hardware.

I'm used to one hard disk (read: BIOS maps target hard disk as hd1 at USB boot) and one usb drive. Any map (hd?) real experince is highly welcome.

Didn't mean to say your was simple as in lame :lol: but for someone who is new to this, meant its easier to understand. I use a mod BOOTWS folder with the firadisk ISO loads.

Firadisk is running after reboot already. A simple registry add won't work after driver is started.

Been testing all day and I am going to put this registry thing on the back burner (given me a headache) since the 1 boot to USB method is working with your IMA stuff, all is good...besides I still have winsetupfromusb which I hear may be getting a newer release.

Should be:

write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/images/winsetup.iso;\n\0

Can you test this at real hardware?

Tried this before but didn't have any luck but that was before your IMA file with setup.cmd. Will try now.

Been testing the new XP_INST.IMA today on my Asus M4A88TD-M/USB3 with three internal HD. The BOOTWS mod has come in nicely. All three XP (Home-Pro-MCE) have installed fine. Will test on Dells tomorrow at work.

Also I use variables so that I can use one XP_INST.IMA and much easier to write ISO name on the fly. Under each menu title I have this 

set XPISO=HOME.ISO
set Image=XP.IMA

set XPISO=PRO.ISO
set Image=XP.IMA

set XPISO=MCE.ISO
set Image=XP.IMA

So end result looks like this 

write --offset=0 (fd0)/setup/ISOimage.ini \\XP\\ISO\\%XPISO%\n;\n;\n;
write --offset=0 (fd1)/setup/ISOimage.ini \\XP\\ISO\\%XPISO%\n;\n;\n;
write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/XP/ISO/%XPISO%;floppy,vmem=find:/XP/Floppy/%Image%;\n\0

UPDATE

@cdob, just finished an install with PRO and only used this line 

write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/XP/ISO/%XPISO%;\n\0

so now this line is not needed

floppy,vmem=find:/images/firadisk.img;\n\0

Also I guess it would be a good idea to remove the firadisk driver and imdisk. I saw in the setup.cmd you have a line to remove Imdisk but not firadisk. Did I miss something? If not might not be a bad idea to add it to the cleanup section.

Something like this 

devcon remove *\firadisk
del %WinDir%\system32\drivers\firadi*.sys

Edited by laddanator
laddanator

laddanator

Posted
Posted (edited)

Text setup mode runs really slow on a older computer with this method as would if loaded from the actually CD. Wonder if the small ISO trick could be map to mem to say (0xFF) and after reboot to start GUI , cdob's, new setup command would run and mount the big ISO and finish install? Just to speed up text setup mode?

If the path to the big ISO has been written to the ISOimage.ini...don't see why not

Edited by laddanator
cdob

cdob

Posted
  • Author
Posted
Text setup mode runs really slow on a older computer with this method

Which old hardware do you use?

Is a USB 2.0 controller available?

Does BIOS enable USB 2.0 speed at USB boot?

Loading a file to RAM may take some time.

Actually there are two textmode parts.

First: boot to user selectable target drive.

Second: Copy files to hard disk

Which part(s) refers to slow on a old computer?

Which time does it take? Name minutes and seconds.

Wonder if the small ISO trick could be map to mem
Which files are inside this ISO image?

A tiny ISO trick will fail.

If a small ISO contains first boot files to user selectable target drive, then first boot can be faster.

Following parts may work or fail.

It's possible to RAM load recovery console and install from flat file at same ISO file.

Compare recovery console part

If the path to the big ISO has been written to the ISOimage.ini...don't see why not
There is a missing gap between tiny ISO file and ISOimage.ini.

Firadisk may map small ISO file and big ISO file.

And windows setup may boot from small ISO.

Next search files inside small ISO to copy to hard disk. However there are no files inside

How to satisfy setup?

laddanator

laddanator

Posted
Posted
Which old hardware do you use?

Is a USB 2.0 controller available?

Does BIOS enable USB 2.0 speed at USB boot?

Old P3 with gig of ram. CD install of text mode setup doesn't go any faster (I timed it) No USB 2. USB 1.0 so of course this will be slower. I must like making more work for myself :blink:

Which files are inside this ISO image?

Haven't got that far. I will stick with what's working and leave the small ISO out of the mix for now.

Actually there are two textmode parts.

First: boot to user selectable target drive.

Second: Copy files to hard disk

Which part(s) refers to slow on a old computer?

Which time does it take? Name minutes and seconds.

About 3 min or so to run first txt setup part (same as CD on this machine) . Coping the files is faster (didn't time that part)

Next search files inside small ISO to copy to hard disk. However there are no files inside

How to satisfy setup?

Some how after the small iso being mapped to (oxff) and when text setup part1 finishes..loads files from the mapped big ISO (222). Sounds crazy but I have done crazier! :sneaky:

  • 2 weeks later...
mexus

mexus

Posted
Posted (edited)

Can you please tell me how to use mkISO_RAMload_sort.cmd.

Never mind found it on a previous page, moderator please delete this post.

Edited by mexus
Oct

Oct

Posted
Posted (edited)

Hi

PLEASE HELP

I have an error at the Beginning of the text base setup. I get the blue windows setup screen, I get the "Press F6 ....", then the "Press F2 ....." but then it fails with the message below, i.e the full iso is loaded into the RAM then XP text based setup starts to loads but stops before loading any of the files.

I then get the error:

Please insert the disk labelled

Windows XP Professional Service Pack 3 CD

Into Drive A

Press enter when ready

Have i missed a step or something obvious ??

Is it a setting I need to modify to point to the ISO loaded into RAM ?

Please help, and thanks ...

post-346388-0-43968400-1328198137_thumb.

Edited by Oct
  • 3 weeks later...
cdob

cdob

Posted
  • Author
Posted

v06 major redesign

One driver only - firadisk

no need to include setup.exe in floppy image

Driver firadisk is used within installation. And disabled at end of installation.

A sample menu.lst is included.

Usage examples:

1: simple case, friendly BIOS - try this first

ISO contents read from USB disk, not loaded to RAM.

2: strange USB BIOS or hardware - adds a reboot if necessary

ISO contents read from USB disk, not loaded to RAM.

3.map : small map RAM loaded boot files

ISO image created by mkISO_RAMload_sort.cmd

Loads textmode boot part to RAM, about 10-20mb data. This includes recovery console.

Other files are read by windows drivers at USB 2.0 speed

Prefer at USB1.x BIOS speed

3.dd: small dd RAM loaded boot files

Uses dd to copy data.

Lower speed, a fargmented ISO image possible.

4: RAM loaded install files

ISO image created by mkISO_RAMload_sort.cmd

Loads textmode boot and copy part to RAM

Fastest approach at USB 2.0 BIOS speed

5: RAM load ISO image

simple approach, use a existing ISO image

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...