General discussion


Is Microsoft at fault

By jterry ·
Why do I read about so many poeple who say they are not going to update windows to SP2 or install any Microsoft updates and than want to blame Microsoft when there PC gets corrupted? They are not only making their own PC vulnerable but opening themselves to be a Bot to infect others.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

I expect ANY product I buy to WORK

by jdclyde In reply to software compatability

The main purpose of this discussion was to get people from both camps to leave camp long enough to see what the other has to offer.

I am running SP2 on all work systems. I should not have had to reformat three of the systems, but I did. It is still better to reformat the three now than to lose them all because of being unpatched. This whole issue is still a MicroSoft problem because it is a DEFECT in their software that has made me go through this process.

I use MS products for home and work and will continue to use them. The products would be much better if the MS camp wasn't just blindly following and DEMAND that MS package a quality package. Until the customer base does, why would MS?

Also was to point out that *nix is a powerful tool that would help many organizations with mission critical applications.

Use what you want and like what you want, I don't care. I am not anti-MicroSoft, though I do lean more towards the *nix camp.

It is just that much of the OS religion is like the natives worshiping the volcano. Hope your not there when it erupts.

Collapse -

Apples and Oranges

by jmgarvin In reply to I pay attention to what I ...

If the app didn't work in XP to begin with, than that is a vendor issue.

HOWEVER...the problem is that SP2 broke tons of apps that worked in XP previously, that is all MS.

Collapse -

It wasn't just apps either

by HAL 9000 Moderator In reply to Apples and Oranges

There was quite a lot of hardware that didn't work properly after SP2 was installed as well. The ones that come to mind readily where the wireless cards and there where a lot of Network Printer problems as well.

It gets very hard to live with something that breaks so many things when all you are supposedly doing is applying a security patch as SP2 was touted by M$. There was a very long discussion thread about SP2 here and while not even close to the longest thread that has been posted here it would have come close to being one of the longest Technical Threads that TR has ever seem. I think it was called something like "SP2 great but it can break things" and it was more a Q & A type thing where everyone was posting problems and others where posting fixes for the posted problems as we worked them out.

Things like Flashing the BIOS on P4's where easy but the wireless and network printing issues where a lot harder to cure if they ever did. Most of the problems listed about network printing was not so much that it stopped working but that it slowed things down to a crawl and made it virtually impossible to keep on the desktops for that reason alone.

Col ]:)

Collapse -

Oh yes more than just apps

by jmgarvin In reply to Apples and Oranges

There were (are) problems with SATA, various video cards, NICs, and some cool issues with some mobo chipsets ;-)

WOO! Thanks MS!

Collapse -


by apotheon In reply to Apples and Oranges

Yeah, the SATA problem I ran into was really interesting.

XP SP2 removed the "uncertified" driver for the SATA controller dynamically, and the SATA drive was what had the OS on it, so the computer crashed. Restarting, obviously, did not fix this, as Windows would start to load from the drive, using the SATA driver, then got far enough along that the SP2-included functionality that checks for uncertified drivers found it, then it dynamically removed the driver from the OS again. The OS vanishes from under itself, and the system crashes. It's shiny side down again. Whee.

Using the Windows XP CD to do a recovery reinstall of the driver changed NOTHING, because (of course) the driver wasn't actually gone: it was just being ignored by the OS as of partway through boot. The only way to make the driver work again would be to uninstall SP2.

The OS couldn't boot far enough to remove SP2 and as a result there was no way to remove SP2 short of overwriting part of the kernel. Since I'm not that insane, I wiped the hard drive and reinstalled from scratch, then cautioned against installing SP2 again. The client listened, this time (he'd installed SP2 on that machine after being advised that he shouldn't).

This entire situation was quite suboptimal, but amusing in retrospect. People wonder why I prefer Linux; that really boggles my mind.

Collapse -


by apotheon In reply to I pay attention to what I ...

It's not progress that killed third-party apps when SP2 was released. It's irresponsible practices on the part of Microsoft.

Without any warning that such would happen, with a "mandatory" patch/upgrade, mission-critical applications were rendered entirely inoperable and unrecoverable. That's like making a cargo van for a shipping company safer by removing the cargo compartment without warning the shipping company in advance. This is not good business practice.

Collapse -

help gudiences

by hi_santoshp In reply to Is Microsoft at fault

hi i am antosh patil
i want exchange 2003 audio & video prsentation
how i get this pls my mail id

Collapse -

Microsoft is at fault!

by sudekumd In reply to Is Microsoft at fault

Microsoft is totally at fault.. Their product is faulty and poory tested. If a car were made the way Microsoft made Windows it would not sell. Oh wait the Yuego was made like Windows and it lasted what 2 years? Granted once installed it IS the customers responsiblity to keep the product up to date but at the same time Microsoft has a moral responsiblity to assist the user to keep their faulty product up to date as simply and easy for the user as can be done. Microsoft has the personell and the talent and the knowledge on how thier product is supposed to be functioning.. they should NOT be having problems like this.. new exploits are being found nearly daily in their products. Test...Test....and test some more then test again...break it fix it....alpha it ... test some more then beta it ... throughly tyesting and fixing what is broken BEFORE it is released is the win.

Collapse -

Tarred and Feathered

by mrafrohead In reply to Is Microsoft at fault

They should all be tarred and feathered huh???

They're the first group of people that will ***** and whine and attack the hacker that created the "mess" they are dealing with. Instead of looking in the mirror to see who the real culprit is.

Those updates are there for a reason. If you aren't going ot update those windoze, buy a freakin' MAC or go to Linux.

nuff said...


Collapse -

Actually I have no problem with patching

by HAL 9000 Moderator In reply to Tarred and Feathered

But I refuse to even consider doing this without first testing the offerings. I would prefer to have my anti intrusion systems working a little harder than not having the computers working at all. :)

Look at this months offerings 10 Patches from MS thankfully all are not for the main products that I use but there will still be a load of testing before deploying these.

I've had my fingers burnt previously by something as simple as a Java plug in trashing an entire OS so I'll never blindly accept MS promise that it's the best that can produce at short notice, granted they have got a bit better now as they don't seem to be recalling patches lately and releasing a new one to fix what the old broke but from my experience when the Patches broke things I had the systems fixed and left un patched by the offending patch long before the fix became available.

Col ]:)

Related Discussions

Related Forums