Creating Blank ISO img file...

[lewi]

Is there a program that will create a blank ISO img file that can later be
written(CD-R/CD-RW/DVD-R/DVD-RW) to by other ISO imaging programs when
mounted by a virual CD/DVD driver...

I have the virual CD/DVD driver Alcohol 120% but I can create a new ISO img
only copy a existing CD/DVD...

Any help...

[Jancsi Farkas]

Post by lewi
Is there a program that will create a blank ISO img file that can later be
written(CD-R/CD-RW/DVD-R/DVD-RW) to by other ISO imaging programs when
mounted by a virual CD/DVD driver...
I have the virual CD/DVD driver Alcohol 120% but I can create a new ISO img
only copy a existing CD/DVD...
Any help...

On linux I have mkisofs which I use to build ISO images.
Perhaps could be compiled on windoz (maybe there is already built for
windoz, check with google)

Jancsi

[Alexei A. Frounze]

Post by Jancsi Farkas
On linux I have mkisofs which I use to build ISO images.
Perhaps could be compiled on windoz (maybe there is already built for
windoz, check with google)

There are. I can't tell the best place to get it, but I think by looking up
mkisofs.exe you can find it. I make ISO CD images with my OS to feed to PC
emulator. I run it like so:
mkisofs.exe -v -r -l -L -o cd.iso -J -R c:\os
to put contents of c:\os (recursively) to cd.iso.

Alex

[Jancsi Farkas]

Post by Alexei A. Frounze

Post by Jancsi Farkas
On linux I have mkisofs which I use to build ISO images.
Perhaps could be compiled on windoz (maybe there is already built for
windoz, check with google)

There are. I can't tell the best place to get it, but I think by looking up
mkisofs.exe you can find it. I make ISO CD images with my OS to feed to PC
mkisofs.exe -v -r -l -L -o cd.iso -J -R c:\os
to put contents of c:\os (recursively) to cd.iso.

Yup, very useful little beast. I develop using bootable cd (as both
bochs and vmware can boot from CD) which is made with mkisofs, and I use
grub to load the whole thing. I found is more easy to work with than
with HD images, as CD image can be mounted directly by linux through
loop device.

Jancsi

Post by Alexei A. Frounze
Alex

[lewi]

Big thanks out to Jancsi Farkas & Alexei A. Frounze cause mkisofs.exe works
great...

[Andy Cooper]

Hi there,
If you want a copy of mkisofs, you can get it from here:

ftp://ftp.berlios.de/pub/cdrecord/

And the binary form from here:

ftp://ftp.berlios.de/pub/cdrecord/alpha/win32

Hope this helps,

Andy

Post by Jancsi Farkas

Post by Alexei A. Frounze

Post by Jancsi Farkas
On linux I have mkisofs which I use to build ISO images.
Perhaps could be compiled on windoz (maybe there is already built for
windoz, check with google)

There are. I can't tell the best place to get it, but I think by looking up
mkisofs.exe you can find it. I make ISO CD images with my OS to feed to PC
mkisofs.exe -v -r -l -L -o cd.iso -J -R c:\os
to put contents of c:\os (recursively) to cd.iso.

Yup, very useful little beast. I develop using bootable cd (as both
bochs and vmware can boot from CD) which is made with mkisofs, and I use
grub to load the whole thing. I found is more easy to work with than
with HD images, as CD image can be mounted directly by linux through
loop device.
Jancsi

Post by Alexei A. Frounze
Alex

[lewi]

Post by Jancsi Farkas
Yup, very useful little beast. I develop using bootable cd (as both
bochs and vmware can boot from CD) which is made with mkisofs, and I use
grub to load the whole thing. I found is more easy to work with than
with HD images, as CD image can be mounted directly by linux through
loop device.

Can you please explain the steps for making grub bootable in a ISO img ...

Any more help...

[Jancsi Farkas]

Post by lewi

Post by Jancsi Farkas
Yup, very useful little beast. I develop using bootable cd (as both
bochs and vmware can boot from CD) which is made with mkisofs, and I use
grub to load the whole thing. I found is more easy to work with than
with HD images, as CD image can be mounted directly by linux through
loop device.

Can you please explain the steps for making grub bootable in a ISO img ...
Any more help...

First, you'll need a bootable floppy image.
Then, you have to pass the

-b images/bootimage.flp -c boot.catalog

parameters to mkisofs. I think this will do it.

from man page:

-c boot_catalog
Specifies the path and filename of the boot catalog to be used
when making an "El Torito" bootable CD. The pathname must be
relative to the source path specified to mkisofs. This option
is required to make a bootable CD. This file will be inserted
into the output tree and not created in the source filesystem,
so be sure the specified filename does not conflict with an
existing file, as it will be excluded. Usually a name like
"boot.catalog" is chosen.

