As far as I know from reports about the Bootcamp 3.0 beta KBDMGR.EXE was renamed into BOOTCAMP.EXE. I will not buy Snow Leopard before next week so I cannot check myself yet.

I put in a call to Applecare, to find out just what gets installed where with the Boot Camp 3.0 installation.  It was strongly recommended to me to run with the BC 3.0 package if I'm running Snow Leopard on my other partition, but as I mentioned in the posts above, I've been holding off because of the DPC Latencies I found with the new drivers.  However, because I've encountered my MacBook Pro (late 2007) running hotter than I remember it doing - mostly due to graphics processing (NVDIA hardware), I was also trying to learn whether the Boot Camp 3.0 installation would provide any improvement with the temperature regulation.  Applecare was careful to not come right out and say anything definitive about this, but again, it was strongly hinted that upgrading to 3.0 would allow things to run better, and possibly, cooler.  I should also mention that I am running Windows XP Pro SP3.

I was able to find out that kbdmgr.exe has been renamed to APPLEOSSmgr.exe, so hopefully disabling this executable will give the same reduction in DPCs as was found with what we all wound up doing with BC 2 and 2.1.  Applecare was quick to point out that disabling this puts you outside of what they're willing to support on the Windows side..., you do so at your own risk, yadda, yadda....

Other information about what drivers come in the 3.0 package can be found here:
http://support.apple.com/kb/HT3777
but I'll quote the pertinent information:

Which drivers are included on the Mac OS X 10.6 (Snow Leopard) DVD?

The Mac OS X 10.6 (Snow Leopard) DVD contains the following Mac drivers for Windows:

Apple Bluetooth
Apple Keyboard Support
Apple Remote Driver
Apple Trackpad
Atheros 802.11 Wireless
ATI Graphics
Boot Camp control panel for Microsoft Windows
Boot Camp System Task Notification item (System Tray)
Broadcom Wireless
Intel Chipset Software
Intel Integrated Graphics
iSight Camera
Marvel Yukon Ethernet
nVidia Graphics
Cirrus Logic Audio
Realtek Audio
SigmaTel Audio
Startup Disk control panel for Microsoft Windows

and of course the Instructions for setting up Boot Camp 3.0 on an Intel Mac can be found here:
http://manuals.info.apple.com/en/Boot_C … -Setup.pdf

Timur,

Just wondering if you've had a chance to look at Boot Camp 3.0 yet, and what the verdict is about BOOTCAMP.EXE and/or APPLEOSSmgr.exe?  Have you had a chance to update your script?

On Macbooks (Pro) the Bootcamp 3 drivers behave the same as the 2.1 ones. So all of my advices about how to get low DPCs are still valid.

Interestingly though the BOOTCAMP.EXE does *not* cause any problems on the new Imacs even when it is the same drivers. So the combination of Macbook and driver is the culprit.

Furthermore the "Atheros" WLAN drivers on Imacs cause a spike every 60 seconds which can only be changed to every 10 minutes via device-manager. Using the driver from Microsoft Update Catalog does not help with the Atheros.

The "Broadcom" WLAN drivers for Macbook (Pro) from Microsoft Update Catalog are still the best choice even while the Bootcamp 3 ones are alot better than the older ones and seem to be more recent the the MS ones.

NVidia drivers issues for 9600M GT are still not fixed, but there are no such problems for the 9400M GT in the IMac. I had no chance to check any Macbook NON-Pro about that.

Go to the "Tips & Tricks" section and read my post about how to get low DPCs on Macbook Pro. It's probably a problem with graphics.

This is not the whole truth.

Actually i have bigger problems with my MacBook. The values seem to be good but i have huge latency when using firewire.

I checked the registry for sidspeed values. Seems to be fine.

There's something about the laptops...

I find that my fully tweaked XP SP3 installation can get down to between 5 and 12 micro-seconds on my iMac, when I unplug all the non-essential USB connections (hub, printers, SD card reader).  On my MacBook Pro (late 2007), the lowest I can get is somewhere between 80 and 120 micro-seconds.  Both machines have all wireless communications (including Bluetooth) disabled.  There are, however, differences in the graphics hardware (NVDIA 7600 GT in the iMac, 8600 GT in the MBP), and of course, there is the more complex powering control because of the battery in the laptop.

There are times I wish I had gotten the smallest iMac instead of the MBP for portable/location work.  One of those and an iLugger case are pretty portable.

DPC times of around 100 us are already perfect, anything lower is just a bonus that wont have any much of an effect. In fact, anything upto 300 us should not be noticeable as long as your audio application uses a high enough priority.

This is because according you can reach in Windows seems to be 1 ms (=1000 us) and you have to be kind of unlucky to have other drivers/applications cause DPC just the moment when the audio driver transfers the next buffer. Because the audio buffer is transfered at a regular interval while other drivers/applications may issue DPCs in irregular intervals it can happen though.

DPCs have higher priority than any software process/thread (even realtime ones), but keeping other processes from accessing drivers/hardware while the audio application is busy also keeps them from interfering with the audio driver.