Problem with XP scheduler?
in [Win32 Kernel]
|
From: J de Boyne Pollard on 26 Dec 2009 09:13 DB> As far as the insults at the end, [...] M. Burn, M. Davidson, M. Grigoriev, M. Craig: You are being trolled. Unmistakable Marks #2, #4, and #5 are now in evidence, as well as some other tell-tales. <URL:http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/ unmistakable-marks.html> The best course of action for grownups is to ignore the ad hominem baloney. Remember that it's no reflection upon you when someone starts an ad hominem argument, even if the ad hominems are aimed at you. It's only a bad reflection on the fool making the ad hominems. Other people will and do easily recognize such arguments for the attempts to distract that they are, and won't give credence to insults from fools, especially when they are clearly risible. Let's please concentrate upon threads where people are *not* here just to waste everyone's time. You actually had it right the first time, M. Craig.
From: Tim Roberts on 26 Dec 2009 17:44 "Boba" <Boba(a)somewhere.net> wrote: >"Pavel A." <pavel_a(a)12fastmail34.fm> wrote: >> ... >> "Rest of the system" includes 3rd party drivers (video is especially >> troublesome, but others as well), for which you can not blame MS. > >and Pavel, do not forget, please, that it is ms who charges >tons of money for those drivers to be tested properly. Microsoft (WHQL) does not test 3rd-party drivers. Vendor test the drivers and submitting the passing test logs. Microsoft validates them and issues the appropriate certificate. Plus, $250 per operating system does not seem like "tons of money". It would be better for everyone involved here if you would stop speaking out on topics where your entire knowledge is based on rumor and baseless innuendo. -- Tim Roberts, timr(a)probo.com Providenza & Boekelheide, Inc.
From: tanix on 26 Dec 2009 22:25 In article <u94dj59h155v95p0lfnnpqic44t22ddckm(a)4ax.com>, Tim Roberts <timr(a)probo.com> wrote: > >"Boba" <Boba(a)somewhere.net> wrote: > >>"Pavel A." <pavel_a(a)12fastmail34.fm> wrote: >>> ... >>> "Rest of the system" includes 3rd party drivers (video is especially >>> troublesome, but others as well), for which you can not blame MS. >> >>and Pavel, do not forget, please, that it is ms who charges >>tons of money for those drivers to be tested properly. > >Microsoft (WHQL) does not test 3rd-party drivers. Vendor test the drivers >and submitting the passing test logs. Microsoft validates them and issues >the appropriate certificate. Plus, $250 per operating system does not seem >like "tons of money". > >It would be better for everyone involved here if you would stop speaking >out on topics where your entire knowledge is based on rumor and baseless >innuendo. It would be probably be even better if you just mind your own busniess instead of telling others "how it is". -- Programmer's Goldmine collections: http://preciseinfo.org Tens of thousands of code examples and expert discussions on C++, MFC, VC, ATL, STL, templates, Java, Python, Javascript, organized by major topics of language, tools, methods, techniques.
From: Grzegorz Wróbel on 27 Dec 2009 07:29 Tim Roberts wrote: > > Get real. A software problem cannot cause your machine to lock up so hard > that even mouse and keyboard stop. Get rational. User mode app can lock up mouse and keyboard just by starving system processes that manage mouse and keyboard input. On the single CPU/core machines it was very common to happen. On the multi core machines much less likely to happen "naturally", but still possible. -- Grzegorz Wr�bel 677265676F727940346E6575726F6E732E636F6D
From: tanix on 27 Dec 2009 09:18
In article <hh7khh$1fb$1(a)nemesis.news.neostrada.pl>, =?ISO-8859-1?Q?Grzegorz_Wr=F3bel?= </dev/null(a)localhost.localdomain> wrote: >Tim Roberts wrote: >> >> Get real. A software problem cannot cause your machine to lock up so hard >> that even mouse and keyboard stop. > > >Get rational. User mode app can lock up mouse and keyboard just by >starving system processes that manage mouse and keyboard input. On the >single CPU/core machines it was very common to happen. On the multi core >machines much less likely to happen "naturally", but still possible. That means your OS is not trully multitasking. -- Programmer's Goldmine collections: http://preciseinfo.org Tens of thousands of code examples and expert discussions on C++, MFC, VC, ATL, STL, templates, Java, Python, Javascript, organized by major topics of language, tools, methods, techniques. |