Francis GALIEGUE wrote:
> 


> > 2. The second computer I installed to (IBM Aptiva AMD K-6/2 350 with an
> > onboard ATI RAGE pro 4MB video card and an old 14" Sony monitor) flips
> > out when you use the screen saver.  The screensaver comes on just fine,
> > but after a few minutes, it starts to move really fast and just starts
> > scrambling the screen or it will just go black.  When you move the mouse
> > or hit a key, it comes back.  Weird?
> >
> 
> The screen going blank after a certain time is no mystery, as the Mach64
> server supports DPMS. But the other porblem looks strange - does it do the
> same thing with all screensavers or just some screensavers in
> particular?

I've been playing with different screen savers and it seems to only do
that with the 'matrix' screensaver.

> 
> > 3. I was able to use imwheel with
> my logitech trackball on Mandrake > 7.0-2 with the following adjustments:
> >
> > 1. edit XF86Config pointer section adding the lines:
> >       Buttons  3
> >       ZAxisMapping 4 5
> > and commenting out the lines:
> > emulate3Buttons
> > emulate3timeout
> >
> 
> Yes, this is a bug - longstanding even. If you don't select the correct
> mouse type, it's always considered a 2-button mouse and basta. I'll try
> and implement a mouse autodetection tool some time after One Week(tm) but
> it won't make it into 7.1 anyway :(
> 
> > 2. put a copy of /etc/imwheelrc into the /home/$user file
> >
> > 3. put a copy of /usr/X11R6/bin/imwheel into the autostart folder
> >
> 
> Huh? imwheel is called from startx! Has someone reverted my changes ?

Got it!  I was following the same procedure that I had to for 7.0-2 but
when I reconfigured my mouse (mousedrake) and took the imwheel copy out
of my autostart folder, it started working.
Same problem with numlock; for some reason, when I installed 7.1b, it
put a copy of enable_X11_numlock in my autostart folder which was
actually killing my numlock in X.  Took that out of the autostart folder
and now numlock stays on in KDE.
> 
> > Now after trying that in 7.1b, nothing happens.  Could you tell me
> > what's changed? I see that there are two XF86Config files now, which one
> > should I change?  I noticed that the format of the XF86Config4 file
> > looked a little different than the standard, does that make a
> > difference?
> >
> > Thanks for all the hard work; overall, I think it looks awesome!
> >
> > Mike
> > [EMAIL PROTECTED]
> >
> 
> --
> fg
> 
> "You can tune a filesystem but you can't tuna fish" (HP/UX' fsck manpage)

-- 
=========================================
The Penguins are coming!!!
=========================================
Michael Holt
[EMAIL PROTECTED]
Kirkland, WA.

Reply via email to