Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!mips!apple!bionet!ames!pacbell!att!mcdchg!mcdphx!teroach.UUCP!stan
From: stan@teroach.UUCP (Stan Fisher)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: SetCPU
Keywords: SetCPU, wIconify, A2630
Message-ID: <12578@mcdphx.phx.mcd.mot.com>
Date: 7 Mar 90 21:48:48 GMT
References: <63+#YL=@rpi.edu> <12568@mcdphx.phx.mcd.mot.com> <264@vela.acs.oakland.edu>
Sender: news@mcdphx.phx.mcd.mot.com
Reply-To: stan@teroach.UUCP (Stan Fisher)
Organization: Motorola Microcomputer Division, Tempe, Az.
Lines: 29

In article <264@vela.acs.oakland.edu> dlcogswe@vela.acs.oakland.edu (Dan Cogswell) writes:
>
>Stan, did you ever think of zapping the SetCPU executable to patch simply
>the name "Workbench"??  That kinda solves all problems, you know?
>-- 
>Dan Cogswell                         | If *ONE MORE*    | Disclaimer:
>(313)625-3234                        | person makes     | Oakland University
>INET: cogswell@vela.acs.oakland.edu  | a joke about     | doesn't HAVE a
>      cogswell@unix.secs.oakland.edu | "Cogswell Cogs!!"| position on this.


Sure! I haven't tried it yet though, 'cause... I gotta say..  I think it's
totally bitchin' to have my Workbench screen called Fastbench ;^)
Makes it _feel_ even faster! :^)

Acutally wIconify is the ONLY program I've had show any conflict with
SetCPU fastbench patch...  and I wasn't sure if patching SetCPU to stick
WorkBench in for WorkBench (instead of FastBench) would break anything 
within SetCPU.

Maybe Dave H. could answer that?

Good point though!  Then you wouldn't need any scripts to detect which CPU
is booted to determine which wIconify to use.


  Stan Fisher -  stan@teroach.phx.mcd.mot.com -  asuvax!mcdphx!teroach!stan
  Motorola Microcomputer Division, Tempe, Arizona   -  Voice (602) 438-3228
  Call our User Group BBS "M.E.C.C.A." running Atredes 1.1 @ (602) 893-0804