Parallels will not shutdown Vista properly...HELP!!!

J

jhiginbotham

Member
I've had this problem ever since I've upgraded to build 5600 and did this because I couldn't use the build previously because Vista was winning about activation so I was stuck using vista in bootcamp. I saw that this issue was addressed but now I can't use bootcamp since parallels will not shut down Vista properly. I've searched this forum and googled the problem and have not found an answer to it. Here is the scenerio, I have a mac bookpro and use parallels for visual studio development. When I'm at work I boot straight into bootcamp so that I have maximum memmory and cpu power. When I'm at home I boot into parallels just to do minor VS things. At work I need the full machine and now I'm stuck in using Vista in parallels until this issue gets resolved. Prior to Vista going to SP1 status everything worked great as long as Parallels shutdown properly. Then SP1 came out and all sorts of problems with Parallels started, mainly activation problems, and yes I did the update in BC. I just waited for the update to parallels to fix this issue. It came out and now I'm stuck using parallels until it can be resolved. Here is what happens, I start my parallels through a bootcamp partition (Vista Ultimate) and do what I need. Go to Start -> Shutdown, like all good boys and girls should do and it does the shutdown process and when it ends, followed by an error message that states:


Boot Camp Windows XP was shut down abnormally while it was used via Parallels Desktop. Please boot into Boot Camp via Parallels Desktop once again and shut down Windows XP normally.

So I was confused that it was stating XP when in fact I'm using Vista. Either way I stated parallels again and when through the process of shuting down and got the error again. Well obviously if I start my BC partition it will not load, and so I tried and I'm right. If I go through safemode It hangs on the crcdisk.sys which I've searched here and googled and have not found any definative clear answers to this. So bottom line, I need a real answer to what is going on. This is really cutting into my productivity at work....Any help will be greatly appreciated. Thanks
 
Sort by date Sort by votes
Thank you,
We found the issue, when Windows partition is located far then first 128 GB, and developers are working on it
As for now I recommend following, try to install Windows in the first 128 gb.
Anyway, please just give a call to support and tell to assign ticket to John, I will submit situation to developers, and in one of upcoming builds we will fix this
 
Upvote 0 Downvote
What number should I call to do this?

For now I'll just live with it until its fixed, I really am not in a position to be reinstalling windows every five minutes, it works in bootcamp for now, I have work to get done.
 
Upvote 0 Downvote
John,

Hmmmm.... I don't think that is the exact problem. I am having this issue on my MB Pro with only a 120 GB drive installed. That drive has only 2 partitions, with the first being an 80GB Leopard partition and the second being my Bootcamp Vista partition. I'm attaching screenshots from Disk Utility showing the partitions and sizes. My Vista partition is disk0s3. Couldn't figure out how to show all the information in 1 screenshot.

I am working on sending the rest of the data you requested. And I have a ticket open on this issue -- #534351.

Thanks,
Spencer
 

Attachments

  • Partitions.jpg
    Partitions.jpg
    12.3 KB · Views: 3
  • Macintosh HD Partition.jpg
    Macintosh HD Partition.jpg
    12.3 KB · Views: 2
  • Vista Partition.jpg
    Vista Partition.jpg
    12.2 KB · Views: 3
Upvote 0 Downvote
Here is my disk listing. As you can see from this, my Windows partition falls after 80 GB, well below the 128 GB limit you mentioned. I have no USB devices attached.

Spencer-Swifts-Computer(1)$ diskutil list
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *111.8 Gi disk0
1: EFI 200.0 Mi disk0s1
2: Apple_HFS Macintosh HD 80.0 Gi disk0s2
3: Microsoft Basic Data 31.5 Gi disk0s3
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: Apple_partition_scheme *279.5 Gi disk1
1: Apple_partition_map 31.5 Ki disk1s1
2: Apple_HFS Storage B 57.8 Gi disk1s3
3: Apple_HFS OS 10.4 Clean 38.2 Gi disk1s5
4: Apple_HFS Storage 91.5 Gi disk1s7
5: Apple_HFS Drive D 91.5 Gi disk1s9
 
Upvote 0 Downvote
I'm just glad to know that I'm not the only yutz with this problem... :) hopefully we can find our simularity and solve the problem because this is getting annoying, I'm able to use both parallels and bootcamp with the detect HAL turned on but getting the annoying message is getting old...I guess it doesn't really hurt anything, but I can't help to think that if I'm getting the message what else is wrong.
 
Upvote 0 Downvote
Right, everything seems to work fine by just ignoring the message. But it seems to point at a real underlying issue.

And I've never done well just "leaving sleeping dogs lie".
 
Upvote 0 Downvote
You must log in or register to reply here.
Back
Top