Closed boras-pl closed 8 months ago
@boras-pl That doesn't sound right.
On startup, Amiberry will check for the rom.key
in a series of paths, starting with the defined Kickstarts
path, and if that fails, then look for it in the root directory, then under a few more variations (roms/rom.key
, starting path/rom.key
, starting path/../shared/rom/rom.key
etc).
The only scenario where this is picked from the root level, is if it's not found in the defined Kickstarts dir in the first round of checks.
Which version of Amiga Forever are you using? The latest ones (for a few years now) require you to run AF once (on Windows), to decrypt the ROMs, before they can be used. They also don't require a rom.key
at all, of course.
Closing this due to inactivity. Feel free to come back with more info if the problem persists.
Describe the bug I have a legal Cloanto's Amiga Forever package. It seems that Amiberry looks for rom.key in the root of Amiberry's path, not in the rom's path.
To Reproduce Steps to reproduce the behavior:
Let's assume the simplest case:
Expected behavior rom.key file should be also searched in The 'System ROMs:' location, not the main Amiberry root directory. The current behavior is not obvious for users.
Desktop (please complete the following information):
Linux (does not matter which: either RaspiOs on RPi5 or Linux Mint on x86_64)
Version v5.6.7, v6.2.0
Love Amiberry? Please consider supporting it: 👉 https://ko-fi.com/midwan