Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!usc!venera.isi.edu!schur
From: schur@venera.isi.edu (Sean Schur)
Newsgroups: comp.sys.amiga
Subject: SetCPU/CPU Crashes My 3000
Message-ID: <14390@venera.isi.edu>
Date: 21 Jul 90 20:49:01 GMT
Reply-To: schur@venera.isi.edu (Sean Schur)
Organization: USC-Information Sciences Institute
Lines: 21

I guess I am writing to Dave Haynie, but if anyone else knows great. I would
like to disable FastRam on my 3000 to see if some applications which don't 
run now might run that way. However if I use "SetCPU NOFASTRAM" in either
2.0 or 1.3 or alternately the CPU command that comes with 2.0. The system 
crashes immediately. Is there something I can do to make this work? Why would
the arguement for NoFastRam be included under 2.0 if it just crashes the 
system? Also I have tried clicking on the NoFastRam icon but it doesn't seem
to do anything. If I inquire with CPU (no arguments) after clicking it says
Fast Ram is still enabled.

==============================================================================

			     \          /
			      \   \    /      / 
Sean Schur		       \   \  /      /
				\   \/      /
USENET: schur@isi.edu		 \  /a\mpyr/
Compuserve: 70731,1102		  \/   \  / ideo 
Plink: OSS259				\/ 

==============================================================================