From: Pavel A. on
"Tim Roberts" <timr(a)probo.com> wrote in message
news:kcmti5h5t6k7pj9mhh519e76mgheppmg9s(a)4ax.com...
> tanix(a)mongo.net (tanix) wrote:
>>
>>What happens is box totally freezes. Task manager ->
>>Performance tab shows one of cores going up to 100% CPU time,
>>mouse freezes, keyboard does not work (not even ctl-alt-del)
>>and disk stops flashing every few seconds as it normally does
>>under XP.
>>
>>Interestingly enough, it does not happen under Windows 7 on
>>the same box no matter how hard I try.
>>
>>Some say it is a problem with crappy XP scheduler.
>>Is there anything I can do under XP to fix this issue?
>
> Get real. A software problem cannot cause your machine to lock up so hard
> that even mouse and keyboard stop. The likely issues are (1) RAM problem,
> (2) graphics driver problem, or (3) USB controller problem (if you have
> USB
> mouse).

The graphic driver and usb driver are software. Win7 has different (better?)
drivers.
-- pa


--
> Tim Roberts, timr(a)probo.com
> Providenza & Boekelheide, Inc.

From: Alexander Grigoriev on

"tanix" <tanix(a)mongo.net> wrote in message
news:hgmhad$sd$2(a)news.eternal-september.org...
> But...
>
> For some strange reason, there is no such a concept in Linux
> as viruses or trojans.
>

Because nobody bothers. Thojans are installed using old good social
engineering (install this codec to play the pron videos!), and Unix/Linux is
not going to make people less stupid than they are in mass.

> When my box was rooted with the "latest and greatest" rootkit,
> that was as sophisticated as I have EVER seen anything,
> and after me, trying to recover for it for few days, thanx
> to my monitoring firewall, the more I was digging into it,
> the more my hairs rose as I began to realize that even if
> i reformat my drive, it won't help anything. The rootkit
> is still there.
>

Here is a simple recipe for you (it worked for me for many years): DON'T run
with administrative privileges. DON'T give admin password to non-qualified
people.


From: Boba on
"Tim Roberts" <timr(a)probo.com> wrote in message
news:kcmti5h5t6k7pj9mhh519e76mgheppmg9s(a)4ax.com...
> ...
> A software problem cannot cause your machine to lock up so hard
> that even mouse and keyboard stop.

lol...u'gotto'bekidding...
even some software written by professionals from MicroSoft
not just can do that but also _does_ it, and does it on a
regular basis with _every_ single version of Windows with
no exception so far. Mr. Roberts, please, do not fool the
audience, we do respect your opinion... Boba TC


From: Don Burn on
And where is your data on this? Microsoft classifies crashes and hangs on a
regular basis and presents it a driver conferences since it has been driver
problems that cause this, not applications. Tim Roberts is a highly
experienced windows developer, please show your data, since the only
published data I know of contradicts you.


--
Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply


"Boba" <Boba(a)somewhere.net> wrote in message
news:uhyQMswgKHA.5460(a)TK2MSFTNGP06.phx.gbl...
> "Tim Roberts" <timr(a)probo.com> wrote in message
> news:kcmti5h5t6k7pj9mhh519e76mgheppmg9s(a)4ax.com...
>> ...
>> A software problem cannot cause your machine to lock up so hard
>> that even mouse and keyboard stop.
>
> lol...u'gotto'bekidding...
> even some software written by professionals from MicroSoft
> not just can do that but also _does_ it, and does it on a
> regular basis with _every_ single version of Windows with
> no exception so far. Mr. Roberts, please, do not fool the
> audience, we do respect your opinion... Boba TC
>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 4708 (20091222) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>



__________ Information from ESET NOD32 Antivirus, version of virus signature database 4708 (20091222) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com




From: Alexander Grigoriev on

"Leo Davidson" <leonudeldavidson(a)googlemail.com> wrote in message
news:da4e6a99-fc5b-432d-bb23-81329d14289f(a)v30g2000yqm.googlegroups.com...
A weird, and completely rule (happened to several people), example I
know if is where people copying data with one program found their
files were corrupted. People blamed the program at first but on
investigation it turned out to be the system bus drivers. The reason

I once had a Intel motherboard which produced _memory_ errors _only_ if disk
IO was performed in parallel. The memory errors were not in IO buffers. Of
course, standalone test like memtest86 would not find that.