Well, I code on a Turbo-r ST with 512k and a EZDrive with COMPASS because of the fast assembling with this hardware but everything, for the moment, for MSX1

Anyway, it obvious that the use of the ST as a prize it's just for "recruiting" as many contestants as possible.

As Dioniso said, the Turbo-R is just to attract more people, because that means more entries, and then more games. This is the goal, and also boost a bit the MSX1 scene.

Of course, I have my own Turbo-R machine, but I do not use it very often. I prefer cross-development, and after that I test it carefully in all the MSX machines that I owe. But I have my own Z80 assembler and I do feel confortable when coding for the MSX1 with MS-DOS EDIT and Rz80, my assembler.

Keep going on!

Coding for MSX1 on a MSX2 or higher is dangerous. Be sure to test the code on an actual MSX1, because MSX1 VDP has much less buffering for VRAM access. It would be really dumb if some games in the competition only work on MSX2 using MSX1 screenmodes

As Pitpan have already said, he always test the games on real MSX1 computers. I also do the same

Yes, I know the differences between TMS9918 and V9958, and my "MSXdev" desktop consists in 2 tables. The first one has got a PC and it is my "development studio". The second, that is just in front of the other, has got a multisync TV and two MSXs: a SONY HB-10P with a fab joystick and a Turbo-R GT+IDE CF+MegaFlash SCC. That is my "debugging studio": I test the programs booting ROM and RAM, in Z80 and R800 mode, at 60 Hz or at 50 Hz, and after this "test", if everything goes fine, then the product is "100% COMPATIBLE" - I know that it is not necesarily true, but it works fine.