Parallels Desktop:Sporadic Launching on NEW MacBookPro

Discussion in 'Installation and Configuration of Parallels Desktop' started by viper69, May 14, 2008.

  1. viper69

    viper69 Bit poster

    Messages:
    9
    I am having problems launching Parallels Desktop so I can access Windows Products on this brandnew MacBooksPro. Yesterday and today, when I click on the Parallels Desktop icon, I get the following error. "The application Para. Desktop quit unexpectedly" Then I can either IGNORE, REPORT or RELAUNCH, None of which help obviously, otherwise I wouldn't be here. Then late last evening, I tried it again, and it automatically loaded as if nothing was wrong. I have included the large amount of details that the software provides saved as Apple Word .txt due to space constraints on the upload for this site. Maybe someone looking at the document can help make sense of this "gibberish"

    The only thing I removed was the usersname, I replaced those characters with a bunch of XXX's

    Here's Macprofile info from the Apple menu

    Model Name: MacBook Pro
    Model Identifier: MacBookPro4,1
    Processor Name: Intel Core 2 Duo
    Processor Speed: 2.4 GHz
    Number Of Processors: 1
    Total Number Of Cores: 2
    L2 Cache: 3 MB
    Memory: 2 GB
    Bus Speed: 800 MHz
    Boot ROM Version: MBP41.00C1.B03
    SMC Version: 1.27f1
    Serial Number: W8816970YJX
    Sudden Motion Sensor:
    State: Enabled

    All I can tell you is that on the desktop there is the yellow Para. icon, and on the Apple dock below, on the far right across the white dotted line is a MS Windows XP.pvs icon that is between two folders, just ahead of the trash can. HELP PLZ....When it works, it works great...but the question is when..OH..after looking around on google. I will say that I did stop and start the program w/the proper buttons once it worked.

    Process: Parallels [238]
    Path: /Users/XXXXXX/Desktop/Parallels Desktop.app/Contents/MacOS/Parallels
    Identifier: com.parallels.desktop
    Version: 3.0 (3.0 Build 4128.0)
    Code Type: X86 (Native)
    Parent Process: launchd [73]

    Date/Time: 2008-05-14 12:08:27.410 -0500
    OS Version: Mac OS X 10.5.2 (9C7010)
    Report Version: 6

    Exception Type: EXC_CRASH (SIGBUS)
    Exception Codes: 0x0000000000000000, 0x0000000000000000
    Crashed Thread: 1

    Thread 0:
    0 com.parallels.desktop 0x0034c890 0x1000 + 3455120
    1 com.parallels.desktop 0x0034c938 0x1000 + 3455288
    2 com.parallels.desktop 0x0034cac5 0x1000 + 3455685
    3 com.parallels.desktop 0x0012e9b3 0x1000 + 1235379
    4 com.parallels.desktop 0x000419ec 0x1000 + 264684
    5 com.parallels.desktop 0x00006792 0x1000 + 22418
    6 com.parallels.desktop 0x000066b9 0x1000 + 22201

    Thread 1 Crashed:
    0 libSystem.B.dylib 0x940bcbce __semwait_signal + 10
    1 libSystem.B.dylib 0x940e78cd pthread_cond_wait$UNIX2003 + 73
    2 libGLProgrammability.dylib 0x9360b332 glvmDoWork + 162
    3 libSystem.B.dylib 0x940e6c55 _pthread_start + 321
    4 libSystem.B.dylib 0x940e6b12 thread_start + 34

    Thread 1 crashed with X86 Thread State (32-bit):
    eax: 0x00000004 ebx: 0x940e78ed ecx: 0xb00a0e9c edx: 0x940bcbce
    edi: 0xa042fe00 esi: 0xb00a1000 ebp: 0xb00a0f18 esp: 0xb00a0e9c
    ss: 0x0000001f efl: 0x00000247 eip: 0x940bcbce cs: 0x00000007
    ds: 0x0000001f es: 0x0000001f fs: 0x0000001f gs: 0x00000037
    cr2: 0xb00a0fec
     

    Attached Files:

    Last edited: May 14, 2008
  2. viper69

    viper69 Bit poster

    Messages:
    9
    40 views and not one helpful response..why did Apple even put this software on the computer then...jeez
     
  3. Hugh Watkins

    Hugh Watkins Forum Maven

    Messages:
    943
    because it keeps on truckin'

    I have a stable WinXp Sp3 system with the update to build 5600 (rebooted Mac OS and reinstalled Parallels tools as usual after an update) on this MacBook Pro

    My system has evolved with updates of VM and WinXp over nearly two years

    First check you have updated to the new build 5600

    then make certain memory allocation is between 500 and 924 mb with a 2gb RAM McBook Pro

    small is beautiful

    I have chickened out of Mac OS 10.5.* and Bootcamp

    when I recently tried some machines at an Apple store the copy of Windows had not been registered

    Did you pay for a working VM ?
    (take it back to the store)
    or is it like other preinstalled software only a trial version

    In which case you may need to purchase a licence key from Parallels and another from Microsoft

    I don't use Bootcamp because two years ago it was in unsupported beta
    and I won't get mac OS 10.5.* until I get a new machine

    Likewise Vista is not for me until I cannot avoid it

    so others may help you there if you state your set up
    It took me more than three weeks to learn Parallels

    and I trashed several VM on the way

    building a VM is like making a computer at home - you need an OEM Windows installation DVD at some point from your local "Build a computer" shop

    A VM also needs standard windows good house keeping

    Hugh W
     
  4. viper69

    viper69 Bit poster

    Messages:
    9
    Well I stated the MacProfile info, above, and the entire error message as a txt file as well.

    How would I know if it's a demo version of Parallels?? This isn't my computer, I'm just trying to help my friend out.
     
  5. John@Parallels

    John@Parallels Forum Maven

    Messages:
    6,333
    Version: 3.0 (3.0 Build 4128.0)
    Code Type: X86 (Native)
    Parent Process: launchd [73]

    Version is too old.
    Upgrade to the 5600
     
  6. viper69

    viper69 Bit poster

    Messages:
    9
    Too old for what John? TO WORK!!!! Give me a break..build a quality product for a change. The computer was brand new back then with little use, and your software is already crashing.
     
  7. John@Parallels

    John@Parallels Forum Maven

    Messages:
    6,333
  8. HonzaI

    HonzaI Member

    Messages:
    71
    I guess little more explanation here will help:
    To old for 10.5.x Mac OS. I believe, that when that build was created, Leopard did not exist. The idiot, who put this old build on this version of OS is the one responsible for your problems. Leopard required major changes in the parallels code which you do not have in your version...
    Update to latest release as John suggests and that one should be able to live with Leopard.

    Jan
     
  9. viper69

    viper69 Bit poster

    Messages:
    9
    Thanks Honz..appreciate the info
     

Share This Page