HDTenEightyP/NetNews huggingface dataset:
From: alm@netcom.com (Andrew Moore)
Subject: Disklabeling (was Re: Another Adaptec Question)
Date: Mon, 17 Aug 92 22:29:21 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Distribution: world,fj,spec

In article <1992Aug17.173807.2309@Informatik.TU-Muenchen.DE> rommel@Informatik.TU-Muenchen.DE (Kai-Uwe Rommel) writes:
>In article <15776@star.cs.vu.nl> kjb@cs.vu.nl (Kees J. Bot) writes:
>>rommel@Informatik.TU-Muenchen.DE (Kai-Uwe Rommel) writes:
>>>
>>>In article <7@tama.spec.co.jp> amurai@tama.spec.co.jp (Atsushi Murai) writes:
>>>>ariticle is not ..but) and Fujitsu M2266SA 1.2 GB Disks. Functionality
>>>>is good but it looks like loosing a space about 200MB (above 1Gbyte).
>>>>And some guy let me know about this is a known problem of 1542B and
>>>>Adaptec will be fixed by new board - 1542C. (Oh well.....)
>>>>[...]
>>It has nothing to do with heads, sectors or cylinders.  The group 0 SCSI
>>read/write commands allow only for a 21 bit block address limiting one
>>to 2 megablocks, which is 1GB at the usual 512 bytes per block.
>
>We don't talk about smart OSes like 386BSD :-) but the original poster
>asked why he doesn't see all the space under DOS/Novell. There it has to
>do quite a lot with heads/tracks/sectors ...
>
>>The group 1 SCSI read/write commands offer a 32 bit block address
>>however, but not all O.S.'s are smart enough to use those commands.
>>
>>>Adaptec has now a new mapping scheme with 256 heads and 64 sectors per
>>>track, [etc...]
>>
>>At least the 64 sectors per track number is wrong, you can't have more
>>than 63 sectors on a track.  I don't like the 256 heads per track
>>either, I know of one (1.5GB) disk with an AT interface that uses the
>>top 2 head bits for two more cylinder bits.  This limits the number of
>>heads per track to 64, but allows for 4096 cylinders.  I don't know if
>>this is a normal way of addressing bigger disks under DOS.  Anyone?
>
>Sorry, for those off-by-one errors, here is the original text from the
>Adaptec README file:
>
>--quote--
>To eliminate the 1 Gigabyte limit, Adaptec's new extended
>translation feature uses 255 heads and 63 sectors,
>extending the disk drive capacity limit under
>DOS to 8 Gigabytes.
>--end-quote--


To return to 386BSD and disklabeling a SCSI drive: 
am I correct in assuming that the specification of # of cylinders,
sectors per cylinder, etc does not matter at all, so long as the total
number of blocks is correct?
Newsgroups: comp.unix.bsd
From: dlee@opencon.com (Daniel Lee)
Subject: HELP!!! - Installation Problem.
Organization: OpenCon Systems, Inc.
Date: Wed, 19 Aug 1992 15:34:15 GMT

Hi all.

I have been trying to install 386BSD 0.1 in my Mylex EISA machine.
It seems that the install program sets up the filesystem correctly
but it does not finish installing.  It just hangs up on me.  When
I invoke install, it formats the HD and then writes some files
to HD.  But then, after about a minute of activity, just hangs up.
If I type CTRL-C, it displays the initial welcome message.

Did anyone here had same problem?  My machine config is :

	486 EISA machine - Mylex
	32 M RAM
	1.44 M FDD - A Drive
	1.2 M FDD  - B Drive
	1.0 Gig SCSI HD
	Adaptec 1542 Controller
	WD Elite Ethernet Card
	Trident SVGA (8900) card

I remove all the other cards - Tape Drive, Multi-I/O card ...

Any ideas?

Dan.
----
dlee@opencon.com
Newsgroups: comp.unix.bsd
From: benjie@quack.sac.ca.us (Andriod)
Subject: BSD on floppy?
Organization: The Duck Pond public unix: +1 408 249 9630, log in as 'guest'.
Date: Sat, 15 Aug 1992 18:48:28 GMT

Does anyone out there in PaloAlto/Sunnyvale area have BSD
system(hopefully, utils (include compiler)) for IBMPC's regular
harddrive on floppies so that I could copy them instead of
downloading?
Thanx
Ben

