Jim Richardson :
> On Tue, 2 May 2006 23:36:56 -0500,
> Erik Funkenbusch <erik@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>> On Tue, 2 May 2006 19:08:11 -0700, Jim Richardson wrote:
>>>> So you're going to blame hardware failur on Windows. Typical. Say
>>>> anything, even if it's not true, to support your pet OS.
>>> you proceed from claiming that it "sounds like a hardware problem"
>>> straight to chastising Roy for blaming MS-Windows "for a hardware
>>> Why don't we wait and see if it actually *is* a hardware problem before
>>> we give MS-Windows a bye on this m'kay?
>> As opposed to instantly blaming it?
> Since you are at least one person more removed from the incident in
> question than Roy, I'll listen to him, more than you.
> Is it a hardware problem? unknown, could it be? yes, could it be
> MS-Windows borking ? yes.
> I just note with amusement, your immediate leap into MS-Protect mode.
I hate my position at the moment, but as described it sounds like a
SMART drive complaint, which would be hardware. I've seen Windows break
a million times, but this doesn't sound like a Windows breakage or
filesystem gone south. Sounds like hardware.
No one wants war.
-- Kirk, "Errand of Mercy", stardate 3201.7