Andre Majorel wrote:
In version 0.82, many games print what looks like emulation
debugging messages while they run. For example, for robby, you
get:

  Machine reset
  cpu #0 (PC=0000004F): unmapped I/O byte read from 00000015
  cpu #0 (PC=0000004F): unmapped I/O byte read from 00000015
  cpu #0 (PC=0000004F): unmapped I/O byte read from 00000015
  cpu #0 (PC=0000004F): unmapped I/O byte read from 00000015
  cpu #0 (PC=0000004F): unmapped I/O byte read from 00000015
  cpu #0 (PC=0000004F): unmapped I/O byte read from 00000015
  cpu #0 (PC=0000004F): unmapped I/O byte read from 00000015
  cpu #0 (PC=0000004F): unmapped I/O byte read from 00000015
  cpu #0 (PC=0000012A): unmapped program memory byte write to 0000C5DF = 28
  cpu #0 (PC=0000012C): unmapped program memory byte write to 0000C5E0 = 3F

In some cases (bombjack, marble2) it's such a flood that the
emulation slows down to a crawl. Is there any way to disable them ?

Whoops, my mistake. You can fix this by deleting the vprintf call in the logerror function in src/unix/config.c. I misread the Windows diff between 0.81 and 0.82 -- this call should instead appear inside osd_die.


_______________________________________________
Xmame mailing list
[EMAIL PROTECTED]
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Reply via email to