Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: bradhansen1 on January 08, 2022, 09:36:43 PM
-
Hi All, just updated my A1200 to 3.2.1. Where can I get information on Soft Kicking
the updated Rom file? Any information on that would be much appreciated.
Thank you,
Brad Hansen
-
There are many options for softkicking, which option to use depends on what CPU board you have.
-
You can use Blizkick to soft kick a Rom. This woks quite well for phase 5 accelerators. You can also use the flash memory in a Deneb board.
If you get a hold of Remus you can build your own Rom and the soft kick it using BlizKick or put it in the Deneb.
http://www.doobreynet.co.uk/beta/ (http://www.doobreynet.co.uk/beta/) - Remus and RomSplit
-
What physical ROM is in your Amiga? Softkicking isn’t strictly necessary with 3.2.x since individual components will all be loaded in via LoadModule in the startup-sequence - very similar to how 3.5 and 3.9 functioned.
-
Thanks for all of your input. I am trying to upgrade my 3.2 Roms in my A1200 to 3.2.1 which shows a Workbench
of .102. I updated the software but the Workbench still shows .97. So it does not seem to automatically update
the Rom as you suggest. I am running an TF1230 accelerator don't know where that puts it but will try one
of the suggested fixes.
Thank you all,
Brad Hansen
-
It looks like you have a similar query to the one I posted here, and think I have subsequently answered. https://forum.amiga.org/index.php?topic=75458.0
It also appears you can use skick with the tf1230. https://aminet.net/package/util/boot/skick346
-
What the difference between BlizKick and skick - they both allow you to soft kick a rom - is one better than the other? Ive only used BlizKick but maybe I should have alook at skick.
-
What the difference between BlizKick and skick - they both allow you to soft kick a rom - is one better than the other? Ive only used BlizKick but maybe I should have alook at skick.
Aminet description of Blizkick: MapROM tool for phase5/DCE turbos.
As Brad uses a TF card, I assumed it's not compatible.
-
What the difference between BlizKick and skick
Blizkick requires an accelerator with MapROM support. Skick works with any CPU and enough RAM.
Blizkick can load every ROM file, skick only works with ROMs for which relocation files exist (.pat and .rtb).
Blizkick protects the mapped ROM area against write accesses (like a real ROM), skick has no protection.
-
Okay, thanks for pointing me to sKick, got it setup with one issue. Skick cannot find my new Rom file in Devs:Kickstarts. I have put it in there
as A1200.47.102.RTB. per what I understood as the instructions. By holding down the left mouse button on startup it shows me a list of all
the available Roms in Kickstarts by release number, like: "47.96" and ask me to choose the one I want to use. But it's not showing my new Rom
file. Any help showing me how I should list the Rom file in Kickstarts would be much appreciated.
Thanks
Brad Hansen
-
Skick cannot find my new Rom file in Devs:Kickstarts. I have put it in there
as A1200.47.102.RTB. per what I understood as the instructions.
That's not how it works. You have to put the ROM file into Devs:Kickstarts as A1200.47.102. Then you either have to get a A1200.47.102.RTB file from the SKick author or create your own A1200.47.102.PAT file. These files list all places in the ROM file which are absolute addresses. So to create such a file, you have to seek through a disassenbled listing of the ROM and note all places which are such absolute addresses.
Section 8.2 in skick.doc describes it a bit more simple than it actually is.
-
I finally got my copy of 3.2.1. I have softkicked the rom file using BlizKick and it works fine.
My question is I also have a deneb card with flashrom. Am i better putting the kickstart image in the Deneb or softkicking with BlizKick?
Weed
-
I'd go with the Deneb - it's a much more transparent process for the system, the next best thing to replacing the physical ROM. Then you don't need to worry about special commands in your startup-sequence.