HDTenEightyP/NetNews huggingface dataset:
From: cwc@ssesco.com (Craig W. Carlson)
Newsgroups: comp.unix.bsd
Subject: [386BSD] Patchkit and slip?
Date: 13 Oct 92 14:32:23 GMT
Organization: SSESCO

I installed the patch kit last night and everything went fine until I tried
to use slip.  The slip configuration seemed to work, and I seemed to be able to
send packets out, but incoming packets appeared to be getting thrown away (at
least it seemed that way by watching the lights on my modem).

I am using the same connection procedure and stty settings that worked before
the patch.  I use kermit to dial into our slip server and initiate the
connection on the remote end and then do the slattach locally with stty setings
"cs8 -istrip crtscts -parenb -parodd -cstopb".  I am running at 38400 through
a FIFO port.

Any ideas?

------------------------------------------------------------------
Craig W. Carlson                                    cwc@ssesco.com
SSESCO                                              (612) 342-0003
511 11th Ave. S. Suite 268
Minneapolis, MN 55415
Newsgroups: comp.unix.bsd
From: sastdr@torpid.unx.sas.com (Thomas David Rivers)
Subject: Re: BSDI, portables, and overhead projectors
Date: Tue, 13 Oct 1992 20:14:59 GMT
Organization: SAS Institute Inc.


  Well, here's a possible simple solution.  Get two portables, have one
 run BSDI (or 386BSD) and the other running a terminal emulator under
 DOS.  Connect the "magic overhead thingy" to the DOS box, and then
 connect a small serial line (null modem, etc..) to the BSDI/386BSD box.

  There ya go...

	- Dave R. -
	(rivers@ponds.uucp)
 
-- 
UPDATE ALL INFORMATION AND POD INTO COSMOS - Federal Express
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: Configuring X386 & etc
Keywords: X386
Reply-To: terry@icarus.weber.edu
Organization: University of Utah Computer Center
Date: Fri, 9 Oct 92 06:52:11 GMT

In article <1992Oct9.051145.16385@u.washington.edu>, ganter@carson.u.washington.edu (Mark Ganter) writes:
|> Hi gang,  I have X386 up and running! I don't have video problems THANKS
|> to many posts, the FAQ for X, xclk, etc.  However, I'm having mouse problems.
|> In the Xconfig file theres a line:
|> (from my human memory)
|> Logitech  /dev/tty00

You can change this from 'Logitech "/dev/tty00"' to 'Logitech "/dev/com1"'.

|> Also, what are other valid names to replace "Logitech"?
|> And how would I know?  Am I missing docs somewhere?  I checked FAQ-X.  Did
|> I miss something?

After running the install script, you can type 'man X386' to, among other
things, get a list of dupported misce, video chip sets, etc.

|> Yet, I see references to higher
|> versions.  Has there been an update within the last week?

Yep.  Updated 03 Oct 92 to the next version.

					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
-------------------------------------------------------------------------------
From: terry@cs.weber.edu (A Wizard of Earth C)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] System's not finding/using swap
Date: 15 Oct 92 16:24:00 GMT
Article-I.D.: fcom.1992Oct15.162400.24424
Organization: Weber State University  (Ogden, UT)

In article <1992Oct15.045324.14859@news2.cis.umn.edu> rodeen@buddha.ncc.umn.edu (Rick Odeen) writes:
>I'm currently bringing up a system using Terry's "HP Vectra/starlan" kernel
>and am experiencing a problem with the system not finding my swap space.
>During the inital boot sequence I get the following message:
>
>Oct 15 00:29:38 manray /386bsd: warning: no swap space present (yet)
[ ... ]
>8 partitions:
>#        size   offset    fstype   [fsize bsize   cpg]
>  a:    21000        0    4.2BSD      512  4096    16 	# (Cyl.    0 - 39)
>  b:    21000    21000      swap                    	# (Cyl.   40 - 79)
^^^^^
>  c:   641550        0    unused        0     0       	# (Cyl.    0 - 1221)
>  d:   641550        0    unused        0     0       	# (Cyl.    0 - 1221)
>  h:   596925    42000    4.2BSD      512  4096    16 	# (Cyl.   80 - 1216)

