Motorola EXORdisk II User manual

" ... "
~
,
:.,j
, ~
~j

MbSMD0S3 (D2 )
.JUNE 1979
EXORdisk IIIIII Operating System User's Guide
Th~ in~ormation in this document has been carefully
ctr~ked; and, is believed to be enti,..ely reliable. No
. T";~spo.n·sibilityJ however, is assumed for inaccuracies.
: FU'r"'t'her1nore, such information does not convey to the
~ p. u/r"c has. e·r 0:f the pro due t des cr· i bed any 1i c en s e. und e r the
:;:pat:e:n·t- T'ig;hts of Motorola, Inc. or othel's.
Motorola reserves the right to change speci~ic:ations
\J1it:llout no t-i c e.
·EXORcise,..@: EXbug, EXORdisk,
EXORterm 'and MDOS are
trade-maT'ks of Motorola, Inc.
Second Edition
CopYTight 1979 by Motorola. Inc.
First Edition, December 1978

TABLE OF CONTENTS
Page
2.9.4 LIST - >F~il·e d lSP lay . . . . . . . . 02-26
2.9.5 MERGE -- File concatenation ... ,. 02-26
2.9.6 BINEX -- EXbug-loadable file c~eatiQn . 02-27
2.9.7 FREE -- Available file space display 02-27
2.9.8 ECHO -- Echo console IIO on p~inter. . 02-27
2.9.9 PATCH -- Executable p~ogram ~ile patching 02-27
2.9.10 CHAIN ----- MDOS command chaining. 02-27
2.9.11 REPAIR -- System table checking . 02-28
2.9.12 DUMP -- Diskette sector display 02-29
2.9.13 FORMAT -- Diskette ref~rmatting 02-28
2.9.14 DOSGEN -- MDOS diskette gene~ation . 02-28
2.9.15 ROLLOUT -- Memor~ rollout to diskette . 02-29
2. 10 MOOS-Supported SoftUJa~e Products . 02-29
2. 11 Paper Alignment . . . . . . . . . . . . . . . 02-29
• 4
Page iv
:"\
j
" /
---,,'

TABLE OF CONTENTS
PART II -- ADVANCED MOOS USER'S GUIDE
3.
4.
5.
6.
BACKUP COMMAND
3. 1 Use .
3.2 Diskette Copying
3.3 File Reorganization
3.4 File Appending
3.5 Diskette Verirication
3.6 Other Options .
3.7 Messages
3.8 Precautions with BACKUP
3.8.1 BACKUP and the CHAIN proces~
3.8.2 Single/double-sided diskettes
3.8.3 Four-drive systems
3.9 Examples
DINEX COMMAND
4. 1 Use .
4.2 Error Messages
4.3 Examples
BLOKEDIT COMMAND
5. 1 Use .
5.2 BLOKEDIT Command File
5. 2. 1 Comment 1 i nes
5.2.2 Command lines
5.2.3 Guoted lines
5. 3 Messages
5.4 Examples
CHAIN COMMAND
6. 1 Use .
6.2 Tag Definition, Assignment, and Substitution
6.3 Compilation Operators.
6.3. 1 Comp i lation Comments
6.3.2 IF operator .
6.3.3 XIF and ELSE operators
6.3.4 ABORT operator
6.4 Execution Operators.
6. 4. 1 Ex ec ut i on Comments
6.4.2 Operator Breakpoints
6.4.3 Error status word
6.4.4 SET operator
6.4. 5 TST operator
6.4. 6 JMP operator
6.4.7 LBL operator
6.4.8 eMD operator
6. 5 Messages
6.6 Resuming an Aborted CHAIN Process
Page
03-01
. 03-01
03-02
03-03
03-08
03-10
03-11
03-13
03-17
03--17
03-18
03-18
03-18
04-01
04-01
04-02
04-02
05-01
05-01-
05-01
05-02
05-02
05-03
05-03
05-05
06-01
06-01
06-02
06-04
06-05
06-05
06-07
06-08
06-08
06-09
06-09
06-10
06-11
06-11
06-12
-06.-13
06-13
06-13
06-16
Page v

