Advertisement
DOSGEN COMMAND
10. 4 -- Messages
diskette usable again.
10.5 Examples
The
rollowing
example
shows
the
operator-system
interaction during a DOSGEN process:
DOSGEN DRIVE 1? Y
DISK NAME:
USEROOOl
DATE (MMDDYY): 072578
USER NAME:
SYSTEM DEVELOPMENT 1
LOCKOUT ADDITIONAL SECTORS?
N
COPYING FILE MDOS
.SY
COPYING
FILE
MDOSOVO
.SY
COPYING FILE MDOSOVl · BY
COPYING FILE MDOSOV2 · SY
COPYING FILE MDOSOV3
· Sy
COPYING FILE MDOSOV4 · SY
COPYING FILE MDOSOV5
· Sy
COPYING FILE MDOSOV6 · SY
COPYING FILE MDOSER
· SY
=
The diskette to be generated was tested with
the
write/read
test
("T"
option)
to ensure that all sectors were good.
A
min
i
mum s y s
t
em wa s
9
en era ted'.
("
U"
0
P
t
ion ) .
The
n
e lIJ
I D
I
USEROOOIJ
the
geneT'ation
date,
July
25,
1978,
and
the
descT'iptive infoT'mation, SYSTEM DEVELOPMENT
I,
were
placed
into
the
ID
sector.
Since no additional sectors lIJeT'e locked
out,
DOSGEN proceeded to copy the MDOS family of system files
that must reside on each diskette.
The
following
example shows what might happen
iF
a bad
diskette is used in the generation process:
=DOSGEN
:2iT
DOSGEN DRIVE 2? Y
DISK
NAME:
USER0002
DATE (MMDDYY): 072578
USER NAME: TEST SYSTEM
SECTOR 0030 LOCKED OUT
SECTOR 0031 LOCKED OUT
SECTOR
0056
LOCKET OUT
LOCKOUT ADDITIONAL SECTORS? N
COPYING FILE MDOS
.SY
MDOS.
SY DOES NOT START AT SECTOR $18
=
Th~ee
bad
sectoT's were
found
during
the
write/read
test.
When
the
MDOS
ramily
of files wa·s copied,
i t
was detect-ed
that the locked out sectoT's prevented the resident
operating
system
file
MDOS.SY from T'esiding
at
the specified physical
Page
10-07
Advertisement
