Problems shutting down illustrator cs3

greetings -
just curious if anyone else has had issues w/ illustrator not shutting down (i.e., file/exit). i have yet to attempt an uninstall/reinstall since it took a long time to install cs3 on my machine the first time (had to restart it once).
about 9 out of 10 times when exiting illustrator, it will freeze up, and i have to do a "ctl+alt+delete"" to terminate the process.
any thoughts are appreciated.
- c

I've been having this daily problem of this 'hanging-on-quitting' problem, too, until I saw this first post (recently, always searching for solution thru other forums as well) and thought that what might be the problem..., often times I would just quit by clicking the Close button, too. For a while, it did work (if I'm using Illy for short period of time) it doesn't hang - but if I would keep it up & work with it for a long period of time, then on quit (even with the File>Exit method) it'll go blank & 'hang' (again). I'm "wild-guessing", but could it be something to do with application's cache/memory issue? I mean, its seems like the more I use it, the more it keeps "building-up inside" so to speak. Also I agree whole-heartedly with JET's post #29 (under "New to Illustrator - all I want to do is draw a triangle") concering the "inelegance" of Illustrator, etc. He really said it well. It seems that each Illy's "improvement" is two-steps-backward at the same time. Very frustrating! I have Windows XP SP2 on two different machines. I hope this post would help to bring out any other thoughts or ideas on this annoying issue.
David Cripe

Similar Messages

Problems shutting down laptop

Good morning!!
I have a Toshiba Satellite P75-A7200 and sometimes I have problems shutting down it. I have seen in some forums that it can be because I have open apps. After checking it out I see that all of them are closed and I cannot close the laptop yet... Do you have any idea why it can happen and how to solve it?
Thanks!!!!!

Satellite P75-A7200
Have you upgraded to Windows 8.1? If so, did you follow these instructions?
How to Update from Windows 8 to Windows 8.1
What happens when you disable fast startup?
Control Panel > Power Options > Choose what the power button does > Change settings that are currently unavailable (near the top)
Under Shutdown settings at the bottom, clear the check box for Turn on fast startup (recommended), and click the Save changes button.
-Jerry

Problems shutting down after installing 10.5.3 update?

Has anyone had any problems shutting down there IMac's after installing 10.5.3 update? I've tried shutting down twice and the image that appears when shutting down seems to go in an endless loop an doesn't shut down.

Can you restart from the menu and hold the shift key down, until the Mac
boots in a SafeBoot login screen; then choose Disk Utility (shortcut under
GO in Finder window, to Utilities folder) and run 'repair disk permissions'
then restart the computer normally...(?)
You may also have to consider starting the computer from the OS X
installer disc and choose from an option menu there (not to install)
and choose to use Disk Utility from the booted installer disc, to run
'repair disk' from there? You could also run 'repair disk permissions'
while booted from that installer disc, but maybe you'd still have to
repair those from the running system for best effect once it is back
running from the hard drive's system.
Some minor issues can happen after an update, usually just repairing
disk permissions before installing the update, and/or running up in
SafeBoot, can help. There are other things to try and do, if these don't
help that much. The state of the system prior to an update is important;
since an update can't fix anything otherwise non-related to an update.
Maintenance issues aside, after you repair disk permissions, safeboot,
and restart, if there still is an issue, you could try to download the Combo
OSX 10.5.3 update file and install it over your system; and then repair
disk permissions again after it finally restarts normally.
Was the 10.5.3 update a smaller (delta) file or was it the Combo (large) file?
Good luck & happy computing!

I am having problems shutting down my MacBook Pro. I go to the apple and click shutdown or restart, it appears the shutdown process starts, the screen goes blue and the little circle keeps going round and round, but nothing happens even after 30 minutes.

I am having problems shutting down my MacBook Pro. I go to the apple and click shutdown or restart, it appears the shutdown process starts, the screen goes blue and the little circle keeps going round and round, but nothing happens even after 30 minutes.

Make sure you quit all your applications before shutting down.
And try resetting the SMC.
Intel-based Macs: Resetting the System Management Controller (SMC)

On start up, says had problem shutting down mac book pro mavericks

on start up, said had problem shutting down, mac book pro mavericks 10.9.4
recently loaded dragon dictate

