So I downloaded the FRS badcoffee acid test 1 but the system roms needed to run this machine in openmsx are about as impossible to find so I tried some "nasty" things with the bluemsx machine editor to test my program for slot problems.
So here is how I started. First test the project on the most usual suspects of failure. Sony-HF500P, Daewoo-CPC300, that victor hc forgot the name machine. Works without trouble.
So I took the time to make it harder. I took the HF500P and inserted MSXDOS2 roms into it, trew the cartridge into a slotexpander together with some expansion ram. Still works.
Okay. Time to beef it up even more. I randomly separated the RAM into 16 K segments divided over subslots and mainslots all over the place. for example. 16Kb in slot 0-0 and 0-2 16 KB in slot 2-1 16 Kb in slot 3-3. Also 16 Kb in slot0-0 32Kb in slot 2 16 Kb in slot 3-0 etc. Still works.
I tried Ciel expert like machine with same slotconfig and VDP waitstate. Works.
Bottomline of the story: Have I practicly passed the acid test 1?

thats extreme. No MSX in the world has that. I will built a catch in the code that will inform the user that not enough free RAM could be located to run the game. I know its bad and against the standard and all that but whoever builds an MSX machine with RAM hooked onto the cartridge slots deserves games to fail on it. Even with BIOS in other slots everything goes the way i want it, at least I can go to sleep knowing that every user in the world popping the cartridge into any MSX2 machine even if slotexpanders and all that are used will be able to enjoy the game
