04 September 2017, 18:37 | #1 |
Posts: n/a
|
Kickstart ROM support?
After scanning the most practically-complete no-intro set for Amiga with FS-UAE 2.9.6dev, it does not find the following Kickstarts:
Amiga 1200, 3000, 4000, CD32 I think CD32 is expected, but I'm confused about the rest. Is there a reason that it's not finding these? I've verified with Romcenter that they are valid wrt the no-intro database, so it's not an issue of bad Kickstart files. On a side note, I thought I'd mention my n00b user experience in case it helps: 1. Attempted to import Kickstart files from library and was confused that none were found (apparently it can't import .zip files directly) 2. Scanned library and was confused that (some) Kickstarts showed up (per above) but no games showed up. 3. Realized that I needed to create an ORGD account and import their database. 4. Attempted to launch a game and was confused that it sat at a boot screen forever. 5. Realized that I needed to manually download and install an IPF support plugin. 6. At this point, games were able to boot. It would be kind of awesome if there was a setup wizard, but I suppose it's going to be a different process for everyone. In particular, I see that FS-UAE seems to be more optimized around helping people import from existing Amiga Forever and/or WinUAE installations, so my use case may be less common. |
04 September 2017, 19:57 | #2 |
Registered User
Join Date: Apr 2016
Location: Greensboro, NC USA
Age: 32
Posts: 116
|
I think that on my FS-UAE setup, I have the appropriate kickstart file manually configured for emulating the 1200. I had the same problem as you, and as long as you save the configurations for later it should be a one-time problem
|
04 September 2017, 20:05 | #3 |
Posts: n/a
|
It's nice to know that it's possible to manually get FS-UAE to do the right thing, but it sounds like there's still an issue here that probably needs to be sorted out.
|
04 September 2017, 20:26 | #4 |
Missile Command Champion
Join Date: Aug 2005
Location: Germany
Age: 52
Posts: 12,467
|
The only TOSEC Kickstart the scanner never finds for me is the A3000. Everthing else is there.
|
04 September 2017, 20:29 | #5 |
Posts: n/a
|
Any idea why it's not finding .zip'd Romcenter-verified no-intro indexed A1200 & A4000 Kickstart's for me then?
|
04 September 2017, 20:44 | #6 |
Computer Wizard
Join Date: Aug 2007
Location: Ramberg/Norway
Posts: 928
|
You have to unpack them, because No-Intro call the KickStart archives for BIOS and they are all split in two files and not one like a real KickStart dump should have been in the TOSEC set's. In No-Intro they are 00 and 01, LOW and HIGH address area, but it's best to get your KickStart legally and not from an illegal torrent file.
|
04 September 2017, 21:13 | #7 | |
Missile Command Champion
Join Date: Aug 2005
Location: Germany
Age: 52
Posts: 12,467
|
Quote:
|
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Bounty: A500 KickStart v1.3 patch with support for scsi.device 40.63 | dJOS | support.Hardware | 75 | 28 November 2023 10:43 |
ClassicWB CD-ROM Support | Tempest 2084 | project.ClassicWB | 18 | 04 August 2016 10:19 |
ClassicWB WHDLoad support and Kickstart requirements | Bloodwych | project.ClassicWB | 0 | 29 July 2008 17:48 |
Beta/Rekick/Kickit kickstart support | gulliver | request.UAE Wishlist | 2 | 28 December 2007 18:20 |
CD32 kickstart rom & extended rom | ben111g | Amiga scene | 1 | 24 February 2007 13:56 |
|
|