Virtual PC copy-checking bug: work-arounds

Yesterday, we cited a problem where Virtual PC, running in OS X, may erroneously claim that another copy of VPC is running and will refuse to launch. A work-around is to logout and log back in. However, Jiro Fujita offers this less disruptive solution, especially likely to work if the problem occurs after a crash of the VPC application: "I found out that there is a process called 'VirtualPC_Services' running in the background even though the actual VPC is not running. If you kill VirtualPC_Services, VPC will launch just fine. As VirtualPC_Services is owned by root, you will have to kill the process as root (via Terminal)." Note: to do so, type <top> to obtain the process's PID number. Then type <sudo kill PID>. Several other readers confirmed this solution.