Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
SiliconAddict said:
Not a dang thing as far as I can tell. I downloaded and installed the new driver package. Didn't update a single driver. Video: nope, audio: nope, USB: nope, bluetooth: nope, iSight support...heck nope. The brightness stepping issue? Nope. WIFI? Nope.
SiliconAddict said:
There is no reason why Apple would need to update BootCamp for a new Mac. Boot Camp is nothing more then a boot manager/loader.
Thats funny. If Boot Camp is nothing more than a boot manager, why would you check to see if you drivers were updated? Oh, thats right. Boot Camp includes Windows drivers, too. So if a new Mac included say a new chipset or a X1900 or RAID support, Apple would probably want to update Boot Camp.

next said:
omg never thought it would be a general problem. Happens here too and it's quite annoying. It just happens for no reason! But after the plug thing when ou turn xp off or restart it pops a lovely blue screen that stays for... less than a second. I'll have my cell phone near for next time to read the screen.:rolleyes:
Do you other USB devices plugged in especially something that draws more power like a portable hard drive or something? I have a 2.5" HD that I use with my iMac. Sometimes when I plug it in I get a message about a power surge on the USB port or something like that and afterwards my keyboard and mouse won't work until I unplug them and plug them back in. By the way, I don't have this problem on my Gateway laptop.
 
SiliconAddict said:
My biggest fear is that Apple is going to intentionally neuter Windows on the Mac

I don't think they are. I think that the reason BootCamp is missing various key elements is simple economics : if Apple had given us everything we wanted in BootCamp as part of the beta, they'd have been removing a significant incentive for people to upgrade to Leopard.

Tiger is more than good enough for me; unless 10.5 is something truly spectacular, I wouldn't see myself rushing to buy it for any reason other than an all-singing all-dancing BootCamp.
 
topgunn said:
Do you other USB devices plugged in especially something that draws more power like a portable hard drive or something? I have a 2.5" HD that I use with my iMac. Sometimes when I plug it in I get a message about a power surge on the USB port or something like that and afterwards my keyboard and mouse won't work until I unplug them and plug them back in. By the way, I don't have this problem on my Gateway laptop.

hi, no, don't have an external hdd, maybe sometimes it happens with the ipod plugged, but it can happen without it too
 
mrichmon said:
In many (possibly all) of those cases the problem was user error in that the user instructed the Windows installer to either wipe the OS X partition or inadvertantly installed Windows over the top of the OS X partition.

My iMac started booting into windows by default after the install, I could see someone not reading the documentation about holding down option at boot and believing t hat they couldn't get into Mac OSX. The startup disk control panel in my XP is all messed up and doesnt work at all, so if it weren't for option a problem could have ensued...

And in my opinion, my iMac boots windows faster than any windows computer I have ever used, including 2.4gHz+ Pentium 4s.
 
topgunn said:
Thats funny. If Boot Camp is nothing more than a boot manager, why would you check to see if you drivers were updated? Oh, thats right. Boot Camp includes Windows drivers, too. So if a new Mac included say a new chipset or a X1900 or RAID support, Apple would probably want to update Boot Camp.

BootCamp contains a CD image of Windows drivers that BootCamp will burn to a CDR for you. However the only function that BootCamp provides that directly relates to getting Windows installed is repartitioning of the drive.

Driver support using Apple supplied drivers for Windows is minimal at best. There is also no reason why Apple could not or would not simply release an updated CD image for the Windows drivers. Releasing drivers for unannounced hardware is a sure way for Apple to leak their upcoming models and given Apple's historical level of secrecy about new products this is very unlikely.
 
The only difference between Boot Camp 1.0 and Boot Camp 1.0.2 is the wording in the instructions for installing it.Apple did it to help noobs better understand how it's done.This is why the update is a 1.0.2 instead of a 1.1
 
Peace said:
The only difference between Boot Camp 1.0 and Boot Camp 1.0.2 is the wording in the instructions for installing it.Apple did it to help noobs better understand how it's done.This is why the update is a 1.0.2 instead of a 1.1
Thank you Peace.
 
if this actually does fix the fact that the screen saver doesn't start, that'd be great. i haven't noticed the problem with my macbook, but then again i usually close it before it would go to a screen saver. but the intel imac 20" that i use at my office never goes to sleep when running windows and the screen saver never comes on, and i worry about the screen's life.
 
whenpaulsparks said:
if this actually does fix the fact that the screen saver doesn't start, that'd be great. i haven't noticed the problem with my macbook, but then again i usually close it before it would go to a screen saver. but the intel imac 20" that i use at my office never goes to sleep when running windows and the screen saver never comes on, and i worry about the screen's life.


