Basically, what you're doing here is system imaging. You'll need to use SysPrep on the live box to prepare it for the "jarring" hardware change that is about to come.
This isn't to imply that your disk read error is caused by not using SysPrep, it could just be another issue, but Windows tends to not boot when certain hardware changes. I no longer recall the specifics but it relates to Windows having more than one kernel but only one being installed, among other things. (For instance the change from SATA to IDE drives might be causing this.) Anyways, I don't know for sure that it will help but I'd suggest looking into the SysPrep tool. --~--~---------~--~----~------------~-------~--~----~ Central West End Linux Users Group (via Google Groups) Main page: http://www.cwelug.org To post: [email protected] To subscribe: [email protected] To unsubscribe: [email protected] More options: http://groups.google.com/group/cwelug -~----------~----~----~----~------~----~------~--~---
