SetCPU collides with CLI path???

Article View: comp.sys.amiga.tech

Article #2898

Back to comp.sys.amiga.tech Previous Next

#2898

From: Darren Leigh
Date: Tue, 23 Jan 1990 03:33

18 lines
1311 bytes

I have found a problem between SetCPU and the CLI path function.  I
run setcpu and and set up a new path in my startup-sequence.  When I
use the fastrom option, the CLI path is deleted (actually set to C:)
or not accepted.  I have tried various combinations of putting one
before the other and in other startup files without result.  Path
seems to work fine in a CLI when I do it manually, but I can't get it
to coexist with fastrom in the startup-sequence.

I use SKsh so the loss of the CLI path doesn't hurt me much.  The
problem is with things like the Lattice "lc" command which looks for
the files "lc1" and "lc2" apparently using the CLI path.  In other
words, I can't get "lc" to work while I have fastrom installed.
Anybody have any ideas?

My system:  A2500, 1.3, SetCPU 1.50, Arp 1.3

Darren Leigh
dlleigh@media-lab.media.mit.edu

Technical Details

Message-ID: <1464@mit-amt.MEDIA.MIT.EDU>

Path:

arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!samsung!think!snorkelwacker!mit-eddie!mit-amt!dlleigh

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!samsung!think!snorkelwacker!mit-eddie!mit-amt!dlleigh
From: dlleigh@mit-amt.MEDIA.MIT.EDU (Darren Leigh)
Newsgroups: comp.sys.amiga.tech
Subject: SetCPU collides with CLI path???
Message-ID: <1464@mit-amt.MEDIA.MIT.EDU>
Date: 23 Jan 90 03:33:43 GMT
Reply-To: dlleigh@media-lab.media.mit.edu.UUCP (Darren Leigh)
Distribution: na
Organization: MIT Media Lab, Cambridge MA
Lines: 18