Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!usc!apple!rutgers!cbmvax!daveh
From: daveh@cbmvax.commodore.com (Dave Haynie)
Newsgroups: comp.sys.amiga.tech
Subject: Re: SetCPU collides with CLI path???
Message-ID: <9440@cbmvax.commodore.com>
Date: 23 Jan 90 18:23:52 GMT
References: <1464@mit-amt.MEDIA.MIT.EDU>
Distribution: na
Organization: Commodore, West Chester, PA
Lines: 17

in article <1464@mit-amt.MEDIA.MIT.EDU>, dlleigh@mit-amt.MEDIA.MIT.EDU (Darren Leigh) says:

> 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.  

Try "SetCPU FASTROM NOPATCH".  For some reason, the PATH command relies on
the Workbench string somewhere staying "Workbench" and not "Fastbench".  I
haven't run into this problem myself, but others have definitely reported
it previously.

> Darren Leigh
-- 
Dave Haynie Commodore-Amiga (Systems Engineering) "The Crew That Never Rests"
   {uunet|pyramid|rutgers}!cbmvax!daveh      PLINK: hazy     BIX: hazy
                    Too much of everything is just enough