-- 
     BBB		Benjie Chen
    BCCCB 		benjie@quack.sac.ca.us
    BCCCB		No Axiomatic System Could Produce All Number-
     BBB		Theoretical Truths, Unless It Is Inconsistent.
From: hpeyerl@novatel.cuc.ab.ca (Herb Peyerl)
Newsgroups: comp.unix.bsd
Subject: Re: X386 far too busy?
Date: 20 Aug 92 14:04:44 GMT
Organization: "NovAtel Communications Ltd."

Bakul Shah (bvs@BitBlocks.com) wrote:
: hpeyerl@novatel.cuc.ab.ca (Herb Peyerl) writes:
: >basically no activity all night.  This morning I did a "ps -agx"
: >and noticed that X386 had racked up 1145:23.29 CPU (minutes?)... 
:
: I suspect this is due to a bug in the com.c driver as I used to
: get the same symptom when I connected a serial mouse to com2.

Yes, I suppose I should mention that I had a few responses to my post
suggesting I install CGD's com.c which I did and it managed to solve
the problem quite nicely... Even cylonled works in X now (X was never
idle previously so _idle was never called, consequently the LED's just
stayed still...)

Anyways, thanx for everyone's help... I suppose something like this should
go in the FAQ...

--
"I was early to finish | hpeyerl@novatel.cuc.ab.ca <Reply-To>   | I brew |
I was late to start, I | peyerlh@cuug.ab.ca                     | there- | 
might be an adult, but | #define JANITOR "Network Administrator"| fore I | 
I'm a minor at heart." |    JANITOR, NovAtel Communications Ltd.|   AM.  |
-- 
"I was early to finish | hpeyerl@novatel.cuc.ab.ca <Reply-To>   | I brew |
I was late to start, I | peyerlh@cuug.ab.ca                     | there- | 
might be an adult, but | #define JANITOR "Network Administrator"| fore I | 
I'm a minor at heart." |    JANITOR, NovAtel Communications Ltd.|   AM.  |
Newsgroups: comp.unix.bsd
From: andrew@zone4.ocunix.on.ca (Andrew Low)
Newsgroups: comp.unix.bsd
Distribution: world
Subject: Re: IDE HARD WRITE ERRORS PLEASE HELP ME
Keywords: IDE ERRORS
Organization: Zone4
Date: Fri, 21 Aug 92 01:17:26 GMT

In article <colin.714197827@marsh> 
colin@marsh.cs.curtin.edu.au (Colin Manning) writes:
>wd0: MAXTOR 7040 AT (40MB IDE)
>wd1: MAXTOR 7040 AT (40MB IDE)

>1)  wd1 has three areas that get hard write errors.  What do I do?

You're IDE drives are 'pretending' to be a different geometry than
they really are.  You'll have to dig up (ie: call someone who will
be able to get you the correct information) the native geometry of
your drives.  It is best to also install the drive as a user defined
type in the CMOS setup (type 47 or 48).  My IDE drives worked under
dos as 5heads 977cyl, they really were 4heads 782cyl.

Can't help with (2), I'm still confused about that.  I reserved 5cyl
just in case - seems like it works.

These should both be FAQ's by now..
+/+\+/+\+/+chew carefully/+\+/+\+/+\+/+\+/+\+/+\+/+\+/+\+/+\+/+\+/+\+/+\+/+\+/+
Roo [andrew@zone4.ocunix.on.ca] m a c h i n e l o v e h a t e f e a r v o i d .
               "dreams are all that separate us from the machines"
Newsgroups: comp.unix.bsd
From: volker@sfb256.iam.uni-bonn.de ( Volker A. Brandt )
Subject: Re: 680x0 version of 386BSD?? [Was: Re: Mac version of 386BSD??]
Organization: Applied Math, University of Bonn, Germany
Date: Thu, 20 Aug 1992 11:52:13 GMT

In article <1992Aug19.134736.6219@news.iastate.edu> niko@iastate.edu (Nikolaus E Schuessler) writes:
>[...] the first few steps would have to be platform
>specific anyway... floppy drivers, video drivers and a minimum kernel...

That's true.  I feel reasonably confident wrt the Atari, but know nothing about
Macs or Amigas.  I don't even have an 68030 Atari but would buy one if there was
a reasonable chance of running BSD.

>Think we could require 68030 or better for openers?

Yes.  68000-only systems don't give the performance necessary, I had Minix on 
my ST for a while but was never very happy with it, for just that reason.

>I was thinking development using gcc...