17.
18.
19.
20.
TABLE OF CONTENTS
LIST COMMAND
17.1 Use
17.1.1 Start/end speciFications
17. 10 2 Ph Y sic all in e numb er s
17.1.3 User-supplied heading
17.1.4 Non-standard page -formats
17.2 Messages.
17.3 Examples
LOAD COMMAND
Page
17-01
17-01
17-02
17-02
17-03
17-03
17-04
17-05
18-01
18. 1 Use 18-01
18, 1. 1 Command-interpreter-loadab Ie programs 18-03
18. 1. 2 Non-command-interpreter-lcadab Ie pl'ogT"ams18-04
18.1,3 Programs in the User Memor~ Map 18-06
18.1.4 MDOS command line initialization 18-07
18.1.5 Entering the debug monitor 18-08
18.2 Error Messages 18-09
18. 3 Ex amp 1es . 18-11
MERGE COMMAND
19. 1 Use
19.1.1 Merging non-memor'J-image files
19.1.2 Mel'ging memory-image riles
19. 1. 3 Othel' options
19.2 Messages
19.:3 Examples '.
NAME COMMAND
20. 1 Use
20.1.1 Changing rile names
20. 1. 2 C han gin 9 f i 1 eat tr i but e s
20.2 Error Messages
20.3 Examples ..
19-01
19-01
. 19-02
19-03
19-04
19-05
19-05
20-01
. 20-01
20-01
20-02
20-03
20-04
Page viii

21.
22.
23.
TABLE OF CONTENTS
PATCH COMMAND
21. 1 Use
21.2 PATCH Command Set
21.2.1 Quit -- Q
21.2.2 Set/display offset -- 0
21.2.3 Display single location
21.2.4 Display lowest address -- L
21.2.5 Display highest add~ess -- H .
21.2.6 Calculate relative address -- R
21.2.7 Dis-assemble ope~ation code -- I
21.2.8 Set search mask and patte~n -- M .
21.2.9 Search for byte -- 5 .
21. 2. 10 Searc h for word -- W
21. 2. 11 Sea r c h f or non -rna t chi n 9 bYt e -- N
21. 2. 12 Sa arc h ~ 0,.. non -rna t chi ng w0 i" d -- X
21. 2. 13 Di sp lay rang e of 1 ocat i cns -- P
21. 2.14 Set/dispiay execution address -- G
21. 2.15 Change locations
21. 2. 16 Instruction mnemonic decode mode
21.3 Special Considerations
21.4 Error Messages
REPAIR COMMAND
22. 1 Use
22.2 ID, LCAT, CATI BootblacK Sector Check
22.3 Directory Sector Check.
22.4 Retrieval Information Block Check
22. 5 CAT Regeneration Phase
22.6 CAT ReplacementJPhase
22. 7 Messages
22. 8 Ex~mp les .
ROLLOUT COMMAND
23. 1 Use
23. 1. 1 User Memory Map
23. 1. 2 Non-over lay ed memory
23.1.3 Overlayed memory
23. 1. 4 5C 1" ate h dis ke t t e con ve r s ion
23.2 Messag es .
23.3 Examp 1 es .
Page
21-01
21-01
21-02
21-02
21-03
21-03
21-04
21-04
21-05
21-05
21-07
21-08
21-08
21-09
21~09
21-09
21-10
21-10
21-12
21-15
21-16
22-01
22-01
22-03
22-08
22-11
22-15
22-18
22-19
22-19
23-01
23-01
23-02
23-03
23-03
23-05
23-06
23-08
Page ix

