#SetCPU1.5
6 messages in this thread
I couldn't stop the SetCPU command from walking over my PATH settings, no
matter where I put the SetCPU command. I checked with Dave Haynie and he
wasn't sure of the reason. Anyway, I moved my PATH instructions into my
Shell-Startup script. This works but I don't know if it would work for
everyone.
-Rich
I am having the same problem with SetCpu1.5. One night on line I talked with
someone from microbiotics (Can't quite remember his name) who was a great help.
He figured It was Knocking out the path because It was renaming workbench to
fastbench, so after using to NoPatch option we found out he was right. Now I
have the same problem with my keyboard. (Repeating Chars.) I believe this could
be fixed if the program didn't name workbench to fastbench. If anyone has any
contact with Dave HAynie maybe they could tell him this. Please keep me
informed if you hear any more
Rick
Richard,
I read a message from Dave on Usenet about the fastbench thing. He suggested
that you take a copy of the program and use NewZap or something like that –
search through the program for all mentions of "Fastbench" and change them to
"Workbench" with the filezapper. You might try that.
Betty
richard, the nopatch isn't the reason. I am using SetCpu 1.5 and have the
same problem (loss of path). I had to put path in the shell-startup file which
isn't really an acceptable alternative. It appears to do some strange things to
other programs, as well. The PD hack, DropCloth, which puts a 4 color 640×200
image as the backdrop for workbench doesn't even run.
— Ethan
I,ve done the same thing, but when I did use NoPatch my workbench wasn't
renamed, and my paths were still good. But when I did use NoPatch it must
affect the keypatch option because I started losing control of mykeyboard at
times, so I guess the best comprimise is to not use nopatch, set the paths in
my shell-startup and wait for a fix. I looked for the word fastbench with a
diskeditor to try and change it but I couldn't find it in the program. Im also
on Bix and if I hear anything I'll let you know.
Rick
I've found a Fix!!
I tried looking for the string "Fastbench" in the SetCPU program but missed it.
(I don't have the best disk editor.) After ricieving a message from Betty that
she recieved from Dave Haynie I decieded to give it another try, and guess
what? I found it!! After finding it I changed it to "Workbench" tried it again
and it still didn't work. My screen was now named Workbench but when I
pressed my menu Button one of the menus was named FastBench. I had noticed the
string "Fast" written right before "FastBench" when I used the Disk editor and
decided to try changing it to "Work", rebooted and everything was fixed. (No
more having to set the Paths in the shell-startup)
So you don't have to go searching for these strings I'll tell you right where
there at.
If you have a disk editor load SetCPU and at Byte 5006(HEX) you'll find the
string "Fast". Change it to "Work". At Byte 500B(HEX) you'll find the string
"Fastbench". Change it to "Workbench".
Thats all there is to it. Hope this helps you out.
Rick