Linked by Thom Holwerda on Mon 27th Aug 2007 22:21 UTC
Thread beginning with comment 266217
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
Linked by Thom Holwerda on 05/15/13 23:03 UTC
Linked by Thom Holwerda on 05/15/13 21:46 UTC
More News »
Sponsored Links



Member since:
2005-07-06
But one would assume that hard coding something as rather stupid, even before this came out - didn't anyone at Microsoft question the decision?
There is the 'Windows Experience Index' - one would have assumed that to create a good experience for the end user they would use the information collected via the benchmarketing process to tweak the scheduler to suite the processor.
For example, information regarding clock speed, memory speed, latency and so forth - all impact on performance of multimedia and thus the schedule should take the information in when setting itself up.
As for me, I haven't seen anything like it yet - then again, I use SonicStage for my media and syncronisation with my MiniDisc player.