CFOG's PIP, November 1989, Volume 8 No. 4, Whole No. 72, page 32
November Programs
No more program chairman means no more programs, right? Wrong. For the November meeting Rand Gerald has promised a program on Paradox, a relational database program for MS-DOS users. Since that means there will be an MS-DOS machine at the meeting, Ben Cohen says that if there's time and interest he'll give a few comments on 4DOS, the 'DOS shell that was reviewed in the August 31 issue of PIP.
CFOG's PIP, November 1989, Volume 8 No. 4, Whole No. 72, page 32
Lrun Library Utility "knows" Where COMMAND.LBR Is
by Benjamin H. Cohen
I keep telling people they should get a modem and I keep hoping I'll get through. You'll get answers to questions that others have, many of which I won't capture and present here in PIP. Sometimes, what happens is that a question on AFRAS elicits a partial answer, and the rest of the answer comes from reading the documentation. I keep telling you to do that, too. Sigh.
I long ago found out about the virtues of LRUN. That's the library utility program that lets you run a program that's in a LBR file. You enter LRUN LBRNAME FILENAME<cr> and the program FILENAME.COM in LBRNAME.LBR runs without having to extract it from the LBR. The latest LRUN is Version 2.3. It has been around for a long time. LRUN is most useful on a system with large allocation blocks -- even at 2K you save some space, at 4K you start saving a lot. Hard disk users can save a lot of space by putting a lot of files in their COMMAND.LBR.
Why did I say you should put a lot of files in your COMMAND.LBR? Well, if LBRNAME is COMMAND you don't have to enter COMMAND, just enter "LRUN FILENAME<cr>" and FILENAME.COM will run. Thanks to Andy's question, and a response from another AFRAS user and CFOG non-member, Ron Rock, we now know that the patch location to change the default drive for your COMMAND.LBR is 00D5 (drive A = 01, B = 02, etc.) and the location for the user area is 00D7 (values 00 - 0F, Ron noted). (The locations given are the program locations, used by SuperZap, some other patching programs use the memory location which requires you to add 0100h.)
If you don't like to use the name COMMAND.LBR, you can easily locate the name in LRUN with Superzap and change it to any name you want to use. You might want to call it just C.LBR to save extra typing of the long name COMMAND when you do LBR maintenance.