| From: | Matt Sealey |
| Date: | 10 May 2001 at 13:33:58 |
| Subject: | Re: ny Startup Sequence gods around? |
Hello Alan
On 09-May-01, you wrote:
> I`m looking for some advice on how to reduce the number of reboots
> my Amiga makes before WB loads.ATM it`s 4.The reasons you`ll find
> below in the first few lines from my startup-sequence.
The Doctor is IN!
> C:BlizKick * EXTRESBUF=175000 SPEEDROM Devs:Modules/FixGetMsg
> Devs:Modules/RomFixes Devs:Modules/SoftSCSI Devs:Modules/NewAlert
> Devs:Modules/AlertFix QUIET
SetEnv ENVARC:BKMODPATH Devs:Modules/
Remove each occurance of Devs:Modules/ from the BlizKick line :)
> C:LoadResident Devs:Modules/IDEfix
Why are you doing this?
> C:MuMove4K NOREBOOT
If you use Harry Sintonen's 44.1 exec replacement, you won't need this
line at all.
> C:LoadModule L:Ram-Handler NOREBOOT
Use BlizKick for this.
> C:OpenOxyPPort
>
> C:SetPatch SKIPROMUPDATES "scsi.device ram-handler" QUIET
Use BlizKick to load ALL of the SetPatch modules, and use the
NOROMUPDATE flag (or rename Devs:AmigaOS Rom Update to
something else).
> C:MuProtectModules ON
Why?
> C:StackAttack MIN=8192 ADD 2048
> C:PatchControl
If you're being anal about your ss, use TRSaferPatches instead of
PatchControl - it's by the same guy who did muLib, you may as
well keep like with like (and it's better IMO :)
> C:MuFastZero MoveSSP FastExec ON
I don't have this line. Moving the SSP seems pointless. And with
the 44.1 exec (and by a quirk of me using LocalFast as an option
for Blizkick) exec is in Fast RAM anyway.
> C:StartupControl_V1.3
What's this for?
If it's any use, here are the first few lines of my SS:
~~
;Set Echo "ON"
Stack 8000
C:StackAttack MIN=8000 ADD=1092
C:BlizKick QUIET DEVS:kick441 EXTRESBUF=80000 LocalFast scsi.device FastFileSystem filesystem.resource ram-handler console.device NoClick
C:LoadIDE QUIET
C:SetPatch NOROMUPDATE QUIET
~~
Thanks
Quote carefully and read all ADMIN:README mails
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/