1.00
0.60
The emulator is initially configured for one MFM hard disc. If you wish to change that, you will need to edit the arcemrc file.
To make a useful program, you will have to add to this the file "ROM" containing an Operating System ROM to your OS set up below. You may also have a drive image file named "HardImage1". This can either usefully be a RISC OS filecore image or Linux ext2 image. Note that RISC OS will quite happily boot without a harddrive.
Warning: ARM Linux does not currently work in the Windows version of the emulator. There is an unknown issue with harddrive access.
Unpack the archive to a location of your choice. You should have the following files:
The emulator is started by running the executable. Unfortunately, if anything goes wrong, the emulator will simply quit with little or no warning. This will be improved in future versions.
Pressing the + key on the keypad will toggle display of the Windows mouse.
Please see the !Help file within the !ArcEm application for usage information.
Copy the arcemrc file to your home directory as .arcemrc. Usage is otherwise similar to the Windows notes, but with some output on a console.
Q. Can ArcEm run RISC OS 3.5 or later?
A. No. ArcEm only emulates Archimedes-style hardware. RiscPC-style hardware is required for RISC OS 3.5 or later. I have no plans to add this, due to the time and research involved, but if someone else wanted to, I would be happy to help.
Q. Where can I get RISC OS 3.1 ROMs?
A. From your A5000, A3020, etc. ROM images obtained from any other source may be of questionable legality. This topic has been discussed at length in various forums, and will not be repeated here.
To save ROMs from your machine, use four 720K DOS formatted floppies (or 1.44MB if your machine supports it) and use the following commands for each floppy:
*save :0.$.ROM1 3800000 3880000 *save :0.$.ROM2 3880000 3900000 *save :0.$.ROM3 3900000 3980000 *save :0.$.ROM4 3980000 3a00000
Finally, ArcEm requires that the ROM image be a single file (unlike the other emulators), so concatenate the files using your favourite method to produce the final file.
Q. It doesn't do anything when it starts/feature X doesn't seem to work?
A. Recompile it with debugging turned on, and find out why. I don't have a better answer than that for the time being if you can't make it work.