IMS CPM Impl Guide pdf

IMS _{INTERNATIONAL}

CP/M 2.2 IMPLEMENTATION GUIDE

For the Series 5000 _{and Series} 8000 _systems

ineluding the hard disk sub-system

Revision 1.2

july

_I,

1981

IMS _{International} 2800 _Lockheed Way

Carson City, Nevada 89701

This doeum ent applies _{to the}

_f

_{ollowing software produet revisions:}

BIOS 2.23

COPY 2.3

CPMPAT 2.1

DSKTEST 2.1

FORMAT 2.2

IMSGEN 2.1

TRANSI4 (LO)*

IJSKTSTHD 1.1

F'ORMATHD 2.0

HDBOOT (1.0) '

IMSGENHD 2.0

TABLE OF _CONTENTS

1.0 CP/M 2.2 IMPLEMENTATION _{. . . .}

_I

1.1 _Diskette systems

. . . _{. . . . .} . _{. . . .} . . _{. . . .}

I

1.2 Hard disk systems

. . . , . . . . 3

2.0 CP/M START-UP PROCEDURE _{. . . .} . _{. . .} . _{. . . . .} 5

2.1 _Diskette CP/M system _start-up

. . . 5 2.2 Hard disk CP/IVi system _start-up

. . . _{. . . .} . _{. .} l3

3.0 SYSTEM _{UTILITY PROGRAMS}

. . . _{. . . .} . _{. . . .} 7

3.1 General _purpose

_utility

_programs

. . . _{. . . .} 7

