Bulletin board 1997 later

Microsoft WindowsNT Server Evaluation Edition Disc:

mkbootcd - make bootable CD image(El Torito specification)
07-Jun-97 gigo@yk.rim.or.jp|imaizumi@nisiq.net Ver.beta008d

== Boot Record Volume Descriptor ==
Indicator:0
Identifier:'CD001'
Version:1
BSIdentifier:'EL TORITO SPECIFICATION'
BootCatLbn:0x00000013, loc:0x00009800, PhyLbn:0x00000013, PhyLoc:0x00009800)
*Warnning - Some Garbage in stab1.

== Validation Entry ==
HeaderID:1
PlatformID:080x86
ID String:'Microsoft Corporation'
CheckSum:0x494c

== Default/Initial Boot Entry ==
BootIndicator:0x88 - Bootable
MediaType:0x00 - No Emulation
LoadSegment:0x0000
SystemType:0x00
SectorCount:4
LoadRBA:0x00000014, loc:0x0000a000

== Direct Mode Boot Image ==

=== Verification Success ===

How to get image from ISO file?
How to make it?

Hi gigo,

Your mkbootcd.exe is very nice.
Ver:08d

Please help me.

MYBOOT.CMD file:
myboot.iso
bootcat.bin
; initial
DOS622.IMA
;--
WIN95.IMA
DOS622.IMA
;---
-SNT4S
-i88
NT4S1.IMA
-i00
NT4S2.IMA
NT4S3.IMA

COMMAND:
MKBOOTCD -
DOS622 and WIN95 can bootable from CD-R. But NT like:

Adaptec AHA-2940 Ultra/Ultra W BIOS v1.25
(c) 1996 Adaptec, Inc. All Rights Reserved.

<<< Press for SCSI Select (TM) Utility ! >>>
SCSI ID:LUM NUMBER #:# 1:0 - SONY CDROM CDU-415

A BOOTABLE CD-ROM IS DETECTED IN YOUR CD-ROM DRIVE...

The boot sections on your bootable CD-ROM are:
0. DEFAULT ENTRY
1. Section 1
2. NT4S
Please select one option (0-2), ESC to by pass Bootable CD:0
Press 2
The boot entries in the section NT4S are:
0. NT4S1.IMA (1.44M FLOPPY FORMAT)

YOUR CD-ROM DRIVE IS INSERTED AS DRIVE A: (0h). THE ORIGINAL
DRIVE A: HAS BECOME DRIVE B:

SCSI ID:LUM NUMBER #:# 4:0 - PHILIPS CDD2600

Setup is inspecting your computer's hardware configuration...

Windows NT Setup

Please insert the disk labeled
Windows NT Server Setup Disk #2
into Drive A:
* Press ENTER when ready.

Can't continue...
IDE CDROM like too.

I have Microsoft WindowsNT Server Evaluation Edition Disc.
Bootable from the disc is OK. Why? How to make?

Thanks.

>> if you try to mount the Cd-ROM you boot from..

If you write CD driver in config.sys and MSCDEX in autoexec.bat same as floppy
boot, it can basicaly.

But many CD driver conflicts BIOS El torito Emulation.

I test Adaptec's driver work well. No Other SCSI CD Driver can this.
And I received a report that ATAPI CD Driver,
Oak Technology Inc. OTI-011 CD-ROM device driver, Rev D011V111
is work well too.(It used by many CD Drive maker such as TOSHIBA corp.)

Trying the driver for OS/2 of these manufacturers is suggested.

Will you be sufficient answer in these?

Folks, Please report the BIOS and individual driver relations to here.

>> Tell what you think about to make a OS/2 bootable Image.

The El Torito emulation becomes ineffective the moment it changed to the
individual floppy/disk driver of OS because it is realized with BIOS.

Possible solutions..

1.copy file to other device(eg. ram drive) first, and load driver from it.
2.To inhibit using individual driver.(such as windows95 safe mode.)

I wants it what you have only to do concretely to be asked to wizard of OS/2.
And write down here for others.

3.The OS/2er requires IBM to support CD boot.:-)

Please Gigo! Tell what you think about to make a OS/2 bootable Image. Exactly like the other guy, my system stopped when OS/2 try to load the same os2asd.dmd (or so) file...

The floppy emulation problem is also problematic if you try to mount the Cd-ROM you boot from... This swap the drive letter and so the system stop during cd boot...

GIGGGGGGGGGGGOOOOOOOOOOOOOOOO.. Please tell us about OS/2 boot floppy and swapping CD and also about to boot without emulation... It seems the right choice, but no operating system boot in this way...
And also what about to make A floppy working also after booting in emulation???

