Perhaps the 'transfer once' restriction is built into the cable? So that when it completes a drive to drive transfer, it has a built-in self "bricking" function to prevent data duping? I'm grasping here, but M$ *did* instruct you to throw it away.
1) Hope it gets hacked for multiple uses.
2) What a load of eWaste. The last thing we need is a few hundred thousand of these in a land fill. Shame on you, M$
Reader Comments (Page 1 of 1)
bobartig @ Apr 26th 2007 2:22PM
Perhaps the 'transfer once' restriction is built into the cable? So that when it completes a drive to drive transfer, it has a built-in self "bricking" function to prevent data duping? I'm grasping here, but M$ *did* instruct you to throw it away.
1) Hope it gets hacked for multiple uses.
2) What a load of eWaste. The last thing we need is a few hundred thousand of these in a land fill. Shame on you, M$