Sorry, I'd edited the wrong post.

The windows application Input Remapper, which help remap keys and right-clicks for Windows on Macs, for whatever reason fixed the broken (on my MBP) screensaver & screen power-off & Active Directory lock-screen GPO. I've not had time to test why or how, but that's all I installed that could have fixed it.
 
screen saver

That's strange that you are having Screen Saver problems (and Sleep mode). I have a MacMini Single Core and both of those features work for me with no problems.

As for the booting of Windows XP. It boots faster then my 2.8Mhz Celeron D. Not to mention some games work better on my Mini as well.

Hugh


whenpaulsparks said:
if this actually does fix the fact that the screen saver doesn't start, that'd be great. i haven't noticed the problem with my macbook, but then again i usually close it before it would go to a screen saver. but the intel imac 20" that i use at my office never goes to sleep when running windows and the screen saver never comes on, and i worry about the screen's life.
 
One thing I noticed since I had to whipe my HDD and get the new bootcamp. When you go to format the Windows side, it no longer allows you to format as FAT, only NTFS.
 
modShade said:
One thing I noticed since I had to whipe my HDD and get the new bootcamp. When you go to format the Windows side, it no longer allows you to format as FAT, only NTFS.

Wow, that's bad if you'd like to read your windows partition from mac os x. Can anyone else confirm this?
 
ironic23 said:
Wow, that's bad if you'd like to read your windows partition from mac os x. Can anyone else confirm this?

If you want to read your Windows partition from OS X then there is not a problem formating the Windows partition as NTFS. OS X can read NTFS without a problem. It is a problem if you want to write to the Windows partition from OS X.

I've just reinstalled Windows on my USB drive without using BootCamp. Before installing Windows I used Disk Utility to partition the drive into two partitions marking the partitions as MS-DOS partitions. During the Windows installation I formatted the install partition as NTFS with the intention of formating the second partition using FAT once I finished the installation of Windows. I installed the Apple drivers that shipped as part of the first release of BootCamp.

When the installation of Windows was complete I found that Windows would only let me format the second partition using NTFS. I found that I could modify the partition table using GParted to set the partition type to FAT32. After that change Windows would give me the option of formating use FAT or using NTFS.
 
Hugh said:
That's strange that you are having Screen Saver problems (and Sleep mode). I have a MacMini Single Core and both of those features work for me with no problems.

This is a problem only with MBPs.
 
modShade said:
One thing I noticed since I had to whipe my HDD and get the new bootcamp. When you go to format the Windows side, it no longer allows you to format as FAT, only NTFS.

The Windows installer will only allow NTFS if installing on partitions over 32GB. This is due to limitations in FAT.

I bet that this is happening here.
 
JQW said:
The Windows installer will only allow NTFS if installing on partitions over 32GB. This is due to limitations in FAT.

I bet that this is happening here.

A limitation in WINDOWS. Linux can format FAT over 32GB and Windows will install correctly onto it.
 
It took you 3:15 to boot up a 2.8Ghz XP box:rolleyes: . It takes about 1:30 seconds on my 600Mhz Celeron XP box.
Nermal said:
I haven't timed my iMac, but it can't be much longer than 15 seconds.

Edit: OK, I had nothing better to do, so I timed it. 35 seconds. That's significantly faster than the 2.8 GHz XP boxes we have at work, which take a good 3-5 minutes. If I remember, I'll time mine tomorrow just to check.

Edit: Finally remembered, it took 3:15.
 
jaxstate said:
It took you 3:15 to boot up a 2.8Ghz XP box:rolleyes: . It takes about 1:30 seconds on my 600Mhz Celeron XP box.

Yeah, the only systems I've seen that take that long to boot Windows are servers. Some of them take FOREVER, and go through trillions of BIOS screens, etc.

But standard hardware running Windows boots really fast. There's no way a normal 2.8GHz Windows system could take 3:15 to boot unless something was drastically wrong.
 
JQW said:
The Windows installer will only allow NTFS if installing on partitions over 32GB. This is due to limitations in FAT.

I bet that this is happening here.

Yep, just realized that. When I first did Bootcamp I gave the windows side 30GB and this time I did 35.

And even though BootCamp may be free, I still paid for Windows XP Pro as well as the computer itself and I've very pleased with the performance.

I actually don't mind booting into Windows over the virtualization until they get to the point where it can run Windows at FULL speed without booting into it.
 
modShade said:
I actually don't mind booting into Windows over the virtualization until they get to the point where it can run Windows at FULL speed without booting into it.

You are my kind of dreamer. I do hope you are right.:)
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.