classic only runs my apps once

[kev j]

if i launch classic and then say photoshop all is well. if i quit this app the try to launch any other classic app i get an unexpected error and absolutly nothing will launch again without relaunching classic. so , i can only use one app at a time and then i have to rebbot classic again. apple seem to think i must have osx on the same drive(but different partion) as os9.

my setup

dp800
3 hardrives'
hd 1(ide) os9.22
hd2 (ide)-
hd3 (uw scizi)os10.1.2

help please


kev j

p.s a format a reinstall does not seem to solve this, also 9.2.2 works great on its own and so does 10.1.2 so i am reluctant to start again

[griffman]

What extension set do you run in Classic mode? If it's not a stripped set, try setting "OS 9 base" and see if the problem repeats -- you can do this through the second pane of the Classic prefs panel, so you don't need to restart in OS 9 to test it.

Also, if you create another user and then test the same Classic with that user, does the problem persist?

-rob.

[lerkfish]

several possibilities:
1. I don't think a reinstall is necessary, what is happening is that your classic is actually crashing, but since OSX continues chugging along, it doesn't seem like it. Sometimes if classic crashes, you need to boot from it once to troubleshoot. For example, if you crash and it has corrupted a preference, some prefs for the classic system will not reset until you actually boot from it instead of OSX.
2. sounds like photoshop is a real good place to troubleshooting. What kind of fonts or font utilities do you use? A corrupted font could be causing this problem.
3. You can try resetting the finder memory for the classic apps larger (photoshop)
4. Photoshop and virtual memory don't get along well. If you have virtual memory running within your classic environment, turn it off as you don't need it while running OSX anyways.
5. you can check/change the location of your scratch disk in photoshop. Similarly, you can save often to keep an overlarge temp file being created, and purge all often.
6. You can rebuild classic desktop, and trash finder, os, and other pertinent prefs to rebuild them.
7. If you use ATM you can trash prefs and fontsets and create fresh ones...

[kev j]

ill try the extensions first. also i dont think its photoshop as that is the only app that works

kev j

[kev j]

tried using a very striped set that didnt work still wont let another app open after i have opend the first one.


9.22 never crashes when boot into it and use on its own

photoshop ect have plenty of ram

virtual men is never on as i have 1.25 gigs of ram

i dont use any font utilities as i only have the system fonts in there.

it also does it when im logged in as another user

kev j

[lerkfish]

what happens if you boot from your classic (9.2.2) system and try to launch the problem programs? If they launch OK under 9, but not under 10, then you might need to 'rebuild classic desktop' from the advanced tab in OSX.

what might help is if you listed the programs this is happening with.

also, what is the exact nature of the "unexpected error"? do you get an actual error dialog, and if so, what does it say?

[kev j]

if i boot from 9.2.2 all is fine as i use it alot of the time.
as for the programs .its all of them.
here is what happens

im in osx and i d-click photoshop(or any other app) , it launches classic and all is fine, i can use the app with no probs. what i cant do is launch a second app at all or quit the app im using and the relaunch it. all i can do is re boot classic and start again.
the error message only says that the application has unexpectantly quit.

ive tried various apps

lightwave
c4d
painter
lots of others.

apple support told me that i must have 9.22 and osx on the same drive but with different partitons and i shouldnt have 9.22 on one drive and x on another, but even when this was the case it still did it.

kev j

just one thing , i put 10.1 on from an installer that came with my i book not my g4 that wouldnt have anything to do with it would it.(not the all in one 2 disk thingy but the seperate 10.1 disk)

[lerkfish]

i'm unfamiliar with the apps mentioned enough to know whether they are indeed usuable in classic at all. Not all apps are updated to be accessible in classic, hopefullysomeone will come along who is more familiar with those apps.

[hschickel]

Just out of curiousity - what are the permissions on your Classic System Folder?

I'm going to take a wild guess and say that something is not getting written to the preference files as it should and this is causing the crashes. The fact that all works fine in 9 and your problems continue with no extensions lead me even more in this direction.

Hugh

[kev j]

all these apps do work under classic as i have spoken to others who are using them,

what would you suggest i do. i could always install another 10.1.2 on the partitoned 9.22 hd as i have plenty of room

kev j

[hschickel]

I would not reinstall. This may be something as simple as a permissions problem.

Depending on how you handled you OS9 installation the "System Folder" and "Applications (Mac OS 9)" folders can have some wacky permissions. Or even worse, from a security standpoint, permissions for everyone.

After extensive testing I've found the following works quite well for all Classic applications and the system. In any case, its better than some of the screwy permissions that seem to crop up in a stock install:

***Do the following at your own risk. This is a rather broad system change that some would recommend against (probably for good reason. :) )

System Folder: owner root - rwx; group admin - rwx; other - rx
/System Folder/Preferences: owner root - rwx; group admin - rwx; other - rwx
Applications (Mac OS 9): owner root - rwx; group admin - rwx; other - rx

Note: the write permissions on the preferences folder for other is only necessary if you have non admin users using the Classic environment. Another more secure option here (Preferences folder) would be to make the group staff - rwx and other - rx.

Hugh

[kev j]

do i just type this into the terminal ?

kev j

[hschickel]

This Knowledge Base Article (http://docs.info.apple.com/article.html?artnum=106677) just came from Apple. It discusses troubleshooting the Classic environment.

Hugh

[hschickel]

This is a quick and dirty gui method. I believe its safe but ymmv. Let me know if you would like to know the terminal method to do the same thing.

1. Download BatChmod (http://www.versiontracker.com/moreinfo.fcgi?id=12057&db=mac). This is a gui front end to change some of X's permissions. This application can be very useful and very dangerous. Use it with extreme care.

2. Drop your System Folder onto BatChmod.

3. Set the owner to Root and check the r, w and x boxes. Set the Group to Admin and check the r, w and x boxes. Under everyone check the r and x boxes and uncheck the w box.

4. Under "Enclosed files and folders" check the box "Apply ownership and privileges".

5. Click the apply button button and enter your admin password at the prompt.

6. If you have non admin users who need to access Classic repeat the process above with the Preferences folder from the System Folder with this difference: under everyone the r, w, and x boxes should all be checked.

***I have found many Classic applications permissions issues can be solved by dropping Applications (Mac OS 9) onto BatChmod and applying permissions as to the System Folder. If you do this please make sure that only Classic applications are in Applications (Mac OS 9). X apps can have internal permissions that differ from these and you can screw them up.

***Under no circumstances should this utility be used in bulk on any X directory. You will screw up the internal permissions and render some or all of your system inoperable.

Good luck.

Hugh

[kev j]

You are not gonna believe this??????!!!

after reading every article/forum on the apple site i found a thread someone mentioned about memory allocation.

i have reduced the allocation to photoshop etc about 50 megs or so and all works.

wierd or what, too much ram to the apps kills them.

kev j

[hschickel]

Good.

And you didn't even have to mess with the permissions.

Hugh

[kev j]

thanks for your time and help


kev j