Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!usc!elroy.jpl.nasa.gov!ames!sparkyfs!unix!hplabs!hp-sdd!ncr-sd!ncrcae!usceast!yarnall
From: yarnall@usceast.UUCP (Ken Yarnall)
Newsgroups: comp.sys.amiga.tech
Subject: "SetCPU FASTROM" weirdness
Summary: It interacts strangely with Path
Message-ID: <3164@usceast.UUCP>
Date: 28 Mar 90 03:07:24 GMT
Organization: Math Department, University of South Carolina (ahem; The USC)
Lines: 21

I have a few questions about SetCPU.  

First, I when I envoke "SetCPU FASTROM", the path command doesn't seem to
work correctly.  Path will set the path correctly in the current Shell, but
if I fire up another Shell (by double-clicking the Shell Icon), the second
Shell doesn't inherit the path.  If I specify "SetCPU FASTROM NOPATCH",
everything is fine.  Is this a known bug?  I *like* the FastROM patches --
they keep my disk drive from clicking!  I would like to be able to use the
Patches with impunity...

On a lesser note, does it make any difference when SetCPU is run, relative to
SetPatch?

If it matters, I have a 2500/30.

Thanks, 
ken
-- 
Ken Yarnall                             yarnall@cs.scarolina.EDU
Math Department, USC			yarnall@ucseast.UUCP
Columbia, S.C. 29208			(803)777-6686