So, to check that I'm up to speed-
I gather that the barrier to using the ROM slot as storage or general-purpose expansion is the absence of any write lines?
Also, Trash, it's worth bearing in mind that a USB *Device* port/chipset/stack and a USB *Host* port are not the same thing. The one on a computer is a host, the one on a disk is a device. There is a protocol that can do both, called USB On The Go (OTG) - but in general, an IC that acts as a device will not be able to mount (host) another device. Pardon me if I'm pointing out the bleedin' obvious here, but from your earlier posts, you
seemed to be making that confusion.
Meanwhile, this tidbit caught my eye, and perhaps warrants further investigation:
How the Classic's ROM disk image is implemented
Sure, still read-only, but perhaps a convenient, OS-friendly way of making use of spare ROM capacity?
*cough* SD card?
One small suggestion for the programming board- USB to RS232 or TTL cables are readily available, cheap, and infinitely useful for further hackery, so, in order to keep the custom board as simple (ergo, cheap) as possible, why not have TTL or serial headers on the board, and let the end user buy a USB converter? Some of us will no doubt have one lying about, and others (like me) have been meaning to get one anyway.
That also leaves the door open for maniacs who might want to program their ROM from a Mac serial port