>From ">owner-ale@ale.org Tue Jan 11 07:37:07 2000
>Date: Tue, 11 Jan 2000 07:35:43 -0500
>From: Wandered Inn ">esoteric@denali.atlnet.com>
>Subject: Re: [ale] PS/2 mouse-port trouble - Asus P3B-F
>
>FWIW, I've had mine up and running for about two weeks now and
>have not had any problems with the mouse.
Hmmm, anything "relevant" in your BIOS setup I might try?
What are your mainboard & BIOS versions?
Here's another thing I've discovered since my message:
If I boot MS-DOS & try to run ProComm+ for DOS (yes, ancient, but
this pgm has *never* ever been any trouble), I get a runtime error
& the system hangs. It takes the hardware reset switch to get it
back. I've run PC+ on dozens of systems over the past (more than)
15 years & it has *never* done *anything* like that...
>Kenneth W Cochran wrote:
>>
>> Have any of you had trouble with the PS/2 mouse port on the Asus
>> P3B-F (1agp/6pci/1isa) mainboard? I have had 2 in a row whose
>> mouseports don't work (under Linux, FreeBSD & even MS-DOS).
>> Board rev is 1.04, bios is 1004. Asus tech-support is no help,
>> other than "send the board..." Linux malfunctions especially
>> badly - if mouse is connected, keyboard will not respond.
>> (Slackware 7.0, kernel 2.2.13 & subsequently 2.2.14)
>>
>> The place I bought the board(s) says they checked the 1st one &
>> it worked for them... (Perhaps because of different (IDE)
>> peripherals?)
>>
>> My config is as follows:
>> CPU - Celeron 433A, *no* overclocking
>> Memory - 128m ECC (Hitachi)
>> AGP - Matrox G400 (configs as irq 11)
>> PCI1 - Intel NIC (also configs as irq 11, but works fine)
>> PCI2 - DPT SCSI HBA (configs as irq 10)
>>
>> Asus-tech suggested moving NIC to another pci slot, whereby it
>> went to a different irq, but that did not help.
>>
>> Did I just hit an unlucky-streak & get a couple of bad ones or
>> should I switch brands? IOW, should I be patient &
>> understanding :) & swap again or should I get something else?
>>
>> Many thanks,
>>
>> -kc
--
To unsubscribe: mail ">majordomo@ale.org with "unsubscribe ale" in message body.