rpix86 v0.03 Beta Release Notes =============================== This version contains the following fixes and improvements: - Improved support for combined keyboard/mouse USB devices (for example Logitech K400). - Fixed a problem in Mode-X STOSD opcode (fixes "Settlers"). - Implemented read from file directly to EGA VRAM ("Heimdall"). - Fixed SB command DSP_RESET to stop auto-init DMA play ("Doom"). rpix86 v0.02 Beta Release Notes =============================== This version contains the following fixes and improvements: - Added int2F AH=AD functions for FreeDOS KEYB.EXE handling. - Implemented missing EGA REP MOVSW version for "Bard's Tale". - Added command line parameters -k? and -m? for overriding the internal keyboard event and mouse event file detection. rpix86 v0.01 Beta Release Notes =============================== Well, here it finally is, the first public version of rpix86! The emulator is still very much work-in-progress, and thus still has quite a few missing features and outright bugs. You can run the emulator simply by running the "rpix86" executable FROM THE CONSOLE SCREEN. Note that rpix86 can not be run within the graphical X environment. By default rpix86 runs full screen with the current working directory as the C:\ root directory and audio output sent to the analog output. You can change these defaults using command-line parameters, run rpix86 with a command "rpix86 -?" to get a usage infor describing the parameters. The first time you run rpix86 (or whenever you change the root directory and that directory or a subdirectory called "4DOS" does not contain "4DOS.COM" command interpreter), rpix86 will ask whether you wish to download the "4DOS.COM" command interpreter from JP Software FTP site. If you do not want to let rpix86 do this for you, you can download it yourself from ftp://jpsoft.com/4dos/files/ (or ftp://207.7.82.31/4dos/files/). You can exit rpix86 by giving an "exit" command on the command prompt, or by pressing Ctrl-C. If/when rpix86 encounters an unsupported opcode or some other error where it can not continue, it will write a crash log file "rpix86dbg.log", into the emulated C:\ root directory. The file gets appended every time this happens, so you can test all your favourite games and then send the log file to me, I might be able to improve the compatibility in future versions based on these crash logs. Thanks for trying out rpix86! Patrick Aalto