TABLE OF CONTENTS
24. SYSTEM DESCRIPTION. .
25.
24.1 Diskette Structure
24; 1. 1 Diskette Identification Block
24.1.2 Cluster Allocation Table.
24.1.3 Lockout Cluster Allocation Table ..
24, 1. 4 Di ree tory
24.1. :; Bootblock
24.2 File Structure.
24.2.1 Retrieval Information Block
24.2.2 File formats ..
24.3 Record Structure ..
24.3. 1 Binar~ records
24.3.2 ASCII records
24. 3.3 ASCII-CQnve~ted-binaTY records
24.3.4 File descriptor records
24.4 System Files
24.4.1 System overlays
24.4.2 System error message file
24. 5 Memorq Map , . . . . .
24.6 MDOS Command Interpreter
24.7 Interrupt Handling.
24.8 System Fun~tion Calls
24.9 MOOS Equate File.
INPUT/OUTPUT FUNCTIONS FOR SUPPORTED DEVICES
25.1 Supported Devices'
25.2 Device Dependent I/O Functions
25.2.1 Console input -- .KEYIN
25.2.2 Check for BREAK key -- .CKBRK
25.2.3 Console output -- . DSPLY, . DSPLX, .DSPLZ
25.2.3. 1 Examp Ie aT console lID ..
25.2.4 Printer output ...- . PRINT, . PRINX
25.2.4.1 Example oT printel' output
25.2.5 Physical sectoT input -- . DREAD, .EREAD
25.2.6 Physical sectoT output -- . DWRIT, . EWRIT
25.2.7 Multiple sector input -- . MREAD, .MERED
25.2.8 Multiple secto~ output -- . MWRIT, . MEWRT
25.2.9 Diskette controller entry points
25.3 Device Independent IIO Functions .
25. 3. 1 1/0 Contro 1 Bloc k -- IOCB
25.3.1.1 IOCSTA Error status
25.3. 1. 2
ICCDTT Data tl"ans-Per type
25_ 3_ 1. 3 IOCnSp
Data burrel' pointel'
25.3. 1. 4 lOCDBS
Data
bUTTer stal't
25. 3. 1. 5
IOCOBE
Data bUrrel'
end
25.3. 1. 6
IOCGDW Generic device word
25. 3. 1. 7
IOCLUN
Logical
uni t
number
25.3. 1. 8
IOCNAM
File name
25.3. 1. 9 IOCSUF
Suffix
25.3. 1. lQ
IOCMLS Maximum LSN referenced
25. 3. 1. 11
IOCSDW Current
SDW
25.3. 1. 12
IOCSLS
Starting
LSN of SDW
Page
24-01
24-01
24-02
24-03
24-03
24-04
24-06
24-07
24-07
24-10
24-11
24-11
24-12
24-13
24-14
24-15
24-16
24-17
24-17
24-20
24-21
24-23
24-25
25-01
25-01
25-01
25-02
25-04
25-05
25-06
25-07
25-08
25-09
25-11
25-12 .
25-13
25-13
25-13
25-14
25-18
25-19
25-22
25-22
25-23
25-23
25-23
25-24
25-24
25-25
25-25
25-25
Page
x
,. ---')
-'. ~.,/'
\
I
.. ./

TABLE OF CONTENTS
25. 3. 1. 13
25. 3. 1. 14
25.3.1.15
IOCLSN
ICCECF
IOCRIB
Next LSN
LSN of end- of-file .
PSN of RIB
Page
25.3. 1. 16
25.3.1. 17
25.3. 1. 18
25.3. 1. 19
25.3. 1. 20
IOCFDF
IOCDEN
IOCSBP
IOCSBS
loeSBE
File descriptor flags
Directory entry number
Sector buffer pointer
Sector blJ~~er start . .
Sector buffer end . . .
25-26
25-26
25-26
25-26
25-30
25-31
25-31
25-31
25-32
25-32
25.3.1.21
IoeSBI
Internal buffer pointer
Reserve a device -- .RESRV
25.3.2
25. 3. 3
25. 3. 4
25.3.5
25. 3. 6
Open a file -- . OPEN.
Input a record -- . GETRC .
Output a record - .PUTRC
Close a file -- . CLOSE.
25.3.7 Release a device -- . RELES
25.3.8 Example of device independent 110
25.3.9 Specialized diskette I/O functions
25.3.9.1 Input logical sectors -- . GETLS
25.3.9.2 Output logical sectors -- .PUTLS
25.3.9.3 Rewind file -- . REWND ....
25.3.9.4 Example of logical sector I/O
25.3.10 Error handling ..... .
25-34
25-39
25-42
25-45
· 25-48
25-49
· 25-51
25-51
25-54
25-56
· 25-58
25-62
26. INPUT/OUTPUT PROVISIONS FOR NON-SUPPORTED DEVICES 26-01
26. 1 Devi c e Dep end ent I/O .
26.2 Device Independent IIO
26.2. 1 Cont~oller Descripto.r Block -- CDB
26.2. 1. 1 CDBIOe CLlrrent IOCB add1'ess
26. 2. 1.2 CDBSDA 50~tware driver address
26. 2. 1. 3 CDBHAD Hardware address . . . .
26.2.1.4 CDBDDF Device descriptor flags
26.2.1.5 CDBVDT Valid data types
26.2.1.6 CDBDDA Device dependent area
26.2. 1.7 CDBWST Working storage
26.2.2 Device drivers . .
26.2.3 Example of device driver ..
26.2.4 Adding a non-standard device
26-01
26-01
26-01
26-04
26-04
26-04
26-04
26-07
26-08
26-08
26-08
26-10
26-13
P ag e xi

