Does Microsoft realize they have a major flaw in Windows XP?

Page 3 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.general (More info?)

After reading through what you wrote I do not have that high a power of
parsing what they say. I assume unsupported means "un-worked on." If you
see a distinction there that's a new one on me and I refuse to go down that
road unless Microsoft says the two are different. But I can tell you Donald
I have spoken with Microsoft many times and unsupported means not currently
being "worked on." If it were true as you think. than IMHO Microsoft should
make the distinction for in my book the two are synonymous.

--
George Hester
_________________________________
"Donald McDaniel" <invalid@invalid.com> wrote in message
news:glt3i1hvo9q710djg1r0506aq6u27b5a5k@4ax.com...
> On Fri, 9 Sep 2005 16:29:47 -0400, "George Hester"
> <hesterloli@hotmail.com> wrote:
>
> >"ONE documented example that they are lying to the public when they say
they
> >are working on something...."
> >
> >Would you prefer I give you any 'ole example of a lie. You are not
> >listening. I did not say Microsoft "lied" about anything what I said
here
> >is that unsupported means no more work on the software which is
unsupported.
> >I can provide much documentation that says that. By why should I that is
> >easily arrived at? As for a lie well since I never said anything about a
> >lie but about "unsuppoprted." I really do not see your point. Finally
if I
> >said, "lie" well No. You first.
>
> Let me quote you from a previous post in this thread:
> (From one of your replies to me on Sept 6, 2005, at 1:09 PM)
> "You are wrong. If Microsoft says they are working on the issue you
> can bet your bottom dollar it has been forgotten. Would you like to
> see a Knowledge Base article that discusses an issue in MS-DOS or in
> Internet Information Services 2.0 or Windows NT 3.51 that says the
> exact same thing? No you wouldn't because you think I am making it
> all up. Well so you say."
>
> This surely looks to me as if you are making a BLANKET statement that
> "if Microsoft says they are working on the issue you can bet your
> bottom dollar it has been forgotten." Since you do not modify your
> statement to only characterize unsupported products, I can only take
> you at your own words.
>
> As I said in my last post, it is only common sense that if an article
> was entered into the Knowledge Base before a product was declared
> "Unsupported", and it is no longer supported, it goes without saying
> that they probably stopped working on that issue. Although we don't
> really know that they have truly stopped working on even a product
> which is no longer supported, since we could only know that if
> Microsoft themselves said that the issue was no longer being worked
> on.
>
> Also, many older issues are continuing to be worked on in the newer
> product lines, because the issues are ones which are universal to
> versions of one or more of Microsoft's software products.
>
> Again, you cannot say with any authority that "if Microsoft says they
> are working on the issue, they are lying.", since you are not privy to
> what goes on in the Microsoft software labs. In addition, such a
> statement can easily fit the legal definition of "slander", since you
> have made this statement in a public forum with the intention of
> causing harm to Microsoft's reputation.
>
> If Microsoft wanted to, they could bring you before a court of law,
> and take everything you have if they won the case.
>
> I seriously doubt that Microsoft will do that, since you really do
> very little harm with your baseless accusations, other than rile up a
> few Microsoft bashers and other weak-minded users. However, you are
> spreading "FUD" among new and marginal users, and users with little or
> no knowledge of computers and software. This is never good. Instead,
> you should be giving them accurate knowledge, so they can come
> up-to-speed on XP, and properly maintain their installations.
>
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.general (More info?)

George