Yes, the first thing would be to get a gcc cross compiler for Moto chips running
under 386BSD.  This compiler could then be used for cross-development within the
386BSD source tree.

I'm just trying to find a good 3.5" ~ ! GB hard disk to get started :-)

-- Volker
-- 
----------------------------------------------------------------------------
Bitnet:   UNM409@DBNRHRZ1                              Volker A. Brandt
UUCP:     ...!unido!DBNRHRZ1.bitnet!unm409             Angewandte Mathematik
Internet: volker@sfb256.iam.uni-bonn.de                (Bonn, Germany)
From: Minh Lang <minh@inst-sun1.jpl.nasa.gov>
Subject: Mac version of 386BSD??
Organization: Jet propulsion Laboratory
X-Useragent: Nuntius v1.1b2
Date: Mon, 17 Aug 1992 21:37:06 GMT

Is there any Mac version of 386bsd (or something similar that runs on the
Mac)? I would appreciate any info/comments. Thank you.

  == Minh ==
Newsgroups: comp.unix.bsd
From: hpeyerl@novatel.cuc.ab.ca (Herb Peyerl)
Subject: X386 far too busy?
Organization: "NovAtel Communications Ltd."
Date: Mon, 17 Aug 1992 21:11:28 GMT

Hi...

I've just gotten the X386 server to work properly on a
DELL 325 with a noname brand ET3000 card and a DELL Super
VGA monitor.  The server is running in 800x600 mode...

I started the server about 18 hours ago and left it with only 
two xterm's, an icon box, and an xclock running... There was
basically no activity all night.  This morning I did a "ps -agx"
and noticed that X386 had racked up 1145:23.29 CPU (minutes?)... 
That's sort of horrendous isn't it?  I'm presently typing on an
Apollo DN3500 running an X11R4 server... The node's been up since
July 16th and is the node I work on all day long every day and it's
only racked up 465 CPU minutes...

I'm wondering if there's something brutal going on in the X386 server...
I mean, I realize that an ET3000 is not your typically fast card
but XTerm's are REALLY grim... Maybe I'm just used to this Apollo
(which, on it's own is not overly impressive compared to say an 
HP720...)

I dunno... Just wondering if anyone else has noticed this?
-- 
"I was early to finish | hpeyerl@novatel.cuc.ab.ca <Reply-To>   | I brew |
I was late to start, I | peyerlh@cuug.ab.ca                     | there- | 
might be an adult, but | #define JANITOR "Network Administrator"| fore I | 
I'm a minor at heart." |    JANITOR, NovAtel Communications Ltd.|   AM.  |
Newsgroups: comp.unix.bsd
From: w2chase@watson.ibm.com (Chase C)
Subject: Re: Difference btn home-made systems & name-brand systems?
Date: Fri, 14 Aug 1992 14:04:10 GMT
Distribution: ibm
Disclaimer: This posting represents the poster's views, not necessarily those of IBM
Organization: Electrical Engineering, Cornell University, Ithaca NY

In article <1992Aug14.021342.24678@wam.umd.edu>, mc@wam.umd.edu (Morgan Tay Chiu) writes:
|> If I assemble a system myself, using the exact same name-brand COMPONENTS (such
|> as motherboard, HD, floppies, controller, etc.) that are used in big-name PC
|> makers like DELL and GATEWAY, would there be any difference on performance 
|> between those two systems?  
|> 

No, there will be no performance difference if you use the same components. 
However you will almost certainly pay more if you assemble it yourself.

When I priced things, it was about a $400 difference for your basic $3K system.

The advantage of buying it piece-by-piece is that you have precise control over
what pieces you get.  So, if you want the Adaptec 1542B disk controller
(386BSD's favorite SCSI), or the Diamond Speedstar SVGA card (one of the most
well known of the X386-supported video cards) you'll know that's
*exactly* what you're getting.

Just don't be surprised when you see a Gateway add for a similar system running
a few hundred less than what you ended up paying.

Good luck,

Craig
Newsgroups: comp.unix.bsd
From: musik@iastate.edu ()
Subject: Has anyone gotten tvtwm to run in 386bsd?
Organization: Iowa State University, Ames, IA
Date: Tue, 18 Aug 1992 01:08:08 GMT

I've been working on compiling tvtwm to run with X386 on 386bsd.
I kept getting:
	underfined symbol _yylineno in gram.o and parse.o

