An illustration of a 3.5' floppy disk. An illustration of two photographs. I've tried them on both FS-UAE and WinUAE:-/ 33,107 Views. DOWNLOAD OPTIONS download 1 file. TORRENT download. Download 4278 files. Uplevel BACK 367.7K 'Allo 'Allo! Cartoon Fun!Disk1.zip download. Installing amiga os 3.5/3.9 using winuae then moving cf to amiga 1200 hi folks, could someone provide me some guidance on how this would be done, baring in mind that i dont have a cdrom on amiga 1200, the iso for 3.5 is available on the pc running winuae only. Im not of the process really, ive just took my amiga 1200 out of storage and thought. Boot into OS 3.5; Find the 'Install' icon left out in the centre of the Workbench and double click it to begin installation. Follow the onscreen instructions to complete the ClassicWB OS39 HDF; Remove the OS 3.5 HDF from the Hard Drives tab, then move the 'System.hdf' from DH1: to DH0: Save the configuration and boot. Keymaps, locale. A list of the torrents we are seeding. Details These are links to the torrents we are seeding: AmigaCityFiles-20181117.torrent - File Contents - Archive of our entire download area: 8.2gb. AmigaVideos-20170630.torrent - File Contents - Amiga Videos: 4.9gb. AmigaFormat-20170702.torrent - File Contents - Amiga Format Cover CDs: 17gb. CUAmiga-20170702.torrent - File Contents - CU Amiga. Hello, I found this post and like to run Amiga OS 4.1 on my PC - I downloaded the files from the links you provided, run the Amiga OS 4.1 in WinUAE and works fine, except for the resolution - It is by default in 'Productivity' and very low resolution and lacks the UAE screenmodes to use PC high resolutions like 1366 x 768 16 bits as an example - I also installed Clanto Amiga Forever 7, but don.

• Amiga Os 3.9 Download
• Amiga Os 3.9

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:

1. Uninstall WinUAE
2. Manually delete and (clean slate)
3. Install InstallWinUAE4100_x64.msi with default Options
4. Launch WinUAE and the following warning (1) pops up:
   
5. In WinUAE Properties select Settings/Quickstart and select Model A1200. Another warning (2) pops up:
   
6. Copy (or any other custom ROM I guess?) to (I also tried not adding .rom suffix)
7. In WinUAE Properties select Settings/Hardware/ROM and select as Main ROM file.
8. In WinUAE Properties select Settings/Configurations enter 'Default' as name and press 'Save'
9. In WinUAE Properties click on 'Quit'
10. now contains
11. Launch WinUAE (it should now load automatically) and another Warning (3) shows up
    
12. In WinUAE Properties click on Start
13. 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:

Amiga Os 3.9 Download

1. Shut down WinUAE and copy to
2. Launch WinUAE
3. In WinUAE Paths click on 'Scan Rom'. It will now detect the new ROM
   
4. In WinUAE Properties select Settings/Hardware/ROM and select as Main ROM file (or another custom ROM I guess?).
5. In WinUAE Properties select Settings/Configurations, make sure 'Default' is selected and press 'Save'
6. In WinUAE Properties click on 'Quit'
7. Launch WinUAE (it should now load Default.uae automatically)
8. 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

Amiga Os 3.9

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.
Thanks for reading!