System Overload & "Save as" crashes

I'm using Logic 7.0.1 on 10.4.2, with Pro App Suport 3. When I begin to play the piece, I get the "System Overload" message every few seconds. (The audio engine was not able to process all required data in time. (-10011). In the CPU window, the right column is never active, while the left column mostly says at 1/4, sometimes spiking to 3/4's. I press the "continue" button and begin to play again. The CoreAudio alert repeats a dozen times as I continue through the piece until I reach the last note I've been able to record.
Then, I can suddenly play back from the beginning of the song, all the way through without the error message at all. It is as if the computer stops when it tries to process each new sample, but once it has played through all of them, it handles them easily. However, once I can play the whole piece, adding a new sample (a large sample like performance legato) doesn't trigger the alert message. I only get it when I am first beginning to play through the piece.
I have an external Firewire HD by LaCie to store my samples, so that on the laptop, 37.91 GB's of 55.76 GB capacity are available. I use EXS 24 samples only, Solo Strings from VSL, with Core Audio (till I get more acquainted with Logic 7 and decide what I need). The piece is a string quartet, so even though I have 80 samples on different tracks, there are only 4 notes playing at once at any time. The only plug ins are platinumverb and gain, and the problem continues with these plug-ins "bypassed."
I have been reading the discussion board and took advice given about upgrading to Logic 7.0.1, and getting Pro Application Support 3.1. The problems I experienced have not been corrected.
I decided to use CoreAudio until I became more familiar with the program, and I realize with a three year old laptop, I must be pushing the system to the limit. But then again, it plays easily once I have slugged through the error messages. I ereased my HD and reinstalled Logic a few weeks ago. That did not fix the problem either. ( I upgraded to 10.4 to use Toast 7, but then I was unable to use my modem. After 72 hours of Apple support trouble shooting via telephone, I was told to erase my hard drive and reinstall everything. I did so and the problem wasn't fixed. I then talked to someone who knew of a bug in 10.4. I didn't have to erase the HD after all. I was told the bug was fixed in 10.4.2)
The second problem involves saving. I save this piece as a "project." I can use the "save" option without a crash, but 99% of the time, if I use the "save as" option, I get the "beach ball of death" and send yet another report to Apple.
How is my laptop able to process the data in time once I slog through all the alert messages telling me it cannot? Does anyone know of a "save as" fix?
Much Obliged!
Billy

I'm not sure if you have this, and mis-typed or something, but Logic 7.1 (the update you pay for) and the 7.0.1 and Pro App Support solved this problem for me. However, we installed them all at once so I don't know which fixed the "Save As..." glitch....
Regarding the other query, I sometimes get this too - the computer seems to think there's too much information even though it's already been playing it all, and even if you mute all but one of the channels! (in fact - I think I recall it refusing to play even when all tracks are muted... christ...)
Generally I have to restart the app (and maybe the computer). This always does the trick for me.
Hope this helps,
Best,
Mickey.