I checked out gram.c and parse.c and found yylineno to be a simple,
utterly straightforward, extern int.  There are DOZENS (if not more)
of other extern int's that work just fine...  what's going on here?

I've tried recompiling with a different variable name... no worky.
I also tried recompiling it as an int (non-extern), and it compiles,
and appears to be working, but it won't read a system-twmrc or a
.twmrc, etc, etc...

Help?

Damien Guay
musik@iastate.edu
Newsgroups: comp.unix.bsd
From: juengst@boss1.physik.uni-bonn.de (Henry G. Juengst)
Subject: paging via nfs
Keywords: paging, nfs 
Organization: Universit"at Bonn, Informatikinstitut, R"omerstr 154, W-5300 Bonn 1
Date: Tue, 18 Aug 1992 18:48:22 GMT

Hello,

  is it possible to use a page file via nfs for 386BSD ?

Henry

-- 
juengst@boss1.physik.uni-bonn.de [131.220.221.30]
juengst@saph2.physik.uni-bonn.de [131.220.221.12]
juengst@pib1.physik.uni-bonn.de  [131.220.221.2] (strange particle)

I'm only speaking for myself, but not for anybody else !
Newsgroups: comp.unix.bsd
From: niko@iastate.edu (Nikolaus E Schuessler)
Subject: Re: Mac version of 386BSD??
Organization: Iowa State University, Ames, IA
Date: Tue, 18 Aug 1992 13:52:49 GMT


>
>   I was seriously thinking of porting it... I however have a 40M hard drive
>   :-(
>
>You'd be better to start off with 4.4BSD Lite, since that will at
                                   ^^^^^^^^^^^
>least have 680x0 support in it.
>
>Of course, 4.4BSD might get shot.
            ^^^^^^^^^^^^^^^^^^^^^^
shot as in toasted? 

Q:
   1) Where would I get 4.4BSD? (site, directory)
   2) What R the chances of me getting my rump sued?
   3) Do I need some sorta license ?
   4) Is there enough interest?





-- 
Niko Schuessler               
Project Vincent Systems Manager              email: niko@iastate.edu
Iowa State University Computation Center     voice: (515) 294-1672
Ames IA 50010                                snail: 272 Durham 
Newsgroups: comp.unix.bsd
From: hpeyerl@novatel.cuc.ab.ca (Herb Peyerl)
Subject: Re: Restrictions on 'free' UNIX / 386BSD (Re: selling 386BSD)
Organization: "NovAtel Communications Ltd."
Date: Thu, 20 Aug 1992 14:04:28 GMT

Philip Anglin (pjangli@afterlife.ncsc.mil) wrote:
: In article <1992Aug18.155958.3671@murdoch.acc.Virginia.EDU> gsh7w@fermi.clas.Virginia.EDU (Greg Hennessy) writes:
: >Then how come every time my brother wants to install a new program, I
: >have to use EDLIN to edit the config.sys file on his pc?
: >
: And how come I have to wrestle with add-on memory managers to
: use anything beyond 640K?  How come I have to severely limit
: the number of network drivers, device drivers, tsr's, etc, that
: I have loaded, lest I run out of memory?  I've done a heck of a
: lot more "diddling" with my PC than I have with my SparcStation.
: At least Unix uses all its available memory right out of the box.

***STOP**** 
Please take this to alt.my.computer.is.better.than.yours.nyah.nyah.nyah
***STOP****
--
"I was early to finish | hpeyerl@novatel.cuc.ab.ca <Reply-To>   | I brew |
I was late to start, I | peyerlh@cuug.ab.ca                     | there- | 
might be an adult, but | #define JANITOR "Network Administrator"| fore I | 
I'm a minor at heart." |    JANITOR, NovAtel Communications Ltd.|   AM.  |
-- 
"I was early to finish | hpeyerl@novatel.cuc.ab.ca <Reply-To>   | I brew |
I was late to start, I | peyerlh@cuug.ab.ca                     | there- | 
might be an adult, but | #define JANITOR "Network Administrator"| fore I | 
I'm a minor at heart." |    JANITOR, NovAtel Communications Ltd.|   AM.  |
From: dawes@physics.su.OZ.AU (David Dawes)
Newsgroups: comp.unix.bsd
Subject: init, rc, signal handling (386BSD)
Date: 13 Aug 92 10:32:35 GMT
Organization: School of Physics, University of Sydney, Australia


