Help!! Startup-Sequence

[protek]

I was installing the Boing Bag 4 into my A4000 all went well until I was prompted to edit the Startup-Sequence with a few lines. I did the changes requested and saved. Now, when I boot I only get CLI and the Startup-Sequence only has the lines that I added or edited. :banghead: How is it possible that the editor omitted everything that was after those lines?

There was an old backup of Startup-Sequence made by BB1 and with that I managed to boot but it's most probably missing all the loadmodule and setpatch lines.

What should I try to do? Should I just re-install all the Boing Bags in sequence and hope that I don't f**k up anything this time? I haven't made any own changes into it so it should be pretty vanilla otherwise.

 

[mfilos]

Why don't you just attach a txt file with the Startup-Sequence of yours, so we can help a bit

 

[protek]

I no longer have the f**ked up Startup-Sequence but it practically contained the lines that were instructed to be entered and modified in the install script of the Boing Bag 4. I'll copy and post the the old backup that I now have restored a little later.

 

[Geraldine]

Oh, I recall that "fun" with Boing Bag 4. I just gave up with it and stuck with Bong Bags 1&2.

 

[protek]

I seem to be in luck. I've got a backup of my hard drive in another CF card. That contained the Startup-Sequence with BB3 settings. I'm going to copy that over to the other CF and give a try.

 

[mfilos]

I never had any issue with BB3 or BB4. Just needs a bit more attention than the other official ones.

 

[protek]

Well, the Startup-Sequence is in the same shape as it was prior to installing the BB4.

The BB4 stuff is there. Is there a way to find the instructions to edit the SS from the installation script or should I just back up the SS, re-install BB4 and hope for the best?

 

[mfilos]

You can check my own BB4 Startup-Sequence's LoadModule declaration, which I used before burning my custom Kickstarts...

C:LoadModule L:FastFileSystem S:Mods/RAM-Handler L:Shell-Seg S:Mods/scsi.device S:Mods/icon.library S:Mods/workbench.library Libs:mathffp.library Libs:mathieeesingbas.library NOREBOOT REVERSE
C:SetPatch SKIPROMMODULES fs,icon,ram,scsi.device,shell,workbench QUIET

The S:Mods/ directory is a folder where I keep all the new modules which I load in the kickstart. Just replace it with where you have the modules installed (Libs/Devs etc). Also I think that the matthffp/mathieeesingbas are my registered HSMathLibs that I load as well so you can ignore as well.

 

[cosmicfrog]

I found in some screen modes it wouldt show you all of what u had to add/change in startup sequense, so I just loaded up the install file and did a bit of cut and past

 

[protek]

I found the suggested changes to the Startup-Sequence from the BB4 install script

"You should add these lines to the start of S:Startup-sequence:\n\n"
"FailAt 21\n"
"SYS:C/LoadResident >NIL: LIBS:dos.library DEVS:card.resource DEVS:trackdisk.device\n"
"FailAt 20\n\n"
"and change the existing LoadModule line to:\n\n"
"SYS:C/LoadModule >NIL: L:FastFileSystem L:RAM-Handler L:Shell-Seg LIBS:dos.library LIBS:icon.library LIBS:workbench.library REVERSE NOREBOOT"

And this from BB3:

"You should add these lines to the start of S:Startup-sequence:\n\n"
"SYS:C/LoadModule L:FastFileSystem L:RAM-Handler L:Shell-Seg DEVS:scsi.device LIBS:icon.library LIBS:workbench.library NOREBOOT REVERSE\n\n"
"SYS:C/SetPatch SKIPROMMODULES fs,icon,ram-handler,scsi.device,shell,workbench QUIET\n\n"
"and remove the existing SetPatch line."

What do the FailAt lines mean and why is scsi.device omitted from the BB4 loadmodules?

 

[AmiNeo]

Stuff like this can happen easily with just a space in the wrong place if something has been edited manually. Perhaps it may be worth going over each line with a fine eye...

 

[mfilos]

I dunno why scsi.device was omitted from the script but I guess it needs to be in the LoadModule declaration.
FailAt usually goes in scripts in case something's is missing it won't give an error.

I guess you should combine the declarations like that:

FailAt 21
SYS:C/LoadResident >NIL: LIBS:dos.library DEVS:card.resource DEVS:trackdisk.device
FailAt 20
SYS:C/LoadModule L:FastFileSystem L:RAM-Handler L:Shell-Seg DEVS:scsi.device LIBS:dos.library LIBS:icon.library LIBS:workbench.library NOREBOOT REVERSE
SYS:C/SetPatch SKIPROMMODULES fs,icon,ram-handler,scsi.device,shell,workbench QUIET

I today installed BB3+BB4 on my Custom ClassicWB 3.9 installation including CGX4+AfAOS and stuffed the following modules into Deneb's Flash ROM:
- BB2 Romupdate,
- BB3+BB4 LoadModule modules plus
- Morelibspace_Module from AfAOS and some other Luciferin's modules like:
- BBlank, FixGetMsg, NewAlert, NoCardSlot, NoClick.

The only things I haven't put so far were:
- Dos.library (cause it's updating everyday)
- Card.resource (cause afaik it's used only for PCMCIA devices alas no need for A4000)
- Trackdisk.library (cause I already have NoClick that works)

System runs pretty stable and rebootless with no issues with no LoadModule/LoadResident and SetPatch as following:

C:SetPatch NOROMUPDATE QUIET

 

[rkauer]

The FailAt script command is to set the level of the return code error another command send back after its execution.

Original value of FailAt is 10, using 20 makes no "command did it right" messages to show, so the script can continue even if an error appears. Only real errors opens a window telling something, but the Startup-Sequence (which is a script) will continue to run.