TABLE OF CONTENTS
Page
27. OTHER SYSTEM FUNCTIONS
.. 27-01
27.1 Register Functions
27.1.1 Transfer X to B,A . TXBA
27.1.2 Transfer a,A to X -- . TBAX
27.1.3 Exchange B,A ~ith X . XBAX
27-01
27-02
. . 27-02
27-02
27.1.4 Add B to X -- .ADBX
27.1.5 Add A to X -- .ADAX
27. 1. 6 Add B, A to X -- . ADBAX
27.1.7 Add X to B,A ~- .ADXBA
27.1.8 Subtract B from X -- .SUBX
27.1.9 Subtract A from X -- .SUAX .
27.1.10 Subtract a,A from X -- .SUBAX
27.1.11 Subtract X from a,A -- .SUXBA
B.A with X -- . CPBAX
27.1.13 Shift X right -- . ASRX
27.1.14 Shift X left -- . ASLX .
27. 1. 15 Push X on stac k -- . PSHX
27. 1. 16 Pull X from stack -- . PULX
27.2 Double-byte Arithmetic Functions.
27.2.1 Add A to memor~ -- .ADDAM
27.2.2 Subtract A from memory -- . SUBAM
27.2.3 Shift memor~ right -- ,DMA
27.2.4 Shift memor~ left -- . MMA
27.3 Character String Functions
27.3.1 StTing move -- . MOVE
27.3.2 StTing comparison -- .. CMPAR
27.3.3 CharacteT-~ill a string -- . STCHR
27.3.4 Blank-fill a string -- . STCHB
27.3.5 Test for alphabetic character -- . ALPHA
27.3.6 Test for decimal digit -- . NUMD
27. 4 Dis ke t t e F i 1e Fun c t ion s . . . . .
27.4.1 Directory search -- . DIRSM .
27-02
27-03
27-03
27-03
27-04
27-04
27-04
27-05
. 27-05
27-05
27-05
27-06
27-06
27-06
27-07
27-07
27-07
27-08
27-08
27-08
27-09
27-10
27-10
27-11
27-11
27-11
. 27-14
27-17
27-20
27-25
27-28
27.4.2 Change file name/attributes -- . CHANG
27.4.3 Load program into memory -- . LOAD
27.4.4 Allocate diskette space -- . ALL DC
27.4.5 Deallocate diskette space -- . DEALe
27.4.6 Display system error message -- . MOERR . 27-30
27-35
27-35
27-38
27-39
27-40
27-40
27.5 Other Functions .....
27.5.1 Process rile name -- .PFNAM
27.5.2 Re-enter resident MOOS -- . MDENT .
27.5.3 Reload MDOS from diskette -- . BOOT
27.5.4 Set system error status word . EWORD
27.5.5 Allocate user program memory ~- .ALUSM
28. ERROR MESSAGES .
28.1 Diskette Controller Errors
28.1.1 Errors during initialization
28.1.2 Errors. after initialization
28.2 Standard Command Errors
28.3 Input/Ouput Functi9n Errors
28.4 System Error Status Word
28.5 Commands Affecting Error Status Word
28-01
28-01
28-01
28-05
28-06
28-18
28-19
28-20
Page xii
. ../