Welcome to Apple Discussions!
I am wondering if your hard drive is failing? You might try downloading and running SMART Utility on it:
http://www.apple.com/downloads/macosx/systemdiskutilities/smartutility.html
You can download the demo and run it several times for free. It is somewhat more critical than Disk Utility, and may give you earlier warning of impending drive failure.
You might also want to run the extended version of the Apple Hardware test and see if you get any error codes.
From the way your hard drive is behaving, it sounds to me like there is something wrong with it. Since reinstalling the OS doesn't solve anything, you are likely dealing with some sort of a hardware issue.
Good luck!

When I put my macair to sleep overnight and want to put it back on in the morning, it says that it had a problem shutting down and all my work is lost. Is that normal?

In the evening when I put my mac air to sleep and turn it on in the morning it says it had a problem shutting down and had to restart again, so all my work is gone, and this is happening quite often now and I bought it in January. So shouldn't I use the sleep mode over night is that too long and causes it to crash? Or should I take it to a apple store for them to check it out?

Overnight isn't too long for sleep mode. I do it all of the time with no problem. However, I save everything first so I would not have the "all my work is gone" issue even if there was a problem. I would have it checked out.

Black screen on starting up in OSX, problems shutting down in XP.

Hi there.
I have a 2-month old iMac with Bootcamp and Win XP installed. It ran OK for a while, but Bootcamp has started behaving erratically. I did postst this in the Bootcamp part of discussions, but have come to the decision that it is not a Bootcamp issue.
If I restart holding down the 'alt' key to bring up the Mac HDD or Bootcamp startup choice, when the screen comes up, it really chugs. The mouse moves once every second, and I cant actually choose the Bootcamp drive. I click on it, double click, etc, and nothing happens. I hit the power button to reset, and it eventually (after literally a few minutes) starts up in XP.
Once XP has started, it runs OK, perfectly fluid. But when I have finished, I try to re-start into OSX. I choose 'Shut down, and nothing happens. I choose 'shut down' a second time, and it turns off almost instantly, but when I restart the mac, I get the startup chime but nothing on screen at all – totally blank.
I tried restarting loads of times, but nothing worked. Eventually I unplugged it for a couple of minutes, started off my system disk, reselected the iMac HDD as the startup disk, and it restarted in OSX fine.
This whole episode really scared me, so I really want to stop it from happening again.
I have some ideas of what might have caused it, but need someone with a better brain than mine to troubleshoot my logic. Here are my thoughts.
1) Bootcamp in itself just facilitates the installation of windows and auto-installation of hardware drivers, etc. Once Windows is installed and working, Bootcamp has really finished it's job.
2) the 'holding Alt at startup' thing is an OSX thing (not Bootcamp specific). I reckon 1 & 2 together logically rule out Bootcamp the app as the problem.
3) The actual OSs and apps in either partition actually work fine once the rigmarole of changing from one to the other is done. So the problem isn't in apps or high-up in the OS.
4) Is it therefore a start-up/shutdown issue, present when either entering or exiting both partitions? As it's both partitions, could it be OS-independent as well?
This leaves hardware. Could corrupt P-Ram settings cause this (if it's still called P-Ram – I originally started using macs back in the days of MacOS 8.6). I'm guessing that the unplugging might have cleared the PMU, as sticking a reset button on the M/B inside an iMac would be pretty bad design.
Any thoughts?

It was the PRAM.

Problems shutting down and starting up

my MacBook Pro (OSX 10.9.3) doesn't shut down when I want it to but goes into a coma periodically.
when I use "Shut Down" every once in a while via Apple menu, the machine doesn't appear to actually shut down. when I open it or got to it the next time, it's in a state of sleep and I can't awaken. when I finally get it to shut down manually and restart, a dialogue saying "you shut down due to a problem" arises next startup. this whole chain is odd to me. I'm a long-time Mac user (IIvx, iMac and iBook) and I don't recall the startup problems but maybe I've just forgotten.
moreover, and related, sometimes when I simply shut the screen to put MacBook Pro to sleep, it won't reawaken. clicking space bar or pushing mouse pad have no effect. so then I have to manually shut down by holding power button, and then restart.
in the old days, we would "zap the PRAM" when there were freezing or startup problems. (I don't even remember how to do that, as my iBook which I had for ten years never gave me these problems). do I zap the PRAM? how? any other ideas?
Thank you!

brutus775,
if you boot into Safe mode, does your MacBook Pro still go into periodic comas?
With MacBook Pros, one “zaps the NVRAM” (or “resets the SMC”) instead.

Problems shutting down...

50% of the times i try to shut down, my computer quits all the open applications and then just gives me the spinning rainbow and does nothing. i eventually just manually turn it off with the button in the back. any advice on fixing this problem?
also when the computer starts up, the first image on the screen is of a folder with a question mark in it. is this a related problem? or a different fix?
thanks
brett

729/3175
"invalid leaf record count"
You are using the Tiger DVD, are you?
(- http://docs.info.apple.com/article.html?artnum=301266 )
Always use the Tiger disc to repair a Tiger volume, and the Panther disc to repair a Panther volume.
If you did so, then I don't know what kind of problem this is, and I'd run a more powerful tool like DiskWarrior, since anything like that should not be left unrepaired IMO.
How do your shutdown times go now?
If not better, try removing all Login Items, see if it is related.
Personally my iMac takes a much longer time to shutdown, since it has Tiger installed, so I wouldn't be surprised, unless of course the machine just NEVER shuts down, even after six or seven minutes...
At the contrary the boot time is much shorter than in Panther.

Thread problems - shutting down.

Okay, I've got my multi-threaded server program working just fine and all is well...until I shut down the server.
By some quirky twist of fate, java chat servers seem to be a popular education assignment in the last two weeks, which will probably put some people off answering this simply because of all the clueless posts on the subject recently. :)
Anyway, a little background on how I'm doing things first.
At the top there is the Server object, which is implementing Runnable. This instances the ClientManager, creates the ServerSocket and then kicks off its own thread and loops in the run() method waiting for connections while a boolean is true. If it gets a connection it calls the ClientManager addConnection() method and passes it the received client socket.
The ClientManager holds a List of ClientConnections and provides methods to add and remove ClientConnections. The ClientManager also runs in its own thread by implementing the Runnable interface and uses its run() method to loop through checking for incoming messages from each client.
A ClientConnection object also runs in its own thread via the Runnable interface. This checks for incoming messages from the client and stores the String ready to be received by the ClientManager and broadcast to all ClientConnections.
So, you've got the Server running in its own thread, the ClientManager running in its own thread and the ClientManager maintaining a List of ClientConnections, each running in its own thread.
I'm starting my threads like this:-
// Constructor.
Public SomeObject() {
    start();
// Runnable method.
Public void start() {
    // threadObject is private class variable.
    bThreadActive = true;
    this.threadObject = new Thread(this);
    threadObject.setDaemon(true);
    threadObject.start();
}I'm running my threadded object like this: -
Public void run() {
    do {
        // Do work here.
    } while(bThreadActive);
    // Activates the shutdown method for this object.
    shutdownObject();
}I'm shutting down my threads like this: -
Public void shutdown() {
    this.bThreadActive = false;
// The main shutdown code.
Public void shutdownObject() {
    // Kill thread object.
    this.threadObject = null;
    // Do other stuff.
}Which I think should work fine. Anything wrong with the above?
I'm getting problems with NullPointerExceptions with the Server object at the point where it tries to shutdown the ClientManager. This works by shutting down all ClientConnections in the List first and then emptying the List before killing its own thread. Also, the Server object seems to shutdown before the ClientManager. And other such weirdness.
I know you're all going to ask for specific code and a stacktrace, which I'll provide....I just want to check that my method for using threads as above is correct first, so I can rule that out - mostly because I suspect I'm missing some vital piece of knowledge on using threads....things are not working as I expect.
Anyway, a quick answer on the above and then I'll start posting more specific info.
Thanks all :)

Ooops....my mistake. I was calling shutdown() twice. Once from the GUI code and automatically from after the loop in the run() method. Funny how the stacktrace doesn't drill down any further than the method that makes this call.
Okay, its almost all working perfectly, except for this part....
    // Start accepting client connections from the server service.
    public void run() {
         while(bThreadActive) {
             if (sockServer != null) {
                 if (!sockServer.isClosed()) {
                     try {
                         sockClient = sockServer.accept();
                         if (sockClient != null) {
                             this.clientManager.addClientConnection(sockClient);
                             this.pOutput.printOutput("Connection accepted from: " + sockClient.getInetAddress().getHostAddress());
                     } catch (IOException ioe) {
                         if (bThreadActive) {
                             this.pOutput.printOutput("ERROR: Could not accept incoming client connection");
                     } catch (NullPointerException npe) {
                         // Leave this for now.
         shutdown();
    // Shutdown the server service and disconnect all client connections.
    public void shutdown() {
        try {
            clientManager.stopThread();
            sockServer.close();
            threadServer = null;
        } catch (NullPointerException npe) {
            npe.printStackTrace();
        } catch (IOException ioe) {
            pOutput.printOutput("ERROR: Could not cleanly shutdown the server socket");
        pOutput.printOutput("Server service shut down successfully");
    // Stop the server thread (automatically shuts down).
    public synchronized void stopThread() {
        bThreadActive = false;
    }When I call the above like this from the GUI object...
    // Stop the server.
    private void stopServer() {
         try {
              server.stopThread();
              setGUIMode(MODE_DISCONNECTED);
         } catch (NullPointerException npe) {
              npe.printStackTrace();
    }...the string "Server service shut down successfully" from the completion of the shutdown() method never appears, so it looks as though its not executing.
But if I do this instead in the stopServer() method and remove the shutdown() call in the run() method, it works......but I get two (sometimes three) outputs of "Server service shut down successfully" which makes me think its being run twice somehow.....once before the ClientManager has been shutdown and once after or twice after.
Server service shut down successfully
Shutting down Client Manager...
All client connections disconnected
Client Manager successfully shutdown
Server service shut down successfully
Server service shut down successfully
Any ideas?

Problems shutting down a 6534

Hi,
I have searched the forums and couldn't find this sorry if its a rehash.
I reciently built a box with a 6534 and a celery 1.7.
Everything is fine it runs fine, doesn't heat up, actually very stable.
Except...
I can't shut it down.
It will shut down/hbrn8,suspend fine, but the power supply fan continues to spin and after a few seconds it will boot back up on its own. I can shut it down and then turn off the powersupply switch, turn it back on and it will stay off. But after I hit the power button, it will again act incorrectly when shutting down. I have replaced the power supply with a know good and it reacts the same.
any help would be appreciated.
bios to 1.4
1.7 celeron
6534 msi board
window 2k
320 megs ram (2 sticks could be problem?)
crappy pci video card sis 6326 (its a business machine not a gamer)
realtec nic
onboard sound
thanks
dex

For STR-1 mode: Standby mode in normal state where the system is "actively suspend". To re-activate system in this mode can be through keypress or mouse press buttons.
For STR-3 mode: Standby mode in power saving state where all active activities are being virtually saved into system memory. When this mode is activated, the system will direct go into a "fake shutdown" state to consume the least amount of power. To re-activate system in this mode is only through the power switch, once activated, the system will fall back to it's last active stage.
STR-3 mode is a recommend suspend mode for quiet and power saving step for a system.
For your case, what are the errors that occurred after a shutdown and a cold bootup?

Problems shutting down, starting up

My IMac has been giving me several problems lately. It sometimes will not go to sleep, and when it does, will not wake up. I have to re-start the computer to wake it up. It often shuts down with no warning or the grey film comes over and says the Mac must be re-started. This morning, I had trouble turning the computer on with the power switch, and when it did turn on, the apple stayed on the computer and the fan turns on loud. I have re-installed the system folder, re-set the PRAM and run Disk Warrier. Any suggestions? My computer is a little over 3 years old.

Hi jfedor, and a warm welcome to the forums!
Since your problem is different, feel free to start a new topic, as it will get more attention, and you problem(s) can be addressed specifically.
Here's the link if it's hard to find where to do it...
http://discussions.apple.com/post!default.jspa?forumID=758
Include what color the Install Disk is, and what it says on it, as well as RAM & free Disk space on you eMac!

Problems shutting down - just starts up again!

Hi
When I try to shut my macbook down, it just bounces back to life again. Very strange. It only started doing this today (I don't think I installed anything new this morning). Everything on the desktop, incl. dock goes away but then it comes back again.
I can switch it off by holding the power button down but that doesn't seem to clear the problem.
I hope this isn't a dumb newbie question.
Does anyone know what the matter could be?
thanks very much
MacBook Mac OS X (10.4.7)

Here's something you can try, you will need to turn on your System administrator account to do this.
Reboot with the original CD by holding the C key. Select english in the list of choices, and when the installer window opens, go to the top menu and select utilities, then choose Reset Password.
Select your drive
Select the user list and drag down to System Adminstrator (root)
Type in a password and verify.
Save
Quit Installer, select Startup Disk
Select your Mac OS X on your Hard Drive, and restart.
Once that is done make sure all applications are quit and saved, you'll need to open Terminal, which will be located under Applications: Utilities
In Terminal type: su
Then your password that you set
It should say root#
then type shutdown -h +1
This should shutdown your system in 1 minute. If this works, then make sure you let the Genius' at the bar know that you succeeded in shutting down this way. It will give them some insight if it is a software issue or not.
Word of the wise... su is a very powerful login... use caution when longing in as a this. I don't usually recommend it but this might help get some insight.
Good luck
-T

Problems shutting down and getting 'Error -39 when trying to open my files

After working all evening using my Macbook Pro, I close out all my programs and shut down the computer.
However, the computer refuses to shut down. The screen freezes and just sits there. After about 10 minutes of waiting I eventually hold down the power button to shut the computer off.
When I restart the MacBook Pro and try to open the file I was working on, I get the following error. 'While attempting to access [FILE], the file manager reported an error -39.'
Why does this keep happening?
MacBook Pro 2.4 GHz Intel Core 2 Duo
4 GB Ram MHz DDR3
Mac OS X 10.5.8
Finale 2010
Logic Studio 9
Yamaha PSR-310 via Midi Interface
null

I don't think you're having an Apple hard disk issue, because your other applications are working without problems.
I believe you are getting the corrupted file(s) (End of file, Error -39) because you are powering off the computer before the application and the computer have completely shut down.
I can't tell you why it is happening, but I suspect that the Finale application is being extremely slow to shut down, and it is leaving the '.mus' file open until it quits.
*Kostby, thanks so much for your reply. I actually work for a software company, so I asked a few people around here and they agree with you. For some reason, the application is taking a very, very long time to quit, and it's causing the computer to keep running instead of shutting down.*
Perhaps some file was corrupted in the old version of the Finale application was carried over with the upgrade? Have you tried reinstalling the application?
*I haven't, but this is a good idea. I will completely remove the program and start over.*
Hardware...
I notice that the keyboard dates from 2006/2007.
*Actually, it's from 1993 (time flies...)*
Is the midi interface Firewire or USB?
USB
Does the midi interface ever cause an error or a 'hang' with or without the keyboard?
*Not that I'm aware of. I haven't used it in awhile, and it's not been connected to the computer in weeks.*
Are there software drivers needed to make the Midi interface work with the Mac.
*No, I simply plugged it in and it worked. No extra software or drivers needed.*
Are the drivers old? (e.g. 10.4.x or 10.5.3)
N/A
Have you tried saving the file to a USB flash drive, rather than a physical hard disk?
*I haven't, but I'll need to save a few tonight if I do a reinstall of Finale.*
Powering off vs suspending vs leaving it run...
Do you get the 'spinning beachball' (spindump) when Finale apparently hangs?
*No spinning beachball. The desktop simply freezes...*
What happens if you leave it on for an hour or overnight after the apparent 'hang'?
*Never done that. Longest I've left it alone during the 'hang' has been about 15 minutes.*
Does the screen ever come back and let you use the computer again?
*After 15 minutes I would hit the power button and force it to shut off. I've never allowed it to go on for this long. I just thought if it didn't come back after 15 minutes it wasn't ever coming back.*
Does the file corruption occur when you suspend the application by closing the lid, rather than shutting it off?
*I've never just closed the lid on my Macbook Pro. I've always either set it to sleep or shut down and waited for it to do so before closing the lid.*
Thanks again for the great suggestions. I will try them all this evening when I get home from work.
Best,
Dana

I have problem shutting down mac book pro os x lion

I have setup os x lion on my mac book pro which i bought after 2010. Over 90% when i want to shut down, the process stop at the end and rounding circle appear for so long that i should turn off the system by pressing and holding power bottom. I do verify and repair the disk permission and for a while it is ok and after some times it is the same story. I even download and install the lion again but nothing happened. As i read over the apple forum some other has the same prob but no one knows how to fix. Smebody tells that it is belong to safari and other mention some other things. Pls kindlly help me.

nahmad02 wrote:
Problem description:
My Mac Book Pro OS X Lion 10.7.5 is running really slow. Takes forever to open the internet and word, please help
Safari Extensions: ℹ️
Searchme Adware! [Remove]
Simple. Click on "Remove" and follow the direction EtreCheck has for you.

Problems shutting down illustrator cs3

Similar Messages

Maybe you are looking for