Does version 3.0 address the heat/fan problem that a lot of people (including myself) are having when running Windows on the unibody machines?
Does version 3.0 address the heat/fan problem that a lot of people (including myself) are having when running Windows on the unibody machines?
hi runebinder,
i love you ...
after reading your thread i downloaded BC 3.0 to try it with my new unibody with intel ssd and WIN7 RC1 32bit.
so in one word: PERFECT !
i burned a iso dvd (bc3.0), started win7 and voila: ALL apple drivers are ok !
(just click and install)
again: thank you !
here it is:
http://www.sumotorrent.com/en/detai...3.0 Drivers build10a314 with HSF support.html
On my Windows 7 64-bit boot camp 3.0, I can access Mac drives. One thing I noticed though, for the main Mac OS X partition, I can access the Users > Name folder, but when I open that folder, nothing exists in that folder (even though there are things in there). Why is that?
On my Windows 7 64-bit boot camp 3.0, I can access Mac drives. One thing I noticed though, for the main Mac OS X partition, I can access the Users > Name folder, but when I open that folder, nothing exists in that folder (even though there are things in there). Why is that?
On my Windows 7 64-bit boot camp 3.0, I can access Mac drives. One thing I noticed though, for the main Mac OS X partition, I can access the Users > Name folder, but when I open that folder, nothing exists in that folder (even though there are things in there). Why is that?
Anyone know if the later builds have updated Bootcamp 3.0 drivers?
+1
I'm also curious if Boot Camp says anywhere that it officially supports Windows 7. I mean I know the Vista drivers would work just fine under 7, but still curious.
@runebinder
i tried your method sadly it gets stuck at the installation saying "KeyAgent" could not be started, check your rights to start system services"
(not 100% right error text because I had to translate)
any help would be great
I installed the final version of windows 7 ultimate 64 bit on my Early 2008 MacBook4,1.
When I installed all this and replaced the files with the patched ones and i run setup, it says: BootCamp x64 is not supported on this computer model.
Is this because i have a (non-pro) MacBook4,1 that doesn't support 64-bit?
Nice to see people using my script!BootCamp.exe works using "BootCampED" version to avoid high Latency <=> Fn Key (brightness, sound, etc.)
This might be another discrepancy of Windows versions. I noticed that the Release CANDIDATE and Beta could be made to work with all Bootcamp driver (2.1), but the final Release could not be made to work with function keys and keyboard-light. So whatever Microsoft changed it affects the (still Vista) Apple driver.=> Bootcamp is running (process is running), but the Fn Keys are not operationnal !!!
You could try installing a mixure of the new 2.2 driver and the 3.0 beta, maybe that will fix the issues. But given that Apple announced official W7 drivers to arrive in december (afaik) it may not be worth the effort.If someone has an answer for my bootcamp.exe process issue (Fn Key not opertionnal after new hardware installation), I will be very Cool
Nice to see people using my script!
I never published the version that tries to automatically remove the Bootcamp icon from the tray, because that doesn't work 100%. With the first Beta of Windows 7 this icon would vanish by itself once the Bootcamp.exe (kbgmgr.exe) process was killed, the RC didn't do that anymore. How does the final Release handle the tray-icon?
This might be another discrepancy of Windows versions. I noticed that the Release CANDIDATE and Beta could be made to work with all Bootcamp driver (2.1), but the final Release could not be made to work with function keys and keyboard-light. So whatever Microsoft changed it affects the (still Vista) Apple driver.
You could try installing a mixure of the new 2.2 driver and the 3.0 beta, maybe that will fix the issues. But given that Apple announced official W7 drivers to arrive in december (afaik) it may not be worth the effort.