Failure to Allocate Memory Issue (and @#$% Apple Support)
This problem can be solved. If you'd like the short story, please proceed to the end of this entry in blue. If you'd like to hear the saga, please read on. 
It's a long story. But, for some reason I need to vent so I'll try to do it here and help somebody out at the same time.
I experienced this problem for the first time last night. To solve it, I tried uninstalling Parallels 2.0 and reinstalling from CD-ROM. I could not proceed because the installer kept recognizing a newer version of the software on my Mac than was on my CD-ROM. So, since I'm already on backorder for a copy of 3.0 (and hope it arrives within 15-days) I decided to try to reinstall 3.0 using the free 15-day trialware. Same problem. Failure to allocate memory.
At this point I tried contacting Parallels for help. It's weekend so all I could do was submit a trouble ticket by e-mail. Also, I found this bulletin board. Three conversation strings seem to indicate that others are experiencing the problem and Parallels may be trying to solve it.
Unfortunately, I can't wait. The reason I discovered the problem was because I was trying to start Parallels. The reason I was starting Parallels was because I was trying to use an application that only runs on Windows. Being a recent convert back to Mac (I went to Windows in '98) the last 9 years of life have been Windows-based. So, I need to solve the problem immediately.
I began thinking about it and trying to isolate what could have caused such a problem. Like most problems like these, it probably originated in a fundamental change to the computer. However, I haven't made any such changes (new application or hardware installations, changes in settings, etc.) in quite some time. HOWEVER, there have been automatic updates of the Parallels software recently. Also, there have been automatic updates of the Apple OS software.
So, I deduced that an update in the Parallels software and/or an update in the Apple software were the most likely sources of the problem.
As I had already tried to fix the problem by uninstalling/reinstalling the Parallels software but the problem persisted I felt confident a Parallels update was not the root cause of the problem. I needed to work the Apple side of the problem.
It seemed the logical places to start my investigation were the Parallels website and the Apple website. All I found on the Parallels site were a few forum threads--no explanations or resolutions. Next I started fishing around the Apple support website.
After almost a decade of dealing with Windows upgrades and updates, I was used to finding quite a bit of info about how to deal with integration issues online. Microsoft might not always have a complete solution but it at least usually acknowledges the problem and suggests a way to deal with it. This alone would allow me to start down the path to solution. I didn't need to waste my time doubting myself. I couldn't find anything about this problem on the Apple website. In fact, I could not find any mention of any 3rd party software vendors at all. Since Apple is supposed to be this hip company with totally chill people to help me out and since I had paid for two years customer service I figured I'd try giving Apple a call.
After waiting about 5 minutes the Apple rep came on the line. I explained to him what was happening: I was experiencing a problem with my Parallels software and that I believed it was caused by an Apple OS update. He explained Apple did not help with 3rd party software and in a very incredulous tone he let me know he doubted that my problem could be attributed to Apple's update. I explained how I had isolated the problem and why I thought it was probably caused by the Apple update of 7/4/07. As incredulous as ever, he told me I could roll back the updates by reinstalling OS X and to be sure to choose the "archive" type of installation. Somehow I felt he doubted whether it could help.
Given that Apple frequently updates its s/w as do its s/w providers I wanted to prepare for the future. So, I asked him whether Apple had any support site pertaining to these kinds of issues. He repeated that Apple did not take responsibility for 3rd party applications and that I should consult their websites. I told him that it must be hard for 3rd party s/w providers to keep pace with Apple's updates and that there must be many Apple customers that experience problems as the result of the integration problems, so isn't there something that Apple would like to do to help us out? To speed the search for a solution? At this point, my chill, groovy Apple rep started getting worked up and talking over me, spouting out some corporate line about how difficult it would be for Apple to support the 1000s of 3rd party s/w packages made for Mac.
I'd had enough. After all, I was just trying to be a good customer and prepare for the future--a future when I did not need to call Apple and could solve the problem myself. I told him I didn't call to hear his lip but to get some help. I pointed out that Microsoft deals with the same sorts of issues and as many 3rd party s/w vendors and it manages to share info with its users about them as necessary. Isn't Apple's extreme policy causing excess grief for its users and s/w vendors? Although I'm sure the genius-that-is-Steve-Jobs thinks this support approach saves Apple money, doesn't it also cost more money by creating more phone enquiries? Doesn't it make it difficult for business users to count on Apple? Anyway, I digress... I asked to speak to a supervisor. After waiting about 5 minutes I decided my time would be better spent trying to solve the problem. So, I hung up.
The great thing for you all is that I think I have the solution to this problem. At least this method worked for me:
1. Reinstall OS X choosing the "archive" option of reinstallation.
2. Try Parallels. If the error message comes up again, try uninstalling Parallels, restarting OS X, and reinstalling Parallels.
This worked for me. Granted, I'm now without several months of Apple software updates. I'm weary because there are probably several critical security issues addressed by them. Without them I am probably at greater risk. However, my Parallels works.
Hopefully somebody at Parallels will read this, call Apple, and find out what the 7/4/07 OS X update included to cause the issue to come up. They'll hopefully work together to solve the problem. Hopefully somebody will let me know it's safe download the updates. I can't find out from Apple so I guess I'm relying on Parallels. I hope you guys pull through for me.
Last edited: Jul 16, 2007
