Anyone using Orpheus w/MPB 2.3GHz in XP Pro?

[sonare]

I have a MBP 2.33GHz running XP Pro in boot camp. The FW chipset is TI. If anyone has this EXACT machine and is using Prism Orpheus in XP Pro, please email me off-list at: richmays AT comcast DOT net

Thanks!

Rich

[ISedlacek]

Hi Rich, I don't have exactly the same MBP, not even Orpheus (but Weiss), but if you are facing some problems, look here, maybe you would find something helpful there (as I did), if not, no problem )

"We have seen a number of issues when using Boot Camp on Mac hardware.

High DPC latencies
Hotfixes from Microsoft should be installed
Incompatibilities with the LSI chipset.


DPC

The boot camp drivers and utilities introduce extreme DPC latencies,
specifically the Keyboard Manager (kbdmgr process) and the WiFi drivers.

When using time-sensitive software and drivers such as with audio
recording, stop the kbdmgr process and disable the WiFi adapter.


Hotfix

Macintosh computers often have an S800 1394B FireWire interface, and the
Microsoft drivers do not handle this correctly without installing a
hotfix (SP2) or making a registry change (SP3). The result without this
is that the driver always uses the interface at the S100 speed, which is
not adequate for high channel-count audio applications.

Windows XP SP2:

- Install the hotfix mentioned in the linked article below. If you add
another OHCI card later you must either re-run the hotfix or manually
fix the SidSpeed field for the new adapter. The first time you run the
hot-fix it will actually update the drivers as well, which fixes other
problems.

XP SP3:

- The SP2 hotfix will not run on SP3, and actually on SP3 the OHCI
drivers are fine. You do however still need to add the SidSpeed manually
if you are using an OHCI card based on a 1394b chip. The article below
explains where to add the registry entry.


See this article for details:
When using 1394 audio devices, users may experience "low resource" "device timeout" or other errors.

After you install the Windows XP SP2update, if you add a host controller for a new 1394 device to your computer, you must add or modify the SidSpeed entry in the Windows registry for the new 1394 host controller.

The hotfix: Performance of 1394 devices may decrease after you install Windows XP Service Pack 2 fixes the same problem on XP SP2 but the problem was reintroduced in SP3.

Note: Microsoft has assured us that they are working on a hotfix for this issue in SP3, but has not released it yet. Please check the Microsoft support website in case it has been released since this article was posted.

Otherwise, SP3 users can follow the instructions for manually changing the relevant registry setting in the KB885222 article above.



Incompatibilities

Some Apple computers, particularly the new MacBook Pro (from the 2nd
half of 2008) include an LSI (Agere) chipset which is not compatible
with our drivers:

Currently, the only workaround is to use an ExpressCard not based on the
LSI chip set. Like this one (http://www.byteccusa.com/product/xP-car ...
t-ecFW.htm)
"

[sonare]

This applies to all MBP/Bootcamp users:

I am very happy to report that Andy Saul at Prism was able to determine that my KB885222 hotfix had NOT installed properly, which prevented the Orpheus driver package from installing correctly. If you locate the KB855222.log file in the system folder and open the log it will tell you if KB885222 installation did not complete. Apart from this log it will look like it was successful.

Uninstall and run the KB855222 hotfix again and check the installer log in the KB855222.log file.

This is GREAT news for those who wish to use Orpheus with a Windows DAW!!

Rich

[sonare]

This states in an easier way what I was trying to say above:

Apply KB855222 before installing Orpheus drivers.

If you have attempted & failed to install Orpheus, uninstall it before re-applying the KB855222 hotfix. Then reinstall Orpheus control panel / drivers.

If the Orpheus installation still hasn’t worked, check C:\Windows\KB855222.log. Search for “KB885222 installation did not complete.” If this is found, uninstall both KB85522 & Orpheus drivers, before reinstalling KB85522 first followed by Orpheus.

Rich