MESS, sur le m\u00eame principe que MAME, veut devenir L’EMULATEUR multi consoles\/ordinateurs de r\u00e9f\u00e9rence.<\/p>\n
Systems Promoted from GAME_NOT_WORKING: Skeleton drivers: System Driver Changes: -vic20: Added support for loading .crt files. Note: this will only -next: Timer free running mode [O. Galibert] Software Lists: Source Changes: T\u00e9l\u00e9charger MAME(MESS) [32 bits] v0.289 (42.5 Mo)<\/a><\/p> T\u00e9l\u00e9charger MAME(MESS) [64 bits] v0.289 (41.0 Mo)<\/a><\/p><\/p>\nNew System Drivers Supported:
\n-----------------------------
\n(none)<\/p>\n
\n---------------------------------------
\n(none)<\/p>\n
\n-----------------
\n(none)<\/p>\n
\n----------------------
\n-n64: Force mtc0 opcodes that initiate to-RSP DMAs to end recompile
\n sequences to force a code check. Fixes certain microcodes from executing
\n garbage code after DMA. [Ryan Holtz]
\n - Miscellaneous machine fixes, gets Conker's Bad Fur Day to boot through
\n its legal screens with interpreter MIPS.
\n - Increase the amount of time consumed by PI DMA, makes certain RSP
\n microcodes that test DMA speed land in the correct window.
\n - Force the main CPU to yield when the RSP reads its atomic semaphore.
\n - Force the RSP to yield when PI DMA completes.
\n - Flush the RSP DRC cache when touching IMEM with SP DMA.
\n - Increase CPU\/RSP interleave from 600Hz to 1200Hz, seems to be just
\n enough for RSP-side PI DMA tests to land correctly.
\n - Don't flush the RSP DRC cache on DMA. Fixes Mario 64 and others.
\n - Fix audio sync issues in Super Mario 64 and probably others, and
\n also bring PI DMA speed into the realm of reality.
\n - Change PI DMA speed from 3 cycles\/word to 5.08 cycles, as average
\n PI speed is between 2.53 and 2.55 cycles\/byte.<\/p>\n
\n work if the first 2 bytes of the file contain the loading address,
\n and only for single part cartridges. Please use the MESS software
\n list instead of loose files. [Curt Coder]<\/p>\n
\n-c64: Added support for the Final Cartridge and Prophet-64 cartridges. [Curt Coder]
\n-ti99: Horizon Ramdisk expansion card added [Michael Zapf]
\n-z88: moved uPD65031 emulation into a device and fixed keyboard input. [Sandro Ronco]<\/p>\n
\n----------------
\n-c64.xml\/c128.xml Added Buddy System 64\/128 v10 floppies. [Quantum Leaper]
\n-ti99.xml: Added softlist support to ti99. XML file is still preliminary,
\n must be filled with more entries. Only two cartridge PCB types
\n supported (standard\/paged) at this time. RPK will continue to be
\n available. [Michael Zapf]
\n-apple1.xml: added a few more tapes [Anon01]
\n-pico.xml: 8 new Euro dumps! [Team Europe]<\/p>\n
\n----------------
\n- 680x0: Ensure fc\/rw and fault address are consistant [O. Galibert]
\n- i386: Prevent page faults when returning to same privilege and unmapped
\n pages are above the stack. Windows 95 boots now. [Carl]
\n- Modernized terminal device and added possibility to change comm parameters [Carl]
\n- i386: LOCK prefix should depend on IOPL on 386. Windows NT beta boots. [Carl]
\n- info.c: several fixes and additions to listxml output [Fabio Priuli]
\n - appended to xml info about devices which can be optionally mounted to slots
\n - added a description attribute to slotoption to show which devices can be mounted
\n in each slot
\n - added to xml info of cpus\/inputs\/image\/slots which are relative to devices (e.g. CPUs
\n or Dipswitches in the device itself)
\n - tags of elements directly attached to the root_device do not display anymore the
\n root colon (slot tags were already behaving in this way); elements attached to optional
\n devices use tags starting with colon (to be interpreted as a relative tags which gets
\n appended to the device tag, when such a device is selected in a slot)
\n - modified when necessary output routines to pass a root_device and a root_tag as
\n parameters, in order to simplify output of relative devices and avoid duplicated code
\n - updated DTD according to the new elements and attributes
\n These changes allow frontends to know in advance how drivers can be configured
\n through the various slot options (by matching option descriptions with device
\n descriptions), without the need to run -lx with the various slot combinations. This is
\n especially of use if a device adds e.g. dipswitches or image devices (like additional
\n floppy drives or additional slot expansions), but also if one wants to know e.g. how many
\n sound channels a soundcard would add to a pc driver, or which kind of screen parameters
\n would be added by a specific choice of video card.
\n[\/CODE]
\n
\n