45 replies to this topic

[oriensol]

Hi All,

I would like to thank Karyonix for his wonderful driver, as being discussed in the thread here: http://www.boot-land...?...pic=8804=

I am attaching a FiraDisk script for livexp. Thanks to Lancelot for the encouragement. Hope this helps.

Update on Sep.6 :

Tested the following:

BootSDI NOT used. ImDisk B: drive is part of the build.

With XP sources (versions 0.0.1.10 and 0.0.1.12) :
1. Booting Livexp from a Firadisk Livexp Iso (menu.lst):

title LiveXP-Firadisk-ISO

map --mem (hd1,0)/test_img.img (hd3)

map --mem (hd1,0)/pmagic-4.3.iso (hd32)

map --mem (hd1,0)/minlex/ISO/LiveXP.iso (0xFF)

map --hook

chainloader (0xFF)

2. Booting Livexp from cd with non-boot Firadisk defined using grub4dos.
3. Booting firadisk LiveXP.iso over network using tftpboot/grub4dos.
4. Booting from a RAM hard disk image.
5. Amalux complete package (with and without bootsdi).

With Win2k3 sources (version 0.0.1.12):
1. Booting Livexp from a Firadisk Livexp Iso
2. Booting from a RAM hard disk image.

Here's what works:

1. Booting Livexp from RAM Disk
2. Exlporer works, all partitions are recognised with drive letters
3. Non-boot RAM CD Rom works
4. Non-boot RAM Disk Works
5. Device Manager shows FiraDisk Virtual Disk Enumerator and the RAM CDRom and Disk.
6. Disk Management recognises the drives
7. Formatting the RAM hard disk works
8. Check http://www.boot-land...hl=livexp tips for Disk Management Partitioning workarounds.
8. "sc query firadisk" shows firadisk is running
9. PXE booting with tftpboot works with LiveXP.iso.


What needs to be noted:

1. The firadisk driver date and version info is suppressed from the Device Manager (to prevent frequent changes to the script). User needs to click on Driver Details to get that information.
2. When you click on the Firadisk Virtual Disk Enumerator in Device Manager, you get an error message before you can continue.
3. When booted from a Firadisk iso, there will be a dummy cdrom RAM drive in addition to X:.

When a newer version of firadisk is released, please download and use the custom file or use the available 0.0.1.12 version included in script.


Latest script attached:

Attached Files

•  vFiraDisk.zip   49.03KB   1464 downloads

[Lancelot]

Thanks oriensol,
Will test as soon as possible

[oriensol]

Sorry I had tested this with BootSDI. Without it, there seems to be an issue.

Please desist from using this meanwhile. Thanks.

[joakim]

Sorry I had tested this with BootSDI. Without it, there seems to be an issue.

Please desist from using this meanwhile. Thanks.

If you implement image creation and preparation in your script, you should be able to get it going without bootsdi (or separated into two scripts).

Or maybe it's time for a modified bootsdi script that can handle FiraDisks requirements.

Joakim

[olegpov]

Or maybe it's time for a modified bootsdi script that can handle FiraDisks requirements.
Joakim

I will agree with your opinion time has come to change BootSDI script.

[Lancelot]

Or maybe it's time for a modified bootsdi script that can handle FiraDisks requirements.

Agree, Since your finding about diskless angel it is in my mind, with FiraDisk now it is a must, need time.....

[oriensol]

I am assuming that once Karyonix is done, the CD ISO would automatically become the RAM disk, if the driver has been installed.

[joakim]

I am assuming that once Karyonix is done, the CD ISO would automatically become the RAM disk, if the driver has been installed.

I think iso mapping is already working according to Karyonix and cdob. But using that as a ramloading option only is far from uilizing its full potential. Most importantly is the disk image mapping to ram.. So it will need a complete rewrite of the bootsdi, or better a complete new one, as it will be very different and not at all similar (although techniqe is somewhat similar).

Joakim

[Lancelot]

@joakim

yes, using iso for ram booting is not a perfect solution, but definately a very practical one (I like the practical side).

sadly this dont work

