Problem with converting bootcamp vm from 2.5 to 4

Discussion in 'Installation and Configuration of Parallels Desktop' started by Oliver Lübben, Oct 15, 2009.

  1. Oliver Lübben

    Oliver Lübben Bit poster

    Messages:
    3
    Hello folks,

    after spending much time in the forum without finding real help I decided to write my own post.
    I have installed my Snow Leopard over Leopard 10.5.x and after this I have noticed that my old Parallels in Version 2.5 is not able to work with SL.
    So I bought Version 4.0 and installed it but now the problems came.
    I can´t convert my bootcamp win xp to the new format, Every time I get the same error.

    " Die Festplatte der Bootcamp-Partition konnte nicht
    konfiguriert werden. Bei der Konfiguration der Festplatte ist ein Fehler aufgetreten.
    Achten Sie daruf, dass Sie die Lese-/Schreibrechte für diese Festplatte besitzen "

    In the forum I find out, that this problem occurs also in older version but all hints don't really work for me.
    So there is no way back and forward there is also no one. Bad situation.

    Can the Support Team help.
    I sold for a Programm and can' use it since weeks.

    Reagards
    Oliver
     
  2. Oliver Lübben

    Oliver Lübben Bit poster

    Messages:
    3
    No ideas ?
    Sorry, I have forgotten the official problem id :
    ID 643232
     
  3. Oliver Lübben

    Oliver Lübben Bit poster

    Messages:
    3
    Problem solved !!!

    Hello everybody,

    after long time reading in this forum I found the following hint :

    #####
    enter the following command in the Terminal:

    mv "/Library/Parallels/Parallels Service.app/Contents/MacOS/BootcampConfigurator" "/Library/Parallels/Parallels Service.app/Contents/MacOS/BootcampConfigurator.old"
    Maybe it came from the support team ?
    #####

    After this everything worked fine. I was able to connect my bootcamp partition with a new virtuall machine. The conversion takes only a few seconds and after this windows starts in parallels and directly in bootcamp. So I am happy.
    But .....
    How is it possible, that this old error can be found from V3 to V4 and nobody has fixed it until now.
    No help came from parallels over all these days. shame on you guys.
    Next time I have to update I will test before I pay. If there are also such strange errors I will switch to vm ware fusion. Seems to work without such failures.

    Have fun
    Oliver
     

Share This Page