Slashdot Mirror

← Back to Stories (view on slashdot.org)

Competitors Cry Foul At Windows XP, 2K Service Packs

Posted by timothy on from the consider-the-source dept.

caudron writes "According to an article at ZDNet, a trade group partly funded, not surprisingly, by Microsoft's competitors is claiming that WinXP SP1 and Win2k SP3 contain 6 separate violations of both the letter and spirit of the proposed DOJ Settlement. Equally unsurprising, Microsoft disagrees with them. And so the Case-That-Wouldn't-Die drags ever onward."

2 of 510 comments (clear)

  1. Re:The -Proposed- Settlement by d3xt3r · · Score: 5, Interesting
    Yes the settlement is not final yet, however, Microsoft claims that SP1 & SP3 comply with the terms of the proposed settlement. Therefore, it is important to point out MS is lying.

    Hopefully this will make the DOJ wise up to the fact that MS will find a way around anything.

  2. My experiences with Win2K & Dell by dcavanaugh · · Score: 5, Interesting

    We have a Dell Poweredge 2450 server including RAID 5 disks, running Win2K & SQL Server. We discovered mysterious anomolies (Control Panel not working and some other wacky stuff). Microsoft support recommends a full restore from tape. OK, we have tapes, let's go. We attempt to boot from CD and we know we need to supply a driver disk for the RAID card. Each time we attempt to boot, things look okay for a while and then BAM! cryptic register dump -- game over. This goes on for THREE DAYS of fumbing & bumbling. My sysadmin is a very knowledgable MCSE, not some newbie who uses the CD-ROM as a cupholder. Microsoft support was puzzled, so was Dell. Eventually, the Dell folks determine that we were given the wrong driver disk for our Dell RAID controller. Evidently our RAID controller had newer firmware than our driver disk (not that Win2K told us anything useful at boot time to suggest this). We download a new driver, and the restore eventually works. This series of events started out as a standard Microsoft response (reinstall the OS) to a standard Microsoft problem (anomolies with no useful clues in the event log). Dell gets some of the blame, but we expect the OS to either boot up or tell us why not.

    By the time we had this little crisis under control, I gave the server in question the nickname "Atta" and wrote it on the paper label we stick on the server that shows name & IP address.

    In my shop we have Microsoft and Linux boxes running side by side. I am the IT manager, so if some Microsoft salesman wants to talk about how their products can improve our uptime and reduce support costs, they will first have to listen to the story of how one of their products motivated us to name a Microsoft server after a middle east terrorist. Then they will have to explain how our costs will decline by paying for licenses/support/upgrades, and how our uptime will improve as we respond to mysterious anomolies by doing full restores on servers that can't even boot properly from CD/floppy.

    Years ago, I worked at a DEC shop. Everything was damn expensive, but it was rock-solid. When things didn't work, we saw messages and error log entries that provided clues. DEC had tech. support that would investigate any crash dump and determine what happened. All of this was very pricey, and DEC got slaughtered by commoditized x86 hardware and Microsoft software. Sure, today's Wintel servers are cheaper and faster, but stability, recoverability, and support are worse now than 20 yrs. ago.