tony@oha.UUCP (Tony Olekshy) (12/29/89)
In message <1989Dec25.164606.1072@ddsw1.MCS.COM>, karl@ddsw1.MCS.COM (Karl Denninger) writes: > > NO! The ATI bus mouse is not recognized here by either SCO or ISC's unix, > although it does work fine under MSDOS. Neither ISC or SCO will support > that configuration, and ATI doesn't know why it doesn't work (nor do SCO or > ISC). It may be 90% Microsoft bus mouse compatible, but it's not 100%. Hmm, works here w/AMI 386 @ 25 + Xenix 2.3.1, most of the time. Is the net's experience is that it never works, or is intermittent? -- Yours, etc., Tony Olekshy (...!alberta!oha!tony or tony@oha.UUCP).
scottw@ico.isc.com (Scott Wiesner) (12/30/89)
> In message <1989Dec25.164606.1072@ddsw1.MCS.COM>, karl@ddsw1.MCS.COM (Karl Denninger) writes: >> >> NO! The ATI bus mouse is not recognized here by either SCO or ISC's unix, >> although it does work fine under MSDOS. Neither ISC or SCO will support >> that configuration, and ATI doesn't know why it doesn't work (nor do SCO or >> ISC). It may be 90% Microsoft bus mouse compatible, but it's not 100%. Worked fine on my machine when I tested it! The one I got from them was actually a logitec bus mouse. Scott Wiesner Interactive Systems X Development Group
karl@ddsw1.MCS.COM (Karl Denninger) (12/30/89)
In article <397@oha.UUCP> tony@oha.UUCP writes: >In message <1989Dec25.164606.1072@ddsw1.MCS.COM>, karl@ddsw1.MCS.COM (Karl Denninger) writes: >> >> NO! The ATI bus mouse is not recognized here by either SCO or ISC's unix, >> although it does work fine under MSDOS. Neither ISC or SCO will support >> that configuration, and ATI doesn't know why it doesn't work (nor do SCO or >> ISC). It may be 90% Microsoft bus mouse compatible, but it's not 100%. > >Hmm, works here w/AMI 386 @ 25 + Xenix 2.3.1, most of the time. >Is the net's experience is that it never works, or is intermittent? We're talking about Unix here.... Xenix may well work, but we haven't tried that. I need it to work with Unix (for "X" windows, among other things). -- Karl Denninger (karl@ddsw1.MCS.COM, <well-connected>!ddsw1!karl) Public Access Data Line: [+1 708 566-8911], Voice: [+1 708 566-8910] Macro Computer Solutions, Inc. "Quality Solutions at a Fair Price"
ke4zv@kd4nc.UUCP (Gary Coffman) (01/02/90)
In article <1989Dec29.213443.8335@ddsw1.MCS.COM> karl@mcs.MCS.COM (Karl Denninger) writes: >In article <397@oha.UUCP> tony@oha.UUCP writes: >>In message <1989Dec25.164606.1072@ddsw1.MCS.COM>, karl@ddsw1.MCS.COM (Karl Denninger) writes: >>> >>> NO! The ATI bus mouse is not recognized here by either SCO or ISC's unix, >>> although it does work fine under MSDOS. Neither ISC or SCO will support >>> that configuration, and ATI doesn't know why it doesn't work (nor do SCO or >>> ISC). It may be 90% Microsoft bus mouse compatible, but it's not 100%. >> >>Hmm, works here w/AMI 386 @ 25 + Xenix 2.3.1, most of the time. >>Is the net's experience is that it never works, or is intermittent? > >We're talking about Unix here.... The problem with the ATI bus mouse is that it is not a Microsoft INPort Bus Mouse. ISC's driver does a signature check to make sure it is talking to an honest to GOD INPort chip. This fails of course with the ATI bus mouse. It took me two weeks of digging to find this nasty. Another problem with the ATI Video Wonder and a Micronics 20Mhz cacheing motherboard is that neither a warm boot nor a hardware reset will work. You get a machine that won't reboot. The ONLY way to reboot this combination is the big red switch. I never did solve this one. Thankfully, GOD stepped in at this point and rebooted my system with a few mega-amps of lightning and my insurance company bought me some nice new 33Mhz hardware.-)-) Gary Coffman
tony@oha.UUCP (Tony Olekshy) (01/02/90)
In message <1989Dec29.213443.8335@ddsw1.MCS.COM>, karl@ddsw1.MCS.COM (Karl Denninger) writes: = = In article <397@oha.UUCP> tony@oha.UUCP writes: = > = >Hmm, works here w/AMI 386 @ 25 + Xenix 2.3.1, most of the time. = >Is the net's experience is that it never works, or is intermittent? = = We're talking about Unix here.... = = Xenix may well work, but we haven't tried that. I need it to work with Unix = (for "X" windows, among other things). Well, since my article 397, we have also gotten the ATI Bus Mouse to work with SCO Unix 3.2 (usemouse) as well. Don't know about X yet, but will keep you posted as we continue to experiment. -- Yours, etc., Tony Olekshy (...!alberta!oha!tony or tony@oha.UUCP).
karl@ddsw1.MCS.COM (Karl Denninger) (01/02/90)
In article <399@oha.UUCP> tony@oha.UUCP writes: >In message <1989Dec29.213443.8335@ddsw1.MCS.COM>, karl@ddsw1.MCS.COM >(Karl Denninger) writes: >= >= In article <397@oha.UUCP> tony@oha.UUCP writes: >= > >= >Hmm, works here w/AMI 386 @ 25 + Xenix 2.3.1, most of the time. >= >Is the net's experience is that it never works, or is intermittent? >= >= We're talking about Unix here.... >= >= Xenix may well work, but we haven't tried that. I need it to work with Unix >= (for "X" windows, among other things). > >Well, since my article 397, we have also gotten the ATI Bus Mouse to work >with SCO Unix 3.2 (usemouse) as well. Don't know about X yet, but will keep >you posted as we continue to experiment. What did you have to do to make it work? We haven't gotten that lucky yet! (SCO Unix 3.2 hasn't worked with the ATI Bus mouse for us!) -- Karl Denninger (karl@ddsw1.MCS.COM, <well-connected>!ddsw1!karl) Public Access Data Line: [+1 708 566-8911], Voice: [+1 708 566-8910] Macro Computer Solutions, Inc. "Quality Solutions at a Fair Price"
larry@nstar.UUCP (Larry Snyder) (01/03/90)
> = Xenix may well work, but we haven't tried that. I need it to work with Unix > = (for "X" windows, among other things). > > Well, since my article 397, we have also gotten the ATI Bus Mouse to work > with SCO Unix 3.2 (usemouse) as well. Don't know about X yet, but will keep > you posted as we continue to experiment Likewise I will keep everyone up to date with my efforts of getting the ATI mouse working with 386/ix X 1.00. -- Larry Snyder, Northern Star Communications, Notre Dame, IN USA uucp: larry@nstar -or- ...!iuvax!ndmath!nstar!larry "NO! QNX is non-standard, not compatible, and is no more Unix than DOS!"
tony@oha.UUCP (Tony Olekshy) (01/06/90)
In <1990Jan2.152037.3553@ddsw1.MCS.COM>, karl@ddsw1.MCS.COM (Karl Denninger) writes: > > In article <399@oha.UUCP> tony@oha.UUCP writes: > > > > Well, since my article 397, we have also gotten the ATI Bus Mouse to work > > with SCO Unix 3.2 (usemouse) as well. Don't know about X yet, but will > > keep you posted as we continue to experiment. > > What did you have to do to make it work? We haven't gotten that lucky yet! > (SCO Unix 3.2 hasn't worked with the ATI Bus mouse for us!) The following is from my associate, Jim Hoover: How to make an ATI VGA bus mouse work with SCO Unix System V 3.2 1. Make sure that your mouse is configured properly. That is, enabled, using the primary port (23C) and IRQ5. The vga board comes shipped with the mouse disabled so you have to boot to DOS and use the VSETUP.COM program supplied by ATI to set the EEPROM configuration registers on the card. Options for configuration are: disabled, use primary port 23C, use secondary port 238; and use IRQ 2, 3, 4, or 5. 2. mkdev mouse, relink and reboot 3. When you boot the system you shoud get a hwconfig line something like name=mouse base=0x23C offset=0x2 vec=05 dma=- type=busmouse I don't know how the driver works but it does appear to sense the presence of the mouse because when I setup the mouse to use the secondary port the mouse initiation line at boot vanished. These next instructions apply to getting usemouse to run 1. Make sure that the appropriate entries are setup in /usr/lib/event/ttys to enable using the mouse on that tty. A typical entry looks like tty01 msbusmouse 2. Make sure that the permissions on the pty's (/dev/ptyp* /dev/ttyp* ) used by usemouse are correct. They should be rw-rw-rw- bin bin Symptoms of incorrect permissions will be a message like can't open slave(errno 13) Or the fact that you can run usemouse as root but not as anyone else. 3. If you use mscreen, there will likely be a problem caused by having a getty attached to the pty that usemouse grabs. This will be pretty obvious as starting usemouse will cause a login prompt to appear! My feeling is that mscreen should be attaching the getty to the pty, instead of having an /etc/inittab entry for getty permanently running on the pty. These next instructions apply to getting the mouse to run under VP/ix 1. Beats me how to do it. I made the mistake of trying to install the DOS driver from ATI and the resulting confusion required me to boot VP/ix off a floppy, fix the CONFIG.SYS file, and then power off the machine before the vga card and mouse stuff would work again (I am not sure if the power off was essential but it didn't hurt). Prof. Jim Hoover | Office +1 403 492 5401 or 5290 Dept. of Computing Science | FAX +1 403 492 1071 University of Alberta | hoover@cs.ualberta.ca Edmonton, Alberta, Canada T6G 2H1 | -- Yours, etc., Tony Olekshy (...!alberta!oha!tony or tony@oha.UUCP).