Table of Contents
Advertisement
-
M Z-5600
2. SOFTWARE CONFIGURATION
1.
2.
8.
2-1 System bootstrap
It becomes possible with the MZ-5600 to bootstrap from
the hard disk when the CPM.SYS or MSOOS is stored on
the hard disk, provided that the following restriction is
applicable.
"The system file (CPM.SYS or MS DOS) can only be loaded
from the physical drive unit number 0 during IPL."
If the CPM.SYS has been stored in the HOO, for instance;
Disk not
inserted in
+
the drive A.
Drive A
0
+
CPM.SYS
Drive A
0
+
MSDOS
CPM.SY
S
CPM.SY
t3
POWER
ON
Bootstrapped with
....::..:..:......-....... the CPM.SYS
from the HDO.
POWER
Bootstrapped with
ON
• the CPM.SYS
from the drive A.
POWER
ON
Bootstrapped with
.. the MSDOS on
the drive A.
Thus, it becomes necessary to store the MSOOS after erasing
the CPM.SYS on the HOO, inorder to bootstrap the MSOOS
from the hard disk.
SYSTEM DISK
DEVICE
SYSTEM
DISK
640KB MFD
0
HD
0
320KB MFD
X
SFD
X
640KB MFO format
256 bytes/sector
16 sectors/track
80 tracks/side
Must
be
created by DSKMAINT.
Must
be
created by DSKMAINT.
Creation and bootstrap are not possible.
Creation and bootstrap are not possible.
2K bytes/block
128 directory entries
*
Prior to the use of a fresh disk, it becomes necessary to
format the disk using OSKMAINT.
2-2 CP/M-86
Logical drive map
Logical drive
A
j
B
C I
D
E
I
F I G
I
640KB MFD
SFD
1
Physical drive
0
I
1
2
I
3
0
I
1
I
2
I
HD
1f
if
2
Physical drive
0
1) Setup for above 1 or 2 is possible using IOCNF utility
program.
2) M represents the memory disk.
3) N supports the SFOO of the one·sided, single denSity.
H
3
-6-
I
I
J
K
I
L
M
N
0
HD
N.U
MD
SFD 320KB MFD
C
1
0
0
O~3
if if
if
4) 0 supports MFOO·3 as 320/640 KB MFO. For kind of
the disk supported, refer to instruction book, OSKCNV.
But drive
0
can only be read. If write is tried to a 320
KB disk, it evoke-s a BOOS error.
,
Hide quick links:
Advertisement
Table of Contents
