Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
system_tools:kickstarts [2020/02/29 01:21]
muaddib
system_tools:kickstarts [2021/05/16 10:14] (current)
renaudschweingruber_txg59n64 [Installing Kickstarts]
Line 11: Line 11:
 These methods are detailed in their own sections below. ​ Some general information:​ These methods are detailed in their own sections below. ​ Some general information:​
  
-  * For method 1, you need ''​VampireMap314''​. For method 3, you need ''​VampireFlash314''​. ​Please ​obtain them from one of the following archives and copy them to ''​C:'':​ +  * For method 1, you need ''​VampireMap''​. For method 3, you need ''​VampireFlash''​. ​To obtain them, download and install ​the latest ​[[saga:updates|SAGA Drivers package]]. 
-    * Stable: ​[[http://​www.apollo-accelerators.com/​files/​AOS314VampireTools.lha|v1.2]] +  * The Vampire is compatible with all Kickstart versions from 1.1 to 3.2 and AROS Kickstart. All ROM sizes (256 KB, 512 KB and 1 MB) are supported. 
-    * Beta: {{:​vampireflashmapv14.zip|v1.4}} +  * Kickstart ROM variants for A1200, A600A500 or CD32 are suitable. Other variants have not been tested. 
-  * The Vampire is compatible with all Kickstart versions from 1.1 to 3.1.4 to 3.9 to 3.X to AROS Kickstart. All ROM sizes (256 KB, 512 KB and 1 MB) are supported. +  * If you are using a 512 KB ROM image, then the methods described below will automatically add Vampire-specific Kickstart modules to the extended ROM area between $E00000 and $E7FFFF. These extended modules have been successfully tested with ROM images of Kickstart versions 2.0, 3.0, 3.1, 3.9, 3.1.4, 3.2 and various releases of Cloanto'​s 3.X.
-  * Kickstart ROM variants for A1200, A600 or A500 are suitable. Other variants have not been tested. +
-  * If you are using a 512 KB ROM image, then the methods described below will automatically add Vampire-specific Kickstart modules to the extended ROM area between $E00000 and $E7FFFF. These extended modules have been successfully tested with ROM images of Kickstart versions 2.0, 3.0, 3.1, 3.9 and various releases of Cloanto'​s 3.X.+
     * If you are using a 1 MB ROM image, then it already occupies the extended ROM area, so you need to ensure that it already contains Vampire-specific Kickstart modules.     * If you are using a 1 MB ROM image, then it already occupies the extended ROM area, so you need to ensure that it already contains Vampire-specific Kickstart modules.
-  * You can use an EmuTOS ROM as a Kickstart replacement.+  * If you are interested in Atari software, you can use an EmuTOS ROM as a Kickstart replacement.
  
 ===== Available methods for switching to a different Kickstart ===== ===== Available methods for switching to a different Kickstart =====
Line 24: Line 22:
 ==== 1) Running a "​MapROM"​ program to load the Kickstart ROM image from disk ==== ==== 1) Running a "​MapROM"​ program to load the Kickstart ROM image from disk ====
  
-The ''​VampireMap314''​ tool will map a Kickstart ROM image from disk to memory and reboot the system with it. The mapped Kickstart will survive through soft resets, but will be lost after a hard reset.+The ''​VampireMap''​ tool will map a Kickstart ROM image from disk to memory and reboot the system with it. The mapped Kickstart will survive through soft resets, but will be lost after a hard reset.
  
 **Usage:** **Usage:**
  
-  >VampireMap314 ​<​path_to_kickstart_file>​+  >VampireMap ​<​path_to_kickstart_file>​
  
 If you are planning to map Kickstart 1.3, you probably want to inject support for booting from an IDE storage device. You can do that with an "​extended Kickstart ROM" file, as described in [[os:​amigaos:​v1.3|AmigaOS 1.3 on the Vampire]]. Then, you can include the "​extended ROM" file in your mapping operation like this: If you are planning to map Kickstart 1.3, you probably want to inject support for booting from an IDE storage device. You can do that with an "​extended Kickstart ROM" file, as described in [[os:​amigaos:​v1.3|AmigaOS 1.3 on the Vampire]]. Then, you can include the "​extended ROM" file in your mapping operation like this:
  
-  >VampireMap314 ​<​path_to_kickstart_file>​ extrom13 <​path_to_extended_kickstart_rom_file>​+  >VampireMap ​<​path_to_kickstart_file>​ extrom13 <​path_to_extended_kickstart_rom_file>​
  
-Once you confirm that the Kickstart ROM image works as intended, and you want to stay on it going forward, you can add the ''​VampireMap314''​ command to the beginning of your ''​S:​Startup-Sequence''​. ​ Or, you can even flash the ROM image into the Core using method 3.+Once you confirm that the Kickstart ROM image works as intended, and you want to stay on it going forward, you can add the ''​VampireMap''​ command to the beginning of your ''​S:​Startup-Sequence''​. ​ Or, you can even flash the ROM image into the Core using method 3.
  
 **Example usage in ''​S:​Startup-Sequence'':​** **Example usage in ''​S:​Startup-Sequence'':​**
