So I've tried to get the latest mame going, and I get a message about no image attached to drive C and I can't boot Venix. It boots fine with a July 5th, 2019 mame
rainbow64 rainbow -hard1 venix-st251.chd -window -comm null_modem -bitbanger socket.127.0.0.1:1234
I build like so:
make SUBTARGET=rainbow SOURCES=src/mame/drivers/rainbow.cpp TOOLS=1 REGENIE=1 -j5
I've tried it with and without the workarounds that I used before, forward ported to new ROM_FILL
--- a/src/mame/drivers/rainbow.cpp
+++ b/src/mame/drivers/rainbow.cpp
@@ -3437,6 +3437,16 @@ ROM_START(rainbow)
ROM_FILL(0xf4303, 1, 0x00) // [0xf4000 + 0x0303] disable CRC check [100-B ROM]
ROM_FILL(0xf535e, 1, 0x00) // [0xf4000 + 0x135e] Floppy workaround: in case of Z80 RESPONSE FAILURE ($80 bit set in AL), don't block floppy access
+#if 1
+ ROM_FILL(0xf4000 + 0x198F, 1, 0xeb) // cond.JMP to uncond.JMP (disables error message 60...)
+
+ ROM_FILL(0xf4000 + 0x315D, 1, 0x00) // AND DL,0 (make sure DL is zero before ROM_Initialize7201)
+ ROM_FILL(0xf4000 + 0x315E, 1, 0xe2)
+ ROM_FILL(0xf4000 + 0x315F, 1, 0x02)
+
+ ROM_FILL(0xf4000+0x3d8, 1, 0x00) // unblock BIOS auto boot (1)
+ ROM_FILL(0xf4000+0x8aa, 1, 0x01) // JMP FAR 0000:1000 (could be a BIOS bug or a CPU oddity) (2)
+#endif
Anybody aware of this issue?
