HDTenEightyP/NetNews huggingface dataset:
From: anything@max.u.washington.edu
Subject: [X386] xdm won't start display :0
Organization: 
Date: Fri, 2 Oct 1992 15:46:09 GMT

HELP!!!
when I start xdm from root I get a lot of disk activity and nothing else.
upon reading my /usr/X386/lib/X11/xdm/xdm-errors I find:

X386 Version 1.2E 1.0.2a / X Window System
(protocol Version 11, revision 0, vendor release 5000)

Fatal server error:
no screens found
error (pid 1064): IO Error in XOpenDisplay
error (pid 1062): Display :0 cannot be opened
(repeated ad nauseum.... and varied with)

Fatal server error:
no screens found
error (pid 1062): Server for display :0 terminating unexpectedly: 1
(also repeated)

the setup is traight out of agate.berkeley.edu /pub/incoming/X386 using
x386install. the video setup is a diamond speedstart Plus using 1024K and the
et4000 chip, the screen is a nec multisync 2 and the default mode was 640x480
which was well within the capabilities of the display combo.
any ideas?

Don Levinson
anything@max.u.washington.edu
alt: levinson@halcyon.com

Newsgroups: comp.unix.bsd
From: bill@twwells.com (T. William Wells)
Subject: Re: 386BSD PARTIAL PATCH KIT NOW AVAILABLE
Date: Sat, 26 Sep 1992 10:04:10 GMT
Summary: DAG's in shell scripts? Sure!
Distribution: usa
Organization: None, Mt. Laurel, NJ

In article <1992Sep15.175003.2628@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes:
: patch00005 will *not* report the requirement of patch00002 if you attempt
: to install it before the other patches, since I only report the immediate
: prerequisites rather than building a directed graph for the available
: patches (something rather hard to do in shell script 8-)).

Once, I wrote a shell script to determine the set of all
intersections of a set of sets. It's amazing what you can do with
sort, join, comm, tsort, and a few other nifty standard tools.

Supposing you have a collection of patches and a set of
dependencies, as in: X -> Y means that X must be applied before Y.
Represent these as pairs on lines, as in:

patch0001       patch0002

means patch0001 is require for and must be applied before
patch0001. (If A -> B and B -> C, only those two have to be
represented; A -> C doesn't, though representing it is harmless.)

Suppose that a collection of wanted patches are specified. The
following script, give or take a few bugs, determines the complete
set of required patches:

cp $1 /tmp/in # input file
order=$2 # file of dependencies
in=/tmp/in
out=/tmp/out
sort +1b $order -o $order
sort -u $in -o $in
while :; do
	join -j1 2 -o1.1 $order $in | sort -u - $in >$out
	if cmp $in $out; then
		mv $out $in
	else
		break
	fi
done
tsort $order |
    egrep -n . |
    sort -t: +1 |
    join -d: -j1 2 - $out |
    sort -n |
    sed 's/^[0-9]*://'

How this does it and what the bugs are (hint: I didn't look at
the manual when I wrote those options to join!) is left as an
exercise for the reader. :-)

---
Bill                            { uunet | decwrl | telesci }!twwells!bill
bill@twwells.com
From: terry@cs.weber.edu (A Wizard of Earth C)
Newsgroups: comp.unix.bsd
Subject: 386BSD PATCH KIT BETA -- PUBLIC RELEASE
Date: 4 Oct 92 11:14:43 GMT
Reply-To: terry@icarus.weber.edu
Organization: Weber State University  (Ogden, UT)


	The 386BSD patchkit 0.1 beta-1 is now complete.  Distribution is
dependant on how long it takes to make it to the normal 386BSD directory
on agate.berkeley.edu.  From there, it will probably be mirrored all over
automatically, and you will see it at your local archive in the next several
days.

	Main features of the new patch kit are:

