Path: utzoo!mnetor!tmsoft!dptcdc!jarvis.csri.toronto.edu!me!radio.astro!helios!utpsych!davidb
From: davidb@utpsych.toronto.edu (David Brodbeck)
Newsgroups: comp.sys.amiga
Subject: Re: Creating a CLI
Message-ID: <1989Apr19.063412.25745@utpsych.toronto.edu>
Date: 19 Apr 89 06:34:12 GMT
References: <149@dunkirk.DKK>
Reply-To: davidb@psych.toronto.edu (David Brodbeck)
Distribution: comp.sys.amiga
Organization: Psychology, U. of Toronto
Lines: 26

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.
>
>Simple task, right....?
>So I get everything working fine, having all the neccessary libs, devs
>and handlers, etc. I try to get a CLI, first by copying it over(including)
>s:CLi-STartup, and everything that even looked like it was neccassary..
>But when I run it(double click the icon), it opens a CLI window for
>a split second and closes it up again.  I've even tried using the WB1.2
>prefs to "turn on a CLI" (1.3 doesn't have this feature), assigning C:
>, and everything I can Think of. 
>
>I cannot understand what I'm doing wrong, any suggestions?


	Just don't issue then endcli command in the startup-sequence, voila
you are left with a cli!
-- 
***********************************************************************
      //  | Dave Brodbeck - University of Toronto Psychology |   GO     
     //   | davidb@psych.toronto.edu   davidb@ziebmef.UUCP      HABS
\\  //    | brodbeck@vm.utcs.utoronto.ca                     |  G O