 Documentation about the Vampire hardware |
| Vampire V2 Doesn't Start After Upgrading to 2.17 | |
|---|
|
|---|
| | 
Karol Wnuk
Posts 2
22 Jan 2024 20:30
| Hi guys,
Today I decided to upgrade my Vampire 1200 v2 from core 2.15 to 2.17 (V1200_G217B_BRONTO.jic). I used VampireFlash tool. The upgrade seems to be done successfully. However - after switching power off and on it only displays Vampire v2 logo with signature "Gold 2.17", falling fruits pictures and dinosaur in the bottom left corner.
I guess the upgrade didn't completely brick the card, but I'd expect the OS to load...
Before the upgrade I was running AmigaOS 3.2 with original ROM uploaded into Vampire. I use a CF card attached to the Vampire IDE port, as well as SD card inserted into socket. Everything was working fine before the upgrade...
I don't know what I can do to bypass the logo screen and go into the CLI/OS mode? I tried holiding 2 mouse buttons for early start up menu, but it doesn't work. The only thing that happens apart from displaying the logo is that floppy drive LED blinks for a few seconds, even though I don't have a floppy drive installed.
Any hints on what I can do now?Link to picture of the screen: EXTERNAL LINK
| |
| | 
Son Goku
Posts 39
23 Jan 2024 09:30
| If you can see the boot logo, the flashing was successful.
As described, did you carry out the SAGA update on your OS before the core update and adjust the startup sequence?
Core 2.16/2.17 no longer work with the old SAGA tools.
You can now connect a VGA Moitor and see if you can get to the boot menu and your CF card is displayed there. This only works with RGB conneted, since the V1200 can't display native modes over DIGITAL-VIDEO.
| |
| |
Karol Wnuk
Posts 2
23 Jan 2024 22:28
| Thanks for the response. Yes, I upgraded the SAGA tools (from 2.7 to the latest 3.1). Stupid me... I didn't switch video inputs on my screen. I've got IndivisionMK3 and I was under impression that it doesn't display any output for some reason. I think I just didn't wait long enough before switching to PAL/AGA. All good, just switched the inputs and the usual failure (LoadModule doesn't work for some reason) appeared. I was able to map rom 3.2 and system loaded successfully. BTW - does anyone know why it the LoadModule command fails during the original AmigaOS 3.2 boot? I'm tempted to test the Vampire ROM as it supports Amiga LEDs. When I map ROM 3.2 my LEDs don't blink durigng HDD/Floppy drive operations.
| |
| | 
Sean Sk
Posts 488
24 Jan 2024 00:12
| Karol Wnuk wrote:
|
I'm tempted to test the Vampire ROM as it supports Amiga LEDs. When I map ROM 3.2 my LEDs don't blink durigng HDD/Floppy drive operations.
|
I don't think the default Vampire KS ROM will work with Amiga OS 3.2. You need to use the corresponding KS 3.2 ROM. If you want your HD LED to blink when using a CF attached to the V1200's own IDE header, then you will need this adapter: EXTERNAL LINK
If you PM djbase directly at the Apollo Discord channel he will be able to help you out with these.
| |
|
|
|
