Julian said:
There's no such thing as "Microsoft Mail."
Pardon me. "Windows Mail." I feel all better about my Outbox being frozen
now that I've been properly admonished.
Why not?
Help us help you by describing the symptoms.
What error message do you get?
That was precisely the problem - I didn't get an error message. Just the
same old same old.
That last file in the Outbox finally cleared, I assume that the utility
cleared it.
I don't know. Have you asked them?
I just started having the problem today.
Your use of inaccurate terms such as "Microsoft Mail" tends to undermine
any confidence in any other of your statements.
And your nitpicking attitude undermines my confidence in you. Go "help"
someone else.
You are not helping anyone by ranting at innocent bystanders.
Have you ever written software?
Yes, actually. For pay and everything. In the pharmaceitical industry,
where the sort of malfunctions I've been coping from "Windows Mail" with
would have been cause for an FDA investigation, fines and possible withdrawal
of marketing authorization of whatever product whose safety and efficacy my
code was documenting,
We have this thing in the Pharma information processing community known as
"peer review and validation prior to code lock."
Not ranting at you specifically, but MS ought to either try it or if they do
use such a process (not really evident from the sort of errors MS is famous
for until about "Service Pack 2" or so of their OSes) refine their checklists
to trap and isolate errors of the sort which require third-party tools to
correct a fundamental operating deficiency which corrupts user databases and
causes loss and/or corruption of stored data.
Their current process undermines confidence in their product and makes it
completely understandable why corporate IS managers want to wait until at
least the first Service Pack release before inflicting Vista on their
company's decision support process and other applications for new OSes.
Note.
Your persistent use of inaccuracies such as "Microsoft Mail"
show just how easy it is to ship piss poor code.
It does no such thing.
"Shipping piss poor code," as you put it - and I won't dispute the accuracy
of the term - shows just how deficient Microsoft's internal policies for
quality control are.
It's a sign of vast indifference to the customer that Microsoft leaves
correction of fundamental problems such as loss of data in an Email program
to third parties rather than undertaking the correction itself.
It's ironic that Microsoft is threatening to sue the open-source community
for patent infringements (signifying that the open source community is
swiping important ideas from Redmond) on one hand and adopting that
commuity's methods for maintaining its code on the other.
