Building a virtual Amiga for retrogaming

Amiga HD desktop

I recently built a new virtual Amiga (emulated via WinUAE) for the purpose of playing classic games. My previous build mostly worked okay, but I was having a few issues primarily from upgrading to OS3.9 as well as  installing software in a haphazard manner, so I decided to start afresh. Now that I have a solid system based around an Amiga 1200 running OS3.1 (in my experience the best configuration for running the vast majority of games) with dozens of classic games installed on a virtual hard drive, I thought I’d put together what I hope is an easy-to-follow guide for those who want to be able play Amiga games without too much fuss or technical knowledge.

Before starting you will need to acquire both an Amiga 1200 ROM and Workbench 3.0 or 3.1 ADFs (Amiga Disk Format), both of which are still copyrighted materials (fortunately most Amiga games are now abandonware). You cannot emulate Amiga software without a kickstart ROM and you cannot build an OS without the Workbench disks.

The easiest way to obtain these legally is to purchase the plus (or premium) edition of Amiga Forever from Cloanto. As well some games and a selection of pre-installed Amiga systems/configurations that run through Cloanto’s own interface, this comes with a variety of Amiga kickstart ROMs and Workbench ADFs. Alternatively you can rip the ROM from a real A1200 (e.g using TransROM; see here for a guide) and the ADFs from real Workbench disks (see here for a guide), if you still happen to own these and have a floppy drive on your PC or a null modem cable.

You may then ask: why not just use the Amiga Forever interface to run games? Well, to be frank, it’s clunky and crap (I’m not a fan), and although it uses WinUAE as its emulation backend, configuration options are severely limited and fullscreen performance is highly variable and sometimes causes sound issues.

Amiga Forever + config

Cloanto’s Amiga Forever heavily restricts configuration options, despite using WinUAE as its emulation backend

The advantage of my current system is that it’s lightning quick, it runs smoothly in fullscreen at my desktop resolution (1920×1200) and I can easily tweak WinUAE settings, when required, to improve compatibility with certain games/software. Once I boot my system I can effortlessly switch between the pre-installed games without ever leaving the Amiga environment or having to faff around with ADFs. It’s also a doddle to capture screenshots and record gameplay footage using my preferred tools – MSI afterburner for screenshots and Nvidia Shadowplay for video capture.

Building the system

Fortunately, a nice chap called Bloodwych has done all the hard work so we don’t have to (wish I’d found this before!). Similar to Jaybee’s Amiga in a Box (AIAB), Bloodwych has put together a comprehensive and elegant-looking Workbench 3.0/3.1 environment, which features everything needed to bring the GUI up to date and make for a much more user-friendly experience than the original Workbench, such as Scalos Desktop, MagicMenu, Magic User Interface (MUI) and New Icons. Importantly, it includes Picasso96, an RTG (ReTargetable Graphics) that interfaces with uaegfx (a virtual Amiga gfx card) to provide support for 16/32-bit colour and modern desktop resolutions (e.g. 1920 x 1080/1200). As an added bonus, there’s also a tonne of other software, much of which you’ll probably never need, and a small selection of classic Amiga game tunes.

1. Install the latest version of WinUAE. For this guide I’m using version 3.0.0.
2. Download Bloodwych’s P96 ClassicWB from here and extract the files. Move Bloodwych’s config file (“ClassicWB_P96.UAE”) into the WinUAE configurations folder, for me this in “C:\Users\Public\Documents\Amiga Files\WinUAE\Configurations\”. Check the “Paths” tab in WinUAE to find where yours is located. You can place “System.hdf”, which is the hard drive file, anywhere you want.

WinUAE paths

WinUAE “Paths” tab (click to enlarge)

3. Run WinUAE, go to the “configurations” tab, select Bloodwych’s config file (“ClassicWB_P96”) and click on the “Load” button.

WinUAE configurations

WinUAE “Configurations” tab (click to enlarge)

4. Select a ROM from the “ROM” tab. If I remember correctly, if you already have Amiga Forever installed WinUAE will automatically detect the available kickstart ROMs that come with the package. Otherwise you will need to direct it to where you have them stored in the “paths” tab. If you only have the Workbench 3.0 ADF, you will need to select “KS ROM 3.0 (A1200)”, otherwise select “KS ROM 3.1 (A1200)”