Similar Messages

  • Logic Pro X Crashing | System Overload

    Earlier today I was recording some friends in my studio using Logic Pro X, only to record, 5 drum mics, 3 guitar tracks, a bass track and then a piano midi layer over the top. My computer coped fine without crashing or showing the annoying 'System Overload' warning. However, this evening, after only adding EQs and changing levels, it crashes always at a particular mark in the project. I tried 'freezing' the tracks in place but still stumping at the same mark. I also tried just bouncing the file down, and still no luck. Any tips?
    Thanks,
    Dan Keen

    HI Dan,
    I have similiar problems in Logic Pro 9 since half a year. I stil haven't found what is causing it, but what works for me most of the times is to have Logic play through the whole song one time before starting to record again. This leads me to think it is a buffering issue so I am gonna have to check out my settings there as well.
    I am on MBP too running 64bits and with 8g memory so that should not be an issue. freezing didn't work for me either.
    RG
    Erik

  • System Overload ...i know ..I'm not the 1st ...

    _History Below_
    Topic : System Overload ...i know ..I'm not the 1st ...
    This topic has been archived - replies are not allowed.
    Your question is not answered.
    Mark as answered.
    Use the "helpful" or "solved" buttons to award points to replies.
    Subscribe to this Topic Back to Topic List
    Replies : 10 - Pages : 1 - Last Post : Aug 10, 2009 12:04 PM by: Pancenter
    4feet4
    Posts: 17
    From: Pasadena
    Registered: Mar 12, 2009
    System Overload ...i know ..I'm not the 1st ...
    Posted: Aug 9, 2009 7:52 PM
    Any quick tips on what to do? My project is small - while monitoring my CPU usage it never goes above 30 while running the project - I've got 2.78 GB of free disk space - 4Gig Ram - I dont use my IMAC OSX 10.5.5 for anything but Logic? Hoping to get around this CONSTANT issue - thanks for your help.
    Imac Mac OS X (10.5.5)
    Larry Mal
    Posts: 654
    From: Saint Louis, Missouri
    Registered: Sep 27, 2007
    Re: System Overload ...i know ..I'm not the 1st ...
    Posted: Aug 9, 2009 9:48 PM in response to: 4feet4
    Well, if you are saying you have only 2.78 GB's of space on your hard drive, then you'll want to have more. You should leave about 10-15% of your drive free.
    dual 2.8GHz Mac Pro, Macbook Pro 2.16 GHz Mac OS X (10.5.6) 2 GB RAM
    4feet4
    Posts: 17
    From: Pasadena
    Registered: Mar 12, 2009
    Re: System Overload ...i know ..I'm not the 1st ...
    Posted: Aug 9, 2009 10:51 PM in response to: Larry Mal
    I'm running LP8 - I have an IMAC OSX 10.5.5 - 2.4 processor - 4 GB RAM - M-Audio Fast Track Pro interface (USB direct to MAC) - I do NOT have an external hard drive ( sounds like I should ? - although I was told by others my system would be sufficient) - I use ALL instruments/track options ( midi etc) and will need to in the future - I want to be able to run a full music project 10-15 tracks. So far I'm running 4-5 tracks -(1) midi - the rest are audio with little to no effects ( in one project I'm using an LP8 template but deleted most of the tracks to cut down on the load ). Don't know if I can freeze these tracks-I'm new to this - thats why I'm looking for options ........ i was also using a 3rd party software in the project - Steinberg Groove Agent 3 (drums) but it was giving me the same error ..even when it was the ONLY track in the project....(its not fully compatible) - however I was finally able to create a full drum track with GA3 - play the midi data back - and record it to an audio track - therefore deleting the midi data I was having issues with and keeping the drums.... hope this helps?
    Imac Mac OS X (10.5.5)
    4feet4
    Posts: 17
    From: Pasadena
    Registered: Mar 12, 2009
    Re: System Overload ...i know ..I'm not the 1st ...
    Posted: Aug 10, 2009 6:39 AM in response to: 4feet4
    Updated
    Imac Mac OS X (10.5.5) 2.4 Processor, 4 GB RAM, M-Audio Fast Track Pro Interface, No External HD
    Larry Mal
    Posts: 654
    From: Saint Louis, Missouri
    Registered: Sep 27, 2007
    Re: System Overload ...i know ..I'm not the 1st ...
    Posted: Aug 10, 2009 7:54 AM in response to: 4feet4
    Perfect. Well here are some suggestions:
    1) Logic 7, 8 and 9 all have a "freeze" function. Logic 9 has a new "bounce in place" function which I haven't used yet. These will make temporary audio files of your MIDI instruments so that you are able to play them as finished audio for the most part and free up CPU power. ( I haven't yet used "bounce in place", I just got Logic 9.) This will help with MIDI instruments quite a bit, and you can still go back and change them by un-freezing... I guess "thawing" would be the proper term.
    2) The reason I was asking about your audio interface is because I was wondering what you had available. You very definitely want to record to a non-system (on that Logic nor your operating system are on) drive. Firewire is much superior to USB, which is why I'm glad to hear you are using USB as your audio in. By using Firewire in and Firewire out, on an iMac, you would be halving the bandwidth. In your case you are not.
    You will add very much stability to your Logic work by adding an external Firewire drive and recording audio to it, and working on Logic projects there! If you have the money, I'd go with Firewire 800, which is frankly overkill, but why not. Firewire 400 drives will work fine for you. Add one and many of the overload messages will disappear, simply because right now you are pulling information from (in the form of calculating what the virtual instruments and Logic are doing) and writing information to (in the form of writing what those instruments and Logic are resulting in) to the same disk.
    Try these two things and get back to us. I think you'll be very happy with the results.
    It's also important to pay attention to your buffer size. When it is not important for you to play with it in real time, you want to make it be 1024. Otherwise as low as possible. So when you are recording audio to a MIDI drum track, you'd want it to be very low so you can play along accurately. When you have all that done, and are editing MIDI only, then put the buffer higher. When mixing, put it higher.
    Let me know how this works, good luck, L
    dual 2.8GHz Mac Pro, Macbook Pro 2.16 GHz Mac OS X (10.5.6) 2 GB RAM
    4feet4
    Posts: 17
    From: Pasadena
    Registered: Mar 12, 2009
    Re: System Overload ...i know ..I'm not the 1st ...
    Posted: Aug 10, 2009 9:10 AM in response to: Larry Mal
    Ok Great - Thanks - makes sense - I was using a Lacie with Protools an my PC ( it recently crashed) - I was under the impression I would have enough processing power with out it on the MAC.
    Looks like I can pick one up for just a little over $100 ( I'm rolling in that kind of cash) ... please clarify though - you stated: "Firewire is much superior to USB, which is why I'm glad to hear you are using USB as your audio in. By using Firewire in and Firewire out, on an iMac, you would be halving the bandwidth. In your case you are not" ....are you GLAD to hear I am using USB as in - We may have found the problem .... go external to free up processing ? Please confirm.
    Thanks again
    Imac Mac OS X (10.5.5) 2.4 Processor, 4 GB RAM, M-Audio Fast Track Pro Interface, No External HD
    CCTM
    Posts: 249
    Registered: Mar 11, 2007
    Re: System Overload ...i know ..I'm not the 1st ...
    Posted: Aug 10, 2009 9:28 AM in response to: 4feet4
    4feet4 wrote:
    Ok Great - Thanks - makes sense - I was using a Lacie with Protools an my PC ( it recently crashed) - I was under the impression I would have enough processing power with out it on the MAC.
    As stated in an earlier reply, if you only have 2 or 3 gigs of free space on your Mac hard drive, processing power is NOT the problem. Your boot disc is way too full. You should have at least 20-30GB free.
    Running a second drive for the audio side will, of course, help, but you MUST clear out the main hard drive (or fit a larger one) before you run into even more serious problems.
    HTH
    CCT
    Larry Mal
    Posts: 654
    From: Saint Louis, Missouri
    Registered: Sep 27, 2007
    Re: System Overload ...i know ..I'm not the 1st ...
    Posted: Aug 10, 2009 9:37 AM in response to: 4feet4
    Well, you have enough processing power, that isn't the issue. All the processing power in the world won't matter if you have 64 megabytes of RAM, there will be a bottleneck. Another bottleneck is with data transference. Like I said, when using a single drive to transfer date from as well as to- which is what you are doing when you are using Logic, running within the scope of the operating system, and hosting virtual instruments, all of which is writing the resulting audio information to the same drive, at the same time, then you are creating another problem. But you don't have to do that, by sending the audio written to another drive other than the one the audio is being generated from.
    In other words, your processing power is both faster than and irrelevant to the physical limitations of the hard drive itself.
    Another bottleneck would be if you were recording tracks on a Firewire in, and sending that to and external Firewire drive out. This is one of the limitations of the iMac, there is no way to add what is called another bus, which is simply another pipeline for data transference. You can get around that with a Mac Pro, in which you add another internal hard drive, which connects directly to the motherboard, and has its own bus. Or by adding another Firewire PCIe card, which will add another Firewire bus, again, with its own data transference. On an iMac, you have one Firewire bus, and one USB bus.
    Clear? You can imagine these as pipes of water. The more pipes you have leading to and from a location the faster it will go.
    USB, in your case, is a dedicated pipeline in. Nothing (well, your mouse, maybe a flash drive) is using that pipeline. Your Firewire is a pipeline out, in this case- you could reverse this, it doesn't matter*. If you use Firewire in and out, then you are sending water flowing in both directions in the same pipe. It will work, but not as well. By adding a dedicated bus, you would be adding another pipe to flow in one way, while the original flowed the other way. No impedances.
    I don't see why you can't use the Lacie drive you already have, though. It's quite likely your crash wasn't due to it. No need to buy another drive, if it's Firewire, anyway. Just give it a shot- this isn't a cure all, but just good audio practice. Let me know how it pans out. Good luck, L
    *Firewire is better than USB in all situations. But you seem to be going a track or two of USB audio in, so I'd use USB for that. For light use it's fine. Then you can use your superior Firewire bus to write the audio to the external Firewire drive.
    dual 2.8GHz Mac Pro, Macbook Pro 2.16 GHz Mac OS X (10.5.6) 2 GB RAM
    4feet4
    Posts: 17
    From: Pasadena
    Registered: Mar 12, 2009
    Re: System Overload ...i know ..I'm not the 1st ...
    Posted: Aug 10, 2009 11:12 AM in response to: Larry Mal
    L - Thanks for laying that out in simple terms - learning a ton and loving it ( when things work) - I will pick up another Lacie - my old Lacie for my PC crashed - I'm better off starting from scratch ( I'm still trying to retrive some data of the old one) ... I'll let you know how it works. I would have got an external drive outright but the Logic Certified guys at Apple told me I would not need one - sounds like this is the big problem. I'll use the freeze method when needed also....... maybe I'll have better luck with Groove Agent 3 with the external drive.
    Much appreciated-
    (TBD)
    Imac Mac OS X (10.5.5) 2.4 Processor, 4 GB RAM, M-Audio Fast Track Pro Interface, No External HD
    Larry Mal
    Posts: 654
    From: Saint Louis, Missouri
    Registered: Sep 27, 2007
    Re: System Overload ...i know ..I'm not the 1st ...
    Posted: Aug 10, 2009 11:39 AM in response to: 4feet4
    And free up some room on that system drive.
    dual 2.8GHz Mac Pro, Macbook Pro 2.16 GHz Mac OS X (10.5.6) 2 GB RAM
    Pancenter
    Posts: 3,306
    From: Southwest U.S.
    Registered: Apr 22, 2007
    Re: System Overload ...i know ..I'm not the 1st ...
    Posted: Aug 10, 2009 12:04 PM in response to: 4feet4
    4feet4 wrote:
    L - Thanks for laying that out in simple terms - learning a ton and loving it ( when things work) - I will pick up another Lacie - my old Lacie for my PC crashed - I'm better off starting from scratch ( I'm still trying to retrive some data of the old one) ... I'll let you know how it works. I would have got an external drive outright but the Logic Certified guys at Apple told me I would not need one - sounds like this is the big problem. I'll use the freeze method when needed also....... maybe I'll have better luck with Groove Agent 3 with the external drive.
    Groove Agent 3 loads samples into memory so I doubt if your luck will change.
    The -first- thing I would do is clear some space on your hard drive, my feeling is that OSX is writing swap files and the drive head is working overtime to try and find free space to write. That in itself could cause an overload.
    Free drive space now or expect more problems than you're currently experiencing.
    pancenter-
    Power Mac G5 1.8GHz Dual, 4GB RAM Mac OS X (10.5.5) RME Audio - MOTU MIDI, Mac (Logic 8.02), Intel/XP-Pro Quad Core PC

    _History Below_
    Topic : System Overload ...i know ..I'm not the 1st ...
    This topic has been archived - replies are not allowed.
    Your question is not answered.
    Mark as answered.
    Use the "helpful" or "solved" buttons to award points to replies.
    Subscribe to this Topic Back to Topic List
    Replies : 10 - Pages : 1 - Last Post : Aug 10, 2009 12:04 PM by: Pancenter
    4feet4
    Posts: 17
    From: Pasadena
    Registered: Mar 12, 2009
    System Overload ...i know ..I'm not the 1st ...
    Posted: Aug 9, 2009 7:52 PM
    Any quick tips on what to do? My project is small - while monitoring my CPU usage it never goes above 30 while running the project - I've got 2.78 GB of free disk space - 4Gig Ram - I dont use my IMAC OSX 10.5.5 for anything but Logic? Hoping to get around this CONSTANT issue - thanks for your help.
    Imac Mac OS X (10.5.5)
    Larry Mal
    Posts: 654
    From: Saint Louis, Missouri
    Registered: Sep 27, 2007
    Re: System Overload ...i know ..I'm not the 1st ...
    Posted: Aug 9, 2009 9:48 PM in response to: 4feet4
    Well, if you are saying you have only 2.78 GB's of space on your hard drive, then you'll want to have more. You should leave about 10-15% of your drive free.
    dual 2.8GHz Mac Pro, Macbook Pro 2.16 GHz Mac OS X (10.5.6) 2 GB RAM
    4feet4
    Posts: 17
    From: Pasadena
    Registered: Mar 12, 2009
    Re: System Overload ...i know ..I'm not the 1st ...
    Posted: Aug 9, 2009 10:51 PM in response to: Larry Mal
    I'm running LP8 - I have an IMAC OSX 10.5.5 - 2.4 processor - 4 GB RAM - M-Audio Fast Track Pro interface (USB direct to MAC) - I do NOT have an external hard drive ( sounds like I should ? - although I was told by others my system would be sufficient) - I use ALL instruments/track options ( midi etc) and will need to in the future - I want to be able to run a full music project 10-15 tracks. So far I'm running 4-5 tracks -(1) midi - the rest are audio with little to no effects ( in one project I'm using an LP8 template but deleted most of the tracks to cut down on the load ). Don't know if I can freeze these tracks-I'm new to this - thats why I'm looking for options ........ i was also using a 3rd party software in the project - Steinberg Groove Agent 3 (drums) but it was giving me the same error ..even when it was the ONLY track in the project....(its not fully compatible) - however I was finally able to create a full drum track with GA3 - play the midi data back - and record it to an audio track - therefore deleting the midi data I was having issues with and keeping the drums.... hope this helps?
    Imac Mac OS X (10.5.5)
    4feet4
    Posts: 17
    From: Pasadena
    Registered: Mar 12, 2009
    Re: System Overload ...i know ..I'm not the 1st ...
    Posted: Aug 10, 2009 6:39 AM in response to: 4feet4
    Updated
    Imac Mac OS X (10.5.5) 2.4 Processor, 4 GB RAM, M-Audio Fast Track Pro Interface, No External HD
    Larry Mal
    Posts: 654
    From: Saint Louis, Missouri
    Registered: Sep 27, 2007
    Re: System Overload ...i know ..I'm not the 1st ...
    Posted: Aug 10, 2009 7:54 AM in response to: 4feet4
    Perfect. Well here are some suggestions:
    1) Logic 7, 8 and 9 all have a "freeze" function. Logic 9 has a new "bounce in place" function which I haven't used yet. These will make temporary audio files of your MIDI instruments so that you are able to play them as finished audio for the most part and free up CPU power. ( I haven't yet used "bounce in place", I just got Logic 9.) This will help with MIDI instruments quite a bit, and you can still go back and change them by un-freezing... I guess "thawing" would be the proper term.
    2) The reason I was asking about your audio interface is because I was wondering what you had available. You very definitely want to record to a non-system (on that Logic nor your operating system are on) drive. Firewire is much superior to USB, which is why I'm glad to hear you are using USB as your audio in. By using Firewire in and Firewire out, on an iMac, you would be halving the bandwidth. In your case you are not.
    You will add very much stability to your Logic work by adding an external Firewire drive and recording audio to it, and working on Logic projects there! If you have the money, I'd go with Firewire 800, which is frankly overkill, but why not. Firewire 400 drives will work fine for you. Add one and many of the overload messages will disappear, simply because right now you are pulling information from (in the form of calculating what the virtual instruments and Logic are doing) and writing information to (in the form of writing what those instruments and Logic are resulting in) to the same disk.
    Try these two things and get back to us. I think you'll be very happy with the results.
    It's also important to pay attention to your buffer size. When it is not important for you to play with it in real time, you want to make it be 1024. Otherwise as low as possible. So when you are recording audio to a MIDI drum track, you'd want it to be very low so you can play along accurately. When you have all that done, and are editing MIDI only, then put the buffer higher. When mixing, put it higher.
    Let me know how this works, good luck, L
    dual 2.8GHz Mac Pro, Macbook Pro 2.16 GHz Mac OS X (10.5.6) 2 GB RAM
    4feet4
    Posts: 17
    From: Pasadena
    Registered: Mar 12, 2009
    Re: System Overload ...i know ..I'm not the 1st ...
    Posted: Aug 10, 2009 9:10 AM in response to: Larry Mal
    Ok Great - Thanks - makes sense - I was using a Lacie with Protools an my PC ( it recently crashed) - I was under the impression I would have enough processing power with out it on the MAC.
    Looks like I can pick one up for just a little over $100 ( I'm rolling in that kind of cash) ... please clarify though - you stated: "Firewire is much superior to USB, which is why I'm glad to hear you are using USB as your audio in. By using Firewire in and Firewire out, on an iMac, you would be halving the bandwidth. In your case you are not" ....are you GLAD to hear I am using USB as in - We may have found the problem .... go external to free up processing ? Please confirm.
    Thanks again
    Imac Mac OS X (10.5.5) 2.4 Processor, 4 GB RAM, M-Audio Fast Track Pro Interface, No External HD
    CCTM
    Posts: 249
    Registered: Mar 11, 2007
    Re: System Overload ...i know ..I'm not the 1st ...
    Posted: Aug 10, 2009 9:28 AM in response to: 4feet4
    4feet4 wrote:
    Ok Great - Thanks - makes sense - I was using a Lacie with Protools an my PC ( it recently crashed) - I was under the impression I would have enough processing power with out it on the MAC.
    As stated in an earlier reply, if you only have 2 or 3 gigs of free space on your Mac hard drive, processing power is NOT the problem. Your boot disc is way too full. You should have at least 20-30GB free.
    Running a second drive for the audio side will, of course, help, but you MUST clear out the main hard drive (or fit a larger one) before you run into even more serious problems.
    HTH
    CCT
    Larry Mal
    Posts: 654
    From: Saint Louis, Missouri
    Registered: Sep 27, 2007
    Re: System Overload ...i know ..I'm not the 1st ...
    Posted: Aug 10, 2009 9:37 AM in response to: 4feet4
    Well, you have enough processing power, that isn't the issue. All the processing power in the world won't matter if you have 64 megabytes of RAM, there will be a bottleneck. Another bottleneck is with data transference. Like I said, when using a single drive to transfer date from as well as to- which is what you are doing when you are using Logic, running within the scope of the operating system, and hosting virtual instruments, all of which is writing the resulting audio information to the same drive, at the same time, then you are creating another problem. But you don't have to do that, by sending the audio written to another drive other than the one the audio is being generated from.
    In other words, your processing power is both faster than and irrelevant to the physical limitations of the hard drive itself.
    Another bottleneck would be if you were recording tracks on a Firewire in, and sending that to and external Firewire drive out. This is one of the limitations of the iMac, there is no way to add what is called another bus, which is simply another pipeline for data transference. You can get around that with a Mac Pro, in which you add another internal hard drive, which connects directly to the motherboard, and has its own bus. Or by adding another Firewire PCIe card, which will add another Firewire bus, again, with its own data transference. On an iMac, you have one Firewire bus, and one USB bus.
    Clear? You can imagine these as pipes of water. The more pipes you have leading to and from a location the faster it will go.
    USB, in your case, is a dedicated pipeline in. Nothing (well, your mouse, maybe a flash drive) is using that pipeline. Your Firewire is a pipeline out, in this case- you could reverse this, it doesn't matter*. If you use Firewire in and out, then you are sending water flowing in both directions in the same pipe. It will work, but not as well. By adding a dedicated bus, you would be adding another pipe to flow in one way, while the original flowed the other way. No impedances.
    I don't see why you can't use the Lacie drive you already have, though. It's quite likely your crash wasn't due to it. No need to buy another drive, if it's Firewire, anyway. Just give it a shot- this isn't a cure all, but just good audio practice. Let me know how it pans out. Good luck, L
    *Firewire is better than USB in all situations. But you seem to be going a track or two of USB audio in, so I'd use USB for that. For light use it's fine. Then you can use your superior Firewire bus to write the audio to the external Firewire drive.
    dual 2.8GHz Mac Pro, Macbook Pro 2.16 GHz Mac OS X (10.5.6) 2 GB RAM
    4feet4
    Posts: 17
    From: Pasadena
    Registered: Mar 12, 2009
    Re: System Overload ...i know ..I'm not the 1st ...
    Posted: Aug 10, 2009 11:12 AM in response to: Larry Mal
    L - Thanks for laying that out in simple terms - learning a ton and loving it ( when things work) - I will pick up another Lacie - my old Lacie for my PC crashed - I'm better off starting from scratch ( I'm still trying to retrive some data of the old one) ... I'll let you know how it works. I would have got an external drive outright but the Logic Certified guys at Apple told me I would not need one - sounds like this is the big problem. I'll use the freeze method when needed also....... maybe I'll have better luck with Groove Agent 3 with the external drive.
    Much appreciated-
    (TBD)
    Imac Mac OS X (10.5.5) 2.4 Processor, 4 GB RAM, M-Audio Fast Track Pro Interface, No External HD
    Larry Mal
    Posts: 654
    From: Saint Louis, Missouri
    Registered: Sep 27, 2007
    Re: System Overload ...i know ..I'm not the 1st ...
    Posted: Aug 10, 2009 11:39 AM in response to: 4feet4
    And free up some room on that system drive.
    dual 2.8GHz Mac Pro, Macbook Pro 2.16 GHz Mac OS X (10.5.6) 2 GB RAM
    Pancenter
    Posts: 3,306
    From: Southwest U.S.
    Registered: Apr 22, 2007
    Re: System Overload ...i know ..I'm not the 1st ...
    Posted: Aug 10, 2009 12:04 PM in response to: 4feet4
    4feet4 wrote:
    L - Thanks for laying that out in simple terms - learning a ton and loving it ( when things work) - I will pick up another Lacie - my old Lacie for my PC crashed - I'm better off starting from scratch ( I'm still trying to retrive some data of the old one) ... I'll let you know how it works. I would have got an external drive outright but the Logic Certified guys at Apple told me I would not need one - sounds like this is the big problem. I'll use the freeze method when needed also....... maybe I'll have better luck with Groove Agent 3 with the external drive.
    Groove Agent 3 loads samples into memory so I doubt if your luck will change.
    The -first- thing I would do is clear some space on your hard drive, my feeling is that OSX is writing swap files and the drive head is working overtime to try and find free space to write. That in itself could cause an overload.
    Free drive space now or expect more problems than you're currently experiencing.
    pancenter-
    Power Mac G5 1.8GHz Dual, 4GB RAM Mac OS X (10.5.5) RME Audio - MOTU MIDI, Mac (Logic 8.02), Intel/XP-Pro Quad Core PC

  • System Overload & How to get the best G4 Performance

    Okay all you Logic and OSX Gurus. I need your help. I've finally made the LOGIC leap from OS9 and have hit the SYSTEM OVERLOAD wall like many of you before me.
    I've been pouring over this, and many other Forums and Blogs, for about two weeks now, and have tried many of the fixes / solutions to no avail. I estimate I'm now getting about 25% of my OS9 Logic performance from Logic in OSX.
    One specific case in point is this. A four minute song sketch. No tempo changes. Four midi tracks, 6 Audio instruments and 2 EFX (1 Guitar Amp Pro, 1 Space Designer that's no even being used).
    I have unsuccessfully tried to Bounce this to disc for two weeks now. The AUDIO and DISK I/O Meters barely register until the GUITAR AMP PRO track brings the AUDIO METER up to about 1/3rd usage. At various points in the Bounce the G4 will completely FREEZE, and I will have manually restart.
    THINGS I HAVE TRIED, and continue to try are:
    - Repairing Permissions
    - Trashing Preferences
    - Updating MOTU Drivers
    - Changing Processor performance setting - which I cannot do BTW, because my system does not seem to support this option.
    - Closing all Widgets
    - Freeing up more Space on my Mac OSx startup disk (I now have 78.41 Gig available on a 114.49 Gig drive)
    - Run Cocktail to clean up System logs and temporary files
    - FREEZING TRACKS as a temporary 'fix'. This did nothing BTW but add more strain to the CPU and I still had about 1/3rd the usage with my GUITAR AMP Plugin (and it still crashed).
    - Increased AUDIO BUFFER to 1024
    So, (and I guess this is really two sides of the same question)...
    1) How do I FIX this SYSTEM OVERLOAD problem, and
    2) How do I "optimize" my Dual 1.25 G4 in order to get the best performance possible out of LOGIC PRO?
    OTHER QUESTIONS I HAVE ARE:
    - Does the G4 have the processing power needed to run LOGIC PRO?
    - I'm confident adding RAM will "help" (can't hurt), but am I really dealing with a RAM Problem here or, again, can these processors really handle it?
    BTW - I'm not looking for an excuse to go shopping for a Quad G5 (I mean who needs an excuse... . But, I'm really trying to determine if at the end of the day I will spend money on RAM, Hard Drives, whatever..., and then still be frustrated and end up shopping.
    - Are SCSI drives a problem with Tiger / Logic? These Cheetah drives are fast (10,000 RPM), reliable, and have been great drives to record on. I'm trying to do this simple bounce to one of the Cheetahs and as I said it's just not happening.
    - Does the startup volume size effect performance?
    - Does the amount of free space on the start up drive effect performance?
    - Firewire 400 vs 800? My sample library is on the Firewire drive, and I'm thinking this does not pull a lot on the CPU as these get loaded into memory before playing? Am I right about that? It is Firewire 400.
    A long letter and a lot of questions. I thank you all in advance for any answers, guidance or direction you can give. Please also let me know if there is something I HAVEN'T asked, looked at or should be doing.
    Best,
    Kevin
    Kevin Saunders Hayes
    SYSTEM SPECS
    Machine Name: Power Mac G4
    Machine Model: PowerMac3,6
    CPU Type: PowerPC G4 (3.3)
    Number Of CPUs: 2
    CPU Speed: 1.25 GHz
    L2 Cache (per CPU): 256 KB
    L3 Cache (per CPU): 2 MB
    Memory: 1 GB
    Bus Speed: 167 MHz
    Boot ROM Version: 4.4.8f2
    Logic 7.1.1 (885)
    Pro Application Support 3.1
    MOTU 896 - Latest drivers
    2 - Seagate Cheetah 9 gig SCSI drives
    1 - Oxford Firewire (Up to 400 Mb/sec) with EXS Library
    G4 Duel 1.25   Mac OS X (10.4.3)  

    And after months of using Express, and a week of
    using Logic, I hadn't had a system overload until
    today. Now I'm having them all the time. It wasn't a
    set up change, it wasn't running on the battery, it
    wasn't running software monitoring, it's set up with
    512 i/o buffer, medium processor buffer. And it
    wasn't brought on by number of tracks - that's for
    sure. After it started happenind and I took a break &
    came back, I was sitting on my couch, Powerbook in
    my lap, tapping a beat in with the onscreen
    keyboard.... a SINGLE instrument, mind you. NO plugs,
    no other tracks of ANY kind. And it happened.
    There's a lot of great, relevant and very helpful info on this forum and it all helps and it all counts. But..... so many people are suffering this when moving up to Pro 7 from either Pro 6 or Express. One expects a change in system load when a major update comes along but more and more people are reporting that simply recording 1 or 2 tracks of audio, pure, no plug-ins or EQ is causing an overload whereas in the previous version(s) this was easily accomodated. This, you may have guessed, has happened to me as well. Are we to accept in 1 version increment (albeit a major one) there is such a massive increase in demand from hardware that you cannot record a pure no-plug-in stereo track? When going back to 6.4.3 it will happily record 8 at once, let you EQ and reverb and then do another 8 AND then another. With no troble at all.
    It is pointing more and more towards fundamental flaws in the programming. Did L7 come out too soon? Are we just beta testing what is pro software? We are only on 7.1.1 and 6 went to 6.4.3 but at no stage was it this bad at the fundamentals of what the App is for. I love Logic, I really do, but I think, even with all the great help we are fighting what Apple should be addressing. Not that you can find/contact/talk to or get any sort of response from them.
    I have tried but have gone back to 6.4.3 until 7.1.2 or even 7.2 appears, but I'm not paying for 7.2. My £200 upgrade from 6.4.3 is now sitting on a shelf desperately wanting to use it.

  • Disk too slow / System overload HELP?

    I'm really hoping someone can help me out with this!:
    I purchased a G4 PowerBook around six months ago, with Logic Pro pre-installed. Since then, I have mixed and mastered lots of music that was recorded on a previous system and imported. I was running multiple tracks simultaneously with tons of plug-ins and everything ran smoothly on my new Mac. HOWEVER, within the last month, my playback capabilities have been severely reduced. When I try to play back even two tracks simultaneously (with just one compressor or reverb), I get the error message, "Disk too slow / System overload."
    My first reaction to this problem was to check my disk space and see how much room I had left: it turns out I have over one third of my harddrive space still available. I checked my memory capabilities and they seem to be more than adequate. I bought new virus protection, too, and ran scans to see if that might make a difference, but it hasn't. I don't understand why this is happening on a system so new. ANY ADVICE YOU CAN OFFER WOULD BE GREATLY APPRECIATED!
    Many thanks.
    Powerbook G4   Mac OS X (10.4.6)  

    It is generally not a good idea to run logic on the same drive that contains your audio files and samples. Most of the data involved with logic whether it be programs or individual audio files will be saved physically all over the place on your hard drive. At a certain point the actual part of the drive that reads the data will not be able to move around to all the little different audio files it needs to access for the session on top of running the program and whatever other software that is up. It is best to save all your audio files and samples to a fast external drive (7200rpm at least) otherworldcomputing.com has great drives that have high quality cases and the option to put any drive they have in stock into the case. (i would recommend seagate) If you are going to continue running your entire sessions off the internal drive then you need to keep up with your basic mac housekeeping. You should repair your permissions 2 times a month (use disk utility) You should buy a good directory repair program such as disk warrior. The directory is exactly what it sounds like. It keeps track of where everything is on the computer. If your directory is corrupt the computer will have to do an extra manual search to find what its looking for. If your directory is healthy your computer will make a straight shot to the file you are looking for.

  • System Preferences Keeps on Crashing

    Every time I open the screen saver settings, System Preferences crashes. I've run the repair disk utility programme, but there were no problems. I also ran the repair permissions programme and some stuff was corrected. But still the screen saver settings crash.
    I don't know what to do. If the crash report would be useful I could copy that here. Has anyone had this problem before?
    Thanks

    Hi redinall,
    First quit System Preferences. Then.....
    Try trashing the .plist found @ Home/Library/Preferences/By Host/com.apple.screensaver.xxxx.plist (where the xxxx stands for an alphanumeric string of #'s and letters).
    Try opening System Preferences again and then open Screensaver preferences and see if any luck.
    If still no luck follow through the steps found in the FAQ from Dr. Smoke, of the X-Lab, "Multiple applications quit unexpectedly or fail to launch".
    hope that helps some,
    littleshoulders

  • Constant system overload errors

    Since yesterday I can't play any project anymore. When I hit play the projects plays for two seconds, slows down and a system overload error pops up saying 'system overload or disk too slow'. Logic crashes after that.
    Nothing on my system has changed, no new plugins, no system changes. Many of the project files are on an external drive but it's working nicely and is not in sleep mode or anything.
    Any tips?

    I am not having system overload, but I do want to comment on the CPU meter. I noticed last night that running 3 tracks rewired through Reason 4, and an EXS instrument, my Logic 8 CPU meter indicated one core (second one) at 60-70% at times, with the other core (first one), barely being used. While running this, I launched Activity Monitor, and then hit "CPU" to watch the activity. Guess what, Activity monitor showed no perceptible difference between core usage, with both running at maybe 20-25% for the whole system, including Logic 8. I wonder if Logic 8's problem with system overload is simply a bad monitoring scheme. It is clearly wrong. I can imagine that if I had one or two more tracks running, I would have hit a limit, even though Activity Monitor would have shown my cores at less than 50% usage. Lame, Apple. Take care of this.

  • Screen Saver WindowServer Crashing

    I have a dual 1.42 GHz PowerPC G4 with 2 GBs RAM running 10.4.5.
    When opening Desktop and Screen Saver in System Preferences and selecting anything in that dialog box System Prefs consistently crashes. I would like to prevent the system from going into sleep mode when I have apps that are processing in the background.
    I have run repair permissions and cleared out the cache. Has anyome else had this problem or, more importantly, does anyone know a fix?
    Thanks.
    Please see the System Preferences Crash log below:
    Date/Time: 2006-03-06 10:16:33.287 -0800
    OS Version: 10.4.5 (Build 8H14)
    Report Version: 4
    Command: System Preferences
    Path: /Applications/System Preferences.app/Contents/MacOS/System Preferences
    Parent: WindowServer [84]
    Version: 3.3 (3.3)
    Build Version: 3
    Project Name: SystemPrefsApp
    Source Version: 1260100
    PID: 723
    Thread: 0
    Application Specific Information:
    Desktop &
    Screen Saver v.1.3 (com.apple.preference.desktopscreeneffect)|ScreenSaver|running|GammaWorkSaver
    Exception: EXCBADACCESS (0x0001)
    Codes: KERNPROTECTIONFAILURE (0x0002) at 0x00000030
    Dual 1.42 GHz PowerPC G4, 2 GB AM   Mac OS X (10.4.5)  

    Yes, screen saver preferences crashes immediately when clicking the screen saver preview mode. I am able to get into the desktop preferences. I don't recall the last download before this happened since this has been about a week. All other apps besides ichat, quicktime and the screen saver preference pane are fine and helvetica font is active. Im guessing its probably an issue with one certain application or corrupt file.

  • System Overload in Garageband

    I recently downloaded Yosemite and the newest Garageband, and I am constantly getting the System Overload error, and it is making Garageband completely unusable. I have 4 drum and 2 guitar tracks running (nothing fancy), all of which are Locked.
    -It's an early 2011 macbook
    -I tried upgrading to 8gb ram
    -reset smc
    -restart computer before each session
    -checked energy saver preferences (putting harddrives to sleep)
    -391gb HD available
    -running Yosemite
    -Filevault is not activated

    Do other programs have the same problem?
    Have you tries a restore library in the menu options?
    Have you tries a uninstall and reinstall of the program?
    Yosemite is known to cause problems that is why I didn't update to it.
    Garageband Facebook Group
    Garageband YouTube Channel

  • "Disk too slow or System Overload" ... hardly

    Hi all!
    I  hung onto my 2007 MacPro until just before summer when I upgraded to be on the safe side. I do orchestral work and have been accustomed to running heavy VSL projects on one single machine pretty effortlessly. On my new 12 MacPro, things are working even smootherEXCEPT for this "Disk too slow or System Overload" happening from time to time on fades. The projects in hich I experience this behaviour are audio only, orchestral mixes of between 60 and 70 audio tracks and I get the message when executing fades on all tracks simultaneously. I can't remember getting this on my old MacPro which had a fraction of the cpu-power and not nearly as much ram.
    My specs are 2x2.66 6-Core w/32GB ram, and all audio files, fade files and othe project files, are written to two 2 TB 7200 disks in the internal disk slots, configured as striped RAID. This gives more than enough speed and I still have 1,64 TB of free space on the RAID set.
    This issue comes and goes and I can't seem to figure out what triggers Logic's problem to read fades fast enough. Just now I had some corrupted fade ailes, rebuildt them and now Logic can't get past the fades at all unless I start playing in the middle of them.
    I can't understand why this problem should be introduced on a configuration much, much faster than my previous MacPro where this problem hardly ever occured. I even doubled the I/O buffer from 512 that I was using on my old mac, to 1024 with no difference at all. Increasing Process buffer size to "Large" doesn't have any affet either.
    Any clues anyone?
    Best regards,
    Ginge

    Good point, nice link!
    But the thing is I'm not using any software instruments and apart from one EQ on a track here and there, two Tube tech plugs and two sends to Altiverb (of which one is inactive). This kind of load was not a problem on the old heap and shouldn't be a challenge for a 12-core... Also, without changing anything apart from the move above, it is now playing with only one pixel-high movement on the meter, like you would expect it to do.
    BTW the quirk is now back on the project that was fixed. I did new fades at another position and CPU 1 is now maxing out again. A new set of fades means equal fades on regions on 63 tracks playing simultaneously.
    As I'm writing I'm becoming aware of one interesting aspect: the project files contains imported aaf data and to save space I'm leaving the media-files at the original location where it was put by Pyramix who exported the aaf. I figure there shouldn't be a difference if the audio files reside in a folder called "Media files" or "Audio files". These folders are sitting on the same disk albeit not in the same subfolder. If anything, I'd assume it would minimize potential for error caused by having several copies of files with identically names on different locations on the disks. But now it seems the issue is less likely to appear if I save the project including assets, copying external audio files (on any disk), or at least that is how it looks like right now. New fades are working fine after I've done this.
    Doesn't make sense to me but it seems to make a difference...
    Ginge

  • CoreAudio: Disk is too slow or System Overload. (-10010)

    I keep getting this error when I'm playing a song that has 16 tracks and effects on each track, but each track is frozen (!): CoreAudio: Disk is too slow or System Overload. (-10010). I'm running a G4 and have 2G RAM. Is this common? What can I do to prevent this? Thanks for any advice you can give!
    -David

    In addition to Rohan's suggestions you have more options depending on how you work and what phases of the project you are in.
    Something overlooked very often is polyphony enabled for the EXS24-some patches are set to 64 drop the polyphony to either the minimum you will need or less (if less you will notice older notes cutting out-but you can set it to the necessary number upon bounce or export). Some mono patches from sound designers are set to 32 or 64-even if you enable unison this is often worthless.
    Up your buffer size-I usually have my PBook at 512-I usually do offline editing, location recording and sound design with the book anyways.
    Export the track.
    Set virtual memory in EXS prefs to 'on' and with the largest RAM allocation-slow disk, lots of activity.
    If you use certain exs patches often but only parts of them trimming the excess off the instrument can improve performance. If you have a piano program with good samples you can initially create a lite version with 2 velocity layers and then when it is time to get things sounding good revert the instrument to the original 5 layer-obviously this makes a huge difference depending on what you are using the piano for, leave it if it is critical.
    Save the Channel strip and export as audio file while keeping the sequence in your session. Like Freezing but you can manually trim the file start position and set the bit depth. Freeze files render from the start until the last audible sample and then truncate the tails, meaning even if you can't hear it it is still pulling "silence" from disk as long as there is sound after it. Exporting as 24 or 16 bit will effectively reduce your file size by 25 (24bit) or 50 (16bit) percent. If you know you don't have to edit a performance for weeks to come exporting it will solve alot of problems for CPU.
    Someone should back me up on this one but at the moment I want to say EXSamples load into memory regardless of freeze settings-reducing your resources.
    Disable the filter (if live or playback-N/A with Freeze)-it is often not critical for some patches. The more synthetic sounds or sounds with fewer/shorter samples rely on them.
    Disable Unison.
    Most sample libraries were not recorded at 88/96k-there is no benefit in running them in sessions in these Sampling rates as far as the EXS sound quality goes.
    That should keep you busy for a while, just some tuning to up your system performance.

  • Disk is too slow or System Overload Error on new Core i7 iMac

    Well I just unboxed the new supercomputer, 27 inch iMac with Core i7 and 8gigs of ram. Spent several hours installing Logic Studio 9 and for an opening act I loaded up the demo song by Lily Allen. Too my utter dismay within seconds of playing the demo in Logic Pro I was greeted with the error "Disk is too slow or System Overload.(-10010)".
    Can anyone make sense of this? Shouldn't this computer be able to handle this multitrack Logic song with relative ease? What is the problem here, I, of course, am very confused and very worried that something is very wrong.
    Thanks

    I am running on less of a machine than you are, so I have experienced similar problems, even when playing back 4 audio tracks while recording 2 all at once (usually with significant plug-ins on the 4 playback tracks).
    The easiest solution I've found, without modifying how your plug-ins run, buying hardware, etc., is to "Freeze" the tracks that aren't being worked on at present. It "renders" all of what the plug-ins are doing so that the CPU and hard drive are not taxes nearly as much while playing back. It just takes a few seconds to render them once, and then your playback/recording drops the amount of resources it requires tremendously.
    The easiest way to activate a freeze on a track is to right-click on the track name in the Arrange pane, select "Freeze" so the button that looks like a snowflake appears next to each track. You can click and drag down the contiguous tracks that can be frozen to turn the option on (or individually click to turn them on). You will then need to play the project to "render" the tracks and freeze them. Next time you play the project, it will run with many less resources and should save you from seeing that message.
    As an aside, you may also want to make sure that you are not running any other applications. I found that another app in the background (Connect360) was running on my Mac and sharing my iTunes to my XBox 360, which was also making a good use of the hard drive at the same time. Any other applications running while Logic is running should be closed to ensure the best performance possible in your audio editing environment.
    Hope this helps!
    Frank

  • System overloaded, repeat immediately by batch when triggering event

    Hi,
      My workflow was working till yesterday. But suddenly today, when I run the same process, event is triggered and I Can see the RFC status 'System overloaded, repeat immediately by batch'. And the workflow is not started.
      Can anyone help me in this?
    Thanks,
    Sivagami R

    Hello,
    It seems that can happen - an event can be created and the workflow it's supposed to trigger doesn't start.
    Was there a system crash? Try looking in tx SM58 for the missed events.
    regards
    Rick Bakker
    Hanabi Technology

  • Logic giving me System Overload-error in a specific project

    Hi everyone. I've got a huge problem on my hands. I have a 25-audiotrack project that I'm mixing for someone else. The audiofiles are .wav, all stereo, 16 bit 44.1kHz if I'm not mistaken. I've set them up on 25 audiotracks in Logic. I haven't even got to the point of putting on effects or anything, so it's just clean tracks with no effects and running no Buses either.
    However upon playback, I constantly get this error:
    System Overload.
    The audio engine was not able to process all required data in time. (-10011)
    Now, I'm running OSX 10.4.7 and Logic 7.0.1 on a dual G5 1.8gHz with 1.25GB RAM. My soundcard is called ESI Juli@ (it's not exactly hi-end but it works). I have a 80ish GB harddrive 7200rpm with 8.5gb free space.
    I'm quite a newbie, so I'm thinking it's my audio settings that's the problem. I've tried switching them around a lot but no help. I/O Buffer Size is set to 1024 (highest number available), Max number of audio tracks is set to 86 (plenty atm), and I've checked "Universal Track Mode" and "Larger Disk Buffer". My Process Buffer Range is set to Large. But nothing works...
    Anyone got any pointers? I'm thinking I SHOULD be able to handle 25 tracks of audio + more without problems. Thanks for any help you might be able to give!

    well,
    25 stereo is a 50 mono tracks
    Its may be hdd speed problem
    First chek your OSX System preference
    Go to Energy Saver section
    There must be an option: Put the Hard Discs to sleep when possible
    If it cheked - unchek it
    I have a 80ish GB harddrive 7200rpm with 8.5gb free space
    Try to empty your HDD on 50%,because when HDD is full on 90%(like in your case)data transfer speed go down up to 3time
    Hope this will solve your problem

  • My screen saver preferences CRASHES!

    So, this is pretty simple.
    I don't have a way to change my desktop background nor my screen saver, cause every time i try to do that. the desktop/screen saver window CRASHES!...
    I tried restarting, I already report the issue with apple... but i don't know what i can do!... I mean, there's a way to fix or to restore that specific part of the OS?
    or, hmmm... i don't know!... I'm very confused!...
    Some other details: I have the "iTunes artwork" screen saver, (i don't know why) but that may be the cause of the crash... maybe it doesn't find a file or a specification...
    THANKS A LOT! =D

    Hi, abrahamca. Welcome to the Discussions.
    You wrote: "I don't have a way to change my desktop background nor my screen saver, cause every time i try to do that. the desktop/screen saver window CRASHES!..."I presume you mean that when you attempt to select the "Desktop & Screen Saver" preference pane in System Preferences, this results in System Preferences quitting unexpectedly.
    If so, try the following:
    1. Quit (Command-Q) System Preferences if it is open.
    2. Trash the following two files in your Home > Library > Preferences folder:
    • com.apple.systempreferences.plist
    • com.apple.desktop.plist
    3. Trash the following files in your Home > Library > Preferences > ByHost folder:
    (a) com.apple.systempreferences.xxx.plist
    (b) com.apple.screensaver.xxx.plist
    (c) com.apple.screensaver.screensaver_name.xxx.plist
    where• xxx is an alphanumeric string, and
    • screensaver_name is the name of a screen saver you have used.Whether preferences files of the type shown in (c) exist depends upon the screen saver and if you have changed its options, if any.
    4. Open your Home > Library > Caches folder, then trash the following two files therein:
    • com.apple.preferencepanes.cache
    • com.apple.preferencepanes.searchindexcache
    5. Empty the Trash.
    6. Launch System Preferences and see if all is well. If so, reset Desktop & Screen Saver preferences accordingly.
    Note that some of the information above is from the "System Preferences" chapter of my book, Troubleshooting Mac® OS X, Tiger Edition.
    Good luck!
    Dr. Smoke
    Author: Troubleshooting Mac® OS X

Maybe you are looking for

  • EDI - Incoming Invoice Error and GR based Invoice Verification - 51 No GR

    Hi, We are implementing EDI for incoming invoices and use Goods Receipts based Invoice Verification.  When processing an inbound IDOC Invoice (type INVOIC01) where the Goods Receipt has not yet been posted, then Inbound IDOC is siiting at Error Statu

  • Is there any way to prevent opening the lid from waking my MBP?

    Hi, I have a problem with my screen on my MBP such that when the computer is asleep in its case the lid often comes ajar, wakes the computer, and drains the battery. Is there any way to prevent the lid opening from waking the computer? Thanks for any

  • Group Folders not being created

    Hi folks, i think this is a simple question: i got Mac OS X 10.4.4 Server with OD and Mobile Homes configured. I set up some custom Groups but the Group Folders are not being created automatically. I think there is a terminal command to do this. Does

  • My screen doesn't display. do i need a new iPad?

    My iPad charges, and displays on my computer when connected. But the screen is blank. Has this happened to anyone else.

  • Open in feature only showing 9 apps to open in...

    On both my iPad and iPhone, I noticed that the "open in" feature, only lists the 9 apps to open the file with, if you have more than 9, the rest of the apps do not show and you find yourself needing to delete some apps to be able to show the app you