As stated in the documentation you need a 3.1 Kickstart ROM for the A1200 - not the A4000 model. Please check again exactly which Kickstart roms are supported here. Make sure you use single file and unencrypted ROM variants as those are the ones currently supported.
These ADF files must be UNMODIFIED and Original copies of the Workbench 3.1 install floppies. The imager tool only supports unmodified versions since changes may introduce incompatibilities which break the automatic install system. There are several different versions of the AmigaOS 3.1 Workbench out there (originally from Commodore, later on sold with Escom Amigas and now sold by Cloanto and their Amiga Forever package) - All of these official versions are supported.
It’s likely you used the Escom 3.1 ADF files, and unfortunately these are missing several key features such as languages and tools. If you have Commodore or Cloanto ADF files available then add them to your ADF search folder and the tool will prioritise them over the cut-down Escom images.
When copying files, you should overwrite older versions with newer update and hotfix files when prompted.
As detailed in the instructions, the default output for the is RGB. You will need to connect your Amiga to your monitor via the DB23 port.
It’s possible the Startup-Sequence was overwritten by your update. Check for if the install process has saved a previous version as part of the upgrade process and copy the sections marked as “modified by Powershell” into the new version of the startup-sequence.
The tool is written in Powershell. Limitations in Powershell (and frankly the knowledge of the coder) make a graphical output difficult. Two examples:
Downloads of the various packages uses standard Powershell functionality. Showing progress for downloads either requires using the standard Powershell output or there is no output whatsoever
Updating progress to a Window is possible, but introduces significant delay in order for Powershell to update the window. “Significant” delay means in some circumstances the tool would take twice as long to run versus what it does now.
In summary, functionality over aesthetics.
Network drives should work in relation to selecting folders for the copying of ADF and Kickstart ROM files, as well as for the Transfer Folder if you have the appropriate access rights for the locations on your network and you use mapped network drives. UNC links are NOT supported.
You cannot use a Network location for the Working Folder or to run the tool. While this possibly could change in the future, there are some limitations that prevent this at the current time including with HST-Imager.
In order for the tool to run correctly (both to set up the SD card as well as write the image to it), the tool needs to run as Administrator. Depending on your set up of mapped network drives you may not be able to see them in the tool. This is a known issue in Windows. Please see the following article from Microsoft:
Note, changes suggested in the article (e.g. changes to your registry) could cause damage to your system and is done at your own risk!
This tool is provided for users who have legally acquired versions of the ROMs and ADFs. If you do, you should have no issue accessing the required files (e.g. using the Hyperion website to download any updates).
If you’ve chosen to “sail the high seas” that’s your choice but you will need to work out how to acquire the complete set. It is not something we can point you towards
The issue is seen where the tool fails at the ‘Preparing Amiga Image’ section where the tool is initialising the partition. This has been noted as an issue with users who have the IBM Trusteer Rapport software, an Endpoint protection tool installed and may be an issue with similar software. Unfortunately, if this issue is noted there is currently no way around this other than disabling the software when running the imager. If you do this please remember to reenable the software after running the imager!
The tool is using the currently available version of Emu68 and Emu68 tools. By all means, reach out for support but please consider if your issue relates to the imager or Emu68. If the later, then it is not something the tool can resolve. However, please raise the issue in the appropriate forum if you encounter it (e.g. the emu68-support channel on Discord)
If you have the full version of Roadshow, copy the bsdsocket.library from the install package to the Libs folder on the Workbench drive. You can either use the option to transfer files when you run the tool (please refer to the Supplying your own additional files section) or copy the files to the FAT32 partition.
The tool is intended to provide a basic image to help you get started, to avoid common pitfalls such as RTG and internet issues and using 100% legally acquired software. Once you have a basic set up you have access to the internet as well as a suitably sized SD card where you can transfer whatever you need to add additional software.
It can be a rewarding experience learning about how to install software on your Amiga. However, if you are after a fully set up and customised distribution with all games and applications pre-installed and where you can write an image to a SD card and just use it then you should download and use one of those.
Short answer: There is none.
Longer answer: The GUI is built using WPF (Windows Presentation Foundation), which as the name suggests, is Windows specific. More importantly, while Powershell (the main language the tool is written in) is supported on Mac and Linux, some of the tools used are not. As an example, 7zip is used to extract LHA archives and this is not available on either Mac or Linux. Unfortunately the Unlha tools themselves have certain limitations. It also makes direct changes to the physical device meaning WINE or similar will not work.