WinUAE ROM

WinUAE “ROM” tab (click to enlarge)

5. In the “CD & Hard drives” tab, click on “Add Hardfile”, then the three dots next to “Path:” and direct it to where you stored “System.hdf”. Type DH0 (that’s a zero) in the box labelled “Device:”. Then go back into the “Configurations” tab and save the changes.

Hardfile settings

Selecting a hard file in WinUAE (click to enlarge)

6. Click on “Start” to boot the system and follow the instructions. When asked for the Workbench disk, hit F12, go to the “Floppy drives” tab and click on the three dots next to the “Eject” button for “DF0:” and direct it your ADF. If you have Amiga Forever installed, this will be somewhere like: “C:\Users\Public\Documents\Amiga Files\Shared\adf\”.

Selecting ADF (click to enlarge)

Selecting ADF (click to enlarge)

If using a Workbench 3.1 ADF, you will be asked if you wish to upgrade to Workbench 3.1. I suggest doing this (just type “y” and press enter), but you will need to provide it with the rest of the Workbench ADFs when prompted. At the end you will be instructed to remove the Workbench disk and to reboot (hit F12, eject the ADF and press “reset”).

upgrade to 3.1

If successful you should end up with something looking like this, displayed in an 800×600 window (to go full screen press CTRL + F12):

classicWB P96 800x600

Changing the display mode

Personally, I like to run my system in fullscreen at my monitor’s native resolution (1920×1200@32-bit), but you can set it to your own taste/requirements. To change screen mode, double click on the “Run” icon on the Amiga desktop and then click “Screen” from the button menu that appears; alternatively, open “System” drive, go into to the “Prefs” folder and double click on “ScreenMode”. Note that you need to click “Save” to make the screen mode permanent, “Use” will only apply it for the current session. Also, if you used the button menu to get to the display preferences, you will need to close this before it can change the display (you will be prompted).

setting screenmode

Changing display mode preferences (click to enlarge)

If you don’t see your desired resolution or colour depth available in the list, you will probably need to allocate more video memory to the RTG. This is done in the “Expansions” tab of the WinUAE interface (press F12 to return) by moving the VRAM slider. I’ve set mine to 256mb. Remember to save your changes by going into the “Configurations” tab. You will need to reset the Amiga for this change to take effect.

WinUAE VRAM

Increasing VRAM (click to enlarge)

If successful you should end up with something like this (we’ll sort out the slightly unsightly tiled wallpaper later):

Amiga desktop 1920x1200

If you want to start in fullscreen by default (rather than windowed mode), you need to go into the “Display” tab and set the “RTG” dropdown to “Fullscreen” and then save the configuration. If running at your desktop resolution, you can also choose to the have the display scaled when you switch back to windowed mode. To enable this, go back into the “Expansions” tab and check “Always scale in windowed mode”. Then go back to the “Display” tab and set a desired window resolution in the “Windowed:” box.

WinUAE display settings

WinUAE display settings (click to enlarge)

Setting up a shared directory with Windows

Although you can browse the internet through your Amiga environment (e.g. using AWeb) and download games/software straight onto your system drive, it’s useful to create a shared directory. This provides a simple method for transferring files between Windows and Amiga, and the same directory can be used for multiple Amiga configurations.

To set this up, first create a new folder anywhere you like in Windows and give it a name. Then in the “CD and hard drives” tab of WinUAE click on “Add Directory or Archive”, direct it to this folder and then label it “DH1” in the “Device:” field. The “Volume label:” field is what the drive will be called on your Amiga, if you leave this blank WinUAE will automatically name it for you.  Save the configuration and reset your Amiga, you should now see this folder mounted as a drive on your Amiga desktop.

WinUAE add directory

WinUAE adding a directory (click to enlarge)

It you want to create folders for this drive, it’s best to do it on the Amiga side. On the Amiga folders are called drawers. To create a new drawer simply right click in the desired drive or directory and select New>Drawer; you will be prompted to give it a name. Drawers created on the Windows side will not have an associated .info file, so they’ll not have an icon and you will only be to see them if you right click inside the window and select View>All Files.