We ask for your words! Thankx Massimo

Adaptec easy CD creator

The adaptec easy cd creator can't read/write the standard ISO image file.
It seems to be only individual .cif format can be handled.

The preparation function of bootable CD of the easy cd creator is a just
easy thing only.

1.It can't make Disk image entry.
2.It can't make multi entry.
3.It can't use imaginary 2.88MB Floppy image.
4.It can't use with Joliet.why?(Romeo not supported too.)
and so on.

Probably, the mkbootcd will be able to be improved to handle the .cif file
in the state which is the same as the standard ISO image file.
But, the reason why it does so isn't found by me.

I think that it should be improved so that an EZ CD Creator can handle the
standard ISO image.

It is inconvinient that the ISO image made by other OSs isn't burned.

I says clearly, The easy CD creator hasn't been recommended to the skilled
person yet.

I will write down how to make a bootable CD that not be able to burn with
easy CD creator.

Hello everybody!
Has anyone an idea of how to create a fully functional os2 boot-cd? I have tired
several times with different config.sys files, my system starts booting but
hangs on loading os2dasd.dmd (I think so).
Can anybody help me with a step-by-step description including the config.sys file?

Thanks, Thomas

Hello all....since all of you have problem making the cd rom boot...so I
want to share about what I have done in the past. First, you just make whatever
system that u want use to boot your computer. SO I make the system into a
floppy disk and use the getimg a: bootcd.img. AFter that, I make a boot iso file
file...where in here, I use Adaptec Easy CD PRO ver 2. SO just put the file
as this order:
bootcatX.bin
bootcd.img
whatever file do u
..
..
..

THen u burn into an iso file eg:bootcd.iso...and select JOLIET *important*.
After u finish that step, use the program mkbootcd.exe
eg : mkbootcd bootcd.iso bootcatX.bin bootcd.img ......
IF you are succesfully with that, then you will get the message say...something
like successfull.......THen use that mkbootcd bootcd.iso again to make sure
it works.

THEN THE last step...it burns bootcd.iso using CD FROM AN IMAGE FILE....

and.......now you should be able to run or use that cd to boot your computer.
I have done twice and all perfect....


Okie....have fun..and good luck!

Hi Gigo,

> >GETBTIMG HD0: G:\DOS622HD.IM1 -A -H32 -S63
> please try,
> GETBTIMG HD0: G:\DOS622HD.IM1 -A

I tried it this way yesterday: GETBTIMG HD0: G:\DOS622HD.IM1 -A

The result was worse than before :

1) with the resulting CD-rom put in the SCSI drive, it gives still
the same problem as before (see previous posts for description)

2) with the resulting CD-rom in the ATAPI drive, now this gives the
message : NON-SYSTEM DISK OR DISK ERROR

Any other ideas ?

Frank Abelshausen

W83877F


Winbond W83877F(not AF) has serial high speed mode, may be.
I wrote new shsmod that support W83877F.

But, I have not W83877F....

>GETBTIMG HD0: G:\DOS622HD.IM1 -A -H32 -S63

please try,

GETBTIMG HD0: G:\DOS622HD.IM1 -A

If use A option without -H and -S, getbtimg set -H64, -S32 automaticaly.

Hello,
Like you suggested as reply to my previous message, I now tried to execute
the GETBTIMG program with the "-A" parameter.
The complete commandline that I used was like this :

GETBTIMG HD0: G:\DOS622HD.IM1 -A -H32 -S63

The result was exactly the same however; which means that the resulting
CD-rom is booting just fine when used in my ATAPI cd-rom, but when used
in my SCSI-attached Plextor CD-drive then it is the same problem as I
reported in my previous report on this BBS.

Has anyone any suggestions please ?

Frank Abelshausen
the same problem

RESENDING of previous mail, now to your BBS as you requested.

Hello there,
Congratulations with your web-page and your programs GETBTIMG
and MKBOOTCD ! A few months ago I already tried to make a
PC bootable CD-rom by following the guidelines on the webpage
of Mr. Tung Cheng Tsai. The result of that experiment was
only "half" a success. (It started from a bootable floppy)

Now I used your programs and your guidelines to make
bootable CD-rom. This time the result was a CD-rom that I can
boot OK, if I put it in my ATAPI CD-ROM drive.
This is what I did :

