Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!elroy!gryphon!richard From: richard@gryphon.COM (Richard Sexton) Newsgroups: comp.sys.amiga Subject: Re: Creating a CLI Message-ID: <14456@gryphon.COM> Date: 9 Apr 89 06:17:39 GMT References: <149@dunkirk.DKK> Reply-To: richard@gryphon.COM (Richard Sexton) Distribution: comp.sys.amiga Organization: Trailing Edge Technology, Redondo Beach, CA Lines: 37 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 a wild assed guess, but could you be running out of memory ? I loathe handshake because it's so obese (100K), but I't the only thing I've founf that works reliabaly with 48 lines of vi. Comm works fine in 24 line mode, but screws up in 48 line mode. If I'm modeming, I usually have to exit handshake to do something else, and then get back into it. Sick. So if you are having trouble with lack of memory (I have 1 MB) maybe you could use Comm or Jez Sans little 8K Amigoterm. Both are on PLINK. Where's my $5 kickback, Laser ? -- ``The second big surprise was that horse conchs, the biggest, baddest, most fearsome univalves in the Atlantic Ocean, like cooked squash.'' richard@gryphon.COM decwrl!gryphon!richard gryphon!richard@elroy.jpl.NASA.GOV