The swap has to go at the end of the disk.


					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
-------------------------------------------------------------------------------
From: sandi@uctcs.cs.uct.ac.za (Sandi Donno)
Newsgroups: comp.unix.bsd
Subject: Re: Help logitech busmouse. missing device.h
Date: 13 Oct 92 15:44:08 GMT
Article-I.D.: uctcs.sandi.718991048
Organization: Computer Science Department, University of Cape Town

In <1992Oct7.132428.15172@rdg.dec.com> hitchens@untadh.enet.dec.com (Francis J. Hitchens) writes:

>Hi,

>I have found the busmouse.v3 kit patch and  tried to add it to my kernel.

>The header file device.h seems to be missing. Can any body point me to
>it please.

This busmouse driver is for BSD/386, and will not compile under 386bsd 
without some conversion being done. I used archie and found the following:

Host athene.uni-paderborn.de

    Location: /uninstalled/386BSD/386bsd-0.1/unofficial
	       FILE -rw-r--r--      10702  Aug 27 15:53  386bsd-busmouse.tar.Z

I have a Microsoft bus mouse, and this driver worked for me. It supports the
Logitech bus mouse too.
--
Sandi Donno
Computer Science
University of Cape Town
South Africa
Newsgroups: comp.unix.bsd
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Newsgroups: comp.unix.bsd
Subject: Re: question about mwrite
Date: 16 Oct 92 07:29:52 GMT
Organization: Uni-Duisburg FB9 Datenverarbeitung
Reply-To: veit@du9ds3.uni-duisburg.de
NNTP-Posting-Host: du9ds3.uni-duisburg.de

In <92289.141235RLM@MAINE.MAINE.EDU> RLM@MAINE.MAINE.EDU (Robert L. Metcalf NV1A) writes:

>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

Any of these work. It is more interesting which error message you get.
If it is something like 'device not found' or 'cannot open' (of course
test.gif must be there), it is because you don't have the floppy device
the mtools want to see. Run from the /dev directory the command
sh MAKEDEV fd0. 
Another possibility is that your floppy is not properly formatted. There
ARE problems with 720K 3,5" and 360K/720K/1.44M 5,25 disks (i.e. remaining:
preferably use 1.2M 5,25 and 1.44M 3,5" disks).

Holger

-- 
|  |   / 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,comp.windows.x
From: bri@pegasus.mit.edu (Brian D. Carlstrom)
Subject: Sound Blaster Driver Question
Organization: mit
Date: Thu, 15 Oct 1992 06:51:57 GMT


just got the standard distribution and XFree going without anyproblems.
Many thanks to all those working on all this great free software...

i was quite happy(and surprised) to see a sb driver for 386bsd.
now, just to clarify. is the driver just for the sb PRO? or is
it for any. i have a good ole 8 bit sb. the post said
sound blaster driver, but seemed to be only for the PRO

-bri

Xref: sparky comp.unix.bsd:7416 comp.os.linux:13389
From: pete@q106fm.uucp (pete cervasio)
Newsgroups: comp.unix.bsd,comp.os.linux
Subject: Re: Which Tape to use with 386BSD and/or Linux ?
Date: Wed, 14 Oct 92 00:51:06 CST
Organization: WKBQ-FM Engineering Department

root@fns.gold.sub.org (Peter Bechtold) writes:

> I'm planning to install 386BSD and/or Linux on my 386 system.
> 
> All I need is a tape drive for that.
> 
> Since I have 2 IDE drives, I would like to by either a
> QIC-02 drive or a 1542 SCSI controller plus SCSI tape drive.
> 
> What would you recommend ?
> 
> I need a tape drive with 150 meg's capacity,
> 250 or 525 wouldn't hurt though :-)

Well, I use Linux and have installed the beta tape driver patches so I
could use my Wangtek 5150EN drive (QIC36?) and it's working very well.
I've got my entire Linux filesystem backed up to tape.  With DC6250 tapes,
it'll do 250 megs just fine!

