BLC%jpl-vax@sri-unix.UUCP (01/13/84)
From: Bruce L. Conroy <BLC@jpl-vax>
Although there are some funny effects in dBase's RESET
command I have found it to be 100% reliable under several
versions of dBase if:
a) Any files on the disk to be changed are closed
(this is merely good practice in any event,)
b) The disk is changed, then
c) The command RESET (not RESET B) is given.
In particular, this sequence avoids the following
anomolies:
a) RESET B or RESET B: or any similar command seems
to have no effect whatever.
b) As long as a data file is open, there is an
unpredicable amount of data in memory, which is not on disk.
If the disk is changed at this point these data are lost,
unless
c) There is a file of the same name on the new disk,
in which case, the extra data are stuffed into that file,
resulting in the loss of the integrity of both data files.
------POURNE%mit-mc@sri-unix.UUCP (01/14/84)
From: Jerry E. Pournelle <POURNE@mit-mc> I warn you: use of DR CP/M Function 37 "reset disk" can be hazardous to your disk directory. The exact sequences that can trigger the bug are not known; but it exists, it's real, it jumps out and bites you, and you cannot know that it won't since we don't know how it does it. You are warned.