01. Make a "boot-media-image"-file by using program GETBTIMG.
I used the following command :
GETBTIMG HD0: G:\DOS622HD.IM1 -H32 -S63
Remark: this physical hard disk 0 is partitioned in
4 partitions by the software PartitionMagic.
Before I started I marked the first primary partition
(=DOS 6.22) as the active partition.

02. COPY BOOTCATX.BIN BOOTCAT1.BIN

03. Create an ISO-image file with Easy CD PRO :
* new project
* CD type: CD-ROM
* drag & drop BOOTCAT1.BIN
* drag & drop DOS622HD.IM1
* reparent both files to delete their "path"
* "check" the option "Write real ISO image only to :
* in the "File names"-tab I chose the option "DOS file names(8+3)"
* push the WRITE - button ...

04. Adapt this ISO-image file to the "El Torito" specification .
This was done with the program MKBOOTCD. I used the following command :
MKBOOTCD G:\ISODOSHD.ISO BOOTCAT1.BIN DOS622HD.IM1

>>>>> THIS PRODUCED AN ERROR MESSAGE <<<<<<< :

-------------------------------------------------------------------------------
*Error - Valid boot record mark 55AA not found in PBR !
We assume 64 track/cylinder, 32 sector/track
-------------------------------------------------------------------------------
But, I checked the file with an hex editor and found that it did
contain a boot record mark 55AA, so I guessed that the error message
was due to the fact that my source hard disk had another geometry
than the defaults used in your program.
So I ignored that error message...

05. Burn the CD-rom with Easy CD PRO:
* new project
* CD-type : "CD from an image file"
* type ISODOSHD.ISO as the filename
* push the WRITE button...

>>>>>>>>>>>><<<<<<<<<<<<
>>>>>>> RESULT <<<<<<<<<<
>>>>>>>>>>>><<<<<<<<<<<<

1. If I put the cd-rom in my ATAPI CD-rom drive
(= TOSHIBA XM-5302TA) :
OK, the system boots just fine from the CD-rom !

2. If I put the cd-rom in my SCSI Plextor drive
(attached to an AHA-2940UW card) :

I see the following messages :

Adaptec AHA-2940 Ultra/UltraW BIOS V1.23
(c) Adaptec copyright .....

<<<< Press fopr SCSISelect Utility >>>
SCSI ID:LUN NUMBER #:# 3:0 - Plextor CD-ROM PX-12 CS
*************************************************************
* A BOOTABLE CD-ROM IS DETECTED IN YOUR CD-ROM DRIVE ... *
*************************************************************

The boot sections on your bootable CD-ROM are :
0. default entry

*************************************************************
* YOUR CD-ROM DRIVE IS INSERTED AS DRIVE C: (80h) . ALL DRIVES (IF *
* ANY) FOUND PREVIOUSLY HAVE BEEN SHIFTED ONE DRIVE LETTER UP*
*************************************************************
SCSI ID:LUN NUMBER #:# 2:0 - TEAC CD-R50S-000

BIOS installed successfully

*****
***** but here the CD-ROM starts making a TERRIBLE NOISE
***** while the "busy" light of the Plextor drive keeps
***** FLASHING very fast .....
*****

Has anybody any idea about this problem when booting from the SCSI
cd-rom-drive ???


Kind regards,
Frank Abelshausen
email address = franka@jeeves.be

request

I get a lot of letters of the inquiry.
Please post your question to bulletin board too,
so that the same question may not come.
And Other people sometimes give you more useful
answer maybe.

Recentry, the mail of the inquiry comes like every day for the familiar
document written more in English whether it is not here.

So, I was decided that draft to the public.
Please cooperate.

After all, time couldn't be spared very much, and anything was hardly made.
Because there will be another schedule next weekend, I don't promise about
mkbootcd 1.0 release and web page update...

A problem is a document, and is not a program.

Mr.Budi,

Let me confirm it a little.

Budi>the cd can not be used anymore..!!!

I suppose, this means the CD-R became not bootable.
I don't know the reason if it has other probrem.