I am not familiar with the tape support under 386BSD, since I don't have
the space to run both right now.  :-(

Pete C.

+----------------------------------------------------------------------+
| Pete Cervasio                | pete%q106fm.uucp@wupost.wustl.edu     |
| I fish, therefore I am.      | pete.cervasio@f1.n2250.z1.fidonet.org |
+----------------------------------------------------------------------+
|  If you think of C as a preprocessor for your assembler, it makes    |
|                   just as little sense as before.   (me)             |
+----------------------------------------------------------------------+
From: knier@miller.cs.uwm.edu (Robert Knier )
Newsgroups: comp.unix.bsd
Subject: Maxtor LXT340S
Date: 11 Oct 1992 21:49:24 GMT
Organization: University of Wisconsin, Milwaukee
NNTP-Posting-Host: 129.89.9.13

	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.  


Thanks,

Bob Knier
(knier@miller.cs.uwm.edu)
Newsgroups: comp.unix.bsd
From: krueger@engin.umich.edu (Erick Krueger)
Subject: Re: Problems with getting 386BSD 0.1 to run
Date: Mon, 12 Oct 92 04:13:47 EDT
Organization: University of Michigan Engineering, Ann Arbor

In article <1992Oct12.061945.530@kithrup.COM> sef@kithrup.COM (Sean Eric Fagan) writes:
>My apartmentmate just bought a 486 machine, and we've been trying to get
>386bsd 0.1 to boot.

I have seen similar problems on my 386DX/20.  It will boot up, show system
diags, and then the floppies are checked, then the HD, and back to the   
floppy like normal.  Except now the floppy light stays on, and the HD is
found and its light stays on as well.  All the while, no system is loaded.
i.e.  There is nothing printed to the screen from 386bsd.
I have seen this occur 2-3 times out of 5 sometimes.  Any ideas here as
well?
 
Inside the system is a 386DX/20, 387, Quantum 105 IDE HD, with 2 floppies.
In addition, I have the sound blaster pro, and a Sony interface CD-ROM. 
 
Thanks for any help.
 
Newsgroups: comp.unix.bsd
From: russo@amazon.chem.columbia.edu (Thomas Russo)
Subject: [386BSD] ACK! Sun devotee buying a PC, need help!  Please!
Organization: Center for Biomolecular Simulation, Department of Chemistry,
	Columbia University
Date: Wed, 14 Oct 1992 18:55:53 GMT

Ok, I've never really bought a PC box before, I've read the
PC-Clone buyers guide, I've called vendors, I've read this group and
I'm this close (he holds his fingers about 1mm apart) to actually
plunking down a pile of money on a 386 box from EPS Technologies.

I'm nervous, coz I want to run 386BSD and X and I'm terrified that I'm
might be buying stuff that won't work.  I've gotten a quote on a
machine with a 386, 387, 8Mb of 70ns,0wait state RAM, 128K ram cache,
AMI 386 BIOS (release date April 1991), diskette drives, 340Mb IDE
drive, a Cardinal 800 SVGA card (with windows accelerator), monitor,
serial ports (16550) and mouse.

So here's the questions:

1) Am I in trouble with that Cardinal 800 SVGA card, which the quote
says is:
    "Cardinal 800 VGA card, 25 bit, 16.7 Million color SVGA w/1Mb
installed 1024x768"

Monitor is "14", noninterlaced multisync 1024x768 RES, .28mm dot
pitch"

I know that the list of XFree86's "supported" ET4000 cards includes a
Cardinal 700 and a Cardinal ET4000.  Anybody know anything about a
Cardinal 800?  I specifically asked them for an ET4000 based card, so
that's what this is.  Anything to lose sleep over here?  Is the
presence of windows accelerators (which I didn't ask for, but this was
the only card with an ET4000 set they could give me, all the others
were Western Digital) going to be a problem?

2)  I just read an article in c.u.bsd that claimed there were problems
with the AMI 386 BIOS.  ACK!  Whaddamigonnadue?  Should I go to
another vendor or should I not worry?

