#2.04 Startup
10 messages in this thread
Since a few week`s I have a problem with booting-up my 2.04 OS which
drives me crazy. When I switch – on my A2000 first thing I get the
requester "Please insert ENV in any drive", after cancel the system
continuse to boot. Then after a while I`m asked to select a "KEYMAP" from
Extras – Disk which I did long time ago and after the system knows what
keymap I use. But since a few weeks the stupid machine ask`s me every time
I switch`m on. I trie`d everything I could think of, get "SETMAP" in C,
WBSTARTUP and SYSTEM directories. To make sure I put "SETMAP d" in to my
"Startup-sequence" without any sucsess.
BindDrivers
Failat 25
Mount VD0:
c:setpatch >NIL:
c:version >NIL:
setmap d
makedir VD0:T
makedir VD0:clipboards
makedir VD0:ENV
makedir VD0:ENV/SYS
assign ENV: VD0:ENV
assign T: VD0:T
assign CLIPS: VD0:clipboards
copy >NIL: ENVARC VD0:ENV all quiet noreq
DHOpts CNC:0/10/640/240/Horst-WShell/CLOSE PIP: MENU S:CNC-Menus
Mount PATH: from DEVS:path-mountlist
addbuffers >NIL: df0: 30
addbuffers >NIL: df1: 30
addbuffers >NIL: df2: 30
Assign TXT: FH0:BT-II/Text
Resident >NIL: C:Execute PURE ADD
Makedir VD0:Downloads
assign Downloads: VD0:Downloads
Makedir VD0:Telefaxe
assign Telefaxe: VD0:Telefaxe
if exists sys:Monitors
join >NIL: sys:monitors/~(#?.info) as t:mon-start
execute t:mon-start
delete >NIL: t:mon-start
endif
setenv Workbench $Workbench
setenv Kickstart $Kickstart
IPrefs
echo "Amiga Release 2. Kickstart $Kickstart, Workbench $Workbench"
conclip
mount speak:
mount aux:
mount pipe:
path ram: c: sys:utilities sys:rexxc sys:system s: sys:prefs sys:wbstartup
addif exists sys:tools
path sys:tools add
if exists sys:tools/commodities
path sys:tools/commodities add
endif
endif
; If this is the initial boot (i.e. keyboard env variable is not set)
; then execute PickMap which will query for a keymap and set the
; keyboard env variable.
;
; if keyboard env variable is set, set the keymap
if ${sys/keyboard} NOT EQ "*${sys/keyboard}"
setmap ${sys/keyboard}
<continued>
Horst,
Looking at my startup-sequence three things come to mind:
1. BindDrivers is not executed until after ENV: is setup
2. the copy command that sets up ENV: refers to ENVARC: not ENVARC
3. the setmap command is after ENV: is setup
You might try playing with these things to see if it makes any
difference.
Hope this helps, 8)
David
One other creeb comes to mind. Make the changes to user-startup. Try to
leave startup-sequence as "pure" as possible so that OS upgrades do not
throw you back into the stoneage away from your usual environment.
{@_@}
Joanne,
Definitely. Maybe I wasn't as clear as I thought, since that's what I've
been trying to say in this thread. I try to leave the startup-sequence as
stock as possible in my machine.
There are, though, certain things that, should you want/need to do them,
need to go into the startup-sequence so that they're run before other
system programs. (Like running Enforcer quiet before Binddrivers if you
have a Bridgeboard, running the special MergeMem command that came with my
Ramworks board so that I have FAST memory, or mounting VD0: and changing
the RAM: references if you want to use it.) I _do_ highly recommend
leaving startup-sequence alone, but, there are legitimate exceptions to
the rule.
I think that we're saying the same thing. 8)
David
(Repeat – lose VD0:. It causes problems with later versions of the OS.)
{o.o}
Joanne,
I like your picture of Betty Boop at the end of your messages. 8^)
Ron
Joanne,
well, this make`s sense. I think I have to work on this now. I still have
the original startup-sequence on WB-disk. What crashes you`r talking about
?? I havn`t experianced anything now, what is your recommendation???
– Horst –
– via Whap!
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.
{@_@}