Install Amiga Os 3 5 Winuae Torrent Rating: 5,0/5 220 reviews. Code: config amigamodel = A4000/040 cdromdrivecount = 1 cdromimage0 = PATHTOAmigaOS3.9.iso. AmigaOS 4.1 FE installation on WinUAE. Spec: Thinkpad T500: P8600/2.40 GHz, 8GB RAM, SSD OCZ Vertex 4 256 GB Windows 8.1 WinUAE 3.0. Amiga Joker Cheat-Diskette, Die Disk 3 (1992)(Joker Verlag)(De) 276 Ko Amiga Library Disk 0015 (1987)(Fred Fish).
Hi! Thanks for welcoming me, DamienD! I'm looking forward to hang around a bit.After reading all your replies and understanding WinUAE does in fact support custom/unofficial Amiga ROMs, I think I need to improve my post: The issue I'm facing isn't about adding non-classic Amiga ROMs to the database (there would be no end to it, right?), but rather that custom ROMs seem get ignored when a single official ROM is present and I don't understand why.
...This will be a long read, I apologize.
First, about that Warning in my initial post:
Winuae Amiga Emulator
- Uninstall WinUAE
- Manually delete and (clean slate)
- Install InstallWinUAE4100_x64.msi with default Options
- Launch WinUAE and the following warning (1) pops up:
- In WinUAE Properties select Settings/Quickstart and select Model A1200. Another warning (2) pops up:
- Copy (or any other custom ROM I guess?) to (I also tried not adding .rom suffix)
- In WinUAE Properties select Settings/Hardware/ROM and select as Main ROM file.
- In WinUAE Properties select Settings/Configurations enter 'Default' as name and press 'Save'
- In WinUAE Properties click on 'Quit'
- now contains
- Launch WinUAE (it should now load automatically) and another Warning (3) shows up
- In WinUAE Properties click on Start
- WinUAE now starts up properly, the ROM seems to work fine.
Here's my question about Warning #3: I'd love to be able to turn it off somewhere. I've defined a ROM file manually, even if it's not in the database, I feel I shouldn't get warned every time I try to launch WinAUE? This warning was the reason I initially created the post, thinking the ROM wasn't supported at all and gets actively rejected.
Now, here's possibly the bug I mentioned at the beginning (or just my stupidity because I missed something): I though I could maybe copy an official ROM into the folder to please the beast, but this lead to a very strange situation:
- Shut down WinUAE and copy to
- Launch WinUAE
- In WinUAE Paths click on 'Scan Rom'. It will now detect the new ROM
- In WinUAE Properties select Settings/Hardware/ROM and select as Main ROM file (or another custom ROM I guess?).
- In WinUAE Properties select Settings/Configurations, make sure 'Default' is selected and press 'Save'
- In WinUAE Properties click on 'Quit'
- Launch WinUAE (it should now load Default.uae automatically)
- In WinUAE Properties select Settings/Hardware/ROM now got reset to 'KS ROM v3.1 (A1200) rev 40.68 (512k) [391773-01/391774-01]' instead of . This means that the original ROM now gets used instead of the one specified in the config file.
still contains
This means that a single co-existing hashed Rom will override my custom choice, even if it is defined in the config. This means it's impossible on for me to launch a custom Rom by double-clicking on a WinUAE shortcut. It appears I need to manually specify a ROM file every time and then click on Start manually.
Edit: I mentioned 'I get booted into AEOS.' in my initial post - this line describes the situation when I manually deleted the only official Rom but didn't re-scan the Roms. When launching WinUAE it now tries to load AEOS instead of the specified Custom Rom.