Sharp Chess Problems

View: New views
2 Messages — Rating Filter:   Alert me  

Sharp Chess Problems

by MacUser :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I know that Mono 1.9.1 is installed correctly on my Mac OSX machine because I can do "mono filename.exe" and apps will generally run (WinForms are about 100x slower than on a PC and are more or less unusable, but they run).

But when I download the exe-only Sharp Chess from the bottom of this page: http://www.sharpchess.com/?page=03%20Download

And then do a "mono SharpChess2.exe" the terminal just hangs there forever, with mono never returning and no application popping up.  Is there some way to diagnose what is going on?

Please note that I am on an actual Mac, not a virtual machine.  I point this out because the last few posts in this bug thread ( https://bugzilla.novell.com/show_bug.cgi?id=341849 ) seem to indicate that the problems are a lot worse for those of us on actual Macs and not always reproducible on the virtual ones.

Re: Sharp Chess Problems

by MacUser :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

"mono SharpChess2.exe" still hangs using Mono 2.0 Preview 1.  I read somewhere else that it may need to sit for a while as fonts cache, but I let it sit for an hour and it never woke up.


MacUser wrote:
I know that Mono 1.9.1 is installed correctly on my Mac OSX machine because I can do "mono filename.exe" and apps will generally run (WinForms are about 100x slower than on a PC and are more or less unusable, but they run).

But when I download the exe-only Sharp Chess from the bottom of this page: http://www.sharpchess.com/?page=03%20Download

And then do a "mono SharpChess2.exe" the terminal just hangs there forever, with mono never returning and no application popping up.  Is there some way to diagnose what is going on?

Please note that I am on an actual Mac, not a virtual machine.  I point this out because the last few posts in this bug thread ( https://bugzilla.novell.com/show_bug.cgi?id=341849 ) seem to indicate that the problems are a lot worse for those of us on actual Macs and not always reproducible on the virtual ones.