version will be saved
as
there
is
still room for. After the command
is
completed, a look
at
a directory will show the new version
is
present, but doesn't occupy enough blocks
to
match the copy
in
memory.
DVERIFY
This command makes a byte-by-byte comparison
of
the program currently
in
mem-
ory against a program on diskette. This comparison includes the BASIC line links, which
may be different for different types
of
memory configurations. What this means
is
that a
program saved to disk on a C64 and reloaded into a
CI28
wouldn't verify properly
because the line links point to different memory locations. If the disk copy
of
the program
differs at all from the copy
in
memory, a "VERIFY
ERROR"
will
be
displayed. This
doesn't mean either copy
is
bad, but if they were supposed
to
be identical, there
is
a
problem.
FORMAT FOR THE DVERIFY COMMAND
DVERIFY "file
name"
[,Ddrive#] [,Udevice#]
The following version
of
the command verifies a
file
that was just saved:
DVERIFY"*"
This command won't work properly after SAVE-WITH-REPLACE, because the last
file used was the one deleted and the drive will try
to
compare the deleted file to the
program
in
memory. No harm will result, but "VERIFY
ERROR"
will always
be
announced. To use DVERIFY after @SA VE, include at least part
of
the
file
name that
is
to be verified
in
the pattern.
COpy
The COPY command allows you to make a spare copy
of
any program or
file
on a
diskette. However, on a single drive like the 1571, the copy must be on the same diskette,
which means
it
must be given a different name from the
file
copied. The source
file
and
other files on the diskette are not changed. Files must
be
closed before they can be copied
or
concatenated.
FORMAT FOR THE COPY COMMAND
COPY [Ddrive#,]
"old
file
name"
TO [Ddrive#,]
"new
file
name"
[,Udevice#]
Where both
drive#s
would be 0 if included.
27
To Next Page
Loading...
