Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: blakespot on February 19, 2006, 06:47:27 AM
-
I installed BoingBag-1 on top of OS 3.9 after I installed the Internet tools - wanted to get the A1200 060 tower on-line with this Linksys PCMCIA card. Worked fine.
I installed both BoingBag-2 (including the ROM update) and the CardPatch & CardReset commands and rebooted. Black screen only. Cycled power - black screen. The HD spins up, etc. but doesn't sound like it's booting to the OS, so not sure what's causing the freeze. (I assumed it was ROM update.) Putting a floppy in the drive, it is not seeking that before it goes black.
I have a Blizard A1260 and 64MB FAST. The ROM update's not updating programmable EEPROMS or anything, I'm sure - so what could this be. All fine until I did the upgrade to BB2.
Thanks.
blakespot :-(
-
Your computer seems to have trouble with the romupdate.
Boot off a floppy or without startup-sequence from the early startup-menu.
Rename "AmigaOS ROM Update" into something else and it should work again. It's in the DEVS: drawer.
You could also edit your startup-sequence and add noromupdate after QUIET.
-
have you try to boot from the Emergency floppy? maybe there is a conflict with the update of the scsi.device.
i use CardPatch & CardReset before setpatch and blizzkick and it works fine.
-
Hmm...
I now have three ROM update files (two disabled w/ rename obviously) in my SYS:Devs dir, after BB2. Here they are:
AmigaOS ROM Update.old 127956 17-SEP-00
AmigaOS ROM Update 321768 26-FEB-02
AmigaOS ROM Update.BB39-2 321768 26-FEB-02
...It seems that BB2 moved what was existing prior to install to .old and overwrote the actual ROM name, and left another copy of itself named .BB39-2. Right?
So it's likely that I was booting fine with the .old file in place, correct? Or should I wipe that too?
Thanks.
blakespot
-
There is an alternative to all of this, actually.
If you donwload the latest version of BlizKick:
http://piru.dyndns.org/~p/sw/
...you can use an included tool to extract all the files from the Amiga ROM Update file. Then, you can use BlizKick to manually load each file as a module.
Use the NOROMUPDATES option with SetPatch during the following process. If you do this you can try each file out, and see which one is causing the trouble. When you have located the updates which caused trouble and loaded the others as modules (they must be loaded before SetPatch) you can keep the NOROMUPDATES option on SetPatch for good and go on as normal.
-
amije wrote:
have you try to boot from the Emergency floppy? maybe there is a conflict with the update of the scsi.device.
i use CardPatch & CardReset before setpatch and blizzkick and it works fine.
I got it going - I put CardPatch, CardReset near the top of Startup-Sequence, before the setpatch. I boot and get a amber colored Recoverable Error (guru looking but not red) - I click and I'm into Workbench and Genesis will start fine.
Every time.
Is there some other trick to launching these two little binaries?
Thanks.
blakespot
-
I'm not sure if both programs are required. That also depends on the card you use. It could be that your card doesn't need it, check this site:
http://www.g-mb.de/pcmcia_e.html
I also seem to recall that Blizkick has an optional module for cardpatch/reset. Don't know for sure though...
-
i use for years blizkick and it's very cool, but a bit tricky to handle and needs a lot of hours to find what works ok and what not. after all these years i still can't make things like poseidon.library or subway.device to boot with it...
anyway the latest rom update is that with 321768 bytes v44.57.
the name must be: AmigaOS ROM Update.
i use cardpatch and cardreset with this order and arguments and they work fine:
C:CardPatch
run >:NIL C:CardReset TICKS 50
first of all in the ss
that's all
-
Have a look on aminet for BK_resetcard.lha this is a pcmcia card fix module for blizkick.
-
@RussellB: today looks like you have plenty of good ideas :-)