yes the 8mb floppy works, you have to mount it as a disk drive not a hard drive. then use the floppy boot rom to load into the 8mb partition
you can find the BLANK and CPM 56kb from deramp.
as memory serves me there is also i big limitation with IOBYTE. the documentation on DERAMP gives you instructions to modify the IOBYTE for the devices on startup and the Data lines up with
the tutorial however when you use DDT and apply it ruins Cp/M on the next start up. i remember this now i was playing around with it for a few days and i kept corrupting the 8mb partition every time.
the modification works fine with the 5mb partitions but does not work with the 8mb partitions.
that means you have to remember to manually change the IOBYTE after startup to map all your attached devices with the STAT command.
you cannot mix the 5mb and 8mb partitions together because 5mb uses the Hard drive rom and the 8mb uses the floppy rom to boot either configuration can only have 2X5mb+2X330kb drives or 2x8MB+2X330kb drives.
so you can't take the good 5mb IOBYTE and stick it on the 8mb drive and fudge it.
i forgot where on deramp i found the IOBYTE documentation but it didn't work for me and kept corrupting the 8mb cp/m
now from Deramp you get a blank 8mb and the cp/m 2.2 56kb 8mb disk.. you will have to use sysgen and expand it to the full 63kb on a 64kb system this is covered in the cp/m documentation.
there is nothing on these disks, no extra tools other that the default that came with CP/M.
between the file limitations of CP/M 2.2 on the expanded partitions and reaching file directory name limits before reaching byte limits and the issues with IOBYTE on the 8mb floppy partitions i stuck with the 5mb partitions.
unless you have a huge database file that will suck up megabytes you will max out at around 3megs before you hit the 250ish file barrier anyway so it is kind of pointless.