HDTenEightyP/NetNews huggingface dataset:
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: 386BSD new user questions
Organization: Weber State University  (Ogden, UT)
Date: Thu, 8 Oct 92 01:27:59 GMT

In article <1992Oct7.154113.3611@hpcvmcdj.cv.hp.com> carlj@hpcvmcdj.cv.hp.com (Carl Johnson) writes:
>A couple days ago I asked for help getting my WD8003 card working.  I
>now have it working, so I am posting the results, in case others have
>a similar problem.
>
>My lan would hang when I tried to make a connection to another machine,
>and any incoming packets would give a 'reject 65531' message.  Peter
>Cooper suggested by email that there might be a conflict in the kernel
>with one of the other lan card drivers.  I removed the other lan card
>drivers from the configuration and then re-configured the kernel, and
>now the lan works fine.

Kernels with some (not all and certainly not Beta level) patches are on
agate and have been there for some time.  They are basically replacement
dist.fs disks.  One of the "fixes" incorporated is leaving out either the
isolan or wd80x3 driver, respectively.

Whenever you have a problem with booting, you should strip the hardware
and try again.  If this fails, either start building boot disks (if you
have more than one machine, and one of them works) or start downloading
dist.fs images from agate and elsewhere (the machine "rachel" in the UK,
which I can never get to, has or will have fully patched kernels on
dist.fs disk images, ready for download; Adrian Hall, who posts here,
runs the 386BSD archive there).

The problem is basically that PC hardware is too stupid to autoconfigure
it's hardware if it's on an ISA bus or an EISA bus pretending it's ISA.
The ethernet drivers generally "probe" on the basis of making sure the
memory address is there, and then (most of the time) checksumming the
ROMs... thus they can find things which aren't there.  Since most of the
ethernet drivers camp on IRQ 2, this means only one of them is going to
be able to handle the interrupts.  This is generally the last board that
is "found" to be installed.

Once you are set up to rebuild the kernel, do it, removing all drivers for
devices not in your machine.  This will reduce the chances for future
conflicts, as well as taking care of most existing ones.


					Terry Lambert
					terry@icarus.weber.edu
					terry_lambert@novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                        "I have an 8 user poetic license" - me
 Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: anything@max.u.washington.edu
Newsgroups: comp.unix.bsd
Subject: [XFree86] crypt how to, new session manager
Date: 13 Oct 92 18:52:38 GMT
Article-I.D.: max.1992Oct13.115238.1

I have a couple questions concerning XFree86 on 386bsd-0.1

 1.) I made the necessary changes to run crypt on my machine.
what changes do I need to  make to XFree86 so that it works with
crypted passwords?

2.) I need a better session manager, I am not very knowledgeable
about X but surely there must be a session manager that will allow
me to start programs and such without having to start them from an
xterm

3.) anyone know of a good file manager for X?

thank you for all assistance
Don Levinson
anything@max.u.washington.edu
From: r_moore@vger.nsu.edu
Newsgroups: comp.unix.bsd
Subject: 386bsd 0.1 in 3 1/2" format
Date: 15 Oct 92 18:17:10 EDT

Hello,
  I have been trying to find 386bsd 0.1 on 3 1/2" floppy format via an FTP
site. I have been to about 7 sites I found through archie but they all just
have the 5 1/4" in format. Could some please point me in the right direction ?
Thanks,  Richard

Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: [386BSD] Installing XFree86 to std.dist. + patchkit
Organization: Weber State University  (Ogden, UT)
Date: Mon, 12 Oct 92 22:02:19 GMT

In article <1992Oct12.200111.21502@athena.mit.edu> bri@pegasus.mit.edu (Brian D. Carlstrom) writes:
>*My problem is applying the 386bsd.patches to my kernel sources.
>does anyone have sources that were patches withthe patchkit and
>that will work with XFree86? should i patch the src's with the
>XFree86 patches first and then the patchkit? any help appreciated.

The patchkit contains all the changes necessary to run X.  These patches
are the ones that came with the latest X distribution.  The only thing
you need to do to run X is set the XSERVER and UCONSOLE(?) options before
rebuilding your patched kernel.  The X software should "just run".


					Terry Lambert
					terry@icarus.weber.edu
					terry_lambert@novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                        "I have an 8 user poetic license" - me
 Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: zawada@softage.demon.co.uk.demon.co.uk (Mark D Simpson)
