I think the key point is this: It's his wife's machine and he wants to take the least risky path to solving the problem. If he just fixes the current machine and wife still has problems, then he gets the arrows. But if he sets up a clean machine and his wife has problems, then Microsoft gets the arrows. Hence, it is in his best interest to set up a "clean" machine.
btw, I use virtualization all the time (VirtualBox, VMWare Server, QEMU) on a linux host machine to run Windows. There are a few limitations to consider: VM's are noticeably slower than the host machine (QEMU is the worst). USB support varies (for example VirtBox can't connect to my thumb drive). 3D Video either doesn't work or sucks to the point that it is worthless.
I agree. The OS code is the core (no pun intended) of the problem, not application programs. For example, application programmers normally don't write sort algorithms. They simply call a "sort" routine provided by library code. Usually these library routines are specific to a particular OS (e.g. dot net).
The bottom line: fix the OS and its related libraries and you'll fix most of the problem described in the article. Microsoft knows this. That is why the are so involved with this issue.
The more things change, the more they stay the same...
I own the copyright to that statement. You'll be getting a letter from my attorney soon...
I think the key point is this: It's his wife's machine and he wants to take the least risky path to solving the problem. If he just fixes the current machine and wife still has problems, then he gets the arrows. But if he sets up a clean machine and his wife has problems, then Microsoft gets the arrows. Hence, it is in his best interest to set up a "clean" machine.
btw, I use virtualization all the time (VirtualBox, VMWare Server, QEMU) on a linux host machine to run Windows. There are a few limitations to consider: VM's are noticeably slower than the host machine (QEMU is the worst). USB support varies (for example VirtBox can't connect to my thumb drive). 3D Video either doesn't work or sucks to the point that it is worthless.
I agree. The OS code is the core (no pun intended) of the problem, not application programs. For example, application programmers normally don't write sort algorithms. They simply call a "sort" routine provided by library code. Usually these library routines are specific to a particular OS (e.g. dot net).
The bottom line: fix the OS and its related libraries and you'll fix most of the problem described in the article. Microsoft knows this. That is why the are so involved with this issue.
-- chuck
Good catch. You would think that before someone posts an summary, they would actually verify it.