classic logjam, can't work

[rooneytunes]

I can't work properly if I can't get this fixed.I had this problem several months ago and it resolved itself but is now back to haunt me. I've trawled the discussions and Apples FAQs and found no cures that actually worked only folks with the same problem but no answers. I vaguely remember a suggestion about "flags" but can't be sure what that was about.
Double-clicking files created in some Classic apps doesn't open the files, just the app. Graphic converter opens fine but not PS or Illustrator, indeed sometimes after PS launches in the dock the printer icon momentarily attempts to launch but doesn't.
I've trashed the relevant plist files, rebuilt the desktop in classic, ran disc utility, did the file info routine, and priveleges routine, ran classic from the same disc as X and off another disc and nothing works. Logged in as root and tried the above and still no luck. What's gone wrong? I was able to work normally for several months, I haven't updated anything. This is seriously slowing down my workflow.
OS10.1.3, classic is of course 9.2

[tlarkin]

If you hold down the cmd + opt keys and then use the mouse to drag the icon of your file over the app you use to view it with and then release the mouse button. what happens?

example:

hold down cmd + opt and select a .pdf file with the mouse. then drag that .pdf file over the acrobat icon and then release it. This will force that application to open that file.

Also what does your system log say when you launch the file

[rooneytunes]

Thanks for the response.
As follows, option/command dragging the file over PS icon starts up classic and PS, as soon as PS open something else attempts to load in the dock, it's VERY quick and looks like a printer icon, but doesn't load and PS sits there, no file.
With PS already open the same procedure gets me a rfequest to locate an additional plugins folder, then asks me to allocate a scratch disc, the PS opens and again, no file.
It's a real handicap as I have GBs of files, many folders and archives deep and usually use iView to browse them, then iView would have let me open my selection with 'creator' which is assigned to PS but I've lost that now.
These logs you mention what are they for and where are they?
Peter

[tlarkin]

the system log is in the /var/log folder. I would launch the application like normal by double clicking one of your files. then switch back from classic to OS X and open up the terminal. once in the terminal type this code:


tail -50 /var/log/system.log | more

OR

dmesg


Either of those commands would work. look through your log and see if any errors pop up when you are opening the app with that file.

copy/paste the log on this forum, also have you tried the open with option on your files?

[mervTormel]

dmesg and the system.log are not related except that entries in dmesg may get into system.log

dmesg is a small, system message buffer that is a push queue where new messages will push old messages off the cliff after it reaches a certain size.

[rooneytunes]

well I get the following with the first text
18:45:12 localhost mach_kernel: WS DSL: ---> DESIRED LEVEL : 2
more
the second text gets me a massive file, I'll copy the last chunk, the rest of it is simply as follows
WS DSL: !Session


last chunk as follows
pppoe_wan_attach, link index = 0, (ld = 0x4105e04)
WS DSL: reject unsuitable options.
WS DSL: message = 0xe0000101
enable_filters: SIP_PROTO_ENABLE -already set flags=29
enable_filters: SIP_PROTO_ENABLE -already set flags=29
enable_filters: SIP_PROTO_ENABLE -already set flags=29
[localhost:~] peterboy%

[tlarkin]

One thing you may want to try and its easy and quick is: make a new test user account, and then open up your files and see if it will open up in that app.

[rooneytunes]

But I get the same thing when logging in as root , but I'll try your suggestion.

[rooneytunes]

Nope, same thing, PS opens but no file, same with any PS file and yes of course I did the 'open with application rourine and trashed PS prefs etc.
Peter

[tlarkin]

do'h sorry did not read that you logged in as root sorry.

[rooneytunes]

Yep it's definitely a printer icon which attempts to launch when PS finishes launching.
Tried the first text command again, here's the full report
tail -50 /var/log/system.log | more[localhost:~] peterboy% tail -50 /var/log/system.log | more
Jun 4 19:38:29 localhost pppd[545]: Terminating connection due to lack of activ
ity.
Jun 4 19:38:29 localhost configd[146]: executing /System/Library/SystemConfigur
ation/Kicker.bundle/Resources/restart-NetInfo
Jun 4 19:38:29 localhost configd[146]: executing /System/Library/SystemConfigur
ation/Kicker.bundle/Resources/set-hostname
Jun 4 19:38:29 localhost configd[146]: executing /System/Library/SystemConfigur
ation/Kicker.bundle/Resources/restart-lookupd
Jun 4 19:38:29 localhost lookupd[219]: Caught SIGHUP - reset
Jun 4 19:38:29 localhost pppd[545]: Connection terminated.
Jun 4 19:38:29 localhost pppd[545]: Connect time 26.2 minutes.
Jun 4 19:38:29 localhost pppd[545]: Sent 16429 bytes, received 168310 bytes.
Jun 4 19:38:29 localhost pppd[545]: PPPoE disconnecting...
Jun 4 19:38:29 localhost mach_kernel: WS DSL: Session closed.
Jun 4 19:38:29 localhost pppd[545]: PPPoE disconnected
Jun 4 19:38:29 localhost mach_kernel: WS DSL: ---> DESIRED LEVEL : 0
Jun 4 19:38:29 localhost mach_kernel: WS DSL: ---> PRESENT LEVEL : 0
Jun 4 19:38:29 localhost mach_kernel:
Jun 4 19:38:29 localhost configd[146]: executing /System/Library/SystemConfigur
ation/Kicker.bundle/Resources/restart-automount
Jun 4 19:38:29 localhost pppd[545]: Exit.
Jun 4 19:38:34 localhost mach_kernel: WS DSL: !Session
Jun 4 19:38:52 localhost last message repeated 9 times

