AGA
in the filename, then an A1200 will be emulated. Otherwise, it falls back to a classic A500 setup. It also supports multi-disk demos and games very simply: If the filenames for your disk images are identical apart from a trailing numerical character, it will “insert” both disks into the system. As an example, here’s what my directory of classic “Grapevine” disk magazines looks like after I’d renamed them according to RunInUAE’s standards:Ctrl
and pressing the Alt
and q
keys, and Ctrl-Alt-s switches out of fullscreen mode. You can also tweak the settings for an individual game by dropping it onto the RunInUAE window and right-clicking to see a menu where you can change the input devices (joysticks etc.), screenmode and other things. This creates a customised .uaerc file for that particular image which you can see opened in Multiview below:Workbench
volume providing a 3.1 installation mounted on a virtual DH0:
. This installation lives under System:Emulation/AmigaDisks/Workbench3.1
– this will be important later on… In addition, my usual volumes (Software, Work and System) are also mounted into the virtual Amiga in read-only mode.IDFn:
volumes. As an example, I’ve mounted the Grapevine disk image with Mounter and you can see it show up on my X5000 desktop, accessible just like a real floppy image:C
directory under System:Emulation/AmigaDisks/Workbench3.1
as the destination. Do not install this into your AmigaOS 4 System volume, as otherwise it’ll overwrite the WHDLoad “shim”. You can see the correct path specified in the screenshot below:Software:Programs/E-UAE_1.0.0
.Software:Programs/E-UAE_1.0.0/.uaerc
based on a template from Amigaone X5000 Blog. I made a few simple changes: Disabled the floppy drive sound, enabled the JIT (after some experimentation, my installation seemed to run better with it) and changed the paths to my emulated hard drives and ROM image. For reference, my slightly modified .uaerc file is listed below:Work:c
directory I keep for my own scripts and tools (this is also added to my path in my S:User-Startup
). I also ran Protect Work:c/a1200 +s
to mark it as an executable script. So that I could also launch this from X-Dock, I copied over a nice .info
icon file to this directory and renamed it as a1200.info
. I then modified the tooltypes as per the screenshot below:C:IconX
which launches script files, and also set the window to the NIL:
device so I didn’t get a screen of UAE debugging output.