Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: PulsatingQuasar on December 29, 2006, 01:13:59 PM
-
I have a problem with Blizkick and a Cyberstorm mk2. I use the same BlizKick command line on all the Amiga's I can get my hands on; BlizzardPPC, 1230, 1260, Cyberstorm mk 2, 3 and PPC.
Only with the mk2 I get a yellow screen after the ROM has been kicked with a prepatched ROM and some modules. It then constantly tries to reboot ending in a yellow screen again UNTILL I reboot manually by using Ctrl-A-A. Everything is OK after that. The ROM HAS been kicked then. I checked.
So what goes wrong when the reboot happens by BlizKick instead of CTRL-A-A?
This problem only occurs with the mk2. Anybody with an idea why this happens? Can it be that I have to set the 'Slow Inquiry Mode' on the SCSI module?
-
For the Cyberstorm mk2 I have found that if I take out the exec.library in the MODULE list( the one from OS 3.9 BB2) then I don't get the yellow screen.
Does anybody else have this problem?
-
PulsatingQuasar wrote:
For the Cyberstorm mk2 I have found that if I take out the exec.library in the MODULE list( the one from OS 3.9 BB2) then I don't get the yellow screen.
Does anybody else have this problem?
Think Doobrey made a new Remus or was it Romsplit that works with OS3.9 exec.library
I use BlizKick and a custom kickrom on my CS MKII but I use Piru's exec 44.1beta
-
OK, I did that now too. Any downside to using the exec 44.1??
-
PulsatingQuasar wrote:
OK, I did that now too. Any downside to using the exec 44.1??
None that I have found :-)