Hi..

I'm using bcd (yes I know it's old but I like it !) to create a dos bootable cd. The problem I have is that after the boot the CD is not accesable as I don't have the drivers for it so I wanted to load some exe's into the ramdisk during the boot sequence directly (so that I can run them from this after boot) and this is where the problem starts.

Even though I've cropped the cabs to remove all the unwanted stuff, deleted the cd driver cabs, edited the modboot cab etc, when I create the CD it ignores what I have done and still creates a CD which loads the original bcd files/dos progs into the ramdisk bin folder even though I've removed all traces of them from the cab files etc.. I've even edited the startup so that it specifically loads my exe into the ramdisk when it loads the command.com file into the ramdisk but this too was ignored (It's as if the copy command is removed during compilation because setpping though the boot it doesn't even try to do it).

Does bcd have an image internally that it uses which ignores the cab changes I've made, if not then how do I get the stuff not required stripped out and replaced with the stuff I want (ie. I have removed everything from the dos.cab and added my exe there but the ramdisk bin folder still contains stuff I've removed from the dos cab file).

Does anyone have any ideas what is going on.

Thank you

Slippery

A good question:
WHAT is BCD?

You mean BCDL/BCDW?

http://bootcd.narod.ru/index_e.htm

It would also be nice if you could actually tell us how you create the .iso. MKISOFS? With which switches?

jaclaz

Hi..

Sorry.. BCD.. from barts site (barts bootable cd using modboot) :
http://www.nu2.nu/bootdisk/cdrom/

I'm following his instructions and using "bcd cdromsi" in a dos command prompt to compile the image and burn the cd.

It all works but it ignores my changes.

Thanks

Slippery

I see.

Excuse me, but it's several years I don't use that BTW still very nice, method.

To introduce variations to that, you need to go to the "basic" Modboot:
http://www.nu2.nu/bootdisk/modboot/

and particularly here:
http://www.nu2.nu/bootdisk/modboot/#dos

But cannot say if it's the "easiest" way.

I mean the modboot concept was a way to have easily a "standard" and "as compatible as possible" result, and if needed adding to it some "small" variations on the "good/solid" base.

It is not the easiest way to create "custom" "specific" things, and introducing "important" variations is relatively difficult.

However, what you are probably missing is changing the bcd.cfg and bootdisk.cfg in \cdromsi to point to the "new" image.

jaclaz