AmiKit
Convert Windows installer to FS-UAE installer
Why create the installation from the Windows version of AmiKit? Because that is the version most likely to be well-tested and supported.
Steps:
- Install AmiKit for Windows (either on a real machine or in a VM).
- Do not run any post-installation options for AmiKit, we want the unpacked
C:\AmiKit\AmiKit
directory to be clean. - Create a new 1 GB
AmiKitTransfer.hdf
file (RDB mode) and create/format an 1 GBAmiKitTransfer:
volume on in. - Set up a new WinUAE configuration with a Workbench 3.x boot floppy or boot
HD, the
C:\AmiKit\AmiKit
directory as a directory hard drive, andAmiKitTransfer.hdf.
- Start the new WinUAE configuration, booting to Workbench
- Open a shell and execute:
copy AmiKit: AmiKitTransfer: all quiet clone
. - Shut down WinUAE after the copy operation is done.
- Set up an FS-UAE config with a Workbench 3.x boot floppy, add a new
empty directory hard drive called
AmiKit
(it is important that this is not C:\AmiKit\AmiKit, but a separate empty directory), and also add theAmiKitTransfer.hdf
you created in step 3. Add the following option to custom configuration:uaem_write_flags = nhsparwed
. - Boot the FS-UAE configuration, booting to Workbench
- Open a shell and execute:
copy AmiKitTransfer: AmiKit: all quiet clone
. - Shut down FS-UAE after the copy operation is done.
The main idea of the above steps is to create a AmiKit directory hard drive with correct metadata for a few files with special metadata and/or filenames.
You can now create a AmiKit.zip
file with the contents of the new AmiKit
directory you created in step 8 to create an archive of the AmiKit installer.
After you've created AmiKit.zip, you can delete the directories and
configurations you've created as part of these steps.
FIXME: Should probably add some information about using a zip archiver with unicode support.