Not a known rom file error with Amiga Forever-roms [Solved]

I've checked the logfile and the location is correct (copied over all roms + key-file from an Amiga-Forever(Windows/Wine)-Installation). However with each ROM-file I get something like this:

found file "amiga-os-300.rom" amiga_add_rom_file
/home/user/Config/Documents/FS-UAE/Kickstarts/amiga-os-300.rom
!: Name='/home/user/Config/Documents/FS-UAE/Kickstarts/amiga-os-300.rom':524288
CRC32=D8D42ECE SHA1=85CB943C83F9D4A9597964331AE7C5307E315925
not a known rom file

So, the files are clearly found. Don't know what the problem is. Thanks for any help.

[FrodeSolheim]

Have you also copied rom.key? This is a decryption key needed to decrypt the rom files. If you have and it still does not work, please attach the complete log file to a post!
EDIT: sorry, saw you mentioned the key file -so just upload the log file -thanks

Hello FrodeSolheim and thanks for the fast reply. I have attached my logfile (only slightly edited, replaced my username and changed from .log to.txt). Thank you again for any help.

Edit: At least I hope attaching worked, as I don't see anything regarding the attachment even though I did upload it.

[nexusle]

Nothing is attached

Another try then...

[nexusle]

In Log every ROM file of your collection will recognized as "not a known rom file". All these ROM files are Cloanto Amiga Forever ROMs. These files are encrypted and you need the file "rom.key" for decrypting. Do you have this file in ROM path, as Frode asked above?

[prowler]

Originally Posted by nexusle

These files are encrypted and you need the file "rom.key" for decrypting. Do you have this file in ROM path, as Frode asked above?

Originally Posted by Greenie

I've checked the logfile and the location is correct (copied over all roms + key-file from an Amiga-Forever(Windows/Wine)-Installation).

Originally Posted by FrodeSolheim

the complete log file to a post!
EDIT: sorry, saw you mentioned the key file -so just upload the log file -thanks

[nexusle]

Ahh yes... It's to hot out there

[FrodeSolheim]

Originally Posted by Greenie

Another try then...

Hi, got your log file this time. I think we first should check
* that the key file exists
* that is lowercase -since this is on Linux -on Windows it would have worked with mixed case)
* that it is readable

In your case, it should be:

ls -l ~/Config/Documents/FS-UAE/Kickstarts/rom.key

It the file exists and looks good, please run the following commands

ls -l ~/Config/Documents/FS-UAE/Kickstarts/rom.key
sha1sum ~/Config/Documents/FS-UAE/Kickstarts/rom.key
file ~/Config/Documents/FS-UAE/Kickstarts/rom.key

It should output something like this:

-rw------- 1 user user 750 may   12 19:12 rom.key
bba8e5cd118b8d92afed56935eeb97702a662d8f  rom.key
rom.key: ISO-8859 English text, with CRLF line terminators

Could you check this, run the commands and paste the output of them in a reply?

I remember I did some changes with regards to kickstart auto-detection in the 1.3 series, but right know I cannot remember what it was supposed to improve (and I haven't checked), so if all else looks good, could you test the latest development version from http://fengestad.no/wp/fs-uae/download-beta ?

And don't worry, we'll make it work

@FrodeSolheim: I just tried to download the latest beta (1.3.19, had installed 1.2.x) and that one seems to work. When I started it, the ROM-image (hand and floppy) appeared. So the problem seems to be solved. Thanks for all the help.