BootSDI and mkisofs questions, Harddiskinstallation and Cloning in one step External links Options

[Icecube]

There are two distinct types of mapping, direct and memory. Direct mapping is generally used for larger images/devices. If using direct mapping to create a virtual device from a disk image, then the image file must be contiguous (not fragmented). Either of the following programs can be used to defragment a file that is contiguous - contig or wincontig. Attempting to directly map a non-contiguous file will result in Error 60: File for drive emulation must be in one contiguous disk area , in which case memory mapping or defragmenting the file, and then retrying, should be attempted.

See: http://diddy.boot-land.net/grub4dos/files/map.htm for the links to contig and wincontig.

[was_jaclaz]

@Tokener
What you might be missing is that the CD IS the .iso and the .iso IS the CD.

You just need to "convert" or "extract" the CD to a .iso.

Take your pick (just examples):
http://www.lucersoft.com/freeware.php
http://www.dubaron.com/cd2iso/
http://www.isodisk.com/
http://isorecorder.alexfeinman.com/isorecorder.htm
http://dpaehl.dd6338.kasserver.com/cdr/cddvdiso.php
and of course cdrtools (command line):
http://cdrecord.berlios.de/old/private/cdrecord.html
http://www.student.tugraz.at/thomas.plank/

jaclaz

[wimb]

@Tokener
You are confusing CD-ISO files with Harddisk-IMG Files.
You should make use of <WinBuilder>\ISO\Ram\I386\BootSDI.img file.

You can use BOOT_IMG.exe to Install LiveXP BootSDI.img IMAGE File
as Boot Option in boot.ini Menu or GRUB4DOS menu.lst
http://www.boot-land.net/forums/index.php?showtopic=5306

[Tokener]

@Icecube

THANKYOUTHANKYOUTHANKYOU

That was IT !
Contig showed up: File was defraged into 2 sometimes 3 or 4 frags.
When contig did his job the iso booted correct.

THANKYOUVERYMUCH, all you WINBUILDERS !

T.

[was_jaclaz]

Nice batch.

A couple of ideas to "clean" it, if I may:

CODE

if not exist bootsect.bin set miss=YES&echo. File missing: bootsect.bin
if not exist Contig.exe set miss=YES&echo. File missing: Contig.exe v1.55
if not exist grldr set miss=YES&echo. File missing: grldr
if not exist mkisofs.exe set miss=YES&echo. File missing: mkisofs.exe
if not exist ntldr set miss=YES&echo. File missing: ntldr

could become:

CODE

FOR %%? IN (
Contig.exe
grldr
mkisofs.exe
ntldr
) DO SET miss=YES&ECHO File missing: %%?

and this:

CODE

echo [boot loader]>>%FTW%
echo default=C:\grldr>>%FTW%
echo [operating systems]>>%FTW%
echo C:\grldr="Start GRUB4DOS Menu">>%FTW%
echo. >>%FTW%

may become:

CODE

(
echo [boot loader]
echo default=C:\grldr
echo [operating systems]
echo C:\grldr="Start GRUB4DOS Menu"
echo.
)>>%FTW%

see "Group commands for redirection" #15 here:
http://www.robvanderwoude.com/clevertricks.php

jaclaz

[cdob]

@Tokener
What you might be missing is that the CD IS the .iso and the .iso IS the CD.

Yes, that's true. Nicely written.

There is readcd, dd, dsfo or ISOBuster to read a CD to a ISO file.


Another option if you like to create ISO file yourself: chainload setupldr.bin.
ISO file is not bootable, hence dosn't require bootsect.bin.
And don't copy temp files to hard disk first.

mkisofs.exe -iso-level 4 -force-uppercase -o C:\LIVEXP.ISO X:\

title - ISO Image - LiveXP BootSDI
find --set-root /LIVEXP.ISO
map /LIVEXP.ISO (hd32)
map --hook
root (hd32)
chainloader (hd32)/I386/SETUPLDR.BIN

[Tokener]

@cdob
Hallo cdob
You mentioned:

@Tokener
What you might be missing is that the CD IS the .iso and the .iso IS the CD.

Let me please ask you what that Quote means or what my fault is.
Am I standing in darkness ?

T.

[cdob]

Let me please ask you what that Quote means

Well, this goes to previous

But normally the BootSDI.iso isn´t on the BootSDI-CD so you can´t install to HDD.

How do you create a BootSDI-CD?
First a CD image file is created: a ISO file BootSDI.iso.
Next this ISO file is written to cd.
The hole CD represent the ISO file BootSDI.iso.

Extract the hole CD to a file: this get the previous image file BootSDI.iso.

[Tokener]

OK.

That´s what i wrote:

To change this I moved the original BootSDI.iso from Winbuilder´s OutputFolder to C:\ and made an entry in boot.ini for grldr,
and one entry in menu.lst for BootSDI.iso.
When booting the Harddisk you can call Grub4Dos from boot.ini, and Grub4Dos can call BootSDI.iso to load.
You need 3 files: BootSDI.iso, grldr and ntldr(might be on C:\).
You have to modify 2 other files: boot.ini and menu.lst.

Did you place a BootSDI.iso in C:\ , and all the other steps ?
I guess not, because if you did, you´d have seen that the BootSDI.iso, that the WINBUILDER074 creates, IS the bootable system, that waits to be called by grldr .
Now, if you want to install this specific system on another HDD you have to carry the ISO - right ?

But normally the BootSDI.iso isn´t on the BootSDI-CD so you can´t install (it) to HDD.

- right ? NO
Read the description on top of the post and you will find a way to get this installation going.

This BootSDI thing is so GREAT because it can replicate itself, it´s biological - like the mother of pearl.
oops... I´m getting offtopic.
Good Night and ThanX again for the BootSDI.

T.

[was_jaclaz]

Tokener, take it easy.

What both myself and cdob are saying is that your initial idea is partly overkill:

Now my idea is to rebuild the BootSDI.iso from the BootSDI-CD:
What2Do:
-boot the BootSDI-CD.
-copy all files from BootSDI-CD(source) to TEMP-folder.
-add bootsect.bin that might be hidden.
-compile the ISO by mkisofs.exe.
-copy grldr and ntldr to C:\
-make entries in boot.ini and menu.lst.

as it can be done as follows:
-boot the BootSDI-CD.
-copy all files from BootSDI-CD(source) to TEMP-folder.
-add bootsect.bin that might be hidden.
-compile the ISO by mkisofs.exe.
-extract whole CD to .iso saving it as LIVEXP.ISO on C:\
-copy grldr and ntldr to C:\
-make entries in boot.ini and menu.lst.

Two steps less.

I'll try to rephrase the info I posted:

What you might be missing is that the CD IS the .iso and the .iso IS the CD.

A .iso file is a byte by byte copy of a CD: an image or clone.
A CD is byte by byte copy of a .iso file.

Instead of extracting parts of the "whole" (files, bootsect.bin) to a TEMP folder, then re-assemble those parts in a new "whole", it is easier, faster and evidently less error prone, to simply copy the said "whole".



jaclaz