From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu From: Adrian Tritschler Message-ID: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <45e22e468ef7fee73c6fdab5bf945f7e@plan9.bell-labs.com> Subject: Re: [9fans] Mouse cursor is too large. Date: Thu, 3 Oct 2002 08:46:47 +0000 Topicbox-Message-UUID: fbe994a8-eaca-11e9-9e20-41e7f4b1d025 Russ Cox wrote: > You're right -- there's only one switch in s3load. > There used to be identical redundant ones. I forgot > that the second got replaced by the dolock variable. Phew, I'm not going crazy. 8904 seems to be the ID for the S3 83C366, but adding it to vgas3.c doesn't make any difference. > When you move the mouse over a window border, > does the cursor change at all? (On a system with a > working cursor, the cursor changes to indicate that > you can drag the window border to resize the window.) Yep, I always get the correct cursor, it changes when it should, its just that it is the top-left 16x16 pixels in the 64x64 block of noise. The remaining block never changes. I'm guesing that somewhere there is a registry setting for a 64x64 hardware cursor, and it was never initialised to all be transparent. Um, as asci-fied below. + is the cursor, the spaces are transparent, X is the black and white noise. +X X X X Adrian --------------------------------------------------------------- Adrian Tritschler mailto:Adrian.Tritschler@its.monash.edu.au ---------------------------------------------------------------