Linux-Hardware Digest #726, Volume #9 Fri, 19 Mar 99 08:15:31 EST
Contents:
SB16PnP-How? (eric malloy)
Re: CM8330 sound card (Efraim Wainerman)
Q: PCMCIA support (network, modem & SCSI) under Linux 2.0.36 or 2.2.3??? (Vladimir
NOVIKOV)
Re: For all you Nicrosoft lovers (doole)
Toshiba Satellite 4005CDS & Serial I/O Woes (Hugh McCurdy)
Re: "Select the application, and then the platform" ("Tom Emerson")
Soundcard problems (Joost de Heer)
Re: Parameters for an old Canon hard drive ("Michael W. Ryder")
Re: failure to find floppy controller ("B. Collins")
Re: Microsoft Serial Mouse 2.0a! DO NOT READ THIS! ("Charles Sullivan")
Re: X munges the graphics card? (Re: Windows 2000 Rah! Rah! Session falls flat)
(Steffen Kluge)
Re: Dual Pentium II support. (Phil Brutsche)
Parameters for an old Canon hard drive ("Peter B. Yorke")
Red Hat vs. Calder nic (John Heppner)
----------------------------------------------------------------------------
From: eric malloy <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux,comp.os.linux.misc
Subject: SB16PnP-How?
Date: 19 Mar 1999 07:48:20 GMT
How do I setup my Sound Blaster PnP 16.. i got this info about it out of
NT:
IRQ=5
DMA= 00
DMA= 00
I/O Range: 0220-022F
I/O Range: 0300-0301
Can someone tell me how to configure this.. when i compiled the 2.2.3
kernel i added PnP support and SB16 support
and if it helps i run slackware 3.6
Thanks
eric
------------------------------
From: Efraim Wainerman <[EMAIL PROTECTED]>
Subject: Re: CM8330 sound card
Date: 19 Mar 1999 07:59:37 GMT
Douglas Stella wrote:
> I have a CM 8330 sound card, and my configuration try is not evolution.
> I hope config my sound card with your help.
> Thanks
>
this is the MINI-HOWTO about this:
CMI8330 Mini-HOWTO
Version 0.05
February 13, 1999
Author: Ken McCord ([EMAIL PROTECTED])
This Mini-HOWTO explains how to configure sound from motherboards
containing
the CMI8330 chip set.
Disclaimer:
This Mini-HOWTO is an outline of what I needed to do to add sound to my
system. I assume no responsibility for any damage that may occur from
following the instructions. Use it at your own risk.
Background:
This Mini-HOWTO was tested on a PC Chips M571 with the CMI8330 chipset.
This chipset has the following capabilities (from the M571 manual):
- SoundBlaster 16/PRO compatible with stereo voice up to 48KHz sampling
rates.
- HRTF 3D Positional Audio Technology
- Windows Sound System 2.0 compatible
- HSP-23 Wavetable Synthesizer
- Full Duplex 16-bit CODEC with filters
- High Quality 3D Sound (On/Off Controllable)
- Auto switch the hardware between Windows Sound System and SoundBlaster
16.
- Stereo Mixer supports analog mixing from CD-Audio. Line-In supports
digital mixing
from Voice, FM/Wavetable and digital CD-Audio.
- Supports 44.1K digital audio (SPDIF) in.
The following peripherals were attached to the system at the time of
testing:
Linksys Ether16 NE2000 clone - set to io=0x300 and irq=3
Western Digital Caviar 2540 IDE Hard Drive as Primary IDE Master
Digital Research (Jamicon) ATAPI 32x CD-Rom as Primary IDE Slave
Sanyo 3.5" floppy drive as Primary floppy
32 MB SDRAM
I used RedHat 5.2 (from CheapBytes) to install and configure the system.
NOTE - I haven't tried the 2.2.x kernel series yet and don't expect to for
some time. I'd rather wait and have it cleaned up first. If you've gone
ahead and gotten this to work with 2.2.x, drop me a line and I'll include
your notes.
I. Check BIOS and Verify Sound Card Settings
This section is be optional. I have included it for completeness (and
it's always good to have a driver disk nearly).
Reboot your computer and go into the BIOS setup. Make sure the 'Onboard
Sound' is enabled. Save and exit.
Create a driver disk from the installation CD-Rom that came with your
motherboard.
If you do not have the CD-Rom (or may want to use an updated version), you
can download the driver from
http://www.cmedia.com.tw/e_snd_drv.htm#released-drivers. I used the file
V4100132.EXE. This file includes DOS, Win 3.x and Win 95 drivers. We will
only need to use the DOS drivers. Download the file and extract to a
temporary directory. Create a bootable floppy disk to which the DOS files
will be installed. Run the Install program from the temporary directory.
At the installation screen, for the DOS drivers, use the path 'A:\DOS', and
leave the Windows path blank. Please note that after installation is
completed, the program will add three lines to your C:\AUTOEXEC.BAT. You
will want to remove these lines.
Reboot the system, using the floppy disk just created. At the DOS prompt,
type 'A:\DOS\CMINIT' and press <ENTER>. Jot down the settings shown on the
screen. These are the settings on my card:
WSS BASE I/O ADDRESS 530
WSS IRQ CHANNEL IRQ 11
WSS DMA CHANNEL DMA 0
VOICE I/O ADDRESS 220
VOICE IRQ CHANNEL IRQ 5
VOICE DMA CHANNEL DMA 1
VOICE 16 BIT DMA CHANNEL DMA 5
MPU-401 MIDI DEVICE DISABLE
MPU-401 I/O ADDRESS 330
MPU-401 IRQ CHANNEL IRQ 9
GAME PORT I/O ADDRESS DISABLE
FM(OPL3) I/O ADDRESS DISABLE
Press <ESC> and select 'save settings and exit'.
At the DOS prompt, type 'A:\DOS\CMTEST' and press <ENTER>. Press <ENTER>
as
necessary to scan for settings. Select 'output voice' and press <ENTER> to
test for sound output. Repeat for 'output music'. If all is working well,
then we're ready to set up Linux! Press <ESC> to exit.
II. Recompile Linux kernel for sound.
Reboot into (or Install) your favorite Linux distribution. For this
Mini-HOWTO, I'm using RedHat 5.2 with kernel 2.0.36. Your settings may be
different with another distribution or kernel version. Make sure your
system has the 'isapnptools' package. Information about this package can
be
found at http://www.roestock.demon.co.uk/isapnptools.
Recompile the kernel. For the section dealing with sound, I selected the
following options as 'M'odules (everything else in the section as 'N'o):
Sound Card Support
OSS Sound Modules (new for 2.0.36??)
100% Sound Blaster compatibles
Generic OPL2/OPL3 FM synthesizer support
MPU-401 support
Microsoft Sound System
Reboot the system.
III. Configure /etc/isapnp.conf
At a bash prompt, type 'pnpdump > /etc/isapnp.conf'.
Modify the '/etc/isapnp.conf' file as necessary. My file is as follows:
#
# CMI8330 /etc/isapnp.conf configuration file
#
(READPORT 0x0203)
(ISOLATE PRESERVE)
(IDENTIFY *)
#
# Windows Sound System Configuration
#
(CONFIGURE CMI0001/16777472 (LD 0
(IO 0 (BASE 0x0530))
(IO 1 (BASE 0x0388))
(INT 0 (IRQ 11 (MODE +E)))
(DMA 0 (CHANNEL 0))
(ACT Y)
))
#
# MPU-401 Midi Configuration
#
(CONFIGURE CMI0001/16777472 (LD 1
(IO 0 (BASE 0x0330))
(INT 0 (IRQ 9 (MODE +E)))
(ACT Y)
))
#
# Soundblaster 16 Configuration
#
(CONFIGURE CMI0001/16777472 (LD 3
(IO 0 (BASE 0x0220))
(INT 0 (IRQ 5 (MODE +E)))
(DMA 0 (CHANNEL 1))
(DMA 1 (CHANNEL 5))
(ACT Y)
))
(WAITFORKEY)
Compare these settings and those in section I to what you found. Save and
exit.
IV. Modify /etc/conf.modules
Add the following lines to /etc/conf.modules:
alias sound sb
alias midi opl3
options opl3 io=0x388
options sb io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330
options ad1848 io=0x530 irq=11 dma=0,0
Save and exit.
V. Compile the program fixcmi.c
Compile the program fixcmi.c listed below. Please note the author's
comments.
/***************************************************************/
/* */
/* Program name: fixcmi.c */
/* */
/* Simple program to adjust the analog CD-in right and left */
/* channels of the CMI8330 sound chip */
/* */
/* Author: Luiz T. S. Mendes ([EMAIL PROTECTED]) */
/* */
/* Version: 1.0 Date: Nov 23, 1998 */
/* */
/* 1.1 Date: Dec 1, 1998 */
/* by Mark W. Vandersteen */
/* ([EMAIL PROTECTED]) */
/* Added extra support for enabling Line-In, */
/* loud, 3d_surround etc */
/* */
/* DISCLAIMER: This software is provided as it is and comes */
/* with absolutely NO WARRANTY . Use it at your */
/* own risk. */
/* */
/* NOTES: (1) This program is meant for the people who already */
/* have their CMI8330-based sound cards working */
/* (except for playing audio CDs, of course). This */
/* means that the following two steps should have */
/* already succeeded on your linux box: */
/* */
/* - installing the proper Linux sound driver; */
/* - configuring the CMI8330 sound chip by means */
/* of the isapnptools (see the Web site at */
/* http://www.roestock.demon.co.uk/isapnptools/). */
/* In this configuration the WSS logical device */
/* (logical device 0 in the CMI8330) MUST be */
/* included, even if the sound card is to be used */
/* in the SoundBlaster mode. */
/* */
/* These steps are fairly documented in the Linux */
/* HOWTOs and in the above isapnptools WWW site. */
/* */
/* (2) This program have been tested ONLY in my Linux */
/* box (Slackware 3.5, kernel 2.0.34). Though it */
/* should work in other configurations, there is */
/* no way to guarantee that. */
/* */
/* */
/* INSTRUCTIONS: */
/* */
/* 1. Change the definition WSS_BASE to match the CMI8330 WSS */
/* I/O base address specified in your /etc/isapnp.conf */
/* */
/* 2. Save the file and compile it with */
/* */
/* $ gcc -o fixcmi -O fixcmi.c */
/* */
/* (CAUTION: the -O option is MANDATORY) */
/* */
/* 3. You must be logged in as root to run the program, or */
/* SETUID it as root: */
/* */
/* # chmod +s fixcmi */
/* */
/* 4. Run it _after_ configuring the chip by the isapnp */
/* command. */
/* */
/***************************************************************/
#include <stdio.h>
#include <asm/io.h>
#include <unistd.h>
/* Some definitions, most related to the I/O addressing */
/* The base io address of WSS from isapnp.conf */
#define WSS_BASE 0x530
#define CMI8330_WSS_BASE WSS_BASE+4
#define CMI8330_WSS_INDEX_ADDR CMI8330_WSS_BASE
#define CMI8330_WSS_INDEX_REG CMI8330_WSS_BASE+1
#define CMI8330_WSS_STATUS_REG CMI8330_WSS_BASE+2
#define CMI8330_EXT_REG1 0x10
#define CMI8330_EXT_REG2 0x11
/* for register 0x10h (each bit)*/
#define SURROUND 0x20
/* for reg 0x11h (each bit)
* 0 - mute microphone
* 1-2 - mute CD-in right & left
* 3-4 - mute Line-in right & left
* 5 - Reserved
* 6 - sound output louder
* 7 - S/PDIF-IN channel
*/
#define MICROPHONE 0x01
#define CDROM_RIGHT 0x02
#define CDROM_LEFT 0x04
#define CDROM CDROM_LEFT | CDROM_RIGHT
#define LINEIN_RIGHT 0x08
#define LINEIN_LEFT 0x10
#define LINEIN LINEIN_LEFT | LINEIN_RIGHT
#define ENABLE_LOUD 0x40
#define SPDIFIN 0x80
/* Will enable access to Indirect Registers of the chip
* bit 6 of register 0x0C en/disables access */
void cmi8330_enable_write(int onoff)
{
outb(0x0C, CMI8330_WSS_INDEX_ADDR);
if (onoff)
outb(0x40, CMI8330_WSS_INDEX_REG); /* set bit */
else
outb(0x00, CMI8330_WSS_INDEX_REG); /* clear bit */
}
void cmi8330_set_reg(int reg, short int data)
{
short int tmp;
outb(reg, CMI8330_WSS_INDEX_ADDR);
tmp = inb(CMI8330_WSS_INDEX_REG) | data;
outb(tmp, CMI8330_WSS_INDEX_REG);
}
main()
{
int status, i;
/* Set the required I/O privilege level for accessing the I/O ports. */
status=iopl(3);
if (status != 0)
{
perror("FIXCMI: IOPL() Error\n");
exit(1);
}
/* Check the CMI8330 WSS register locations */
if (inb(CMI8330_WSS_STATUS_REG) != 0xCC)
{
printf("FIXCMI: Invalid WSS I/O address\n");
exit(1);
}
/* Now set the required bits for turning on whatever */
cmi8330_enable_write(1);
cmi8330_set_reg( CMI8330_EXT_REG1, SURROUND);
cmi8330_set_reg( CMI8330_EXT_REG2, CDROM | LINEIN | ENABLE_LOUD |
MICROPHONE);
cmi8330_enable_write(0);
}
VI. Test the system.
Reboot the system.
If your system's startup does not automatically run 'isapnp
/etc/isapnp.conf' and 'insmod sound', type in each line and press <ENTER>
(Note that RedHat 5.2 includes these lines in '/etc/rc.d/rc.sysinit').
Run the program 'fixcmi'.
Type 'cat /boot/vmlinuz > /dev/audio' and press <ENTER>. You should get
output from your speakers. Press <Control>+<C> to stop.
Place your favorite CD in the CD-Rom.
>From a command line, run 'cdplay' (or from X, run 'xplaycd' and press
start). You should now hear music coming from the speakers.
If everything is working, edit '/etc/rc.d/rc.local' and place a call to
'fixcmi' in it so the file is loaded upon startup. Save the file and exit.
VII. Notes
Marco Antonio Checa Funcke mentions that isapnptools 1.17 and sndconfig
0.29 (RH 5.2 ships with versions 1.15 and 0.27) autodetects the chipset
and creates the following conf.modules file:
Alias sound sb
Alias midi mpu401
Options mpu401 io=0x330 irq=9
Options sb io=0x220 irq=5 dam=1 dma16=5
He recommends changing this setup manually to the setup listed in section
IV.
Marco also mentions that RH5.2 stores *.o3 and *.sb files in /etc/midi
instead of /etc. This was causing problems with playmidi. Copying them
to /etc solved the problem for him. Can anyone concur?
Adam Rice wrote in to note that pnpdump needs to be run when all devices
are in use, and/or /etc/isapnp.conf needs to be configured properly. I
don't have any other pnp cards in my box, so I can't confirm this. Little
help, anyone?
Adam continues to add that only RedHat seems to have modularized sound in
the kernel 2.0.x series. Other distributions may have to slightly modify
this How-To. Also, fixcmi seems to do it's job before the sound modules
are loaded (if fixcmi is running in your init scripts, for example). His
CD player programs wouldn't produce any sound until he does
echo >/dev/audio
to load the sound drivers.
If you're running another distribution, please send me your changes. I'm
starting to switch over to Debian from RedHat, so I'll try to incorporate
Debian changes in the next version.
Trevor Boicey mentions that the WSS part of the card doesn't require an
IRQ, just a base address. If you're tight for IRQ's, you may want to give
this a try.
Finally, Matthew Joseph needs some help with the following problem. For
some reason, he's only getting 8 bit mono sound. Any suggestions??
VIII. Acknowledgments
I'd like to thank:
Luiz Mendes for the program 'fixcmi', for which this mini how-to would not
be possible.
Mark Vandersteen for his improvements to the original program.
Hans Wolters for the Dutch version of this document. The translation is
located at http://home.gelrevision.nl/~h.wolter/linux.htm (Yes, I've got
to get this on a site!)
Marco Antonio Checa Funcke, Adam Rice and Trevor Boicey for their
contributions to the Notes section.
================== Posted via SearchLinux ==================
http://www.searchlinux.com
------------------------------
From: [EMAIL PROTECTED] (Vladimir NOVIKOV)
Subject: Q: PCMCIA support (network, modem & SCSI) under Linux 2.0.36 or 2.2.3???
Date: 19 Mar 1999 07:59:43 GMT
Hello all,
I need to buy urgently some PC cards for my office and I want to be
sure to get the products supported by Linux (the Laptop will run SuSE
Linux 6.0).
First of all I need SCSI to PC card adapter. I think the only choice
are Adaptec cards 1460 (standard) and 1480 (Cardbus). I prefer the
Cardbus 32 bits version for the speed, but what about Linux support?
Then I need the combo modem V90 + 10/100 Mb network card.
I heard about wanderful Xircom Realport adapter, but Xircom isn't
supported by Linux yet, right? What are the alternatives?
The other think I don't like about Xircom is its PC card 3 format,
because I'll need sometimes to get all cards (SCSI, network and even
modem) working at the same time. So, I need the PC card 2 format
combi.
Many thanks in advance for your help.
Vladimir NOVIKOV
------------------------------
From: [EMAIL PROTECTED] (doole)
Crossposted-To: alt.os.linux,comp.os.linux.setup,comp.os.linux.networking
Subject: Re: For all you Nicrosoft lovers
Date: 19 Mar 1999 07:59:56 GMT
Reply-To: [EMAIL PROTECTED]
"liam toh" <[EMAIL PROTECTED]> apparently said this:
>
>BTW doole: do you work for the IRS?
>
<g> No, but good question.
------------------------------
From: Hugh McCurdy <[EMAIL PROTECTED]>
Subject: Toshiba Satellite 4005CDS & Serial I/O Woes
Date: 19 Mar 1999 08:00:31 GMT
I am trying to help someone load Linux to a Toshiba
Satellite 4005CDS notebook computer.
Linux loads and runs but it can't use the serial port.
Want to use the serial port as a login (getty) port.
Linux Kernel 2.0.35.
Connected a breakout box. Lights look OK. Attempting
to send from Toshiba does not flicker the TD light
(as it should).
Rebooted to Win98. Noted that data and signal lights
from Toshiba turn off during Win98 boot.
Tried DOS based terminal emulator. Lights come on.
Still can't send characters from Toshiba.
Tried HyperTerm. It turns the lights and and did allow
sending of data. (Great, must need a secret code...)
And I believe one of two things are wrong.
1) The Toshiba should work but it broken.
2) The Toshiba's design is such that Linux won't be able
to use the serial port.
* Does anyone have a Toshiba Satellite 4005CDS that works or
doesn't work with respect to serial I/O under Linux?
(Or a computer in the same model series?)
Clearly, if other computers of the same model work, I can
claim to Toshiba that the computer is broken.
* Does anyone know of a Linux solution (like a program or
driver patch that can initialize a Toshiba port)?
Or does anyone have any other useful or potentially
useful comments. I will read the newsgroup and the
e-mail address I've supplied is valid.
--
Hugh McCurdy
------------------------------
From: "Tom Emerson" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.advocacy,comp.os.ms-windows.advocacy
Subject: Re: "Select the application, and then the platform"
Date: 19 Mar 1999 08:01:05 GMT
[EMAIL PROTECTED] wrote in article <7colnn$p5a$[EMAIL PROTECTED]>...
> In the sacred domain of comp.os.linux.hardware didst Todd Bandrowsky
<[EMAIL PROTECTED]> eloquently scribe:
> :>I guess you've never heard of MOTIF. Funny thing I was always required
to
> : follow the MOTIF >standard for dialogs and used the core widgets for
say an
> : open file dialog.
>
> : If MOTIF is so prevalent on Unix, then why do all X applications look
> : different? Why do I have a bunch of different X apps on my Linux box
that
> : all have different styles of FILE | OPEN. Heck. skip that even. Why
does
> : every one have completely different menus?
>
> Motif is the widget set.
> It's the application writer who decides what menus will hold what options
> and where they're going to be.
>
> The only thing Motif (or any other widget set) disctates is what the
buttons
> will look like, and how they react to being pressed...
I fear this is going way wide of the topic's relevance in the
...linux.hardware group I'm reading this in [not to mention the advocacy
groups], but this last comment seems to explain a problem I'm having with X
at the moment: One application I'm running (freeciv, to be exact) has
"menus" that are coded as macintosh-style menus, i.e., click/hold on the
menu button to bring up the menu, drag down to the menu item you're
interested in, then release to select. This is all fine and dandy when it
works, but on occaision, "something" goes awry and I end up with a case
where "dragging" doesn't select anything -- restarting the app doesn't work
either, I have to COMPLETELY exit X and restart it.
Is this a case where the "widget" of a menu is set to react this way
[click/hold, drag, release] or of the person writing the app coding to
react to "events" in this manner? If it is the "widget" that is reacting
this way, what can I do to get a more PC-like menu that is
click-and-release to enable the menu, then move & click/release to select
an item [clicking away from the menu entirely to dismiss, rather than
releasing "off-menu" to dismiss]
I know this isn't controlled by the "window manager", because I've also run
the client on a win95 machine using a commercial "X" server for 95 -- this
ends up being REALLY strange because I'm not actually running a "window
manager" on this server, just the freeciv client... [which means I cannot
move/resize windows...]
------------------------------
From: [EMAIL PROTECTED] (Joost de Heer)
Subject: Soundcard problems
Date: 19 Mar 1999 08:00:44 GMT
I have troubles getting my soundcard working. It's an Aztech Sound Galaxy PnP
card. I can play .au files and CDs normally, but things like MP3s don't work,
I get an 'Unable to open the audio device / Unable to reset audio device'
error. I'm using kernel 2.2.3, if you need the exact soundcard settings I
used, and/or the exact IO/DMA/IRQ settings required, let me know.
Joost
[EMAIL PROTECTED]
--
Why is it that people are so afraid of it? What is it about it that scares people so
deeply?
Because they are afraid that there is more to reality than they have ever confronted.
That there are doors that they are afraid to go in and they don't want us to go in
there either
because if we go in there, we might learn something that they don't know. And that
makes us a little out of their control.
------------------------------
From: "Michael W. Ryder" <[EMAIL PROTECTED]>
Subject: Re: Parameters for an old Canon hard drive
Date: 19 Mar 1999 08:00:46 GMT
Check http://blue-planet.com/tech/index.html (The Tech Page). They have
the settings for a lot of old and new drives.
Michael W. Ryder
[EMAIL PROTECTED]
"Peter B. Yorke" wrote:
>
> Would anybody happen to know what CMOS setting I need to use so my PC
> can see an old Canon 486v hard drive?
>
> I guess it's so old that the automatic detect doesn't. I'm hoping someone
> out there in LinuxLand either has one and can look at their CMS settings
> or has a book on the subject...
>
> Thanks,
> Pete Yorke
> [EMAIL PROTECTED]
------------------------------
From: "B. Collins" <[EMAIL PROTECTED]>
Subject: Re: failure to find floppy controller
Date: 19 Mar 1999 08:00:12 GMT
Reply-To: [EMAIL PROTECTED]
Henrik Carlqvist wrote:
>
> "B. Collins" wrote:
> > The system reports that /dev/fd0 is not accessible. The
> > /var/log/messages file looks like this:
> >
> > Floppy drive(s): fd is 1.44M
> > reset set in interrupt, calling 001711bc
> > floppy: no floppy controllers found
>
> Is the floppy connected to a floppy controller on the motherboard? If
> so, what is the brand of your motherboard? Is the floppy connected to an
> IDE-channel like an LS-120? If so you will have to compile a kernel or a
> module with support for IDE/ATAPI-floppys.
>
> regards Henrik
>
> --
> spammer strikeback:
> root@localhost [EMAIL PROTECTED] [EMAIL PROTECTED]
> [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
It's definitely connected to the floppy controller not the IDE
controller. I've tried loading multiple operating systems on this system
including DOS, Win'95, Win'98, SCO Open Server, Solaris, and BSD. All of
them "see" the floppy drive. On a whim, I loaded my old slackware
1.2.13 verson of Linux of linux and found I could use the floppy. I
have to conclude that some floppy controllers on not supported by the
2.0.x kernels that were supported by earlier kernels. A sad state of
affairs IMO.
------------------------------
From: "Charles Sullivan" <[EMAIL PROTECTED]>
Crossposted-To:
comp.sys.ibm.pc.hardware.misc,comp.os.ms-windows.nt.setup.hardware,alt.comp.hardware.pc-homebuilt,comp.os.linux.x
Subject: Re: Microsoft Serial Mouse 2.0a! DO NOT READ THIS!
Date: 19 Mar 1999 08:01:25 GMT
Check to see that the roller bars that contact the ball are clean. My old
M$
bus mouse (circa 1991) has stainless steel rollers that always seem to
collect gunge. My new M$ Intellimouse has some sort of black plastic
rollers
that so far seem to stay a lot cleaner - I haven't yet experienced any
skipping.
(The newer ball looks the same but may be a different material that doesn't
pick
up and transfer as much dirt to the rollers.)
Mool wrote in message <01be70cc$31935110$330b5e18@computer>...
>Why don't these mice ever work right?!!!!!!!!!!!! I have tried other mice
>too, what is the secret to having a mouse that rolls perfectly with minimal
>pressure?
>
>Is it the mousepad? My mouse is clean BTW. Is it the ball inside?
>
>WHAT IS THE TRICK TO GETTING A MOUSE TO WORK PERFECTLY AND RESPOND WITH
>MINIMAL PRESSURE?
>
------------------------------
From: [EMAIL PROTECTED] (Steffen Kluge)
Crossposted-To: comp.os.linux.advocacy,comp.os.ms-windows.advocacy,comp.os.linux.setup
Subject: Re: X munges the graphics card? (Re: Windows 2000 Rah! Rah! Session falls
flat)
Date: 19 Mar 1999 08:01:10 GMT
Reply-To: [EMAIL PROTECTED]
In article <[EMAIL PROTECTED]>,
Zenin <[EMAIL PROTECTED]> wrote:
> $ for dir in `find . -type d`; do
> > mkdir $dir/icons
> > for image in `find $dir -name '*.jpg'`; do
> > convert -geometry 64x64 $image $dir/icons/`basename $image`
> > done
> > done
> And yes, I and thousands of other "archaic" CLI users do type stuff
> like the above off the top of our heads on command lines all day
> long.
Yes, because you don't really have to remember any of those
command lines as a whole. You just make them up as you go. This
is true communication between intelligible systems. You don't
have to learn and remember all sentences you are ever going to
use in inter-human communication either, do you? A GUI (at least
in the form commonly used nowadays) is just like that - a dialog
based on canned phrases, with no way of expressing anything that
hasn't been "pre-thought".
That's why the single most important X application is xterm (and
friends).
Cheers
Steffen.
--
Steffen Kluge <[EMAIL PROTECTED]>
Fujitsu Australia Ltd
Keywords: photography, Mozart, UNIX, Islay Malt, dark skies
--
------------------------------
From: Phil Brutsche <[EMAIL PROTECTED]>
Subject: Re: Dual Pentium II support.
Date: 19 Mar 1999 07:47:59 GMT
On Mon, 15 Mar 1999, Andrea Borsic wrote:
> Hi,
>
> I'm looking to buy a fast machine for scientific calculation pourposes.
> For some constraints I'm looking to an Intel platform, so I cannot go
> Alpha.
>
> The idea is to buy a dual pentium II machine ( Dell Workstaion series
> 210 ).
>
> The problem is this: will Linux support this machine?
Quite easily; however, I would recommend that you upgrade to 2.2.x (it has
better SMP support than 2.0.x)
>
> What matherboard chipset/BIOS is supported for SMP?
Only Intel chipsets do SMP compatible with Linux/i386 - If you get a BX
motherboard you would be in good shape.
======================================================================
Phil Brutsche [EMAIL PROTECTED] | [EMAIL PROTECTED]
Microsoft: "Where do you want to to today?"
Linux: "Where do you want to go tomorrow?"
------------------------------
From: "Peter B. Yorke" <[EMAIL PROTECTED]>
Subject: Parameters for an old Canon hard drive
Date: 19 Mar 1999 08:00:41 GMT
Would anybody happen to know what CMOS setting I need to use so my PC
can see an old Canon 486v hard drive?
I guess it's so old that the automatic detect doesn't. I'm hoping someone
out there in LinuxLand either has one and can look at their CMS settings
or has a book on the subject...
Thanks,
Pete Yorke
[EMAIL PROTECTED]
------------------------------
From: John Heppner <[EMAIL PROTECTED]>
Subject: Red Hat vs. Calder nic
Date: 19 Mar 1999 08:00:17 GMT
I am installing red hat linux on a compaq 6000. Most of the drivers I
need come with red hat. However the nic (netflex 10/100 by compaq) is
not supported. Calder does have a driver for it. Can I get the driver
and incorporate it into red hat? If so, how can I do it, else tell me
what I can do.
Please email me back at [EMAIL PROTECTED]
Thank you kindly.
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.hardware) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Hardware Digest
******************************
