Update: Link above broke, I think it is this thread: http://five.pairlist.net/pipermail/coco/2014-January/129547.html
Bill Pierce did a good job of answering this request. The important thing is to decide what is meant by emudsk support. Will this be limited to VCC or include MESS and JVC emulators. Is the support needed just to read .vhd disks from a floppy or do you want a boot disk that can be backed up to a .vhd disk so you can boot without a floppy.
Emudsk needs different content for different emulators. Emudsk and descriptors is in 3rdparty/drivers/emudsk the boot module is 3rdparty/booters/boot_vhd.asm
Given the confusion people are having using DW and VCC RGBDOS & .vhd images, I'm not sure just how far we should go with nightly disk builds. A compromise might be to add the boot module, driver, and descriptors into the NitrOS-9\6x09\Level2\modules\BOOTTRACK & RBF directories so that users can build their own disks. That would also mean adding content to standard.bl and maybe a commented out extra line in mb.floppy to include the correct boot module.
Let's see what other people think.
You seem to have CSS turned off.
Please don't fill out this field.
@@ -1 +1,3 @@
+Update: Link above broke, I think it is this thread: http://five.pairlist.net/pipermail/coco/2014-January/129547.html
Yes, I think we should add the modules to the /NITROS9 tree on the disks, so that people can more easily build their own boot files. On which disk images would this make sense? Only the DW one? Which one is it natural to start with on a VCC emulator?
We could include an mb.emudsk and emudsk.bl if that would help.
Or should we go all the way and build disk images that also boot using emudsk? I don't use VCC so I don't know what makes sense or what is possible. Ah, this whole thing is only for those who want to have HDBDOS and NitrOS-9 on the same disk image, right, so building "just" a bootable NitrOS-9 disk (without HDBDOS) doesn't make much sense. And we are definitely not gonna generate hybride HDBDOS disks.