HDTenEightyP/NetNews huggingface dataset:
From: grog@lemis.uucp (Greg Lehey)
Newsgroups: comp.unix.bsd
Subject: Re: does the UMC chipset work with 386BSD?
Date: 12 Nov 92 17:39:37 GMT
Organization: LEMIS, W-6324 Feldatal, Germany

In article <49432@shamash.cdc.com> pbd@runyon.cim.cdc.com (Paul Dokas x4629) writes:
>I'm looking at a 486DX-33 (2 VESA LB slots, 6 ISA slots, 256K
>cache, 8 MB DRAM) that uses the UMC chipset with an Intel 486.
>Has anyone heard of the UMC chipset?  And does anyone know if
>I'm going to have problems running 386BSD?

Well, I have just removed a 486/50 with UMC from my machine, and gone
back to a 486/33 using an OPTI chip set. Nothing else changed - I had
a different 486/33 OPTI board (same design, though) in there before.
I'm running BSD/386.

The OPTI board ran with no problems since March, and I installed the
UMC board last week. On average, it crashed 5 times a day. This could
be a defective board, of course, but I didn't have another board to
compare it with. 

In the meantime, a report came out in c't, a German magazine,
comparing chipsets. It showed that the UMC board is very conservative
in its bus cycle, and the results with some benchmarks showed down to
40% of the performance of other chipsets (i.e. the program ran 2.5
times as long on a machine with the other chipset). This ties in with
the fact that my initialisation routines showed a speed only about 10%
faster than the 33 MHz OPTI chipset.

-- 
Greg Lehey                       | Tel: +49-6637-1488              
LEMIS                            | Fax: +49-6637-1489
Schellnhausen 2, W-6324 Feldatal, Germany
Newsgroups: comp.unix.bsd
From: bjork@telebit.com (Steven Bjork)
Subject: [386BSD] bash machines.h patch and a question
Originator: bjork@napa
Organization: Telebit Corporation; Sunnyvale, CA, USA
Date: Sat, 7 Nov 1992 01:12:04 GMT


Here's an Unofficial patch I used to compile bash.

Now, I have a question, probably a bash FAQ. I telnet
into my 386BSD/bash system and have problems with
crlf in an xterm window. I suspect it's actually an
xterm problem, but has anyone else got a workaround?

Oh, the problem is that I end up having lines apparently 
ended with an lf without cr, so I get crud all over
my xterm window. Doesn't happen if I run a sh.

--Steven


*** machines.h.factory	Sun Nov  1 07:57:29 1992
--- machines.h	Sun Nov  1 08:22:17 1992
***************
*** 392,397 ****
--- 392,405 ----
  #    undef HAVE_DUP2
  #  endif /* Sequent 386 */
  
+ #  if !defined (done386) && defined (__386BSD__)
+ #    define done386
+ #    define M_MACHINE "i386"
+ #    define M_OS Bsd
+ #    define HAVE_VPRINTF
+ #    undef HAVE_BISON
+ #  endif /* i386 && 386BSD */
+ 
  /* Generic 386 clone running Mach (4.3 BSD-compatible). */
  #  if !defined (done386) && defined (MACH)
  #    define done386
Newsgroups: comp.unix.bsd
From: rich@Rice.edu (Richard Murphey)
Subject: Re: XFree86 problems: the bell, keyboard hanging overnight
Reply-To: Rich@rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University
Date: Fri, 13 Nov 1992 17:01:16 GMT

