Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!ira.uka.de!smurf!nadia!aragon!vampire
From: vampire@aragon.gtc.de (Kai Kapp)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Running CLI from DF1:
Message-ID: <8180@aragon.gtc.de>
Date: 7 Feb 91 18:33:48 GMT
References: <1991Jan25.035427.15004@usenet.ins.cwru.edu>
Organization: aragon, Sindelfingen, Bundesrepublik D
Lines: 38

nnn@po.CWRU.Edu (Nik N. Nik Mahdi) writes:


>Hello,
>   I have a problem. Whenever I boot a disk without a CLI file
>or Icon, I could not run the CLI when I have a disk with a CLI
>file in DF1:. 

There is another way of doing this.
If you boot with another disk as your workdisk you have to assign the pathes
in the right way.
If you click the shell and get your info from the workbench it says :
Default-Tool : SYS:SYTEM/CLI
ok, now there is in df1: the workbench disk and in df0: another one, from
which you have booted. SYS: is always the disk from which you booted.
So the Shell (or CLI-icon) looks for DF0:system/cli !!!
                                     ===

Just put in the startup-sequence of df0: the following (or just type it each
time you booted.)
assign sys:c df1:c
assign sys:fonts df1:fonts
assign sys:l df1:l
assign sys:devs df1:devs
assign sys:libs df1:libs
assign sys:system (if there is at all) df1:system
assign sys:prefs df1:prefs
just assign all the Dirs ...
assign sys: df1:

This should work ... if you still have questions ... write me

--------------------------------------------------------------------------------
|This is REALLY written by | /		| /				       |
|			   |/		|/				       |
|			   |\  a  i	|\  a  p  p	From STUTTGART 	       |
|			   | \     	| \				       |
--------------------------------------------------------------------------------