nuts to you microsoft...
04-28-2003, 08:19 AM
#1
It's my first day.
Thread Starter
Join Date: Nov 2001
Location: Grafton, WI.
Posts: 13,635
Likes: 0
Received 0 Likes
on
0 Posts
nuts to you microsoft...
Taken from NTFS.org
A message on the Neohapsis bulletin board said that using Windows Explorer and right clicking on a file gobbles up the CPU to the tune of 100%.
Mark Luczkowski says the problem only happens when you select files with a right click of the mouse, not having selected the file with a left click first.
He says that the problem can be reproduced on both Pentium III and Pentium 4 machines, and we've certainly reproduced it here at the INQUIRER.
Further, Mark has contacted Microsoft, which has told him that it won't fix the problem because it will cause too many changes to critical code paths.
The workaround, apparently, is to left click on the file first before right clicking it. But as the discoverer points out here, that makes the Single Click option in Windows Explorer pretty much redundant.
\
bastards! fix your shitty program.
A message on the Neohapsis bulletin board said that using Windows Explorer and right clicking on a file gobbles up the CPU to the tune of 100%.
Mark Luczkowski says the problem only happens when you select files with a right click of the mouse, not having selected the file with a left click first.
He says that the problem can be reproduced on both Pentium III and Pentium 4 machines, and we've certainly reproduced it here at the INQUIRER.
Further, Mark has contacted Microsoft, which has told him that it won't fix the problem because it will cause too many changes to critical code paths.
The workaround, apparently, is to left click on the file first before right clicking it. But as the discoverer points out here, that makes the Single Click option in Windows Explorer pretty much redundant.
\
bastards! fix your shitty program.
04-28-2003, 08:35 AM
#4
It's my first day.
Thread Starter
Join Date: Nov 2001
Location: Grafton, WI.
Posts: 13,635
Likes: 0
Received 0 Likes
on
0 Posts
Originally posted by reno96teg
um.. doesn't happen with me.. and really, :gives:
even if it did peak to 100%, what would it affect? nothing.
um.. doesn't happen with me.. and really, :gives:
even if it did peak to 100%, what would it affect? nothing.
04-28-2003, 08:37 AM
#5
Moderator
Join Date: Dec 2000
Posts: 21,573
Likes: 0
Received 0 Likes
on
0 Posts
Originally posted by Fujiwara Takumi
it drags the system to a halt.
it drags the system to a halt.
04-28-2003, 09:03 AM
#7
It's my first day.
Thread Starter
Join Date: Nov 2001
Location: Grafton, WI.
Posts: 13,635
Likes: 0
Received 0 Likes
on
0 Posts
Originally posted by Tirod˛slc
wtf? im selecting all kinds of files all the time like pics and shit and that hasnt happened once... inquirer? bish pls...
wtf? im selecting all kinds of files all the time like pics and shit and that hasnt happened once... inquirer? bish pls...
hfawk: its still never happened to me on my p3 laptop with xp pro or my p4 desktop with xp home...
04-28-2003, 09:11 AM
#9
Join Date: Oct 2000
Location: Location Location
Posts: 44,908
Likes: 0
Received 0 Likes
on
0 Posts
Originally posted by reno96teg
um.. doesn't happen with me.. and really, :gives:
even if it did peak to 100%, what would it affect? nothing.
um.. doesn't happen with me.. and really, :gives:
even if it did peak to 100%, what would it affect? nothing.
just tried it on 3 systems. ranging from PIII 833MHz to 1.8GHz Xeon and none of them showed this problem.
the utilization went up to 2% from 1% in one system but that was it.
__________________
'00 Dakar Bus CRS Edition
LCD Squad #0001
'00 Dakar Bus CRS Edition
LCD Squad #0001
Originally Posted by WiLL
...I really wanna get out and shoot people.
04-28-2003, 10:54 AM
#10
Moderator
Join Date: Dec 2000
Posts: 21,573
Likes: 0
Received 0 Likes
on
0 Posts
and, of course, it is expected for cpu usage to go up. after all, it does look to see what kind of file it is, and what menu items it requires. (i.e. an mp3 file will pull up "Play in Winamp.. Enqueue in Winamp..", etc.)