 |
 |
Weird BootCamp Partition Failure
|
|
|
|
|
Fresh-Faced Recruit
Join Date: Jul 2007
Status:
Offline
|
|
For months boot camp had worked fine on my computer along with Parallels Desktop connecting to the same partition. Recently though, I have not been able to boot up the Windows partition via holding option at the mac hard boot screen to select the Windows partition. To make things weirder the same partition can still be started up via Parallels Desktop.
When I attempt to actually boot the Windows partition (non-Parallel) I get one of the two scenarios:
1. The screen turns black, pauses for 3 seconds, and restarts to the mac hard boot screen.
2. I get an error involving some weird DLL that already exists where it says it doesn't.
I've tried redoing the boot.ini for windows, but of course that was no help. 
If anyone has heard of a partition created by Boot Camp having this problem before and knows how to fix it please help. 
Thanks,
- MacFever
|
|
|
| |
|
|
|
|
|
|
|
Moderator  Join Date: Oct 2001
Location: San Jose, CA
Status:
Offline
|
|
You may not be shutting down Windows correctly in Parallels. You need to do a true shutdown of Windows from the Start menu (12 years of Windows 95 and that still makes no sense). Then, it should work fine when you switch to booting from the Boot Camp partition. You can't just quit Parallels to do the switch.
Steve
|
|
|
| |
|
|
|
|
|
|
|
Moderator Join Date: Dec 2000
Location: Polwaristan
Status:
Online
|
|
I had a similar problem -- Parallels somehow hosed my Windows boot camp installation. I couldn't get it back on track, so I just started over. Now I have a stand-alone Parallels virtual disk and a stand-alone boot camp partition.
|
|
|
| |
|
|
|
|
|
|
|
Fresh-Faced Recruit
Join Date: Jul 2007
Status:
Offline
|
|
I just noticed I haven't installed the Boot Camp updated drivers so I'm going to do that now. I'll try a restart and if neither of those solve the problem then I'll join the boat Cold Warrior is in and just nuke the partition and start over. I already backed everything up assuming there was no fix for it.
|
|
|
| |
|
|
|
|
|
|
|
Administrator  Join Date: Apr 2001
Location: San Antonio TX USA
Status:
Offline
|
|
It's an unwritten rule that one tool for Windows maintenance is the installation disc-reinstalling is often the best way to fix a problem, and in particular when Windows says it can't find a DLL that YOU can find, it's probably time to "refresh" the install.
ibook_steve, the reason for the structured shutdown is that Windows keeps eleventy-billion files open all the time. These files are as simple as log files or as complex (and the worst offenders) as the Registry files. Starting and stopping Windows is a relatively delicate thing because those files must be properly closed, and in the proper sequence, or the OS can't figure itself out. Not smart from our perspective, but it works...after a fashion, anyway. 
|
|
Glenn -----
OTR/L, MOT, Tx
|
| |
|
|
|
|
|
|
|
Fresh-Faced Recruit
Join Date: Jul 2007
Status:
Offline
|
|
Ok so today after work I got home and with one last attempt tried to solve the problem. I had windows repair the boot.ini, repair the boot registry, and updated the drivers for boot camp. Of course, none of that did anything and Windows had made its ultimate decision to be re-installed. I'm just happy that these things don't happen when I'm on OS X. Thanks for your help and advice everyone!
Oh, and one last thing: A good tip for Mac users using boot camp with windows -- constantly backup files you will want (I'm lucky it crashed the day after I bought a new external HD and backed up).
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
 
|
|
|
Forum Rules
|
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|
|
Top