3) Anybody else out there bought anything from E.P.S. Technologies?
They seem pretty good, and they claim to have lots of Unix customers.
The price seems pretty good based on the half-dozen or so quotes I've
gotten so far.  They do have all the warranty stuff I've been told to
look out for (60 money back, 1year onsite service from a big service
company, etc.)

I've already been cautioned about gcc-2 being flaky with its 387
support and the fact that my 8Mb will be on 1Mb simms which will need
to be removed to upgrade further.  I'm going to have to live with that
as I can't afford the 16Mb configuration at this time.  My main
concerns right now are the BIOS and the VGA card.  Can anybody give me
warnings or advice or reassurance?

--
Thomas Russo			russo@nile.chem.columbia.edu
Department of Chemistry and Center for Biomolecular Simulation
Columbia University
------contact via email for pgp public key
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Newsgroups: comp.unix.bsd
Subject: Re: [386bsd]Where is outb defined?
Date: 8 Oct 92 09:09:16 GMT
Organization: Uni-Duisburg FB9 Datenverarbeitung
Reply-To: veit@du9ds3.uni-duisburg.de
NNTP-Posting-Host: du9ds3.uni-duisburg.de

In <colin.718505860@marsh> colin@cs.curtin.edu.au (Colin Manning) writes:

>Hi,
>	I was looking through wt.c, and fd.c, and came across outb() and 
>out_fdc().  I can't find where they are defined.  Could someone please point me
>in the right direction?

>Thanks

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

>"Knowledge is not knowing all the answers, but knowing where to find them."
>                                                                  -anon.

out_fdc should be in fd.c, outb is in locore.s (there are also macros in
/usr/include/machine/pio.h).

Holger

-- 
|  |   / 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: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: How to compile X386 applications ?
Organization: Weber State University  (Ogden, UT)
Date: Thu, 8 Oct 92 20:55:37 GMT

In article <FZQ793P@mailgzrz.tu-berlin.de> witke@cs.tu-berlin.de (Marius Witke) writes:
>
>Hi,
>
>I tried to compile some small X examples but had no success...
>The linker always complains: 'undefined symbol ... referenced from text
>segment' - and that for all X functions in the program.
>
>I set the LD_LIBRARY_PATH and LD_RUN_PATH to /usr/X386/lib and 
>compiled with options -L/usr/X386/lib and -lX11
>
>What am I doing wrong ???

Use -L to the linker to specify /usr/X386/lib, and -lX, etc. to pick
libraries from the directory.

"LD_LIBRARY_PATH" and "LD_RUN_PATH" are for shared libraries on Sun
systems, and are used for linking shared and runtime loading of libraries,
respectively.  Neither is currently applicable to 386BSD.


					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: carlj@hpcvmcdj.cv.hp.com (Carl Johnson)
Subject: Re: 386BSD new user questions
Organization: Hewlett-Packard Company, Corvallis, Oregon USA
Date: Wed, 7 Oct 1992 15:41:13 GMT

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.

I haven't heard any comments from anybody as to where the screen timeout
and size options on the floppy boot come from.  Any suggestions on how
to set this up on a standard system would be appreciated.
-- 

Carl Johnson              carlj@cv.hp.com
Newsgroups: comp.unix.bsd
From: eoahmad@ntuix.ntu.ac.sg (Othman Ahmad)
Subject: Re: How to use fixit to get DOS and 386BSD on same drive?
Organization: Nanyang Technological University - Singapore
X-Newsreader: TIN [version 1.1 PL6]
Date: Wed, 14 Oct 1992 02:01:36 GMT

Mike Whisenhunt zmw@selu.edu (zmw@altair.selu.edu) wrote:
: 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

I recommend strongly that you use only 32Mbyte for your DOS partition because
mtools cannot work with more than that.

: 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

You have to remove install first using ndd or fdisk on dos 5 with a special
option that I forgot, /mdr(?)


: 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!

type disklabel, and a menu will come out.
It will be better if your existing partition structure be told so that some
analysis can be done.