o	Ability to use "I ALL" to install all patches without user
o	The real Makefile.i386 fix from Chris G. Demetriou
o	All known boot problem patches
o	All known memory problem patches
o	Reserved ports on NFS
o	NFS support for AIX3.2 clients
o	All known stability patches (Greenman/Maclachlan/Kranenburg/etc.)
o	All XFree86 compatability patches
o	The McKay "eats a key until another key is hit" fix
o	Fixes for sh and csh
o	Second WD disk patch
o	WD ethernet to WD ethernet routing patch
o	Init fixes
o	Kernel profiling fixes
o	Floating exception in "ps" fixed
o	Herb Peyerl's fix to allow 3COM 3C503 AUI selection from ifconfig
o	Make fixes
o	File system fixes, including "disappearing CD ROM files" fix
o	CMOS Daylight savings time fixes in the kernel
o	Bob Wilcox's fix to elvis ("vi") to fix yank buffers
o	SILO overflow fixed (if using 16550's)
o	Fixed "hang after copyright" (workaround, but works)
o	Make *all* the games compile
o	Havard Eidnes' netstat fixes
o	Havard Eidnes netstat installed for you (binary patch)


A full listing for each patch follows in the next two posts.



					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: wkt@csadfa.cs.adfa.oz.au (Warren Toomey)
Subject: Reminder: comp.unix.bsd news archive
Organization: Australian Defence Force Academy, Canberra, Australia
Date: Tue, 6 Oct 1992 04:44:50 GMT

A reminder that I'm archiving comp.unix.bsd in minnie.cs.adfa.oz.au:bsdnews.
Readme follows...


Welcome to the 386BSD news archive in minnie. This contains the Usenet news
articles from comp.unix.bsd since just before 386BSD 0.1. If the 386BSD
newsgroup changes, the archive here will track the change.

The archive is kept as a set of MS-DOS ZIP files, each containing 100 news
articles. For example, 3400.zip contains articles 3400 to 3499. Requests to
change the format of the archive will fall on deaf ears.

Other files in this directory give the subject lines for the articles. For
example, subject.300 holds the subject lines for files 3000 to 3999. These
subject files are ordered by subject, not by article number. I have edited
out those articles related to the USL/BSDI suit etc. etc.

Updates to the archive will probably be done on a weekly basis. Disk space
is currently tight, so expect to see files disappear on a FIFO or LRU basis.

	Warren Toomey	wkt@csadfa.cs.adfa.oz.au


Newsgroups: comp.unix.bsd
From: st923150@pip.cc.brandeis.edu (Benjamin A. Tober)
Subject: Problem with xconsole
Reply-To: st923150@pip.cc.brandeis.edu
Organization: Brandeis University
Date: Sun, 27 Sep 1992 17:45:44 GMT

Folks-
	I'm using 386BSD with X386 and it works nicely except that xconsole
does not function properly.  Attempts to write to /dev/console cause
keyboard input to be mangled, thus necessitating a reboot.  I do have
getty disabled on /dev/console and the ownership of /dev/console is correct
(i.e.- the same as the invoking user).  I'm using xdm and twm.  Has anyone
seen this phenomenon?  Is there a fix?
-ben
Newsgroups: comp.unix.bsd
From: SCHLIGHW@dosuni1.rz.uni-osnabrueck.de (Hans Schligtenhorst)
Subject: anybody uses IDE and SCSI in one PC?
Organization: University of Osnabrueck, FRG
Date: Tue, 6 Oct 1992 14:12:09 GMT

Hi!
 
Simple question: Uses anybody SCSI-harddisk (perhaps with streamer?) and IDE-
hd in one computer? On which hd is bsd installed? Are there any subject to look
for?
 
Thanks in advance
 
Hans
--
Hans Schligtenhorst                     ! Hey, my computer is a musician.
schlighw@dosuni1.rz.uni-osnabrueck.de   ! The hd squeaks in C-major ...
Newsgroups: comp.unix.bsd
From: witr@rwwa.COM (Robert Withrow)
Subject: Re: Newbies (Was Re: new new scsi release beta2 part 1 of 5)
Reply-To: witr@rwwa.com
Organization: R.W. Withrow Associates
Distribution: usa
Date: Sun, 4 Oct 1992 15:26:19 GMT

In article <id.LBST.KY3@ferranti.com>,
  peter@ferranti.com (peter da silva) writes:

| For the past 6-8 years I've been gafiating in System V land, and one of
| the few really nice things about System V [...] is the configuration method. 
| [..] I've not seen better, for any OS.

It has it's shortcommings, namely the time required for a test-change-test 
cycle during active developement.  The ID stuff goes through and rebuilds
*all* of the space.c and stubs.c files for every driver, deletes *all* of
the /dev nodes, creates new ones, rebuilds the config.h, etc... for *every*
cycle.  In contrast the BSD method usually amounts to a single compile, link,
copy, and reboot.  The difference in times is frequently an order of magnitude.
(like 10 minutes versus 1) ((still faster than watching VMS reboot though ;[) ))

I would prefer a method that selects the best features of both, namely
something like the device configuration methodology from the ID stuff, but
the make-based building method from BSD.  This could be used for binary-only
rebuilding also.

-- 
 Robert Withrow, Tel: +1 617 598 4480, Fax: +1 617 598 4430, Net: witr@rwwa.COM
 R.W. Withrow Associates, 21 Railroad Ave, Swampscott MA 01907-1821 USA
Newsgroups: comp.unix.bsd
From: andrick@sun.rhrk.uni-kl.de (Ulf Andrick [Biologie])
Subject: Re: Installing 386bsd
Organization: University of Kaiserslautern, Germany
X-Newsreader: Tin 1.1 PL4
Date: Tue, 6 Oct 1992 16:21:00 GMT

terry@cs.weber.edu (A Wizard of Earth C) writes:
: In article <Bvn4H4.5Fz@immd4.informatik.uni-erlangen.de> prkoch@cip.informatik.uni-erlangen.de (Peter Koch) writes:
: >
: >my technical datas
: >------------------
: >
: >	386 25MHz
: >	AMI-BIOS
: >	8 MB RAM
: >	1.2 MB and 1.44 MB floppys
: >	205 MB Seagate AT-Bus disk
: >	- 33MB DOS 3.3 - System Partition
: >	- 70MB DOS 3.3 - Extended Partition
: 
: The DOS partition should follow the 386BSD partition on the disk; the
: 386BSD partition has to be first.
: 
: The use of a 33Meg primary DOS partition is good; it means that the
: "shutdown -todos" will work for you.
: 
: You didn't say if you are using IDE; if you were, select drive type 45

German `AT-Bus' translates to IDE in English.

: in the CMOS setup and enter in the actual number of heads/cylinders/etc.;
: this may mean that you can't use all your drive, since DOS is dumb about
: greater than 1024 cylinders.
: 
: Alternately, you can use the whole disk for 386bsd, in install sufficiently
: to rebuild asboot and disklabel, and move the 386BSD partition to later
: on the disk.  This will take a lot of work; installing 386BSD *and* DOS
: on the same IDE drive is difficult.

Is it? My partition tables make me believe that my DOS
partition is the first on my disc and that 386BSD partitions are
located after it. The DOS partition just happened to be where
it is when I set up 386BSD by `install'. Do I face any major
problems because of that?

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

--
Ulf R. Andrick                                andrick@rhrk.uni-kl.de
FB Biologie - Tierphysiologie
Universitaet                             Was du nicht selber weiszt, 
D-W 6750 Kaiserslautern       das muszt du dir erklaeren (Tegtmeier)
Xref: sparky comp.unix.bsd:6671 comp.unix.large:328 comp.sys.ibm.pc.rt:514
From: tm8t+@andrew.cmu.edu (Tod McQuillin)
Newsgroups: comp.unix.bsd,comp.unix.large,comp.sys.ibm.pc.rt
Subject: Re: strdup
Date: 1 Oct 92 05:45:58 GMT
Article-I.D.: andrew.Qemk4KW00WB98ZYN5Z
	<lckirmINNosg@spim.mti.sgi.com>
Organization: Carnegie Mellon, Pittsburgh, PA

koblas@mips.com (David Koblas) writes:

> Here's a copy (typed in off the cuff, so I won't say it is
> guaranteed to work):
> 
>         char *strdup(char *str)
>         {
>                 char    *cp = (char *)malloc(strlen(str));
>                 return cp ? strcpy(cp, str), cp : NULL;
>         }
> 

