Gert van den Berg wrote: > wPrime 1.55 runs, 2.0 hangs in its hardware detection phase. > > Another note: 1.55 does not seem to thread properly. Was unable to > detect core count, only used 25% CPU even when forced to 4 threads.... > > Gert The threading isn't working under wine. You can hit ~ to get the console, wPrime 2.0 stops at the initiating thread stage. What it does at this stage is it runs a quick test (512K sqrt) to test and sync the threads. wPrime 1.55 defaults to one thread and thus it gets past this stage correctly. wPrime 2.00 defaults to four threads, so it runs the test, one thread finishes and the others fail to report, so it sits there waiting for the other 3 threads. http://www.wprime.net/wprimeblank.exe This exe was created with the wPrime customizer, it doesn't do any of the startup tasks, so you'll get the wPrime console when it starts. Type: ft x - this sets the thread count to x. It's only going to work with 1 thread <enter> Type: gui - this opens up the gui <enter> You can then run the tests, but you'll see that no matter what the thread count is set at, it will only run with 1 thread, and it will fail to complete on any thread count above 1. Code: cd /tmp wget http://www.kegel.com/wine/winetricks mv winetricks /bin/winetricks winetricks vb6run wsh56 cd ~ wget http://www.wprime.net/msvbvm60.dll wget http://www.wprime.net/wprimeblank.exe mv wprimeblank.exe wprime.exe This should get wPrime 2.00 working from day 1, assuming you have wine already installed.