I have copies of my Amigas’ rom installed in the folder Kickstarts/ , but when I try to do an ‘import’, FS-UAE doesn’t take in account my KICK31.ROM file which is a revision 40.68.
Here’s the sum:
[sim@mbkp ~/Desktop/fs-uae-suite_2.5.30dev+portable_macosx/Kickstarts]$ shasum KICK31.ROM
Also, doing an hex dump on it, shows the following output:
[sim@mbkp ~/Desktop/fs-uae-suite_2.5.30dev+portable_macosx/Kickstarts]$ hexdump -C KICK31.ROM |head -n 14
00000000 11 14 4e f9 00 f8 00 d2 00 00 ff ff 00 28 00 44 |..N……….(.D|
00000010 00 28 00 0a ff ff ff ff 00 41 4d 49 47 41 20 52 |.(…….AMIGA R|
00000020 4f 4d 20 4f 70 65 72 61 74 69 6e 67 20 53 79 73 |OM Operating Sys|
00000030 74 65 6d 20 61 6e 64 20 4c 69 62 72 61 72 69 65 |tem and Librarie|
00000040 73 00 43 6f 70 79 72 69 67 68 74 20 a9 20 31 39 |s.Copyright . 19|
00000050 38 35 2d 31 39 39 33 20 00 43 6f 6d 6d 6f 64 6f |85-1993 .Commodo|
00000060 72 65 2d 41 6d 69 67 61 2c 20 49 6e 63 2e 20 00 |re-Amiga, Inc. .|
00000070 41 6c 6c 20 52 69 67 68 74 73 20 52 65 73 65 72 |All Rights Reser|
00000080 76 65 64 2e 00 33 2e 31 20 52 4f 4d 20 00 65 78 |ved..3.1 ROM .ex|
00000090 65 63 2e 6c 69 62 72 61 72 79 00 65 78 65 63 20 |ec.library.exec |
000000a0 34 30 2e 31 30 20 28 31 35 2e 37 2e 39 33 29 0d |40.10 (15.7.93).|
000000b0 0a 00 4e 71 4e 71 4a fc 00 f8 00 b6 00 f8 37 06 |..NqNqJ…….7.|
000000c0 02 28 09 69 00 f8 00 8e 00 f8 00 9b 00 f8 04 d4 |.(.i…………|
000000d0 4e 70 4f f8 04 00 41 fa ff 28 72 ff 74 01 7a 00 |NpO…A..(r.t.z.|
guess I’m missing something, but cannot find what…
Hmm, checksum looks correct for A1200 v3.1 ROM. Perhaps something trivial like FS-UAE Launcher not scanning files with capital .ROM extension? Try renaming to kick31.rom for fun, and rescan… (please report back on that). If that does not help, perhaps the launcher log file contains something interesting related to KICK31.ROM?
I have an older cd-rom version of Amiga Forever, from 1997, and FS-UAE have problems finding the roms in the package.
First, they are in a different location (Amiga Forever/Emulation/shared/rom). Second, FS-UAE doesn’t seem to accept some of the roms. The A1200 rom is labeled as not existing, and while CD32 is marked as existing, it reports that it doesn’t find it when I run a game. If I assign them manually however, they all work fine. Would be great if FS-UAE would automatically accept them though.
Hi, I have registered a todo issue for the different location: https://github.com/FrodeSolheim/fs-uae-launcher/issues/20.
The problem with the missing A1200 rom is that it actually is missing from earlier Amiga Forever CDs! amiga-os-310.rom is an A4000 ROM. Newer Amiga Forever releases contains amiga-os-310-a1200.rom.
As you discovered, using the ROM manually seems to work, but some A1200 functions may not work correctly, so FS-UAE does not automatically use mismatching ROMs.
When trying to import from Amiga Forever CD (Amiga Files/Shares/rom) I get a error stating “This is not a directory. Import task is done.”
I assuming this field is designed to look for the Amiga forever disc.
Is this because the .rom key is in the same folder as the kick starts (thus this field may not check for rom ? ).
If so, then it will always happen because every Amiga forever CD as least now has the .rom key in the same directory, and since u cannot select files unless u use the first option under “Import Kickstarts” window, its never going to work, unles you drag and drop from the CD, which defeats the purpose looking for the disc/image.
Hi, with the “import from Amiga Forever CD” you are supposed to select the root directory of the CD, i.e. “D:\” or “/media/AmigaForever” or whatever it is on your system. My guess is that you have browsed to the Shared/rom directory on the CD, and that’s why it does not recognize the Amiga Forever CD layout. If not, please send a screenshot of the import kickstarts dialog (when you have selected the Amiga Forever CD) as well as a screenshot of the error dialog to email@example.com. Thanks 🙂
thanks.. it worked..
Amiga Forever 2014 Plus Edition rom.key does not work 🙁
I did buy AmigaForever 2014 Plus Edition and created the iso image. Then I mounted the ISO on a Mac and tried to import the kickstarts. Everything fine so far, all kickstarts detected and all kickstarts and rom.key are copied to the Kickstarts folder. BUT FS-UAE does always complain:
Amiga Launch Task failed with exception ‘did not find rom.key to decrypt ROM with’. See log file for details.
What could be the problem? I did also try to import all files from the shared/rom folder, does also not work 🙁
was an issue with the old configuration. It was searching in a wrong folder. Deleting the content of the data and cache directories did solve the issue.
I own Amiga Forever premium, and there are no .key files present for any of the ROM’s. So unfortunately Amiga Forever is no longer an option for FS-UAE roms.
This is very disappointing, if true. What exact version of Amiga Forever do you have?
I have the latest PLUS version of AF, the rom.key is located in
on Windows 7
rom.key has always been included in Amiga Forever Plus/Premium Edition, but please note that we are talking about one file only (not one per ROM), so it may be easy to miss. It is in Amiga Files/shared/rom on the disc, or if running Amiga Forever select Open Amiga Files from the Tools menu, and then go inside Shared/rom.
I found I had to run Amiga Forever once before rom.key was created in the …\Shared\rom directory.
Thanks, that’s very useful to know!
Pingback: FS-UAE Amiga Emulator: Komfortable Guru Meditation | Superlevel
I have the Amiga 3.9 CD. Would it be possible to load and use this later system?
Yes, that will work fine, but to install from this CD you need to rip it to .iso or .bin/.cue first and use the CD image as installation medium. FS-UAE does not support real CD-ROM devices.
Can you use this on a real Amiga to switch between ROMS? I have Amiga Forever and a real Amiga 4000. I am finding the 4000 will not run a lot of the older software. It keeps looking for an A500 ROM.
I’m not sure what you refer to by “this”, but I suppose the answer is no anyway. If you want to run titles which normally does not run in your A4000, you should probably have a look at WHDLoad. You can also try to “softkick” your A4000 to Kickstart 1.3 by using the software “ReloKick” (google for it). That’s no guarantee that older games will run though (since the CPU is much faster than what many old games except, and also, some games may not like the updated chipset. Anyway, I cannot give support for real hardware problems here, try eab.abime.net instead 🙂
I have an Amiga A500+, coming with Kickstart 2.0. In those days, I also bought a Kickstart 1.3 disk that I could boot up my Amiga with. I would put the disk in the drive, boot up, and it would load the kickstart, and then restart the Amiga. Whilst the Amiga was restarting, I would remove the disk, and voila, Amiga would boot into a Kickstart 1.3 startup screen. How can I manage to to this using FS-UAE?
You should be able to do it just like with your old Amiga. But you need to have a disk image (.adf) of such an Kickstart 1.3 disk. When the Amiga restarts, you can eject the disk from the first floppy drive from the F12 menu.
The software you are looking for is probable “ReloKick” btw, just google for it 🙂
You should make the amiga emulator already come with a kickstart and a ROM
I would love that, of course, but the original kickstarts are not freely distributable 🙁 It does come with a kickstart replacement though, which can be used to run quite a lot of Amiga software (set kickstart to “internal” in FS-UAE Launcher).
Your email address will not be published. Required fields are marked *
Save my name, email, and website in this browser for the next time I comment.
Current ye@r *
Leave this field empty