In <36 months, virtualization will be the rage... as lowering the barrier to switch to mac attracts more an more users...
As such, transporter becomes an absolute critical component... While I cannot say from experience as I am one of those users still on the fence (mainly because I have a fortune invested in the sw on my windows box that I do not want to lose).. The "Switching costs" are still too high unless there is some certainty.
my wish list is to make Transporter failure the exception not a branch on the forums... Now, before the Parallels engineers reply, "duhh.... "... my suggestion is:
during transport, temporarily turn on a TFTP server, DHCP server, and PXE (on the mac)... and on the remote PC they enable "network boot" instead of booting to windows... The network would of course be the Mac.. which could run an imaging program (sorry, won't be pretty, but functional) - very similar to legacy versions of norton ghost.. and then mount a network drive(mac)... and remove the issues of windows installation bugs or anything that would slow the transport... with a 100Mbps link, you should be waiting on the PC HD .. not the mac nor the network... and basically remote launch a mini-OS, I dont care if it is an MS-DOS boot disk equivalent... just something that can access the mounted (mac) drive... and then stream the data to the mac in real time never letting the PC have a chance to let windows get in the way.. in effect, pulling out a tree in the ground by cutting 10 feet under the roots, instead of getting the dirt soaking soaking wet.. and then pulling hard on the tree...
my $0.02..
/mr
As such, transporter becomes an absolute critical component... While I cannot say from experience as I am one of those users still on the fence (mainly because I have a fortune invested in the sw on my windows box that I do not want to lose).. The "Switching costs" are still too high unless there is some certainty.
my wish list is to make Transporter failure the exception not a branch on the forums... Now, before the Parallels engineers reply, "duhh.... "... my suggestion is:
during transport, temporarily turn on a TFTP server, DHCP server, and PXE (on the mac)... and on the remote PC they enable "network boot" instead of booting to windows... The network would of course be the Mac.. which could run an imaging program (sorry, won't be pretty, but functional) - very similar to legacy versions of norton ghost.. and then mount a network drive(mac)... and remove the issues of windows installation bugs or anything that would slow the transport... with a 100Mbps link, you should be waiting on the PC HD .. not the mac nor the network... and basically remote launch a mini-OS, I dont care if it is an MS-DOS boot disk equivalent... just something that can access the mounted (mac) drive... and then stream the data to the mac in real time never letting the PC have a chance to let windows get in the way.. in effect, pulling out a tree in the ground by cutting 10 feet under the roots, instead of getting the dirt soaking soaking wet.. and then pulling hard on the tree...
my $0.02..
/mr
