or Connect
AppleInsider › Forums › Software › Mac OS X › List of 'old' apps that do / don't work under Classic
New Posts  All Forums:Forum Nav:

List of 'old' apps that do / don't work under Classic

post #1 of 31
Thread Starter 
Here they are based on my 'heavy' testing.


After Effects 5 - Works.....Remember DON'T allocate more than 438MB RAM to it! Otherwise it won't launch! :eek:

ImageReady 3 - Only with some minor brush glitch...otherwise okay

WORD 98, 2001 - Works except it takes a while to open the Open Dialogue box <img src="graemlins/hmmm.gif" border="0" alt="[Hmmm]" />

Fontographer 4.15 - Works perfectly!

Dreamweaver 4 - Works but menus are slower than under OS 9

Director 8.5 - Just remember NOT to open / work with big files

Photoshop 5.5/6 - NIGHTMERE!!!!! Don't even think about it

SoundEdit 16 - Works fine but with the sound input disabled. Also takes a lot longer to start a new file

Media Cleaner 5 - Works. Just don't allocate more than 380MB RAM to it. But I started not using it since the first day I had Sorenson Video Developer

Flash 5 - Don't know why I can't even launch it :confused:

Debablizer 1.6 - Works without problem

Painter 3D - Works without problem. Reason I still use it because the OSX native BodyPaint doesn't support stylus pressure yet

QuarkXpress 4.1 - Works without problem


So far....that's it. Once Photoshop and Final Cut Pro go native (After Effects too, maybe) I will switch to OSX full-time and leave other apps running under Classic.

[ 11-19-2001: Message edited by: Leonis ]</p>
Mac Pro 2.66, 5GB RAM, 250+120 HD, 23" Cinema Display
MacBook 1.83GHz, 2GB RAM
Reply
Mac Pro 2.66, 5GB RAM, 250+120 HD, 23" Cinema Display
MacBook 1.83GHz, 2GB RAM
Reply
post #2 of 31
What's your problem with Photoshop 6? I use it frequently in Classic with no trouble at all.

The only issue worth noting is that you shouldn't switch apps while Photoshop is loading because it has to be in the foreground to load the menubar.

It's hardly a nightmare for me. :confused:

[edit] since this is a list of apps that do and don't work, it's important to note that Apple's Final Cut Pro does not work in Classic.

[ 11-20-2001: Message edited by: starfleetX ]</p>
post #3 of 31
Thread Starter 
Final Cut Pro won't run under Classic is given. So I don't think it's necessary to list it

Anyway....I do have some very annoying problems with Photoshop 6:

1)Can't allocate more than 438MB RAM to it. This is a BIG problem. Because I work on LARGE files all the time

2) Menu bar thing. I know I should not touch or do anything when PS is launching. Otherwise I will 'miss' the menu bar

3) Option-click outside the working window will cause the entire Classic environment quit

4) Brush painting is slower, a lot slower. Also is a pain to me because I paint in Photoshop a lot

5) I have to set the History level to 5 MAX. Otherwise........the app will just freeze


...as a very heavy Photoshop user these bugs/problems are intolerable. In order for me to use OSX full time I have to wait for PS 6.5 or 7.

Also Final Cut Pro......

[ 11-20-2001: Message edited by: Leonis ]</p>
Mac Pro 2.66, 5GB RAM, 250+120 HD, 23" Cinema Display
MacBook 1.83GHz, 2GB RAM
Reply
Mac Pro 2.66, 5GB RAM, 250+120 HD, 23" Cinema Display
MacBook 1.83GHz, 2GB RAM
Reply
post #4 of 31
I have 2 (different) problems in Photoshop 5.5 in Classic.
When dragging stuff round (layers, selections,etc) when I have got it to the right place and let go of the mouse button it sometimes 'jumps' a few pixels. Great, graphic design is all about acuracy.

