Originally posted by Kazuko
actually, it's not MS who is the culprit on the server end... DMR (the coding that will be included IN THE PROCESSOR) is what kills the net. Of course, you can turn it off, however, DMR keeps "unauthorized" programs from running on a PC. Chances are the servers will have this activated. Windows merely acts as a GUI for the DMR settings.
As long as servers have AMD and Intel processors, they will have DMR in the system (starting soon) and therefore, be tainted.
actually, it's not MS who is the culprit on the server end... DMR (the coding that will be included IN THE PROCESSOR) is what kills the net. Of course, you can turn it off, however, DMR keeps "unauthorized" programs from running on a PC. Chances are the servers will have this activated. Windows merely acts as a GUI for the DMR settings.
As long as servers have AMD and Intel processors, they will have DMR in the system (starting soon) and therefore, be tainted.
If you're running Linux (which will include DMR support, eventually), then don't worry, a patch will be included with Linux (well, not officially) (or will be able to be downloaded - the DMCA doesn't reach that far) to do a 'software bypass' - totally reasonable, the encryption key will be the only real roadblock. And I'm sure a few sysadmins running large processor clusters won't mind using some spare cycles

Correct me if I'm wrong (it's been a while since I read all about this - perhaps I'm mistaken).
Comment