SCOUG-HELP Mailing List Archives

>> Next Message >>

Date:	Sun, 18 Apr 2004 00:28:03 PDT7
From:	"Steven Levine" <steve53@earthlink.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: Utility CD

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

In <4080A26E.1020406@charter.net>, on 04/16/04
at 08:27 PM, Ray Davison said:

>I am trying to create bootable utility CD. I have what appears to be a
>bootable VFDISK. The info I have seems to say capture an image with
>SAVEDSKF and then create an ISO with MKISOFS. The SAVEDSKF part seemed
>to work. I can't get MKISOFS to do anything meaningful.

>I have two versions of MKISOFS and the only similarity is the name. One
>is 36252 bytes, 23 Jan 99n and the other is 428760, 19 Jan 03. Anyone
>know how to operate either one?

Sure. Lots of folks know how to use mkisofs. I'm running version V0.2.0
and the files are dated 10/3/2001. Do you have a URL for your 12 Jan 03
version?

IAC, based on our discussion at the meeting a took a refresher course on
the Bootable internals because I did not immediately recall why savdskf
was used. WIth the switches that bootable uses, the command is just being
used to do a sector image, uncompressed copy of the diskette image to a
file. The resulting file is of the form required by the El Torito CD
spec.

To build the ISO, I define the 4OS2 alias:

alias isob mkisofs -v -o %=%ISOFILE -r -J -graft-points -b OSBOOT.IMG -c
boot.cat -path-list=pathlist.in -exclude-list=pathlist.out `%+` dir
%=%ISOFILED

The environment variable ISOFILE contains the ISO file name (i.e
j:\tmp\tmp.iso).

OS2BOOT.IMG is that 2.88MB boot image file created by Bootable (using
savedskf). Note that case is important.

pathlist.in defines the rest of the ISO content. In my case this is:

/=J:/TMP/00BootCD/

because this is where I stage the content.

pathlist.out is an empty file in this case.

If you don't use 4OS2, it's easy enough to convert the mkisofs command to
something that can be put in a cmd file.

As I mentioned, I use Bootable to prepare the image content. I run
bootable with the following alias:

alias bldimg Bootable slamain.cfg MakeCD.cfg

This means I run Bootable with 2 configuration files.

slamain.cfg contains standard settings for my burning environment.
MakeCD.cfg contains settings specific to preparing the bootable CD.

Excluding comments slamain.cfg contains:

VIRTUALDRIVE='U:'
WRITERDRIVE='Z:'
CDBOOTMENUFILE='J:\Util\CDBoot\cdboot.exe'
LXLITECOMMAND='D:\BIN2\LXLITE.EXE'
ADDITIONALCFG=''
COUNTRY=001
KEYBOARD=US

This is sufficient to override the Bootable.cfg defaults for my setup.

Excluding comments MakeCD.cfg contains:

CDRECORD='YES'
WRITERDRIVE='J:\TMP\00BootCD'
CDRECORDCLEANDIR='YES'
CREATEBOOTCD='YES'
FORMATMAINTENANCE='NO'
BOOTIMAGENAME.1='OSBOOT.IMG'
BOOTIMAGENAME.2='OSBOOT_2.IMG'
OS2APPS='NO'
CDBOOTMENU='NO'
CDBOOTMENUFILE='P:\CDBoot2v200\cdboot.exe'
CDBOOTMENUTIMEOUT=10
CDBOOTMENUOTHEROPTIONS=''
VERBOSE=1+2+4+64
PAUSEBEFOREBOOTIMAGE='YES'
IDE='NO'
DANIIDE='NO'
ATAPI='NO'
LATESTATAPI='NO'
DANIATAPI='NO'
NON512DASD='NO'
SCSI=1
SCSIBEFOREIDE='NO'
SCSIADDFILE.1=OSBOOTDRIVE'\os2\boot\aic7870.add'
SCSIOPTIONS.1=''
ASPI='YES'
FAT32='NO'
JFS='NO'
LVM='NO'
USBOHCI=0
USBUHCI=0
USBEHCI=0
USBKEYB='YES'
USBCOM='YES'
USBMOUSE='YES'
USBPRINTER='YES'
USBCDROM='YES'
USBSTORAGE='YES'
UNICODE='NO'
BOOTFLTFILE='f:\os2\boot\daniboot.flt'

This is a simple setup for a system with the CD attached to an Adaptec
SCSI controller. Most of the settings were copied verbatim from the
samples.

HTH,

Steven

--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.41 #10183 Warp4/FP15/14.093c_W4
www.scoug.com irc.webbnet.info irc.fyrelizard.org #scoug (Wed 7pm PST)
----------------------------------------------------------------------

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================

Return to [ 18 | April | 2004 ]

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.