[mervTormel]

pre 10.2, there were files that held type/creator associations.


$ ll -G ~/Library/Preferences/{LS*,.LS*}
-rw------- 1 merv 2.3M Aug 12 13:39 .LSApplications_Backup
-rw------- 1 merv 1.0M Aug 12 13:39 .LSClaimedTypes_Backup
-rw------- 1 merv 29k Aug 12 13:39 .LSSchemes_Backup
-rw------- 1 merv 2.3M Aug 12 14:51 LSApplications
-rw------- 1 merv 1.0M Aug 12 14:51 LSClaimedTypes
-rw------- 1 merv 29k Aug 12 14:51 LSSchemes

try deleting those files

[rooneytunes]

Sorry, no change

[rooneytunes]

Ran fsck, still no luck.

[anthlover]

Your still in 10.1x over 10.2 but...

I have noticed the following about Classic in General.

Your better off launching it yourself and you get much more reliable launching behavior from classic applications once Classic is launched.

I have also noticed that ***** restarting the classic environment periodically helps. There are times when clicking on doc for app does little or at best launches the app but not the doc. You may also need to restart the Finder too. Do you get better behavior after a fresh X restart first classic run?


Lastly, I have noticed that Classic is much more solid in 10.2x at the moment 10.26 then 10.1x.

[dimon]

Originally posted by rooneytunes
As follows, option/command dragging the file over PS icon starts up classic and PS, as soon as PS open...

As I understood, PS is Photoshop, not PostScript, right? Keep in mind that PS extension is for PostScript printer files by default.

...something else attempts to load in the dock, it's VERY quick and looks like a printer icon,...

What is preferred app for that files in "Get info"? May be you accidentally changed that in some way?


...With PS already open the same procedure gets me a request to locate an additional plugins folder, then asks me to allocate a scratch disc, the PS opens and again, no file....

Seems like Photoshop treats your's files of that kind like a PostScript files AND definitively IS BAD INSTALLED or configured (sounds like it can't found PS parser). what version do you use?
It runs natively or thru Classic?
Can you open that files from "Open" dialog? What Photoshop says about their type? Can you open them by forcing "PSD"(or whatsoever) type in "Open" dialog?

Dimon

[rooneytunes]

'File open with' has always been assigned to PShop, hasn't been accidentally changed.
I keep an OS9.2 folder on a FW drive and when I start up from that PS and ILL both behave normally, double-clicking a PSD file opens PS and the file as expected.
It makes no difference if I start classic at start up or launch classic when double-clicking a PSD I just get the app and have to do a tedious trawl down through GBs of files to locate my file and then tell PS to open it. That works fine but is a real working disadvantage.
BTW I found my old posts on this subject and a bloke reported that he solved this by switching his time zone to UK. I vaguely remember trying that but someone else gave me a terminal command about changing 'flags' but I can't remember now. I do remember the problem being 'fixed' but cant remember what actually did it. I do know that changing my time zone to UK didn't do it for me this time.
Getting frazzled now and resigned to going back to 9.2, don't have the dosh to upgrade all my classic DTP stuff.

[dimon]

Originally posted by rooneytunes
'File open with' has always been assigned to PShop, hasn't been accidentally changed.

You mean info from 9 or X?


I keep an OS9.2 folder on a FW drive and when I start up from that PS and ILL both behave normally, double-clicking a PSD file opens PS and the file as expected.

How many fonts are open? If more than 128, thats not good, if more than ~350-450 that'll drive Adobe products krazy - Illustrator&photoshop losts tools, can't open files, can't read/save prefs, etc.

It makes no difference if I start classic at start up or launch classic when double-clicking a PSD...

What PS version? Why you are starting PS under Classic from OS X?

I just get the app and have to do a tedious trawl down through GBs of files to locate my file and then tell PS to open it. That works fine but is a real working disadvantage.


You can drag&drop from Finder to PS "Open" window


BTW I found my old posts on this subject and a bloke reported that he solved this by switching his time zone to UK.

Seems like result of filesystem corruption/repairing, or...
I once had strange problems when time on my system wasn't in sync with time on server, where files was stored.

In general: startup from CD, check filesystem (sad but true: disk first aid can't recognize some types of drive errors), rebuild desktop, check (in X "get info") that "Open in the Classic ..." checkbox is cleared, get X "Get info" for one of target files and check that "Open with" looks like "Adobe Photoshop 7 (by default)"
Get rid of all that acdsee, etc., check that none of them added some extensions to PS.
It have to work.

Good luck.
Dimon