Table of Contents
AmigaOS 3.1.4 ROM installation
Two ways are provided to install the AmigaOS 3.1.4 ROM image on Vampire Cards. You may choose between the MapROM option or the Flash option. The former method is useful for testing purposes as it avoids permanent changes to the card. The FlashROM option will directly overwrite the Kickstart image in the Card's flash such that the 3.1.4 ROM will be available at power-on.
Be careful should you choose to write the ROM into Flash. Should the flashing process get interrupted, the Vampire won't be able to boot anymore. Recovery from such a situation requires to re-flash the Core image by means of a USB Blaster.
- Vampire V2 (V500V2+ or V600V2) card
- Minimum Gold 2.10
- AmigaOS 3.1.4 ROM image purchased from Hyperion or a reseller
Suitable ROM images are the A1200, A500 or A600 releases. Other variants have not been tested by the team. Please note that Core flashing is not yet enabled/supported on Vampire V4 standalone (as of version 1.4). Use the MapROM variant in the meantime.
MapROM on Apollo-Core FPGA Cards
Non-permanent installation of the 3.1.4 ROM into a running system can be achieved by the VampireMap314 tool, provided by Apollo Team. The tool will add the additional modules to a user-provided ROM image and reboot the system with it. This method is the recommended way of testing the new ROM before a persistent installation. It should be added into the startup-sequence in the following way:
Version >NIL: expansion.library 45 If WARN C:VampireMap314 Devs:Kickstarts/kick.a1200 EndIf
The Kickstart will be mapped until a power-cycle takes place.
FlashROM on Apollo-Core FPGA Cards
An alternative to a modified startup-sequence can be achieved by a semi-permanent installation of the ROM into the Card’s Flash memory. Please note that the flashing needs to be repeated after a Core update which overwrites the whole Flash. Make sure that your system is idle before starting the flash procedure. The safest way to perform this operation is booting without startup-sequence and typing the command from CLI.
The VampireFlash314 utility takes the path of the ROM image as only argument. Example:
Please replace the example path of the Kickstart image by the actual location on your harddrive. The tool will need about 5 minutes to compress the Kickstart image after a quick verification of Flash chip type and Kickstart location within it. The flashing may commence after the compression was finished. Please confirm the flashing procedure with YES (as shown, in caps), followed by Return.
You need to power-cycle your Amiga after flashing.
WORK IN PROGRESS
Kickstart 3.1.4 ROM Image with updated intuition.library
The ability to flash updated Kickstart images has the additional benefit that reboots at cold start can be avoided. Veteran Amiga users who own Accelerators that feature the MapROM ability have been doing this for ages. A highly recommended tool for the creation of custom ROM images is Doobrey's Remus/ROMSplit combo. Please install these tools first and don't forget a close look on the “requirements” list of additional libraries and MUI classes provided on Doobrey's page.
Now start Remus and click on the “Split” button in the toolbar. Load your original ROM Image . Please note how Remus suggests an output path matching the detected Kickstart image: …Remus_path…/Modules/46.143_Hyperion(a1200) Keep that suggested Path. Klick on “Select All”, followed by “Extract File(s)”.
In the next step, the most convenient starting point for a custom ROM is by using a preset. Doobrey kindly provided a number of presets for the most common image types. Load the default project for A1200 ROMs.
If you have followed the steps above, then Remus will load the preset file and automatically add all relevant modules from the ROM you've extracted in the first step. Now go to the directory where you have stored intuition V45. Select intuition.library in the left-hand list and remove it. Drag intuition V45 into the left list view. It doesn't have to be at the exact same location but please make sure it's not the first entry. The first entry has to be exec.library.
You might want to have a look at the “settings” tab and adjust the output filename there. The other options should be kept as they were (hint: the preset covers the necessary settings already). Now the last step is the “compile” button in the toolbar.
Copy the new ROM image somewhere on the hard drive and test it by “VampireMap314” as outlined above with the new ROM image as argument. Once you confirmed that the new ROM image works as intended, you may change the MapROM command line in startup-sequence or flash it.
The same procedure applies if you have an A500/600/2000 image. The only difference is that you have to load the appropriate preset in that case.
Kickstart 1.3 with SCSI.device
While the tool is named “VampireMap314”, it's actually not limited to the specific AmigaOS ROM release that it's file name would probably imply. The Kickstart modules for the extended features of the Vampire have also been successfully tested with ROM images of Kickstarts 1.3, 2.0, 3.0, 3.1, 3.9 and various releases of Cloanto's 3.X.
The Kickstart 1.3 ROM does not contain a scsi.device driver. There is, however a patch available on Aminet that will either build a special scsi.device enabled 1.3 ROM image or a 1.3-sepecific scsi.device for use with Remus. It's assumed further on that the latter variant was chosen (i.e. a patched scsi.device was built).
In the next step, put a “ROM header” first into the ROM contents list. You'll find a suitable ROM header in the Remus distribution, as well as the Kick13ScsiPatch archive. The second module you need to add is the scsi.device itself. Save your project, compile a ROM image and that's it.
(Note: please don't mind the FC file name suffix to RomHeader in the example picture. VampireMap314 will take care of the correct values in the ROM header. It just has to be present.)
Next, call VampireMap314 with the Kickstart file, followed by the “extrom13” option whose argument is the name of the newly built Kick1.3 extension ROM. Make sure you have a drive connected that'll actually be 1.3 compatible. In the example below, the WB1.3 was booted from the default Kick for the mapping procedure.