HDTenEightyP/NetNews huggingface dataset:
From: kjb@cgl.citri.edu.au (Kendall Bennett)
Subject: 386BSD - Seems to stop my disks from booting...
Organization: RMIT Advanced Computer Graphics Centre, CITRI, Melbourne
Date: 12 Sep 92 08:32:50 GMT

I am trying to install 386 BSD on my system. I have a 486/33 system with
8M ram, and two 120M Western Digitial 2120 hard disks (WDC AC2120M). 
Currently I have OS/2 2.0 install on my system, and was hoping to get
them working side by side (using the boot manager).

Originally I was going to have OS/2 2.0 on one disk, and 386 BSD on the
other, changing disks simply by flicking a switch which changes the
master slave relationship between the two drives (IDE drives). This worked
fine when I tested it for MSDOS 5.0, but after I installed 386 BSD on
the entire disk, it simply would not boot (machine hung and the A: drive
sat a whirred - even Ctrl-Alt-Del did not work). I could still boot from
the first drive as per normal.

Then I removed everything BUT the drive that I was installing 386 BSD on,
and tried again but to no avail (running the OS/2 2.0 Fdisk showed the
disk as being free, but Tiny386BSD could still recognise and even
mount the drive properly).

Now for the strange part. After deciding something was wrong :-), I
installed MSDOS 5.0 onto the disk (thinking that the HPFS format could
be confusing 386BSD), but now MSDOS wont boot either! ARRRGHH! I low
level re-formatted the drive (from the BIOS setup - don't know if this
actually does anything for IDE drives), but it still does not boot.

Finally I decided that maybe something was wrong with my second drive, so
I reformatted it as an OS/2 2.0 installable file system and transferred
all of my OS/2 stuff over to it (OS/2 unlike others can boot from the
second drive!), so I would then have a 1 Mb boot manage partition, 4Mb
MSDOS partition and a 114Mb 386BSD partition. I installed 386BSD on
the disk, rebooted and guess what - the stupid machine did excatly the
same thing - it wouldn't boot. By now I was real worried about not
having a single hard disk that would boot, so I booted up OS/2 2.0
from floppies, and ran fdisk. Fdisk now found a partition marked as
A5, so I added it to the boot manage menu. Rebooting and up came boot
manage - selected 386BSD and boom - machine did a hardware reset!

Damn. I also worked out that if I do a shutdown -to386bsd, it puts the
system back into the non-bootable state, and a shutdown -todos makes
MSDOS startable again, but I have to load OS/2 2.0 from floppies to get
boot manage to work again (using fdisk).

My system has an AMI BIOS (latest 7/7/91 release) with an ETEQ chipset. 
I also have a MegaEVA/2 ET4000 based video card with HiColor RamDac 
installed.

Any clues pppplllleaaasssse?
From: mav@encap.hanse.de (Jan-Oliver Neumann)
Newsgroups: comp.unix.bsd
Subject: 16550; 386BSD 0.2; Kernel-Book
Date: 11 Sep 92 20:24:13 GMT
Organization: Private site in the north of Germany.


    Hello.

    I have a  couple of questions  that hopefully haven't  been answered to
    many times before:

    a) Does 386BSD support  the 16550 AFN UART ? Will it  use the FIFO ? If
    not, is  there any patch  available for making  386BSD using the  16550
    AFN? Or is support planned for 386BSD 0.2 ?

    b) Is  there any estimate for  386BSD 0.2 ? When  will it be available,
    what will be new/fixed ?

    c) What about the book 386BSD From the Inside-Out. It was mentioned for
    late 1992 in INSTALL.NOTES. Is this still valid?

    Regards,
	    Jan-Oliver
------------------------------------------------------------------------------
Jan-Oliver Neumann                                          mav@encap.hanse.de
 - We all know what makes the flowers grow, but we don't know why,
   we all have the knowledge of DNA, but we still die... (New model army)
From: terry@spcvxb.spc.edu (Terry Kennedy, Operations Mgr.)
Newsgroups: comp.unix.bsd
Subject: Re: ec0 question, use 3c501 instead of 3c503?
Date: 9 Sep 92 07:56:45 GMT
Organization: St. Peter's College, US

In article <92252.033848MHS108@psuvm.psu.edu>, MHS108@psuvm.psu.edu (Mark Solsman) writes:
> Seems that tiny bsd doesn't recognize my 3com 3c501 card, the install.notes
> mentions  3com 3c503 support.  Is there any way to use a 3c501 card instead?

  The 501 is an utterly different board from the 503. It [the 501] is also
