Illustrator 8 wierdness in Classic mode

[Joe_Shoulak@adobeforums.com]

Hello,
When it comes to new technology, we're a slower-moving company in some respects, but especially in our move to upgrade the Macs throughout the office.
We're still using Illustrator 8 but intend to make the shift over to using CS in Panther within the next month or so. Our first step was for me to receive a G5 with CS and Illustrator 8 installed. I would work with the only G5 in the office and test it out.
I've experienced some wierdness with Illustrator 8 in Classic mode on the G5 and I'm wondering if someone knows what's going on. Here's what happens: I create an Illustrator 8 file and work on it for a few minutes. Then, when I choose "save", I get a "Disk I/O error" message or a "cannot save file, it is busy or in use" message. This happens when I try to save to a server or just to my desktop.
My workaround has been to save new versions, such as file1, file2 etc.
I haven't yet re-installed Illustrator 8 but I probably will at some point.
I know that the best solution is to just dump 8 and move on to CS - and we intend to do that eventually - but until then we have to all work with the same version.
Thanks for any input,
Joe

[Dee Holmes]

This happens to us occationally, although we still use OS9.2.2 and AI10.03. Do you also have Quark 4.11 open with the file in place? We have had some luck closing Quark and then trashing Quark Preferences on some machines.

Or on one machine we had this problem and putting the file into another work folder on the hard drive instead of on the desktop worked. This was one of the OS9 machines that had the desktop hidden when another Mac was trying to file share.

The same sort of situation could be happening in Classic Mode?

Worth testing out for now, I think.

Also, it's not recommended to work straight from the server. Copy the files needed to your hard drive, save them on your hard drive, and then copy them back if you use it for your backup also.

[Joe_Shoulak@adobeforums.com]

Hi Dee,
Thanks very much for your suggestions.
No Quark isn't open when this happens. But I'll try trashing Quark prefs.
Also, I don't work from the server, I copy items to my hard drive.
I work on Illustrator 8 in Classic mode.
I find this bizarre... it doesn't happen in those rare instances that I use Illustrator 8 in Classic mode on my G4 with Panther in my home office.
Any other insights?
Thanks again.

[Scott_Weichert@adobeforums.com]

Just a personal observation here, no substance or cold hard facts to back it up.

I find classic on a G5 is much less stable than classic on a G4. My assumption is that Apple isn't concerned about classic on a G5 too much, hoping to kill classic off entirely.

[Br0wn_Recloose@adobeforums.com]

make sure to keep your ill 8 around just in case. in my experience ver.8 is more reliable than any of the following versions when it comes to printing. so far every time i've gotten printing errors in ver.10 and CS, i've been able to print the same document from ver.8 successfully. currently i'm using CS in osx and 8 in classic mode, on a G5.

-j

[Mike_Schwabauer@adobeforums.com]

Joe, I'm having the same problems with errors when doing a Save of an Illustrator 8 file in Classic in Panther. I've tested on six computers so far (three G5s, two G4s and one G4iMac), and so far the iMac is the only one that does NOT have this problem.

On all the other, you can do a Save As just fine, as long as you're creating a new file. But from then on out, if you make a change to the file and do a Save, you'll get the error...and then an AI Temp file in the location of your file. You get the same behavior if you do a Save As and try to REPLACE the existing file.

I've not yet been able to determine a fix or why the one computer works, but this is very troublesome (though comforting to know I'm not alone). Basically it feels like Illustrator 8 is having a hard time doing whatever it needs to in the background to "remove" the old version of a file and "replace" it with the changed version when doing a Save.

I'm hoping there might be some kind of permissions fix that takes care of it, but somehow I'm not optimistic.

I'll keep you posted if I find anything out, and I hope you'll do the same.

:) Mike