TABLE OF CONTENTS
Page
APPgNDICES
A. Cylinder-Sector/Physical Sector Conversion Table . A-O!
B. ASCII Character Set 8-01
C. MDOS Command Syntax Summary C-Ol
D.
Diskette Controller
C' ... +0 .... "
1-" '" I ':f
Points
E. Mini-Diagnostic Facility
F.
Diskette Description, Handling, and Format
G. D ire c tor y Has h in 9 Fun c t ion
H. MDOS-Supported Software Products
H.1 ASM -- M6BOO Assembler
H.2 ASM1000 -- M141000 Cross Assembler
H.3 ASM3870 -- M3870 Cross Assembler
H. 4 BASIC -- BASIC Interpreter
H.5 E -- CRT Text Editor
~. 6 EDIT -- Text Editor
H.7 EM3870 -- M3870 Emulator
H.e FORM1000 -- M141000 ObJect File Conversion
H.9 FORT -- Relocatable FORTRAN Compiler
H. 10 MASM -- MACE Cross Assembler
H. 11 MBUG -- MACE Loader and Debug Module
H. 12 MOTEST -- Component Tester Executive
H. 13 MPL -- MPL Compiler
H. 14 PPLO/PPHI -- PROM Programmer I
H. 15 PROMPROG -- PROM Programmer 11/111
H. 16 RASM -- Re 1 ocatab 1e M6800 Macro As semb 1 er
H. 17 RASM09 -- Relocatable M6809 Cross Assembler
H. 18 RLOAD -- Li n king Load er
H. 19 SIM1000 -- 141000 Simulator
H.20 USE with MDOS
1. MDOS EQ.uate Fi Ie Listing
J. MDOS 3.00 Differences
~. 1 Impact of MDOS 3.00 on Previous MDOS Programs
J.2 Enhancements to MOOS 2.20/2.21
J.3 Enhancements to MDOS 3.00
K. IOCB Input Parameter Summary
L. EXORdisk 11/111 Sgstem Specifications
0-01
E-Ol
F-Ol
G-Ol
H-Ol
H-02
H-04
H-07
H-09
H-l0
H-l1
H-13
H-14
H-16
H-1S
H-20
H-21
H-22
H-24
H-26
H-27
H-30
H-33
H-39
H-40
1-01
,)-01
""-01
J-04
,)-06
K-01
.L~Ol
Page xiii

CHAPTER 1
1. INTRODUCTION
The EX OR dis k I lis a sin 9 1e -5 ide d, sin 9 1e- den sit tJ ' d ua 1
diskette drive storage system designed for use with the
EXORciser or EXORterm, The EXORdisk III is a double-sided,
single-density, dual diskette drive storage system designed
for use with the EXORciser or EXDRterm. The EXORdisk III can
be expanded into a four-drive system.
With either the EXORdisk II or EXORdisk III system, the
following items are also included: a Tlopp~ disk controller
module, a floppy disk interconnection cable assembly, and a
software disk operating system. An illustration of a typical
EXORdisk system is shown in Figure 1-1.
The M6800 Diskette Operating System (MOOS) or M6809
Diskette Operating System (MDOS09), in conJunction with the
EXORciser and EXORdisk II or EXORdisk III, provides a
powerful and easy-to-use tool for software development. t"or
the remainder of this manual, all references to MDOS will
encompass both the M6800 version as well as the M6809
version, unless otherwise specified.
MDOS is an interactive operating system that obtains
commands from the s~stem consol~. These commands are used to
move data on the diskette, to process data, or to activate
user-written processes from diskette. All this can be
accomplished with a minimum of effort; and since MDOS is, a
facilities oriented system; rather than a supervisory
o~iented onel a minimum of overhead is imposed.
In addition, an extensive set of resident system
functions are provided for general ~evelopment use. Such
functions as dynamic space allocation, random access to data
files, record I/O for supported and non-supported devices, as
well as many registerl string, and other diskette-oriented
routines make MDOS a good basis for a user's application
system.
Page 01-01

r
/,----
Figurg 1-1.
Typcial EXORdisk system.
Page
01-02
I
/

