I've looked around for a while and can't find a definite answer on this ... if I try to make a Windows 7 partition on my Mac now will it work and be as easy as it was with XP?
Thanks.
Thanks.
Boot Camp 3 drivers will install without a problem.
Comes with Snow Leopard![]()
Okay, thanks. So when I do this I'll need my Snow Leopard disc? Because it's currently on the other side of the country ...![]()
Most of the Vista drivers work fine.OK, I'm somewhat confused. I thought Apple was still in the process of updating Boot Camp for Win 7 but it appears that people are installing 7 through Snow Leopard, which I have. Is that correct?
I've been holding off on installing my copy of Win 7 on my 24" iMac while waiting on the BC update. Should I just go ahead?
I installed Windows 7 Ultimate 64-bit edition on a 1TB drive in my Mac Pro today, and after installing the Boot Camp 3.0 drivers off the Snow Leopard disc, it was able to see my other hard drives with OS X file system partitions on them.
Only thing is, they didn't show up in Win 7 in the order I expected. (I have a drive called "Data 1" and another called "Data 2", but Windows 7 decided to assign the "Data 2" drive as letter F: and the "Data 1" as G
So, knowing how Windows is with its drive letters, I went to the Disk Management program under Administrative Tools, and reassigned the drive letters so they were in the order I wanted. Worked great, UNTIL I rebooted into OS X. That's when I discovered Windows 7 clobbered those partitions. OS X doesn't recognize the drives as having valid partitions on them anymore!
Only way I can see the data on them now is to boot back into Windows 7, where it happily views it all!
Tried running Disk Utility in OS X to fix the drives but it refused to even try, reporting I needed to try to back up any data possible and reformat!?!
This appears to just be a matter of Win 7 modifying an identifier of some sort in the directory table. Anyone know a way to fix this?
I installed Windows 7 Ultimate 64-bit edition on a 1TB drive in my Mac Pro today, and after installing the Boot Camp 3.0 drivers off the Snow Leopard disc, it was able to see my other hard drives with OS X file system partitions on them.
Only thing is, they didn't show up in Win 7 in the order I expected. (I have a drive called "Data 1" and another called "Data 2", but Windows 7 decided to assign the "Data 2" drive as letter F: and the "Data 1" as G
So, knowing how Windows is with its drive letters, I went to the Disk Management program under Administrative Tools, and reassigned the drive letters so they were in the order I wanted. Worked great, UNTIL I rebooted into OS X. That's when I discovered Windows 7 clobbered those partitions. OS X doesn't recognize the drives as having valid partitions on them anymore!
Only way I can see the data on them now is to boot back into Windows 7, where it happily views it all!
Tried running Disk Utility in OS X to fix the drives but it refused to even try, reporting I needed to try to back up any data possible and reformat!?!
This appears to just be a matter of Win 7 modifying an identifier of some sort in the directory table. Anyone know a way to fix this?
It's not a major problem, it's an user error. Windows will assign Drive letters to the hard drives in your Mac Pro. This is because there is "Read Only" HFS support in the newest Boot Camp Drivers. However, if you were to change the Drive Letters, it actually alters the drive information, screwing up on the OSX side.
I have C Drive for Windows HD, D Drive for Macintosh HD, then E Drive for external DVD+/-RW drive and F for Daemon tools. I don't dare mess with D drive whatsoever.
Wrong. While the user should not have made the drive letter change; one of the first things we tell the programmers is to (within reason) make sure users can't do what they shouldn't.
I don't think it is unreasonable to expect a few people to try this and Apple should make certain they cannot. Adding functionality that creates the potential for data loss is unacceptable, period!
This appears to just be a matter of Win 7 modifying an identifier of some sort in the directory table. Anyone know a way to fix this?
Wrong. While the user should not have made the drive letter change; one of the first things we tell the programmers is to (within reason) make sure users can't do what they shouldn't.
I don't think it is unreasonable to expect a few people to try this and Apple should make certain they cannot. Adding functionality that creates the potential for data loss is unacceptable, period!
Cheers,
Just confirming/summing up the thread: So if I attempt to install Windows 7 on my iMac now - using the old Instruction Manual and Leopard discs (not Snow Leopard), everything should be simple and work fine?
Just confirming/summing up the thread: So if I attempt to install Windows 7 on my iMac now - using the old Instruction Manual and Leopard discs (not Snow Leopard), everything should be simple and work fine?
Vista and 7 share the same driver model (Windows Driver Model 1.7). In theory, a device driver written for Vista should work in 7.
However, this often isn't the case, since many drivers are poorly engineered, or rely on the minutiae of Vista that don't apply in 7.
If you have a recent Mac, you'd see this pretty quickly trying to get by with Boot Camp 3.0 and 64-bit Windows 7
So, Apple IS going to update Boot Camp for 7 support, and they originally claimed it would be before the end of the year. Time's running out on that promise though.
No. The Snow Leopard disc has read-only drivers for HFS volumes, which the Leopard version lacks. That's probably not the only difference, though.Do the Leopard (2.1) and Snow Leopard (3.0) discs have the same Drivers?