Hi! Thanks for welcoming me, DamienD! I'm looking forward to hang around a bit.
May 06, 2019 Join GitHub today. GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
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:
- 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.
Thanks for reading!
Hi all, I've been trying to install a Workbench 3.1 in an 60Gb HD or in a 2Gb CF Card.
I've installed the HD in the A1200 (rev. 1D4), succesfully made a 1Gb Partition and a 2Gb Partition just to make things running.
I have been unsuccesfull with the CF card, tryed all the tutorials in the internet, and it won't boot from the CF card. When I try to do the same with the HD, in WinUAE it gives me access denied.
So after all of this, as I'm a mac user, i wanted to see if this is doable through FS-UAE. If it goes right I would manage to do a step-by-step tutorial for future reference for Amiga-Mac users.
So My question for now I guess is ... how to get FS-UAE to read the external CF card. I mean ... it reads it, but shouldn't I run admnistrative privileges or something?
_________________________________________________
Amiga config:
Escom A1200
Kick 3.1
WB3.1
FS-UAE Config:
# FS-UAE configuration saved by FS-UAE Launcher
# Last saved: 2013-04-24 18:10:12
[fs-uae]
amiga_model = A1200/020
chip_memory = 2048
fast_memory = 8192
floppy_drive_0 = amiga-os-310-install.adf
hard_drive_0 = /Volumes/CFAmiga
kickstart_file = amiga-os-310-a1200.rom
uaegfx_card = 1
zorro_iii_memory = 131072
in a Macbook Pro | OSX 10.8.3
_________________________________________
Thank you,
P.S.: After a few hours of being On, it reboots with a Guru Meditation - Software Failure, and after that every 10m or so it reboots with the error. Anyone know by chance what could be wrong? Caps?
I've installed the HD in the A1200 (rev. 1D4), succesfully made a 1Gb Partition and a 2Gb Partition just to make things running.
I have been unsuccesfull with the CF card, tryed all the tutorials in the internet, and it won't boot from the CF card. When I try to do the same with the HD, in WinUAE it gives me access denied.
So after all of this, as I'm a mac user, i wanted to see if this is doable through FS-UAE. If it goes right I would manage to do a step-by-step tutorial for future reference for Amiga-Mac users.
So My question for now I guess is ... how to get FS-UAE to read the external CF card. I mean ... it reads it, but shouldn't I run admnistrative privileges or something?
_________________________________________________
Amiga config:
Escom A1200
Kick 3.1
WB3.1
FS-UAE Config:
# FS-UAE configuration saved by FS-UAE Launcher
# Last saved: 2013-04-24 18:10:12
[fs-uae]
amiga_model = A1200/020
chip_memory = 2048
fast_memory = 8192
floppy_drive_0 = amiga-os-310-install.adf
hard_drive_0 = /Volumes/CFAmiga
kickstart_file = amiga-os-310-a1200.rom
uaegfx_card = 1
zorro_iii_memory = 131072
in a Macbook Pro | OSX 10.8.3
_________________________________________
Thank you,
P.S.: After a few hours of being On, it reboots with a Guru Meditation - Software Failure, and after that every 10m or so it reboots with the error. Anyone know by chance what could be wrong? Caps?