Can't install 3.2 or 3.2.1 if Amiga Forever is installed in Windows

[HVR88]

If you have Amiga Forever installed on your system, setting up a pre-build (8gb example) with 3.2 or 3.2.1 will fail and abort in the first steps of installation after launching WinUAE.

CAUSE: The image setup script detects Amiga Forever and copies 3.1 adf into the root of the "amigaos" folder. When the installation is started in WinUAE, it will try to install 3.1 but the active KickStart is 3.2 or 3.2.1 from the previous setup steps.

MANUAL SOLUTION: Before running WinUAE, open "amigaos" folder and delete the 3.1 adf files.

I mentioned this here: https://www.youtube.com/watch?v=-weyDLMZwLo&t=586s

[henrikstengaard]

Use hstwb_image_setup_patch_only instead of hstwb_image_setup with Amiga OS 3.1.4+.

Differences between the 2 scripts:

• hstwb_image_setup:
  • Detects if Amiga Forever is installed, if present, Amiga Forever adf and rom files are copied to amiga os directory.
  • Scans amiga os adf and kickstart rom files and updates WinUAE and FS-UAE emulator config files.
• hstwb_image_setup_patch_only:
  • Scans amiga os adf and kickstart rom files and updates WinUAE and FS-UAE emulator config files.