Quote:
|
Originally Posted by cmac2012
Years ago, before ol' Ma Bell was broken up, they came out with an ad campaign slogan which idle malcontents cruelly twisted for their own nefarious ends and put it on bumperstickers. It could work for Microsoft as well:
We're Microsoft. We don't care. We don't have to.
The original slogan was the same only in the affirmative starting with: We're the phone company....
|
I'm not sure what their response level is. I've had several cases over the years that earned me tech documents created by MS. Every one of the tech documents conveniently omitted crucial details necessary to diagnose and resolve the stated problem. This is still their pattern.
A short story: several years ago a Dell server would spontaneously reboot while running a backup used with NT4’s ntbackup program. I first worked with Dell, and replaced every component in the server, then did a ground up rebuild of the OS, and the problem persisted. I turned to Microsoft and spent about 30 hours with them. No solution. And I stopped using the $2,300 backup drive. A year later I was talking with another MS support tech about it while on another topic. They did some research and suggested looking for a file with a pipe character in the file name “|” I found such a file and renamed it. The tape backup worked reliably ever after. Now there is
NO WAY a backup program should ever interpret a file name as anything but a name, but for reasons never explained, and never resolved through the NT4 product cycle, it remained a problem. Sounds hauntingly familiar to the xcopy issue mentioned above. Thanks MS!
