4.0 upgrade issues

I find it hard to believe that none of these issues came up during regular testing.

What is the status of the "7B" BSOD that I am getting? Further to my problem, I have noticed that I am unable to mount my Boot Camp partition using the Parallels Browser (or whatever its called). It fails to mount, something about not being able to access the drive. I figure the two issues are related.
 
I agree. The really funny thing is that they seem to be in denial that it's their software. I had a tech tell me to run a Windows repair! (This of course, I had done LONG ago.)

I'm about a day or so away from calling my credit card company. This is not release quality software.
 
I'm glad I didn't fork out any money for it yet. Its about $120 in Canadian dollars. I would be furious right now if I paid for this mess.

I wonder if they'll give me a new trial key since my trial period will be long gone before the problems are fixed.
 
I find it hard to believe that none of these issues came up during regular testing.

What is the status of the "7B" BSOD that I am getting? Further to my problem, I have noticed that I am unable to mount my Boot Camp partition using the Parallels Browser (or whatever its called). It fails to mount, something about not being able to access the drive. I figure the two issues are related.

7B status is result of incorrect drive setting, just walk through http://kb.parallels.com/en/5670
 
After re-booting twice: EVERYTHING WORKS!!
Memory and CPU sliders work (1-4 no problem, 5-8 have an asterisk denoting not fully supported, but, hey, four is a whole lot better than 1).

Alas, the same is not true for my iMac installation: both sliders are not accessible and it only sees one core. It does, however, work fine in coherence mode.

All in all, I'm satisfied enough to go ahead and buy another version 4 for my MacPro. The ability to address 256MB of video memory is very important on my MacPro because it has two 30" Apple Cinema monitors. Version 3 would not support them because it only had 64MB of video memory.

But I must say that I agree with so many others: this version was not ready for release considering all of the problems with installation. I have been and am on beta test teams and this one was just not ready. Nevertheless, I'm sure that the current beta team will clean up the installation problems and the other prevalent bugs.
 
Last edited:
Can you be a little more specific? I haven't "changed" anything since Parallels 3. Do I need to modify my boot.ini file? If I do that, I'm willing to bet it won't boot up properly using Boot Camp.

I agree - we need more specifics. The link provided does not really provide a great explanation. Sorry - this is buggy software - I had to pay for a buggy software and trying to find a solution in this forum. This cannot be the quality understanding of Parallels!
 
During the 3.0 to 4.0 upgrade, has anyone had Windows XP (XP Pro SP3 for me) tell you that there has been a significant HW change and Windows needs to re-activate? (Non-boot camp)

Yes, I have run into this with both of my Windows VM's (Home and Pro). One thing that you can try is to make sure the MAC address of the network interface card is the same as it was in PD3. This may or may not work depending upon other hardware changes.

I am very curious as to how many people have been required to re-activate their Windows VM's. I know that for me, the re-activation required a manual upgrade/conversion approach to the VM's and I would have thought this situation would have been run into all the time during beta testing.
 
BSOD 7B: The Parallels team ignores that issue. I have deleted PD4 and run an older version. This is frustrating, but I have never been able to get an answer from Parallels.
 
Is error looking something like that
STOP: 0x0000007B (0xF741B84C,0xC0000034,0x00000000,0x00000000)
INACCESSIBLE_BOOT_DEVICE

Here is a screenshot:
Picture%2023.png
 
Back
Top