StevenM wrote:In that case please put your paranoia aside for a brief moment, it would be great if you could compare experiences on the Bootcamp partition for us.
Ok, haven't played enough hands to confirm if the HUD missing issues still occur, but I have a Bootcamped install up and running.
First the good news. Its Fast. Very slick & responsive. Only played 20 hands or so on a single table to check it out but HUD updating fine, hands importing near realtime from 888. Switching between graph, reports & stats has a <2sec response time to draw & populate graphs/reports. Memory usage according to Task manager started around 130mb now remains around the 150mb mark.
Now the bad news. Processor usage is high. Macbook is working hard after the first few minutes fans spin up and quickly the CPU climbs to around 40% util. This seems to continue even after the poker table is closed down, slowly creeping up now to near 50%. Not sure what's going on there. Switching off 'Get Hands whilst playing' the CPU usage drops right away to a background process taking near zero cpu as you'd expect, though memory usage has crept up to 160mb whilst I've been typing this lot.
Bootcamp install is Windows 7 Home Premium x64
Macbook Pro Intel Core 2 Duo T9600 2.8 Ghz 4GB DDR3
Windows Experience Index is 5.7 (limited by HD data transfer rate - other metrics range from 5.9 to 6.5)
Running postgres 9.0.6 x64 on localhost (windows 7 bootcamp)
Will stress it harder over the next couple of days.
Also have a working postgres install in Mac OS X now. Bit of a hassle to backup & restore the database from the VMWare guest OS to the OS X host. Couldn't get the backup & restore functions within PT4 to do what I expected. No matter what options I selected or deselected for use default server/port I couldn't get it to restore the backup to the remote postgres db on the host even though I deleted all other postgres connections (leaving just a blank test db on the host) and shutdown postgres on the vmware localhost. Eventually I figured a way to create a similarly named blank DB on the host OS then used pgAdmin to take a backup of the VMware DB and load it up on the host. After much fiddling and a few fatal error crashes, PT4 seems to happy talking to the OSX host's postgres server. Ended up using a similar technique to get the DB loaded up in the bootcamped windows 7 install.
Haven't played any hands on the VMWare WinXP setup since, but browsing through the stats & results tabs things do feel a little quicker.
Let me know if you'd like more detail on any of the above. I'll post further updates in the coming days.