Subject: PPP for 386bsd 0.1?
Distribution: world
Organization: Softage Solutions
Date: Tue, 6 Oct 1992 04:41:31 +0000

Has anyone out there got PPP running under 0.1 386BSD.  There was
a version that was adapted for 0.0  386BSD floating around, but it doesn't
work under version 0.1.

Mark Simpson
(Desperately wanting to get his 486 on the internet under 386BSD).
Newsgroups: comp.unix.bsd
From: jtk@netcom.com (Jane Valencia)
Subject: [386BSD] crash 0/2
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Date: Sat, 10 Oct 1992 21:13:09 GMT

While exploring the internals of 386BSD, I found that I'd written
enough stuff that a crash-dump analyzer program wouldn't be too
hard to throw toether.  So included is the first release of such
a beast.  It does process dumping, virtual and physical examination,
stack backtraces, and inode/vnode examination.  It's mostly just
a framework, so please let me know if I've left out something
obvious.

Certain files I used were leveraged from existing code.  I've
tried to leave the copyright messages intact.  The rest of the
code is orignal, and you can do anything you want with it.

					Regards,
					Andy Valencia
					jtk@netcom.com

Newsgroups: comp.unix.bsd
From: peter@wiesel.cosy.sbg.ac.at (Peter Burgstaller)
Subject: Starting XFree861.1
Organization: University of Salzburg / Austria
Date: Thu, 8 Oct 1992 09:48:50 GMT

Hi folks!

I got a problem with XFree861.1
I did the tar and x386install stuff; everything was fine!
then i edited the Xconfig file, found my ET4000 card
(2-The-Max) took the parameters and used the standard monitor
settings!
Then I started xinit (also startx) then I got the following 
Message!

XFree86 v1.1 Xwindow System
(protocol version 11, revision 0 vendor release 5000)
Configured drivers: 
  VGA256(256color svga):
      ET4000,ET3000,PVGA1,GVGA,ATI,TVGA8900
XIO:  fatal io error 32 (broken pipe) on Xserver ":0.0"
      after 0 reqests (0 known processed) with 0 events remaining.
      The connection was probably broken by the server shutdown or
      Killclient.

Anybody any suggestions ??
- Please help!
--
/-------------------------------------------------------------------\
| Peter Burgstaller| Student of Computerscience			    |
| (peter@cosy.sbg.ac.at)| in Salzburg, Austria (Europe)		    |
| "So Long, and Thanks for All the Fish" (Douglas Adams)	    |
\-------------------------------------------------------------------/
Newsgroups: comp.unix.bsd
From: ob@obh.in-berlin.de (Oliver Brandmueller)
Subject: Hardware handshake (RTS/CTS) on serial line with 386BSD
Organization: obh - private bbs in Berlin/Germany
Date: Fri, 16 Oct 92 13:58:11 GMT

Hi out there,

how can I use the hardware handshake (RTS/CTS) with 386BSD on
com1? Without RTS/CTS handshake it is impossible to have a high
speed modem connected.
Does another serial device driver exist for 386BSD which does
this job or can I use the "normal" one and just have to #define
something in the sources?!

Bye, Olli


-- 
| Oliver Brandmueller | Detmolder Str. 64 | 1000 Berlin 31 | Germany - (FRG) |
| ob@obh.in-berlin.de | V +49 30 853 6980 | Cityruf 315 30 68 30 (numerisch) |
| "Ich werde Millionaer, heirate Jodie Foster und nehme mir eine Nymphomanin |
|          als Putzfrau. Dann habe ich alles erreicht." - ob@school          |
Newsgroups: comp.unix.bsd
From: rich@Rice.edu (Richard Murphey)
Subject: Re: It actually works (almost 8-)
Reply-To: Rich@rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University
Date: Fri, 9 Oct 1992 05:34:15 GMT