Line 42: Line 40:
   If WARN   If WARN
     ; Use the correct Kickstart file path.  If mapping an extended ROM file with Kickstart 1.3, add the appropriate arguments.     ; Use the correct Kickstart file path.  If mapping an extended ROM file with Kickstart 1.3, add the appropriate arguments.
-    C:VampireMap314 ​DEVS:​Kickstarts/​kick.a1200+    C:VampireMap ​DEVS:​Kickstarts/​kick.a1200
   EndIf   EndIf
  
Line 55: Line 53:
   * Wastes a bit of time after every hard reset, due to booting (partly) into the OS and rebooting during mapping.   * Wastes a bit of time after every hard reset, due to booting (partly) into the OS and rebooting during mapping.
  
-**Note:** If you want to map an AROS Kickstart ROM or an EmuTOS ROM, you need to use ''​[[system_tools:​vcontrol|VControl MAPROM]]''​ instead of ''​VampireMap314''​.+**Note:** If you want to map an AROS Kickstart ROM or an EmuTOS ROM, you need to use ''​[[system_tools:​vcontrol|VControl MAPROM]]''​ instead of ''​VampireMap''​.
  
-==== 2) Letting the Core load the Kickstart ROM image from an SD card during power-on initialization ​====+==== 2) Running a "​FlashROM"​ program to install ​the Kickstart ROM image into the Core's flash memory ​====
  
-After powering on the Amiga / Vampire, the Core will map a Kickstart ROM image from an inserted SD card to memory and run the system with it. The mapped Kickstart will survive through soft resets, but will be lost after a hard reset. +The ''​VampireFlash''​ tool will flash a Kickstart ROM image from disk into a location in the Core that is reserved for a Kickstart ROM, overwriting the existing Kickstart there. The flashed Kickstart will survive through soft and hard resets. However, a new Core installation will revert the Kickstart to the default one contained in the Core.
- +
-**Usage:​** +
- +
-  - Make sure the SD card is formatted with the FAT32 filesystem. +
-  - Save the Kickstart ROM image with the filename ​''​kick.rom''​ in the root directory of the SD card. +
-  - Insert the SD card before powering on the Amiga / Vampire. +
- +
-Once you confirm that the Kickstart ROM image works as intended, and you want to stay on it going forward, you can flash the ROM image into the Core using method 3. +
- +
-**Advantages:​** +
- +
-  * Useful for testing purposes as it avoids permanent changes to the Core. +
-  * Makes it possible to switch to a different Kickstart **mechanically**,​ without needing access to the OS or a special program. +
- +
-**Disadvantages:​** +
- +
-  * Requires the SD card to be inserted at every hard reset. +
- +
-**Note:** This method does not work on Vampire accelerator boards connected to a classic Amiga yet. +
- +
-==== 3) Running a "​FlashROM"​ program to install the Kickstart ROM image into the Core's flash memory ==== +
- +
-The ''​VampireFlash314''​ tool will flash a Kickstart ROM image from disk into a location in the Core that is reserved for a Kickstart ROM, overwriting the existing Kickstart there. The flashed Kickstart will survive through soft and hard resets. However, a new Core installation will revert the Kickstart to the default one contained in the Core.+
  
 **Usage:** **Usage:**
Line 88: Line 63:
 Make sure that your system is idle before starting the flash procedure. The safest way to perform this operation is booting with no Startup-Sequence and typing the command from the CLI. Make sure that your system is idle before starting the flash procedure. The safest way to perform this operation is booting with no Startup-Sequence and typing the command from the CLI.
  
-  >VampireFlash314 ​<​path_to_kickstart_file>​+  >VampireFlash ​<​path_to_kickstart_file>​
  
 The tool will need about 5 minutes to compress the Kickstart ROM image, after a quick verification of the flash chip type and the Kickstart location inside it. The flashing may commence after the compression is finished. Please confirm the flashing procedure with YES (as shown, in caps), followed by <​key>​Return</​key>​. The tool will need about 5 minutes to compress the Kickstart ROM image, after a quick verification of the flash chip type and the Kickstart location inside it. The flashing may commence after the compression is finished. Please confirm the flashing procedure with YES (as shown, in caps), followed by <​key>​Return</​key>​.
Line 110: Line 85:
 **Note:** This method does not work with AROS Kickstart ROMs and EmuTOS ROMs. **Note:** This method does not work with AROS Kickstart ROMs and EmuTOS ROMs.
  
-**Note:** This method does not work on the Vampire Standalone yet. 
  
 ---- ----
Last modified: le 2020/08/02 12:37