3.1.(1 _BAUD

. . . _{. . . , . . . .} 7

3.1.1 MEMTEST

. . . _{. . . . .} . _{. . . .} 7

3.1.2 TRANS14

. . _{. . . .} . _{. .} . _{. . . .} 7

3.1.3 _cpNipAT

. . . _{. . . .} 8

3.2 _Diskette system

_utility

programs _{. . . .} . _{. . .} 9

3.2.0 FORMAT

. . . _{. . . .} 9

3.2.1 COPY

. . . _{. . . .} . _{. . . .} 10

3.2.2 DSKTE<<T

. . . _{. . . .} 11

3.2.3 IMSGEN

. . . 11 3.3 Hard disk system

_utility

_programs.

. . . 11

3.3.0 _FORMATHD

. . . , . . .

II

3.3.1 DSKTSTHD

. . . 13 3.3.2 HDBOOT

. . . 14 3.3.3 IMSGENHD

. . . _{. .} . _{. . .} 15

4.0 THE BIOS _{. . . .} 17 4.1 Console and _{list device routines.}

. . . 17 4.2 CP/IYI BIOS _{for diskette .}

. . . 17 4.2.0 Series 5000

. . . 18

4.2.1 Series 8000

. . . _{. . . .} 18

4.3 CP/M BIOS _for hard disk

. . . 19

5.0 SYSTEM _{GENERATION USING} MOVCPM

. . . 21 5.1 _Diskette system _generation

. . _{. . . .} 21

5.2 Hard disk system _generation.

. . . _{. . . .} . _{. . . .} 21

6.0 SECOND LEVEL SYSTEM _GENERATION

. . . _{. . . .} 23

APPENDIX A _{. . . .} . _{. . . .} . _{. . . .} 29

APPENDIX B

. . . _{. . .} . _{. . .} . _{. . . .} . _{. . . . .} . _{. .} 31

APPENDIX C

. . . _{. . . .} 33

1.0 CP/M 2.2 _{IMPLEMENTATION}

The IMS _{International implementation of} CP/M 2.2 _{for the} Series 5000 and Series 8000

ineludes the support of a CMD hard disk sub-system and _{extended aeeessiiig}

eapábilities for double-density and double-sided _diskettes. 1.1 _{Diskette systems}

The Series 5000 _{will support two diskette}

_f

_{orm ats:} Single-sided, _{double-density}

Double-sided, _{double-density} 5" _{single-density}

_f

_{orin ats are not} supported.

The Series 8000 _{will support three diskette formats:} Single-sided, _{single-dewity}

Single-sided, _{double-density} Double-sided, _{double-density}

8" double-sided _{single-density} form at is _not supported.

Note that the system must contain double-sided drives to support double-sided form ats.

In diskette based CP/M systems, _{the operating} system is designed _{to reside on the first}

two tracks of a double-density diskette. The diskette may also be double-sided.

The storage and _{directory eapacities for the} Series 5000 and Series 8uóÜ _diskette form ats _are:

diskette

_total

directory min. block

f

orín at storage entries size

SERIES 5000

double-density 152 kb 64 1 _kb

double-sided 3C4 kb 64 2 _kb

SERIES 8000

single-density 243 kb 64 1 _kb

double-density 486 kb 128 2 _kb

dcuble-sided 972 kb 256 4 kb

The BIGS _{automatieally} determines _{the diskette format} in _{its first aeeess to a drive.}

If

after aeeessing _{a drive,}

_it

is desired _to cmange the diskette format in that cirive, _a

warm bcot (control-C) must be _{executed. For} example,

_if

_{a single-density diskette} was

first

aeeessed _in a drive, and

_it

_was desired _{to replaee}

_it

_{with a double-density}

diskette, a warm bcot would be _required.

In the IMS Series 8000 system, _{single-density formats are fully compatible in ciirectory}

structure between CP/M versions 1.4 and _{2.2. Double-density} and double-sided

formats, however, have differenees in directory structure. Under CP/N! 2.2, a

direetory entry earí control multiple 16K extents, whieh reduces _directory searching and speeds _{up the system. Double-density files created} under CP/Nl 1.4 _{that are}

greater than 16K _{bytes in length will yield two directory listings for} single-sided

diskettes and _{four listings for double-sided diskettes.} A

_utility

_{program ealled} TRANS14 is ineluded _on the CP/M 2.2 _{diskette to} allow _one disk _{drive to} be seleeted

for reading and _writing using _the CP/Ni 1.4 _{directory structure} (TRANS14 _will be be diseussed _{in more detail later).}

In the Series 5000 system, _{no ineompatibilities exist between} CP/M 1.4 and CP/M 2.2 (double-sided _{formats were not} supported _under CP/M 1.4).

PIP and STAT have ehanged _for CP/M 2.2 and _care should be _{taken to use the} new versions _with CP/M 2.2.

Series 5000 _{añcl Series} 8000 _{both use 256-byte sectors.} To _support reading and

writing of l28-byte kgieal records, seetors _are blocked and debloeked _in the BIOS. A _{256-byte buffer} is _{maintained in the} BIOS _{for this} purpose. To insure thát records

written to this buffer _{are written} to diskette, open files must be elcsed before a

diskette may be removed. Applications programs should always _{ekse files before}

terrninatirg.

The IMS CP/M _{contains a BDOS modification tc} handle _errors. When _{a disk error} is

encountered, a BIOS _error message

will

be _{given, followed} by a BDOS message.

Typing a _{return will ignore the error} and _{continue, while typing eontrol-C will} warm

boot the system and _{leave drive} A _seleeted.

_If

_{an attempt} is mad€ _{to aeeess a drive}

whieh is _{not on the} system, _or

_if

_{durirg the first} aeeess to a drive the BIOS cannot

read the diskette, a BDOS _{select error} is _{given. Typing} any key _{will perform} a warm

boot and _{leave drive} A _{seleeted. Onee the} BIOS has accessed _{a drive} and _the

diskette format is _{determined, attempting to access the drive with the diskette} removed _{will produce a "DRIVE x} NOT _READY" message on the eonsole (where x is

the drive number e _to 3 _{corresponding to the} CP/M devices A _to D).

_If

_{the diskette}

is re-inserted, the BIOS _{will sense drive ready} and _{continue without user interaction.}

Typing any key will perform a warm boot and leave drive A selected.

Parity _error detection for the 64k dynamic _memory board _is included _in the BIOS. When _{a parity error} is _{detected, all cf memory} is _{re-initialized,} the _{parity error} is

reset, eurrent console

_activity

is _interrupted, and _the message "PARITY ERROR,

IGNORE?" is _{printed on} the console.

_If

_"Y" is typed, _{the interrupted} program will

continue.

_If

any other key is typed, a warm boot is performed. Note that

if

the

error oeeurred within the BIOS, a warm boot may not be suffieient to restore the system. A _{cold boot,} however, _{will reload the entire operating} system.

1.2 Hard disk systems

A _hard disk sub-system _may be added _{to a Series} 5000 system _{or a Series} 8000 system. A _{hard disk based operating} system is _{included which} is designed _to reside _on the

removable eartridge of the hard disk. Hard disk _{drives are referred to} by _their

unformatted storage eapaeities (32, 64, and 96 megabytes). _{All contain one} removable

eartridge of 16 _{megabytes, plus fixed storage of} 16, 48, _or 80 megabytes. _The

eartridge is _{referred to as Volume} O _{and the fixed storage as Volume 1.}

In hard disk systems, _{multiple lcgieal} devices _are used _{to name the drive.} Devices A and B are on the cartridge while the fixed storage eontains deviees C through _L.

The BIOS _{for a hard disk system} is _{upward eompatible with diskette} systems.

Diskette formats deseribed above and _{a maximum of four diskette drives are} supported

by the BIOS. _{The four diskette device names direetly follcw the} hard disk deviee names. After initial system _loading and _{execution, driver initialization} is _performed

tc determine the size of the hard disk and _{name the} hard disk and chskette devices. A _{list of device names} is _{printed on the} console _{after the sign-on} message.

The hard disk system _{uses a 512-byte seetcr format which} is _blocked and deblccked

similar to double-density diskettes. The _{buffer for the} hard disk is _loeated on the

controller. Access to this buffer is _{via a DMA} ehannel _{on the diskette controller}

board. The same rules apply as for double-density diskette systems to insure that

buffers _{are written} to disk. Caution should be used when enanging hard disk

cartridges. To be safe, _{cold boct the} system whenever _{a new eartridge} is _inserted. The CP/IVí _{kgieal device names vary with drive size as follows:}

hard disk size cartridge fixed diskette drives

32 megabyte A and B C and D E _thru E

64 megabyte A and B C _thru H _{I thru} L

96 megabyte A and B C _thru L M _thru P

Hard disk _{device eapaeities vary} irt size _{as shown} by this _table:

hard disk

_total

directory min. block

device storage entries size

A 6560 kb 512 8 _kb

C,E,G,I,K 6576 kb 512 8 _kb

B,D,F,H,J,L 6592 kb 512 8 _kb

BDOS and BIOS _{error messages are} as deseribed for diskette systems.

CP/M 2.2 Implementation Guide Rev 1.2 81JULO1

2.0 CP/M START-UP PROCEDURE

2.1 Diskette CP/M system start-up

The _{initial start-up of a CP/M diskette} system consists _{of the following:}

1. _{Conneet any} 9600 baud CRT _terminal whieh _{requires no special} hand-shaking _to

the ehannel 1

serial port.

2. _{Apply power to the} system and _the CRT.

3. _{Insert a double-density} CP/NI 2.2 _{diskette in arive} A _{(the left-mast} cirive). The

diskette should be _{inserted with the label faeing right} and _{entering the diskette}

' drive last.

4. _{Close the} door _{of the drive. Loadirg of the} system should _{oegin immediately with}

the drive activity light on and the sound _{of the} head _{loading onto the diskette.}

For CP/M 2.2 _{the standard IPL} ROM does _{not prompt before system} load (See

Appendix C). The system should sign _{on with:} IMS _{International}

64K CP/M _ver 2.2n

Series 5000 _(or Series 8000)

If

the sign-on message does not appear perform the following eheeks: 1. _{Verify that the terminal} eable eonneeticns _{are eorrect.}

2. _{Verify that the terminal cable} eonneetors are seeurely attached. 3. _{Verify that the} eonsole is _{properly configured.}

4. _{Verify that the I/O} board _to DB-25 _{eonneetor cable} is _{in place} and _that UARTO signals _are going _to Channel 1.

5. _{Verify that the vector interrupts on the diskette eontroller} are properly shunted (see _Appendix A).

Retry the IPL procedure deseribed above.

_If

_no cK:_{ivé aetivity}

oeeurs, a double-sided

diskette may be mounted in _{a single-sided drive.}

_If

_there is _{drive activity but the} head unloads _within one seeond, then one of the following probíems may exist:

1. The _{diskette in drive A is a single-density diskette.}

2. The _{diskette in} cirive A does not _contain CP/M _{on the} system _traeks. 3. A _diskette read _error oeeurred _{while loading} the CP/M system.

Series 8000 _diskette based CP/NI systems _are supplied _{on a double-density, single-sided}

diskette which will lcad and _{run on single-sided or} double-sided _{drives. The standard} system _diskette is _{configured to leave the default IPL} ROM _drive step _{rate of} 6

ms unchanged. In systems _with double-sided _{drives, the} step _rare should _{be emng«1 to}

lessen drive noise during stepping. Read about CPMPAT _{in the}

_utility

programs

seetion and pateh NIOVCPM _{to reset the drive} step _rate.

2.2 Hard disk CP/M system start-up

Sinee _{all software for the hard} disk is supplied _{on a 3" or} 8" _{double-density diskette,}

it

is _{necessary to perform drive initialization} procedures _{to build a hard} disk system and _{write the} system _{to a cartridge. The} hard disk sutr-system _{diskette contains the}

programs and _{files required. Ekgin first by reading this entire} doeument and _bringing up a diskette based CP/M system. _This system is used _{to initialize hard dkks} and

provide back-up in ease of hard disk _{failure. After} this is done, _{verify that the} hard

disk eontroller is _{in the} system and _{connect the} eábles _{to the drive. Apply power to}

the drive, insert a cartridge, and presq the start button on the drive front panel. A

list of steps for initialization of _{the hard} disk _follows:

1. Use _{the hard} disk _{formatting progran} FORMATHD _{to format all} deviees _on the

drive. Eaeh _{device will take} about 10 minutes _{to format.}

2. Use _{the hard disk} CP/Nl _reloeator MOVCPMHD (described _{below) to build} the

largest system _{that will}

_fit

in _{your memory eonfiguration.} Leave _{the new} system

in memory. DO NOT run any program except IMSGENFJD.

3. Use _IMSGENHD (described _{below) to write the} system _from memory to the hard disk _cartridge.

4. _{There are two ways to perform an IPL of a hard} disk _operating system. The _first is _{to run the} HDBOOT _{prcgrarrí from a diskette} based CP/NI system. HDBOOT

will

load and _{execute the} CP/IVi system on the hard disk earrridge. The seeond

requires the latest revision of the IPL ROM (see _Appendix C). This ROM _will

boot the system _{directly from the cartridge.} Simply _{press reset on the computer}

or perform a _power ort _sequence. When using the IPL RON!, make sure that

diskette drive O _{is open}

or the IPL ROM will attempt to load from the diskette. 5. _{Depending on the} size _{of the} hard disk, _{diskette device names will} begin _at E, I,

or NI.

All

deviee names are listed on the eonsole when the hard disk system

signs cm. Onee _{the device} names _{are known,} use PIP to transfer files from

diskette to the hard disk devices.

The hard disk based CP/M system _{initialization} has now been completed. To initialize a new eartridge, format only hard disk devices A and B according to Step 1. To

write a system to the cartridge, perform Steps 2 _through 5

.

The standard _{distribution version of} MOVCPMHD has _{a diskette drive} step _{rate of} 6

ms. Use CPMPAT to patch MOVCPMHI) and reset the diskette drive step _{rare to the}

correct value for your drives (see CPMPAT below).

3.0 SYSTEM _{UTILITY PROGRAMS}

Digital Research _{transient programs are} described _{in the} manual _{"An Introduetion to}

CP/N Features and _{Faeilities". This seeticn} explains the _{use of} IMS

_utility

_prcgrams

provided with the system. N!OSt _gf these programs are unique to INiS hardware, and

will

not run on other implementations of CP/M. Souree _{files for some of} these

programs are provided on the system _diskette. They _may be assembled _with the _Digital Eeseareh MAC _maero assembler.

3.1 _{General purpose}

_utility

_programs

These _{programs are} designed _{for use with both diskette} and hard disk CP/NI systems.

3.1.0 BAUD

-

Set printer baud rate

The BAUD program will temporarily set _{the printer port to the} baud _{rate specified iri}

the command _line. BAUD _{will only accept the rates} 110, 150, 300, 600, 1200, 4800, &nd 96CO _{unless the rate} is preeeeded _{by an} "@" _{eharaeter, in which ease any rare}

between 110 and 96CC may be entered. Rates _{other than the speeified} values _may

not be precise Cue _to rounding by _{the divider eireuit} whieh _{generates eloek} pulses _for

the UARTS. The _new baud _{rate on the printer port will} be _{in effect until BAUD} is

run again or the IPL ROM (cold _boot) is _executed. Warm boots _{will not affect the}

printer tutud _rate.

3.1.1 MEMTEST

_-

Memory test

_utility

This

_{utililty will}

perform a one pass test on system memory from approximately

address 300 hex _{te the} begirming _{of the} BIOS. No _parameters are required. Once

loaded, MEMTE£T _will begin _{testing. After one complete test of memory, a reboot} of

the system is performed. Errors _{are displayed} with _{the memory} address _first,

followed by the bytes written and read _{at that loeation. If multiple} memory _errors

occur, control-S may be used _{to stop the display. TM} eonsole is ehecked _for a

ccntrol-C break eharaeter. 3.1.2 TRANS14

-

Translate CP/M 1.4 double-density

TRANS14 is a self-relocating program that will allow a diskette with 1.4 directory

strueture to be used _{on one drive.} The _drive name is speeified when _the prcgram is

called by _entering a valid drive name (A:, B:, C:) after the prcgram name: TRANS14 B: _{<er>. The eurrent drive may not} be _{specified. If the eurrent cirive} is named, _the message "Drive name error" is printed on the console. Onee a drive is set for 1.4

eornpatibility, double-density 1.4 _{diskettes may} be aeeessed _{with any of the} system

utilities or application programs.

CP/M 2.2 _{Implementation Guide Rev 1.2 81JULO1}

TRANS14 loc ates _itself below the CCP and changes _the BDOS _entry address _{to itself,}

to prevent other programs from overwriting TRANS14. TRANS14 _{will trap warm} boots and _{print out} the _message:

(Trans14 _active)

(Drive n set for CP/M 1.4 _{eompatibility)}

where n stands for the drive speeified when TRANS14 _{was ealled.} The _{warm boot} is

then allowed to preeeed, so diskettes may be ehanged without running TRANS1A

again.

_If

TRANS14 is _{run while the} module is _{aetive in memory,}

_it

_{will elear itself}

from memory. All drives will then be assumed _to have 2.2 _{direetory structure. After}

clearing, the _message:

Trans14 eleared, system _restored

will

be _{printed on the} eonsole. TRANS14.ASM is the _{source file for this prcgram. It} is _{prcvided for reference} only, sinee _{the programs} needed _{to generate} TRANS14 _are not inelud ed.

3.1.3 CPMPAT

_-

Patch

_{utility for}

MOVCPM

CPMPAT will make _{limited modificatiors to the} BIOS _{without a second level} system

generation. CPMPAT allows _{the user to examine} and _{alter the drive} step _rate,

eonsole and

_list

_deviee baud _rates, and enable _or disable handshaking _with the _list

deviee. CPMPAT _{informs the user of the} ehange

_it

is ready _{to perform,} displays _the

opticns allowed and _{the eurrent} value, and ásk< _for a new value. Typing only a <cr>

(carriage return) to any input request will retain the current value. The last prompt asks

_if

_{all changes are ecrreet; typing a "Y" will update} MOVCPM _{with the new} changes.

CPMPAT will only pateh versions _of MOVCPll/l whieh _{contain the current} BIOS.

_It

_will

verify

this and print a TABLE ERROR message

if

the BIOS is _{not current.}

Information about the table is in _{the souree of the} BIOS. To _eall CPMPAT _from CP/M, _use the _format:

A>CPMPAT filename.typ <er>

where "filename.typ" is _{the name of the} MOVCPM _{prcgram which will} be patched. _It je _{suggested that a eopy of} MOVCPM be patehed _{te allow recovery from the original}

in ease _{of error.}

CPMPAT _may also be used _{on the reloeator for} hard disk systems, _ealled N!OVCPN!HD. N _{ote that} CPMPAT only changes _the BIOS _{contained in the} MOVCPM _program, and _not

the system _{on traeks} O _and 1

or the system in memory. A system must be generated

with N!OVCPN! _{to integrate} these changes. CPMPAT.ASM is _{the source file fcr this} program.

3.2 _{Diskette system}

_utility

programs

These programs all contain drivers for IMS _{diskette controllers. They are} used _for

formatting, copying, and _{media validation. The source files for} these _programs

contain the conditional assembly _switeh MINI. When set TRUE, _{the file will} assemble

& Series 5000 version (5" eontroller). _{With MINI set FALSE, a Series 8000 version will}

be _generated (8" _controller).

Although the current release of the BIOS _{for diskette} systems _{uses interrupts} t"or

diskette routines, all these

_utilities

disable processor interrupts and use polling.

Af ter returning to CP/Nl _{via a warm boot, processor interrupts are re-enabled by the}

first diskette command.

3.2.0 FORMAT

_-

Diskette Formatting

_Utility

This program is used to initialize diskettes to be used _{with the} IMS CP/N! 2.2 system.

It

should be used _{on new diskettes to insure their eompatibility with the} system.

_It

m ay be used to reformat diskettes whieh produce _errors. FORMAT _{destroys all data}

on the diskette, so _{proper eare} should be _{taken to recover daIa before reformatting.}

There are two versions _of the FORMAT program, one for Series 5000 formats and one

for Series 8(100 _formats. The _{following tables} deseribe supported _formats:

5" DISKETTE FORMATS

Single-sided Double-sided

40 Traeks 40 _Traeks/side

Double- 16 _{Seetors/Traek} 16 _{Seetors/Track}

density 256 _Bytes/Seetor 256 Bytes/Seetor

8" DISKETTE FORMATS

Single-sided Double-sided

Single- 77 _Tracks

density 26 Seetors/Track

128 _Bytes/Seetor

Double- 77 _Tracks 77 _Traeks/Side

density 26 Seetors/Track 26 _{Seetors/Traek}

256 _Bytes/Seetor 256 _Bytes/Seetor

FORMAT

_first

prompts for a drive name (A through D). The diskette should be

inserted into the drive in whieh

_it

is _to be _{formatted. The} Series 8UOO _{version will}

issue a density prompt

if

a single-sided diskette was inserted. The Series 5000

version will issue _{a side prompt}

_if

_the system has double-sided _drives. Both versions

provide an abort prompt, then begin formatting. During the format process, eaeh

track is _{read verified after}

_it

is _formatted. The keyboard _{is eheeked for a eontrol-C}

eharaeter.

CP/M 2.2 _{Implementation Guide Rev 1.2 81JULO1}

The followirg example shows _{an exeeution of} FORMAT _{on drive} B _{of a Series} 8000 system:

A>FORMAT <er>

INIS _{International}

8" Disk _{Format Utility Versicn} 2.2

Type disk _{(A-D) to formd or return to reboot} B _<er> Single _or Double _density (S/D)? D _<cr>

Format will destroy all data on disk B

Press EETURN _{to eontinue or CONTROL-C to abort <cr>}

After formatting is completed, FORMAT _will again ask _{for a drive name. Type return}

to reboot CP/N. FORMAT _{will abort after an error} and _{return to the drive name}

prompt. Drive A is always _{selected after program termination.} FORMAT.ASM is _the source file for this prcgram.

3.2.1 COPY

-

Diskette Copy

Utility

COPY is used _to make _{a track for track direct copy from one diskette to another.}

The diskettes must have _{the same format or} COPY _{will output} a format error and

terminate. COPY accepts _three commands: _{ALL, DATA, or} SYSTEM. COPY _ALL

copies the _entire disk _(tracks O-39 _for the Series 5000 and _traeks O-76 _for the Series

8000). COPY DATA eopies _{the direetory} and _{data areas (tracks} 2-39 _{for ttie} Series 5000 and _tracks 2-76 _for the Series 8000). COPY SYSTEM _{will transfer the first two}

tracks of the diskette which contain the CP/M 2.2 _operating system. Sourc e and

destination drives (A _{thru D) may be specified after the copy} command _{in the format}

"destimtion=soure e". CCPY _{will default to "B=A", that} is, souree on arive A and

destination on drive B. COPY _prcvides read _verifieation unless _the eommand _line is

followed by a "/" eharaeter to disable this mode.

COPY is _called from _the eommand _{level of} CP/NÍ by _entering: COPY eommand [destination=souree] _[/]

([]=optional)

COPY vvill _{print the source} and _{destination drive names, follcwed by an abort prompt}

which accepts a eontrol-C to return to CP/M. _Diskettes should be placed _{into the}

source and destination drives at _{this time. Type} EETURN _{to start the} COPY. _Anv

pair of

_like

format diskettes may be placed into the drives even

if

a different format was previously copied.

Errors _{whieh occur during eopying are printed} on the eonsole with the message

"ignore?".

_If

a "Y" is typed, COPY _{will continue.}

_If

any other key is typed, CCPY

will

terminate and _{return to CP/M. The keyboard is eheeked for} a eontrol-C

eharaeter.

_After

_{the eopy} is _{complete, a prompt} is issued _with the options _of

repeating _{the copy or returning} to CP/M. CCPY.ASM is _{the source file for this} program.

3.2.2 DSKTEST

_-

Drive/Media Verif ieation

_Utility

DSKTEST is used _{to verify the readability of} each _{sector on a diskette.}

_It

does _not

write on the diskette. DSKTEST is _{self promptiríg} and _{requires no parameters.}

There is _{an optional} long seek mode _in whieh _{a seek to the last traek} is _performed

before traeks O-middle are read, and _{a seek to track} O _{is performed before tracks}

middle-last are read.

_If

_{an unreadable sector} is eneoímtered, _{a disk error} message is

printed first, followed by the track number, head number (if double-sided), and _sector number _{of the error.} The eonsole is ehecked

_f

_{or a control-C eharaeter} during _testing. DSKTEST.ASM is the _{source file for this program.}

3.2.3 IMSGEN

-

Diskette system generation

utility

IMSGEN is _funetionally iCíentieal _{to the Digital} Researeh SYSGEN _{program, with the} added _{eapability of} aceessing _{double-density diskettes.} With _{this prcgram,} systems m ay be brought into memory from double-density, sirgle- or double-sided diskettes,

and _{then written to any format diskette. Single-density diskettes are a special ease}

in that only a partial system _ean be _{written on the operating} system _{tracks. This} may be done to allow a single-density diskette to be placed in drive A after IPL from

a double-density diskette, but only _warm boots _are allowed _{after this.} IPL must b e done from _{a double-density diskette.} IMSGEN.ASM is _{the scuree file for this program.}

3.3 Hard disk system

_utility

_programs

These _utility programs all eontííin driver software fcr the hard disk _eontrcller. They

are used to format the drive, boot CP/M, test the hard disk system, and eopy the

operating system.

Although the eurrent release of the BIOS uses interrupts t"or hard disk _routines, these

utility

programs disable interrupts and use pollirg. After the prcgram terminates, proeessor interrupts are re-enabled by the first disk command.

3.3.0 FORMATHD

_-

Hard disk format

_utility

FORMATED is _{the format program for the hard} disk. _The IMS hard disk _controller is

hard-sectored. An B-byte header is _maintained at _{the b€ginnirg of} eaeh _512-byte

seetor, making the tc:_tal number _{of bytes per sector} 520. _{This program} must tje _run

to

_initialize

eaeh _{sector on the drive.} When _{the drive} is _{brought up for the first}

tim e, all devices must be formatted. When using new cartridges, only devices A and B need be _formatted.

CP/lVí 2.2 _{supports a logical storage device with a maximum} size _of 8 _megabytes.

Sinee the eartridge and each surfaee _{of the fixed} media have _roughly 13 megabytes _of

f

orm atted storage capacity, multiple CP/M devices must be defined on the drive. The

cartridge, with a single surf aee, contains the CP/M operating system on track O.

CP/M logical devices A and B _{are on the cartridge.} Each _fixed media _surface

eontains a pair of CP/N! lcgieal devices, beginning with C and D and, depending upon

the size of the drive, extending through device L. This will permit at _{least tour} CP/M _diskette devices.

CP/M 2.2 _{Implementation Guide Rev 1.2 81JULO1}

The _{lcgieal to physical} mapping _of CP/IVí deviees _follows:

CP/M device media head surface tracks

A _cart O _* O

thru 410

B _cart O

* 411 _thru 822

C _fixed (I 1 O

thru 410

D _fixed O

I

411 _thru 822

(32 megabyte _drive ends here)

E _fixed 1 2 C _{thru 410}

F _fixed 1 2 _{411 thru 822}

G _fixed 2 3 O _{thru 410}

H _fixed 2 3 _{411 thru 822}

(64 megabyte _drive ends here)

I _fixed 3 ₄ O _{thru 410}

J _fixed 3 _{4 411}

thru 822

K _fixed 4 5 O _{thru 41U}

L _fixed 4 5 _{411 thru 822}

(96 _{megabyte drive ends} here)

*Surfaee identifiers are used with the fixed media only.

FORMATHD first determines the size of the drive, prir2ting _{on the} eonsole _{the lcgieal}

device names and _{their lceations.} The _user is then asked

_if

_instructions are desired.

Next, FCRMATHI) will ask _{which device to format. Note that in the event that a}

portion of the drive becomes unusable, _{only one lcgieal device} need be _reformatted.

After

the device name is entered, the corresponding _{physieal parameters are listed.}

An abort prompt is _{then given.} Type _{"Y" to continue,} or "N" to abort. Form _atting

will

take about 10 minutes _per deviee. Bad _traeks found _{by the prcgrarn are listed on}

the eonsole. After the logical deviee has been _{formatted, the user will} be asked _to

input known bad _{tracks that were not detected by} FORMATHD. _{Enter the list} of bad

tracks provided by _{the drive manufacturer. This list will refer to the} bad _traek by

track and _{surface number. Note that the} bad _{track input prompt} is _given when

formatting eartridges, although _they should _{not contain} bad _traeks.

_If

bad _traeks are

found by the program or entered by the user, FORMATHD

will

create dummy

directory entries to pre-allocate those _tracks. In normal CP/M _{operation the} system

will not _{attempt to use} those _tracks.

FCRNÍATFID _{will terminate on these errors:} 1. _{Drive I/O errors (except READ)}

-

Errors in writing, seeking, or seleeting heads are defined as I/O errors.

2. Bad _{direetory track}

-

Due to the method of handling bad tracks, the directory

track can not be bad. 3. Bad system _traek

-

This error occurs only on the cartridge. 4. More _than 128 bad _traeks

-

A drive with 128 bad traeks should no longer be used.

During device formatting, FORMATHD monitors the console _{for a eontrol-C eharaeter.}

If

typed, _the prcgram will ask _the user to verify that the prcgram should be _aborted.

Type a "Y" to eontinue formatting. In _{this way, users may verify that} FCRNIATHD is

running.

Due to the destructive nature of formatting, FORMATHD should be used _{with eaution.} FCRMATHD.ASIV! is _{the souree file for this program.}

3.3.1 DSKTSTHD

_-

Hard disk test

_utility

DSKTSTHD is a sereen-oriented test

_utility

for the hard disk _eontroller and _drive. A

help menu can be viewed by typing "HELP". Do _{not use the formatting} eommand _of DSKTSTHD. Use FORMATHD _{to format the} hard disk.

The _terminal dependent _portion of DSKTSTHIJ is _{in one area} of _{the program.}

_It

_may

be altered using _{the terminal} dependent _{area seuree file} HDTDA.ASN!. To _{charge the}

terminal dependent routiríes, edit and re-assemble HDTDA.ASM _{for your terminal.}

Integrate the new HDTDA.HEX file into DSKTSTKD _{as follows:}

A>DDT DSKTSTHD.COM <er> ; initiate DDT DDT VERS 2.2

NEXT PC 3800 0101)

-IHDTDA.HEX <er> ; initialize FCB

-R <er> ; overlay new drivers

NEXT PC 3800 OCOO

-GO _{<cr> ; exit} DDT

A>SAVE 55 _{DSKTSTHD.COM <cr>} ; _save modified _program

DSKTSTHD.ASM is _{the souree}

_file

_{for this prcgram. HDT.LIB} is _{a maero library}

ealled durirg assembly.

CP/M 2.2 _{Implementation Guide Rev 1.2 81JULO1}

3.3.2 HDBOOT

-

Hard disk CP/M boot loader

HDBOOT is _{a seeondary IPL for the hard} disk system. _{It was written to} be used _in

two ways. Assuming that a cartridge has been formatted and a CP/NI system written to the

_first

track, HI)BOCT _may be _{run direetjy} from _{the diskette} based CP/M

system as a transient program.

_It

will load and exeeute _the CP/M system _{from the} eartridge. This is useful for running the system _{the first time.} HDBOOT _may also be _{written to} the _{first two traeks of a diskette.} When _{a diskette} prepared _{in this} m anner is booted, HDBOCT is read and executed instead _{of a CP/N!} system. HDBOOT

will then load and _execute the CP/N! system _{from the cartridge.} (Since _{the current}

IPL ROM _{eontains a hard disk loader, using HDBOOT on a diskette would} be

redundant.)

To _{write the} HDBOCT program to the first two traeks of a double-density diskette

while running _{a diskette} based CP/M system, perform the following steps:

A>DDT HDBOOT.COM <er> ; use DDT to read RDBOQT DDT VERS 2.2

NEXT PC 2000 0100 -GO _<er>

A>IMSGEN _{<cr> ; now} read IMSGEN INS _{Internaticnál}

8" Sysgen Version 2.1

Type souree drive name (or returíí to skip) <cr>

Type _{destinaticn drive} name (or return to reboot) B <cr>

Destination on B, type return to continue <cr>

Double-density function eomplete

Type _{destinaticn drive} name (or return to reboot) <er>

Place this diskette in drive A and _{press reset to} load CP/Ni _{from the} hard disk. HDBOOT.ASM is _{the source file for this} program.

3.3.3 IMSGENHD

-

Hard disk system generation

utility

IMSGENHD is used _{to write an operating} system _{to the} hard disk.

_It

ean also be used

to read an operating system from _{the hard} disk and _place

_it

_{in memory.} INISGENHD

requirec no parameters wherí ealled from CP/M.

To _{build a 64K} system _with MOVCPMHD and _write

_it

_to a eartriccge with IMSGENHD:

A>MOVCPMHD 64 _{* <er> ; build a 64K} system and _{leave in memory} CCNSTEUCTR"G 64K CP/M _ver 2.2

FOR A _HARD DISK SY"TEM

READY FOR "INISGENHD" OR "SAVE 51 CPMHI)64.COM"

A>IMSGENHD <cr> ; _{run immediately after} NIOVCPMHI) IMS _{International}

Hard Disk System _Generation Program Version 2.0 Load system _from Hard Disk (Y/N)? N _<cr>

Write system _to Hard Disk _{(Y/N)? Y <cr>}

Function eornplete

Write system _to Hard Disk (Y/N)? N _<cr>

To read _the system from _the hard disk and _write

_it

_to a file named TEST.SYS:

A>IMSGENHD <er>

ÍMS _{International}

Hard Disk System _Generation Prcgram Version 2.0 Load system. _from Hard Disk _{(Y/N)? Y <cr>}

Function complete

Write system _to Hard Disk (Y/N)? N _<er>

A>SAVE 51 _{TEST.SYS <cr>}

IMSGENKD.ASM is the _{source file for this} program.

(This _{page irítentionally}

_left

_blank)

4.0 THE BIOS

This seetion deals _{with the} IMS _{International implementation of the} CP/M 2.2 Basic

Input/Output System (BIOS). BIOS.ASN is the _{souree file distributed with} Series 5000 and _Series 8000 systems.

_It

is assumed _{that the reader} has _{a bask} understanding _of

the BIOS, _{as outlined by the Digital} Researeh "CP/Ni 2.2 _Alteration Güide". The NEC uP D765 doeument _will aid _{in understanding the diskette routines.} Doeum _entatiorí

_f

or

the IMS _I/O board _will aid _{in understanding} console and _{list deviee routines. If your}

system ineludes a hard disk, _{the doeumentation for the} hard disk _{controller will} be

useful.

This doeument describes the BIOS _{as supplied by} IMS. _{Previous to the} end _user's

delivery dealers may have altered the BIOS. _{Inform ation} about possible _charges should be requested from _{your dealer.}

One _source

_file

_{is used for the} BIOS. _Conditional assembly _{switches are} used _to

customize the system. These switehes _are described _{in more detail in the section}

titled "Seeond _Level System _Generation". The BIOS _{contains a limited eonfiguration}

table at _the end _{of the} jump _table. This _table is used by _{an initialization routine to}

dynamically set eonsole and

_list

_device baud _{rates, patch the}

_list

_{driver for}

handshaking, and change _{the diskette drive} step _rate. CPMPAT allows _{the user to}

modify the image _{of this table which} is _{eontained in} MOVCPM (see CPNIPAT).

The IMS _{dynamie memory} board _{with parity} is supported by _the BIOS. _{For proper}

reset of parity _{errors the} board should _{be set for I/O} address O _{with the I/O enable}

shunt "on" (see _Appendix A

_f

_{or shunt inform}ation). When _{parity errors} occur, memory

is

_{re-initialized}

and _{the parity error} is _eleared. The _{message "PARITY} ERROR,

IGNORE?" is _{printed on} the console.

_If

_{a "Y"} is typed, _{the interrupted} prcgram is

eontinued.

_If

any other response is typed, the BIOS performs a warm boot. Note

that

_if

the parity _error ceeurred in _the BIOS _{portion of the} system, a warm boot may

not be _{sufficient to reeover} from _{the error.} A _{cold boot} should be _performed.

4.1 Console and

_list

deviee routines

The Model 440 _I/O board (I/OBD) has _{two serial ports} and _{a 24-bit parallel device} (8255) _with addresses _{whieh follow the serial ports.} The standard system does _not use

the parallel device. _{The board ean be assigned base addresses in} 16 address

ineremeríts. For the standard system, 10 hex is _the base address. _{Both serial ports}

have sof tware programmed baud _{rates. They are initially} set _for 9600 and 300 baud

by the IPL ROM, _{whieh assumes that the} 19.2 _{kilobaud oscillator} is _{not present.} The BIOS _{resets the} UARTS during _{initialization, setting the} baud _{rates specified in} the

eonfiguraticn table diseussed above. (See CPMPAT for more information.)

4.2 CP/M BIOS

_for

diskette

IMS _{diskette eontrollers} have a base address _of 80 hex etched _{intc the} boards. _This

base ean be moved _in 16 address inerements, however, _this is _not recommended since

incompatibility

_will

_{occur with} diskette

_utilities

and _{the IPL} ROM. _Diskette

interrupts shculd be shunted _{to vector} 5 _{for proper operation} (see _{Appendix A).}

CP/M 2.2 _{linplementation Guide Rev 1.2 81JULO1}

4.2.0 Series 5000

The Series 5000 BIOS supports _single-sided and double-sided _formats. Both _formats

are double-density, with 256-byte sectors, 16 sectors per track, and 40 _{tracks per}

side. Reading and writing are done from a 256"byte buffer in the BIOS. Eaeh read

or

write

request from BDOS _{results in the transfer of} a 128-byte lcgieal record

between the buffer and _{the eurrent DMA address. Double-sided diskettes are}

buffered in the same way. Each traek orí side two of the diskette is a extensiorí of the same traek on side one. Rather than using a sector interlace tatúe, the SECTRAN _{subroutine in the} BIOS _{ealeulates the interlace for} each disk _aecess.

The 5" disk _{parameter blocks} used _in CP/Ni _{look like this:}

double- double-density

density double-sided

SPT 32 64

BSH 3 ₄

BLM O1Í1B O1111B

EXM O 1

DSM 151 151

DRM 63 63

ALO OCOFI OBOE

ALI O O

CKS 16 16

OFF 2 2

4.2.1 Series 8000

Sirgle-density diskettes are used to transfer files between CP/M systems. When the BIOS is _{in single-density} mode, _{diskette reading} and _writing is done imm _ediately using

the current DMA address. The _{standard Digital} Researeh _{sector interlaee} is used. When _the BIOS je _{in double-density mode, reading} and _{writing are buffered} as deseribed above _for 5" _diskettes.

The 8" disk _parameter bloeks used _for CP/M _{look like this:}

single- double- double-density

density density double-sided

SPT 26 52 1U4

BSH 3 ₄ 5

BLM OI11B 011118 01111113

EXM O

I

3

DSlV! _{242 242 242}

DEM 63 127 255

ALO OCOE OCOR _ocoIí

ALI O O G

CKS 16 32 64

OFF 2 2 2

4.3 CP/M BIOS

_for

hard disk

The IMS _{hard disk eontroller} has a base address _of 90 hex etched _{into the} board.

This base e an Ij€ moved _in 8 _{address increments, however, this is not reeommended}

since ineompatibility _{will occur with} hard disk _utilities and _{the IPL} ROM. Hard disk

controller interrupts should be shunted _{to vector} 5 _{for proper operation} (see _Appendix A).

The Series 5000 _and 8000 hard disk BIOS _{are functionally identical except for diskette}

size. The hard disk devices _are always _{the first} CP/M _lcgieal devices. _{Diskettes are}

the next four logical devices. Warm boots _are always _{from the eartridge} or the first diskette deviee.

The hard disk uses 512-byte sectors with an additional 8 bytes for a header. The

header contains a select code, cylinder number, sector number, and an optional CRC

word. Since _{the controller performs a hardwar€} CRC, the _{optional software} CRC is

not used. The hard disk sector buffer is _located on the eontroller. Reading and

writing is done _{via DNA} channel 2

on the diskette eontrcller. The _hwd disk devices have disk _parameter bloeks _{as follows:}

A C,E,G,I,K B,D,F,H,J,L

SPT 128 128 128

BSH 6 6 6

BLM O111111B O111111B _O11I1I1B

EXM 3 3 3

DSNI 819 821 823

DRM 511 511 511

ALO ocoEí OCOH OCOH

ALI O O O

CKS O Q O

OFF 1 O ₄₁₁

Note that the directory cheek _{veetor size} (CKS) is _{zero for all} hard disk deviees,

including the removable eartridge. This means that the directory integrity of the

cartridge deviees is _{dependent upon the user performing} a system boot when

eartridges are ehanged.

(This _{page intentionally}

_left

_blank)

5.0 SYSTEM _{GENERATION USING} MOVCPM

System _{generations with} MOVCPM and CPMPAT _can change _{the memory} size _of the

operating system, _{re-define the} baud _{rate of the} console _{or list device, switéh to the}

19.2kb oseillator, ehange _{the diskette} step _rate, and do _{limited configuring of the list}

driver. These ehanges _ean be easily implemented _with CPMPAT, _{whieh will aeeess} and _{charge the driver configuration table in} the BIOS (see CPMPAT).

The IMS _{version of} MGVCPM _(or MOVCPMED _for hard disk systems) is _{funetionálly}

identical to MOVCPM _{as deseribed} by _Digital Research _{in "An Introdueticm to} CP/M Features and Fae _ilities". The minimum _{memory size for} & CP/M 2.2 system is 22K. 5.1 _{Diskette system generation}

Before proceeding _further, make _{a copy of the diskette provided by} IMS. Use COPY

ALL to do _this. Plaee _{the original diskette} in _{an arehive file for} backup.

Cold boot from this new diskette. Use CPMPAT to examine and/or mcdify the

eonfiguration table in the BIOS (see CPMPAT). Then _{type the} command: A>MOVCPM _*

_*

_<cr>

This _{will generate the largest} CP/M system _{that will}

_fit

in _{memory. After the} CCP

prompt returns, type in the command: A>IMSGEN _<cr>

IN!SGEN _will ask _{for a source drive name or "Peturn to skip".} Type a return since _the

system is _{already in memory.} IMSGEN _{will then request a destination drive name.}

Type in "A" to write the system _{to diskette.} Now _{reset the computer to start the}

IPL. The system _will sign _{on with the new version} of CP/M. Use INISGEF' _{to eopy}

the system _{from this diskette to} others, _{as desired.} 5.2 _{Hard disk system generation}

The procedure for generating hard disk systems is the _{same as that for diskettes,}

except

_for

the system generation

_utility.

The corresponding programs are

MCVCPMHD and IMSGENHJJ.

Use CPN!PAT _{as described} above _{to customize} MGVCPNÍED. _{Next, run} MOVCPMHD _to

create a CP/M image in memory. Finally, run IMSGENHD.

IMSGENEÍD _will ask _{whether to} load _the system from _{the eartridge. Type "N" to} skip

this proeess, since _the system is _{in memory. Next, the program will} ask _{whether to}

write the memory image to the hard disk cartridge. Type a "Y". When

it

is finished,

IMSGENHD

_will

prirtt "Function complete" and ask _{whether to write a system} c:_n

another eartridge. Type an "N" to return to the operating system. Reset the eornputer _to load and _execute the _new CP/NI system.

(This _{page intentionally}

_left

_blank)

6.0 SECOND _LEVEL SYSTEM _GENERATION

This seetiori is _{a guide for gerteratirg a custom} BIOS _{for use on} IMS systems. _An

understanding of the BIOS is assumed (see _{the Digital} Researeh "CP/M 2.2 _Alteration

Guide"). A second _level system _{generation is necessary to alter the} BIOS _{routines in} any _way. A back-up diskette should _be used _{to test the new} system _before

_it

is

written _{to other diskettes.} Before altering the BIOS, _review the _appropriate seetions

of this document. Note that a second level system generation makes MCVCPM unusable, Qiñéé

_it

_{will not eontain the modified} BIOS _routines. Also, CPMPAT is _no

longer useful, since

_it

cperates _{on MOVCPM.}

Second _level system _generation is _{generally the same for all} versions _of INIS systems.

Differenees will be _{pointed out where they} oeeur.

The _{following files are} needed _{for a second level generation:}

BIQS.ASM _{; BIGS scurce file}

ED.COM ; text editor

ASM.COM _{or MAC.CON! ; CP/M} assembler

DI)T.CCM _{or SID.COM ; debugger}

Additional files needed

_f

_{or diskette} system _{generations include:}

N!OVCP1\/LCCM _{; CP/NI reloeator}

IMSGEN.CONI _{; system} generation

_utility

Corresponding _{files for} hard disk system _{generations are:}

MOVCPMHD.CCM _{; CP/M reloeator}

INISGENHD.COM _{; system generation}

_utility

STEP _{#1: ASSEMBLY} OF _THE BIOS

Using _the CP/M _editor ED (or another _{text editor), edit the} BIOS assembly _switchés described _below.

MSIZE The m aximum memory size which will be used by the system

(range _{= 22 to} 64).

MINI Set TRUE to generate eode for 5" _{diskette drives;} set

FALSE _{to generate} code _for 8" _{diskette drives.}

HDSK Set TRUE _{to generate} code _{for a hard} disk _drive.

AUTO Set _{TRUE to eause} the _{automatic exeeution of a file} named

INIT.SUB after _{power-up or system reset.} INIT.SUB and SUBNIT.COM must be _{present on} deviee _A. INJT.SUB should

eontain the eommand _or eommands _to be exeeuted. (See _the

Digital Research manual _{"An Introdueticn to} CP/M Features and _{Facilities" for more inf ormation} about SUBMIT _files.)

STEP $RATE Set to the number of milliseeonds required to step the

diskette drive track-to-track (range ₌ O _{to 16). Note that}

the 5" _{controller eloek rate} is _one-half the 8" _{controller rate.}

Step rates for 5" _{drives will therefore} be _{twice the value set}

by STEP$RATE.

_If

STEP$RATE is _{set to zero, the rate} remains _{as set} by _{the IPL} ROM.

STEP$RATE 8" Drive 5" Drive Diskette drive Value rate (IllS) _rate (ms) _{recommendation}

1 1 2

2 2 _{4 5" MPI}

3 3 6 _{5" Tandon, 8" Qume}

4 4 8

5 5 ₁₀

6 6 _{12 (IPL RON! default)}

7 7 ₁₄

8 8 ₁₆

9 9 ₁₈

10 10 20 8" Shugart

11 11 22

12 12 24

13 13 26

14 14 28

15 15 30

16 16 32

LIST$DEVICE Set _{to the desired}

_list

_{deviee driver} from _{the table below.}

For drivers using clear to send (CTS), _{deviee buffer status}

must be conneeted to pin 4 _{of the printer port DB-25}

eonneetor.

LIST$DEVICE Printer driver description

TTY Serial

_{driver for}

Teletype 33 and _other

devices _{requiring no riandshaking.}

TIBIO _{Serial driver for} TI81C and _{other devices}

which transmit clear to send (CTS) _{true to}

indieate buffer empty.

NECSER _{Serial driver for} NEC _Spinwriter and _other

deviees whieh transmit dear to send (CT'S)

false to indicate buffer empty.

DIABLO Serial driver

_for

Diablo and _other devices

which _{use ETX/ACK} protoeol to indicate buff er empty.

TTY40 _{Serial driver for Teletype} Model 40. NECPAR _{Parallel driver for} NEC _Spinwriter.

CENTEPAR Pardlel driver for Centronics printer.

CONSOLE$BAUD$RATE

LIST$BAUD$RATE Set each baud _{rate from the table} below (range ₌ O

to 8).

BAUD$RATE Baud

Value Rate Comm _ents

O _{19200 requires 19.2kb oseillator}

I

9600

2 ₄₈₀₀

3 ₂₄₀₀

4 1200

5 ₆₀₀

6 ₃₀₀

7 ₁₅₀

8 _{110 two stop bits provided}

OSC$192K Set TRUE

_if

the 19.2 kilObaud _oscillator is _{installed on the}

I/O board, else FALSE.

The standard INLS _{distribution version of the BIOS has the switches set as follows:}

MSIZE EQU 64 _{; memory size}

MINI EQU _{TRUE/FALSE ; diskette size}

HDSK EQU TR UE/FALSE _{; TRUE}

_if

hard disk

AUTO SET FALSE _{; auto-load}

STEP$RATE EQU O

; diskette drive step rate

LIST$DEVICE EQU NECPAR _{; list device selection}

CONSOLE$BAUD$EATE EQU 1

; 9600 baud console

LISF$BAUD$RATE EQU 6

; 300 baud list deviee

OSC$192K EQU FALSE _{; oscillator not installed}

After

the assembly switches have been set, assemble _the BIOS using the _Digital

Research ASM _or MAC assembler. _{(Note that} ASN! _will produee _{errors on the TITLE} and PAGE _direetives. These _errors may be ignored.)

CP/M 2.2 _{Implementation Guide Rev 1.2 8IJULO1}

STEP _{#2: RELOCATING THE} SYSTEM

Use MCVCPM _(or MOVCPMHD) _{to build a system for the target memory} size. Save

the system on disk:

A>MOVCPM _xx

_*

_{<cr> ; for diskette} systems

-

or

-A>MOVCPMHD xx

*

<cr> ; for hard disk systems

0 @ 0 0

. . . .instructs MOVCPM to leave system in memory

0

. . . _{. memory} size in kilobytes

Follow the instructions given by MOVCPM (or MOVCPMHD) _{to save the memory} image

in a file named CPNÍxx.CCM, where _xx is _{the memory} size.

STEP #3 _{OVERLAYING THE} CUSTOM _BIOS

The next task is _{tc overlay the new} BIQS.HEX _{over the new} CP/M system. _This is done using DDT _{or SID. Type the} command:

A>DDT CPMXX.COM _{<er> ; xx} is _the system _size

DDT

_will

load CPMXX.COM _{into memory} ancl issue _{the prompt}

_""'.

_{Type the next} eommarid _{to DDT:}

-IBIO&HEX <er>

This initializes the DDT _{file control blcck for the new} BIOS _file. The _next step is _to

read in the new BIOS.HEX with the proper bias to plaee

it

over the old BIOS. The

bias differs with memory size. Standard read bias values are listed below, but any

bias may be eomputed by subtracting the absolute address of the BIOS from 1F80 hex. This _computation must _either be done _in hex or converted to hex for use with DDT.

In a 64k Series 8000 system:

The BIOS _will begin at F400 hex. 1F80 hex

-

F400 hex = 2B80 hex (read bias for DDT). In & 64K Series 5000 system:

The BIOS _will begin _at F600 hex. 1F80 hex

- F600 hex = 2980 hex (read bias for DDT).