Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!comp.vuw.ac.nz!waikato!aukuni.ac.nz!kcbbs!dgd
Newsgroups: comp.os.386bsd.misc
Subject: Stallion multiport cards
From: dgd@kcbbs.gen.nz (David Dix)
Date: 19 Sep 93 13:18:53 GMT
Message-ID: <1593261.47933.1689@kcbbs.gen.nz>
References: <27c89g$gc@cleese.apana.org.au>
Organization: Kappa Crucis Unix BBS, Auckland, New Zealand
Lines: 51
In message <<27c89g$gc@cleese.apana.org.au>> newton@cleese.apana.org.au writes:
>UnixWare really sucks rocks. Take my word for it.
>
>I've been doing some volunteer work for an organization that's using a
>UnixWare system with a Stallion EIO Intelligent 8-port serial card. Since
>Novell's latest Unix product is so losing, we want to run something cheaper
>and more capable on the system (like one of the BSD's, for example).
>
>Whether or not this is totally workable is dependent on 386BSD/NetBSD's
>ability to drive the Stallion card.
Take my word for it - Stallion cards suck even more.
After more than $1000 wasted on a Stallion, countless hours trying to get
the damm thing working as it said in its manual and lots of phone calls to
Stallion in Australia I embedded the f**king thing in concrete in my
driveway so I could at least get the pleasure of driving my car over it
daily.
>
>So, does anyone have any drivers for such a beast?
>
>There are various hack solutions we can use in preference to the Stallion
>card, but staying with it is much cleaner.
I heard a rumour (rumor for some) that SCO unix might work with a Stallion.
Anyway you will find 386bsd excellent compared to the other offerings available
and its damm good value too - all source code, it works almost continually,
and there are very few problems with serial i/o ports if you use the sio
driver with 386bsd0.1 with 0.2.4 patchkit. I have six ports each using its
own interrupt and all are connected to high speed modems - two Zyxel 1496e+,
a Dynalink 14k4, a Mutitech v32 and two PEP2 modems. Everything works real
good, rts/cts flow control on all ports (unlike Stallion whose driver was
incapable of any decent flow control) using NS16550afn serial controllers
The only minor problems I have had is with the Multitech that sometimes
(seldom) get into a funny state where the rx and tx leds are fully on and
its not connected to anything. Uses up some cpu cycles but nothing too
serious.
dgd
#! rnews 1368 sserve.cc.adfa.oz.au
Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!cs.utexas.edu!uunet!mcsun!dxcern!tifrvax.tifr.res.in!basant
From: basant@tifrvax.tifr.res.in (Sundar Nagarajan)
Subject: 386BSD or Linux ??
Message-ID: <16SEP93.02290762@tifrvax.tifr.res.in>
Sender: news@dxcern.cern.ch (USENET News System)
Organization: MIT PLASMA FUSION CENTER
Date: Thu, 16 Sep 1993 02:29:07 GMT
Lines: 20
I have a 486 PC with 16 MB RAM and an ethernet card. I want
to load a BSD flavour of Unix on it and my requirements are as follows:
1) I want TCP-IP support to connect to my Local Area Network as well as
to the local WAN router.
2) I want NFS features to mount my PC's disk on other machines on the local
net and want to be able to mount other filesystems on
local machines on my machine.
3) I want a DOS partition on my machine and I heard that BSD386 crashes
destroying the DOS partition. Is this true ? Are there any workarounds
to 386BSD to ensure that the DOS partition remains inviolate ?
The stuff on my DOS partition is of utmost importance to me.
4) What are the merits / demerits of Linux in this respect ? How does Linux
compare with 386BSD ?
Thanks, and please reply to:
bhiksha@tifrvax.tifr.res.in
bhiksha@tifrvax.bitnet