title LiveXP.iso karyonix
map --mem /LiveXP.iso (0xFF)
map --hook
chainloader (0xFF)

Some time needed for bootsdi enchancements..........

edit

[joakim]

So who's gonna take the challenge?

Joakim

[Lancelot]

So who's gonna take the challenge?

Sadly me, by following your foot steps .

[joakim]

Sadly me, by following your foot steps .

That does not sound right. I mean, I could always give a helping hand, but if you where to write the actual script it would be the first free and automated way of breaking the old 512 limit, and possibly also creating live diskless systems. And that should not make you feel sad.

Joakim

[olegpov]

Sadly me, by following your foot steps .

I will watch working out and to assist

[Lancelot]

And that should not make you feel sad.

I know, As far as i remember I was the first that followed your steps with success (and full excitement ). At that times I also checked the readme of diskless angel and I "guess" distrubing it is free with including all archive (.zip)....

sad part is, I am not as good as Galapo and fxscrpt, Give me 1 day and I will pm you if i need help


edit:
@olegpov

Thanks a lot dude, I will inform you about the progress

[oriensol]

As a newbie, I can help where I can, with some guidance. Thanks.

[cdob]

I think iso mapping is already working according to Karyonix and cdob. But using that as a ramloading option only is far from uilizing its full potential.

The ISO mapping is working at 1.0.4, fails at 1.0.6 here.
ISO mapping result to a read only RAM based CD drive.
That's nice for first testings or special requirements.

Yes, a hard disk based image is prefered if you like write acess to RAM based image.

ISO RAM loading is nice at special requirements, e.g.
XP installation from a ISO image
or Boot the loop http://www.boot-land...amp;#entry24379

Just a crazy idea: map --mem (cd0) (0xFF)
Modern boot the loop with firadisk.
Maybe useful at a filled 8 cm CD-R.
Questionable at a dual layer DVD. Did anybody used the 64bit firadisk driver?

@Lancelot
What about a more modular concept:
Two single scripts for firadisk and grub4dos.
Both CreateISO.script and BootSDI.script may use them.

At second glance the "map --mem (cd0) (0xFF)" should work at CreateISO.script. Not tested.

In addition, remember grub4dos does load gzipped images to RAM.

[oriensol]

Here's the update. Also updating the info in the first post.

Tested the following:

BootSDI NOT used. ImDisk B: drive is part of the build.

With XP sources (versions 0.0.1.10 and 0.0.1.12) :
1. Booting Livexp from a Firadisk Livexp Iso (menu.lst):

title LiveXP-Firadisk

map --mem (hd1,0)/test_img.img (hd3)

map --mem (hd1,0)/pmagic-4.3.iso (hd32)

map --mem (hd1,0)/minlex/ISO/LiveXP.iso (0xFF)

map --hook

chainloader (0xFF)

2. Booting Livexp from cd with non-boot Firadisk defined using grub4dos.
3. Booting firadisk LiveXP.iso over network using tftpboot/grub4dos.

With Win2k3 sources (version 0.0.1.12):
1. Booting Livexp from a Firadisk Livexp Iso

Here's what works:

1. Booting Livexp from RAM Disk
2. Exlporer works, all partitions are recognised with drive letters
3. Non-boot RAM CD Rom works
4. Non-boot RAM Disk Works
5. Device Manager shows FiraDisk Virtual Disk Enumerator and the RAM CDRom and Disk.
6. Disk Management recognises the drives
7. Formatting the RAM hard disk works
8. Check http://www.boot-land...hl=livexp tips for Disk Management Partitioning workarounds.
8. "sc query firadisk" shows firadisk is running
9. PXE booting with tftpboot works with LiveXP.iso.


What needs to be noted:

1. The firadisk driver date and version info is suppressed from the Device Manager (to prevent frequent changes to the script). User needs to click on Drive Details to get that information.
2. When you click on the Firadisk Virtual Disk Enumerator, you get an error message before you can continue.
3. When booted from a Firadisk iso, there will be a dummy cdrom RAM drive in addition to X:.

When a newer version of firadisk is released, please download into %GlobalTemplates% or any other location and point the script to the location of the zip, using the interface.

Latest script in first post.