Good thing you included a dislaimer.  You need to use
malloc(strlen(str)+1) else the null terminator may trash the heap.

Here is the 4.3BSD-reno version: (sorry about the long copyright but they
insist you leave it in)

/*
 * Copyright (c) 1988 The Regents of the University of California.
 * All rights reserved.
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 * 1. Redistributions of source code must retain the above copyright
 *    notice, this list of conditions and the following disclaimer.
 * 2. Redistributions in binary form must reproduce the above copyright
 *    notice, this list of conditions and the following disclaimer in the
 *    documentation and/or other materials provided with the distribution.
 * 3. All advertising materials mentioning features or use of this software
 *    must display the following acknowledgement:
 *	This product includes software developed by the University of
 *	California, Berkeley and its contributors.
 * 4. Neither the name of the University nor the names of its contributors
 *    may be used to endorse or promote products derived from this software
 *    without specific prior written permission.
 *
 * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
 * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 * ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
 * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
 * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 * SUCH DAMAGE.
 */

#if defined(LIBC_SCCS) && !defined(lint)
static char sccsid[] = "@(#)strdup.c	5.4 (Berkeley) 2/24/91";
#endif /* LIBC_SCCS and not lint */

#include <stddef.h>
#include <stdlib.h>
#include <string.h>

char *
strdup(str)
	const char *str;
{
	int len;
	char *copy;

	len = strlen(str) + 1;
	if (!(copy = malloc((u_int)len)))
		return((char *)NULL);
	bcopy(str, copy, len);
	return(copy);
}
Newsgroups: comp.unix.bsd
From: hasty@netcom.com (Amancio Hasty Jr)
Subject: Re: X386 gives a bus error in ET4000EnterLeave()
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Date: Sat, 3 Oct 1992 22:44:47 GMT