No offence or ill will meant. But get your facts and what you are saying straight. Reading all those articles can get to be interpreted wrong. And that is what happened here.

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"George Hester" <hesterloli@hotmail.com> wrote in message news:OgglHvYtFHA.3316@TK2MSFTNGP12.phx.gbl...
> You would have known I meant unsupported when I gave you a list of
> unsupported software. You need to do some background on Microsoft's
> software products over the years. Then you would know that articles that
> say they are working on the issue in Knowledgebase articles about
> unsupported software puts the onus on Microsoft to make a distinction
> between software that is unsupported but they are "still looking into it" or
> unsupported and they are no longer "looking into it."
>
> You don't seem to see the ditinction that's OK. When Microsoft puts the
> same wording in software that they are currently supporting this loss of
> distinction raises questions about the veractiy of what is neing said.
>
> I asked you to give me one example of a Knowledge base article that had the
> wording at the end "Microsoft is looking into it" for which a new or same
> article came out furthering information on what was previously said. Just
> one.
>
> --
> George Hester
> _________________________________
> "Donald McDaniel" <invalid@invalid.com> wrote in message
> news:glt3i1hvo9q710djg1r0506aq6u27b5a5k@4ax.com...
>> On Fri, 9 Sep 2005 16:29:47 -0400, "George Hester"
>> <hesterloli@hotmail.com> wrote:
>>
>> >"ONE documented example that they are lying to the public when they say
> they
>> >are working on something...."
>> >
>> >Would you prefer I give you any 'ole example of a lie. You are not
>> >listening. I did not say Microsoft "lied" about anything what I said
> here
>> >is that unsupported means no more work on the software which is
> unsupported.
>> >I can provide much documentation that says that. By why should I that is
>> >easily arrived at? As for a lie well since I never said anything about a
>> >lie but about "unsuppoprted." I really do not see your point. Finally
> if I
>> >said, "lie" well No. You first.
>>
>> Let me quote you from a previous post in this thread:
>> (From one of your replies to me on Sept 6, 2005, at 1:09 PM)
>> "You are wrong. If Microsoft says they are working on the issue you
>> can bet your bottom dollar it has been forgotten. Would you like to
>> see a Knowledge Base article that discusses an issue in MS-DOS or in
>> Internet Information Services 2.0 or Windows NT 3.51 that says the
>> exact same thing? No you wouldn't because you think I am making it
>> all up. Well so you say."
>>
>> This surely looks to me as if you are making a BLANKET statement that
>> "if Microsoft says they are working on the issue you can bet your
>> bottom dollar it has been forgotten." Since you do not modify your
>> statement to only characterize unsupported products, I can only take
>> you at your own words.
>>
>> As I said in my last post, it is only common sense that if an article
>> was entered into the Knowledge Base before a product was declared
>> "Unsupported", and it is no longer supported, it goes without saying
>> that they probably stopped working on that issue. Although we don't
>> really know that they have truly stopped working on even a product
>> which is no longer supported, since we could only know that if
>> Microsoft themselves said that the issue was no longer being worked
>> on.
>>
>> Also, many older issues are continuing to be worked on in the newer
>> product lines, because the issues are ones which are universal to
>> versions of one or more of Microsoft's software products.
>>
>> Again, you cannot say with any authority that "if Microsoft says they
>> are working on the issue, they are lying.", since you are not privy to
>> what goes on in the Microsoft software labs. In addition, such a
>> statement can easily fit the legal definition of "slander", since you
>> have made this statement in a public forum with the intention of
>> causing harm to Microsoft's reputation.
>>
>> If Microsoft wanted to, they could bring you before a court of law,
>> and take everything you have if they won the case.
>>
>> I seriously doubt that Microsoft will do that, since you really do
>> very little harm with your baseless accusations, other than rile up a
>> few Microsoft bashers and other weak-minded users. However, you are
>> spreading "FUD" among new and marginal users, and users with little or
>> no knowledge of computers and software. This is never good. Instead,
>> you should be giving them accurate knowledge, so they can come
>> up-to-speed on XP, and properly maintain their installations.
>>
>
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.general (More info?)

George,

Ypu are incorrect.
While I cannot disclose the delivery for particular fixes to specific issues
I can say that this is a known issue that is being worked on for delivery to
end users.
--

Regards,

Mike
--
Mike Brannigan [Microsoft]

This posting is provided "AS IS" with no warranties, and confers no
rights

Please note I cannot respond to e-mailed questions, please use these
newsgroups

