Date   : Sat, 21 Jan 1984 13:32:46 EST
From   : Bob Bloom (TECOM) <bbloom@brl>
Subject: more fat on the dbase reset fire

From my dBase II version 2.4 user manual:

RESET [<drive>]

The RESET command is used to reset the CP/M bit map after a 
diskette has been swapped.  Normally, if a diskette is swapped, 
CP/M will not allow writes to take place util after a warm or 
soft boot has taken place.

If <drive> is not specified, then the entire system will be 
reset.  Unfortunately, neithr dBase nor the operating system can 
detemine which diskettes you may have swapped and I/O errors may 
result if a disk that has open files is replaced.  If <drive> is 
specified, dBase  checks to see whether any of its files are open 
on that drive and will prevent I/O errors.  THE <DRIVE>-LESS FORM 
SHOULD THEREFORE NOT BE USED AND IS MAINTAINED FOR COMPATIBILITY 
REASONS ONLY.  [Emphasis mine.]  Do not swap and RESET the drive 
which contains the dBase system command files.

So, have you tried the RESET <drive> form vs. the vanilla RESET?

I'm interested because I'm currently involved in writting a 
hopefully saleable package that will require a disk reset.  Also 
note that one cannot reset a disk containing a .CMD file that you 
are running even if no actual swap is made.

I may also note that Ashton-Tate has been very helpfull when I 
call their service number.  (Have your REGISTERED serial number 
handy - they ask for it.)  Ask about the "Technical Reference 
Notes" and the "Technical Support Notes" - these give some hacker 
type information on some of the bugs that have been found and 
what to do about them.  No notes on the reset command though.

I've not had problems using the reset d: form - should I expect any?
I am carefull to close all files first, never reset disks with either
dbase or a running command file on it.  The usual routine is to reset
a floppy drive on a HD system in order to read/write back-up files
while within dbase command file.

bob bloom