OS9, MouseWorks and file corruption?

rhinosaur

rhinosaur

Registered
Okay, I was going to let this go as a fluke until it happened twice.

I recently got a Kensington TurboRing and installed the MouseWorks software on my Quicksilver 733 at work. I work mostly in OS X, but occasionally I'll have to spend quite a bit of time in 9. This was the case after I installed the MouseWorks software. All was fine until one day, upon a restart, my Apple Menu items crashes my machine. So I turn off Apple Menu items and go about my business because I have deadlines.

The next day, (in OS9 still), I begin to get these erratic "finder unexpectedly quit" errors. And they're followed by every app that I have open doing the same thing. Fortunately, my tight deadlines are behind me and I can boot back into OS X to get some work done.
I blissfully forget about my problems until, once again, I need to boot into 9. Rather than go through a painful extension conflict test, I do a quick reinstall of 9.1 and run the 9.2.1 updater. Reinstall a few control panels and extensions (mouseworks being one of them)...some of them I just move from my "previous system" folder. VIOLA...everything is fine, until...

I take the MouseWorks software home...I frequently take my TurboRing home with me to help me adjust to the new device...after just a day or two in 9, guess what? Apple Menu options crashes my start up! Then I get all kinds of "quits" again...just like at work. So I resort back to OS X to get what I can done.

Yesterday...either my Apple Audio Extension or my CD/DVD extension on my work machine crashed the start up process. I disabled it. Haven't even booted into 9 to see if anything quits unexpectedly quits. And I had already replaced the CD/DVD extension with an older version to address the previous problems with 9.2.1...so I think the extension was good.

I guess I'm just wondering if anyone else has had these kinds of problems using OS 9.2.1 and MouseWorks. It really ticks me off because the MouseWorks software has a ton of features for OS 9 that the OS X version doesn't have, and it only seems to wreak chaos on my machine.

One other note...another guy here at work is also running MouseWorks, without a problem on OS 9.1...he doesn't use OS X...so he hasn't updated OS 9 accordingly.

Comments, suggestions, etc., welcome...thanks.
 
Pardon me if this is an obvious question, but are you running two different versions of MouseWorks? There are separate versions for OS 9 and OS X, and if you're using the wrong version for the OS that you're in, that might be the cause of your problems.
 
I'm using the proper version for each OS. I'm pretty sure the OSX version won't run in OS 9, and my extension set for OS 9 disables the Kensington Extensions, so there's know way that I could accidentally run MouseWorks for 9 in X. Any other ideas?
 
I have also experienced this apple menu crash (3 times now) but I do not have mouseworks. this appeared to have started back in 9.1 when the apple menu stopped replacing recent applications. I didn't bother with it then since the only app i ever launch there was included. Since upgrading to osx and experiencing the problem i have tried several methods ike yourself but have found that simply removing the applemenu control panel (removing, NOT disabling) cause the system to generate a new one. My current one has lasted about a week or more thru 4 or 5 9.2.1 reboots. I still am not sure what causes this but I am pretty sure it is not your kensington software. I have not yet rebooted to 9 since installing 10.1.1 yesterday. maybe apple addressed this somewhere. And anytime you have any wierdness with your dock on the sides, try moving it back to the bottom. this seems to cure a lot of osx problems for some strange reason.
anyone know more about this?:rolleyes:
 
Way back when, as a method of speeding up Classic's launch time, I disabled the AppleMenu Options CP. Do those of you who are getting AppleMenu crashes have it enabled?
 
Yes gengiscohen, it is enabled when it crashes. The fact is that i find it a very useful tool when running 9, and even more so now as it is the nicest way to access startup disk options when booting back & forth. I left it disabled after one of the crashes for awhile but just found that I missed it too much not to give it another try. Actually, once Appleworks gets all the bugs out and Toast goes fully functional in x, i will not have much use for it anymore. (i hope !!!)
 
You must log in or register to reply here.
Back
Top