INTRODUCTION
1. 1 -- Ha~dwa~e Suppo~t Requi~ed
1. 1 Ha~dUJare SUppOT't Requi~ed
The minimum hardware configuration required to support
MOOS consists of:
an EXORciser o~ EXDRterm with EXbug ri~mware
16K RAM
EXORdisk IIIIII dual diskette drive unit
EXORdisk IIIIII floppy disk controlle~ module
Interconnect cable
ASR33 (TTY) Or RS=232C compatible te~minal
The EXORdisk II can read and write diskettes recorded in
an IBM-3740-simila~ TOT'mat (single-sided} single-density).
The EXORdisk III can ~ead and write all diskettes that the
EXORdisk II can handle. In addition: diskettes fQT'matted in
the Motorola single-density, double-sided format can also be
read and written. The double-sided diskettes cannot be used
in the EXORdisk II.
The above minimum configuration will allow the use~ to
run any of the MDOS commands that reside on the MDOS system
diskette at the time of purchase. Othe~ additional ha~dwa~e
may be required to run the MDOS-Suppo~ted software p~oducts.
Such information is described in Appendix H.
1.2 Additional Supported Hardware
MDOS also supports a line printer and the ~eaderlpunch
(record) devices of the system console. The line printer
interfaces to the EXORciser through the printe~ interface
module (MEX68PI) which consists of two PIA's plus the
necessa~y buffering devices and add~ess decoding. If the
printer inte~face from an EDOS system is used instead, it
must be modified for use with MDOS. The modirications
consist of adding the rollowing lines to th€ printe~
interface PIA:
1. Print select (high=selected) to PBO (pin 18 of PIA)
2. Paper out (low=paper available> to PBl (pin 11 of
PIA)
The system console's automatic readerlpunch
(record)
devices must be similar to a Teletypewriter's paper tape
reade~ and punch. For a complete description or the system
console requirements consult the "M6800 EXORciseT' User's
Gu ide ".
Page 01--03

NTRODUCTION
1.3 -- Software Suppo~t Required
1.3 SOTt~are Support Required
No additional software is re~uired to run the operating
system as it comes shipped on the system diskette.
1.4 Program Compatibility
All of the MDOS commands and system Tiles that are
shipped on the system diskette must be used with that
particular version of MDOS. MDOS commands and system Tiles
rrom other versions should never be intermixed.
MDOS-Supported softlllal'e products (see A-9pendi~ H) with
version numbers 3.00 or greater must be used with MDOS 3.00.
They will nat operate correctly with p~iQr ver~ions o~ MDOS.
In addition} prior versions of the M6800 Linking Loader
CRLOAD, through version 2.03) will not operate with MDQS
3.00. Prior versions of other MOOS-Supported sOTtware
products will work with MDOS 3.00.
Most user-~ritten assembly language programs that were
developed independently oT MDOS can be executed on an MDOS
system without reassemblYi hOUlever, such programs 111111 have
to be converted into the memory-image rile format before they
can be loaded rrom diskette into memol'q (see section 2.8.5).
Programs need only be changed ~hen transferred ~o MDOS if:
1.
They make assumptions
initialization of the stack
they are loaded into memory}
about the
pointer after
2. They are origined to load (initialize memorq
~hile loading) below hexadecimal location
$20,
3. They make assumptions about the physical
structure of diskette tables or files,
4. They utilize the diskette for input/output,
5. They make assumptions about the contents of
the SWI and IRG interrupt vectors.
If a user has prior EXORciser support software products
which he has purchased f!'om Motorola (e. g. I editors,
assemblers, or compilers), that software must be upgraded to
be compatible with MDOS.
If a user has softUJare that
he has developed
using
previous
ve,..·s ions
of
MDOS,
then Appendix
.J should be
consulted
for
a
list or dirferences between
MDOS 3. 00
and
prior
versions
that may
affect programs
running
. wi th
MOOS
3.00.
Page 01-04
\
J

