home *** CD-ROM | disk | FTP | other *** search
- DSKDRIVE documentation (85/1/30) C.B.Falconer
- =============================================
- revised 85/5/15
-
- Copyright (c) 1985 by C.B. Falconer. This program may not be SOLD without
- express written permission. It may be copied and used as desired.
-
- As presently configured this program allows read/write of IBMPC CPM86 DSDD,
- HP125 (DSDD), Televideo TS802 (DSDD), and KAYPRO II (SSDD) format disks on
- the Kaypro 4 (at least the 1983 version Kaypro). The Kaypro II format is
- included because the Kaypro native disk sensing system cannot distinguish
- between double sided disks and double side disks that have been re-
- formatted to single sided. The program is designed to be dynamically
- alterable to other disk configurations, and can also read Kaypro format
- disks. (see source annotation).
-
- The various alternate configurations are specified by executing
-
- d>DSKDRIVE A (or B or C). omitting a parameter used the default.
-
- The separate program ALTDRIVE allows configuration to a wide range of disk
- formats, through menus or direct specification. This has not yet been
- released, but will work with your revised version if you follow the stated
- rules, and above all do not alter the "info" vector format.
-
- You will require RSX.DOC for documentation on installation and protocol.
- To customize to your own system you must build the host driver (rdhst and
- wthst), and customize the "seek" procedure to your hardware (which
- hopefully uses the WD 179x series of disk controller chips). I suggest you
- first get the program to read your own disks. A "marked" disk, containing
- full 128 byte records (including cr and lf) which specify the track,
- sector, and physical sector (agreeing with DU), and write protected, will
- be very helpful. DU will be useful to check the configuration parameters,
- located at label "info". (this is the run-time memory address returned by
- the RSX system for parameter = 1. READ THE RSX DOCUMENTATION).
-
- The non-cpm standard values specified in the "info" data are:
-
- hstblk number of CPM sectors per physical sector. 1, 2, 4 or 8
- modrv Which drive to alter. 0 is A, 1 is B, etc.
- dskod Handy coding for controller to select that disk
- chgsid Handy value for configuring side change commands
- sec1st How is the first physical sector labelled. Some systems
- start at 1, others at 0. This is not the CPM sector,
- but has to do with how the disk is formatted.
- invert boolean allowing for controller inversion of data bits
- config a strategy for converting "host" addresses from the
- Digital Research deblocking algorithm into actual
- physical addresses on the 2 sides of the disk.
- ntrks How many physical tracks on 1 side of a disk
- nsecs A constant that allows modification of the physical
- sector address on side 1. Used with config.
-
- As this program is used I hope more useful configuration values will
- appear, and possibly "include" files to configure the host driver to
- various machines. This documentation needs clarification also, but at
- least it is a start. You will need to read the source to adapt to machines
- other than Kaypro. Kaypro users should only need to alter the "info"
- vector to read any disk (except Apples, which are a world to themselves).
- BE WARNED: later version Kaypro's use at least a different port for system
- control (bitpt), interchange drive select codes, and invert the sense of
- several bits (motor on, side select).
-
- I suggest that when first adapting this program to other hosts, you set the
- "driver" equate to false. This will allow the program to load in a non-
- standard CPM environment (such as under DDT), but will prevent the BDOS
- ever accessing the revised drivers. However the system can then be
- exercized by DU, which performs direct BIOS access via the pointer at (1),
- and will thus use the test system. IN THIS CASE BE CAREFUL NOT TO ACCESS
- THE TEST DRIVE THROUGH BDOS, e.g. by DIR, STAT, logins, or other such. USE
- WRITE PROTECTED DISKS. At the same time try to set the default
- configuration to your own machine. Once DSKDRIVE can read and write your
- own disks the rest will be easy. If your system cannot handle double sided
- disk you are severely handicapped in the formats available to you.
-
- The driver system can also serve as a model for native code drivers for any
- machine.
- Q
-