HDTenEightyP/NetNews huggingface dataset:
From: julian@tfs.com (Julian Elischer)
Subject: Two small patches for the SCSI beta3 release.
Organization: TRW Financial Systems
Date: Tue, 13 Oct 1992 00:20:25 GMT


the following patches fix a couple of problems that some people have
been having:


*** scsiconf.c.oops	Mon Oct 12 17:08:22 1992
--- scsiconf.c	Mon Oct 12 17:18:12 1992
***************
*** 148,155 ****
  
  #ifdef	KODAK_SCANNER
  	printf("waiting for scsi devices to settle\n");
! 	spinwait(1000 * 30);
  #endif	KODAK_SCANNER
  	targ = 0;
  	while(targ < 8)
  	{
--- 148,158 ----
  
  #ifdef	KODAK_SCANNER
  	printf("waiting for scsi devices to settle\n");
! #define SCSI_DELAY 15
! #else
! #define SCSI_DELAY 2
  #endif	KODAK_SCANNER
+ 	spinwait(1000 * SCSI_DELAY);
  	targ = 0;
  	while(targ < 8)
  	{
***************
*** 384,390 ****
  {
  	int	numents = (sizeof(knowndevs)/sizeof(struct scsidevs)) - 1;
  	int	count = 0;
! 	int			bestmatches;
  	struct	scsidevs	*bestmatch = (struct scsidevs *)0;
  	struct	scsidevs	*thisentry = knowndevs;
  
--- 387,393 ----
  {
  	int	numents = (sizeof(knowndevs)/sizeof(struct scsidevs)) - 1;
  	int	count = 0;
! 	int			bestmatches = 0;
  	struct	scsidevs	*bestmatch = (struct scsidevs *)0;
  	struct	scsidevs	*thisentry = knowndevs;
  
*** sd.c.oops	Mon Oct 12 17:05:47 1992
--- sd.c	Mon Oct 12 17:05:47 1992
***************
*** 791,797 ****
  	/*******************************************************\
  	* If the inflo is already loaded, use it		*
  	\*******************************************************/
! 	if(sd->flags & SDHAVELABEL) return;
  
  	bzero(&sd->disklabel,sizeof(struct disklabel));
  	/*******************************************************\
--- 791,797 ----
  	/*******************************************************\
  	* If the inflo is already loaded, use it		*
  	\*******************************************************/
! 	if(sd->flags & SDHAVELABEL) return(ESUCCESS);
  
  	bzero(&sd->disklabel,sizeof(struct disklabel));
  	/*******************************************************\


Newsgroups: comp.unix.bsd
From: eleung@fraser.sfu.ca (Edward Leung)
Subject: driver for bus mouse
Organization: Simon Fraser University, Burnaby, B.C., Canada
Distribution: na
Date: Wed, 14 Oct 1992 07:57:10 GMT

Hi.  I've recently acquired a hard drive with BSD installed.
I was wondering if anyone could let me know where to get a driver
for bus mouse to work with BSD.  I also have a sound blaster pro,
and it would be nice if you could tell me where to get a hold of that
driver too.  Thanks.

Ed.
eleung@sfu.ca
From: zmw@altair.selu.edu (Mike Whisenhunt zmw@selu.edu)
Newsgroups: comp.unix.bsd
Subject: How to use fixit to get DOS and 386BSD on same drive?
Date: 13 Oct 92 09:42:47 -0600
Organization: Southeastern Louisiana University

I'm having the same problem as described below in getting DOS to reside in
a 34MB partition and 386BSD v. 0.1 in an 80MB partition on my 120MB Conner
Peripherals 120MB drive.  When I let the install program use the entire disk
everything installs and boots great, but when I make the partitions and
format DOS, then install BSD, my AMI 386 goes into a panic loop when I try
to boot.  I have retrieved and created the fixit diskette, but could someone
point me to some documentation or describe how I can use the fixit program
to place the disklabel at the proper place within the 80MB partition?  Thanks!
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
Mike Whisenhunt                |Internet: zmw@selu.edu   |How to tell if your
VMS System Manager/Postmaster  |Phone   : (504) 549-3643 |boss has used your 
Southeastern La. Univ, Box 430 |Fax     : (504) 549-5092 |Word Processor? Look
Hammond, La 70402  USA         |"Wise men still seek Him"|for whiteout on CRT.


>I had the same problem on the computer of a friend of mine. He wants to
>have DOS and BSD to live on the same disk. So we installed a DOS partition with
>fdisk on the fresh low-level formatted disk. Then we boot BSD with the dist.fs
>floppy. We told install only to created the BSD partition. We now boot from the
>fixit.fs floppy and edit the disklabel. As Bernard mentioned, at this point the
>DOS partition has gone. I know knew the problem. The `install' program writes
>the disklabel at front of the whole disk and not at the start of the BSD
>partition.  Editing the disklabel with the fixit.fs floppy now edits 
>the correct place, the start of the BSD partition.
From: amurai@specgw.spec.co.jp (Atsushi MURAI)
Newsgroups: comp.unix.bsd
Subject: Re: Maxtor LXT340S
Date: 13 Oct 92 17:12:34 GMT
Organization: System Planning and Engineering Corp., Tokyo, Japan
X-Newsreader: Tin 1.1 PL5

Robert Knier (knier@miller.cs.uwm.edu) wrote:
: 
: 	Would anyone have a disktab entry for a Maxtor LXT340S SCSI
: drive?  I tried to make an entry but was unsucessful due to the 
: sectors per track being 47-72.  

Ooops! Is that true ? I just order the exactry same one for 386BSD-0.1...

If you have a response by e-mail, please summerize and post it..

( Sorry I still can't get mail from outside of domestic..  )

Thanks in advance.

-- 
$@B<0f!!=_(J (Atsushi Murai)                              Junet : amurai@spec.co.jp
SPEC                                                  Voice : (03)3833-5341
System Planning and Engineering Corp.
Newsgroups: comp.unix.bsd
From: erik@eab.retix.com (Erik Forsberg)
Subject: Re: The ultimate 386BSD machine?	(FAQ fodder)
Keywords: 386BSD
Organization: Retix, Santa Monica CA
Date: Thu, 8 Oct 1992 16:49:19 GMT

In article <Bvsss4.9nz@ibmpcug.co.uk> adrian@ibmpcug.co.uk (Superuser) writes:
>In article <1992Oct8.072512.8700@elroy.jpl.nasa.gov> earle@elroy.jpl.nasa.gov (Greg Earle - Gainfully Unemployed) writes:
>>- I have seen some benchmarks whereby a 486DX2/66 outperforms a 486DX/50.  But
>>  I saw a posting by Barry Shein that indicated that due to the bus speed on
>>  the former being only 33 MHz, this would not be a good idea as doing things
>>  like bitblts in X would be faster on a "native" 50 MHz system.  This seemed
>>  perfectly reasonable, so it seems that a 486DX/50 is the best idea.  Right?
>>
>
>I have run 386BSD on both, albeit without X (I cant get the card and
>monitor with the correct resolution at the same time in the office).
>To be quite honest, there is not much difference between the two. I
>think in terms of 386BSD, when you get to these speeds, either will
>do. *I* would go for the DX50, since that has the faster bus system.
>and generally, disk speed has been my downfall.
>
>>- I saw a posting from Lynne Jolitz that I believe mentioned that a 32-bit
>>  disk controller was the best idea.  I have assumed from subsequent postings
>>  that the Adaptec 1542B is the "controller of choice", no?  OK, but that's
>>  an EISA board, correct?  But now I'm confused, I thought that 386BSD didn't
>>  support "EISA machines".  What's the deal?
>>
>>  As an adjunct to this, I expect Julian to jump in with "But an Adaptec 1742A
>>  is supported with my new SCSI subsystem ... ".  Fine, but can one get the
>>  system up first (with it installed) to get to the point where one can
>>  recompile the kernel with the new SCSI subsystem?
>>
>
>Julians SCSI system works by setting th 1742B into 1542 mode, and then
>when the probe works out its a 1742, it shoves the card into enhanced
>mode itself.
>

This seems to be a BAD approach. It would EXCLUDE all existing 1740 cards
from functioning. ONLY the newer 1740A (and obviously 1742A) allows switching
between standard and enhanced mode at runtime. The older 1740 (which probably
still is the most common Adaptec EISA card out there) requires you to
download firmware that is specific to the operating mode.

So, useful support for Adaptec 1740 cards, requires support for enhanced
mode in everything (boot blocks, standalone boots and kernels).

-- 
---------------------------------------------------------------------------
Erik Forsberg, erik@eab.retix.com Phone: (310) 476-7133 FAX: (310) 476-7657
From: RLM@MAINE.MAINE.EDU (Robert L. Metcalf NV1A)
Newsgroups: comp.unix.bsd
Subject: question about mwrite
Date: 15 Oct 92 18:12:35 GMT
Article-I.D.: MAINE.92289.141235RLM
Organization: University of Maine System

I am having a problem trying to use the 'mwrite' command to
write files to a DOS floppy.  I have tried the following without
any luck:

mwrite test.gif "a:test.gif"
mwrite test.gif "A:TEST.GIF"
mwrite test.gif "A:\"
mwrite test.gif A:

Am I totally missing the boat here?  I couldn't find any man pages
for mwrite.  Do any exist?

thanks..
Robert
RLM@Maine.Maine.edu
From: terry@spcvxb.spc.edu (Terry Kennedy, Operations Mgr.)
Newsgroups: comp.unix.bsd
Subject: Re: Lance query
Date: 10 Oct 92 09:17:08 GMT
Organization: St. Peter's College, US

In article <BvvDAt.ItC@flatlin.ka.sub.org>, bad@flatlin.ka.sub.org (Christoph Badura) writes:
> Well, according to SunOS 4.0.somethings le(4S):
> 
>   lr%d: transmitter frozen - resetting
> 	A bug in the LANCE chip has stopped the chip's transmitter
> 	section. The driver has detected this condition and
> 	reinitialized the chip.
> 
> The next to pages list a lot additonal anomalies (:-)) of the chip.

  This seems to no longer be present in 4.1.1. Perhaps Sun discovered that
they mis-read the data sheet?

	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
From: jimj@miller.cs.uwm.edu (James Jegers)
Newsgroups: comp.unix.bsd
Subject: Re: New XFree86 starting problems
Date: 12 Oct 1992 18:03:41 GMT
Organization: University of Wisconsin - Milwaukee
Distribution: world
NNTP-Posting-Host: 129.89.9.13

In article <Bvunnr.5H8@cosy.sbg.ac.at>, peter@wiesel.cosy.sbg.ac.at (Peter Burgstaller) writes:
|> Hi again!
|> 
|> First, THANKS to all who mailed and newsed!
|> Now I'm a little bit closer to the solution!
|> 
|> Second: path settings are O.K
|> 	
|> Here is the result of xdm -nodaemon:
|> 
|> error (pid 88): Can't create/lock pid file /usr/X386/lib/X11/xdm/xdm-pid
]


   Don't ask me why.. But I changed the permissions on the file to
   chmod 666 xdm-pid and now it works...

|> 
|> But this file exists and has rw permissions for root.
|> If I delete this file the same thing happens.
|> 
|> Here is the result of xinit >>& xinit.log
|> 
|> XFree86 Version 1.1 / X Window System
|> (protocol Version 11, revision 0, vendor release 5000)
|> Configured drivers:
|>   VGA256 (256 colour SVGA):
|>       et4000, et3000, pvga1, gvga, ati, tvga8900
|> VGA256: et4000 (mem: 1024k numclocks: 16)
|> VGA256:   clocks: 25 28 33 37 41 45 57 65 13 15 17 18 20 23  0  0
|> VGA256: SpeedUp code selection modified because virtualX != 1024
|> VGA256: SpeedUp mode selected (Flags=0xf)
|> failed to set default font path  
|> '/usr/X386/lib/X11/fonts/misc/,usr/X386/lib/X11/fonts/75dpi/'
|> Fatal server error:
|> could not open default font 'fixed'
|> XIO:  fatal IO error 32 (Broken pipe) on X server ":0.0"
|>       after 0 requests (0 known processed) with 0 events remaining.
|>       The connection was probably broken by a server shutdown or  
|> KillClient.
|> 
|> After that I looked into the fonts directories and found all fonts  
|> compressed, so I thought maybe I should uncompress them, but this
|> ends in the same result!
|> 
|> You can see that the clocks aren't 36, 40 or 50 so I changed a little
|> the values of the 800x600 mode (thats the standard mode for this card)
|> to
|> 
|> "800x600"	40  800 841 968 1056	600 601 605 628
|> 
|> the screen flips to grafix-mode but apparently with wrong timings
|> 
|> Hey dudes help me to make it through!
|> 
|> - Peter 8*(
|> --
|> /-------------------------------------------------------------------\
|> | Peter Burgstaller| Student of Computerscience			    |
|> | (peter@cosy.sbg.ac.at)| in Salzburg, Austria (Europe)		    |
|> | "So Long, and Thanks for All the Fish" (Douglas Adams)	    |
|> \-------------------------------------------------------------------/

-- 
     ______________________________________________________________
    /\               University of Wisconsin -- Milwaukee          \
    \_| Computing Services Division     Computer Science Department |
      |   jimj@csd4.csd.uwm.edu           jimj@miller.cs.uwm.edu    |
      |   jimj@convex.csd.uwm.edu                                   |
      |   __________________________________________________________|___
       \_/_____________________________________________________________/
Newsgroups: comp.unix.bsd
From: julian@tfs.com (Julian Elischer)
Subject: Re: kernel too large to load
Organization: TRW Financial Systems
Distribution: comp
Date: Fri, 16 Oct 1992 04:38:37 GMT

In article <1992Oct16.032203.9531@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes:
>In article <BOOT.92Oct15130622@donald.osf.org> boot@osf.org writes:
>>What's the simplest fix if I build a kernel which the boot program
>>claims is too large to load?
>
>1)	Strip it.
This may not help, stripping won't make the text+data+bss smaller.

take something out.
>
>2)	Link it to load above 1 Meg and use Julian's boot blocks to load it;
>	you may not be able to use the memory below 1 Meg unless you write
>	more code to add it to the usable pool.

the loader does this just fine, but the kernel explodes.
Bill tells me you need som patches to load above 1MB.
I'll ask him this weekend.

>
>
>					Terry Lambert
>					terry@icarus.weber.edu
>					terry_lambert@novell.com

+----------------------------------+       ______ _  __
|   __--_|\  Julian Elischer       |       \     U \/ / On assignment
|  /       \ julian@tfs.com        +------>x   USA    \ in a very strange
| (   OZ    ) 2118 Milvia st. Berkeley CA. \___   ___ | country !
+- X_.---._/  USA+(510) 704-3137(wk)           \_/   \\            
          v


Newsgroups: comp.unix.bsd
From: hitchens@untadh.enet.dec.com (Francis J. Hitchens)
Subject: Logitech mouse driver.
Reply-To: hitchens@untadh.enet.dec.com (Francis J. Hitchens)
Organization: Digital Equipment Corporation
Date: Thu, 15 Oct 1992 11:31:10 GMT

Hi,

I have tried the two available logitech bus mouse drivers mentioned in
comp.unix.bsd,
but nether work.

I have looked at the PC's tech reference, and find that the mouse is
actually attached 
via the Keyboard Controller 8042/8742.

Is this a busmouse or a keyboard mouse ?

Has anybody got a driver for one ?

regards...
Newsgroups: comp.unix.bsd
From: paoletti@cps.msu.edu (David R. Paoletti)
Subject: 386BSD: continual reboot cycle w/ SCSI drive
Originator: paoletti@pacific.cps.msu.edu
Organization: Dept. of Computer Science, Michigan State University
Date: Thu, 15 Oct 92 02:04:17 GMT

I'm trying to create a disktab entry for a Fujitsu 2266S drive.
It is translated to 1023 cyl, 32 sec/track and 64 tracks/cyl by
my AHA-1542B controller.

I was able to create the following disktab entry, disklabel the
drive, create the root and user filesystems, copy stuff to them.
Doing a 'disklabel -r as0' gives the expected results.

My problem now is that I can't boot off of the hard drive -- it
just goes into a continual reboot cycle without printing anything.
I've seen people complain of this before with IDE drives, but not
SCSI, and so never really paid attention to the postings.

Here's the disktab entry that I'm using (MS-DOS is taking up
cylinders 0-330):

fj2266|Fujitsu 2266S: \
	:ty=winchester:dt=SCSI:se#512:nt#64:ns#32:nc#1023:rm#3600:\
	:pa#65536:oa#677888:ba#8192:fa#1024:ta=4.2BSD: \
	:pb#65536:ob#743424:tb=swap: \
	:pc#2095104:oc#0: \
	:ph#1286144:oh#808960:bh#8192:fh#1024:th=4.2BSD:

Thanks,
  Dave Paoletti :)
From: cs101f87@dcl-nxt33 (cs101 student)
Newsgroups: comp.unix.bsd
Subject: DISKTAB question
Summary: Need info on partitions in DISKTAB file
Keywords: disktab partitions
Date: 16 Oct 92 05:08:36 GMT
Article-I.D.: news.Bw77MD.K3
Organization: University of Illinois at Urbana

This may be a rather stupid question, but you can pipe all your flames to
/dev/null anyway...

	I have recently been looking at doing "real" partitioning on my hard 
	drive (386BSD 0.1 already installed and running...).

	I have looked at the DISKTAB entry and am still confused on how I 
	would create my own.  The cause of this confusion is the partition
	names... This is what I have figured out:

		Partition		Purpose

		   a			Root filesystem
		   b			Swap partition
		   c			Whole space allocated to 386BSD

	My question concerns the "d" and "h" partitions... 
	In some disktab entries, the d partition is the same as the "c" 
	partition, namely all of 386BSD's space... On others, however,
	it is its own partition with 4.2BSD filesystem installed... Why
	is this so, and how do I know which one I want??

	If I wanted to leave the original 386BSD single root filesystem (as
	installed by the TinyBSD INSTALL program), and increase my swap space,
	would I be saved any trouble of dealing with "d" and "h" partitions??

	^^^ By the way, I realize that I will have to NEWFS the drive anyway,
	since I will be taking the extra swap space out of the original root
	filesystem...

					Thanks ahead,
						Rafal

Rafal Boni							r-boni@uiuc.edu
rkb55989@uxa.cso.uiuc.edu         		   cs101f87@sumter.cso.uiuc.edu
Newsgroups: comp.unix.bsd
From: sef@kithrup.COM (Sean Eric Fagan)
Subject: Problems with getting 386BSD 0.1 to run
Organization: Kithrup Enterprises, Ltd.
Date: Mon, 12 Oct 1992 06:19:45 GMT

My apartmentmate just bought a 486 machine, and we've been trying to get
386bsd 0.1 to boot.  In the meantime, I also tried to get it running on my
machine, and it failed there, also.

The machines and symptoms are:

his) 486DX, 33MHz, 8MBytes RAM, 64KBytes external cache, Micronics
motherboard with VL-bus IDE hard- and floppy-controllers.  Standard SVGA
card, and a WD80013 ethernet card (which is irrelevent, as the same
behaviour results whether or not we have the card in).  Phoenix BIOS.  The
behaviour is that the machine boots, and tries to read the floppy; the light
comes on and stays on, but, after a while, the disk stops seeking, and we
can open the drive door and everything.  It is not a happy camper.

mine) 386DX, 25MHz, 8MBytes RAM, I forget about the cache, noname clone
motherboard.  RLL hard-disk controller, Adaptec 1542B with floppy disabled,
noname "i/o card" (with serial and floppy, maybe the parallel port too).
(It's been a long timem since I really looked at what was inside this
machine, obviously :).)  WD80013 Elite16 Combo card.  AMI BIOS.  Behaviour
is that the machine, instead of hanging, jumps into the AMI extended setup
and configuration code, although it is hung, and ignores keyboard input.

We're much more interested in getting his machine to run 386bsd, since it's
"the new toy."

Any help would be greatly appreciated.  Thanks...

-- 
Sean Eric Fagan  | "You can't get lost in one room, no matter how
sef@kithrup.COM  |  little effort you make to learn your way around."
-----------------+    -- William E Davidsen (william@crd.GE.COM)
Any opinions expressed are my own, and generally unpopular with others.
Newsgroups: comp.unix.bsd
From: gottloeb@eel.dsd.trw.com (Jeffrey R. Gottloeb)
Subject: Re: fax software for 386bsd?
Organization: TRW, INC.
Date: Wed, 14 Oct 1992 18:42:10 GMT

In article <1992Oct5.105838.13230@Informatik.TU-Muenchen.DE> gebhart@Informatik.TU-Muenchen.DE (Ralf Gebhart) writes:
>In article <1992Oct5.103838.13036@Informatik.TU-Muenchen.DE> gebhart@Informatik.TU-Muenchen.DE (Ralf Gebhart) writes:
>>>
>>Hi
>>I'm currently working on porting GNU-netfax to 386BSD.
>>I have already compilid it (need GNU-make for this).
>>With the exception of one ioctl, I only had to change some #defines.
>>I don't know yet if that ioctl is really necessary, because I don't know
>>what it does. Ultrix and SUNos have it, but 386BSD not. Unfortunately
>>I couldn't get any docs/info about that ioctl yet.
>>Another problem is, I am currently very busy with other things,
>>so it will take at least another month, til I have finished that beast.
>>BTW: I'm working with a ZyXEL 1496E.
>>
>
>I forgot some things to mention.
>I used Version 3.2.1 of GNU-fax
>
>and is there anyone who can tell me what 
>
>ioctl(fd, TCXONC, TCOOFF);  exactly does ?
>
>I know it has something to do with XON/XOFF, but is so special to it,
>can it be replaced by one of the usual XON/XOFF-related ioctl ?
>
>
>      Snake
>


I've got most of done and am testing it right now.  I am able to send faxes
out via the spooler but I am having difficulty receiving faxes.  The problem
seems to be a time-out problem after receiving the CONNECT message.

One thing I found out about the ZyXEL's is that they are not returning
Class 2 values that are strings (eg. FCSI, FTSI) properly.  The values
should have double-quotes around them (eg. +FCSI:"18005551212") but do not
(at least with the V5.02 ROMSs).

I also needed to increase the timeout value TIMEOUT_ANSWER in c2proto.h from
15 seconds to 60 seconds to allow for long carrier detect times (all those
protocols :-).

Something that made by efforts easier was a patchfile that was posted here
earlier.  If you don't have it, email me.

I don't remember at the moment what I changed that ioctl to but I can check
tonight.

Jeff Gottloeb
gottloeb@gumby.dsd.trw.com
Newsgroups: comp.unix.bsd
From: stripes@pix.com (Josh Osborne)
Subject: Re: 16-colour X server?
Organization: Pix Technologies -- The company with no adult supervision
Date: Tue, 13 Oct 1992 11:38:37 GMT

In article <1992Oct13.015735.7298@ntuix.ntu.ac.sg> eoahmad@ntuix.ntu.ac.sg (Othman Ahmad) writes:
[...]
>	Then it will be 8 times faster but you only have 2 colors, black and
>white. I used to think that 8-bit is too much but when I run the XFree86, it
>is so fast that there is no need to speed it up by 2 time. I'm only using
>a non cached 386 25 Mhz without 387.

Well mabie you have a faster video card, but I can tell the diffrence
between a 386/33 w/64k cache and 387 and a ET4000 running XFree86, and
a SparcIPX.  Just run xtank a 3rd machine with the display attached to
the PC or IPX.  Now for the money the PC is a great deal, but I could
use a faster X server...

>	In fact 16-bit is the ultimate. There is no need to go any futher.
>The 24-bit and 32-bit DACs are wasteful because they do not take into account
>human visual perception.

In my PSYC100 class we were told that (most) people could distingush
between a picture with 16M colors and one with fewer colors, but not one
with more then 16M colors and one with 16M colors (it has been 5 years
for me, so I do not remember the details).  16M is more then 2**16, in
fact it is *very* close to 2**24 (2**23 is too small).  If the study
is correct 24bit DACs are a waste for most people (but not all).

Of corse there is monitor quality.  It may be my mind playing tricks on
my, but on a no-name monitor I couldn't tell teh diffrence between
32K colors and 64K colors, but on a NEC MultiSync 3D (same card, same
TIFF, same PC) I could.

>	At least that is what TV textbooks say. Is there any recent work proving
>otherwise?

Well mabie that only applys to TV tubes then :-)
-- 
           stripes@pix.com              "Security for Unix is like
      Josh_Osborne@Real_World,The          Multitasking for MS-DOS"
      "The dyslexic porgramer"                  - Kevin Lockwood
We all agree on the necessity of compromise.  We just can't agree on
when it's necessary to compromise.       - Larry Wall
Newsgroups: comp.unix.bsd
From: ac@cs.brown.edu (Arthur!! Chai)
Subject: Floating point ops don't work
Organization: Brown University Department of Computer Science
Date: Fri, 16 Oct 1992 14:43:28 GMT

I have the patched 1.0.3 kernel and XFree86 mono working. However, I just
realized that floating point ops no longer work while trying to get
ghostscript to work.  Hmmm ... is it because the kernel supplied with
the X distribution is for a machine with a 387 installed ? If so, does 
anyone have one without that ? Or am I just confused ? I have a plain 386SX-25
without a 387 installed.  I would like to be able to have both X and floating
point ops ;^) Any pointers would be appreciated.
Arthur!!