-b eltorito_boot_image
Specifies the path and filename of the boot image to be used
when making an "El Torito" bootable CD. The pathname must be
relative to the source path specified to mkisofs. This option
is required to make an "El Torito" bootable CD. The boot image
must be exactly the size of either a 1200, 1440, or a 2880 kB
floppy, and mkisofs will use this size when creating the output
iso9660 filesystem. It is assumed that the first 512 byte sector
should be read from the boot image (it is essentially emulating
a normal floppy drive). This will work, for example, if the
boot image is a LILO based boot floppy.

[ ... ]

Best regards,
Jancsi

[lewi]

Post by Jancsi Farkas
is required to make an "El Torito" bootable CD. The boot image
must be exactly the size of either a 1200, 1440, or a 2880 kB
floppy, and mkisofs will use this size when creating the output
iso9660 filesystem. It is assumed that the first 512 byte sector

This output img size is of this boot.catalog thing or the whole ISO file? I
don't just want a 1440 kB CD-ROM limit in future versions...

Any more help...

[Jancsi Farkas]

Post by lewi

Post by Jancsi Farkas
is required to make an "El Torito" bootable CD. The boot image
must be exactly the size of either a 1200, 1440, or a 2880 kB
floppy, and mkisofs will use this size when creating the output
iso9660 filesystem. It is assumed that the first 512 byte sector

This output img size is of this boot.catalog thing or the whole ISO file? I
don't just want a 1440 kB CD-ROM limit in future versions...
Any more help...

It is the floppy boot image. When computer boots from CD-ROM, a floppy
is emulated. This will be the 'floppy drive' your BIOS will see, if
booting from CD-ROM. (if you boot DOS from floppy, A: will be your cdrom
drive:) )

Usually when booting from CD-ROM , this boot image contains the kernel
and everything required in order to access CD-ROM (device drviers, etc)


Best regards,

Jancsi

[lewi]

Post by Jancsi Farkas
It is the floppy boot image. When computer boots from CD-ROM, a floppy
is emulated. This will be the 'floppy drive' your BIOS will see, if
booting from CD-ROM. (if you boot DOS from floppy, A: will be your cdrom
drive:) )
Usually when booting from CD-ROM , this boot image contains the kernel
and everything required in order to access CD-ROM (device drviers, etc)

I quess I just want to know if mkisofs.exe bootable output is just 1440 kB
same as FD or is from 1440 kB to Max CD size with the 1440 kB img some where
inside...

Post by Jancsi Farkas
-b images/bootimage.flp -c boot.catalog

I also tried

mkisofs.exe -v -r -l -L -b myos.flp -c boot.catalog -o cd.iso -R d:\isodata

but I get an "uh oh could find boot image"...

Any ideas why this command doesn't work right...

Any help...

[Jancsi Farkas]

Post by lewi

Post by Jancsi Farkas
It is the floppy boot image. When computer boots from CD-ROM, a floppy
is emulated. This will be the 'floppy drive' your BIOS will see, if
booting from CD-ROM. (if you boot DOS from floppy, A: will be your cdrom
drive:) )
Usually when booting from CD-ROM , this boot image contains the kernel
and everything required in order to access CD-ROM (device drviers, etc)

I quess I just want to know if mkisofs.exe bootable output is just 1440 kB
same as FD or is from 1440 kB to Max CD size with the 1440 kB img some where
inside...

Post by Jancsi Farkas
-b images/bootimage.flp -c boot.catalog

I also tried
mkisofs.exe -v -r -l -L -b myos.flp -c boot.catalog -o cd.iso -R d:\isodata
but I get an "uh oh could find boot image"...
Any ideas why this command doesn't work right...
Any help...

I think your boot image has to be inside the files going to cd
image...(d:\isodata\myos.flp)

Jancsi

[Mark & Candice White]

Post by Jancsi Farkas
I think your boot image has to be inside the files going to cd
image...(d:\isodata\myos.flp)

With floppy emulation the 'floppy' is a img file on the CD.
There are some tricks to not map the file in the fs of the CD,
but the image usually is visible.
This also allows users to dd or rawrite the image to a real floppy
for the odd system that does not boot from CD.

But remember that 1.44MB floppys are not the only things that the
bootable CD standard ?el'toro? supports. There is also support for
2.88 floppy and HD partitions. You could have part or the whole CD
be the 'C:' drive instead of just a 1.44MB floppy img being the 'A:'.
I would not suggest anything over 2.88MB floppy though. HD emulation
is not used much and as such it is likely that there might be some
BIOS do not support it correctly.


Hope this helps.
Mark White







-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----

[lewi]

Post by Jancsi Farkas
I think your boot image has to be inside the files going to cd
image...(d:\isodata\myos.flp)

That and the path in the cmd must be relative to the input directory...