Amiga view all files

Amiga: view all files (click to enlarge)

If you want to give a drawer an icon (or any file for that matter), right click in the window and select Icons>Filetypes. This should bring up two new windows. One window should display a range of icon styles, simply drag the desired icon to the “Source” box of the other window. Now drag the iconless drawer to the “Destination” box. This drawer should now have an associated .info file and you will be able to see it by default.

Amiga create icon

Amiga creating an icon (click to enlarge)

To improve icon support I also suggest that you install PeterK’s icon replacement library, which provides support for PNG icons, otherwise many of the games you download will have nondescript dots as icons. To do this open “Drawers” (next to “Run”), then navigate to “MyFiles\Install\Icons” and run “Install_Icons_Support”. Type “y” when prompted. The system will reboot twice during the installation process.

Amiga install icon support

Install icon support (click to enlarge)

Changing wallpaper and tidying up the desktop

Obviously this step is not crucial. Ideally your wallpaper needs to be the same size as your Amiga desktop as OS won’t resize the background, so you may need to resize in an image editor. To support large image files, I suggest going into the “RAM” tab of WinUAE and setting “Z3 Fast:” to 256mb.

WinUAE Z3 memory

WinUAE Z3 memory (click to enlarge)

The image will need to be a JPEG, PNG or GIFF (or IFF the default Amiga image format). Simply drop the image into your shared directory and then copy over to “System:Prefs\Patterns\”. Then double click on “Run” to bring up the button menu and select Settings>Scalos>Pattern. Highlight the current pattern in the list and the click the icon to the right of the text box below, you should then be able to find your image in the subsequent list.

Amiga change background

Changing wallpaper (click to enlarge)

To tidy up your desktop, simply drag icons into position, right click and select Snapshot>All. You can do the same for the contents of drawers. Be aware that if you have drawers or files with no associated .info, this will not save properly.

Amiga tidy desktop

Amiga tidy desktop (click to enlarge)

Installing and running games

Fortunately, unlike the ROMs which are still under copyright, the vast majority of Amiga games can be legally obtained for free on the internet as abandonware. As a bonus, many are available in a pre-installed WHDLoad format, which means that they can simply copied onto your Amiga’s hard drive and run from there without extra steps. To able to run these you first need to install the WHDLoad user package. Bloodwych’s build already comes with this installed (v17.1), but it’s worth updating to the latest version (v18.0 at the time of writing). Download it from here (WHDLoad_usr.lha), extract (e.g. using 7-zip in Windows or on your Amiga by double clicking and choosing an extraction path) and copy to your shared directory. Run the installer using the default options.

WHDLoad format games require access to the Amiga kickstart ROMs to work. Again we can use the ROMs that came with Amiga Forever. These need to be copied across via the shared directory to “System:Devs/Kickstarts/ and must be renamed as outlined here. You will also need to copy across the “rom.key” file; however, the relocation (.RTB) files should already be in the “Kickstarts” drawer, so you can ignore that part.

WHDLoad ROMs

WHDLoad kickstart ROMs (click to enlarge)

Now it’s time to grab a game, these can also be found on the WHDLoad website here. Let’s head over to WHDownLoad to download a pre-installed version of Alien Breed II AGA, one of my favourites. Extract it and copy across to your shared folder. Before running, it’s a good idea to create a quit key, otherwise you will have to reboot the Amiga when finished playing. To do this right click on the game icon and select “info”, then click on “Tooltypes” followed by “Add new”. I want to use “Del” as my quit key, so I’m going type “QUITKEY=$46” into the text box and then press save. You can use anything you want, see here for a list of key codes, but don’t choose anything needed to play the game! Follow the same procedure for installing other games.

WHDLoad quit key

WHDLoad quit key (click to enlarge)

WHDLoad is shareware, so unless you purchase a key (£15/€20/$30) from the creator, you will have to wait a short period (around 20 seconds) each time you run a game. If you want games to run in your desktop resolution, go in back into WinUAE’s “Display” tab and select the correct resolution from the “Fullscreen:” dropdown menu and save your configuration.

Amiga game resolution

WinUAE display settings (click to enlarge)

If you choose to do this, it’s also a good idea to go into the “Filter” tab and set the scaling to “Automatic scaling”.

