Slashdot Mirror

Uh, other than the fact that Windows NT *was* OS/2 v3, that it contained the full OS/2 subsystem, and that Microsoft worked with IBM on OS/2 v1-v3 until renaming v3 to Windows NT?

>If he would've reported it to the vendor (in this case Microsoft), it wouldn't have been 'a known hole', but to the Microsoft developers. They would've came up with a patch...

Oh... you mean like this, this, this, and this?

Their update server wasn't compromised

It has been before. when code red hit. Although the link given in that article is no longer working there are plenty of screen shots of www.windowsupdate.com with 'hacked by chinese' on it out there somewhere.

You cannot blindly trust anything, from anyone. I don't care if Mom says her apple pie is just dandy I'm gonna run my own tests.

I call bullshit on that...

http://www.winnetmag.com/Windows/Article/ArticleID /16435/16435.html

Well, if you'd love to get in contact Paul (the author of this wonderful piece of literature), and perhaps let him know how you feel about this article, here's his email address...

Mail Paul (I'm-A-Fucking-Idiot-Thurrot) here

Go on, you pay your ISP for your mail handling, you deserve to send as many emails as you like to Paul.

Here are a few good ideas to get you started...

- Dear Paul, stop being such a retard, by the time Longhorn eeks its way out of Redmond, Apple will have made a least one more major OS release. And by your own standards, we'll be able to judge Longhorn when it ships against Apple's future 2-year-away OS (10.6?).

- Dear Paul, stop being such a cock. Love, [your name here]. xxx

- Dear Paul, before you go writing a load of shite perhaps you should have an inkling of that of which you speak.

- Tosser/

Well, if you'd love to get in contact Paul (the author of this wonderful piece of literature), and perhaps let him know how you feel about this article, here's his email address...

Mail Paul (I'm-A-Fucking-Idiot-Thurrot) here

Go on, you pay your ISP for your mail handling, you deserve to send as many emails as you like to Paul.

Here are a few good ideas to get you started...

- Dear Paul, stop being such a retard, by the time Longhorn eeks its way out of Redmond, Apple will have made a least one more major OS release. And by your own standards, we'll be able to judge Longhorn when it ships against Apple's future 2-year-away OS (10.6?).

- Dear Paul, stop being such a cock. Love, [your name here]. xxx

- Dear Paul, before you go writing a load of shite perhaps you should have an inkling of that of which you speak.

- Tosser/

Well, if you'd love to get in contact Paul (the author of this wonderful piece of literature), and perhaps let him know how you feel about this article, here's his email address...

Mail Paul (I'm-A-Fucking-Idiot-Thurrot) here

Go on, you pay your ISP for your mail handling, you deserve to send as many emails as you like to Paul.

Here are a few good ideas to get you started...

- Dear Paul, stop being such a retard, by the time Longhorn eeks its way out of Redmond, Apple will have made a least one more major OS release. And by your own standards, we'll be able to judge Longhorn when it ships against Apple's future 2-year-away OS (10.6?).

- Dear Paul, stop being such a cock. Love, [your name here]. xxx

- Dear Paul, before you go writing a load of shite perhaps you should have an inkling of that of which you speak.

- Tosser/

Well, if you'd love to get in contact Paul (the author of this wonderful piece of literature), and perhaps let him know how you feel about this article, here's his email address...

Mail Paul (I'm-A-Fucking-Idiot-Thurrot) here

Go on, you pay your ISP for your mail handling, you deserve to send as many emails as you like to Paul.

Here are a few good ideas to get you started...

- Dear Paul, stop being such a retard, by the time Longhorn eeks its way out of Redmond, Apple will have made a least one more major OS release. And by your own standards, we'll be able to judge Longhorn when it ships against Apple's future 2-year-away OS (10.6?).

- Dear Paul, stop being such a cock. Love, [your name here]. xxx

- Dear Paul, before you go writing a load of shite perhaps you should have an inkling of that of which you speak.

- Tosser/

Well, if you'd love to get in contact Paul (the author of this wonderful piece of literature), and perhaps let him know how you feel about this article, here's his email address...

Mail Paul (I'm-A-Fucking-Idiot-Thurrot) here

Go on, you pay your ISP for your mail handling, you deserve to send as many emails as you like to Paul.

Here are a few good ideas to get you started...

- Dear Paul, stop being such a retard, by the time Longhorn eeks its way out of Redmond, Apple will have made a least one more major OS release. And by your own standards, we'll be able to judge Longhorn when it ships against Apple's future 2-year-away OS (10.6?).

- Dear Paul, stop being such a cock. Love, [your name here]. xxx

- Dear Paul, before you go writing a load of shite perhaps you should have an inkling of that of which you speak.

- Tosser/

Well, if you'd love to get in contact Paul (the author of this wonderful piece of literature), and perhaps let him know how you feel about this article, here's his email address...

Mail Paul (I'm-A-Fucking-Idiot-Thurrot) here

Go on, you pay your ISP for your mail handling, you deserve to send as many emails as you like to Paul.

Here are a few good ideas to get you started...

- Dear Paul, stop being such a retard, by the time Longhorn eeks its way out of Redmond, Apple will have made a least one more major OS release. And by your own standards, we'll be able to judge Longhorn when it ships against Apple's future 2-year-away OS (10.6?).

- Dear Paul, stop being such a cock. Love, [your name here]. xxx

- Dear Paul, before you go writing a load of shite perhaps you should have an inkling of that of which you speak.

- Tosser/

Yeah it takes some time to setup in the beginning but it really works great if you are always pushing new machines out the door or doing annual reinstalls.

Here are a couple of links for those curious:

From Winnetmag.com

Unattended Installs in a Perfect World

Unattended Installs with Windows 2000 Professional

my $0.02

Yeah it takes some time to setup in the beginning but it really works great if you are always pushing new machines out the door or doing annual reinstalls.

Here are a couple of links for those curious:

From Winnetmag.com

Unattended Installs in a Perfect World

Unattended Installs with Windows 2000 Professional

my $0.02

A pointless grumble here, but I submitted a story that covered this 36 hours ago, and was rejected. Oh, BTW, it also covered the EU and Massachusetts antitrust cases, too. My link? Here. Read about the antitrust trifecta.

Let's just the feature ripped off by Microsoft and shoved into Longhorn in 2005/6. :-)

Actually, it has been claimed that the reason Microsoft is keeping a tight lid on the Longhorn GUI is that they already had a feature just like Expose and Apple somehow stole it. Riiiiiiiiight. Anyone care to provide proof of that? I find it highly dubious that while Expose has been being demoed for months now at every Apple event pimping the forthcoming 10.3, it was only very recently that Microsoft said that it was a feature filched from them and they have in fact been demoing something like that for years. I dunno, I've seen quite a few Microsoft demos, and read about still others. I saw video of the USB BSOD at the Win98 demo. I heard about their pointless "flapping Windows" feature in their knockoff of Quartz Extreme. But I've never heard a peep about their version of Expose, and considering the reaction it got when Apple demoed it and how useful people working with Panther betas seem to find it, you'd think someone would have heard something of Microsoft's.

~Philly

Isn't it safe to say if the cost of a 'server' or 'workstation' 64bit chip is cheap enough to replace a 'standard' chip in a PC then why can't they claim the right to the first Desktop PC (64bit)...just because it can be used as a server or workstation doesn't mean it can't do all of the needs of a PC.

If that's how you choose to define things, the first 64-bit desktop PC's were made over a decade ago.

Oh, and if one 64-bit PC architecture weren't enough, how about this one? Of course, back then, Windows NT also ran on the PowerPC architecture.

So... either the fact that the Opteron, like the MIPS and Alpha chips, was not designed or intended for use in "personal computers" means that Opteron-based workstations are not "personal computers" any more than Alpha- or MIPS-based ones were... or neither AMD nor Apple has the first "64-bit personal computer" by an entire decade.

(Incidentally, Windows NT 4.0 CD's -- I have one -- still contain code for those other architectures!)

Aswell I don't know if I agree with the statement that is has to be a basically "Dell" or some big name company build to be a PC... I have a 17inch monitor, speakers, headphones a mouse and keyboard and athlon 1600+... I call it a PC..and I built it from parts.

It doesn't -- it just has to be substantively identical to one. "Personal computers" are -- or are substantively identical to things that are -- mass-produced and marketed to consumers. You didn't see commercials on VH-1 for your system, and you didn't buy it at the mall or a big-box computer store -- but you (or others) have probably seen commercials for substantively identical kit on VH-1, and you could have bought something substantively identical to it in a mall or big-box store.

You cannot (to my knowledge) walk into the mall, or a big-box computer store, right now, and walk out with a BOXX workstation or something substantively identical, nor will you see commercials for it on VH-1. You will see commercials on VH-1 for Apple's G5, and you can walk into an Apple Store or possibly even a CompUSA store (I don't know who's gotten shipments of what, ya know?) and walk out one. (They'll be upset, though, if you don't pay.)

I realize, of course, that this all reeks of people with advertising budgets getting to declare that their products are whatever the heck they darn well please. Apple could have claimed that the G5 was a desktop, a personal computer, a workstation, a server, even a cheese grater, and since they're spending the bucks on commercials, that's what The Masses(tm) will probably believe. :)

Just close off port 135 - or even better, disconnect it from the net completely to achieve Orange Book C2 security.

How secure is it anyway?

It'd be useless for just about everything except typing Word documents and balancing your checkbook, but at least it's secure from Internet Worms and SQL queries.

Karma: Whore (you post anonymously when you're a troll)

Ok, I'll buy that they sued in time. But my other argument on Microsoft's stupid lawyers still holds water. IE has had plugin support since at least Aug 1996 (history) in IE 3.0 I'm sure they have code dating way before that.
How could the lawyers lose this case! It seems so obvious to me.

As far as I know, from pages MSDN it appears to be true of exchange, and Sql Server. Here are some links related to the topic http://www.microsoft.com/mspress/books/sampchap/40 90a.asp, http://www.winnetmag.com/Articles/Index.cfm?Articl eID=273. I'm sure there are more, but consider the following fact in the context of High Performance/High Availability. A typical high end enterprise system has to support tens of thousands of transactions per second. If the default number of worker threads for Sql Server is 255 and recommended max is 512 on a heavily loaded SMP box, is it likely Sql Server can support 5K concurrent queries? Or does this tell you the way Sql Server is designed is not appropriate and wouldn't be able to support say 10K concurrent queries a second like DB2 and Oracle? Forgetting the fact that current SMP bus motherboards can't that level of parallel access anyways. On a 4 CPU box with a couple hundred concurrent queries, the CPU usage will already be between 60-80%. With that kind of utilization and heavy cost of context switching, could Sql Server handle that kind of load?

I believe he was referring to the failure of Hailstorm, a.k.a. .NET My Services. For more information, see articles like this one, which were all over the place a year ago.

.NET Perspectives
I've received several reports from sources in and close to Microsoft that suggest the software giant is getting ready to walk away from .NET, its troubled attempt to move the computer industry from monolithic desktop applications to subscription-based software services. In this issue of .NET UPDATE, I'll examine the long, convoluted history of the .NET initiative, Microsoft's many failures to get customers, developers, and partners to adopt the technology, and the various ways in which the .NET vision has changed over time. Then, I'll discuss the rumors I've heard and the ramifications these potential changes could have on .NET.

As I described in the first-ever issue of .NET UPDATE, published in January 2001, the .NET initiative began with the "Internet Tidal Wave" memo Bill Gates sent to Microsoft employees in 1995. Gates could sense that the computing industry was changing rapidly because of the Internet, and he charged the troops with adapting to this change. Microsoft would meld Internet capabilities into all its products, Gates said, and during the next several years, the company did just that. Microsoft eventually decided it would need to redesign its entire product line to embrace the standards-based technologies that would underlie Next Generation Web Service (NGWS), later (and wisely) renamed .NET.

The goal for the company was to transition to a subscription software model, similar to cable TV subscription services. One of the problems with Microsoft's sales models is that the company has peaks in its earnings reports that are tied to big product introductions, and valleys that occur when existing products have matured or the company has replaced them with lackluster revisions. To smooth its earnings curve, Microsoft embarked on a controversial (but, at the time, legal) decade-long earnings restatement project, in which the company put aside portions of its earnings in each peak quarter and applied the difference to quarters in which the company didn't perform as well. The result was an unnaturally smooth earnings growth curve, in which the company experienced double-digit growth, year over year, throughout the 1990s. Unfortunately for Microsoft, earnings reporting laws changed. Federal regulators began to examine the company's books, and Microsoft had to change the way it reported earnings.

Although the company knew it couldn't maintain its historical growth rate, it was still eyeing ways in which it could smooth out revenues and avoid the bizarre daily stock-price changes that affect most high-tech companies. One obvious way, of course, was to move to the subscription software model it had so long desired. Instead of customers purchasing Microsoft Office once every 3 years for $400, for example, perhaps the company could convince customers to subscribe to an Office service for $100 a year. Like a gigantic aircraft carrier turning slowly at sea, Microsoft moved to implement this plan. On the enterprise side, software licensing had already evolved to a subscription-like plan, so Microsoft met little resistance among its business customers until it so egregiously changed the licensing fees in Licensing 6.0 that customers revolted and the company finally had to make concessions to lower the cost.

Consumers represented a different problem for Microsoft's subscription-service scheme. Most people think that when you buy a software product, you own it--Microsoft's obscure and little-understood licensing terms notwithstanding. Explaining to an individual that the software he just purchased for $100 wasn't really his to keep and continue using proved to be a challenge that even Microsoft's unlimited marketing budget couldn't overcome. In test markets for subscription software--in particular, Office XP--consumers universally panned the

Longhorn? Forget it. I'm now in the process to converting all my software to run on winPE. So thank you Microsoft...But no thanks.

A quick MS kludge that deserves mention (and of course has many limitations) is booting Windows boxen to a WINNT.sif file (aka an "answer file").

Pop a floppy in the drive. Open up notepad, and put in something like this. Save your file as "winnt.sif" (w/the quotes...otherwise it will name it winnt.sif.txt), and reboot your computer with both the install *and* bootdisk in the drives. The cd (boots first in BIOS, of course) installs according to the WINNT.SIF instructions on the floppy.

Oops--let's try the link again.

"VMS is probably a close second in terms of security. Its C-2 secure right out of the box."

You can do all sorts of things with vbscript and windows scripting host. Although, on Win98, WSH is a bug-ridden-security-exploit-waiting-to-happen. I looked into using it on a small network of Win98 computers, but ended up applying patches by hand because of all the possibilities for security problems. For "automatic" anything, Windows NT/2000 is a requirement from a security standpoint.

The sysdiff program has the "-m" option when reapplying differences to a system. It is required. That's right a required option! What does "-m" stand for? Manditory. "-m" is the manditory option !!!

Only from Micros~1...

This issue with Dell is only another case of Micros~1 presenting an option to the consumer.

Just another manditory option...

I meant to link HAL customization

Maybe the admin can just telnet in over a wireless connection and fix the problem!

Windows is so cool!