1. this kind of questions would receive more attention (and faster reply) at the MESS forum 
2. if you want to understand what you were doing wrong, go to point 3. otherwise, if you only want something that works, copy the kof94 entry in aes.xml and you'll be done.
3. it seems you don't fully understand how the loading routines work in MAME/MESS. look closer to the MAME source: you have a 2M rom and a 2M CPU region to fill.
*but* the CPU wants the two halves to be loaded in the opposite order: from 0 to 1M it wants the second half of the rom, from 1M to 2M it wants the first half of the rom.
MAME works this around with ROM_CONTINUE: it starts loading at offset 1M and it loads only half of the ROM (you can see this because the size in the source is only 1M even if the rom is twice as large), then it continues to load the remaining data at offset 0 (so that the second half ends up where the CPU expects it).
in MESS we do the same with the loadflag="continue"
can you see now what you were doing wrong? you started loading at the correct offset, but you loaded the full rom (2M) at that offset and after that you asked MESS to keep loading one more 1M chunk after the end of the file (this explains the error you get: the rom is only 2M and you ask MESS to load 3M out of it ).
the second example does not make MESS to complain because you don't try to load a 3rd 1M block from the 2M rom, but of course the CPU does not find any correct data at 0 either...
the proper way to do this is to use size="2097152" for the dataarea, then to load only size="1048576" of your 212-p1 file at offset="0x1000000", and finally to use the continue flag to load the second half at offset 0...
|
Index 
Flat 
Re: Neo-Geo load question
Reply
