I'm asking this question because of the flood of reports of what I'm calling the "Boot Camp/Parallels Windows reactivation dance." The issue seems to be that if one installs Parallels Tools for Boot Camp (at least under many users' conditions), Windows sees "hardware" changes and demands reactivation when Windows XP is started within the virtual machine environment. If the user returns to direct boot into XP from power up using Boot Camp, Windows sees hardware changes again, and demands anotther reactivation. Pretty soon the number of authorized reactivations is exceeded. I suspect almost all those who are using Boot Camp have needs within the Windows environment that Parallels won't meet any time soon; e.g., seamless use of all USB 2.0 devices, seamless access to the entire Windows graphical environment, seamless networking. I also would guess that many of us reluctant Windows users have more prosaic needs for Windows that can be met easily by Boot Camp (business software that runs only within the Windows OS or (even worse) only within Internet Explorer for Windows (that's my personal affliction). I'd love to have access to my Mac while running Windows, but there are still things I can't do within the Parallels scheme. Do the Parallels developers believe they'll be able to resolve this issue of a demand for Windows reactivation each time the user changes the method through which he/she access the Windows OS? Thanks so much, Jim Robertson
