add directory bin

bin/partition-programs/edpart.doc

@@ -0,0 +1,31 @@
+Edpart.exe is a disk partition editor capable of managing up to four
+partitions on PC/XT and AT hard disks.  It specifically says "no
+copyright", so I figured someone else might like to use it rather than
+doing fdisk/diskfix pairs to create partitions.
+
+There's no instruction file and no real on-line help, so here's a
+summary:
+
+EDPART.EXE maintains up to four hard disk partitions on either of two
+hard drives.  If it sees more than one hard drive, it will ask which
+one to edit.
+
+The commands are:
+
+CREATE	Create hard disk partitions
+DELETE	Delete hard disk partitions
+STATUS	Bootable partitions may have the following status:
+	ACTIVE		This partition is the boot partition
+	READ/WRITE	R/W, not the boot partition
+	Non-bootable partitions (``extensions'') may be any of:
+	READ/WRITE
+	READ-ONLY
+	INACCESSIBLE
+TYPE	There are four types; for Minix purposes, either "extension"
+	type will do to my knowledge.
+	DOS(4) Bootable		For DOS 3.x
+	DOS(4) Extension
+	DOS(1) Bootable		For DOS 2.x
+	DOS(1) Extension
+	The "Bootable" partitions are recognized by MS-DOS directly,
+	so I don't advise using either of them for Minix.

bin/partition-programs/pdisk.doc

@@ -0,0 +1,79 @@
+This stuff is mostly self explanatory, but:
+	part takes one optional argument, which is the disk number with
+	which to start (either 0 or 1. 0 is default).
+
+	286pd1.sys and 286pd2.sys are for driving partitions on your first
+	and second disks, respectively.  They will only work on 80186 or higher
+	processors.  For 8086/8088 computers, use pdisk1.sys, pdisk2.sys. They
+	are just a *wee* bit slower....
+
+	fdins is for use when you're short of free space in "low menory" --
+	i.e. free interrupt vectors.  fdintins, on the other hand, doesn't
+	use up any application space memory.  In either case, these programs
+	don't do *anything* directly -- you run them in order to create a
+	.COM program that does the dirty work.  You get TBL1.com, TBL2.com,
+	TBL1INT.com, or TBL2INT.com, depending on whether you run fdins,
+	fdintins and specifiy disk 1 or 2 (== 0 or 1).
+
+	pformat is for when you want to be particularly destructive with your
+	new partition.  You run "pformat <drive>:" where <drive> must be a
+	valid pdisk.  It's good for marking newly developed bad sectors,
+	I guess.  Be careful.
+
+According to tests I ran with the PC Magazine benchmark program, disk access
+to a pdisk is actually faster than the normal DOS driver (i.e. C: or a DOS
+3.3/4.x extended DOS partition).  (This may only be true using the 286 version,
+and may be affected by your usage.  The main point is that you certainly do
+not take a performance *cut* by using my program.)
+
+I am not including most of the COPYING file that comes with stuff from the
+Free Software Foundation (Richard Stallman, et al.) because I don't know
+if I'm allowed, but that's what I intend for this software.  Specifically,
+you can *give* away as many copies of this software as you like.  You can
+charge a *reasonable* handling fee.  You can even incorporate parts of it
+into other projects, as long as you distribute at least the source you got
+from pdisk.  I don't want money or contributions, I want plaudits.  I hope
+this software is helpful to you.
+
+When you find the inevitable bug (there are *none* in the driver, but I
+don't absolutely swear for the partitioning program), please try to
+fix it yourself and let me know the solution.  Failing that, drop me a
+line describing the situation exactly, especially including DOS version and
+all hardware, including fixed disk and controller type.  I don;t promise
+to do anything about it, but I might.
+
+One thing I recommend from experience:  my boot code will only work on some
+IBM compatibles.  It is best to use the manafacturer's (or generic) MSDOS
+fdisk to set up the initial partition, then use "format c: /s" to set up
+your bootable DOS partition.  If you can get this working right with pdisk,
+that would be nice.
+
+have fun.  Scott E. Garfinkle
+			smsdpg!seg@uunet.uu.net
+
+<The following is taken from Project Gnu's AWK distribution, the COPYING
+ File.  I hope I'm not violating their copyright, or anything.
+ >
+
+		       NO WARRANTY
+
+  BECAUSE PDISK IS LICENSED FREE OF CHARGE, WE PROVIDE ABSOLUTELY NO
+WARRANTY, TO THE EXTENT PERMITTED BY APPLICABLE STATE LAW.  EXCEPT
+WHEN OTHERWISE STATED IN WRITING, SCOTT GARFINKLE
+AND/OR OTHER PARTIES PROVIDE PDISK "AS IS" WITHOUT
+WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT
+LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
+A PARTICULAR PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND
+PERFORMANCE OF PDISK IS WITH YOU.  SHOULD PDISK PROVE DEFECTIVE, YOU
+ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+ IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW WILL  SCOTT GARFINKLE
+AND/OR ANY OTHER PARTY
+WHO MAY MODIFY AND REDISTRIBUTE PDISK AS PERMITTED ABOVE, BE LIABLE TO
+YOU FOR DAMAGES, INCLUDING ANY LOST PROFITS, LOST MONIES, OR OTHER
+SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR
+INABILITY TO USE (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA
+BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY THIRD PARTIES OR A
+FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS) PDISK, EVEN
+IF YOU HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, OR FOR
+ANY CLAIM BY ANY OTHER PARTY.