In article <48408@shamash.cdc.com> pbd@runyon.cim.cdc.com (Paul Dokas) writes:
   Well, I've compiled X11R5 (pl17 with XFree1.1) and it actually works
   on my machine (386-40, Diamond SpeedStar+, 8MB 1542B, 1.5GB of disk)
   I'm quite impressed (although now I need a monitor greater than 14")

   But there only two catches.  I can't get PEX or the shape extentions
   to work properly.  PEX gobbles up lots of memory and starts the machine
   to swapping so badly that nothing responds.  Even after 10 minutes of
   waiting I was not able to reclaim my Xserver.  I guess that PEX just
   requires a lot of memory (more than I've got anyway).

   Shape extentions almost works.  oclock for example, comes up with the
   window manager title bar and a white circle.  Then it just sits there,
   nothing is ever drawn onto the white circle.  It also slows down my
   Xserver quite a bit while it is running.

   Anyone have any suggestions about fixing these things?

PEX and the Shape extensions have worked fine in all the versions I've
tested.  My setup was almost identical (486-33, 8M, Orchide Pro II,
1542B), so unless you are trying to use a non-stock compiler I would
check the setup.

   BTW, for those of you who asked me, here is the disk space requirements
   for X11R5.  All results are in 512Kb blocks as given by 'du':

     170151   ftped MIT distribution (mit-[1234].*, contrib-[123].* and fixes)
     265396   mit directory:  source, objects and executables (created with 'make World')
      41769   /usr/bin/X11
      40897   /usr/lib/X11 (around 43000 with the X libraries in /usr/lib/lib*.a)
       5074   /usr/man (only expanded X libraries)
     ------
     523287   total (around 260MB for me, your mileage may vary)

You must be compiling with the debugging option.  My source tree takes
up 73Mb and the installed distribution takes up 26Mb.  Rich
From: scotty@gagetalker.com (Scott Turner)
Subject: IAnyone seen this with XFree86 1.1  and 386bsd?
Organization: L5 Computing
Date: Thu, 8 Oct 1992 12:22:54 GMT

I've re-extracted src01.
I then installed the beta-1 patch kit.
I then backed out patches 4, 21, 38, 47.

I installed the XFree86 1.1 binaries from agate. And then
moded Xconfig to use an et4000 chip set and try for 640x480
with a 25MHz clock (the first one on the clocks line.) And
I'm using a Logitech serial trackman on tty00.

Whan I type X or xinit the screen flips into graphics mode
and shows me a bunch of un-inited stuff on the screen. Then
the screen flips back to text mode and the server exits with
no error message. (xinit says the pipe to the server was
broken.)

Has anyone else run into this one? (I've tried three
different et4000 based cards and I've worked with
Roel's server for years.)

Scotty

Newsgroups: comp.unix.bsd
From: futzi@uni-paderborn.de (Michael Kutzner)
Subject: Re: Starting XFree861.1
Organization: Uni Paderborn FB 17 Informatik GERMANY
Date: Fri, 9 Oct 1992 11:35:19 GMT


>>>>> About Starting XFree861.1, Peter Burgstaller said:
Peter> Nntp-Posting-Host: wiesel

Peter> Hi folks!

Peter> [...]

Peter> XFree86 v1.1 Xwindow System
Peter> (protocol version 11, revision 0 vendor release 5000)
Peter> Configured drivers: 
Peter> VGA256(256color svga):
Peter> ET4000,ET3000,PVGA1,GVGA,ATI,TVGA8900
Peter> XIO:  fatal io error 32 (broken pipe) on Xserver ":0.0"
Peter> after 0 reqests (0 known processed) with 0 events remaining.
Peter> The connection was probably broken by the server shutdown or
Peter> Killclient.

Peter> Anybody any suggestions ??

I have had the same problem, because there was the wrong com-Port for the
mouse in my Xconfig (/dev/com?).

Michael

********************************************************************************
** -------------------------------------------------------------------------- **
**     Michael Kutzner    **  X-Betreuung     **  <futzi@uni-paderborn.de>    **
**                                                <xgurus@uni-paderborn.de>   **
** -------------------------------------------------------------------------- **
********************************************************************************
From: vak@guam.relcom.msk.su.rd.relcom.msk.su (Serge V.Vakulenko)
Newsgroups: comp.unix.bsd
Subject: [386BSD] patch for mtools to find C and D automagically
Date: 12 Oct 92 16:16:22 GMT
Organization: Relcom R&D
X-Newsreader: Tin 1.1 PL4

Here is my patch for mtools from 386bsd srcdist,
which makes it possible to work with DOS partitions
on hard disks without recompiling mtools every time
you change partition table.  C and D disks are marked
in devices table as having offset -1, and
DOS partition then is searched through partition table.

Serge Vakulenko

*** /tmp/mtools/devices.c	Mon Oct 12 19:06:10 1992
--- ./devices.c	Tue Oct 13 07:12:08 1992
***************
*** 30,33 ****
--- 30,37 ----
  	{'B', "/dev/rfd1a", 0L, 12, 0, (int (*) ()) 0, 40, 2, 9},  /* 360k */
  	{'B', "/dev/rfd1a", 0L, 12, 0, (int (*) ()) 0, 40, 2, 8},  /* 320k */
+ 	{'C', "/dev/rwd0d", -1L, 16, 0, (int (*) ()) 0, 0, 0, 0},
+ 	{'C', "/dev/ras0d", -1L, 16, 0, (int (*) ()) 0, 0, 0, 0},
+ 	{'D', "/dev/rwd1d", -1L, 16, 0, (int (*) ()) 0, 0, 0, 0},
+ 	{'D', "/dev/ras1d", -1L, 16, 0, (int (*) ()) 0, 0, 0, 0},
  	{'\0', (char *) NULL, 0L, 0, 0, (int (*) ()) 0, 0, 0, 0}
  };
*** /tmp/mtools/init.c	Mon Oct 12 19:06:06 1992
--- ./init.c	Tue Oct 13 07:12:59 1992
***************
*** 27,30 ****
--- 27,31 ----
  extern struct device devices[];
  static struct bootsector *read_boot();
+ static long find_partition ();
  
  int
***************
*** 62,69 ****
  
  		name = expand(dev->name);
! 		if ((fd = open(name, mode | dev->mode)) < 0) {
! 			perror("init: open");
! 			exit(1);
! 		}
  					/* set default parameters, if needed */
  		if (dev->gioctl) {
--- 63,68 ----
  
  		name = expand(dev->name);
! 		if ((fd = open(name, mode | dev->mode)) < 0)
! 			goto try_again;
  					/* set default parameters, if needed */
  		if (dev->gioctl) {
***************
*** 72,75 ****
--- 71,79 ----
  		}
  					/* read the boot sector */
+ 		if (dev->offset < 0)
+ 			dev->offset = find_partition (fd);
+ 		if (dev->offset < 0)
+ 			goto try_again;
+ 
  		disk_offset = dev->offset;
  		if ((boot = read_boot()) == NULL)
***************
*** 153,157 ****
  			break;
  
! try_again:	close(fd);
  		fd = -1;
  		dev++;
--- 157,162 ----
  			break;
  
! try_again:      if (fd >= 0)
! 			close(fd);
  		fd = -1;
  		dev++;
***************
*** 323,325 ****
--- 328,352 ----
  
  	return(&boot);
+ }
+ 
+ static long find_partition (fd)
+ {
+ 	char buf [512];
+ 	int i;
+ 	struct partition {
+ 		unsigned char flag, bhead, bsect, bcyl;
+ 		unsigned char system, ehead, esect, ecyl;
+ 		unsigned long relsect, numsect;
+ 	} *p;
+ 
+ 	if (read (fd, buf, 512) != 512 ||
+ 	    ((unsigned short *) buf) [255] != 0xaa55)
+ 		return (-1);
+ 	p = (struct partition *) (buf + 0x1be);
+ 	for (i=0; i<4; ++i, ++p)
+ 		if (p->flag != 0 && p->flag != 0x80)
+ 			return (-1);
+ 		else if (p->system == 4)        /* find DOS-16 partition */
+ 			return (p->relsect * 512);
+ 	return (-1);
  }
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Newsgroups: comp.unix.bsd
Subject: Re: Memory problem
Date: 16 Oct 92 14:36:40 GMT
Organization: Uni-Duisburg FB9 Datenverarbeitung
Reply-To: veit@du9ds3.uni-duisburg.de
NNTP-Posting-Host: du9ds3.uni-duisburg.de
Keywords: memory

In <1bmcvjINN5m3@corax.udac.uu.se> goran@astro.uu.se (Goran Hammarback) writes:

>In article <wmbfmk.719081295@rwb.urc.tue.nl>, wmbfmk@rwb.urc.tue.nl (Marc van Kempen) writes:
>|> Hi, I seem to have a memory related problem with 386bsd.

>It's a known problem that 386BSD just hangs if you fill the swap.
>I call it a bug (I doubt you will find anyone saying it's feature 8-) ).

Of course it is a feature! This demonstrates you drastically that you need
more RAM and more disk (swap-) space. Several OS vendors and OS writers
seem to be heavily "sponsored" by the semiconductor and mass storage industry
just to build in this *feature*. I remember times when a Fortran 77 or
an AZTEC C ran in 51K TPA area (guess when and which OS...)
:-))))

