Tuesday, November 29, 2005

and today's bash at microsoft is . . .

. . . Unspecified error!

AAARG!

i don't know who's idea at microsoft it was to make the Unspecified error error message, but whoever it was should be shot... it's coming up everwhere and is totally useless... there is no diagnostic information... there isn't even anything to uniquely identify the error condition, searching for "Unspecified error" reveals that it's returned in all sorts of microsoft products under all sorts of different conditions... it's virtually impossible to narrow down the cause of the error i'm facing because it's so difficult to uniquely identify the error itself...

microsoft, you suck...

No comments: