Re: I need consultation on running WINE on the Mac

2012-10-16 Thread Joshua Root 
On 2012-10-17 05:40 , William H. Magill wrote:
> 
> On Oct 16, 2012, at 7:00 AM, Joshua Root  wrote:
> 
>> After installing wine-crossover, all you should need to run is (all one
>> line, ignore any line breaks inserted by email software):
>>
>> WINEPREFIX="/Users//Library/Application
>> Support/CrossOver/Bottles/Lord of the Rings Online" wine
>> ~/Library/Application\ Support/CrossOver/Bottles/Lord\ of\ the\ Rings\
>> Online/drive_c/Program\ Files/PyLotRO/pylotro.exe
> 
> Hmmm... seems to partially work...  Keep in mind that I have only ever used 
> Crossover, and never "raw WINE." 
> I did install wine-devel, apparently successfully, which I then uninstalled.
> 
>> uninstalled wine-devel
>> sudo port install wine-crossover
>>  "No broken files found."
> 
>> I have multiple bottles, so I simply modified the paths as necessary.
> 
> WINEPREFIX="/Users/magill/Library/Application 
> Support/CrossOver/Bottles/LOTRO-4" wine ~/Library/Application\ 
> Support/CrossOver/Bottles/LOTRO-4/drive_c/Program\ Files/PyLotRO/pylotro.exe
> 
> fixme:heap:HeapSetInformation 0x0 1 0x0 0
> fixme:process:SetProcessDEPPolicy (1): stub
> fixme:heap:HeapSetInformation 0x0 1 0x0 0
> err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make 
> sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in 
> the winbind package of your distribution.
> Application tried to create a window, but no driver could be loaded.
> Make sure that your X server is running and that $DISPLAY is set correctly.
> err:systray:initialize_systray Could not create tray window
> Application tried to create a window, but no driver could be loaded.
> Make sure that your X server is running and that $DISPLAY is set correctly.
> QEventDispatcher: Failed to create QEventDispatcherWin32 internal window: 1
> 
> fixme:system:SetProcessDPIAware stub!
> err:module:import_dll Library QtSvg4.dll (which is needed by L"C:\\Program 
> Files\\PyLotRO\\qt4_plugins\\iconengines\\qsvgicon4.dll") not found
> err:module:import_dll Library QtSvg4.dll (which is needed by L"C:\\Program 
> Files\\PyLotRO\\qt4_plugins\\imageformats\\qsvg4.dll") not found
> QWidget::create: Failed to create window (Invalid window handle.)
> err:module:import_dll Library QtSvg4.dll (which is needed by L"C:\\Program 
> Files\\PyLotRO\\qt4_plugins\\iconengines\\qsvgicon4.dll") not found
> err:module:import_dll Library QtSvg4.dll (which is needed by L"C:\\Program 
> Files\\PyLotRO\\qt4_plugins\\iconengines\\qsvgicon4.dll") not found
> QWidget::create: Failed to create window ()
> wine: Unhandled page fault on read access to 0x0010 at address 0x6514382d 
> (thread 0009), starting debugger...
> Application tried to create a window, but no driver could be loaded.
> Make sure that your X server is running and that $DISPLAY is set correctly.
> Unhandled exception: page fault on read access to 0x0010 in 32-bit code 
> (0x6514382d).
> Register dump:
>  CS:001b SS:0023 DS:0023 ES:0023 FS:1007 GS:000f
>  EIP:6514382d ESP:0032f0c8 EBP:0032f0d8 EFLAGS:00210246(  R- --  I  Z- -P- )
>  EAX:00154ae0 EBX: ECX:00154ae0 EDX:
>  ESI:001548b8 EDI:
> Stack dump:
> ...
> Threads:
> process  tid  prio (all id:s are in hex)
> 0008 (D) C:\Program Files\PyLotRO\pylotro.exe
>   00280
>   00090 <==
> 
> 
>  Correct, I have not installed X11, and therefore no X server. However, I 
> thought PyLotRO bypassed that issue by using Python.

PyLotRO uses the PyQt bindings, but since it's built as a Windows app,
Qt uses Windows API calls, which are implemented by wine using X11.
CrossOver runs its own internal X server. With MacPorts, you'll need
either XQuartz or the xorg-server port.

- Josh
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: I need consultation on running WINE on the Mac

2012-10-16 Thread William H. Magill 

On Oct 16, 2012, at 7:00 AM, Joshua Root  wrote:

>> I know this is not a MacPorts issue, so please direct this to somewhere that 
>> makes sense.
>> 
>> Basically, I'm a total newbee when it comes to RAW WINE. I've historically 
>> used Codeweavers Crossover which is Wine 1.4.1
>> Which is packaged to run quite nicely under Mountain Lion (10.8.2)
>> 
>> I play LOTRO, which just did a major upgrade, and therefore no longer runs 
>> under 1.4.1
>> 
>> WINEhq has a fix which requires WINE 1.1.15. 
>> However, the folks there are al LINUX types.
>> 
>> SO. I just installed MacPorts wine-dev 1.5.15 and now I need to do two 
>> things. (That I know of.)
>> 1- Find out how to apply the patch (which I believe is a classic diff 
>> file)-- I have no idea how badly that will break the MacPorts installation.
> 
> I've just applied it to the wine-crossover port. Seems to work fine.
> 
>> 2- Find out how to configure "raw WINE"  on the mac. In particular how to 
>> point it to the existing Crossover WINE Bottles.
>> 
>> Pointers to appropriate OSX oriented instructions are desired.
>> Any help is greatly appreciated.
> 
> After installing wine-crossover, all you should need to run is (all one
> line, ignore any line breaks inserted by email software):
> 
> WINEPREFIX="/Users//Library/Application
> Support/CrossOver/Bottles/Lord of the Rings Online" wine
> ~/Library/Application\ Support/CrossOver/Bottles/Lord\ of\ the\ Rings\
> Online/drive_c/Program\ Files/PyLotRO/pylotro.exe

Hmmm... seems to partially work...  Keep in mind that I have only ever used 
Crossover, and never "raw WINE." 
I did install wine-devel, apparently successfully, which I then uninstalled.

>uninstalled wine-devel
>sudo port install wine-crossover
>   "No broken files found."

>I have multiple bottles, so I simply modified the paths as necessary.

WINEPREFIX="/Users/magill/Library/Application 
Support/CrossOver/Bottles/LOTRO-4" wine ~/Library/Application\ 
Support/CrossOver/Bottles/LOTRO-4/drive_c/Program\ Files/PyLotRO/pylotro.exe

fixme:heap:HeapSetInformation 0x0 1 0x0 0
fixme:process:SetProcessDEPPolicy (1): stub
fixme:heap:HeapSetInformation 0x0 1 0x0 0
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make 
sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the 
winbind package of your distribution.
Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set correctly.
err:systray:initialize_systray Could not create tray window
Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set correctly.
QEventDispatcher: Failed to create QEventDispatcherWin32 internal window: 1

fixme:system:SetProcessDPIAware stub!
err:module:import_dll Library QtSvg4.dll (which is needed by L"C:\\Program 
Files\\PyLotRO\\qt4_plugins\\iconengines\\qsvgicon4.dll") not found
err:module:import_dll Library QtSvg4.dll (which is needed by L"C:\\Program 
Files\\PyLotRO\\qt4_plugins\\imageformats\\qsvg4.dll") not found
QWidget::create: Failed to create window (Invalid window handle.)
err:module:import_dll Library QtSvg4.dll (which is needed by L"C:\\Program 
Files\\PyLotRO\\qt4_plugins\\iconengines\\qsvgicon4.dll") not found
err:module:import_dll Library QtSvg4.dll (which is needed by L"C:\\Program 
Files\\PyLotRO\\qt4_plugins\\iconengines\\qsvgicon4.dll") not found
QWidget::create: Failed to create window ()
wine: Unhandled page fault on read access to 0x0010 at address 0x6514382d 
(thread 0009), starting debugger...
Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set correctly.
Unhandled exception: page fault on read access to 0x0010 in 32-bit code 
(0x6514382d).
Register dump:
 CS:001b SS:0023 DS:0023 ES:0023 FS:1007 GS:000f
 EIP:6514382d ESP:0032f0c8 EBP:0032f0d8 EFLAGS:00210246(  R- --  I  Z- -P- )
 EAX:00154ae0 EBX: ECX:00154ae0 EDX:
 ESI:001548b8 EDI:
Stack dump:
...
Threads:
process  tid  prio (all id:s are in hex)
0008 (D) C:\Program Files\PyLotRO\pylotro.exe
00280
00090 <==


 Correct, I have not installed X11, and therefore no X server. However, I 
thought PyLotRO bypassed that issue by using Python.


T.T.F.N.
William H. Magill
mag...@mcgillsociety.org
mag...@mac.com
whmag...@gmail.com





___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: port selfupdate incredibly slow

2012-10-16 Thread cowwoc 

 I was estimating. I just checked ports.tar and it's 54MB. But 
again, the point is you could compare the timestamp of a marker file to 
last-modified timestamp of the tar and the comparison would be 
instantaneous.

Gili

On 16/10/2012 9:05 AM, Ryan Schmidt-24 [via Mac OS Forge] wrote:
>
> On Oct 15, 2012, at 18:19, cowwoc wrote:
>
> > You're right. It's writing an awful lot of data. Why is that? 25 
> seconds times an average of 10MB/s (which is a conservative 
> estimate)... it's writing out around 250MB.
>
> That seems large to me. I haven't looked at the ports.tar file on the 
> rsync server, but the ports.tar.gz you can get from our web site [1] 
> is 21MB, it decompresses to a 123MB ports.tar file, which extracts to 
> 149MB of files. So the ports.tar you got seems to be twice as large as 
> it should be?
>
>
> [1] https://trac.macports.org/wiki/howto/PortTreeTarball
>
>
> ___
> macports-users mailing list
> [hidden email] 
> http://lists.macosforge.org/mailman/listinfo/macports-users
>
>
> 
> If you reply to this email, your message will be added to the 
> discussion below:
> http://mac-os-forge.2317878.n4.nabble.com/port-selfupdate-incredibly-slow-tp117503p197044.html
>  
>
> To unsubscribe from port selfupdate incredibly slow, click here 
> .
> NAML 
> 
>  
>





--
View this message in context: 
http://mac-os-forge.2317878.n4.nabble.com/port-selfupdate-incredibly-slow-tp117503p197057.html
Sent from the MacPorts - Users mailing list archive at Nabble.com.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: port selfupdate incredibly slow

2012-10-16 Thread Ryan Schmidt 

On Oct 15, 2012, at 18:19, cowwoc wrote:

> You're right. It's writing an awful lot of data. Why is that? 25 seconds 
> times an average of 10MB/s (which is a conservative estimate)... it's writing 
> out around 250MB.

That seems large to me. I haven't looked at the ports.tar file on the rsync 
server, but the ports.tar.gz you can get from our web site [1] is 21MB, it 
decompresses to a 123MB ports.tar file, which extracts to 149MB of files. So 
the ports.tar you got seems to be twice as large as it should be?


[1] https://trac.macports.org/wiki/howto/PortTreeTarball


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: I need consultation on running WINE on the Mac

2012-10-16 Thread Joshua Root 
On 2012-10-16 22:33 , Ryan Schmidt wrote:
> 
> On Oct 16, 2012, at 06:00, Joshua Root wrote:
> 
>> I've just applied it to the wine-crossover port. Seems to work fine.
> 
> But wine-crossover 11.2.2 is based on wine 1.4.1, with which William says his 
> game no longer runs. I think he said the patch requires wine 1.5.15, so he 
> may want to try the wine-devel port instead, as he said he was doing.

Yes, the game no longer runs in any released wine version. As I said,
the patch works fine with wine-crossover.

- Josh
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: I need consultation on running WINE on the Mac

2012-10-16 Thread Ryan Schmidt 

On Oct 16, 2012, at 06:00, Joshua Root wrote:

> On Oct 16, 2012, at 01:27, William H. Magill wrote:
> 
>> I play LOTRO, which just did a major upgrade, and therefore no longer runs 
>> under 1.4.1
>> 
>> WINEhq has a fix which requires WINE 1.1.15.

Did you mean 1.5.15?

>> However, the folks there are al LINUX types.
>> 
>> SO. I just installed MacPorts wine-dev 1.5.15 and now I need to do two 
>> things. (That I know of.)
>> 1- Find out how to apply the patch (which I believe is a classic diff 
>> file)-- I have no idea how badly that will break the MacPorts installation.
> 
> I've just applied it to the wine-crossover port. Seems to work fine.

But wine-crossover 11.2.2 is based on wine 1.4.1, with which William says his 
game no longer runs. I think he said the patch requires wine 1.5.15, so he may 
want to try the wine-devel port instead, as he said he was doing.



___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: I need consultation on running WINE on the Mac

2012-10-16 Thread Joshua Root 
> I know this is not a MacPorts issue, so please direct this to somewhere that 
> makes sense.
> 
> Basically, I'm a total newbee when it comes to RAW WINE. I've historically 
> used Codeweavers Crossover which is Wine 1.4.1
> Which is packaged to run quite nicely under Mountain Lion (10.8.2)
> 
> I play LOTRO, which just did a major upgrade, and therefore no longer runs 
> under 1.4.1
> 
> WINEhq has a fix which requires WINE 1.1.15. 
> However, the folks there are al LINUX types.
> 
> SO. I just installed MacPorts wine-dev 1.5.15 and now I need to do two 
> things. (That I know of.)
> 1- Find out how to apply the patch (which I believe is a classic diff file)-- 
> I have no idea how badly that will break the MacPorts installation.

I've just applied it to the wine-crossover port. Seems to work fine.

> 2- Find out how to configure "raw WINE"  on the mac. In particular how to 
> point it to the existing Crossover WINE Bottles.
> 
> Pointers to appropriate OSX oriented instructions are desired.
> Any help is greatly appreciated.

After installing wine-crossover, all you should need to run is (all one
line, ignore any line breaks inserted by email software):

WINEPREFIX="/Users//Library/Application
Support/CrossOver/Bottles/Lord of the Rings Online" wine
~/Library/Application\ Support/CrossOver/Bottles/Lord\ of\ the\ Rings\
Online/drive_c/Program\ Files/PyLotRO/pylotro.exe

- Josh
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users