Holger

>-- 
>Goran
>Goran Hammarback              |     goran@astro.uu.se

-- 
|  |   / Dr. Holger Veit         | INTERNET: veit@du9ds3.uni-duisburg.de
|__|  /  University of Duisburg  | "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
|  | /   Dept. of Electr. Eng.   |   Sorry, the above really good fortune has
|  |/    Inst. f. Dataprocessing |      been CENSORED because of obscenity"
Newsgroups: comp.unix.bsd
From: julian@tfs.com (Julian Elischer)
Subject: Re: partition table help?
Organization: TRW Financial Systems
Date: Thu, 15 Oct 1992 01:29:16 GMT

In article <1992Oct14.070315.23390@msuinfo.cl.msu.edu> paoletti@cps.msu.edu (David R. Paoletti) writes:
>
>I'm already using 331 cyls for MS-DOS.  I'd like to have a
>32M root (is this size OK for most things?), 32M swap, and
>the remainder of my disk (692 - 64 = 628 cyls) for /usr.
>
>Now I know that 386BSD's partition a is /, b is swap, and
>c is /usr.  What about the h partition that appears in most of
> the initial disktab entries? Do I have to define partition d at all?
No partition h is user.
take a closer look at eh other disktabs
partition c is "the whole unix space" by tradition, and you should
not try put a file system on it.

