Noob questions about Amiga OS 3.2

[olliethebasset]

Hello folks! I am considering purchasing Amiga OS 3.2 and I wanted to ask a question first. Has anyone installed it on an a500 running an ACA500plus? If so did you incur any difficulties? I’m a little new to working with Amigas so I want to anticipate any complications. My hope was to take the ROM, map it onto the ACA500plus, put the CD in my PC, pop the install disks onto my Gotek and do a fresh install on a CF card running 3.1. Will this work? Alternatively, I could do the installation on a CF card in WINUE. Please let me know if you can provide any guidance.

M

 

[miggymad]

Your OS 3.2 CD will have a copy of the correct ROM file on it for use in WinUAE as standard. There is no need for you to dump it from physical ROM chips.

Yes, you can pop the OS3.2 cd into your pc, copy the adf files to your gotek and install directly to your A500 without any problems. Just make sure you swap out your current kickstart chip with the 3.2 one first

Also remember to keep the boot partition on your CF card below the 4 gigabyte limit. For example, in one if my Amiga's I have a 300mb boot partition for Workbench ( DH0: ) , a 1gb partition called Work ( DH1: ) for dpaint protext xcopy etc and a 56gb partition for games and music ( DH2: ).

Any problems, come back and post some more. Somebody will come along and provide more help and guidance.

Oh and don't forget to check the plastic shrinkwrap for the OS3.2 registration number! Hyperion in their infinite wisdom put the label there instead on something like the manual or inside the case itself.

 

[miggymad]

@olliethebasset 1 more thing before I forget ...

When copying the adf files to your gotek, DON'T rename them as the install script looks for them by name as well as the disk title itself

 

[Boing-ball]

Just to add to Miggymads write up on installation. Technically you don’t need the updated ROMs to start with. Why? As the installer will pick this up and copy over and update the Startup-sequence the updated and any missing modules. Just means that the system will boot a bit slower as it executes the new modules on startup.
As for MAP Romming the new 3.2 or 3.2.1 ROMS (Don’t forget you need the license key to access and download the 3.2 updates including the latest ROM 47.111 from the Hyperion website). Then yes, I have done this with my Blizzard 1230 and 1260 cards using the Blizkick utility. Again just means you will get a reboot as the system executes into the new ROM.