Category : Word Processors
Archive   : AMAC43B.ZIP
Filename : MACR.DOC

 
Output of file : MACR.DOC contained in archive : AMAC43B.ZIP
MACR.DOC
September 26, 1991

MACRxx.QM contains a series of txtfiles and macfiles to use with QEdit and
QMAC, the macro translator from SemWare.

To get started:

1. Load MACRxx.QM with QEdit. You will find a description of the macros, the
revision history, and the macros with comments. You may want to to save the
original copy and make a new copy with a different name. If you do the latter,
just replace MACRxx below with the name of the new copy. Be sure the name
extension is QM.

2. Change "f:\qe" to the drive:\directory where your QCONFIG.DAT and "standard"
macros exist on you system. This can be quickly done as follows:


S
R
f:\qe

[enter your ram or active [drive]:\[directory] e.g. "f:\qe\"]

I

Y or N as prompted

Save file.

3. The name for my standard macros, the macros I use all the time, is
"macros.qm" and "macros.mac". Using the same procedure as in step 2, carefully
replace "macros" with the name of your standard macros as follows:


S
R
MACROS

[enter your standard macro name]

I

Y or N as prompted


"Standard" macros and QCONFIG.DAT must be in the same directory. Also change
QCONFIG.DAT name if yours if different.

4. Save file.

5. c:\ is my ram disk. A ram disk is not necessary but macros convert much
faster with a ram disk. Load all batch file in QEdit. As above, replace "c:",
not "c:\" with your ram disk, e.g. "D:".

If you do not have a ram disk, you may replace "c:" with any active drive on
your system.

6. Save file.

7. "Shell" to Dos

8. Now make a macfile from MACRxx.QM as follows:

QMACB MACRxx


9. Read macfile MACRxx.MAC as follows:


M
R
MACRxx.MAC


You should now be ready to run any of macros in MACRxx.QM.


If your txtfiles do not have the file name extension "QM" and your macfiles do
not have the file name extension "MAC", I suggest you copy all your txtfiles and
macfiles with the following:

copy *.[your txtfiles extension] *.QM
copy *.[your macfiles extension] *.MAC

10. Run Alt-7 as above which will convert the txtfile you loaded to a macfile
named c:$.MAC, convert c:$.MAC to a txtfile c:$.QM, and then load the c:$.QM and
read c:$.MAC. Although the macfile name has changed, the macros in your macro
buffer should still be the same as before running this macro.

11. Run Alt-0 which will convert the txtfile to a macfile and read it's
macfile.

12. Run ALt-9 which will which does the same as step 11 but the macfile is not
re-read.

13. Run Alt-3. Enter "ZERO.QM" at the prompt, then Enter. You should see ZERO.QM
at the end of DUM4.QM which is txtfile of the current active macros with ZERO.QM
appended to it.

14. With ZERO.QM loaded, run Alt-4 and you should see the txtfile ZERO.QM at the
end of DUM3.QM which is a txtfile of your standard macros with the ZERO.QM
appended to it. DUM3.MAC is a macfile of your standard macros with ZERO.MAC
appended to it. DUM3.MAC has been read.

Remember QEdit macro buffer is limited to 2046 (not 2048) bytes, so be careful;
if your standard macros are large and you try to append large macros to them,
you will get an error message.

15. Run Alt-5 anytime after macros using QMAC have been run to load "c:!" in a
window showing any errors from QMAC. Press Enter to remove error window. Macros
using an error window will automatically find the first error in the txtfile for
easy correction. You may test the error window by removing the asterisk at the
end of MACRxx.QM.

16. Run Alt-8 to load the macfile MACRxx.MAC. This is not necessary but is just
a test of Alt-8.

17. Run Alt-2 to refresh the macro buffer with your standard macros.

QEdit and QMAC are powerful editing tools. I hope these macros help.


  3 Responses to “Category : Word Processors
Archive   : AMAC43B.ZIP
Filename : MACR.DOC

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/