INTRODUCTION
1.5 -- Hardware Installation
1.5 Hardware Installation
The floppy disk controller module and drive" unit should
be inspected upon receipt for broken, damaged, or missing
parts as well as for damage to the printed circuit board.
The packing materials should be saved in case reshipping is
necessary.
1. 5.1 Four-drive system installation
The following procedure must be performed to install the
four diskette drive version of the EXORdisk III. This
section is not applicable to EXORdisk II systems or to
dual-drive EXORdisk IiI systems. This procedure must be
performed before the floppy disk controller module is
instailed (next section). It should be noted that in the
four-drive configuration, all diskette controller originated
lines must be terminated in the last d~ive of the daisy
chain. When facing the front of the disk drive units, drive
zero is on the left and drive one is on the right of one
unit, ~hile drive two is on the left and drive three is on
the right of the other unit. Before the following
modifications are made, both dual-drive units are identical.
1. The housings from both dual-drive units must be
removed.
2. In the dual-drive unit that is to contain drives
and one, the Terminator Network (Motorola
51NW9626A01) should be removed from the socket
on printed circuit board (pcb) for d~ive zero.
drive one pcb socket XA22 should not have
Terminator Network installed.
zero
PIN
XA22
The
the
3. JPR 11 should be installed in the Jumper area of the
pcb for drive zero.
4. JPR 9 should be installed in the Jumper are~ of the
pcb for drive one.
5. The housing should be replaced on this dual-drive
unit and the drives marked as zero and one.
6. On the other dual-drive unit the Terminator Network
should be installed in socket XA22 of the pcb for
d~ive three. There should be no Terminator Network
installed on socket XA22 of the pcb ror drive two.
7. ,",PR 11 in the. Jumper area of the pcb for drive two
should be removed (ir installed>. JPR 8 should be
install ed.
Page 01-05

!NTRODUCTION
8.
1.5 -- Hardware Installation
~PR 9 in the Jumper are Or the pcb ror drive three
should be removed (if installed), JPR 10 should be
installed.
9. The 50-pin ribbon cable that connects to Pi o~ the
Controller Interconnect Board must be disconnected
and insulated
against
mater ial.
contact
... .: .....
I.U.""II
conductive
10. The housing on ,this dual-dT'ive unit should be
11.
replaced and the drives marked as two and three.
The 50-pin
should be
tlUo/th"'~HL
ribbon cable (Motorola PIN 30BW1824X01)
installed between drives zer%ne and
1. 5.2 Floppy disk controller installation
To install the floppy disk controlleT' module into the
EXORciser, the following steps should be ~ollowed:
1. The PWR .keysUJitch on the EXORciseT' should be
turned OFF. CAUTION: InseT'ting the floppy
di~k controller module while pow~r is applied
to the EXORciser system may result in damage
to components o~ the module.
2. Any other card
to addresses
through $EC07,
from the system
address range.
in the EXORciser that responds
between hexadecimal $E800
inclusivel must be removed
or configured ror a di~ferent
3. The floppy disk cont~oller module can then be
inse~ted into anq available card slot. It is
desirable to keep all or the cards in the
EXORciser close togethe~i it is speci~ically
recommended that dynamic memory boards be
kept as close to the MPU board as possible.
When properly installed, the component sides
of all cards should be facing the left-hand
side of the EXORciser chassis (as viewed from
the rront)' The EXORciser motherboard
connectors are offset and keyed to prevent
backward installation of cards.
4.
The interconnect cable
attached to both the drive
diskette controller module.
should then
unit and
CAUTION:
pln index mark on the connector must match
with the index mark on the cable. Damage
the module will result if the cable
installed the wrong way.
be
the
The
up
to
is
Page 01-06
'\
I
'\
I
.J

INTRODUCTION
5.
1.5 -- Hardware Installation
Power can now be applied to both the drive
unit and to the EXORciser -- the hard~are is
installed.
habit of
following
EXORciser,
power off
The operator should get into the
turning on the power in the
sequence: system console,
EXORdi~k, and line printer. The
sequence should be the reverse:
line printer, EXORdisk; EXORcise~: and system
console. No diskettes should be in a drive
while the drive's or the EXORciser's power is
being turned on or off.
1.6 Software Installation
There is no so~tware installation that need be
performed. All MDOS software is included on the diskette
that is shipped with each EXORdisk. This diskette contains
the operating system and a set of commands that comprise
MDOS. It mayor may not contain any of the MDOS-supported
software products such as editors or assemblers. These
products are dependent on the mode of system purchase.
Page 01-07

-
-
c
C:::
c::
~
C-
o

CHAPTER 2
2. GENERAL SYSTEM OPERATION
This chaptg~ provides the user with the basic concepts
that are necessary for the simplified and typical operation
of MOOS. It contains descriptions and examples or the
initialization procedures and of the basic forms of the most
frequently used commands. These examples clearly illustrate
hoUl MOOS is used to ed ita programl to assemb 1e i tl to
convert it into a loadable modulel to load it and execute it#
as well as some other useful ope~ations. The commands are
presented in a sequence that is commonly followed in a
software development environment.
2.1 System Initialization
To initialize the operating system, power must first be
applied to the EXORciser and to the diskette drive unit. No
diskette should be in the drive while power is being turned
on or off on either the drive or the EXORciser. Once the
power is onl the following steps must be ~ollowed:
1. EXbug must be initialized and configured for
the proper speed of the system console. If
power has Just been turned on for the first
time} EXbug initialization is automatically
performed by the power-up interrupt service
routine in EXbug. If power is already on and
MOOS is to be re-initialized, then either the
ABORT ,or RESTART pushbuttons on the
EXORciser's front panel must be depressed to
initialize EXbug. The prompt "EXBUG V.R"
will be displayed by EXbug indicating it is
waiting for operator input. "V" indicates
the version and "Rn the revision number of
the EXbug monitor in the system.
2. An MDOS diskette (one shipped from Motorola
or one that has been properly prepared by the
user (see section 2.8.10» must be placed in
drive zero. The door on the drive unit must
then be closed in order for the diskette to
begin rotating. For the side-by-side drivesl
drive zero is on the left side, as seen from
the front. For the EDOS-converted systems
us i ng ·t h eve r tic all y . S t a c ked dr i ve sid r i ve
zero is the top one.
The diskette must be oriented properly before
Page 02-01