You will never get per pixel frames on Virtual PC as the graphics driver does not report per pixel support.
Neil Banfield
Install WindowFX. Run it. Does it offer to enable HW acceleration, and if so enable it and reboot.
Set a hotkey to jump to primary and you should be able to return to your primary machine. Please note that if one PC has rebooted the MP will detect this and disconnect from it (returning the mouse to the primary) and will reconnect when it returns.
MCPClient isn't used by WB. WBsrv.dll is the replacement for fastload.dll.
grcentral002: Are you running windowfx? If so its not WB5 compatible yet.
The beta release of WindowBlinds 5 does NOT support 64 bit windows. No amount of fiddling will get it to work correctly on that OS. Once we are happy with the beta of WB5, we will build the 64 bit dlls.
Well the odd colours on the titlebar of that perpixel skin can be fixed by downloading WB 4.90a which went on SDC a while ago. Right click overrides are not operational for per pixel skins yet. The black issues in wbconfig are new to me. Unsure why that would happen right now, but I will look into it.
iseekserendipity: You must have Service Pack 2 or later installed with this beta of WindowBlinds.
4.90a should be showing up in SDC
Please install SP2.
Its up now as 4.90a
If you have a nvidia card then please hold off on downloading WB5 for the next 15 mins or so. We believe we have a fix for the nvidia corruption problems which is currently being tested.
BrokenSquare: look for wblind.dll in your install directory. Is it there?
There should be at least 1 per pixel theme included with it and I am sure more will arrive on Wincustomize quickly.
WFX 2.11 is not the latest version. WFX 2.19 contains a fix for this resize problem and the beta of WFX 2.5 should be out this week I hope. You should be able to install 2.19 by downloading Stardock Central & entering your WindowFX serial number.
You need to install WB 4.4 or later to be compatible with the athlon64 chip + SP2.
There is no city of heros demo so we can't look into this problem currently. If you can find an app which has a similar problem with a demo then we can investigate further. Do you have fade desktop enabled or the status window showing? If so what happens if those are disabled?
If you have firewire ports on both PCs then you could buy a cable & setup a private firewire link between the 2. Instant fast reliable 400Mbits/sec private LAN. BTW a network being a little slow should not cause MP to disconnect. It might make the mouse laggy when the network gets slow, but thats unavoidable. Only a network which either loses packets, or takes more than 5 seconds to do a 'ping' will cause a disconnect. If you have quick detection of disconnec
What does the crash say?
Please bug this with Microsoft
If you set a ping running between the machines (using ping ipaddr -t), do the ping times alter much when you move the mouse in circles? Try from both the primary to the secondary & secondary to primary.
That does sound abnormal. We will look into the memory usage as its usage should be low and remain low.
Which version do you have installed and what does the error message say? Also is the crash on the primary or the secondary?
Yahoo Messenger does not use DirectSkin. At a guess I would say its a graphics driver issue and you need to upgrade them if possible. If that doesn't fix it, contact Yahoo and see if they have any ideas.
There is a trial of the non pro version so you can see for yourself