Support for the bell under X has been added to XFree86 using either
Holgers new `keycap' driver or a modified 0.1 pccons driver.

The current status is: it's gone through alpha testing and is ready
for the next beta test.  If you want it early, feel free to beta test
it.  After the beta test it will be in the general release.

I've not been able to track down the cause of the keyboard hanging
overnight.  I've narrowed it down to something invoked by /etc/daily,
but we need more information before we have an idea of the cause.

Rich Murphey
Newsgroups: comp.unix.bsd
From: mjl@bos.locus.com (Mike Leibensperger)
Subject: Re: [BSD4.3reno] /bin/sh problem?
Organization: Locus Computing Corp., Boston Massachusetts USA.
Date: Thu, 5 Nov 1992 18:37:21 GMT


In article <1d9m3vINN8nh@charnel.ecst.csuchico.edu>
rodmur@ecst.csuchico.edu (Dale Harris) writes:

   Has anyone ever tried doing a function or sub-routine in a shell script
   in BSD4.3 or BSD4.4, it doesn't seem to want to work, and it works on 
   several other flavors of Unix.

   func()
   {
   shell script stuff here
   ;}

   func

You only get shell functions with the Korn shell (/bin/ksh, linked to
/bin/sh on some systems).  The Korn shell requires a seperate license
from AT&T or USL or whatever, so I doubt that stuff straight out of
Berkeley (4.3reno, 4.4, Net2) comes with it.

	yr obdnt svnt,
	mjl
--
Michael J. Leibensperger      "Rats and roaches live by competition under the
Locus Computing/Boston		 laws of supply and demand; it is the privilege
25 Mall Road; Burlington MA	     of human beings to live under the laws of
01803 (617)229-4980 mjl@locus.com       justice and mercy."  -- Wendell Berry
Member of the League for Programming Freedom --- write league@prep.ai.mit.edu
From: rcs98326@zach.fit.edu (Vijay Kothari/ADVISOR Pollack)
Newsgroups: comp.unix.bsd
Subject: [BSD386] How to boot with 3-1/4 inch floppy
Date: 12 Nov 92 20:12:00 GMT
Organization: Florida Institute of Technology, Melbourne USA

Hi 386 BSD users!

	Please let me know if I can boot 386 BSD using a small floppy.
I don't have a high density 5 - 1/4 inch floppy in my computer but the
disk image available in public domain seems to be only for the 5-1/4
high density floppy. Is there any way I can boot with small floppy.

Thanks for your time
-skdutta

NB - Please send reply via e-mailat rcs98326@cs.fit.edu
From: pierre@pcch01.triumf.ca (Pierre Amaudruz)
Newsgroups: comp.unix.bsd
Subject: Floating point operation under 386BSD
Date: 7 Nov 1992 01:12:10 GMT
Organization: TRIUMF, Vancouver BC
Distribution: world
NNTP-Posting-Host: pcch01.triumf.ca

hello
Having installed successfully 386BSD running Xwindow in 1024x768
on a 486/25 or/33 with XL wonder, the next step for us was performances.
As our private benchmark tests did not satisfies us, the question is :

a) Does 386BSD use the internal Floating Point Processor(FPP) of the 486?

b) Does libm.a emulate the FPP operation to be portable on 386 w/o 387?

c) Is there some tools to check if the FPP is being used?

d) using gdb> info float<cr> does return me NOTHING! Is is suppose to
  to tell me something?

e) Should I get my hand on a special library? 

-- 
-------------------------------------------------------------------
Pierre-Andre Amaudruz
TRIUMF, Vancouver BC
Newsgroups: comp.unix.bsd
From: "Scott Nesbitt" <p00135@psilink.com>
Subject: trouble with 0.1 on compaq 25e
Organization: Nesbitt Consulting
Date: Fri, 6 Nov 1992 01:43:53 GMT
X-Mailer: PSILink (3.2)

having touble getting the dist.fs floppy to boot in a compaq 386/25e.
tried both the regular dist.fs floppy, and the dist.0.1.compaq.fs
floppy from met.super.org.  

when i boot, the floppy light goes on for three seconds, then the
machine hard boots; repeat.

any suggestions would be appreciated.  do i have to regress to 0.0?

thanks

scott 
Newsgroups: comp.unix.bsd
From: kapela@prism.poly.edu (Theodore S. Kapela)
Subject: Re: [386BSD] XFree memory requirements, swap space
Organization: Polytechnic University, New York
Distribution: comp
Date: Thu, 12 Nov 92 17:47:32 GMT

In article <INKARI.92Nov10020725@lk-hp-12.hut.fi> inkari@snakemail.hut.fi (Juha Inkari) writes:
>
>Adding swap was also a piece of cake. The install program reserves a
>swap partition but it was not marked as one. So I did a disklabel -e
>/dev/rwd0a and changed /dev/wd0b partition to type swap and added a
>line /dev/wd0b swap swap sw 0 0 to /etc/fstab.
>

The entry in fstab isn't needed.  The GENERIC kernel in the distribution
looks for swap on wd0 and as0.  Look for the line in the config file 
(in /sys/i386/conf, if I remember correctly) that starts "root on . . ."
The "swap on wd0 and as0" says that the kernel should look at the disklabels
on wd0 and as0 for partitions marked as swap, and if it finds them, to use
them.

You only need to add entries to /etc/fstab when swap space is added on
other devices.  You don't need to rebuild the kernel just to add
swap space.

-- 
..............................................................................
 Theodore S. Kapela				kapela@poly.edu
 Center for Applied Large-Scale Computing	
 Polytechnic University
From: stephens@ultrix.csc.usf.edu. (Daniel Stephens (CSC))
Newsgroups: comp.unix.bsd
Subject: Gargantuan problems with oddball SCSI adapter
Date: 1 Nov 92 08:57:38 GMT
Organization: Univ. of South Florida, Center for Scientific Computing


	I seem to have run into a rather nasty problem attempting to get
my BSD system up.  I've installed it once before to a smallish MFM hard
drive with comendable success, however I've recently purchased a SCSI
card and drive and now want to use them for my system and toss the MFM
deal to the Salvation Army (or wherever).  
	The problem is simple, BSD refuses to acknowledge my SCSI
adapter.  Bloody well skips over it without a second thought.  What are
the necessary parameters to use a SCSI adapter (port address, irq, drq
etc) and is there any way to change these parameters to work with my
card.  I'm no UNIX guru, and in fact, have decided to learn BSD to get a
better understanding of this odd OS.

Thanks much in advance, 

Dan Stephens,
University -o- South Florida
Center for Scientific Computing
Newsgroups: comp.unix.bsd
From: fty@bizarre.rtpnc.epa.gov (Frank Terhaar-Yonkers)
Subject: Re: Ported software list.
Organization: United States Environmental Protection Agency
Date: Tue, 10 Nov 1992 13:41:10 GMT

Is anyone else having a problem?  I show 750 accesses to this archive in the 
past two months and no other complaints ...

- Frank

In article <1992Nov9.145903.19244@autelca.ascom.ch>, nbladt@autelca.ascom.ch (Norbert Bladt) writes:
spedpr@thor.cf.ac.uk (Paul Richards) writes:

>Well I've started on a ported software list. I wouldn't even call this a
>first draft. It's really so we can decide if the format's right and get
>people to start making submissions. If you've ported any software to
>386bsd then fill in the form below and mail it to me. If you think there
>should be other fields in the form then let me know. 

First, thanks for this list.

[ other packages deleted - NB. ]

>---------
>PACKAGE: XS3
>---------
>Description:	X server for the S3 chipset (very similar to the
>		8514/a)
>Status:		
>Maintained by:	Primary: Amancio Hasty
>		Secondary: 
>OS version:	
>Installed at ref.tfs.com: 
>Available from: sunvis.rtpnc.epa:/pub/386bsd/incoming
Is somebody really able to access this host ?
From Europe it is NOT possible. Except for one directory listing of
pub/386bsd/incoming (and, believe it or not: XS3 is NOT in this directory)
I couldn't get anything from this before the ftp-server crashes etc.
>Requires: 
S3 VGA board, of course.
>Notes:
ftp-server seems to be very flakey. I tried several other hosts in the states
without any problem. But this one: unreachable at best, sorry.

I would really like to run this server, but can't for obvious reasons.
BTW: How big is the XS3 server, if I am able to connect to ref.tfs.com, someday.

Norbert Bladt.
-- 
Norbert Bladt, Ascom Autelca AG, Worbstr. 201, CH-3073 Guemligen, Switzerland
Phone: +41 31 999 65 52			FAX: +41 31 999 65 44
Mail: nbladt@autelca.ascom.ch   UUCP: ..!uunet!mcsun!chsun!hslrswi!aut!nbladt

-- 
-------------------------------------------------
Frank Terhaar-Yonkers	fty@bizarre.rtpnc.epa.gov
Unisys/U.S. EPA		(919)541-2297

Newsgroups: comp.unix.bsd,comp.os.minix,comp.os.linux
From: bselling@darwin.helios.nd.edu (brian selling)
Subject: Floppy overrun/underrun messages...what does it mean?
Organization: OUC, University of Notre Dame
Date: Thu, 12 Nov 1992 00:48:14 GMT


I recently switched from an ESDI setup to a SCSI setup.  On reinstalling
linux from SLS ver 0.98pl1 i got numerous floppy overrun/underrun errors...
retrying, etc.  This happened both when I was mkefs -c -ing the drive, and
on the install from floppies.  I don't remember this happening when I installed
on the ESDI drive.  My new controller is a Ultrastore 14F.  But everything
seems to work in the end.  I have X and all up and running, so I guess the
retries worked, but anyone know why I might have gotten these errors or whether
its serious or not?

--
Teresa Selling
South Bend, IN
Newsgroups: comp.unix.bsd
From: alm@netcom.com (Andrew Moore)
Subject: reset (was Re: why erase/kill echoed by [c]sh in xterm? [386BSD/X386])
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Date: Sun, 8 Nov 1992 09:04:38 GMT

In article <1992Nov7.111935.2731@netcom.com> I <alm@netcom.com> write:
>The new X386 is wonderful!  And it is with much trepidation I ask the
     ^^^
The old too!

>world: why does the erase char print under the 386BSD shell, rather than go
>backwards one char (it does delete a char backwards, it just doesn't

The terminal needs to be reset.  The problem is evidently that
.login/.profile is not executed when xinit invokes xterms.  One
solution is to run xdm instead.  Or a reset/tset can be put in .cshrc
(for interactive shells only!  - so the which command doesn't reset the
screen).  Unfortunately tset is not part of the distribution yet...
Since I don't like invoking reset even on interactive shells except at
login, I just type reset as the first command after xinit.  Is there a
better way?  Thanks.
-Andrew Moore <alm@netcom.com>
Newsgroups: comp.unix.bsd
Subject: sendmail probs :( (HELP)
From: <G72BB@CUNYVM.BITNET>
Date: Saturday, 7 Nov 1992 17:20:16 EST
Organization: City University of New York/ University Computer Center

Hello:

     I've managed to sucessfully install 386BSD on a 486 33 machine and
have it sitting on a SLIP behind a SUN SPARC Server.  Everything seems OK
I can send mail, ftp, telnet ... But am having a h*ll of a problems re-
ceving mail.  Everytime I try (and I have tried to figure it out by
playing with my sendmail.cf) I get mail bounced back.  (i.e. I can not
receive mail.

     The error messages I get are:

>>> HELO mh-slip.educom.edu
<<< 553 mh-slip.educom.edu config error:  mail loops back to myself
554 < marco@mh-slip.educom.edu>... Service unavailable

     Any suggestions, ideas etc....   Thanks in adcance for the help.


---

     Marco Hernandez   <mah@info.educom.edu>
           alternates:  g72bb@cunyvm.cuny.edu
                        marco@bitnic (BITNet)
From: fish@ecst.csuchico.edu (Kevin Haddock)
Newsgroups: comp.unix.bsd
Subject: Help for g++ memory leaks?
Date: 10 Nov 1992 07:34:06 GMT
Organization: California State University, Chico
Distribution: world
NNTP-Posting-Host: cscihp.ecst.csuchico.edu

Could someone please straigten me out about the supposed memory
leaks in g++ (or make?).  I cannot compile any program of any
substantial size because of the slowdown/hanging problem as described
by several parties in this group.  I have installed the patch as per
message id <JJC.92Oct30133157@jclark.jclark.com> to cplus-decl.c but
my g++ is to BUGGY to recompile itself!  Can someone send me the
binary to fix this.  It seems a little rediculious that I should have
to create a 60+MB swap space to recompile this thing.  It is a little
like putting more bilge pumps on rather than fixing the hole in the bottom
of the boat!

Thanks for your tolerance at letting me rant....

-Kevin
fish@cscihp.ecst.csuchico.edu

-------
Hackers do it with fewer instructions!
Newsgroups: comp.unix.bsd
From: ujlh@pool.info.sunyit.edu (James Henrickson)
Subject: Re:  WD 8003 help
Organization: State University of New York -- Institute of Technology
Date: Sat, 7 Nov 1992 04:09:36 GMT


Will the person that mailed me asking for WD 8003 help please mail me
again?  I finished my response but deleted your message before sending
it. 

Sorry for the inconvenience.

-- 
Jim H.
*
* James L. Henrickson  |  "I don't need a signature, I need a job!"
* ujlh@sunyit.edu      |  BSCS, December 1992
Newsgroups: comp.unix.bsd
From: alm@netcom.com (Andrew Moore)
Subject: Re: : How create /dev/lp within 386bsd-0.1
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Date: Wed, 11 Nov 1992 07:34:37 GMT

In article <1992Nov10.210330.7080@delos.stgt.sub.org> migieger@delos.stgt.sub.org (Michael Giegerich) writes:
>Hi,
>
>the subject says it all...
>When booting I receive a message like "lpd[] /dev/lp not found";
>

There are several lpt.c patches/replacements available.  You might
start with Eric Haug's  lpt.driver.patch available on
agate.berkeley.edu in pub/386BSD/386bsd-0.1/unofficial.  This includes
instructions for installing the driver.  There is also an lp.c
replacement which does not use interrupts and is said to be faster.
-Andrew Moore <alm@netcom.com>
Newsgroups: comp.unix.bsd
From: bbs.barfeau@tsoft.sf-bay.org (David Fox)
Subject: [386bsd] patch for free: memtop problem?
Organization: The TSoft BBS and Public Access Unix, +1 415 969 8238
Date: Fri, 6 Nov 1992 18:58:50 GMT

I am in the midst of applying Terry's patchkit to my kernel.  While I
was working on this, occasionally I'd get a message like:
 
free: bad block memtop xxxxx
 
After a few of these, csh would die, I'd have to relogin, and I'd find
a core.csh file.
 
I didn't specifically find a patch in Terry's patchkit to address
this problem.  So the question is which patch solves the problem?

--
David Fox (bbs.barfeau@tsoft.sf-bay.org)
Newsgroups: comp.unix.bsd
From: grefen@wilbur.uni-mainz.de (Stefan Grefen)
Newsgroups: comp.unix.bsd
Subject: Re: Input/Output Errors (with Julian's SCSI drivers)
Date: 5 Nov 92 09:20:40 GMT
Organization: Johannes Gutenberg Universitaet Mainz

In article <1992Nov4.021808.6027@tfs.com>, julian@tfs.com (Julian Elischer) writes:
|> In article <49224@shamash.cdc.com> pbd@runyon.cim.cdc.com (Paul Dokas) writes:
|> >I'm having mysterious problems with my hard drives.  About once every day or
[...]
|> >My machine is a 386-40, 1542B, with CDC wren IV (330MB) internal and an
|> >IMPRIMIS 1.0GB external.  I also have an Archive VP 150e tape drive.
|> >BTW, I'm using Julian's SCSI driver (3rd alpha release).
|> >-- 
|> 
|> This is a new one..
|> the unit attention error message indicates that the scsi device has
|> either been reset or has had a powerdown.
|> It is possible that you have:
|> 1/ a flakey power supply or cable
|> 2/ a suspect controller
|> 3/ a suspect scsi cable. (check for frayed copper on the ends)
only 3/ beacuse the 1GB is external !!
Have you dismounted the resistors on the Adaptec ???
Not doing so will lead to 3 terminators on the wire instead of 2.
MfG
 Stefan
-- 
Stefan Grefen   ---   Johannes Gutenberg University Mainz   ---    Germany
Email: grefen@goofy.zdv.uni-mainz.de       ---        Phone:  06131/392415
Newsgroups: comp.unix.bsd
From: andrick@sun.rhrk.uni-kl.de (Ulf Andrick [Biologie])
Subject: [XFree86] Problems with tvga9000
Organization: University of Kaiserslautern, Germany
X-Newsreader: Tin 1.1 PL4
Date: Fri, 13 Nov 1992 14:47:52 GMT

I have a Trident tvga9000 card with 512 k RAM and some noname 14" 
monitor with 35.5 kHz max. hor. scan freq..
This hardware allows me to use 800x600 256-colour graphics
under DOS.  The monitors data sheet gave some timings, 
from which I calculted the dot clocks for Xconfig and I got
exactly the VESA values as supplied by Th. Roell.
In fact, the mono server ran with Xconfig.idiot without any
modification. It also tolerated setting the chipset to
tvga8900 and giving the clocks 25 28 45 36 as mentioned in
README.trident. xclock.exe also reports these values. 
(What I want to use is 36 MHz.)

The colour server refused to run with
Xconfig.idiot. I changed chipset and clocks and commented the
pseudo-800x600 modes out of Xconfig and then the server run,
and the timings appeared to be correct, but only that one line
output by the video card was spread over two lines on the
screen. Apparently, the graphics card produces a clock
frequency which is only half of that required. 
I also tried to comment chipset and/or clocks out and let the
server "autodetect". But either the server exits without doing
anything or it tries some clocks and exits then.

I also used the tvgactrc-utility under DOS. It shows me that
there is an optional 72 MHz clock available, and in fact, when
I used it, it displayed the corrrect hor. scan freq. and
produced a correct result, while 36 gave strange values. I
don't understand that. Maybe, there is something wrong with
the hardware. But the software seems to be wrong as well then.
And then: why does the mono server work and the colour server
not? Why does the card work under DOS? I wasn't able to
produce a better output by shifting the 36 around in my clocks
entry.

Here is (from memory) what I use in Xconfig:

vga256
  chipset "tvga8900"
  clocks 25 28 45 36 .....
  videoram 512
  modes "800x600" "640x480"

  viewport 0 0

nd the VESA dot clocks for 800x600 36 MHz.

Any help? Any other experiences with the mentioned graphics
adaptor? Is tvga9000 not compatible to tvga8900C?

--
Ulf R. Andrick                                andrick@rhrk.uni-kl.de
FB Biologie - Tierphysiologie
Universitaet                             Was du nicht selber weiszt, 
D-W 6750 Kaiserslautern       das muszt du dir erklaeren (Tegtmeier)
Newsgroups: comp.unix.bsd
From: raz@socs.uts.edu.au (The Inimitable Raz)
Subject: Re: [386bsd] Colorado Jumbo tape drive device driver.
Keywords: Colorado, No dice, Tape drive
Organization: Computing Sciences, Uni of Technology, Sydney.
Date: 12 Nov 92 03:44:48 GMT

root@hrd769.brooks.af.mil (Super User) writes:

>  I was pursueing pretty much the same thread in comp.os.minix about a year
>ago.  Does the Jumbo tape drive have a QIC number?  If so, the address to
>write to for the complete scoop on the interface is available from
>Freeman Associates in California for FREE!  If it does, drop me a line and
>I will scramble around here until I find all of my stuff.

YES! Colorado responded to my fax within 48 hours which, given the 
experience of someone else here seems pretty good. Their advice was

	- Get the QIC-40, 80, 117 specs. These are the minimal set
	to get started. QIC-117 is apparently particularly tricky
	to implement.

	- Research floppy controller I/O. Apparently the drive
	doesn't even look like a floppy to the floppy chip! What
	this means in practice, I have no idea.

	- Research the DMA and beware of its limitations.

	- Read a text on error correction before ANY of the 
	above!

>  I had the same thought for my QIC-40 floppy tape drive for minix.  The
>actual interface was a relative snap (although I never did commit it to 
>disk), but the error correction algorithm used is very scary.  I had to 
>sit at the feet of a mathematician for a solid week before I understood
>the rudiments of finite field mathematics.  Reed-Solomon ECC is its name,
>and it is not for the faint of heart!!!  The project was pretty much 

OH NO! This is the same scheme used for CD ROM (unless I'm mistaken).
I once spent 4 hours getting a VAGUE understanding of it - nowhere near
enough to implement.

Can you tell me where to get copies of the standards I mentioned?


--
Bye for now.
         - Raz           

raz@socs.uts.edu.au   (Roland Turner)   (OH) 61 2 319 5700
Newsgroups: comp.unix.bsd
From: tgt@cstr.ecn.purdue.edu (Conan the Librarian)
Subject: XFree and ATI Ultra R1.4
Keywords: does it work yet?
Organization: Purdue University Engineering Computer Network
Date: Sun, 8 Nov 1992 07:27:40 GMT

This is a question regarding running the latest XFree in 386BSD
with an ATI Graphics Ultra card.  Has anyone got this to work with
a Revision 1.4 graphics card?  I have a Gateway 2000 486-33 system
with a "stripped down" (for Gateway) version of the Graphics Ultra
card (no bus mouse, but otherwise I believe the card is the same).
Unfortunately however the revision number is 1.4, and (some months
ago) I fought with this and could not make XFree work with it.

If anyone has been able to get such a setup to work, PLEASE email
me on compuserve with the details.  Thanks.

-tom tobin

Compuserve: 71172,2707
Internet: 71172.2707@compuserve.com

--
Tom Tobin				UUCP:     pur-ee!tgt	
Dept. of ChE				INTERNET: tgt@ecn.purdue.edu
Purdue University			Ma Bell:  home (317) 463-0189
W. Lafayette, IN 47907				  office "   494-4052