Re: FIX for ZoneAlarm & KB951748 issue released

Re: FIX for ZoneAlarm & KB951748 issue released

Secure Home | Search | About

Microsoft Applications Security - Microsoft's general security discussions and announcements 

Bookmark this page:  YahooMyWeb Yahoo!  Google Google  Windows Live Favorites Windows Live  del.icio.us del.icio.us  digg digg  Add to Netscape Netscape
Subject Author Date
Re: FIX for ZoneAlarm & KB951748 issue released xxexbushpig 07-12-2008
Posted by =?Utf-8?B?eHhleGJ1c2hwaWc=?= on July 12, 2008, 1:46 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
Well it might have been a "dimbulb" (which is a great new word BTW), but it
wasn't as big a dimbulb as the Microsoft person who issued the KB951748
update that screwed up millions of people!

"Nunya Bidnits" wrote:

> PA Bear [MS MVP] wrote:
> > Nunya Bidnits wrote:
> > <snip>
> >> OK, I just refreshed the page and now its there. But you can see
> >> from the cut and paste it wasn't there, at least not for a while.
> >> The "date last revised" on that page has not changed, July 9. I may
> >> be crazy but I ain't stupid, when everyone said it was there I tried
> >> that page several times, and
> >> have never navigated to it before today, so it was not in my cache.
> >
> > That page has been revised at least four (4) times since it was first
> > published on 08 July 2008.
>
> Well, some dimbulb revised it at least once without the update links....
> sheesh.
>
> MartyB in KC
>
>

Posted by PA Bear [MS MVP] on July 12, 2008, 1:51 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
So Windows must be compatible with ZA and any other third-party application,
not the other way around?

Get real.


xxexbushpig wrote:
> Well it might have been a "dimbulb" (which is a great new word BTW), but
> it
> wasn't as big a dimbulb as the Microsoft person who issued the KB951748
> update that screwed up millions of people!


Posted by V Green on July 12, 2008, 2:41 pm
If you were  Registered and logged in, you could reply and use other advanced thread options

> So Windows must be compatible with ZA and any other third-party application,
> not the other way around?

Why not?

ZA WORKED before the update. The update BROKE it.
So it's ZA's problem?

Get real.

>
> Get real.
>
>
> xxexbushpig wrote:
> > Well it might have been a "dimbulb" (which is a great new word BTW), but
> > it
> > wasn't as big a dimbulb as the Microsoft person who issued the KB951748
> > update that screwed up millions of people!
>



Posted by Shenan Stanley on July 12, 2008, 3:42 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
<snipped>

PA Bear [MS MVP] wrote:
> So Windows must be compatible with ZA and any other third-party
> application, not the other way around?

V Green wrote:
> Why not?
>
> ZA WORKED before the update. The update BROKE it.
> So it's ZA's problem?
>
> Get real.

Yes.

Stay general and tell me how you can logically and reasonably say
otherwise... Leave out any specific names.

The original manufacturer of an original product released a patch/upgrade
for their original product. The original product had been modified in this
case by a third party product. The original manufacturer has no
responsibility to test all the possible third party add-ons/changes you can
perform on their product - because they simply would not have the resources
or time to do so - nor is it probably logistically possible/plausible.
Therefore - if a change (critical) is made to the original product and the
third party product no longer functions as the third party vendor said it
would - it is their responsibility to decide whether or not to make it
right.

I responded like this in another location already - if you have someway to
legitimately change that logic around - I would be glad to read. This is
what I wrote earlier - it's repetative in many ways to what I wrote above -
but perhaps seeing it described in a couple of ways will allow more people
to understand the point... And if there is another side to it - perhaps be
able to explain that point of view.

( begin repost )

No offense meant below - honest question...

You have a (potential) problem with an update for the original product you
purchased because you have modified the original product with the addition
of a third party product that has no relation with the manufacturer of the
original product other than the fact they made their product to fit 'on top
of' that original product - and your complaint is with the original product
manufacturer?

Wouldn't your complaint be better received if made to those who made the
third party product you chose to replace the parts of the original product
when you decided you wanted to modify it?

P.S. - I couldn't care less that the specific complaint is about Microsoft,
Chevrolet, Whirlpool or whomever - that is why I left out names in my actual
query completely.

It doesn't matter who made the original product in question - if you chose
to modify it with some third party product and then some
recall/update/upgrade comes out for the original product - do you honestly
believe the manufacturer of the original product should find out every
modification you *could have made* to their product is and make sure their
upgrade/update for their product works with all of those possibilities? Or
would it be more logical to place the responsibility of maintaining the
third party modification to the makers of said modification?

( end repost )

In the end - I believe one could more easily argue the point that it is the
end-users responsibility more than anyone's - as they are the one who made
the conscience choice to change the original product for 'supposed' more
protection with a third party add-ons; and then, when the original product
is changed in some way (by the original manufacturer) and that makes the
original product fail unless the add-on is removed... well - who made the
choice to utilize that product?