2 when you have somthing on the clipboard and you make new document (so it's the same size as the clipboard item) it takes ages to open the new window (after you have clicked OK in the 'new' dialouge box.

These 2 problems are what has put me off finishing my theme.
It took me ages to find this post without my image sig
Reply
It took me ages to find this post without my image sig
Reply
post #5 of 31
[quote]1)Can't allocate more than 438MB RAM to it. This is a BIG problem. Because I work on LARGE files all the time <hr></blockquote>

I think Mac OS X ignores those memory allocations and handles the memory using its own dynamic memory management. What happens if you change the memory allocation back to its suggested size?

[quote]3) Option-click outside the working window will cause the entire Classic environment quit

5) I have to set the History level to 5 MAX. Otherwise........the app will just freeze <hr></blockquote>

I'm unable to duplicate these problems... have you tried watering down Classic's extension set, trashing Photoshop's prefs?
post #6 of 31
Thread Starter 
Classic Applications still require manual memory adjustment by the user.
Mac Pro 2.66, 5GB RAM, 250+120 HD, 23" Cinema Display
MacBook 1.83GHz, 2GB RAM
Reply
Mac Pro 2.66, 5GB RAM, 250+120 HD, 23" Cinema Display
MacBook 1.83GHz, 2GB RAM
Reply
post #7 of 31
Thread Starter 
Here you go



This is after allocating 350MB RAM to After Effects 5, 30MB to WORD 2001, 30MB RAM to Dreamweaver 4. takes about 30.4% of total of 1.5GB of RAM.

Even I don't open any file or do anything the memory usuage will always stay at this level. But all those native apps don't suffer this problem.....
This really shows how sucky the memory manager of the Classic OS


Maybe I will get another 512MB modules for the 4th RAM slot (bump to 2GB!) of my Gigabit DP G4 so I will not need to care about how much memory the Classic environment sucks up

[ 11-20-2001: Message edited by: Leonis ]</p>
Mac Pro 2.66, 5GB RAM, 250+120 HD, 23" Cinema Display
MacBook 1.83GHz, 2GB RAM
Reply
Mac Pro 2.66, 5GB RAM, 250+120 HD, 23" Cinema Display
MacBook 1.83GHz, 2GB RAM
Reply
post #8 of 31
[quote]This is after allocating 350MB RAM to After Effects 5, 30MB to WORD 2001, 30MB RAM to Dreamweaver 4. takes about 30.4% of total of 1.5GB of RAM.

Even I don't open any file or do anything the memory usuage will always stay at this level. But all those native apps don't suffer this problem.....
This really shows how sucky the memory manager of the Classic OS<hr></blockquote>

I still don't think that the memory you allocate a Classic app affects performance while running under Classic, since X's memory management manages all processes - including classic processes.

Also, the CPU/memory consumption you see in the Process Viewer I think is pointless, as resources are divied out in context with what is going on, and depending on the nice level set. When more stuff is going on, those same apps will take less memory and less cpu.

I've never tried to see what will happen when you set a classic app to a ridicously high memory allocation (as far as if it presents any particular problems), but I'm pretty sure there is no point in managing resources in this fashion.

Classic is allocated 1 gig of RAM, and will use what it can as it sees fit.
post #9 of 31
Photoshop 5.5/6 sure work great for me, like a dream (not a nightmare); I don't have any of the problems you guys do. <img src="graemlins/bugeye.gif" border="0" alt="[Skeptical]" />
art may imitate life, but life imitates tv.
Reply
art may imitate life, but life imitates tv.
Reply
post #10 of 31
Photoshop 6 works fine in Classic on my iBook... I dont know why other would have problems with it. Premiere is sometimes a little weird though, it doent recongize the firewire ports like 50% of the time...
post #11 of 31
Thread Starter 
[edit] don't want to do that argument anymore, getting tired