In article <48243@shamash.cdc.com> pbd@runyon.cim.cdc.com (Paul Dokas) writes:
>I've completely rebuilt X11R5 from the original (patched) MIT source
>and now I'm trying to run it, but typing "X386 :0" results in:
>
>       X386 Version 1.2E 1.0.1  / X Window System
>       (protocol Version 11, revision 0, vendor release 5000)
>       Bus error
>
	Two reasons this may happen:
	(1) you have not switch to X mode in x386Init.c
	(2) your kernl was not patched for X support in pccons.c
	If you are interested in the way that did, you
	can look in agate.berkeley.edu:/pub/incoming/X386, at
	patches for X and 386bsd.

	If you have further problems, just e-mail to me.

	Enjoy,
	Amancio Hasty

>:-(
>
>My SVGA card is a et4000 card (Diamond SpeedStar Plus) in a generic
>386.  I've tried several different Xconfig's, but there seems to be
>little difference:
>
> .
> .
> .
>#
># The graphics drivers
>#
>vga256
>  chipset "et4000"
>  videoram 1024
>  viewport 0 0
>  virtual 1024 1024
>  clocks 25 28 65 72 79 59 64
>  modes "640x480" "800x600" "1024x768"
>
>ModeDB
>#Modename    clock  horzontal timing      vertical timing
> "640x480"   25     640  664  760  800    480  491  493  525
> "800x600"   36     800  824  896 1024    600  601  603  625
>             40     800  840  968 1056    600  601  605  628
> "1024x768"  65    1024 1088 1200 1328    768  783  789  818
>
>I've run X386 through gdb and found that it's dying on line 398
>of et4000/driver4.c, which is:
>
>      vgaIOBase = (inb(0x3CC) & 0x01) ? 0x3D0 : 0x3B0;
>
>(actually in the inb() which is an inline function found in ../../compiler.h)
>So it seems that I can't read/write to the needed ports. Anyone have any
>suggestions?  Am I SOL because of the Diamond card?  I thought that the
>proprietary clocks were only on the newer cards like the Stealth.
>
>BTW, I've patched and rebuilt my kernel with the XSERVER patches.  I've
>also created a /dev/vga with "mknod /dev/vga c 12 0".
>
>-- 
>#include <std.disclaimer>
>#define FULL_NAME                          "Paul Dokas"
>#define EMAIL                              "pbd@runyon.cim.cdc.com"
>/* we are realizing infinite possibilities in exchange for our soul */


Newsgroups: comp.unix.bsd
From: philsuth@mycroft.DIALix.oz.au (Phil Sutherland)
Subject: Re: AHA1542B vs Sysgen SC4000 controller under BSD386
Reply-To: philsuth@DIALix.oz.au
Date: Tue, 6 Oct 92 01:13:14 GMT

brian@ucsd.edu (Brian Kantor) writes:

>I managed to score a Sysgen SC4000 SCSI-to-QIC-02 controller, an Adaptec
>Stand-Alone-Tape-Controller QIC-02-to-QIC-36 board, and an Archive 5945C 
>drive.  This bizarre combination is what Sun used to use in their really
>old (Sun-2/68010 days) tape backup boxes.

>When I connect this mess up to my Adaptec controller and try to bood
>386BSD with Julian's SCSI package, the error light on the SC4000 comes
>on, and the computer just keeps telling me that command timed out.
>The light on the Adaptec just stays on.

Your problem may be that the early versions of SCSI did not support
SCSI bus parity. I believe (though I don't have a manual close at
hand) that the 1542B at least can be jumpered to disable SCSI parity
checking. Note that you'll have to do this for all devices connected
to that SCSI bus, including any disk drives etc.

phil


-- 
------------------------------------------------------------------------
Phil Sutherland        Perth, Western Australia    philsuth@DIALix.oz.au
From: matt@OES.ORST.EDU (Matthew Curfman)
Newsgroups: comp.unix.bsd
Subject: RN/TRN ported to 386BSD?
Date: 30 Sep 92 06:52:54 GMT
Organization: Oregon Extension Service, Oregon State University, Corvallis, Or.

Has anybody had any success porting RN-4.3 or TRN-2.2 to 386BSD?

I have had problems porting either of these in the remote server configuration.
Details of the problems will be supplied on request.  I'd just like to avoid
reinventing the wheel if it already exists.

Thanks,

-mc
_____________________________________________________________________________
Matt Curfman                                        Computing Technology Unit
matt@oes.orst.edu                           Oregon State University Extension
Newsgroups: comp.unix.bsd
From: adam@cs.curtin.edu.au (Adam Sawyer)
Subject: Corruption in BIN01.56?
Organization: Curtin University of Technology
Date: Wed, 30 Sep 1992 13:56:22 GMT


Has anyone else had problems when trying to extract the BIN01.(1-56) 
distribution?

When I go to extract the files (after mread b:*.* /tmp) for all 56 BIN01.X
files, I am always getting the error :

Corruption in BIN01.56

And I've already b) recopied the file onto a new disk
                 c) re-ftped the file from kirk.bu.oz.au
                 d) (re-ftped ensuring that I was in BINARY mode)
                 d) re-ftped from agate.berkeley.edu


