Installed BB2 and skipped ROM updates

[Acill]

I got my system back up at last, but decided to skip the ROM update after installing BB2. Is this the correct thing to do? I've been told in the past not to use it. My system will crash on a reboot every now and then since the install. It gets an error just before WB comes up telling me RAM lib failed or something. A warp boot will fix it nine out of ten times. Any ideas? Can I just install BB2 again and choose to patch the ROM this time, or should I?

[KennyR]

Your ramlib crashes are caused by low ramlib stack. Try a ramlib stack patch (like one on Aminet) to cure this.

[Acill]

installed stack attack, is that the same thing? I just did it so we'll see if i get any more crashes.

[KennyR]

No, StackAttack only raises the stack of tasks that are run after it. ramlib appears long before this so isn't patched.

[Damion]

Hi Acill,

If you use Blizkick, the "romfixes" or "ramlibstack"
modules will also fix this problem.

[Acill]

Beeen wanting to use blizkick, but could never quite figure  it out. Could someone type a sime setup duide to get me started? Does it work on a CSPPC?

[lempkee]

acill:yes u can use it on csppc , anyway i dont have this i have only a bppc ..

but the thing is, use an uptodate version of the modules + use the 3.9 ones.

here is my line..


Blizkick * EXTRESBUF=99943 QUIET MODULE SpeedyChip shell romfixes NoClick romupdate.idtag filesystem.resource FixGetMsg console.device ram-handler exec.library fusionreserve BPPCFix


and then my setpatch line looks like this (make sure blizkick is the first line in u-s!)


C:SetPatch QUIET NOROMUPDATE


cheers..

[Framiga]

Hi KennyR

i have OS 3.9BB-2 installed and i've just noticed, that my ramlib Stack, is 2048 PRI 0.

It is right? (MCP installed for few things)

Cheers

[DaNi]

Hi! in the past i have the some problem with the ramlib error, but i add the "ramlibstack & romfixes" i correct the this error, and work fine fine. I paste my blizzkick with full BB2 in modules with a few extras:

C:BlizKick >nil: sys:devs/kickstarts/rom_v40.68 EXTRESBUF=190000 MODULE exec.library Noclick Fixmath404 PatchMath020 romfixes LocalFast NewAlert FastFileSystem FileSystem.resource scsi.device ram-handler speedyChip SoftScsi console.device bootmenu shell romupdate.idtag ramlibstack chipsaver fusionreserve movevbr

C:SetPatch QUIET WAITFORVALIDATE AVOIDMEMFKICKFORPATCHES NOROMUPDATE    

c:PatchControl

Work fine! =)

[Damion]

Hi Acill,

Blizkick can be a bit tricky to get setup. Here's a quick rundown:

Install Blizkick with the installer or by hand, just make sure
to create two directories:

sys:devs/kickstarts -- for the kickstart file(s) you wish to be mapped by Blizkick

sys:devs/modules -- the default directory for Blizkick modules

Use the tool included with Blizkick to "grab" the rom image from your machine,
and store it as a file. Now would be a good time to patch the romfile with
exec44. Put it in your devs/kickstarts drawer, named something like "kick31.rom",
"kick31rom.patched" or whatever you like.

Now the tricky part:

Put Blizkick somewhere in your startup-sequence, I put it at the very beginning
before anything else, but you may have to experiment a bit depending on your
particular card and configuration.

The bare minimum would be something like:

c:blizkick sys:devs/kickstarts/kick31.rom QUIET

This will "remap" your (hopefully patched) romfile into the fastram
of your Cyberstorm, speeding things up considerably.

You will probably want to include the names of some commands and/or module files
to your Blizkick commandline, at least the "romfixes" module:

c:blizkick sys:devs/kickstarts/kick31.rom MODULE localfast romfixes noclick A1000jingle QUIET

etc...

About the BB2 romupdate -- You don't have to skip it completely, you may only want to
avoid a few select parts...

setpatch SKIPROMMODULES "exec.library" "scsi.device" QUIET

...to skip only exec and scsi.device.

Now, there is an interesting tool that comes with Blizkick, called "romupdatesplit",
which will actually allow you to split the romupdate into it's segmented components,
and use only the ones you require as Blizkick modules. This is pretty cool, if
(for example) you wanted to use only the scsi.device from the romupdate:

c:blizkick sys:devs/kickstarts/kick31.rom MODULE localfast romfixes scsi.device QUIET

and then remember to skip the romupdate completely:

setpatch NOROMUPDATES QUIET

This will also have the added effect of completely avoiding the extra reboot
required by setpatch when you use any of the "romupdates"; there will only
be the one needed by Blizkick to "remap" your romfile and modules.

You will probably need to use the "extresbuf" option with Blizkick, to increasae
the "maprom" area. The default maprom area is only 512k...usually not enough for
the romfile and several extra modules.

c:blizkick sys:devs/kickstarts/kick31.rom EXTRESBUF=100000 MODULE localfast romfixes QUIET; etc...

I hope this helps a little, Blizkick is definately a worthwhile and valuable tool. Just
pay close attention to the docs and you'll have no problems getting it setup. If you have
anymore questions just let us know!