__/ [ Jeanette Russo ] on Thursday 26 April 2007 04:29 \__
> Tom Wiley wrote:
>> A question for any MS gurus visiting here.
>>
>> When I am running a program in XP and the program blows up in my face, it
>> doesn't give me a log, or searchable error code, or anything that might
>> help me to work around the problem. But it apologises very politely and
>> offers to tell MicroSoft about the problem. My question is, what is the
>> average time it takes for a MS rep to get back to the user with a fix?
>>
>> In my case, it has been two weeks and I am still waiting. Should I send
>> the error in again?
Why wait? Follow the routine you'll be advised to attempt.
(1) Stop and start the program
(2) Log in and log out again
(3) Reboot the machine
(4) Reinstall the application again
(5) Reinstall the operating system
(6) Dance naked around the machine, waving a rubber chicken
(7) "Take your machine back for servicing"
> Your joking right?
I think he is, but the first paragraph is deceiving. I can recall collecting
feedback about error codes that somehow get translated into a verbal
description. Why even give codes rather than descriptions? Maybe it's
intended to give jobs to support people who can do a lookup in some table
and heroically declare that they can fix the issue. In many issue, the fix
is to revert back to defaults in one way or another, as the above indicates.
It's lossy, time consuming, and it gives the user absoluely no clue as to
how the issue can be resolved for good, rather than recur.
--
~~ With kind regards
Roy S. Schestowitz | Othello for free: http://othellomaster.com
http://Schestowitz.com | RHAT Linux | PGP-Key: 0x74572E8E
5:05am up 11 days 4:33, 5 users, load average: 0.48, 1.29, 1.42
http://iuron.com - Open Source knowledge engine project
|
|
