Bug: OS Installation Assistant keeps appearing

D

drtofu

Bit poster
I've already installed XP as my guest OS, but every time I start up Parallels by clicking the parallels application icon, it always displays the OS installation wizard with no way to access my already installed guest OS. As a workaround, I have to open my XP install by opening the actual .pvs file.

This has only started happening on 3.0. i'd discarded my old XP install and had created a new one using the Windows Express install option (which was very nice).

Any tips of how to make Parallels open the last-used virtual machine again?
 
I had a similar happening and the root cause was that the .pvs and .hdd files were not in the proper locations. I dragged and dropped them into the proper locations [user/Library/Parallels/winxp/winxp.hdd] as specified by Parallel's and it's been fine since.
 
wonder_mice said:
Have you installed your OS form iso image?
Click to expand...
I installed from a CD
wonder_mice said:
Can you give a screen shot of what happens?
Click to expand...

I can email it to you, but the forum won't accept an image this large.

It's just the OS installation assistant window.
 
ajay said:
I had a similar happening and the root cause was that the .pvs and .hdd files were not in the proper locations. I dragged and dropped them into the proper locations [user/Library/Parallels/winxp/winxp.hdd] as specified by Parallel's and it's been fine since.
Click to expand...

I have them in the new 3.0 standard ~/Documents/Parallels/ folder. Had them in the library before and same problem.
 
Okay, my workaround was to create a new virtual machine with the name "winxp", rather than the default name, "Microsoft Windows XP" and that seems to have worked. It no longer prompts me to create a new virtual machine.

But this sounds like a bug. Why wouldn't it accept the default name?
 
Another solution...

The exact same thing was happening to me after updating to 3.0.4128.

After going through MULTIPLE iterations of creating new virtual machines and moving files (.pvs, .hdd, etc.) from old to new locations I finally just *renamed* my .pvs file to match my original .hdd file (both now winxp.pvs and winxp.hdd, the default WAS Microsoft Windows XP.pvs), and I have had no problems loading the correct virtual machine just by launching the application from the dock.

Hope this helps
 
drtofu said:
Okay, my workaround was to create a new virtual machine with the name "winxp", rather than the default name, "Microsoft Windows XP" and that seems to have worked. It no longer prompts me to create a new virtual machine.

But this sounds like a bug. Why wouldn't it accept the default name?
Click to expand...

Hard to say WHY... but, as we can see... YOU had to figure it out... the post by Parallels was a canned and ludicrous answer about leaving the CD in the drive !!

Common Parallels people.... This is exactly the kind of offensive replies that insult the intelligence of the customer. Then, after the canned answer... POOF... you are done and the customer is left to his/her own fate.
 
You must log in or register to reply here.
Back
Top