WinUAE scaling

WinUAE scaling (click to enlarge)

WinUAE is compatible with a range of controllers including the Xbox 360 controller (my personal preference) and these can be selected in the “Game ports” tab. If you don’t have a controller, you will need to select a suitable keyboard layout (such as arrow keys or numeric keypad) for games that require a joystick.

WinUAE controller setup

WinUAE controller set-up (click to enlarge)

What if the game I want to play isn’t available as WHDLoad?

Sometimes you can find the WHDLoad game installer but not a pre-installed version. For this you will require the ADFs. Simply run the installer, choosing a suitable installation location, and provide the required ADFs through the “Floppy drives” tab when prompted.

If you can only find ADFs for the game you want to play, you can still use your configuration to boot from these. Simply insert the ADFs into the virtual drives through the “Floppy drives” tab. You can set-up up to four disk drives to reduce disk swapping. If you’re having compatibility issues (usually with really old A500 games), then you can use WinUAE’s “Quickstart” function to effortlessly set-up an A500.

Troubleshooting and additional tweaks and settings

Here are my sound settings, these can be configured according to taste and set-up. If your having audio issues, it may be worth disabling “Interpolation” or reducing the “Sound Buffer Size”. If you’re feeling particularly nostalgic you can emulate the floppy drive sound, which will click loudly at regular intervals until you insert a disk, but this becomes extremely annoying after say 5 seconds.

WinUAE sound settings

WinUAE sound settings (click to enlarge)

If you’re having issues with games, the first thing to usually try is unchecking JIT (Just-in-time) in the “CPU and FPU” tab. This will slow down the emulation, but increase compatibility. You can also try checking “More compatible” or playing around with “CPU Emulation Speed”. If you’re experiencing graphical corruption, head into the “Chipset” tab and check “Wait for blitter”.

WinUAE CPU and FPU tab

WinUAE CPU settings (click to enlarge)

Just because I can, I have provided my Amiga with extra memory. This doesn’t seem to cause any compatibility issues for me, but you can play with these settings if you’re having any problems with your system or certain games.

WinUAE RAM settings

WinUAE RAM settings (click to enlarge)

Now that you’ve set-up your virtual Amiga, why not celebrate by launching Eagleplayer and listening to some classic Amiga tunes:

Useful resources

You may also be interested in my guide to emulating Amiga CD32 games.

For finding games:

  • WHDownLoad – repository of pre-installed WHDLoad games
  • WHDLoad – official WHDLoad site, which also contains a repository of game installers (note that these are not pre-installed like above and you need the ADFs to install the game to your hard drive)
  • Lemon Amiga – general Amiga resource, includes database of games and links to where you can download
  • Commodore is Awesome – general Commodore resource, includes downloadable Amiga games (both ADF and WHDLoad versions), box art and an archive of Amiga Format issues
  • Hall of Light – Amiga game database

General:

Advertisements

