Date   : Sat, 07 Jan 1984 1745 :00PST
From   : Eric Stork <STORK@mit-mc>
Subject: Answer to my dBASE2 question

Two suggestions were received, and are shared herewith:
From: Bruce L. Conroy <BLC%JPL-VAX>
Subject: dBase Overlay file locations
Reply-To: BLC%JPL-VAX
To  set  the  drive where dBase looks for its overlay
and  message  files, there are two locations to patch
In version 2.03 there are two prototype
file control blocks, which look like:
42cc    00 44 42 41 53 45 4d 53 47 43 4f 4d   .DBASEMSGCOM
42ed    00 44 42 41 53 45 20 20 20 4f 56 52   .DBASE   OVR
Changing 42cc and 42ed to 03 causes dBase to look for the files on
drive C. I have looked at later versions of dBase,
and while the actual locations have  been changed,
all versions seem to have two of them,  between 4200
and 4300, and the ASCII file names make them jump out on a DDT display.
^_
Another solution:

Date:     Sat, 7 Jan 84 8:27:43 EST
From:    Rick Conn <rconn%brl>
I got around it under ZCPR2 by creating a script command like the
following:      A:;dbase setup;B:
        In this way, I have all my work on B: and dbase.com and its
overlays on A:.  The command processor goes to A:, runs dbase, and the
setup.prg file sets default to B:, so any files I reference come from B:.
When done, the trailing B: puts me back into B:.
                Rick