| From: | Alan Watson |
| Date: | 10 May 2001 at 20:19:34 |
| Subject: | Re: ny Startup Sequence gods around? |
Hey Mike,
>>> C:LoadResident Devs:Modules/IDEfix
>> Why are you doing this?
I thought it would stop a reset.Removed now,using C:LoadIDE
instead.
>>> C:MuMove4K NOREBOOT
>> If you use Harry Sintonen's 44.1 exec replacement, you won't need this
>> line at all.
How stable is it?I`ve been tempted but not too sure about it
since it`s beta.
>>> C:LoadModule L:Ram-Handler NOREBOOT
>> Use BlizKick for this.
Okay.
>>> C:MuProtectModules ON
>> Why?
Because it`s recommended in the MMULib/PatchRam docs.
>>> 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 :)
I wouldn`t say anal.PatchControl has been there since I first
installed MCP,which was a few years ago now.Never had the need
to change it.But I`ll try TRSaferPatches instead.
>>> C:StartupControl_V1.3
>> What's this for?
It listens for a lmb press/hold at boot-time and opens a menu
which lets you enable/disable WBStartup,use a PAL screenmode
in emergencies(I`m using a Voodoo3),opens a dos prompt,run
scripts/programs.It`s pretty old,but has come in handy many times
over the years.
Cheers Matt,
Regards,
ALan
Quote carefully and read all ADMIN:README mails
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/