> > Not saying that it isn't a HLDM issue, but shit does happen to
> > hardware, even in the best data centers.

> Agreed. If this was something other than hardware (or even plugins)
> you would see this list filled with the same reports. I run dual
> xeon my self and never see win32 console corruption.

Speaking as a programmer myself, and someone who also builds PC and server
Setups for a living I can state 100% there's no hardware fault on my box.

Seems a bold statement, but I belive there's no _FAULT_.

Maybe however there is an incompatabilty.  Lol, I mean, it's not like the
first time software written by valve doesn't work right now is it ;)

I will check all my drivers are up to date (though I'm pretty sure they are
already) and report back.

I still think that if valve had my system and ran a debugger on it they
*would* find a problem with their code and be able to fix it. - Something
that I as a programmer am all to familiar with - "it works here" doesn't
mean your software is bug free.  I once had to install Windows 2000 chinese
edition and use chinese fonts to find the cause of a crash bug in my
software (which actually turned out to be a microsoft richedit problem
rather than a bug in my software) but until I had checked it out and
implemented a work-around there was no way for me to find or recreate the
bug.  Similar things could be happening to valve's software here.

And I also disagree that just because I'm the first to report the bug
doesn't mean I'm the only one suffering from it.  - And I state that though
years of experience dealing with users who just wait for the next version to
see if it's fixed or not without actually reporting the issue.

Thanks,

Dominic Clifton


_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds

Reply via email to