Advertisement
REPAIR COMMAND
=DUMP :2
PHYSICAL MODE
:RD 7
:5
CHANGE BUFFER
PSN=OOOA
00
42 41
53
49
10
46 52 45
45
20
45
51
55
20
30
4C
4F
47 20
40
00 00 00 00
50
00 00 00 00
60
00 00 00 00
70
00 00 00 00
: 3Ci
3C FF
52/001
:W
:G
=REPAIR
:2
43
20
20
20
00
00
00
00
DISI( ID:
MDOS0300
VERSION:
03
REVISION:
00
DATE:
072578
20 20
20 20
20 20
20 20
00 00
00 00
00
00
00 00
USER:
SYS DEVELOPMENT
20
43
20
43
20
53
20
43
00
00
00
00
00
00
00
00
DISK
30 GOOD FILES
00 FILES WITH
BAD
4D 01
4D 02
41 04
4D
05
00 00
00 00
00 00
00 00
RIBS
RECONSTRUCTED
C. A. T.
MATCHES DISK
=
22.8 -- Examples
00
72 00 00 00
BASIC
eM ..
i' . .
B4
72
00 00 00
FREE
eM ..
r ..
BO 65 00 00 00
EGU
SA ..
e ..
70
FF FF 00 00
LOG
eM.
p ...
00 00 00 00 00
·
........................
00 00 00 00 00
.............................
00
00 00 00 00
·
...........................
00 00 00 00 00
·
.........................
The
REPAIR
c,ommand
was
then invoked
a
second
time
to
ensure that the "fix" usas correctly
applied.
Since
REPAIR
then
recognized
the file LOG.CM as a memory-image file,
the
RIB errol' disappeared automatically.
The same
erro~
could have been corrected without
having
the
detailed
systems
knowledge
that was used in the above
example.
If"
the file were deleted,
the errol'
Ulould
be
~ixed
and
the
diskette
would
be
a
valid
MDOS
diskette.
The
rollowing example shows
the
minimal-knowledge
approach
to
fixing
the
diskette:
=REPAIR : 2
DISK ID:
MDOS0300
VERSION:
03
REVISION: 00
DA TE:
072578
USER:
SYS DEVELOPMENT DISK
OA
07 03
LOG
.eM
0570
FFFF 0000
ILLEGAL ATTRIBUTE OR UNUSED BYTES.
DELETE? Y
2F GOOD FILES
00 FILES WITH BAD RIBS
WRITE RECONSTRUCTED C.A.T. TO DISK? Y
=
Page
22-21
Advertisement