But that's a completely different point of view than the one I originally
presented - but one I could see someone taking and being able to defend.

Please - present your point of view and back it up - I would actually like
to hear it because I am finding it difficult to fathom it right now.
Perhaps you have a generalized way of explaining it where I can see your
point of view.

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html



Posted by V Green on July 12, 2008, 5:39 pm
If you were  Registered and logged in, you could reply and use other advanced thread options

> <snipped>
>
> PA Bear [MS MVP] wrote:
> > So Windows must be compatible with ZA and any other third-party
> > application, not the other way around?
>
> V Green wrote:
> > Why not?
> >
> > ZA WORKED before the update. The update BROKE it.
> > So it's ZA's problem?
> >
> > Get real.
>
> Yes.
>
> Stay general and tell me how you can logically and reasonably say
> otherwise... Leave out any specific names.
>
> The original manufacturer of an original product released a patch/upgrade
> for their original product. The original product had been modified in this
> case by a third party product. The original manufacturer has no
> responsibility to test all the possible third party add-ons/changes you can
> perform on their product - because they simply would not have the resources
> or time to do so - nor is it probably logistically possible/plausible.
> Therefore - if a change (critical) is made to the original product and the
> third party product no longer functions as the third party vendor said it
> would - it is their responsibility to decide whether or not to make it
> right.


Sorry, but no. I don't screw over MY customer base that way.
If you choose to live life doing that sort of stuff, then
we must just agree to disagree.

And good luck with customer loyalty...wait a sec, Windows
is a monopoly. Happy Customers, what are those??? They don't
have a choice (go ahead and argue that if you wish, you KNOW
it's true and I won't respond to it) so what do we care about their "user
experience"?



>
> I responded like this in another location already - if you have someway to
> legitimately change that logic around - I would be glad to read. This is
> what I wrote earlier - it's repetative in many ways to what I wrote above -
> but perhaps seeing it described in a couple of ways will allow more people
> to understand the point... And if there is another side to it - perhaps be
> able to explain that point of view.
>
> ( begin repost )
>
> No offense meant below - honest question...
>
> You have a (potential) problem with an update for the original product you
> purchased because you have modified the original product with the addition
> of a third party product that has no relation with the manufacturer of the
> original product other than the fact they made their product to fit 'on top
> of' that original product - and your complaint is with the original product
> manufacturer?
>
> Wouldn't your complaint be better received if made to those who made the
> third party product you chose to replace the parts of the original product
> when you decided you wanted to modify it?
>
> P.S. - I couldn't care less that the specific complaint is about Microsoft,
> Chevrolet, Whirlpool or whomever - that is why I left out names in my actual
> query completely.
>
> It doesn't matter who made the original product in question - if you chose
> to modify it with some third party product and then some
> recall/update/upgrade comes out for the original product - do you honestly
> believe the manufacturer of the original product should find out every
> modification you *could have made* to their product is and make sure their
> upgrade/update for their product works with all of those possibilities? Or
> would it be more logical to place the responsibility of maintaining the
> third party modification to the makers of said modification?
>
> ( end repost )
>
> In the end - I believe one could more easily argue the point that it is the
> end-users responsibility more than anyone's - as they are the one who made
> the conscience choice to change the original product for 'supposed' more
> protection with a third party add-ons; and then, when the original product
> is changed in some way (by the original manufacturer) and that makes the
> original product fail unless the add-on is removed... well - who made the
> choice to utilize that product?
>
> But that's a completely different point of view than the one I originally
> presented - but one I could see someone taking and being able to defend.
>
> Please - present your point of view and back it up - I would actually like
> to hear it because I am finding it difficult to fathom it right now.
> Perhaps you have a generalized way of explaining it where I can see your
> point of view.
>
> --
> Shenan Stanley
> MS-MVP
> --
> How To Ask Questions The Smart Way
> http://www.catb.org/~esr/faqs/smart-questions.html
>
>



Similar ThreadsPosted
Re: FIX for ZoneAlarm & KB951748 issue released July 10, 2008, 11:54 am
RE: FIX for ZoneAlarm & KB951748 issue released July 12, 2008, 12:32 pm
Re: FIX for ZoneAlarm & KB951748 issue released July 12, 2008, 4:03 pm
Re: FIX for ZoneAlarm & KB951748 issue released July 13, 2008, 12:33 am
Re: FIX for ZoneAlarm & KB951748 issue released July 14, 2008, 11:32 pm
WMP & ZONEALARM October 24, 2005, 4:52 pm
ZoneAlarm July 16, 2008, 1:26 pm
Use of ZoneAlarm February 15, 2009, 12:20 am
ZoneAlarm Configuration Help June 21, 2005, 1:51 pm
Re: IE bypasses Zonealarm August 28, 2007, 2:17 am

The site map in XML format XML site map

Contact Us | Privacy Policy