I've noticed that signal handling gets screwed up for commands run from
/etc/rc.  One particular example is xdm.  When started from /etc/rc
the signal handlers it installs don't work -- the signals get ignored.
I checked the init source, and it resets the signal handling the SIG_DFL.

I tried a simple program which checks this, and the default handler's are
correctly set -- but signals are being ignored regardless of the default
behaviour or if a handler is installed.

This is making it impossible to shutdown xdm cleanly when it is started
at boot time from /etc/rc.

Does anyone have any ideas about this?

David
--
------------------------------------------------------------------------------
 David Dawes (dawes@physics.su.oz.au)    DoD#210      | Phone: +61 2 692 2639
 School of Physics, University of Sydney, Australia   | Fax:   +61 2 660 2903
------------------------------------------------------------------------------
From: guy@Auspex.COM (Guy Harris)
Newsgroups: comp.unix.bsd
Subject: Re: Reading 386bsd dist files (bin,src,etc)
Keywords: byte swapping problem
Date: 20 Aug 92 21:25:10 GMT
Distribution: usa
Organization: Auspex Systems, Santa Clara

>Attempting to use cpio to extract the files in the various
>386bsd dists, I ran into a byte swapping problem (running on both a Gould
>and a SUN3).  CPIO generates the wonderfully-descript error message "Out of
>phase -- get help" and then exits.

If that's so, then unless your Sun-3 is running SunOS 3.0 or so, there's
something broken in its "cpio".  As of SunOS 3.2, "cpio" is supposed to
automatically figure out if it's trying to read an old-format (not "-c")
"cpio" file in the wrong byte order, and automatically swap the bytes
for you.  (The changes to do that should also be in the BSD "cpio".)

>Since I really want to look at the srcdist stuff off-line from my PC
>(not enough memory yet!) but couldn't find any flag to massage cpio into
>appropriate behavior on the Gould or the SUN (so much for archive portability)

SV's "cpio" is busted, and has some almost completely useless
byte-swapping flags that don't help.  Sun's (not "SUN", please) "cpio"
should, as indicated, automatically figure out that it has to swap the
bytes.

As indicated elsewhere, the *correct* answer is to use "cpio -c" when
creating "cpio" archives; that causes "cpio" to make text, rather than
binary, headers, which obviates the need for byte-swapping.
Newsgroups: comp.unix.bsd
From: dabdub@aeolus.caltech.edu (Donald Dabdub)
Subject: FORTRAN for 386BSD?
Originator: dabdub@aeolus.che.caltech.edu
Organization: California Institute of Technology, Pasadena
Date: Thu, 13 Aug 1992 06:08:39 GMT

Hello world!

I am almost ready to install 386BSD on my 386.  I have been following
this newsgroup for a while and read the bsd-FAQ..  I have not seen any
reference to FORTRAN.  I have read that C and C++ come bundled with 386BSD.

Is there a Fortran compiler available for 386BSD?  Where would I get it?
Is it free?

Please send your answers to:
dabdub@aeolus.che.caltech.edu


I will summarize the responses and post them in the newsgroup.

All the best,


-- 
Donald Dabdub
210-41 Chemical Engr
CALTECH
Pasadena, CA 91125
From: satmech@ecst.csuchico.edu (satmech)
Newsgroups: comp.unix.bsd
Subject: fix for tip
Date: 23 Aug 92 12:58:50 GMT
Organization: California State University, Chico

This patch fixes the problem of tip being stuck in 7bit word length, if
you use zmodem at all, you need this.

*** tip.c.orig	Sun Aug 23 06:35:02 1992
--- tip.c	Sun Aug 23 06:23:15 1992
***************
*** 593,599 ****
  		bits8 = 1;
  		return;
  	}
! 	bits8 = 0;
  	flip = 0;
  	clr = 0377;
  	set = 0;
--- 593,599 ----
  		bits8 = 1;
  		return;
  	}
! 	bits8 = 1;
  	flip = 0;
  	clr = 0377;
  	set = 0;
Newsgroups: comp.unix.bsd
Subject: Re: Restrictions on free UNIX / 386BSD (R
From: rmk@rmkhome.UUCP (Rick Kelly)
Organization: The Man With Ten Cats
Date: Wed, 19 Aug 1992 02:50:35 GMT
Reply-To: rmk@rmkhome.UUCP (Rick Kelly)

In article <7238@skye.ed.ac.uk> richard@aiai.ed.ac.uk (Richard Tobin) writes:
>In article <1992Aug18.015903.8526@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes:
>>Because Hurd is an OS, does this mean that *any* application that runs on it
>>is a derivitive work and falls under GNU Public License?
>
>No, no more than any application that runs under SunOS falls under Sun's
>licence.
>
>It would probably be better if you didn't suggest this to USL's lawyers :-)


