> Windows is very fussy about the hardware. If the hardware changes from >when it was originally installed, it refuses to run. This is >(supposedly) to prevent unauthorized copies. So it is unlikely you will >be able to get the copy on disk to run. It's true that when you make major changes to the hardware, Windows often won't be able to see the boot device. But this is not a refusal to run, and it isn't a form of copy protection. It's simply a matter of not having the proper drivers for the new hardware. There are several ways around the problem - one is to run Sysprep, which makes all drivers known to the OS available for use on the next boot with the option of adding drivers during the boot. Another is to run windows from a drive controller that can be installed in the new system, so that Windows finds itself booting from the same hardware it always has. Sometimes this works great, sometimes not. It's not impossible to move Windows to new hardware, and it's not even that hard to do. However, you might end up having to call Microsoft after the move to get it activated. That's the copy protection part. They ask you a couple of questions and you get the new code. And they're usually pretty nice about it. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