47 thoughts on “Building a virtual Amiga for retrogaming

  1. Thank you for the guide, it is really helpfull. I have a problem concerning the improved icon support. When I open drawers and navigate to “MyFiles\Install\”, I don’t have the “icons” and therefore I cannot run “Install_Icons_Support”. Any idea why is that?

    Like

      • Hi there, thanx for the comment.
        I did copy over to my files and did the installation, but I got an error message which i didn’t catch up and then i couldn’t boot to my amiga anymore…
        Fortunately I had backed up the configuration and I just copied to my winuae amiga files and i saved it :))
        Anyway, i’ll give it a try again some point later.
        I have another question if you don’t mind. I want to open the games I load from WHDload, with the igame. This WB has already installed the igame. So, as I understand, I copy the games to the System, into the drawer “games”, and then I run igames and go to ‘actions’ -> scan repositories. Am I correct?

        Like

        • Well, good luck. For the igames, I believe that is correct, but I run all my WHDload games directly from my shared directory where I store them – this makes it easier to transfer my games between different configurations.

          Like

  2. I think you have made a BIG MISTAKE
    In order to maximize graphics quality your window resolution must be an exact multiplication of low res amiga resolution. So 800×600 would look ugly because some pixels will be doubled and some tripled. The most optimal resolutions are:
    672×528
    1008×792

    Like

    • I appreciate your feedback, but I’d hardly call it a big mistake, more a matter of personal preference! As far as I’m concerned the games I play look great in 1080p (in the guide I use 1920×1200 but I now use a 1920×1080 monitor) and I like to fill the whole screen (or at least most of my 27in monitor), and I find this works well for screenshots and recording and uploading to YouTube. Obviously, some will regard the change in aspect ratio as a huge faux pas, but as I state in my guide “Personally, I like to run my system in fullscreen at my monitor’s native resolution (1920×1200@32-bit), but you can set it to your own taste/requirements”. Also remember that the original Amiga supported both PAL (320×256 or 640×256) and NTSC (320×200 or 640×200), which gives you a variety of aspect ratios, though I believe most games were in the 320×256 format.

      Like

      • I believe you still do not understand me and what i want to tell you. Everything other than exact multiplication create graphics artefact which are clearly visible for example in Wrokbench text.
        Using 1920×1080 create totally distorted fonts which looks different in different places of the screen.
        Yes most games on Amiga are run in 320×256, but we are not talking about Amiga games, we are talking how the Winuae displays Amiga screen. It displays adding 8 low res pixels (16 high res) on left, top and right, but not bottom!!!
        I did not create Winuae or its way to display things. It just the way it is and by using exact multpilication also using Filters makes real sence.

        Like

        • Well as I said in my reply, it all looks fine to me (both in Workbench and in game). If you examine my screenshots closely you will notice that the Workbench fonts are very clear, sharp and readable and I have not noticed any distortion. Personally I leave the filters turned off (I don’t like how they look), except for “automatic scaling”

          But once again, this is a matter of personal preference.

          Like

          • Unfortunatelly IT IS NOT A MATTER OF PERSONAL PREFERENCE, but a matter of assumption everybody else has the same configuration like ME (because of lack of knowledge)
            What ypu write above is an universal for everybody instruction, but you assumed something which is not true for other PC configurations.
            Default Winuae resolution is 720×568, but the overscan area is much lower as the resolution suggest. As i told you before it is 8 lower res pixels on left, top and right but not bottom, while on real Amiga the overscan displayable area is much larger. If you set this resolution to any other IT WILL NOT change the amount of overscan area winuae will display, and in some games you wont see for example the bottom of the screen (all pixels on lines 257-313)
            Take a look how the screen looks on INTEL HD display which is pretty common graphics card, but does not smooth resized area.

            http://screenshotcomparison.com/comparison/139244

            You do have probably NVIDIA or ATI card which smooths the screen, so you do not see the artefacts I see.
            You also do not need to use filters, coz you have hardware filter, but i have to.
            Even if your graphics card does have internal smooth resizer the mathematical precision says in order to maximise quality you have to use round multiplication. Good luck arguing with math.

            I hope everything is clear now.

            Like

            • Thanks for explaining further, but it would be virtually impossible to write a guide that covers all hardware configurations/permutations and of course this is based on my own experience on my own hardware. However, this is only meant to be a simple “guide” for the average user (there is much I don’t cover, hence the links to other resources and I do not profess to be an expert). Plus the average PC user (especially anyone into gaming) will usually have either an Nvidia or AMD/ATI based graphics solution (for the record I have an Nvidia gtx 780). However, I also run WinUAE on my laptop with an IntelHD/Nvidia combo (which uses the Intel graphics solution for 2d applications to reduce power consumption), and I still do not have the issues you document.

              It’s also worth pointing out that my guide uses the p96 version of Bloodwych’s preinstalled Workbench system (http://classicwb.abime.net/index.htm), which runs at 800×600 by default.

              Do you know for a fact these differences are down to hardware smoothing?

              Also, might I add, that I find your tone unnecessarily aggressive.

              Like

  3. Pingback: Building a virtual Amiga for retrogaming | rayduece

  4. Pingback: Amiga CD32 emulation guide | the cake is a lie: a nostalgic gaming blog

  5. VERY cool and looks beautiful. I’ve had all kinds of problems trying to run this in Windows 10. I love the look, but am such a novice. At the end of finally getting almost everything to work it talks about the Picasso RTG libraries not being able to load. Used to LOVE the look of Amiga in a Box way back in the day too. Anyway, thanks for the blog post. 🙂

    Like

    • Thanks. I have no experience of WinUAE in Windows 10, still using 8.1, so can’t really help. Probably worth checking that you have the latest version of the emulator. Hope you sort your problems.

      Like

  6. Thanks very much for this guide. I’m a total novice and have found it easy to follow so far. I’m now at the point of trying to change my wallpaper and have set up a shared folder and created a new background image in it. The problem I’m having is that I can open them in the shared folder without issue from the Amiga side, but I cannot move them to any other Amiga location without them ‘changing’. Instead of the image icon it changes to the tools icon, and the file can no longer be opened. I’ve saved it as several different file types – one as a JPG, one as an IFF, and one as a PNG – but they all do the same thing. An ideas what might be going on there? Am I missing something really obvious? Thanks very much, Mark

    Like

    • Thanks, glad it’s useful. I think you may need to create the relevant .info file. The Amiga does this by default, but you need to do it manually for the PC. Easiest way to do it is to copy one from another file.

      I explain how to do this under the “Setting up a shared directory with Windows” section:

      “If you want to give a drawer an icon (or any file for that matter), right click in the window and select Icons>Filetypes. This should bring up two new windows. One window should display a range of icon styles, simply drag the desired icon to the “Source” box of the other window. Now drag the iconless drawer to the “Destination” box. This drawer should now have an associated .info file and you will be able to see it by default.”

      Like

      • Thanks very much for the quick reply. I’ll try that tonight and report back. I’m hoping that I can actually get the games to work after all of this effort – I haven’t actually got so far as to try that bit yet!! Thanks again, Mark

        Like

          • Hi again. Your previous advice worked thanks – wallpapers now working!

            I have got stuck with the ROMs now! I’ve got them from AmigaForever and put them in the right place with the correct naming formats. I can’t find a rom.key file anywhere in the AmigaForever files though. Some games seem to work fine like this (e.g. Cannon Fodder) but when I try to boot some (e.g. Beneath a Steel Sky) I get a WHDLoad window pop up saying:

            DOS-Error #205
            (object not found)
            on reading “devs:kickstarts/kickstart34005.a500

            Is this because the rom.key file is missing? Or have I missed something else too?

            If you could point me towards the rom.key so i can re-try I’d be very grateful.

            Thanks again for all your help, it’s really appreciated. Can’t believe someone in the comments had the nerve to be rude when you’ve gone to all this effort to help others!!

            Like

            • Glad that helped. Yes you need to have the relevant kickstart files and different games require different ones. Do you have Amiga Forever? You can find them all in the AF install directory. For me that’s: C:\Users\Public\Documents\Amiga Files\Shared\rom. Just copy them all across to your shared drive then copy again into the devs:kickstarts folder on the Amiga’s system drive.

              Like

              • Thanks for the quick reply. I’ve got all the ROMs in the right place – the one that Beneath a Steel Sky can’t find is there. I don’t have the rom.key file you refer to though – I can’t find it anywhere and wonder if that’s what’s causing the problem? Thanks again, Mark

                Like

                  • Thanks, but I’ve already renamed as per that guide, as you’ve explained in the tutorial above, and the relocation files are also present. Is the missing rom.key file the problem? Thanks very much, Mark

                    Like

                    • Yes, then that’s probably the issue. The rom key should be in the Amiga Forever roms directory. Copy that into the same folder.

                      Like

  7. Sorry, me again!

    2 last questions – promise!!

    1. Is there a way to get WinUAE to boot up straight to the Amiga screen with my config pre-loaded? When i run it currently each time I have to go to the configuration tab, load my configuration, then click start. Can I automate/bypass all of that somehow?
    2. Is there a way to save Amiga window (drawer screen) sizes so that they stay the same when re-opened another time? I have my Amiga games looking all pretty in my shared folder – https://snag.gy/f95bEW.jpg – but every time I open it I have to stretch it out to full screen as it opens in a tiny window. I’m guessing it’s just an Amiga quirk with no workaround but here’s hoping!

    Thanks very much
    Mark

    Like

    • Hi again!

      1. If you double click on the config file in the list it loads immediately, without having to also press load and then start. I’m not sure if you can set it up so it loads by default when you start WinUAE.

      2. Yes. Right click in the relevant window and select snapshot>all.

      Like

      • Thanks Steve.

        1. I found a way of doing this. Rename the config file as ‘default’. In the misc menu untick ‘show gui at startup’, and on the quickstart menu untick ‘start in quickstart mode’. Works pretty well, though for some reason the emulated hardware shown on the quickstart menu seems to reset to A500 sometimes.

        2. Thanks for that. I was hoping for a solution that saved even after exit and restart of WinUAE, but think I’m perhaps being unreasonably demanding with that one!

        Thanks again
        Mark

        Like

        • 1. That’s cool, didn’t know you can do that. Although I have multiple configurations that I switch between such as super fast ones and slower more compatible ones. If you encounter issues with the really old games you may need to slow down the emulation or check “wait for blitter”. I also have one set-up for running the CD32; mostly for playing the CD versions of The Chaos Engine and Diggers.

          2. Yeah, it’s a bit annoying having to manually save the size, position and layout of each window! But what I always loved about Workbench is that there is no shutdown process, you could just literally pull the plug and everything would be fine when you booted it back up.

          Like

          • Yeah, I’ve had a few compatibility issues (sound and graphics going a bit dodgy) and so have been trying to make a second config file for the A500 by tweaking the A1200 one I set up using your guide but don’t really know what I’m doing. I got one working by adding the KS ROM v1.3 to my WinUAE folder, using the default A500 settings from the quickstart menu, and adding my system.hdf as DH0, and it boots to the white 1.3 screen with the hand on but there are no desktop folders and so I can’t load my hard drive games from there, just those I insert through the floppy drives in the gui. Am I missing something basic?

            Like

            • That system won’t work well/properly using an A500 rom. When I’m having issues, I slow down the emulation and enable some of the compatibility options. You’ll find these mostly in the “CPU and FPU tab” and “Chipset” tab.

              In Chipset check the “Wait for blitter”, “Cycle-exact (FULL)” and “Cycle-exact (DMA/Memory accesses)” options. The blitter option usually works well when experiencing graphical corruption.

              In the CPU tab make sure JIT and 24-bit addressing are disabled and that the CPU emulation speed is set to “Approximate A500/A1200 or cycle-exact”. You may also want set the CPU frequency as low as 2x (A500) – though this will take ages to load the desktop and you will need to be patient. However, the compatibility is very good. Also some games will run too fast, even if set to A1200 speed. For instance, Jaguar XJ220 is hilariously fast if you have the CPU frequency too high.

              Anyway, you can experiment with different combinations of these options to find the best compromise between emulation speed and compatibility.

              For one or two games, you may need to resort to running them from floppies (ADF) using a basic A500 set-up. You can use one of the quickstart configs for this and tweak to your taste (and then save after for repeated use).

              Like

              • Thanks Steve, that’s improved things for the majority of games – you’re right about the loading of the desktop being slooooooow though! Maybe I should try XJ220 at speed, give myself a challenge. I just ran North and South at high speed and the guy at the start blows his trumpet faster than I’ve ever seen anyone play an instrument! Haha! Still can’t get the sound right on one or two – I used to love Putty and Banshee but the crackling and distortion makes them horrid to play. Shame, but following the death of my Amiga (RIP) I’m just pleased to be able to play things again! Cheers, Mark

                Like

  8. Does anyone know how to save game states from within the emulated Amiga? Obviously saving adf states are not going to work in this instance… Please help!

    Like

    • As far as I know you can’t, unfortunately. That is certainly one drawback to running games from a virtual HD instead of ADFs. But you can pause indefinitely by either pressing pause or F12 and then leaving WinUAE running in the background. Though far from ideal!

      Like

        • I’ve never used a CF card, but I assume it’s the same. I used to run an A1200 with an actual hard drive and there was no way I know of to save states like you can for ADFs in WinUAE.

          Like

  9. Hello,
    i my eyes is AmigaSYS a bit better, even despite that is outdated.

    I was more hardcore and installed Vanilla WB 3.1 and installed all these items alone and to be honest without Amiga knowledge is task for 2 weeks.

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s