Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Windows 7 on Bootcamp - Macbook Mid 09 - Desperate!
- Thread starter Vazzyb
- Start date
- Sort by reaction score
kny3twalker
macrumors 65816
Press and hold the option button at bootup. After the chime you should be greeted by the boot menu. Boot into osx, then copy all of your files off the bootcamp partition, not windows or your programs just your work. Then use the disk utility in osx and delete the windows partition and start over. If something is wrong with your windows install, a lot of times it's just easier to reinstall windows than diagnosis.
Timur
macrumors 6502a
Most likely you wont need to copy anything. Just boot into OS X once, reboot into Windows afterwards and the freezing should stop. Windows' Save Mode should work without that trick, but that's much of a help I guess.
If it happens repeatedly then try to reset the NVRAM/PRAM. I had this occuring myself, seemingly something gets mixed up in Mac's Firmware/EFI/BIOS emulation.
If it happens repeatedly then try to reset the NVRAM/PRAM. I had this occuring myself, seemingly something gets mixed up in Mac's Firmware/EFI/BIOS emulation.
start up
hi i loaded windows 7 on my new i mac, i have a problem in start up on boot camp, sometimes it boots into windows and other times it freezes up and have to restart , when this happens a message also comes up saying, "disk read error occurred" in windows. Is there any solutions to this problem, ?? robimac
hi i loaded windows 7 on my new i mac, i have a problem in start up on boot camp, sometimes it boots into windows and other times it freezes up and have to restart , when this happens a message also comes up saying, "disk read error occurred" in windows. Is there any solutions to this problem, ?? robimac
kny3twalker
macrumors 65816
Run some disccheck type tools either in windows or osx, because from your statements it sounds like your harddrive might be failing.
kny3twalker
macrumors 65816
Timur
macrumors 6502a
Do not follow the routine described in the link for running Windows Chkdsk on a Mac!
Instead use the Windows Installation CD, use the repair routines and start the command prompt from there.
The reason is that the CD runs a native Windows enviroment that uses Windows' routines for running Chkdsk/harddisc access. But when you use Chkdsk as described in the link it will run Chkdsk *before* Windows is run in a DOS like enviroment that uses BIOS routines to access the harddrive.
Problem with the latter is that Apple's BIOS emulation is so incredibly slow that it will take hours (literally) to finish a Chkdsk run that otherwise would only takes minutes. It's even so slow that you can see the screen drawing with simple text output. Besides, there are several quirks about Apple's "BIOS" that make it seem rather unreliable, so it's not a good basis for running harddisc repair operations on.
Instead use the Windows Installation CD, use the repair routines and start the command prompt from there.
The reason is that the CD runs a native Windows enviroment that uses Windows' routines for running Chkdsk/harddisc access. But when you use Chkdsk as described in the link it will run Chkdsk *before* Windows is run in a DOS like enviroment that uses BIOS routines to access the harddrive.
Problem with the latter is that Apple's BIOS emulation is so incredibly slow that it will take hours (literally) to finish a Chkdsk run that otherwise would only takes minutes. It's even so slow that you can see the screen drawing with simple text output. Besides, there are several quirks about Apple's "BIOS" that make it seem rather unreliable, so it's not a good basis for running harddisc repair operations on.