And now I'm lost for ideas, its only this one last file *sigh*


Adam!
From: alan@ulka.zso.dec.com (F. Alan Jones)
Newsgroups: comp.unix.bsd
Subject: Re: How to format UNIX floppies under 386BSD
Date: 6 Oct 92 17:36:48 GMT
Article-I.D.: ninja.1992Oct6.173648.13606
Reply-To: alan@ulka.zso.dec.com (F. Alan Jones)
Organization: Digital Equipment Corporation


What you are asking me to do is bring down a mult-user system because
someone forgot to keep a supply of formated disks.  What I'm looking
for is DOS independence.  I'll repeat my question:  Does there exist
source for isa/ide lower level floppy formatting?  Does there exist
a good reference on the subject?

Alan
Newsgroups: comp.unix.bsd
From: rich@Rice.edu (Richard Murphey)
Newsgroups: comp.unix.bsd
Subject: Re: Where can I find xterm for 386BSD for PC.
Date: 6 Oct 92 03:49:40 GMT
Reply-To: Rich@rice.edu
Distribution: usa
Organization: Department of Electrical and Computer Engineering, Rice
	University

In article <1aqhtdINNb4r@gossip.pyramid.com> dinesh@pyramid.COM (Dinesh Jalisatgi) writes:
    I just downloaded the X386 oftware from agate and I find that there is no xterm included in it.

    Where can I find one for the 386BSD based PC.

