J JKing3 Bit poster Nov 9, 2011 #21 +1 for the issue as well, only while in Bootcamp. Its driving me nuts, hours of searching I finally found this thread. Would love to know when this will be slated to be fixed and is there bug tracking tool to see status? Thanks.
+1 for the issue as well, only while in Bootcamp. Its driving me nuts, hours of searching I finally found this thread. Would love to know when this will be slated to be fixed and is there bug tracking tool to see status? Thanks.
J JKing3 Bit poster Nov 10, 2011 #22 Hi! Just wanted to update that I installed the latest update/patch for parallels 7, updated parallel tools and its working as it should now! yey!
Hi! Just wanted to update that I installed the latest update/patch for parallels 7, updated parallel tools and its working as it should now! yey!
M MKPARK Bit poster Feb 25, 2012 #23 You can just terminate prl_* processes... When using boot camp, just call the task manager and terminate the processes with the name beginning with prl_*(prl_cc.exe ... and so on). You should do it after every boot time, but it works for me.
You can just terminate prl_* processes... When using boot camp, just call the task manager and terminate the processes with the name beginning with prl_*(prl_cc.exe ... and so on). You should do it after every boot time, but it works for me.
G Gary King Member Mar 8, 2012 #24 Can someone confirm if the latest Parallels Tools fixes this problem? I just realized yesterday that it was Parallels causing it; I had been living with the problem for months prior.
Can someone confirm if the latest Parallels Tools fixes this problem? I just realized yesterday that it was Parallels causing it; I had been living with the problem for months prior.