"George Hester" <hesterloli@hotmail.com> wrote in message
news:%23URvc7xsFHA.2072@TK2MSFTNGP14.phx.gbl...
> You are wrong. If Microsoft says they are working on the issue you can
> bet
> your bottom dollar it has been forgotten. Would you like to see a
> Knowledge
> Base article that discusses an issue in MS-DOS or in Internet Information
> Services 2.0 or Windows NT 3.51 that says the exact same thing? No you
> wouldn't because you think I am making it all up. Well so you say.
>
> --
> George Hester
> _________________________________
> "Donald L McDaniel" <invalid@invalid.com> wrote in message
> news:m7nrh1ptfendg3j6f1ltihnl38n9684b55@4ax.com...
>> On Tue, 6 Sep 2005 12:17:41 -0400, "George Hester"
>> <hesterloli@hotmail.com> wrote:
>>
>> >Reinstall was necessary. Now I just have to figure what happened so
>> >that
> I
>> >don't do it again. But to be honest with you I think it is a flaw in
> this
>> >operating sytem and I am not the first to experience it nor will I be
>> >the
>> >last. Of course with the level of feedback I received by my post I can
>> >understand why the issue will likely never be fixed. Out all who took
> the
>> >time to respond I wish to extend my thanks to Jon. Jon we need more
>> >like
>> >you here.
>>
>> I'm really sorry you didn't like the truth, my friend. That's all I
>> have to give. If Microsoft says they are working on the issue, they
>> are, you can bet on it.
>>
>> Donald L McDaniel
>> Please reply to the original thread.
>> If you must reply via email, remove the obvious
>> from my email address before sending.
>> =======================================================
>
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.general (More info?)

Tell you what Mike let's put our money where our mouths are. I would like
to bet you that that article will not be updated by the time Windows
Longhorn whatver its name becomes is released to the retail market. $20.00
US. If it is updated before Longhorn comes out I will pay you $20.00. If
is not you owe me $20.00. Deal?

--
George Hester
_________________________________
"Mike Brannigan [MSFT]" <mikebran@online.microsoft.com> wrote in message
news:ONw3UOatFHA.3500@TK2MSFTNGP09.phx.gbl...
> George,
>
> Ypu are incorrect.
> While I cannot disclose the delivery for particular fixes to specific
issues
> I can say that this is a known issue that is being worked on for delivery
to
> end users.
> --
>
> Regards,
>
> Mike
> --
> Mike Brannigan [Microsoft]
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights
>
> Please note I cannot respond to e-mailed questions, please use these
> newsgroups
>
> "George Hester" <hesterloli@hotmail.com> wrote in message
> news:%23URvc7xsFHA.2072@TK2MSFTNGP14.phx.gbl...
> > You are wrong. If Microsoft says they are working on the issue you can
> > bet
> > your bottom dollar it has been forgotten. Would you like to see a
> > Knowledge
> > Base article that discusses an issue in MS-DOS or in Internet
Information
> > Services 2.0 or Windows NT 3.51 that says the exact same thing? No you
> > wouldn't because you think I am making it all up. Well so you say.
> >
> > --
> > George Hester
> > _________________________________
> > "Donald L McDaniel" <invalid@invalid.com> wrote in message
> > news:m7nrh1ptfendg3j6f1ltihnl38n9684b55@4ax.com...
> >> On Tue, 6 Sep 2005 12:17:41 -0400, "George Hester"
> >> <hesterloli@hotmail.com> wrote:
> >>
> >> >Reinstall was necessary. Now I just have to figure what happened so
> >> >that
> > I
> >> >don't do it again. But to be honest with you I think it is a flaw in
> > this
> >> >operating sytem and I am not the first to experience it nor will I be
> >> >the
> >> >last. Of course with the level of feedback I received by my post I
can
> >> >understand why the issue will likely never be fixed. Out all who took
> > the
> >> >time to respond I wish to extend my thanks to Jon. Jon we need more
> >> >like
> >> >you here.
> >>
> >> I'm really sorry you didn't like the truth, my friend. That's all I
> >> have to give. If Microsoft says they are working on the issue, they
> >> are, you can bet on it.
> >>
> >> Donald L McDaniel
> >> Please reply to the original thread.
> >> If you must reply via email, remove the obvious
> >> from my email address before sending.
> >> =======================================================
> >
>
>
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.general (More info?)