All the previous sessions are no relation to bootablity in case of adaptec I/F.
It is never special.(It doesn't need to be bootable. :-))

When you do add session:

bootcatX.bin:
The bootcatX.bin must put into each iso image file.

#It'is the limitation of mkbootcd..It was found now...
#In some condition, may not must this.
#I will try to remove this limitation in next release.

For example,
I chose the X is same as session number.
The 9'th session include bootcat9.bin.

Boot-Media-Image-file(BMI):
The mkbootcd with -D[Drive Letter] option can search BMI in already burned.
If you will not add or change BMI, no need to BMI put into ISO image.

command line:
mkbootcd -M [-DQ] addsession.iso bootcatX.bin osboot.img

*If use BMI file that already burned , -D option required.
*ex. -DQ means specify target CD-R in drive Q.

and burn it, CD-R became bootable.

caution:
The ISO image file is must be build with
"add to the present medium" option.
Sorry, option name not exact, so I have not English version of Easy CD Pro.

All right ? I'm waiting for your result.

Technical information:
The -M option means the target ISO image has offset from physical top sector.
In case of first session, the offset is zero.
The other, offset = final writted sector LBN + number of GAP sector.

There is no reliable way of computing the offset as the mkbootcd can't know
last writted LBN and gap length.
But the mkbootcd can suppose and check this when the ISO image for add was
build by EASY CD-Pro.

For other writing software, you must calculate offset somehow.
You must check session gap length, as that changed by session order.
Please don't ask me about this. I can't help you as I don't know about this
as much as you. Some writer softs are add offset on the fly, so no information
in ISO iamge. These writer not add offset to El Torito part, the media became
non bootable of course!

Non Adaptec Users:
These are applicable to only some adaptec I/F(BIOS).
The other I/F not have boot from added session capability yet.
Boot from first session always. No relation of added session.

Hi Gigo, thank you for your replying my question. But still I can not add another
file and I have tried it your way by adding mkbootcd -M ! SO I better show you what
I have done in order to make it more clearly and please correct me if I am wrong

The first step I make a image by using getbtimg a: osboot.img, then I burn the
bootcatX.bin+osboot.img using easy cd pro2.21 by writing the real iso to "bootcd.iso"
THen mkbootcd -M bootcd.iso bootcatX.bin osboot.img. and after that use that command again
mkbootcd -M bootcd.iso and get the message like this:

== Boot Record Volume Descriptor ==
Indicator:0
Identifier:'CD001'
Version:1
BSIdentifier:'EL TORITO SPECIFICATION'
BootCatLbn:0x00000017, loc:0x0000b800, PhyLbn:0x00000017, PhyLoc:0x0000b800)

== Validation Entry ==
HeaderID:1
PlatformID:080x86
ID String:'Gigo's Bootable CD TEST'
CheckSum:0x7e0f

== Default/Initial Boot Entry ==
BootIndicator:0x88 - Bootable
MediaType:0x02 - 1.44MFD
LoadSegment:0x07c0
SystemType:0x00
SectorCount:1
LoadRBA:0x00000018, loc:0x0000c000
== Floppy Diskette Boot Image ==
OEM data: '(D6:nIHC'
NumberOfSectors:2880(0x0b40)

=== Verification Success ===

And the last thing....burn it using the "CD from IMAGE FILE". If I have done until
this stage, the cd can be to use boot the computer. But if I want to adding another
session by using 'MULTISESSION", and tick "load the complete track if present" with
JOLIET .....the cd can not be used anymore..!!!

SO is there any mistake that I made in here...if so...please help me to figure
it out...!! THank you very much GIGO ...

Cheers
Budi Dharma Sendjaja

Mr Budi,

The last session is effective in the case of some adaptec I/F.
Therefore, it is improper if the last session is not bootable.

Make iso image for add with Easy-CD Pro. and
use the mkbootcd with -M option.

If you need more detailed explanation for add session, please
write your question to this board.

Hai, I just wondering about the boot cd. First, I use your way to make a bootcd
and it works....fantastic. But when I wanted to add another file the cd can not be
use to boot up my computer. SO, do you know why..?? I am using easy cd pro 2.21 and
use "from IMAGE FILE" to burn the iso.

mkbootcd quick reference is rewritten.


Mkbootcd quick reference is rewritten by Michael Leslie.
Thank you !

The V1.0 package will release in this weekend.
And if I can, build mkbootcd page that written in English.

---------------------------------------------------------------------

0. Basic Preparation

The hardware and software necessary for creating a CD-R and also for
booting from a CD-ROM are necesary (refer to the test result section
of this page.) Additional necessary programs are available here.


1. Preparation of boot floppy/disk

First, a bootable floppy or hard disk must be made.
When it becomes a CD,
It cannot be written to (naturally).
It cannot be exchanged (no removal).
Be careful to keep these in mind.
You can use a ready-made floppy such as DOS installation,
or windows95 repair disk to test with.


2. Extraction of the boot image.

Once you have made a satisfactory bootable floppy / hard disk,
dump it sector by sector into a file. This file is called the
Boot-Media-Image file.
The dos application getbtimg on this page can make the image
of a DOS/Windows95/WindowsNT floppy, ot the image of a DOS/
Windows95 hard disk.