pretty brain-dead. I'd suggest getting one of the 503 family cards or some
other supported card.

	Terry Kennedy		Operations Manager, Academic Computing
	terry@spcvxa.bitnet	St. Peter's College, Jersey City, NJ USA
	terry@spcvxa.spc.edu	+1 201 915 9381
Newsgroups: comp.unix.bsd
From: zxmsd01@mailserv.zdv.uni-tuebingen.de (Gunther Schadow)
Subject: Re: ghostscript under 386BSD?
Organization: Comp. Center (ZDV) U of Tuebingen, FRG
Date: Fri, 11 Sep 1992 22:14:01 GMT

In <s-vn48f.alm@netcom.com> alm@netcom.com (Andrew Moore) writes:

>Ghostscript is part of the /etc distribution of 386bsd. I rebuilt it
>using the default makefile (for epson device). But when invoked it dies
>with diagnostic:

>Initializing... Zget t_string 256 >= 256
>Unrecoverable error: rangecheck in get
>Operand stack:
>    256 [...]

This error occurs in my ghostscript only if you do not set the -r
option in the way gs likes it. Gs doesn't like the x and y resolutions
to be to far apart from each other. So try -r240x216 and he should not
complain. If you use -r360x360 he shouldn't complain too. I think I
once succeded even with -r360x180 but don't remember (since I use TeX
now :-). So be sure not to leave -r undefined.

cheers
-Gunther
-------------------------------------------------------------------------------
Gunther Schadow,	          e-mail: Gunther@mailserv.ZDV.Uni-Tuebingen.DE
Sudetenstrasse 25,	          Phone:  (49) 7071/37527
7400 Tuebingen, Germany.__________Stop__________Horn Please!__________O.K. TATA
--
-------------------------------------------------------------------------------
Gunther Schadow,	          e-mail: Gunther@mailserv.ZDV.Uni-Tuebingen.DE
Sudetenstrasse 25,	          Phone:  (49) 7071/37527
7400 Tuebingen, Germany.__________Stop__________Horn Please!__________O.K. TATA
From: ajv@xhost92.csd.mot.com
Newsgroups: comp.unix.bsd
Subject: Re: /dev/lp and LARGEW configurations
Date: 11 Sep 92 17:15:29 GMT

dri@gl.pitt.edu (Paul) writes:

>More exactly the printer starts to spit out a ROOT banner page and then
>the system softreboots.

I saw this too with the original printer driver.  I think you need
to have a parallel interface which streams interrupt to your system
at a rate unrelated to any parallel activity.  That you're seeing this
also suggests that the original printer driver wouldn't work very
well for you, anyway.

Mr. Stanglmeier came up with a lpt driver which doesn't need interrupts.
I tweaked it a little bit more.  It handles my printer fine, and
also appears to use LESS(!) CPU than the interrupt-driven configuration.
Anybody who missed the posting with this driver can E-mail me and I'll
be happy to send you a copy.

					Regards,
					Andy Valencia
					ajv@csd.mot.com
Newsgroups: comp.unix.bsd
From: colin@cs.curtin.edu.au (Colin Manning)
Subject: Re: backup w/ compression for UN*X?
Organization: Curtin University of Technology
Date: Mon, 14 Sep 1992 03:47:39 GMT

brtmac@maverick.ksu.ksu.edu (Brett McCoy) writes:

>In article <1992Sep06.104350.2659@rubikon.han.de> toad@rubikon.han.de
>(Peter Cleve) writes:

>>Something like this: (Not a ready to go script, but it shows the idea)
>>
>>YourFavoriteArchiver |
>>YourFavoriteCompress | (
>>	   echo Insert Media > /dev/tty
>>	   read dummy < /dev/tty
>>	   dd of=YourFavoriteDevice bs=Foo count=YourFavoriteMediaSize
>>)
>>
>>Reading from the Media should be implemented easily too.

>There is a serious problem with this scheme.  You have to read every
>single disk, or whatever, to get a file that is on the last disk.
>Also, if a disk in the middle of the dump is bad there is no way to
>get the data from the disks following the bad one because you can't
>start reading a compressed file in the middle.

>++Brett;

What about:

find / -name "*" -exec "ind-comp"{}";"

where ind-comp is:
compress $1
tar -r $1
uncompress $1

