Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!linus!decvax!harpo!eagle!mhuxl!ihnp4!zehntel!hplabs!sri-unix!STORK@mit-mc From: STORK%mit-mc@sri-unix.UUCP Newsgroups: net.micro.cpm Subject: none Message-ID: <15281@sri-arpa.UUCP> Date: Sat, 7-Jan-84 21:31:00 EST Article-I.D.: sri-arpa.15281 Posted: Sat Jan 7 21:31:00 1984 Date-Received: Fri, 13-Jan-84 06:26:50 EST Lines: 41 From: Eric Stork Subject: Answer to my dBASE2 question The question was: Can someone tell me how to set up DBASE2.COM so that it can be permanently on Disk C:, and will find its overlay files on C: even if it is invoked from A: or B:? In WordStar there is a location to set for where to look for overlay files. Logically, there should be such a location in dBASE, too. Advice will be appreciated. Eric. Date: 7 Jan 1984 1745 PST Two suggestions were received, and are shared herewith: From: Bruce L. Conroy 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 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