Pardon the late response, but you might consider getting your entire XP and dev environment set up and getting it right then backing up the /Documents/Virtual Machines/Windows XP file to some external drive. One reason is to is to avoid problems in the hard drive upgrade you spoke about, but more importantly you can avoid (or at least roll back) "Windows bloat" this way. My virgin images weigh in about 4 GB. I've seen them grow to almost 20 GB over time! There were no other changes to account for this bloat. No new SW installed, and all my working files are on the Mac shared drive (not in the C: drive which is part of the VM image.) So I rolled it back. Lastly, if your mac should ever bomb on you while a VM is open it can do some nasty things to the XP image - and you'll really want that virgin image. Alden Gerhard Fiedler wrote: > Joseph Bento wrote: > > >> The XP install was not without issues, however. Seems I installed my >> copy one too many times, even though the only place that copy has >> ever been used was on this MacBook. >> > > XP doesn't ever see your MacBook; all it sees is the VM you are > installing it in (and its virtual hardware). The XP activation tracks > the hardware XP sees -- which is not your MacBook, but the VM where > you're installing XP. > > >> I eventually want to upgrade the HD in this MacBook, and only hope the >> cloning software also moves the virtual machine without issue. >> > > A VM is nothing more than a set of files that is properly registered > with the program that can "play" the VM. So if you make sure that you > copy over all the relevant files, you'll have your VM on your new disk. > If for some reason the registration of this VM with your VM "player" > (seems to be VMware Fusion) doesn't copy over, you can register it and > it should work normally. People exchange VMs between different systems > all the time. > > Gerhard > -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist