I've got vmware and sp2 xp pro running quite nicely now, and the only program I couldn't get to work was Laplink. I use Laplink extensively for file syncing and transfer over my network between computers. It's very fast for syncing and quite important in my office.
Laplink did work in Bootcamp, so I would reboot at the end of the day into bootcamp and all was well.
Last week, was messing with it and changed the VM network settings from NAT to Bridged and suddently Laplink would see my other computers. Then when done, I switch back to NAT as I would lose internet connectivity in bridged.
The weird part is that Laplink is now working over NAT or Bridged. I tried for hours to get it working in NAT before with no luck, but now it sees my network every time in VMware regardless of network settings.
Any ideas what changed..is it self-healing or magical? I plan on doing more MBP's this way, so if there's a trick to what I did, it would be great to have a better understanding of what is happening with these network settings.
Mark
Laplink did work in Bootcamp, so I would reboot at the end of the day into bootcamp and all was well.
Last week, was messing with it and changed the VM network settings from NAT to Bridged and suddently Laplink would see my other computers. Then when done, I switch back to NAT as I would lose internet connectivity in bridged.
The weird part is that Laplink is now working over NAT or Bridged. I tried for hours to get it working in NAT before with no luck, but now it sees my network every time in VMware regardless of network settings.
Any ideas what changed..is it self-healing or magical? I plan on doing more MBP's this way, so if there's a trick to what I did, it would be great to have a better understanding of what is happening with these network settings.
Mark