My friend's computer originally came with Windows ME, and a Phoenix 6.00
PG, dated 01/07/2003 BIOS. The problem is that there appears to be a
short delay (under a second) between clicking the mouse and getting a
response. The pointer on the screen immediately follows the mouse as I
roll it around, and scrolling in response to the middle wheel is okay.

It's very annoying, particularly on one solitaire game I play. If I
rapidly double-click on an series of cards to be moved, none of them
move until a short time after my last double-click. It's like something
in the system is storing all my rapid series of double-clicks, and
waiting for a period of inactivity before executing each of the "stored"
double-clicks.

In Control/Panel/Mouse, the double-click speed Test is okay.

I've changed OS to W2K Pro, and updated the video and 4-in-1 chip
drivers; same problem. I haven't touched the BIOS. Could it be the problem?

Thanks,

Ray

I would doubt it
You have presumably tried changing the various mouse settings?

"Ray K" <(E-Mail Removed)> wrote in message
news:490fe2dc$0$4877$(E-Mail Removed)...
> My friend's computer originally came with Windows ME, and a Phoenix 6.00
> PG, dated 01/07/2003 BIOS. The problem is that there appears to be a short
> delay (under a second) between clicking the mouse and getting a response.
> The pointer on the screen immediately follows the mouse as I roll it
> around, and scrolling in response to the middle wheel is okay.
>
> It's very annoying, particularly on one solitaire game I play. If I
> rapidly double-click on an series of cards to be moved, none of them move
> until a short time after my last double-click. It's like something in the
> system is storing all my rapid series of double-clicks, and waiting for a
> period of inactivity before executing each of the "stored" double-clicks.
>
> In Control/Panel/Mouse, the double-click speed Test is okay.
>
> I've changed OS to W2K Pro, and updated the video and 4-in-1 chip drivers;
> same problem. I haven't touched the BIOS. Could it be the problem?
>
> Thanks,
>
> Ray
>
>

DL wrote:
> I would doubt it
> You have presumably tried changing the various mouse settings?
>
Yes, I did via Control/Panel/Mouse, and the double-click speed test.

> "Ray K" <(E-Mail Removed)> wrote in message
> news:490fe2dc$0$4877$(E-Mail Removed)...
>
>> My friend's computer originally came with Windows ME, and a Phoenix 6.00
>> PG, dated 01/07/2003 BIOS. The problem is that there appears to be a short
>> delay (under a second) between clicking the mouse and getting a response.
>> The pointer on the screen immediately follows the mouse as I roll it
>> around, and scrolling in response to the middle wheel is okay.
>>
>> It's very annoying, particularly on one solitaire game I play. If I
>> rapidly double-click on an series of cards to be moved, none of them move
>> until a short time after my last double-click. It's like something in the
>> system is storing all my rapid series of double-clicks, and waiting for a
>> period of inactivity before executing each of the "stored" double-clicks.
>>
>> In Control/Panel/Mouse, the double-click speed Test is okay.
>>
>> I've changed OS to W2K Pro, and updated the video and 4-in-1 chip drivers;
>> same problem. I haven't touched the BIOS. Could it be the problem?
>>
>> Thanks,
>>
>> Ray
>>
>>
>>
>
>
>

"Ray K" <(E-Mail Removed)> wrote in message
news:490fe2dc$0$4877$(E-Mail Removed)...
> My friend's computer originally came with Windows ME, and a Phoenix 6.00
> PG, dated 01/07/2003 BIOS. The problem is that there appears to be a
> short delay (under a second) between clicking the mouse and getting a
> response. The pointer on the screen immediately follows the mouse as I
> roll it around, and scrolling in response to the middle wheel is okay.
>
> It's very annoying, particularly on one solitaire game I play. If I
> rapidly double-click on an series of cards to be moved, none of them
> move until a short time after my last double-click. It's like something
> in the system is storing all my rapid series of double-clicks, and
> waiting for a period of inactivity before executing each of the "stored"
> double-clicks.
>
> In Control/Panel/Mouse, the double-click speed Test is okay.
>
> I've changed OS to W2K Pro, and updated the video and 4-in-1 chip
> drivers; same problem. I haven't touched the BIOS. Could it be the
problem?
>
> Thanks,
>
> Ray
>
>

Not likely to have anything to do with the bios

try a different mouse

philo wrote:
> "Ray K" <(E-Mail Removed)> wrote in message
> news:490fe2dc$0$4877$(E-Mail Removed)...
>> My friend's computer originally came with Windows ME, and a Phoenix 6.00
>> PG, dated 01/07/2003 BIOS. The problem is that there appears to be a
>> short delay (under a second) between clicking the mouse and getting a
>> response. The pointer on the screen immediately follows the mouse as I
>> roll it around, and scrolling in response to the middle wheel is okay.
>>
>> It's very annoying, particularly on one solitaire game I play. If I
>> rapidly double-click on an series of cards to be moved, none of them
>> move until a short time after my last double-click. It's like something
>> in the system is storing all my rapid series of double-clicks, and
>> waiting for a period of inactivity before executing each of the "stored"
>> double-clicks.
>>
>> In Control/Panel/Mouse, the double-click speed Test is okay.
>>
>> I've changed OS to W2K Pro, and updated the video and 4-in-1 chip
>> drivers; same problem. I haven't touched the BIOS. Could it be the
> problem?
>> Thanks,
>>
>> Ray
>>
>>
>
> Not likely to have anything to do with the bios
>
> try a different mouse

Same problem.

>> Not likely to have anything to do with the bios
>>
>> try a different mouse
>
> Same problem.

I wonder if the type of mouse connection could be the problem. The
problem computer uses an optical, 2-button, wired wheel mouse connected
to a USB connector, but the port is not USB2. Mouse software is whatever
comes with W2K.

"Ray K" <(E-Mail Removed)> wrote in message
news:49133af5$0$4911$(E-Mail Removed)...
> >> Not likely to have anything to do with the bios
> >>
> >> try a different mouse
> >
> > Same problem.
>
> I wonder if the type of mouse connection could be the problem. The
> problem computer uses an optical, 2-button, wired wheel mouse connected
> to a USB connector, but the port is not USB2. Mouse software is whatever
> comes with W2K.

Well I don't know what the problem is.
a mouse should definitely not require USB2

philo wrote:
> "Ray K" <(E-Mail Removed)> wrote in message
> news:49133af5$0$4911$(E-Mail Removed)...
>>>> Not likely to have anything to do with the bios
>>>>
>>>> try a different mouse
>>> Same problem.
>> I wonder if the type of mouse connection could be the problem. The
>> problem computer uses an optical, 2-button, wired wheel mouse connected
>> to a USB connector, but the port is not USB2. Mouse software is whatever
>> comes with W2K.
>
> Well I don't know what the problem is.
> a mouse should definitely not require USB2

.... but it would be interesting to see what happens with a PS2 mouse.