Path: utzoo!attcan!uunet!lll-winken!lll-tis!oodis01!uplherc!utah-gr!stride!tahoe!malc
From: malc@tahoe.unr.edu (Malcolm L. Carlock)
Newsgroups: comp.sys.amiga
Subject: PopCLI (and regular CLI) Question
Keywords: damn thing ALWAYS wants the WorkBench disk.  AAAAARRRGGGHHH!!!!
Message-ID: <1298@tahoe.unr.edu>
Date: 14 May 88 02:06:35 GMT
Organization: Univ. of Nev., Reno-Mathematics
Lines: 39

I may be missing something obvious here, BUT . . .

I have installed in my ASDG-RAM (vd0:) the following:

	NewCLI
	CLI
	EndCLI
	CLI.info

VD0: is the second name in my search path, after "current directory".

Up till now, whenever I click on the CLI icon in VD0:, I get a disk requester
for WorkBench if WorkBench is not currently in a drive.

A friend advised me to start using PopCLI.  I dutifully installed PopCLI in
my WorkBench C: directory, and placed into my startup-sequence the following
line:

	run popcli 300 newcli >nil:

This allows PopCLI to run fine, AS LONG AS WORKBENCH IS INSERTED!!
I also tried

	run popcli 300 vd0:newcli >nil:

which also works fine, AS LONG AS WORKBENCH IS INSERTED!!  If WorkBench is
not in a drive, I still get the *&*$#$@&!% system requester!

However, if I type "newcli" in a CLI window, whether WorkBench is inserted or
not, I get a new CLI window with no problem.  But just try getting it from
the icon in VD0 or via PopCLI, and no soap!

Why can't I bring up a CLI window from the WB screen or using PopCLI without
having the &*&^*&#^$# WB disk inserted?

Thanks.

Malcolm L. Carlock
-----------------------------------------------------------------
malc@tahoe.unr.edu.UUCP		       University of Nevada, Reno