Path: utzoo!attcan!uunet!lll-winken!ames!oliveb!tymix!antares!jms
From: jms@antares.UUCP (Joe Smith)
Newsgroups: comp.sys.amiga
Subject: Re: Creating a CLI
Message-ID: <439@antares.UUCP>
Date: 16 Apr 89 04:17:24 GMT
References: <149@dunkirk.DKK>
Reply-To: jms@antares.UUCP (Joe Smith)
Distribution: comp.sys.amiga
Organization: Tymnet QSATS, San Jose CA
Lines: 31

In article <149@dunkirk.DKK> will1990@dunkirk.UUCP (The phone Cops) writes:
>
>Being a one drive user, I am trying to create a disk that will boot on
>its own, run a vt100 emulator (handshake) from icon, and be able
>to open a CLI (or shell, whatever) for disk activity... such as 
>unarcing and copying, etc.

I have the following startup-sequence on my "vt100" disk:

setpatch >nil:
stack 50000
setmap usa1
run vt100
wait 18
dmouse -s0
setclock opt load
newcli con:8/70/632/130/CLI
echo "This window will go away when VT100 exits."
loadwb
endcli

The "wait 18" is overkill, it was optimal for the version of vt100 that needed
to read in j132.font.  The main thing is that I can press F10 (which dials
the phone) and get logged in without having to wait for WorkBench to finish
gronking the disks.  In many cases it is more convenient to start up a
second CLI from your startup-sequence and punt off the original CLI.
-- 
Joe Smith (408)922-6220 | jms@antares.Tymnet.COM or jms@tymix.Tymnet.COM
McDonnell Douglas FSCO  | UUCP: ...!{ames,pyramid}!oliveb!tymix!antares!jms
PO Box 49019, MS-D21    | PDP-10:JMS@F74.Tymnet.COM  CA license plate:"POPJ P,"
San Jose, CA 95161-9019 | narrator.device: "I didn't say that, my Amiga did!"