It now builds fully 15 MB with MP3 I threw in it expand size, but the iso
wouldn't but in VMware. Also I cant use it in BOCHS cause it has to be
mounted on a drive letter but the img is an linux iso img and Windows ISO
program won't mount it...

[BGainey]

Post by lewi

Post by Jancsi Farkas
I think your boot image has to be inside the files going to cd
image...(d:\isodata\myos.flp)

That and the path in the cmd must be relative to the input directory...
It now builds fully 15 MB with MP3 I threw in it expand size, but the iso
wouldn't but in VMware. Also I cant use it in BOCHS cause it has to be
mounted on a drive letter but the img is an linux iso img and Windows ISO
program won't mount it...

not so, bochs is perfectly capable of accessing iso images - just set the
path in bochsrc.txt to something like

ata0-slave: type=cdrom, path="myos.iso", status=inserted, biosdetect=auto,
model="Generic 1234"

other cool El'Torito boot modes are available i've noticed such as No Boot,
which causes the bios to mount the cd as a drive (either HD or Floppy) but
boot off a normal drive, and you can also get it to simply load and boot a
binary image off the cd without it emulating a drive. Dunno howmany BIOS
support this options tho.

ben

[lewi]

Post by BGainey
not so, bochs is perfectly capable of accessing iso images - just set the
path in bochsrc.txt to something like
ata0-slave: type=cdrom, path="myos.iso", status=inserted, biosdetect=auto,
model="Generic 1234"

Sorry, ata0-slave wasn't in any of the comments in the BOCHSRC file on my
system so I added it so thanks cause it works in BOCHS...

But in VMware it still doesn't work...

[lewi]

Post by lewi
But in VMware it still doesn't work...

Oh ya, when I say that it doesn't work I mean I get the standard DOS msg
that I get when booting from a non-bootable disk Floppy Disk or Hard
Drive...

Any more help...

[lewi]

Post by lewi

Post by lewi
But in VMware it still doesn't work...

Oh ya, when I say that it doesn't work I mean I get the standard DOS msg
that I get when booting from a non-bootable disk Floppy Disk or Hard
Drive...

Oops, just realized I fogot to disabled the Harddisk img in the VMware
configuration and it worked after the fix...

Thanks...

So now I have one last question, How do I set the boot device/IMG or boot
order in VMWare in like I can RealPC and in BOCHS so I can boot from CD img
and get my FDC testing files off a Floppy image(must be fd0) to finish load
my kernel img...

Any more help...

[ifconfig]

When you boot the Virtual Machine, you can access its BIOS using F2, like a
normal PC.
--
ifconfig
BAGOS
http://bagos.sourceforge.net

Post by lewi

Post by lewi

Post by lewi
But in VMware it still doesn't work...

Oh ya, when I say that it doesn't work I mean I get the standard DOS msg
that I get when booting from a non-bootable disk Floppy Disk or Hard
Drive...

Oops, just realized I fogot to disabled the Harddisk img in the VMware
configuration and it worked after the fix...
Thanks...
So now I have one last question, How do I set the boot device/IMG or boot
order in VMWare in like I can RealPC and in BOCHS so I can boot from CD img
and get my FDC testing files off a Floppy image(must be fd0) to finish load
my kernel img...
Any more help...

[lewi]

Post by lewi
So now I have one last question, How do I set the boot device/IMG or boot
order in VMWare in like I can RealPC and in BOCHS so I can boot from CD

img

Post by lewi
and get my FDC testing files off a Floppy image(must be fd0) to finish

load

Post by lewi
my kernel img...

Thanks...

[lewi]

Any docs on mkisofs.exe...

I got it to work by storing a simple test file/dir and now I tried a full
group of files...

1) Added as much I could and then ran mkisofs.exe and it said what file fit
before overflowing.
2) Then I deleted file that didn't fit reran mkisofs.exe and it build and
completed 791,561,208 bytes ISO file
3) Trying all ISO file reader I get no file or programs like Alcohol 120%
says to insert a disk...

Why did the test work before but not ~791 MB ISO file work?

Any more help...

[lewi]

Post by lewi
1) Added as much I could and then ran mkisofs.exe and it said what file fit
before overflowing.
2) Then I deleted file that didn't fit reran mkisofs.exe and it build and
completed 791,561,208 bytes ISO file
3) Trying all ISO file reader I get no file or programs like Alcohol 120%
says to insert a disk...
Why did the test work before but not ~791 MB ISO file work?

I look up boot IMGs in a Hex editor and I found that 791,561,208 bytes ISO
file has "Linux" at the found of file and that may be why my Window ISO
readers can't read the IMG(built with mkisofs.exe built in cygwin on Win XP
Pro)...

So is there any Win32 versions of mkisofs.exe or any other programs that
create ISO file(CD-/DVD- + R/RW) from HDD directorys...

Any more help...