[ 11-21-2001: Message edited by: Leonis ]</p>
Mac Pro 2.66, 5GB RAM, 250+120 HD, 23" Cinema Display
MacBook 1.83GHz, 2GB RAM
Reply
Mac Pro 2.66, 5GB RAM, 250+120 HD, 23" Cinema Display
MacBook 1.83GHz, 2GB RAM
Reply
post #12 of 31
Claris Emailer is still chuggin' away. Everything works perfectly; except, when you're done unpacking your new messages the alert sound gets cut off. Other than that, you'll have to pry Emailer from my cold, dead hands.
post #13 of 31
For us scientific types, SPSS does not run in classic, at all. Too bad for it because I could use OS X protected memory from having to restart the computer every time I try cut/copy/paste large chunks of data. Such a piece of shit program should not be allowed to run unless it's under OS X so that i don't have to restart my computer all the damn time...
post #14 of 31
[quote]Originally posted by Leonis:
<strong>Lots of people do have the same Photoshop problem as I have.

Even in Apple's own support site!

Can we just back to topic and list the programs that you can use under Classic??????????????????????????</strong><hr></blockquote>

Settle down already; don't take it out on us because U.E. has caused your copy of Photoshop not to work.

And just because lots of people are having the same problem, whether they mistakenly talk about it on Apple's boards (about an Adobe product) or not, does not mean it isn't U.E., though the fact that to date you are the only person to complain of these specific problems does lend to the conclusion it is.

And if you don't know what U.E. stands for, guess.

[ 11-21-2001: Message edited by: bradbower ]</p>
art may imitate life, but life imitates tv.
Reply
art may imitate life, but life imitates tv.
Reply
post #15 of 31
Lemme think, what works in Classic?

Photoshop, Flash, NS 4.x (I only use it for testing), ShrinkWrap, umm, I don't have much else that I even use, I guess.
art may imitate life, but life imitates tv.
Reply
art may imitate life, but life imitates tv.
Reply
post #16 of 31
Thread Starter 
UE - user error

I belive many problem are caused by the end users. But in some case it's not the user. It's the bug that's with the OS. Anyway. if you dont' believe that many people do have the problem. fine. You don't have the problem doens't mean other's also don't.

I better stop now. I am tired

[ 11-21-2001: Message edited by: Leonis ]</p>
Mac Pro 2.66, 5GB RAM, 250+120 HD, 23" Cinema Display
MacBook 1.83GHz, 2GB RAM
Reply
Mac Pro 2.66, 5GB RAM, 250+120 HD, 23" Cinema Display
MacBook 1.83GHz, 2GB RAM
Reply
post #17 of 31
I never said that I didn't believe you or others weren't having the problem--I have no cause to believe that, do I? I said that due to the fact it's not widespread and you are the only person I have heard of having these problems, that I think this may be an isolated, user-contributed problem. Perhaps preferences, applications, frameworks, extensions, fonts, files, or permissions are screwed--you've got a ton of variables when you're talking about running basically two separate environments and a huge application/suite like Adobe Photoshop. It's just not very likely that it is a problem due to Classic, or even more remotely, OS X. If I were you I would try troubleshooting a little deeper and solving this, instead of repeatedly whining about it when you hear people say "whaaaat, it works for me!"
art may imitate life, but life imitates tv.
Reply
art may imitate life, but life imitates tv.
Reply
post #18 of 31
Thread Starter 
[quote]Originally posted by besson3c:
<strong>

I still don't think that the memory you allocate a Classic app affects performance while running under Classic, since X's memory management manages all processes - including classic processes.
</strong><hr></blockquote>

I agree with you at some point.... however the case really is somewhat different and complicated with those memory hog like AE and PS. The problem with these apps is that they only see the amount of memory allocated to them even under OS X's Classic. If I allocate 200MB to either After Effects and Photoshop they will only see 200MB. To find out the RAM they see....on AfterEffects...go to apple icon and choose "About Adobe After Effects". For Photoshop. Open a file or start a new one. Click the triangle at the bottom left hand corner and pick "Scratch Size".