Note: Image acquisition of only the first partition has been
thoroughly tested.

Usage example:

for floppy,
getbtimg A: filename
getbtimg B: filename

for disk,
getbtimg HD0: filename
getbtimg HD1: filename

In case of a hard disk, the CHS parameter must be same as the system
you are booting from CD-ROM (SCSI under 1GB Disk, 64 heads, 32 sectors
are certain). The CHS compensation function has been added to getbtimg,
but has not been well tested yet.

Other methods of acquiring a disk image are:

- Using Norton's or other similar tools for low-level disk access
- On UNIX systems, you can do a byte for byte copy of the device you
wish an image from, for example, on a Linux system:

cp /dev/fd0 floppy.img # copies a floppy to the file floppy.img
cp /dev/hda1 disk.img # copies partition 1 on the first ide disk
cp /dev/sdb3 disk.img # copies partition 3 on the second scsi disk


3. Preparation of ISO image.

The ISO image file containing the boot-media-image file and bootcatX.bin
can be made using your favorite CD-R writing software. The file bootcatX.bin
is included in mkbtcdx.zip. (Note: the contents of bootcatX.bin are of no
consequence; it is just a placeholder so that mkbootcd can find it in the
ISO image and fill in the necessary boot information)


4. Building El Torito structure with ISO image file by mkbootcd.

mkbootcd isoimagefile bootcatX.bin boot-media-image

for example,
ISO image file name:Bootable.iso
spacing file name: bootcatX.bin
Your bootable media image file name: DC390WFU.IMG

Note that the spacer file (bootcatX.bin) and bootmedia image file (DC390WFU.IMG)
must have been placed in the ISO image prior to any manipulation by mkbootcd.

Type,
mkbootcd Bootable.iso bootcatX.bin DC390WFU.IMG

and then

mkbootcd Bootable.iso

to verify the result. (Note: Linux LILO-based floppies currently show up as
having invalid sizes. This is because the LILO floopy format is not the same as
a DOS floppy. The image still boots fine)

For more information, mkbootcd for help screen and see the examples of
indirect command files in the archive.

mkbootcd does not access any files other than Bootable.iso to make the image
bootable. It does, however, access a CD-ROM in the case of multi-session to
examine the boot-image-file of previous session.


5. Writing the ISO image

The now bootable ISO image can be written with your favorite CD-R writing
software and confirm that the resulting CD is now bootable.

mkbootcd can also make multi-entry and/or multisession bootable CDs.
Details forthcoming. (or read document written in japanese.)


6. Miscellaneous tips

How to generate a 2.88M floppy image if you don't have a 2.88M floppy:

Linux allows you to do things like mounting an image file onto the filesystem,
which is useful for mounting and testing iso images and also for creating and
refining floppy images. If you have a 1.44M floppy image, you can turn it into
a 2.88M image with WinImage (I forget where; I'm sure a quick search will yield
its whereabouts). This resultant 2.88M image file can then be mounted onto the
filesystem and filled up with more stuff. Neat, eh?

-------------------------------------------------------------------------

Mr. beseow,
Did you see my article on june 5 in this bulletin board ?

Gigo. I have tried. But in the bulletin here, I only see tables which I do not understand and results. But I don't see instructions... Sorry, would appreciate your help in giving me the structions cos I truly believe, a lot of users like myself are eager to know..... Maybe instuctions do not need to be very detail, but may in point forms and steps to do it. tks..

Mr. benseow,
Trying it first is suggested.

There are no few people who could make multi entry bootable CD-ROM only
from the information in English part of this homepage and sample indirect
command file in archive well.

Then, if it well, it is better than that you write a manual for other
people.

I think this must be the most impressive and outstanding effort gigo has showned. This is the only site I've search so far that talks about multi-image boot for CDRom. The rest are all about single image boot. However, would appreciate if you can tell us step by step (treat us like 3 yrs old) of how to do it.

Tks.

There is no general way of making the bootable CD of No emulation mode.
You must begin at the place to prepare for boot strap program which can be
used with the CD-ROM. If it is made, it can be made by using mkbootcd.

It is another story to copy the bootable CD of no emulation mode.
You can image copy easily as another type of CD-ROM with suitable utility.
But if you try to file to file copy, you must know the behavior of the boot
strap loader well. Again, The general boot starp loader for no emulation mode
is not exist. it is different from one bye one, another and another condition
required.

How can I make a bootable CD with NO emulation?
This is being done by Compaq now.

I've looked at their CD and I can not properly
copy what they have done to make it work....

thanks

Bulletin board index