Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: punkyclown on August 14, 2015, 10:53:48 PM
-
Well there I was happily installing the Boing Bags and during Boing Bag-2 it ask me if I wanted to update my Rom, feeling extremely confident I clicked yes. The install finished and ask
me to reboot. And I did that, and then I got a big Pink Screen... I have a Forever Amiga
CD but how do I replace my Rom? How do I do anything?
help....
Brad Hansen
-
Well there I was happily installing the Boing Bags and during Boing Bag-2 it ask me if I wanted to update my Rom, feeling extremely confident I clicked yes. The install finished and ask
me to reboot. And I did that, and then I got a big Pink Screen... I have a Forever Amiga
CD but how do I replace my Rom? How do I do anything?
help....
It didn't do anything to the physical ROM. BB2+ soft-loads a ROM update file, that's why the double reboot (if you ever watched an updated 3.9 system boot, it boots once to load the updated modules and whatnot, and then a second time to load the OS. Basically similar to how the LoadModule (http://aminet.net/package/util/boot/LoadModule) command works. Read the description in the link).
What model of Amiga are you using? And what model did you specify in the requester?
I'm going to throw this back out there again - doesn't 3.5 also have some ROM update modules? According to this link (http://www.gregdonner.org/os35faq/installtips.html#15) it does. I would bet money on you still having some conflicting files between your old 3.5 install, and 3.9.
In any case, here's your perfect opportunity to do that fresh install we talked about, or at a minimum, go 3.1-to-3.9. I never liked 3.5 and have tried to avoid it like the plague, haha. ;)
-
Mike, your a breath of fresh air, but your leaving me in the dark a bit. My system is an A1200
with a 6830 upgrade module with 32 msg of ram. I tried to run the 3.1 install disk, no luck, still the pink screen. How would I begin to start over...?
Thanks
-
Okay, forget that... I got it. Thanks...
-
Okay, forget that... I got it. Thanks...
Could you tell us how you fixed it as I had the same problem and ended up formatting my drive and re-installed everything minus the rom update
-
Sure, Sorry, I just copied over the "Installer" file from my OS3.9 CD and that did the trick.
Oh, the Pink screen, Yeah I just did what you did, started over and re-installed everything.
No real fix.
-
No need to re-install - just boot without startup-sequence (if you're stuck in a crash loop then do this from a cold start, before the ROM update has a chance to kick in) and then rename the update file from the AmigaDOS shell. It's in Devs: and is called something like AmigaOSRomUpdate.
SetPatch calls the ROM update and if it can't find it (i.e., it's been renamed) it'll skip past it.
The ROM update has some compatibility problems with certain hardware that can cause crashes. If you want to get most of the functionality of the ROM update back, you can selectively skip certain modules that cause conflicts by using command line arguments on the SetPatch line in the startup-sequence. See the OS3.9 FAQ (http://www.gregdonner.org/os39faq/os39faq.html).
Also, if you run one of those utility programs early in the startup-sequence to reserve memory for Mac emulation you can get rid of it. That functionality is built into the ROM update and running one of those programs AND the ROM update can cause the crash loop you described.
-
We might all love it but Amiga OS 68k is one PITA to set up compared to the latest versions of other OS. I guess I'm getting too old for faffing around! Once set up though it makes me smile.
-
It's pretty easy if you have working floppy drive and Workbench
disks that came with Amigas that supported HD and CD.
Making it shine is more of a effort but you can take some things from
AmigaSYS ClassicWB or Amikit to speed things up.Better way (long way)
is to add every patch and library manually as well as right (stable) versions
of software and when something start to crash because you added
something else you delete that something else.My system is rock solid but
far from up to date which doesn't bother me as I like compatibility to old
stuff.
-
I never liked 3.5 and have tried to avoid it like the plague, haha. ;)
I LOVE OS3.5! Am I the ONLY one? Especially for an A1200 WHDLoad machine! :laugh1:
-
I'm tempted to make a list of software that works on kick 3.0 but
fails to work with kick 3.1 :-)