Cds2105 Bug Options

[johnq]

I use bcdw-2.0a1.zip's "mkbtiso.bat -v2u" and CDRW

using cds2105, I get

Error booting from CD/DVD drive.
Press any key to reboot...

[                                                                ]808002F9

using cds2104, everything is fine.

[d4vr0s]

I had a similar problem after upgrading to 2.1.5. I discovered if I resaved the file with UltraISO the problem went away.

[johnq]

Before I was about to give up on Alex Kopylov's mkisofs and try MS CDimage, I use paraglider's ToUpper.exe to uppercase all files of BartPE and XP SP2 Recovery Console, then just use "mkbtiso.bat -v2", everything is fine again!

[Mike]

In CD Shell 2.1.5, I added support for ISO9660:1999 (-iso-level 4). One of the side effects is that when you use that type of filesystem, identifiers are interpreted as case-sensitive. So while it may have worked fine in the past, you should make sure that all of the CD Shell files' names are in lower case in the ISO you create, if you're using the 9660:1999 spec.

[Former_Bendes_post]

In CD Shell 2.1.5, I added support for ISO9660:1999 (-iso-level 4). One of the side effects is that when you use that type of filesystem, identifiers are interpreted as case-sensitive.  So while it may have worked fine in the past, you should make sure that all of the CD Shell files' names are in lower case in the ISO you create, if you're using the 9660:1999 spec.

I use this method and it works except for one think, I explain myself:

On my bootable CD, all directory "boot" is in lowercase, the rest is in uppercase. If I choose to boot on a simple "Windows 98 SE" bootable floppy image, the image boot but when I type the following command at the DOS prompt:

CODE

<CD-ROM Letter>:
CD boot

I have a message telling me that it's an "Invalid Directory"


Can you tell how to resolve this????

[d4vr0s]

My error is this:

Error booting from CD/DVD drive.
Press any key to reboot...

[                                                                  ]808003F9

I tried both lower casing and upper casing all the files for cdshell with the same results.
It might have something to do with using the --force-uppercase along with the -iso-level 4 switch in mkisofs?
UltraISO appears to be making these changes to the volume descriptor (using isoinfo):
Original -> New

CODE

Volume size is:307399 -> Volume size is: 307249
El Torito VD version 1 found, boot catalog is in sector 501 -> El Torito VD version 1 found, boot catalog is in sector 499
CD-ROM uses ISO 9660:1999 relaxed format -> (UltraISO removes this reference)
Bootoff1F6 502 -> Bootoff1F4 500

In UltraISO - File - Properties of the new file, 'Omit ISO 9660 version number' is ticked.
The resulting file is exactly the same size as the original.
This hasn't caused any problems yet here and cdshell works.
Edit:
Throwing the -N switch at mkisofs (Omit ISO version numbers from file names) did not help.

This post has been edited by d4vr0s: Mar 30 2005, 09:14 AM

[myegon]

Hi,

I've built a CD that uses bcdw as main boot loader. There is an entry which runs cdshell (\boot\loader.bin). When cdshell is selected the following error is shown (I run it through vmware 4.5.2):
*********
error booting from CD/DVD drive.
press any key to reboot...
*********
The error code in the right down corner: 808003F9

What's the problem?

I try using cdshell 2106.


Regards

..--

[d4vr0s]

@myegon
I'm not sure what the problem is, but my UltraISO solution works for that situation here.

Edit:
I am using the --force-uppercase switch in mkisofs, this possibly is the problem with mine, but I haven't experimented to find out.

This post has been edited by d4vr0s: Apr 27 2005, 09:00 AM

[Mike]

d4vr0s, the force uppercase switch is probably the problem. You can try opening the iso in isobuster to see if the CD Shell files have been uppercased. If that's the case you'll have to do one of the following:

a. Don't use iso9660:1999.
b. Don't use --force-uppercase.
c. Hex edit or reassemble loader.bin to look for CDSH.BIN instead of cdsh.bin.

You may be stuck with a. or b. depending on your application, so that would just leave option c for you to do. I realize that this is somewhat of a hassle, but there's not much we can do here. Iso9660:1999 implements case-sensitive file names, so it's entirely possible that you have cdsh.bin, CDSH.BIN, and CdSh.Bin all in the same folder, for example, which would cause problems if we just ignored case to make life easier in this one instance.

[Mike]

myegon, I'm sorry I don't know what the problem is in your situation. That's the standard error code given when CD Shell can't read from the disc. I don't have any experience working with BCDW so I'm not sure where the problem lies. Maybe someone here has more experience with that.

[d4vr0s]

@Mike
Thanks, I'll try option c next.
But, as I posted earlier, UltraISO fixes the issue by removing the iso9660 information from the volume information as well.

[myegon]

Mike,

thanks for options a to c.
Now I'm using cyrano's postprocessing plugin for BartPE. \boot is lowercased (that's option so it's possible to use CD-Shell as primary and "secondary" boot loader.

Hacking loader.bin didn't work for me.


Regards,

..--

[SKiNNiEH]

I know this is an old topic, but just to let you guys know how i fixed it.

a. Hex Edited loader.bin and changed: cdsh.bin to CDSH.BIN, /boot to /BOOT
b. Hex Edited sloader.bin and changed: same as above

Now i can just use cdimage and not do anything extra afterwards.

[bober]

new version is 2106

[rewss]

new version is 2106

And I'm having problem with this new version.
I got the Boot error code: 808002F9.
So, i wonder what is problem with mine.....

[rewss]

everyone.
i just found the solution for it.
in the cdshell.ini, dont even think puting *.*.dat files as command.
for my cdshell.ini, it had:

if $lastKey == key[1]; then chain /HOM1.dat
if $lastKey == key[1]; then chain /MCE1.dat

i was wondering what will be happen if i delete those two codes from the cdshell.ini, cause when i ran the cdshw.com, thats what it gaves me error, which is "files are not found."
so, i deleted from cdshell.ini, saved it, and made made iso, and burned to dvd, it boots fine.
yay me.