[oriensol]

Tested with hard disk image also, with both XP and W2k3 sources (version 0.0.1.12)

[oriensol]

Added interface changes suggested by Lancelot.

Fixed problem with Acronis recognizing hard disks when used with Amalux package.

Changed name of script from Firadisk.script to vFiradisk.script. Latest script uploaded to first post.

[oriensol]

FYI, the script now allows the Amalux complete package(but without bootsdi) to be booted using map --mem (was getting BSOD 7B before without bootsdi), with the following changes to the Amalux package:

1. Uncheck BootSDI (under Finish/2 Create Image)
2. Check CreateISO (under Finish/2 Create Image)
3. Check ImDisk (under Basic/Shells/Addons). Ensure 'Create ramdisk at boot' is checked. Change other parameters as needed by you (%, MB, Name, etc.)
4. Make following changes to Basic/!WBManager/Define Fundamentals
- Change RAM Drive Letter from "--" to "B:"
- Change 'Settings' Drive from System Drive to RAM Drive
5. Add FiraDisk under Drivers\4 Storage
6. Optionally, add USB Mass Storage Dummy Filter Driver (for recognizing multi-partition USB Flash drives)

menu.lst:

title LiveXP-FiraAmaluxp-ISO

map --mem (hd1,0)/xplivexp.img (hd3)

map --mem (hd1,0)/2k3livexp.img (hd4)

map --mem (hd1,0)/amaluxp/ISO/LiveXP.iso (0xFF)

map --hook

chainloader (0xFF)

Hope this helps.

[oriensol]

Just a crazy idea: map --mem (cd0) (0xFF)
Modern boot the loop with firadisk.
Maybe useful at a filled 8 cm CD-R.

Just tried this, after 'cdrom --init' and 'map --hook'. grub4dos gives the message:

grub> map --mem (cd0) (0xFF)

Error 67: Should not specify '--mem' when mapping a whole drive

grub>

[karyonix]

Error 67: Should not specify '--mem' when mapping a whole drive

What if you map only 50000 sectors of 50000 sectors CD ?
map --mem (cd0)+50000 (0xFF)

[oriensol]

@karyonix

That seems to work! Great!

But then what is the easiest way to find out the number of sectors in the iso?

[oriensol]

Got the number of sectors from ImgBurn and tried.

map --mem (cd0)+nnnnnnn (0xFF)

map --rehook

chainloader (0xFF)

Booted fine - no apparent issues.

[oriensol]

Glad to report that I was able to build an automated firadisk livexp hard disk image (xp source) using a quick and dirty script I put together, that works.

Big thanks owed to jaclaz and BootSDI authors - the current script uses jaclaz's mbrbatch and BootSDI script modified suitably.

These are the details:
a. No BootSDI used.
b. No Win2k3 ramdisk.sys and setupldr.bin used
c. X: is a firadisk ram hard disk.
d. X: Size is a parameter. Tested with 800 MB with Amalux package. Free space on boot 582 MB.
e. Uses (hard coded) 255/63 geometry hard disk (NTFS partition).
f. The batch file and programs used (like dsfo...) need to be in %Tools%.
g. Image can be mounted using ImDisk.
h. NTLDR & NTDETECT.COM not compressed.

While the script works the design needs to change.

What I am thinking of:

1. A separate tool (based on mbrbatch) for creating a blank hard disk image. By keeping this separate, this can be used independent of winbuilder, within a script and also when the PE is running. This tool will create a blank hard disk with 255/63 geometry and a single partition entry for an unformatted NTFS partition (to keep things simple).
2. Tool in (1) used in a script to create the firadisk livexp image. This can be a separate script or included in BootSDI.
3. Another option is to separate out the image creation part out of BootSDI. Probably, we can have three options under Create Image (iso, BootSDI, Firadisk) and a separate script/section probably called 'Install Image', which will include options for installing the created image (ISO or BootSDI or Firadisk) onto CDROM, USB, HDD, etc.

I am working on the tool in [1] above, which is really independent of the script. We can probably discuss here the best approach for the script(s) [2 and 3]. As a newbie, help is appreciated.