>
>Here's my disktab so far:
>
>fj2266|Fujitsu 2266S: \
>	:ty=winchester:dt=SCSI:se#512:nt#64:ns#32:nc#1023:rm#3600:\
>	:pa#65536:oa#677888:ba#4096:fa#512:ta=4.2BSD: \
>	:pb#65536:ob#743424:tb=swap: \
	:pc#1417216:oc#808960: \
	:pd#2095104:od#0: \
>	:ph#1286144:oh#808960:bh#4096:fh#512:th=4.2BSD:
>
>Does anyone see any problems with this?  I know that it may
>take a minute or two to check the math, but any errors?
>
>Thanks,
>  Dave Paoletti :)
>

also:

1/ 32MB for root is too big
the ideal root file system is hardly ever writtnhen to so
that it is unlikely to be corrupted. it should contain
only a small booting subset of unix.

2/ d need not be explicitly given, but that's what it
will do so one might as well put it in to save confusion.

3/ you are using the adaptec's TRANSLATED geometry.
in that manner it is imposssible to express
any thing bigger than what you have shown..
if you use the REAL (or approximatly so) figures
you can get a truer feel for things. 386bsd can use 
real figures.. believe me your drive does not have
63 heads as you suggest. 
(it may even be bigger.. you may find that you have more than
that available but DOS just couldn't express it in any way).
(I don't know that drive so I don't know for sure).

julian





Newsgroups: comp.unix.bsd
From: mark@student.business.uwo.ca (Mark Bramwell CS STAFF)
Subject: Xremote and X for a PC
Organization: University of Western Ontario
Date: Thu, 8 Oct 1992 15:26:58 GMT

With an Intel X11 floating around for 386/486 unix machines, has anyone
ported the source for ms-dos?

It would be nice to be able to 'slip' into the bsd box without supporting
a full 2nd unix box just to be a smart terminal.

I hear that X11R6 will have Xremote.  Will that be an unix thing, dos thing,
or both (or should I say - a generic X thing)?


Most of the X packages for mos-dos cost big $$$, too much for us poor
university employees who want to connect once or twice a week during the night.


mark@student.business.uwo.ca (Mark Bramwell CS STAFF)
Western Business School  --  London, Ontario
Newsgroups: comp.unix.bsd
From: tdphette@mke.ab.com (Thad Phetteplace x4461)
Subject: Re: 386BSD won't boot with AMI BIOS/Gateway 2000
Organization: Allen-Bradley Co.
X-Newsreader: Tin 1.1 PL4
Date: Thu, 15 Oct 1992 14:29:08 GMT

rahardj@ccu.umanitoba.ca (Budi Rahardjo) writes:
: boehme@unvax.union.edu (Eric M. Boehm) writes:
: 
: >I have seen oblique references to a problem with AMI BIOS in other
: >messages. I recently upgraded my BIOS from 030389 to 050591. 386BSD
: >still won't boot. The drive light comes on and stays on. Ctrl-Alt-Del
: >won't regain control -- time for the red button.
: 
: I haven't seen (heard) anybody can get 386bsd up and running on a
: Gateway machine. I have posted twice, but the only responses I have
: were me too mails.
: I phoned Gateway tech. rep. and he knows nothing of 386BSD.
: I guess we (gateway owner) are stuck. I guess I should stick with Linux then.
: 
: -- budi
: --
: Budi Rahardjo <rahardj@ccu.umanitoba.ca>
: Unix Support - Computer Services - University of Manitoba

I have 386BSD running on my Gateway 2000 with no major problems.  I do have
a problem when I try to warm boot (the system hangs) but when I hit the
reset button it starts up fine.  I haven't bothered to try and fix it
because I rarely reboot the system and I'm too busy working on X386 code
and a cross development system.  I'm using Pheonix BIOS but I'm not sure
the problem is BIOS related.  Are you using the patched version of the
boot disks?  My system hung with the drive light on before I got the correct
dist.fs.  

--
Thad Phetteplace
Network Systems Analyst, Allen-Bradley Co.
Phone: (414)382-4461
Email: tdphette@mke.ab.com

The opinions expressed here are entirely my own and not that of my employer...
I am not a slob, I am simply doing an experiment in domestic entropy!

Newsgroups: comp.unix.bsd
From: sbartram@xzaphod.com (Scott Bartram)
Subject: XFree86 gives blank screen
Organization: XZaphod in Rockville, MD
Date: Fri, 16 Oct 1992 20:52:12 GMT


 I had XFree86 1.1 up and running fine a few days ago. Then I did 
something to break it: I decided to start a new source tree so that
I could apply all of Terry's patchkit patches. Since I got everything
fixed up and a new kernel built, I can't run X. When I start the 
server, it flips to graphics mode, blanks the screen and never
draws anything. The programs are running (server, xterm, etc) because
I can type 'exit' and it switches back to text mode like everything
is fine.

 I have even tried going back to my last (pre-patchkit) kernel that
was working, and it does the same thing! Does anybody have any 
idea what's going on or at least a starting point for debugging inside
the server?

scott

-- 
=======================================================================
Scott Bartram
sbartram@xzaphod.com
uunet!xzaphod!sbartram
Newsgroups: comp.unix.bsd
From: randy@chinet.chi.il.us (Randy Suess)
Subject: Re: 16-colour X server?
Organization: Chinet - Public Access UNIX
Date: Sat, 10 Oct 1992 13:19:49 GMT

In article <7656@skye.ed.ac.uk> richard@aiai.ed.ac.uk (Richard Tobin) writes:
>Has anyone written / is anyone writing / are there any plans for a
>16-colour driver for XFree386?  This would be useful for those of us
>with video boards with only 512k and should also be twice as fast as
>the 8-bit version (unless vga is even more brain-dead than it seems).

	It would seem to make more sense to go out and spend $90 on a
	new, supported VGA card.  Sure would be simpler than spending
	the time to write a new server.

-- 
	I am created Shiva the Destroyer; Death, the shatterer of worlds!
	Who is this dog meat who stands before me now?
	That's the biz, sweetheart.
Randy Suess					 randy@chinet.chi.il.us