Hello everyone,
I am attempting to add another boot option to our multi-boot technical resource
CD where I work. I currently have 8 working floppy disk images, but this time I
need to add a piece of software which I only have access to through an ISO
image. This ISO image, when burned to a CD, boots and runs the software fine.
I know that isolinux does not support booting ISO images. I used ISObuster on a
windows machine (http://www.smart-projects.net/isobuster/) to extract the
bootable image part of the ISO. This file had the extension .img, which I
renamed to .bin. I then edited my isolinux.cfg file to look like this:
-----snip-----
label 8
kernel memdisk
append initrd=dft32.img
label 9
kernel cb.bin
---end-snip---
Here, the 'label 8' is an option I already had which works, and is built
from a floppy disk image. The section starting 'label 9' is the boot
image from the ISO.
I then copied the CD-ROM contents to the directory I am using to build the
end-product ISO image. Everything appears to work fine, until the cb.bin image,
when loading from the CD-ROM, tries to access a file on the CD to complete
booting (the file is IOS.SYS, which I have esured is on the CD).
The output is exactly:
---screen-shot---
boot: 9
.
Loading....
IOS.SYS not found !
BOOT error!
---end-screen---
It looks like isolinux is loading the .bin file correctly to me.
So, my questions are: why does the cb.bin image fail to loacte the file on the
CD correctly when booting? Does this have something to do with the boot catalog?
Would it be better to instead make a hard disk image with the contents of the CD
(it is a small piece of software)? If so, is there a guide to doing this
available?
Thank you all so much for your time, and for the awesome free software!
Brent W.
Brent Winfield Woodruff wrote:> > So, my questions are: why does the cb.bin image fail to loacte the file on the CD correctly when booting? Does this have something to do with the boot catalog? Would it be better to instead make a hard disk image with the contents of the CD (it is a small piece of software)? If so, is there a guide to doing this available? >This is impossible to know without knowing what this stuff is. -hpa
H. Peter Anvin wrote:> Brent Winfield Woodruff wrote: > >> >> So, my questions are: why does the cb.bin image fail to loacte the >> file on the CD correctly when booting? Does this have something to do >> with the boot catalog? Would it be better to instead make a hard disk >> image with the contents of the CD (it is a small piece of software)? >> If so, is there a guide to doing this available? >> > > This is impossible to know without knowing what this stuff is. > > -hpaThe ISO image is created using a McAfee (Network Associates) program called Clean Boot Manager. While not supported by McAfee, it creates a very useful bootable virus scanner. The Clean Boot Manager is used to update the virus definitions and can generate either an ISO image or a three disk (floppy) set. The many other things on the CD I am creating all work fine, as they are created from floppy disk images. Also, I forgot to include in my last email the mkisofs command I am using to build my ISO image: mkisofs -o tech.iso -b isolinux/isolinux.bin -c isolinux/boot.cat \ -no-emul-boot -boot-load-size 4 -boot-info-table -r -J tech Hope this information helps... Brent W.
It's important to know what the ISO of the McAfee product looks like. If you boot that ISO, does it use no-emulation mode? or diskette emulation mode? (you should see a A:), or does it boot some kind of Linux? Does your obtained bootsectorfile have a 2KB size? Where can we find more info on this McAfee product/tool? with which McAfee product is it bundled? VirusScan ? Maybe UBCD 3.0 (Ultimate Boot CD) also has this tool. Bernd ---------------------------------------------------------------- Op deze e-mail zijn de volgende voorwaarden van toepassing: http://www.fontys.nl/disclaimer The above disclaimer applies to this e-mail message. ----------------------------------------------------------------
@Brent W. Woodruff For some reason McAfee CleanBoot needs to have its files (especially License.dat)be at the first part of the CD. I believe you can do this with an MKISOFS sort list. Although I have it running fine on my multiboot using ISOLinux/MKISOFS without using a sort list, success that way seems to vary for everyone. You can read some of the gory details at the following two pages: http://www.911cd.net/forums/index.php?showtopic=7169&hl=cleanboot http://www.msfn.org/board/index.php?showtopic=26486&hl=cleanboot Cheers