1.
The ExpressCard Slot cannot be used with bootcamped Windows Vista at all!
There is no workaround that I know about for this problem.
2. Using a (JMicron based) eSATA ExpressCard
leads to data corruption and crashing on OS X eventhough the build-in OS X AHCI drivers are used.
3. On OS X the unbuild Broadcom
WLAN does not deliver the advertised N-standard rates of upto 300 mb/s but only upto 130 mb/s (upto around 150 mb/s when using the A band).
On bootcamped Windows the same applies, but a new Broadcom driver downloadable only from Microsoft Update Catalog finally allows the full 300 mb/s bandwidth with my N-standard router.
4. When using the 9600M GT on OS X the Macbook Pro will
draw about 5W more power after waking it up from Sleep.
This can only be "solved" by either restarting the computer or by switching back and forth to the 9400M GT.
5. On OS X (10.5.7)
Software Update runs everytime I log in, scanning my HD and using CPU load and thus unnecessarily slowing down the boot-up process.
Furthermore the
Software Update preference pane will always switch back to "weekly" updates regardless of what you setup there and it will even turn back on when you disabled Software Update either via preference pane or via Terminal.
6. The Macbook Pro draws over 1W power when in Sleep mode on OS X and upto over 2W power when in Sleep mode on Windows. That means
the battery is drawn out of power within 25 - 50 hours in Sleep mode.
7. When using bootcamped Windows the
Apple KBDMGR.EXE driver drags down all other drivers and especially leads to audio-dropouts (high DPC Latencies and other quirks caused by KBDMGR.EXE).
8. When using bootcamped Windows XP the 9600M GT/Nvidia driver shipped with Bootcamp (or downloaded via NVidia)
does not dynamically change the GPU's clock-rate but keeps the GPU running at maximum clock-rate and voltage permanently.
9. When using bootcamped Windows Vista the 9600M GT/NVidia drivers
does dynamically change the GPU's clock-rate, but on it's lowest performance level "Standard 2D" the
GPU driver drags down all other driver especially leading to Audio dropouts (high DPC Latencies caused by GPU driver).
Furthermore the either the dynamic switching
leads to the whole system freezing sporadically.
Manually setting the GPU's performance level to a fixed level ("Low Power 3D" or "Performance 3D") via Rivatuner seems to be a workaround, but then the GPU keeps running at higher clock-rate and voltage and thus wattage and temperature.
10. Using a (TI based) Firewire Expresscard
leads to higher CPU load and sporadic freezing on OS X eventhough the build-in OS X Firewire drivers are used.
11. The build-in LSI/Agere
Firewire 800 port cannot be used with certain FW Audio interfaces (RME Fireface 400) without putting a hub/repeater in between.
According to web-sources this is a known issue of the chipset and finally has been resolved by LSI/Agere with a new chipset revision. Apple
knows about the issue but still uses a faulty chipset. On older MB/MBPs this reportedly only caused problems with the FW400 port, on unibody MBPs the only FW800 port fails to deliver.
12. On bootcamped Windows
audio-output only delivers bass to the right side. That does not mean that the bass is coming from the right side (where the bass speaker is located inside the chassis), but any sound played to the left speaker (like balancing the stereo output all left) does not trigger the bass speaker at all.
13. After exchanging the harddrive of my MBP (came originally with a Hitachi 250 gb / 7200 rpm drive) I noticed that the new
HD does not seem to ever park its heads via the MBP's free-fall sensor.
Furthermore I noticed that the original Hitachi drive comes with a free-fall sensor of its own (it audibly clicks/parks the heads even when being used in an external FW/USB/eSATA case).
Additionally the new HD (Hitachi 500 gb / 5400 rpm) goes into Idle (clicking of heads parking and drive spinning slightly up and down) every few seconds on OS X (not on Windows). I could workaround that by using a downloadable utility called HDAPM and setting the drive's power-managment to Maximum with every startup of OS X.
There you go, over a dozend issues I'd like to get some technical support for.
