2.04 Startup
In regards startup-sequence leave it as stock as possible. It is not a
crashes issue as much as an upgrade issue. I have reduced the changes to
startup-sequence around here to two edits. (One if I had ROMs instead of
using a special command to allow me to test new versions of kickstart or
am working off my A3000 which is still running the kickstart ROMs.) The
first is the first executable line in the script which tells my A2000 to
load newer kickstarts. The second change is fairly early in the script and
runs off to another script which runs such commands as must be run early
in startup-sequence to make them effective. (The binddrivers/janus/
enforcer example comes to mind as one such. I use the script to install
pathhandler, point to some special pathing I want done early, and run up
WShell's DisplayHandler. I do the special pathing early because I have no
non-distribution or non-Commodore commands on system2.0: barring maybe
three files. I use pathhandler to make new definitions for things like S:
that follow a path to several subsidiary s directories where scripts I
need are run.)
Re VD0: I don't remember what crashes. I just remember comments by several
developers that their machines have run more stably under 3.x once they
nuked VD0:. No "proof" there. But it is suggestive.
{@_@}