I'm not sure on the syntax, but you should get the general idea.

Colin.
--
Colin [colin@cs.curtin.edu.au]

"Knowledge is not knowing all the answers, but knowing where to find them."
                                                                  -anon.
Newsgroups: comp.unix.bsd
From: bremner@cs.sfu.ca (David Bremner)
Subject: Re: 386bsd -- The New Newsgroup <Summary>
Reply-To: bremner@cs.sfu.ca (David Bremner)
Organization: CSS, Simon Fraser University, Burnaby, B.C., Canada
Date: Sat, 12 Sep 1992 23:22:07 GMT

In article <1992Sep12.205451.15726@terminator.cc.umich.edu> pauls@umich.edu writes:
>
>Did I fail to represent anyone who has posted in this thread so far?
>
>I would like to get a feel for what sort of support each of these  
>positions has.  Please either follow up or email me.

My own proposal was to move comp.unix.bsd to comp.os.bsd; unless USL wins, 
in which case we are all in deep doo-doo.

Then subgroups of comp.os.bsd could be created for 386bsd and other bsd
based systems.  My attachment to a unified bsd hierarchy does not seem 
to be shared by the other posters in the thread, or by Lynne Jolitz.

I'm not sure whether or not two separate newsgroups are needed for bsd386 
and 386/bsd.  I realize there are political considerations here, but 
comp.unix.pc-clone.32bit ( or whatever it is called ) serves about 
6 major flavours of SYS V based unix on intel processors.

In a soundbite

	comp.os.bsd
	comp.os.bsd.pc-clone

Which would cover bsd386, 386/bsd, mach-386, BNRSS-386, (the last two
only in regard to their BSD nature, not their mach nature)

Cheers,

David

-- 
bremner@cs.sfu.ca 				          ubc-cs!fornax!bremner
Newsgroups: comp.unix.bsd
From: satmech@ecst.csuchico.edu (satmech)
Subject: Re: fdprobe() returns 0
Keywords: fdc wdc patch fdprobe
Organization: California State University, Chico
Date: Thu, 10 Sep 1992 00:07:31 GMT

