Note: ticket submitted on this as I think it is a CXG/Wine issue related to the recent 10.6.4 update , not PyLotRO.
CodeWeavers Ticket System wrote:
CX Version: 9.0.0-mac
Application: LOTRO
Operating System: Mac OS X 10.6 (Snow Leopard)
Under Mac OSX latest update (June, 2010) 10.6.4 !!!
Updated bullroarer (test server) client with current beta version via PyLotRO with no apparent problem.
Launched PyLotRO and successfully logged in. PyLotRO (apparently) successfully passed control to Turbine client....
client went to black window, and then aborted with the following error:
6/18/10 9:16:30 PM [0x0-0x140140].com.codeweavers.CrossOverGamesHelper.Bullroarer.PyLotRO/ .PyLotRO[2555] wine: Call from 0x7b828395 to unimplemented function msvcr71.dll._set_purecall_handler, aborting
The above is the only error in the System Log. PyLotRO continues to run successfully; the X-windows created for PyLotRO continue to exist as they would for a normal execution. Only the window for the actual game execution is created, goes black, then closes.
This configuration, runs LOTRO normally. The Bullroarer client (public test server) is installed in the same bottle. It is updated for each different version of LOTRO for testing prior to public release. This is the first I've had a problem with this configuration.
..... [ 20 June]
Additional/correction information.... Bullroarer client and normal LOTRO client are in different bottles. Both were configured the same.
With the Bullroarer client, If I turn off Vertex Shader Support (set to none) and unchecked "Allow Pixel Shader" the two in-game splash screens load and the game begins to load and check for client status. At this point, the Turbine client reports "unable to patch."
This implies that despite the fact that the PyLotRO client has (apparently) successfully patched the Bullroarer client the Bullroarer client is now doing some sort of additional check prior to switching to active game play.(At this point the PC Client would be going through the "update" check screens.)
(Note in PyLotRO, the "Hi-Res Graphics" option is disabled, but this had no effect.)
PyLotRO patching now simply reports "finished" with any subsequent attempts to patch. (The first major patch effort DID run for a significant amount of time and apparently patched things normally.)