"George Hester" <hesterloli@hotmail.com> wrote in message
news:eekfn2CuFHA.2064@TK2MSFTNGP09.phx.gbl...
> Tell you what Mike let's put our money where our mouths are. I would like
> to bet you that that article will not be updated by the time Windows
> Longhorn whatver its name becomes is released to the retail market.
> $20.00
> US. If it is updated before Longhorn comes out I will pay you $20.00. If
> is not you owe me $20.00. Deal?
>

George,

I did not say the article was going to be updated.
I said that according to our internal version of it - the issues is
scheduled to be fixed and that fix released some time in the future. I
cannot however discuss in a public newsgroup the timescales for this or the
proposed release method.

--

Regards,

Mike
--
Mike Brannigan [Microsoft]

This posting is provided "AS IS" with no warranties, and confers no
rights

Please note I cannot respond to e-mailed questions, please use these
newsgroups

"George Hester" <hesterloli@hotmail.com> wrote in message
news:eekfn2CuFHA.2064@TK2MSFTNGP09.phx.gbl...
> Tell you what Mike let's put our money where our mouths are. I would like
> to bet you that that article will not be updated by the time Windows
> Longhorn whatver its name becomes is released to the retail market.
> $20.00
> US. If it is updated before Longhorn comes out I will pay you $20.00. If
> is not you owe me $20.00. Deal?
>
> --
> George Hester
> _________________________________
> "Mike Brannigan [MSFT]" <mikebran@online.microsoft.com> wrote in message
> news:ONw3UOatFHA.3500@TK2MSFTNGP09.phx.gbl...
>> George,
>>
>> Ypu are incorrect.
>> While I cannot disclose the delivery for particular fixes to specific
> issues
>> I can say that this is a known issue that is being worked on for delivery
> to
>> end users.
>> --
>>
>> Regards,
>>
>> Mike
>> --
>> Mike Brannigan [Microsoft]
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights
>>
>> Please note I cannot respond to e-mailed questions, please use these
>> newsgroups
>>
>> "George Hester" <hesterloli@hotmail.com> wrote in message
>> news:%23URvc7xsFHA.2072@TK2MSFTNGP14.phx.gbl...
>> > You are wrong. If Microsoft says they are working on the issue you can
>> > bet
>> > your bottom dollar it has been forgotten. Would you like to see a
>> > Knowledge
>> > Base article that discusses an issue in MS-DOS or in Internet
> Information
>> > Services 2.0 or Windows NT 3.51 that says the exact same thing? No you
>> > wouldn't because you think I am making it all up. Well so you say.
>> >
>> > --
>> > George Hester
>> > _________________________________
>> > "Donald L McDaniel" <invalid@invalid.com> wrote in message
>> > news:m7nrh1ptfendg3j6f1ltihnl38n9684b55@4ax.com...
>> >> On Tue, 6 Sep 2005 12:17:41 -0400, "George Hester"
>> >> <hesterloli@hotmail.com> wrote:
>> >>
>> >> >Reinstall was necessary. Now I just have to figure what happened so
>> >> >that
>> > I
>> >> >don't do it again. But to be honest with you I think it is a flaw in
>> > this
>> >> >operating sytem and I am not the first to experience it nor will I be
>> >> >the
>> >> >last. Of course with the level of feedback I received by my post I
> can
>> >> >understand why the issue will likely never be fixed. Out all who
>> >> >took
>> > the
>> >> >time to respond I wish to extend my thanks to Jon. Jon we need more
>> >> >like
>> >> >you here.
>> >>
>> >> I'm really sorry you didn't like the truth, my friend. That's all I
>> >> have to give. If Microsoft says they are working on the issue, they
>> >> are, you can bet on it.
>> >>
>> >> Donald L McDaniel
>> >> Please reply to the original thread.
>> >> If you must reply via email, remove the obvious
>> >> from my email address before sending.
>> >> =======================================================
>> >
>>
>>
>