At this point, since the Hurd is only vaporware, this doesn't matter.

-- 

Rick Kelly	rmk@rmkhome.UUCP	unixland!rmkhome!rmk	rmk@frog.UUCP
From: David.Fox@Saigon.COM
Newsgroups: comp.unix.bsd
Subject: Mountain filesavfafe support in 0.1
Date: 10 Aug 92 01:29:55 GMT
Organization: Station Zebra Corp, Sunnyvale CA Ph:408-739-1520

I have a Mountain Filesafe tape drive (Mach2 controller, Model 8000 Plus
and it uses a proprietary tape format (TD-101) under MS-DOS.  I'm consider-
ing to switch to 386bsd, and it would be nice if my tape drive were
supported.  I know I can read/write QIC-80 format tapes, and if TD-101
isn't doable, I'd sure like to see QIC-80 in there soon.  Anyone have
a timeframe for that?  (I am aware that it is unsupported at this time.)
Xref: sparky comp.unix.bsd:4115 comp.sys.ibm.pc.hardware:21802
From: jack@admin.mport.COM (Jack Craig)
Newsgroups: comp.unix.bsd,comp.sys.ibm.pc.hardware
Subject: Re: Another Adaptec Question
Date: 13 Aug 92 19:59:47 GMT
Followup-To: comp.unix.bsd
Organization: Microport Inc., Scotts Valley, CA 95066 US of A

hollings@cs.wisc.edu (Jeff Hollingsworth) writes:

>There seems to be two versions of the Adaptec 1542A card, one that supports bus
>mastering and one that does not.  I have two questions about this:

not quit, the 1542[a/b] both support(are forced to use) bus mastering.

the 1522 is a pio device(no bus master).

>1.) How much benefit is bus mastering for UNIX (assumming the OS supports it)
A lot! you should talk to neal nelson on this subject, 312-755-1000.
hes doing a paper on it.

>2.) Does either BSDI or 386bsd support bus mastering?
its up to the host adapter and its driver.

>One other question, what exactly do the Adaptec cards do that make them
>more expensive than the Future Domain cards?

i dont beleive the FD card is a bus master. BM takes a cpu on the
card to do the work, that is part of the cost.

jack...
=============================================================================
 Jack Craig      Microport SVR4      408-438-UNIX        uunet!mport.com!jack   
=============================================================================

>-------------------------------------------------------------------------------
>Jeff Hollingsworth					Work: (608) 262-6617
>Internet: hollings@cs.wisc.edu				 FAX: (608) 262-9777
>Home: hollings@warthog.madison.wi.us			Home: (608) 256-4839
>X.400: <pn=Jeff.Hollingsworth;ou=cs;o=uw-madison;prmd=xnren;c=US>
From: bs@Germany.EU.net (Bernard Steiner)
Newsgroups: comp.unix.bsd
Subject: 386bsd disk sector size
Date: 14 Aug 1992 11:17:00 GMT
Organization: EUnet Backbone, Dortmund, Germany
Distribution: world
NNTP-Posting-Host: walhalla.germany.eu.net

Folks,
I checked the documentation for my second ESDI drive (yeah, WREN III)
and the i fiddled with the dip switches - et voila: I got sectors of 2048
bytes each and 10 sectors per track. This seems to be slicghtly more than
sectors of size 512 with 36 sectors per track.

Question: Is it possible to use 2k *physical* block size for the second drive ?
I think there may be problems with the bootstrap code if it were the first
drive - loading sector #0 for initial bootstrap is OK, but then what about
loading the following 15 sectors ?

Anyway, using that as the second drive is OK, so how about it ?

Bernard
-- 
Bernard Steiner, FB Informatik/IRB, Uni Dortmund,    vox +49 231 755 2444
Postfach 500500, D-W-4600 Dortmund 50, Germany       fax +49 231 755 2386
bs@Germany.EU.net          ...!uunet!unido!bs

*III  And they gave it Instructions, but knew it not. } From The Book of Nome,
*IV   It is, they said, a Box with a Funny Voice.     }      Mezzanine v.III-IV
Newsgroups: comp.unix.bsd