Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

InDesign Problems

We are running into many problems with Indesign CS 3.0.1.

Our G4 eMacs are running 10.2.8 with 512MB RAM. We are also running Centurion's Drive Shield on all the Macs.

All users are authenticated to an Active Directory server via LDAP. The user logging on is given admin rights to the local computer. We have a login script that adjusts the ownership and privileges on a default home directory on the local computer so the user has access to a local home directory.

Here is a typical example:

1) User creates new Indesign doc. Saves it to a network volume. (A windows 2K server running afp)
2) User adds pics, text, etc.
3) User prints - Indesign unrepentantly quits
4) Document is corrupted and user has to start over.

I have also run into different variations on this theme. Sometimes the user never prints but the doc is still corrupted and they crash as soon as they try to save. There have been a couple other users (though I have never seen this myself) who insist that they opened an existing document, made changes, saved and quit just fine. When they open the doc again the changes they made are gone, though the document opens just fine.

These problems are very intermittent (I would say they occur with about 10% of the users) but they are very annoying.

Some thoughts I've had:

1) Since we are running Drive Shield all users need to save their work on the server. It would be easy to blame this on the network, however since we have very few (if any) saving their work to the local hard drive this is difficult to prove. I have thought about having students work on their documents locally and then copy them to the network, but this would require a significant amount of end user training.

2) I was able to duplicate the problem running version 3.0. I created a new document and every time I tried to print it Indesign would crash. After upgrading to 3.0.1 the very same document would print fine. I thought the problem was fixed - but apparently not.

3) Could driveshield itself be the culprit? Would it be worth my time to temporarily disable Drive Shield in the lab and see if that makes a difference?

4) I've read that 10.2.8 is a bit buggy. Is there a newer version in the 10.2.x family that I should upgrade to?

Any input would be greatly appreciated!




Dan Gomoll
Academic Computing
Alverno College
_______________________________________________
maclabmanager mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/maclabmanager
Do not post admin requests to the list. They will be ignored.



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.