See the annoucment for XFree86 posted here today.  There is an xterm
executable in /pub/386BSD/0.1-ports/XFree86/core-bin-1.1.tar.Z which
is part of the 1.1 distribution.  Rich
Newsgroups: comp.unix.bsd
From: wutcd@chemnitz.guug.de (Joerg Wunsch)
Subject: Re: [386BSD] fixing ps: major/minor numbers for /dev/console wrong?
Organization: tu-chemnitz
Date: Mon, 28 Sep 1992 17:26:32 GMT

ghod@drycas.club.cc.cmu.edu writes:

>Actually, this was a true honest to goodness bug, not an attempt to whittle
>the kernel down to fit onto the distrubution diskette. The kernel on dist.fs
>is slightly larger than 400 Kbytes. The one I ftp'ed from
>rachel.ibmpcug.co.uk was about 380 Kbytes, and included more drivers than the
>stock kernel. Go figure. :)
Okay, you win.

>...
>command name, not the command line args, so I guess the solution will indeed
>lie in some kernel hacking.
Yes, in my eyes, i'm totally sure of this.

>Unfortunately, I don't have the space to build
>a new kernel (and with only a 16Mhz 386SX it would probably take days :)
Oh noooo, you're totally wrong. I'm running 386bsd only on two different
386/sx with 16 MHz, too. If this'll take one our, it's a lot. Most of
the time (at least, it seems so) will take the ``make depend'', i.e.
if you design a new driver and only make minor changes (no re-config),
you'll have to do this only once. The re-compilation after something has
changed is done in less than 15 minutes! Seems that those simple boxes run
quite faster than with dos. But you should have some ram inside and not
too few swap space.

	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: alan@ulka.zso.dec.com (F. Alan Jones)
Subject: Re: How to format UNIX floppies under 386BSD
Reply-To: alan@ulka.zso.dec.com (F. Alan Jones)
Organization: Digital Equipment Corporation
Date: Wed, 7 Oct 1992 02:22:47 GMT


brian@ucsd.edu (Brian Kantor) writes:

|> The manual for the floppy controller chip shows you precisely what
|> you need to do to format a floppy.  If you want to see example code that
|> implements that flowchart, look at the IBM PC Technical Reference
|> Manual in the BIOS listing, or at any of the older CP/M BIOSs.

Thanks for the reply Brian.  So, what make/model is the floppy controller
chip on a stock PC?  When I have that, I can write the manufacturer.  My
PC is a "street" machine with no docs.  I assume the IBM PC Tech Ref is
off the shelf and still in print.

Alan
P.S.  I get the idea.  Looks like driver code with raised IPL.  Did we say
this was a real time OS (just kidding)?