In article <1992Sep7.192540.10143@Urmel.Informatik.RWTH-Aachen.DE> kuku@acds.physik.rwth-aachen.de writes:
>
>I installed the 2nd drive (updated) patch from Tom Helbekkmo
>(tih@barsoom.nhh.no) and since then (?) I cannot access my fd drive any longer.
>
>I peeked into fdprobe() with a printf() and find that fdprobe() does
>not even see the FD controller (at 3f0). 
>
>I'm baffled. I will now successively go back in steps to see at which kernel 
>configuration I can see my floppies again. 
>
>It does not seem to be hardware - a different IDE controller gave the same
>bad result and I can still boot dist.fs (I'm using a 386SX 16MHz Morse Motherboard with 8MB, two disks). It's really strange, maybe too strange 
>to post it here - but if anyone has a vague idea what I could also look for or check I'd be thankful.
>
This seems to be a problem with all IDE controllers (mine too).  It doesn't
respond to the NE7CMD_SPECIFY command in fdprobe().  I just commented this
part out, the if(out_fdc(NE7CMD_SPECIFY) < 0 ) { ... } lines 125-128 in
/sys/i386/isa/fd.c and it recognized both my 1.44m and 1.2m floppies and
mtools works great...

If anyone has a better fix than this quick hack, please tell me about it.

Xref: sparky comp.unix.bsd:5736 comp.os.mach:1287 misc.int-property:986 alt.suit.att-bsdi:305
From: tjc50@juts.ccc.amdahl.com (Terry Carroll)
Newsgroups: comp.unix.bsd,comp.os.mach,misc.int-property,alt.suit.att-bsdi
Subject: AT&T "DeathStar" Trademark (was: Are you sure UNIX is a trade mark?)
Date: 15 Sep 92 16:22:45 GMT
Reply-To: tjc50@juts.ccc.amdahl.com (Terry Carroll)
Organization: Amdahl Corporation

In article <4093@novavax.UUCP>, burtond@novavax.UUCP (Donald B. Burton) 
writes:
> actually, i have heard of this
> purely as a rumor--the death-star <well thats what i call it> symbol
> you know, the orb made with line-art so often seen with at&t logos
> was once untm-ed and un <c>-ed.  then some joe-schmoo noticed and
> copyrighted it before the execs at at&t realized.  at&t had to
> pay him $$$ to buy it back/pay royalt etc. 

I very much doubt this.

It couldn't be copyrighted, because to be copyrighted, a work must be 
original with the author seeking copyright, and that's not the case here.  
Worst case is that AT&T didn't copyright the artwork, so it was public 
domain, so others could use it, but they certainly couldn't copyright it 
themselves and prevent AT&T from using it, because you can always use 
something in the public domain.

On trademarks, a trademark is only registerable if it is used, or there is a 
bona-fide intent to use, the trademark in commerce.  Unless Joe Schmoo was 
actually using it, or had a bona fide intent to use it (and considering the 
circumstances here, that's be a tough showing), he couldn't register it as a 
trademark.  Even so, it could continue to be used as a common law trademark 
in areas where it had been used by AT&T -- and that's nationwide.

Terry Carroll - tjc50@juts.ccc.amdahl.com - 408/992-2152
The opinions presented above are not necessarily those of a sound mind.
From: wk0x@ANDREW.CMU.EDU (William Stephen Kish)
Newsgroups: comp.unix.bsd
Subject: XFree86 on MAG 17F
Date: 6 Sep 92 21:31:58 GMT
Organization: Carnegie Mellon, Pittsburgh, PA


Does anyone know the correct X386.modeDB entries for a MAG 17F monitor?

Thanks,
Bill Kish
Newsgroups: comp.unix.bsd
From: kgermann@zeos.com (Ken Germann)
Subject: Re: local bus and 386bsd compatible?
Organization: Zeos International, Ltd
Date: Sat, 12 Sep 1992 04:10:33 GMT

In article <BuFuy5.JMs@rice.edu> fontenot@ravl.rice.edu (Dwayne Jacques Fontenot) writes:
>hello,
>
>I will very soon be in the market for a machine on which to run 386bsd.
>I intend to get an EISA machine because I know that EISA drivers will be
>written sooner or later :-)

I will be testing the TinyBSD on our Local Bus System in the next week or
so. We just received two of the motherboards to put into two systems
in Tech Support today. I will post the results in biz.zeos.general
and here. I have tested most of our systems in house including most
of our notebooks.  


-- 
Ken Germann              ZZZZ EEEE  OO   SSS    ZEOS International, Ltd.  
support@zeos.com   INET     Z E    O  O S       Technical Support Dept.
uunet!zeos!support UUCP    Z  EE   O  O  SS     530 5th Ave N.W.
800-228-5390      VOICE   Z   E    O  O    S    St. Paul, MN 55112
612-633-7337             ZZZZ EEEE  OO  SSS     FAX         612-633-4607
Newsgroups: comp.unix.bsd
From: richard@pegasus.com (Richard Foulk)
Subject: Re: 386bsd questions (descriptive Subject:'s please)
Organization: Pegasus,  Honolulu
Date: Tue, 8 Sep 92 06:53:50 GMT

> Subject: Re: 386bsd questions

Just a (hopefully) helpful reminder ... there's a fair amount of traffic
to wade through as one reads the Usenet news.  Good `Subject:' lines
are very important.

Do yourself and others a favor by selecting an appropriate `Subject:'
line, so that people don't waste time reading things that aren't of
interest to them or questions that they can't answer.

Something like `386bsd questions' is fairly useless.  Something more
specific will help you and your readers:

	Subject: ifconfig, com1 lockups, console driver, etc. ?

The less descriptive your `Subject:' line the more likely people will
skip it without reading it.


Thanks for listening.


-- 
Richard Foulk		richard@pegasus.com
Newsgroups: comp.unix.bsd
From: pauls@icecreambar.css.itd.umich.edu (Paul Southworth)
Subject: Re: 386bsd -- The New Newsgroup
Reply-To: pauls@umich.edu
Organization: University of Michigan
Date: Wed, 9 Sep 1992 14:33:23 GMT

Holger Veit writes
[...]
| You should not multiply entities unless it is absolutely necessary
| (free translation of William of Occam's well-known statement). 
| 
| We have considerably high traffic on 'I cannot boot with my  
configuration', say
| 'newbie' stuff. Since I follow this group quite long, I would have an  
idea
| where to post such a question, but if I were a beginner and desperate 
| because of 386bsd had just cleaned my whole disk, I would perhaps ignore 
| the different groups and send my mail to all of them, perhaps to find 
| one who can answer.

I see your point.  Thanks to everyone who responded to my original  
posting.  I guess what I am most interested in is getting at least one  
exclusive 386BSD group going.  It seems to me that perhaps two or three  
would be better, but I am most concerned with actually getting this thing  
off the ground.  Preferably soon, but without undue rush.

I'm not stuck on the names of any of these, so don't debate them with me.   
This is what I would propose if I were to do it today:

comp.os.386bsd                <-- misc discussion and coordination
comp.os.386bsd.install        <-- slightly nicer term for newbie
comp.os.386bsd.development    <-- patches, bugs, ports, new software

I think those are pretty self-explanatory.
Newsgroups: comp.unix.bsd
From: torda@igc.ethz.ch (Andrew Torda)
Subject: Re: Fixed: Runs at 8MHz, Crashes at 33MHz, 386bsd
Organization: Computational Chemistry, ETH, Zuerich
Date: Sat, 12 Sep 1992 15:16:54 GMT

In article <1992Sep11.222258.2144@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes:
[...]
>>>     At 8 MHz, my machine appears perfectly stable.
>>>     At 33 MHz, I get repeated trap type 12 panics.
[... replacing 80 ns simms with 70 fixing the problem ..]
[... aha1542b gets blamed ...]
>Test:  Anyone have a non-SCSI system that has the "works OK at 8MHz but
>not at 33MHz" problem?  I realize this isn't a definitive test, as I
>might get responses from someone running 200ns RAM saying "Yeah; funny...
>no one else seems to have the problem", but it should give a weight of
>SCSI-with-problem vs. not-SCSI-with-problem.

Yes, have a look at the original post in this thread (from me).
Definitely no SCSI controller here. From my original posting
     Machine details:
     386 clone (Blackship), no maths chip, 8M memory
     ATI motherboard (ATI-386/B2-33, 64K cache)
     AMI BIOS (04/09/90)
     video: ET4000 based, DFI VG-5000 with 1 Mb
     pc0 <color> at 0x60 irq1 on isa
     com1 at 0x3f8 irq4 on isa
     com2 at 0x2f8 irq3 on isa
     wd0 (MAXTOR LXT-213A> at 0x1f0 irq 14 on isa
     fd0 drives 0:1.2M, 1: 1.44M at 0x3f0 irq 6 drq2 on isa
That maxtor number is a non-scsi model. It's an IDE.
The actual controller is some anonymous card called a 'CCAT200A'.
There is some western digital chip on the controller.
This was also the machine which ran SCO unix at full speed with no
problems.
I think the issue remains unresolved, although some of the mail and
speculation I got was amusing.
-Andrew
-- 

Andrew Torda, Computational Chemistry, ETH, Zurich, torda@igc.ethz.ch
Newsgroups: comp.unix.bsd
From: thomasg@cip-s02.informatik.rwth-aachen.de (Thomas Gellekum)
Subject: Re: [386BSD] cc1 fatal error
Organization: Rechnerbetrieb Informatik  /  RWTH Aachen
Date: 11 Sep 92 06:55:55 GMT

Tao Jiang <tj2n+@andrew.cmu.edu> writes:


>Hi, I tried to compile a program and got the cc1 fata error like:
>cc -I.. -I../..  -O -c fogdeck.c
>cc: Program cc1 got fatal signal 6.
>*** Error code 1

>I could not figure out what's wrong with it.

>Any help will be greatly appreciated!

>TJ

try to compile without -O. i had the same problem on metafont (mf1.c)
and there it worked without the optimizer.

thomas
-- 
thomas gellekum, kapellenstr. 26, d-5100 aachen, w-germany
dq060ge@dacth11.bitnet	     |      thomasg@pool.informatik.rwth-aachen.de
"why stop now, just when i'm hating it?" - marvin 
Newsgroups: comp.unix.bsd
From: mark@student.business.uwo.ca (Mark Bramwell CS Staff)
Subject: exabyte drive and 386bsd? will it work?
Organization: University of Western Ontario
Date: Wed, 9 Sep 1992 20:17:06 GMT

I am trying to use an exabyte scsi drive with 386bsd.  I am not sure
about the device name.

I have the drive set as device #2.  I have tried

tar -cvf /dev/as2d and the drive kicks, but I get errors.

What is the correct device name for a scsi drive?

mark@student.business.uwo.ca (Mark Bramwell CS Staff)
Western Business School  --  London, Ontario
Newsgroups: comp.unix.bsd
From: cproto@marsh.cs.curtin.edu.au (Computer Protocol)
Subject: Re: which X386 in agate is better?
Keywords: X386
Organization: Curtin University of Technology
Date: Wed, 9 Sep 1992 13:07:40 GMT

ko053@cucs11.cs.cuhk.hk (Patrick Ko) writes:

>I've the 386bsd up and running with 150M partition 
>with 20M DOS partition healthy.  TCPIP under ethernet
>card NE2000 with another DOS machine doing NCSA ftp
>things, fine. 

>Now I am going to get a copy of X386 and I found
>there are 2 directories that contain it. One is
>in /pub/incoming/X386 and the other is in /pub/386BSD/ports-0.1.

>Is there anybody who kindly tell me what are the
>differences between them? Which one should I get?

>Thanks for all you guys.

I tried both. The one in /pub/incoming/X386 is far better.

Regards - Tibor Sashegyi (cproto@abel.cs.curtin.edu.au)

Newsgroups: comp.unix.bsd
From: mullens@jamsun.ic.ornl.gov (James A. Mullens)
Subject: Re: Some more on NMI problems (some meager advancement)
Organization: Oak Ridge National Laboratory
Date: Tue, 8 Sep 1992 18:15:28 GMT

In article <cproto.715945053@marsh>, cproto@marsh.cs.curtin.edu.au (Computer Protocol) writes:
|> rivers@ponds.uucp (Thomas David Rivers) writes:
|> 
|> 
|> >Well, I thought I would relay my current status with the NMI
|> >investigation.
|> 
|> >  Right now, I'm thinking it has something to do with an IDE
|> > controller/disk drive, so I have been examining the wd.c driver
|> > trying to divine what it might be; without too much luck. (I 
|> > know very little about the IDE/WD disk controllers.)
|> 
|> [STUFF DELETED]
|> 
|> >  - Dave Rivers -
|> >   (rivers@ponds.uucp)
|> 
|> I'm also experiencing the problem. I disagree with the IDE controller
|> idea. I still think it's a spurious parity error. Note that the NMI
|> interrupt reports the value of I/O port 61. This value has the highest
|> bit set which indicates a parity error. But after running QAPLUS for
|> several days I'm convinced my memory is ok.
|> 
|> Could it be some sort of setup problem - e.g. wait states which can
|> be configured in my AMI BIOS.
|> 
|> BTW I do have a IDE controller/disk so Dave might be right.

Memory parity errors can also be the fault of the system board/bus
controller.  You really need to check for errors while your system
is "highly loaded" -- lots of I/O going on.  A memory tester may not
be able to see the problem otherwise...

I once had a completely-reproducible NMI which could not be found by
a tester.  It seems that my computer's "bus tended to be unstable
during periods of high load" and the chips I had purchased did not
tolerate this very well.  I switched chip manufacturers and the computer
has run w/o problems ever since.  This was so long ago that I
can't recommend the manufacturer, NMBS, on this basis.  In fact, I
visited our PC repair shop and found a notice that, FOR A CERTAIN MODEL
OF COMPUTER, NMBS and Siemens DRAM "will cause problems".  (Assume that
is someone's theory, not an authority's pronouncement!  Don't read too
much into this since -- it just indicates that not all motherboards
and DRAM mix well).  You might call your computer/system-board manufacturer
and try to get a recommendation.

I have also read a recommendation that 3-chip and 9-chip SIMMs not be
mixed together, but I have no real reason to believe this makes a
difference.

jim mullens
  Internet: jcm@ornl.gov		(128.219.128.17)
            mullens@jamsun.ic.ornl.gov	(128.219. 64.31)

I speak for myself, not for the organization I work for.
From: rjw9917@bcstec.ca.boeing.com (Robert J. Willard)
Newsgroups: comp.unix.bsd
Subject: 3 button mouse for X386
Keywords: X386 386bsd
Date: 8 Sep 92 23:22:41 GMT
Organization: 777 New Airplane Division

I've got 386bsd and X386 running smoothly, using
a microsoft serial mouse.  However, I'm accustomed
to using a 3 button mouse with X and am wondering
which mouse (preferably a CHEAP one) would be good.
Any ideas?

- Bob Willard
  Boeing Commercial Airplanes
-- 
Bob Willard
Boeing Commercial Airplanes
rjw9917@bcsaic.boeing.com
Newsgroups: comp.unix.bsd