HDTenEightyP/NetNews huggingface dataset:
From: scotty@gagetalker.com (Scott Turner)
Subject: Re: Question on Diamond Clock Synthesizer
Organization: L5 Computing
Date: Tue, 13 Oct 1992 02:41:32 GMT

In article <1992Oct11.045446.1020@fcom.cc.utah.edu> terry@cs.weber.edu (A  
Wizard of Earth C) writes:
|> In article <1b7tmgINNi06@agate.berkeley.edu>, curtis@cs.berkeley.edu (Curtis  
Yarvin) writes:
|> |> Er, well, actually two:
|> |> 
|> |> (1) Can Diamond's "programmable" clock synthesizers generate
|> |> _any_ frequency?  Could they thus be used to drive a fixed-scan
|> |> monitor?
|> 
|> Don't know.  I lost interest in Diamond hardware.
I've lost interst in Diamond hardware for another reason:
The STB Evolution VGA card

This card does everything the Diamond cards do, 4/8/15/16/24 bit color,
clock synthesizer (and a BETTER one than Diamond's!!!), on board mouse
hardware eith separate color space in the DAC, and the ability to go into
a linear memory scheme, and as if all that weren't enough, it has the
ability to use all the fancy 4 plane hardware in 8 plane mode!

This puppy vidspeeds identical to a Diamond and has twice the winmarks.

Documentation on the board is available from Cirrus Logic, you need their
CL-GD5422 data sheet. This is a true single chip VGA, the RAMDAC and clock
synth are all on board so with this data sheet you've got complete dox on the
STB card.

I'm busily hacking a driver for it.

Best of all the STB card costs close to 50% less than the Diamond cards.

Bye bye Diamond!

Scotty
From: amurai@tama.spec.co.jp (Atsushi Murai)
Newsgroups: comp.unix.bsd
Subject: Re: cant build kernel
Date: 10 Oct 92 13:52:02 GMT
Distribution: world, fj
Organization: System Planning and Engineering Co,.ltd


In article <andrew.718593697@citr.uq.oz.au> andrew@citr.uq.oz.au (Andrew A Zander) writes:
> I have just installed the patch kit which includes the
> fix concerning the inability to build kernels ( something
> about vers.o ). This fix was duly applied but when i try
> to build a kernel i get an error from the make, it cant find
> vers.o. can anyone help?

 Do a "make newvers" if you talk about 386BSD-0.1 with Terry's patch Beta3.

Good luck!
--
Atsushi Murai                                     FAX:   +81-3-3832-2779
System Planning & Engineering co,.                Phone: +81-3-3833-5341
Newsgroups: comp.unix.bsd
From: adrian@ibmpcug.co.uk (Superuser)
Subject: Re: patched dist.fs or /386bsd available?
Organization: The IBM PC User Group, UK.
Date: Wed, 7 Oct 1992 22:39:28 GMT

>Does anyone have either a complete dist.fs(.Z) or just the /386bsd kernel 
>binary available somewhere which has all of Terry's patchkit installed 
>within it?

It will be in the ftp area of rachel.ibmpcug.co.uk very soon.

Adrian
-- 
--------------------------------------------------------------------------
Adrian Hall					Connect Systems Manager
adrian@ibmpcug.co.uk				The IBM PC User Group
Tel: +44 81 863 1191				Harrow, London, UK
From: wutcd@chemnitz.guug.de (Joerg Wunsch)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD and manual pages
Date: 12 Oct 92 19:06:05 GMT
Distribution: global
Organization: tu-chemnitz

g89s9112@hippo.ru.ac.za (Dirk Sturzebecher) writes:

>Hi all,
>just a short question. how do manual pages work with 386bsd ?

>they are not in the normal format but rather as some form of text
>file...
Actually, there are two distinct formats. The preformatted pages (as
used by the man(1) command) are nroff output, highlighted characters
are ``char-backspace-char'' sequences, understruck are `char-backspace-
underscore''. More(1) can handle this, and a standard printer will
accept it, too. These pages are usually suffixed with ``.0''. The
source form of man pages is in -mandoc format, i.e. running [nt]roff
with ``-mandoc'' option is used to process them. Refer to mdoc.samples(7)
man page for description. The sources end in ``.1'' thru ``.8'', depend-
ing on the section they belong to.

	J"org

--
J"org Wunsch, TCD GmbH Dresden, R"ahnitzgasse 18, D-O-8060 Dresden
                                                              \     ~.~. 
	joerg_wunsch%bonnie@hadrian.hrz.tu-chemnitz.de         \   ~  | ~ 
	voice: +49-351-5965 137                                 \    ===
Newsgroups: comp.unix.bsd
From: jim@stargate.helios.nd.edu (Jim McCusker)
Subject: 386BSD Distribution Question
Organization: OUC, University of Notre Dame
Distribution: comp.unix.bsd
Date: Sat, 10 Oct 1992 03:35:45 GMT

I'm about to get the 386BSD distribution on either 1.2M floppies or 1.44M.
My systems A: drive has a 1.2M drive and the B: is a 1.44M.  

Simply, can I copy the distribution to 1.44M diskettes (and save a few 
diskettes in the process) and then load them onto my HD???

                     -- Jim

Newsgroups: comp.unix.bsd
From: ecoleman@qualcom.qualcomm.com (Eamonn)
Subject: XFree86 and a FATAL error!
Organization: Qualcomm, Inc., San Diego, CA
Date: Thu, 8 Oct 1992 21:02:52 GMT

When I fire up X I get the following displayed on the console:

init FATAL error: vga: Interrupted system call

This message appears anywhere in the first minute after startup 
and then repeats itself ad infinitum. Once it does appear my 
xterm stops functioning - although I can log in from over the net
and all appears to be well with the rest of the system. I'm running
version 1.1 of XFree including the kernel supplied with it.

Can anyone tell me what's going on here?

Thanks, Eamonn.

eamonn@qualcomm.com
-- 
Eamonn Coleman                            Qualcomm Incorporated
eamonn@qualcomm.com                       10555 Sorrento Valley Road
Tel. (619) 597-5280                       San Diego, CA 92121-1617   
Newsgroups: comp.unix.bsd
From: plante@spang.Camosun.BC.CA (Mike Plante)
Subject: Re: XFree86 problems...
Organization: Camosun College, Victoria B.C, Canada
Date: Sat, 10 Oct 1992 00:52:29 GMT

In article <1b4qr2INN7l5@maverick.ksu.ksu.edu> brtmac@maverick.ksu.ksu.edu (Brett McCoy) writes:
>
>>What might cause the following error in the xdm-errors file?
>>
>>     Fatal server error:
>>     Cannot open /dev/vga (errno=6)
>>
>>     error (pid 95): Server for display :0 terminated unexpectedly: 1
>>
>>The /dev/vga is there! Am I missing something obvious? I did your basic
>>binary install from the XFree86 core distribution.
>
>Make sure that your X server is not suid to some uid that can't access the
>/dev/vga file.  I had gotten my X server suid bin and /dev/vga was owned and
>only accessible by me.  I got around this by removing the suid bit on the
>server executable, but I don't use xdm.  You probably need to make your X
>server suid root if you are running XDM, or get rid of the suid bit since
>it is probably being run by root anyway.
>
>++Brett;

I solved it. Turns out that there already existed a /dev/vga so when I
installed XFree86 and used x386config, it simply left it alone. But the
original /dev/vga had a different major and minor value than what the
x386config was going to create. So I deleted the original and ran mknod
again with the new values....all works fine.

Thanks to those who responed.

Mike

plante@spang.camosun.bc.ca
Newsgroups: comp.unix.bsd
From: chmr@fstgds01.tu-graz.ac.at (Christoph Robitschko)
Subject: Re: nfs:  'mountd' hangs, must ^c...
Organization: Technical University of Graz, Austria
Date: Thu, 8 Oct 92 18:04:47 GMT

In article <1992Oct7.231718.22241@Arco.COM> Matt Mannhardt <lasmtm@Arco.COM> writes:
[ complaint about a hanging mountd deleted ]

This is a known problem.
There is a patch for it in the beta patchkit.

>I'm not an NFS guru (Apollo sys Admin, don't use NFS much at all) so I'm
                      ^^^^^^^^^^^^^^^^
>running
>out of idea.  Any help would be appreciated...

My condolences.
More condolences if you used NFS on Apollos (I do.) 8-)


							Christoph
-- 
.signature: Result too large
Newsgroups: comp.unix.bsd
From: jdolter@eecs.umich.edu (James W. Dolter)
Subject: Re: [386BSD] System's not finding/using swap
Organization: University of Michigan EECS Deptartment
	<1992Oct15.162400.24424@fcom.cc.utah.edu>
Date: Thu, 15 Oct 1992 19:04:14 GMT

>>>>> Regarding Re: [386BSD] System's not finding/using swap; terry@cs.weber.edu (A Wizard of Earth C) adds:

   .....

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

That is not true.... I have both of my configured swap partitions in the
middle of my disks.

I suggest checking out your kernel config and swap386bsd.c to make sure
that you have a entry in the swap device table (swdevt)...



--
+--------------------------------------------+--------------------------------+
| James W. Dolter                            | Real-Time Computing Laboratory |
| Internet: jdolter@sawtooth.eecs.umich.edu  | The University of Michigan     |
| UUCP:     umich!umeecs!jdolter             | 1301 Beal Ave                  |
| Office:   2222 EECS                        | Ann Arbor, MI 48109-2122       |
| Voice:    (313) 763-5363                   |                                |
+--------------------------------------------+--------------------------------+
Newsgroups: comp.unix.bsd
From: eoahmad@ntuix.ntu.ac.sg (Othman Ahmad)
Subject: Re: DOS and 386BSD (and NT and OS2)
Organization: Nanyang Technological University - Singapore
X-Newsreader: TIN [version 1.1 PL6]
Date: Thu, 15 Oct 1992 08:19:04 GMT

A Wizard of Earth C (terry@cs.weber.edu) wrote:
: |> 
: |> I am somewhat confused now. Should the DOS primary partition be put first
: |> (avoiding the problem that you can't run past cyl. 1023) or second, to
: |> keep asboot, disklabel, family happy?
: 
: I believe that the confusion here lies with the fact that Othman's procedure
: will not work on a geometry translated drive.
: 

I may be wrong but I recall being told that the translation is not done by
bios, rather by the controller.
	The real geometry of the IDE disk is that of variable number of 
sectors for each cyclinder, to get the maximum number of bytes.

I do not think that there is any OS that can handle varaible sector number so
the disk controller must convert the variable sector number to a linear number.
The input parameters are the number of sectors per head, and number of heads
per cylinder.

Theoretically, we can just choose any geometry on the bios, and it will work.
Provided your bios/software know the geometry that you store your data in.
I did this on a Western Digital 40Mbyte hard disk.

However the IDE controller may allow software to read a recommended geometry,
which may be different from the BIOS setting(in CMOS RAM). DOS still works
because of the above reason.

The problems come because of the mismatch between BIOS and disklabel geometries.

However DOS and 386bsd can still co-exist in this circumstances. Just instruct
the OS boot manager to load the appropriate partitions calculated using the
BIOS informations, converted from the disklabel info.

I have worked with 200Mbyte Conner, 200Mbyte Maxtor, 120 Mbyte Maxtor.

I have another 240mbyte quantum pro IDE, but I believe I can install the DOS
as well, but I must have the OS-BS software. Otherwise, it will surely fail.

--
Othman bin Ahmad, School of EEE,
Nanyang Technological University, Singapore 2263.
Internet Email: eoahmad@ntuix.ntu.ac.sg
Bitnet Email: eoahmad@ntuvax.bitnet
From: terry@cs.weber.edu (A Wizard of Earth C)
Newsgroups: comp.unix.bsd
Subject: Re: Problems with patchkit
Date: 13 Oct 92 16:28:13 GMT
Article-I.D.: fcom.1992Oct13.162813.17853
Organization: Weber State University  (Ogden, UT)

In article <1992Oct13.173506.56549@qut.edu.au> csb960lanaga@qut.edu.au writes:
>Is anyone having trouble the patch kit ? I have insttalled all of the
>patches onto the srcdist files. 
>
>config GENERICISA works fine
>make depend works fine
>make falls over with a signal 11 (Segmentation Violation)
>
>The make stops when you get to the SYSTEM_LD line. I suspect that it has
>got something to do with the added object vers.o. I have compiled the kernel
>before on other machines with out too many problems, so it is one of the 
>patches that is the problem but which one.

I'll assume you mean "make" with no arguments.  You should do a "make newvers"
then a "make" with no arguments.

The reason is that the Beta-1 kit uses the CGD make patches rather than
my own, or modificiations of the CGD patches, like the Alpha kits did.

The reasoning on the Alpha-1 kit was "get it running".  The reasoning on the
Alpha-2 and Alpha-3 kits was "make a new version for each "config".

Chris' reasoning was that with sources, you might get new versions without
a new config because of source changes.  I don't necessarily agree here,
but weight of argument was pro Chris' approach.


					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: hasty@netcom.com (Amancio Hasty Jr)
Subject: Re: [XFree86]XOpenDisplay cannot open display :0
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Date: Thu, 8 Oct 1992 01:25:01 GMT

In article <1992Oct7.150800.1@max.u.washington.edu> anything@max.u.washington.edu writes:
>for some reason I cannot get XFree86 to start. I am using the old
>Beta version (1.0.2a) but still it should work. it starts. the screen
>blanks and then synchronizes but remains blank and the keyboard is
>unresponsive. my equipment is a Diamond Speedstar Plus v5.01 (et4000) and a NEC
>multisync II. here is a dump of /usr/X386/lib/X11/xdm/xdm-errors
>
>X386 Version 1.2E 1.0.2a  / X Window System
>(protocol Version 11, revision 0, vendor release 5000)
>VGA256: et4000 (mem: 1024k numclocks: 16)
>VGA256:   clocks: 25 28 81 69  0 29  0  0 13 15 41  0  0  0  0  0
>error (pid 87): IO Error in XOpenDisplay
>error (pid 85): Display :0 cannot be opened
>X386 Version 1.2E 1.0.2a  / X Window System
>(protocol Version 11, revision 0, vendor release 5000)
>error (pid 89): IO Error in XOpenDisplay
>error (pid 85): Display :0 cannot be opened
>X386 Version 1.2E 1.0.2a  / X Window System
>(protocol Version 11, revision 0, vendor release 5000)
>error (pid 91): IO Error in XOpenDisplay
>error (pid 85): Display :0 cannot be opened
>X386 Version 1.2E 1.0.2a  / X Window System
>(protocol Version 11, revision 0, vendor release 5000)
>error (pid 93): IO Error in XOpenDisplay
>error (pid 85): Display :0 cannot be opened
>error (pid 85): Display :0 is being disabled
>
>
>Don Levinson
>anything@max.u.washington.edu
>alt: levinson@halcyon.com


If you don't have a core dump...
Try the following
X386 >& error_output

The output should tell us what is wrong..

If you can't sort out the output, just send it
to me.

One day soon I will finished my FAQ for XFree86 under 386bsd.


Cheers,
Amancio
Newsgroups: comp.unix.bsd
From: larry@vaxb.acs.unt.edu
Subject: Sep  5 15: 13:11  /386bsd: com1: silo overflow
Organization: University of North Texas
Date: Wed, 7 Oct 1992 20:08:40 GMT

I'm am having trouble getting a dialup line to work on com2.

I altered the entry for com2 in /etc/ttys, but when the modem answers getty
sends the login prompt, and that causes the modem to hangup.

I think the problem has something to do with  the modem settings, but I can't
seem to find the correct combination.




Later....Larry
From: CALT@SLACVM.SLAC.STANFORD.EDU
Newsgroups: comp.unix.bsd
Subject: modem, Delete key, PATH
Date: 12 Oct 92 23:29:44 GMT
Organization: Stanford Linear Accelerator Center

Hello --
I finally have 386bsd and XFree86 1.1 running on my PC.
Thanks for all the people who helped me.
But I seem to have some problems as follows:
1. modem: Can I use com2 to connect an extern modem to
   dial out? How to configure it?
2. Delete key in Xterm sessions: The Delete key in the
   session generates ^H. Thus, I did: stty erase "^H".
   Then the Delete key seems to "erase" the characters.
   However, the erased characters still appear on the
   screen. Is there any way to solve this?
3. PATH: I added /usr/X386/bin to my path in .login.
   But it won't show up for Xterm sessions? Did I miss
   anything?
Thanks in advance for help!
Ching Shih
shih@cithex.caltech.edu
Newsgroups: comp.unix.bsd
From: stripes@pix.com (Josh Osborne)
Subject: Re: 386BSD won't boot with AMI BIOS/Gateway 2000
Keywords: AMI Gateway 2000
Organization: Pix Technologies -- The company with no adult supervision
Date: Thu, 15 Oct 1992 12:34:47 GMT

In article <1992Oct14.225619.26784@ccu.umanitoba.ca> rahardj@ccu.umanitoba.ca (Budi Rahardjo) writes:
>boehme@unvax.union.edu (Eric M. Boehm) writes:
[...]
>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 have seen it running on a Gateway 2000 w/ Phenox BIOS - but I doubt it
has much to do with the BIOS.  One of the first machines I heard that
386BSD worked with was a Gateway.  This said, I also think the Gateway
label is worthless.  They just go out and but a boatload of the cheapest
motherboard/cards/whatnot whenever they need more and slap their name on it.
That means one Gateway 2000 is nothing like another.  It also means that
their tech-support can't be all that helpful since each month sees a new
motherboard...

>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.

Well if you bought it recently, you should be able to return it.  In fact
just letting them know that you will return it if they can't get BSD running
(or help you) may get them moving, or mabie not.
-- 
           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: eoahmad@ntuix.ntu.ac.sg (Othman Ahmad)
Subject: Re: Sound Blaster Driver for 386BSD
Organization: Nanyang Technological University - Singapore
X-Newsreader: TIN [version 1.1 PL6]
Date: Wed, 14 Oct 1992 01:39:23 GMT

A Wizard of Earth C (terry@cs.weber.edu) wrote:
: 
: Yes.  But like the Am33C93A, it doesn't matter about the chip; what matters
: is the DMA and control interface.  In the case of the WD7000-FASST2, for
: instance, this is a register interface to a Z80.  You *never* get to talk
: to the chip directly.  I suspect the same will be true of other cards as
: well.

Maybe it is true for intelligent SCSI cards like Adaptec 1542, but for a cheap
SCSI card like pro-16, it may not be. The SCSI protocol is supported by that
Zilog chip.

: 
: What you will need will be a programming guide for the board which includes
: formatting and issuing SCSI commands; this will probably have to come from
: the manufacturer.
: 
IF it were a dump SCSI card, what we have to do is to identify where the
registers for the Z5380 are, trial and error.

--
Othman bin Ahmad, School of EEE,
Nanyang Technological University, Singapore 2263.
Internet Email: eoahmad@ntuix.ntu.ac.sg
Bitnet Email: eoahmad@ntuvax.bitnet

Newsgroups: comp.unix.bsd
From: nbladt@autelca.ascom.ch (Norbert Bladt)
Subject: Re: Starting XFree861.1
Organization: Ascom Autelca AG, Guemligen, Switzerland
Date: Wed, 14 Oct 1992 12:11:40 GMT

scotty@gagetalker.com (Scott Turner) writes:

>In article <Bvsr9F.CFv@cosy.sbg.ac.at> peter@wiesel.cosy.sbg.ac.at (Peter  
>Burgstaller) writes:
>|> Then I started xinit (also startx) then I got the following 
>|> Message!
>|> 
[ XFree86 starting problem deleted - NB.]

>Ah, know it well, spent _hours_ on this one myself. It's
>probably yer mouse. I've got the patched kernel (beta-1) and
>re-mknod'd my serial ports and I wound up having to use com2
>to get to com1. :) Of course that was _AFTER_ I figured out
>I wasn't supposed to be using tty0! Too many hours on the 
>commercial unixes...
[ some text deleted - NB. ]

After reading this (and the README file which came with the patchkit) I
think I need some help with the setup of the com-ports after applying
all the patches in the patchkit.

The information part for the com-port patch (select and re-numbering the
ports) just contains:
	"You have to re-mknod your com ports"
This text without instructions how to do it, is a very useful hint, but
is not enough for me.
I have 2 com-ports installed on my system but never used one.
However, I will try to compile X11R5, apply the diff's for XFree86-1.1, etc.
and will want to use my mouse on one of those com-ports for X. Now, if I do
have to re-mknod my com-ports how would I do it (I know how it works and which
program to call, though) ?
I saw that there was no new "/dev/MAKEDEV" in the patch. So, unless the
major or minor device-numbers didn't change, I don't need to do new
mknod's, right ?

It all burns down to the simple questions:
	What are the major / minor device numbers for the "new" com-ports ?
or in other words:
	Are the major numbers the same (I guess so) or what are they ?
	Are the minor numbers 0 for com1, 1 for com2, etc. ?

If somebody can tell me (and other new users of XFree86) what do to exactly
AFTER you have applied the patches, I am sure, it will save some troubles.

Thanks in advance,

Norbert.
-- 
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
From: tardieu@artemis.enst.fr (Samuel Tardieu)
Newsgroups: comp.unix.bsd
Subject: French Keyboard
Keywords: bsd,pc,unix,french,keyboard
Date: 7 Oct 92 14:51:28 GMT
Organization: Telecom Paris, France

I have installed BSD386 on a computer with a french keyboard (i.e azerty).
Is it possible to make Unix use a correct keyboard table ?
OK, I can do like if it was a qwerty keyboard, but...

-- 
     Samuel TARDIEU  -  Telecom Paris  -  sam@enst.fr  -  (1) 45-81-71-97
From: anything@max.u.washington.edu
Newsgroups: comp.unix.bsd
Subject: [Xfree86 on 386BSD] xtank ported yet?
Date: 14 Oct 92 17:55:19 GMT
Article-I.D.: max.1992Oct14.105519.1

Has anyone ported Xtank to XFree86/386BSD yet?
Newsgroups: comp.unix.bsd
From: hand@spc9.jpl.nasa.gov (Kolin Hand)
Subject: Re: kermit for 386BSD
Organization: Jet Propulsion Laboratory, Pasadena, CA
Date: Wed, 14 Oct 1992 02:17:24 GMT

In article <92287.113452CALT@SLACVM.SLAC.STANFORD.EDU> <CALT@SLACVM.SLAC.STANFORD.EDU> writes:
>I am looking for Kermit for 386BSD. Any suggestions?
>Thanks!
>
>Ching Shih
>shih@cithex.caltech.edu

The latest version of Kermit, available from watsun.cc.columbia.edu, 183
I believe, ports with very little effort.  Look for cku183.tar.Z on that site.

Kolin

+===========================================================================+
+  "Guilt Trip:  The nuclear weapon of relationships."  -- K. Hand          +
+---------------------------------------------------------------------------+
+  Kolin E. Hand                              hand@spc7.jpl.nasa.gov        +
Newsgroups: comp.unix.bsd
From: deeken@iti.informatik.th-darmstadt.de (Hans-Christoph Deeken)
Subject: Re: Maxtor LXT340S
Date: Thu, 15 Oct 1992 14:32:51 GMT
Organization: TU Darmstadt

In article <1ba7h4INN4du@uwm.edu>, knier@miller.cs.uwm.edu (Robert Knier ) writes:
> 	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.  

Huh? I'm using exactly this type of drive in my 386BSD machine at home.
Didn't have to make a disktab entry, install did everything for me. :-)

I can mail you my disklabel, if it is of any help.


> Thanks,
> 
> Bob Knier
> (knier@miller.cs.uwm.edu)

Ciao,
Hannes
-- 
Hans-Christoph Deeken                                        (Glenlivet on IRC)
Inst. fuer theoret. Informatik		(deeken@iti.informatik.th-darmstadt.de)
TH Darmstadt, Germany          (I don't speak for THD, they don't speak for me)
        "Whisky ist fluessiges Sonnenlicht --- George Bernard Shaw"
Newsgroups: comp.unix.bsd