Thank you Microsoft.
Look, its quite clear that Longhorn will contain DRM that limits what we can and cannot do with our computers.
Note that that PPT is straight from Microsoft's own website. If this is FUD, then I dread to think what FrontPage 2000's EULA is.
The PPT is not FUD, your misinterpretation of what it means is.
Longhorn will contain functionality which allows copyright owners to restrict the usage of their copyrighted material. If you don't like that, it's the media owners you should direct your complaints at, not those implementing the functionality required by the spec.
The alternative is that Longhorn is unable to play back that media at all. The HD-DVD and Blu-ray specs will require that any device capable of playing back the discs has this kind of protection on it, simple as that.
It's no different from the current requirement of DVD playback devices to support Macrovision.
Macs will have this too.
Among all this fun and crazy stuff, as a windows user and a fan, what I'd like to know and learn is how Microsoft is going to go about using the PowerPC platform?
I believe it's called X-Box 360.
Now that Apple are ditching PowerPC there aren't going to be any mainstream PowerPC boxes on sale (aside from consoles) so, if anything, it would make even less sense to start selling Windows for PowerPC now than ever before.
Since Itanium2 (IA-64) is VLIW, it's supposidly "better" than RISC, so this might just work...
Contrary to what they like to teach students there isn't an obvious VLIW > RISC > CISC type progression. Indeed as memory becomes significantly slower than CPUs there is an argument that CISC > RISC.
Unfortunately the ADC site appears to have gone down so I can't get any more details from there (and I'm not sure I remember my Apple login anyway...)
CAD generates a non-maskable interrupt which tells the CPU to "drop everything and do this instead", where "do this" is show the Security window. When you then click task manager, the system launches it normally and so you have to wait.
If you're using the Welcome screen, CAD gives you instant access to Task Manager instead. Which is nice. Shame there is no way of getting that response in a domain environment though...
Explorer is the shell for Trident. Any issues with "IE" are inherently issues with Explorer (or Trident)
If you read the linked advisory you'd note that the actual flaw is in the Client for Microsoft Networks (i.e. NetBIOS)
To describe that as a Critical IE flaw is pushing things a bit.
XPSP2 systems wouldn't be vulnerable in the default configuration anyway (File and Print Sharing is blocked by the firewall), pretty much every broadband router will be blocking those ports out of the box, even in the unlikely event the ISPs aren't already and corporate networks that allow NetBIOS traffic from the web deserve everything they get!
As for third-party add-ons, wouldn't that be a vunerability in IE's plugin architecture?
There were a lot of flaws in ActiveX, do holes in that count at holes in IE?
If you take that argument to it's logical conclusion then all software vulnerabilities are the responsibility of the Windows team. After all, Firefox is just a third party plug-in for Windows right?
If it were just IE's handling of ActiveX at fault (which has been the case in the past) then fair enough. If the flaw is internal to the plugin and is exploitable via any web browser hosting it, as is the case there with Netscape and Opera, then it hardly constitutes an IE issue.
I think it should be done on a "per browsing platform" basis, which includes the rendering engine (Trident/Gecko), container application (Explorer, Firefox), and any loaded plugins and extensions (Flash/HappySmilyToolbar). It makes more sense that way.
Well yes, when Secunia start rating things like that the statistics might be a bit more meaningful.
Until then, always assume all browsers are vulnerable to something - because sooner or later you'll find out they are. That's the only way to really be safe...