BTW. If you guys have a lot of RAM and have both apps why not try to test to see if you can get over 438000KB to PS and 456800KB to AE? I asked many people who too used these apps a lot to try and they all couldn't pass these amounts.

I will send you all my smilies if you can get over these numbers

[ 11-21-2001: Message edited by: Leonis ]</p>
Mac Pro 2.66, 5GB RAM, 250+120 HD, 23" Cinema Display
MacBook 1.83GHz, 2GB RAM
Reply
Mac Pro 2.66, 5GB RAM, 250+120 HD, 23" Cinema Display
MacBook 1.83GHz, 2GB RAM
Reply
post #19 of 31
[quote]I agree with you at some point.... however the case really is somewhat different and complicated with those memory hog like AE and PS. The problem with these apps is that they only see the amount of memory allocated to them even under OS X's Classic. If I allocate 200MB to either After Effects and Photoshop they will only see 200MB. To find out the RAM they see....on AfterEffects...go to apple icon and choose "About Adobe After Effects". For Photoshop. Open a file or start a new one. Click the triangle at the bottom left hand corner and pick "Scratch Size".<hr></blockquote>

Leonis,

you don't seem to be listening to me... I'm pretty sure (but will gladly be proven wrong) that those memory allocations are IGNORED. It doesn't matter what the program says, it's running in Classic mode under OS X's memory management.
post #20 of 31
Thread Starter 
Why don't you try it yourself?

Allocate 200MB RAM to Photoshop. Open a 100MB file. Under normal condition a file like this big requires about 400MB of real RAM in order to avoid the crazy data swapping between RAM and Hard drive. Photshop under Classic really only sees 200MB is available if the manual memory allocation is 200MB and it will swap all those extra data to the hard drive.

This is not just me. Other people who use Photoshop as crazy as I am also see the same thing with their systems.

Classic apps is classic app. It won't be any different even under X. The TrueBlue environement does have the dynamic memroy allocation at some point. But the Classic apps don't. Remember what Steve Jobs and Avie said back to WWDC 1998? Classic apps, not the environment, won't have the advantage of dynamic memory allocation.

This is going to be the last time I say this and I won't say anymore.
Mac Pro 2.66, 5GB RAM, 250+120 HD, 23" Cinema Display
MacBook 1.83GHz, 2GB RAM
Reply
Mac Pro 2.66, 5GB RAM, 250+120 HD, 23" Cinema Display
MacBook 1.83GHz, 2GB RAM
Reply
post #21 of 31
[quote]Why don't you try it yourself?
Allocate 200MB RAM to Photoshop. Open a 100MB file. Under normal condition a file like this big requires about 400MB of real RAM in order to avoid the crazy data swapping between RAM and Hard drive. Photshop under Classic really only sees 200MB is available if the manual memory allocation is 200MB and it will swap all those extra data to the hard drive.<hr></blockquote>

Photoshop under Classic will think it has 1 gig of RAM to play with... are you able to generate an out-of-memory error?

[quote]Classic apps is classic app. It won't be any different even under X. The TrueBlue environement does have the dynamic memroy allocation at some point. But the Classic apps don't. Remember what Steve Jobs and Avie said back to WWDC 1998? Classic apps, not the environment, won't have the advantage of dynamic memory allocation.<hr></blockquote>