Newsgroups: comp.unix.bsd
From: rich@Rice.edu (Richard Murphey)
Subject: Re: Xfree86.  Too slow!!
Reply-To: Rich@rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University
	<BvvDAt.ItC@flatlin.ka.sub.org>
	<1992Oct10.022626.16150@news.iastate.edu>
Date: Sat, 10 Oct 1992 06:56:21 GMT

In article <1992Oct10.022626.16150@news.iastate.edu> song@iastate.edu (Chang-Hyeon Song) writes:
   Hello, netter.
   I have just installed XFree86 I got from agate on my 386BSD.
   Then I have noticed that when I open two or more xterm, it is too slow.
   It was swapping all the time.

   Is this the way it is, or am i missing something here?
   I have 8Meg RAM with 169Meg HD for my BSD.
   And running 1024x768 with Tseng card with SONY 1304.
   Thanks in advance.

I get resident set sizes of 1Mb for X386, 800K for xterm and 600K for
twm.  I wouldn't expect that to overload an 8mb system.  Check the
resident set sizes with 'ps axl' to see what's hogging all of your
memory. Rich
Xref: sparky comp.unix.bsd:7282 comp.windows.x:17756
From: dwex@cbnewsj.cb.att.com (david.e.wexelblat)
Newsgroups: comp.unix.bsd,comp.windows.x
Subject: Re: List of XFree86 Video Boards
Date: 12 Oct 92 15:55:26 GMT
Organization: AT&T

In article <1bbu2aINNvp@usenet.INS.CWRU.Edu> at626@cleveland.Freenet.Edu (Dave Strout) writes:
> 
> All--
> 
> I was shopping for a video board to run XFree86 on, but didn't have a list
> of what boards worked w/ it (I hesitate to say "supported").  Anyway, I
> made a list out of modeDB.txt and an emacs macro.  Here it is, hope it's
> useful. 
> 
> dave.

	[ list deleted ]

> An 'i' at the end (e.g 1024x768i means "interlaced").
> 

Interlaced or not is largely irrelevent.  That's only there because that's
what the contributor of the entry was using.  The size of the virtual i
display area supported by a given board is simply 

	(VirtualX * VirtualY) <= Size of Memory in bytes.

For a 1M board, that is usually 1024x1024 or 1152x900.  A 512K board can
support ~800x650.  The size of the PHYSICAL display area depends on the
capabilities of the monitor, and the dot-clocks available from the board.
If the physical screen is smaller than the virtual screen, then the
displayed area will pan around the virtual area.

> I take no responsibility for the completeness of this, no endorsement or
> lack of endorsement is intended by inclusion or omission, I don't speak for
> the authors of xFree86 or any derivative works, no ozone-depleting CFCs
> were used in the preparation of this, your mileage may vary, etc.
> -- 
> Dave Strout          <at626@cleveland.freenet.edu>
> "Thompson's Rule for First Time Telescope Makers:
> It is faster to make a four-inch mirror then a six-inch
> mirror than to make a six-inch mirror."

Be very careful buying a Diamond board.  Recent Diamond ET4000-based
boards (as well as their other boards, but we don't support those chipsets
anyhow :->) use a new mechanism for selecting dot-clocks.  Diamond
prefers to keep the relevent programming information proprietary, so 
XFree86 does not work with these boards (the SpeedStar 24 is an example
(not to be confused with the 24X, which uses a different chipset entirely).
There have been reports of a SpeedStar Plus board with this problem, but 
that may simply have been confused with the 24).  If you are purchasing
new hardware, make sure that it works with XFree86 before you buy it.
The Orchid ProDesigner IIs is an ET4000-based board that is quite fast
and works well.

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
David Wexelblat             | dwex@mtgzfs3.att.com  | Somebody get me a
AT&T Bell Laboratories      | ...!att!mtgzfs3!dwex  |   cheeseburger!
200 Laurel Ave - 4B-421     |                       |      
Middletown, NJ  07748       | (908) 957-5871        | --Steve Miller Band