Then why can we control Classic processes through Mac OS X? If the True Blue Environment was controlling these processes, we'd have to call on it specifically to do something to a classic process (for instance a force quit), right? Moreover, it would be possible to generate an "out of memory" error....
post #22 of 31
Thread Starter 
Hey besson3c ..... check out my private message
Mac Pro 2.66, 5GB RAM, 250+120 HD, 23" Cinema Display
MacBook 1.83GHz, 2GB RAM
Reply
Mac Pro 2.66, 5GB RAM, 250+120 HD, 23" Cinema Display
MacBook 1.83GHz, 2GB RAM
Reply
post #23 of 31
I just tested, and besson3c is right. I can't get Classic apps to listen to what I put in the memory values.
art may imitate life, but life imitates tv.
Reply
art may imitate life, but life imitates tv.
Reply
post #24 of 31
Leonis is correct about the memory allocation. I concur wholehartedly without a doubt that that is the way it works.
[quote]Originally posted by bradbower:
<strong>I just tested, and besson3c is right. I can't get Classic apps to listen to what I put in the memory values.</strong><hr></blockquote>Hmm... that can not be correct. I just allocated 500KB to Photoshop 6.0 and got an out of memory error when I tried to open one document. Obviously Classic apps do use the allocations.
post #25 of 31
[quote]Originally posted by Leonis:
<strong>3) Option-click outside the working window will cause the entire Classic environment quit</strong><hr></blockquote>Odd. I'm option-clicking between apps like crazy right now and nothing has crashed yet. Double-check your extension set for extraneous stuff.
[quote]<strong>4) Brush painting is slower, a lot slower. Also is a pain to me because I paint in Photoshop a lot </strong><hr></blockquote>It's just as fast for me in X as in 9 on my DP500G4. What kind of mac are you using? Again, check the extension set.
post #26 of 31
Thread Starter 
[quote]Originally posted by starfleetX:
<strong>It's just as fast for me in X as in 9 on my DP500G4. What kind of mac are you using? Again, check the extension set.</strong><hr></blockquote>

Same machine but with 1.75GB RAM installed.

About option-clicking. That Classic "crash" only happen when I am in Photoshop and option click to the desktop or other apps. I do this as crazy as you with other apps (even After Effects under Classic) and have no problems...

[ 11-22-2001: Message edited by: Leonis ]</p>
Mac Pro 2.66, 5GB RAM, 250+120 HD, 23" Cinema Display
MacBook 1.83GHz, 2GB RAM
Reply
Mac Pro 2.66, 5GB RAM, 250+120 HD, 23" Cinema Display
MacBook 1.83GHz, 2GB RAM
Reply
post #27 of 31
:confused: Gosh, Leonis, I wish we could figure out what the problem here is. I am really having zero trouble option-clicking to the desktop or anything else from Photoshop 6; it works just as expected. I don't have After Effects; so, I can't test that. All I can realy think of is to reiterate what I said before about the extension set and hopefully you'll find some cdev's or init's to disable.

But anyway, back to the main subject of the thread... Guess what I just discovered. I found the old Final Cut Pro 1.0 installer and FCP 1.0 works in Classic! Yeah, it's a bit out of date and it can't communicate with my camera in Classic, but at least now I can do some editing without rebooting.
post #28 of 31
logic audio (the audio) doesn't work. MIDI is fine.

Since d/loading the new OS X SparkME, SparkXL doesn't work now in 9.

Reason can't find the soundmanager outputs in X, doesn't work.

In a nutshell, most of my audio apps
post #29 of 31
Thread Starter 
Starflex....you can use Final Cut Pro 1.2 under Classic? Wow...that's cool.

OSX for now is a curse to the pro audio people unfortunately
Mac Pro 2.66, 5GB RAM, 250+120 HD, 23" Cinema Display
MacBook 1.83GHz, 2GB RAM
Reply
Mac Pro 2.66, 5GB RAM, 250+120 HD, 23" Cinema Display
MacBook 1.83GHz, 2GB RAM
Reply
post #30 of 31
Indeed!! Those audio apps (or lack of them) keep me from swicthing to OS X full time.

Ah well, at least logic Audio will be out january 7th! And Deck will be released this year. Can't wait!!!!
post #31 of 31
double post

[ 11-24-2001: Message edited by: macanoid ]</p>
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Mac OS X
AppleInsider › Forums › Software › Mac OS X › List of 'old' apps that do / don't work under Classic