Jan 022018
DOS command stack, does NOT disable DOS edit keys. | |||
---|---|---|---|
File Name | File Size | Zip Size | Zip Type |
STAK.COM | 2496 | 751 | deflated |
STAK.DOC | 3456 | 1557 | deflated |
Download File STAK.ZIP Here
Contents of the STAK.DOC file
STAK.COM --- Version 1.10 --- BY Marc Kinsey
STAK is a general purpose DOS command stack. It should only work
at the DOS prompt; however, a DOS command which prompts you for
say, the time or date, uses the same internal buffer. This is the
only exception I have seen to the prompt rule.
To enable STAK make it the LAST entry in your autoexec file, if
it is not placed last or you have a trailing carriage return in
your batch file, STAK will not function. The reason is simply
that STAK intercepts DOS' request for input immediately after it
has loaded - a batch file request does not use the same internal
buffer that DOS uses for keyboard input, consequently STAK will
retrieve the wrong internal buffer address and will not function
( although it will remain resident, wasting valuable memory ).
This version of STAK has room for ten entries, all entries are
accessed by use of the up-arrow key. At first invocation, all
entries will be empty - after entering a few DOS commands just
hit the up-arrow and STAK will display the previous command. At
this point you may either request the preceding command by
pressing the up-arrow again or hit any other key to either use
the currently displayed command or to ignore it.
To use the currently displayed command simply enter any non-
extened key ( say, backspace to edit or a carriage return to
enter it ). A non-extended key may also be used to append to the
current entry - say, C:>dir is the current entry, entering /w
will then tell DOS to do a wide directory listing and this
command will be placed in the stack. If you hit an 'extended' key
( say F3, Ins, or any DOS edit key ), the currently displayed
line is ignored. HINT: if the stack is full and you do not wish
to use the currently displayed command, hit the down arrow ( or
any 'extended' key not used by DOS ) - this will erase the
displayed line and allow you to enter a new command.
Please note, the up-arrow must be the FIRST key that you hit in
order to invoke STAK. If you enter any other key and then try to
invoke STAK with the up-arrow you will get no response ( DOS is
ignoring it).
If you come across an empty entry, keep hitting the up-arrow and
you will quickly come across one that isn't ( you'd be surprised
how quickly ten entries can get filled up! ). STAK's command
stack is continuosly up-dated, it is filled in forward order and
recalled in reverse order. All carriage returns on null strings
are ignored; however, it is possible to have multiple copies of
the same entry in the stack - this can happen only if an entry
already in the stack is ignored by you and entered manually.
STAK has been thoroughly tested and debugged by the author using
DOS 3.3, it should operate without incident under versions 2 and
after. I have no knowledge of whether this program will interfere
and/or be interfered with by other TSR programs, if you discover
any please let me know. If you have any problems, comments,
questions or suggestions please write to me at the address below.
Revisions, source code and/or technical information IS available
( a $5donation is requested, please indicate disk type ) - I will
gladly include some other handy utilities as well as the revised
version of STAK.
Enjoy!
Marc Kinsey
270 E Susquehanna Ave
Towson MD 21204
STAK is a general purpose DOS command stack. It should only work
at the DOS prompt; however, a DOS command which prompts you for
say, the time or date, uses the same internal buffer. This is the
only exception I have seen to the prompt rule.
To enable STAK make it the LAST entry in your autoexec file, if
it is not placed last or you have a trailing carriage return in
your batch file, STAK will not function. The reason is simply
that STAK intercepts DOS' request for input immediately after it
has loaded - a batch file request does not use the same internal
buffer that DOS uses for keyboard input, consequently STAK will
retrieve the wrong internal buffer address and will not function
( although it will remain resident, wasting valuable memory ).
This version of STAK has room for ten entries, all entries are
accessed by use of the up-arrow key. At first invocation, all
entries will be empty - after entering a few DOS commands just
hit the up-arrow and STAK will display the previous command. At
this point you may either request the preceding command by
pressing the up-arrow again or hit any other key to either use
the currently displayed command or to ignore it.
To use the currently displayed command simply enter any non-
extened key ( say, backspace to edit or a carriage return to
enter it ). A non-extended key may also be used to append to the
current entry - say, C:>dir is the current entry, entering /w
will then tell DOS to do a wide directory listing and this
command will be placed in the stack. If you hit an 'extended' key
( say F3, Ins, or any DOS edit key ), the currently displayed
line is ignored. HINT: if the stack is full and you do not wish
to use the currently displayed command, hit the down arrow ( or
any 'extended' key not used by DOS ) - this will erase the
displayed line and allow you to enter a new command.
Please note, the up-arrow must be the FIRST key that you hit in
order to invoke STAK. If you enter any other key and then try to
invoke STAK with the up-arrow you will get no response ( DOS is
ignoring it).
If you come across an empty entry, keep hitting the up-arrow and
you will quickly come across one that isn't ( you'd be surprised
how quickly ten entries can get filled up! ). STAK's command
stack is continuosly up-dated, it is filled in forward order and
recalled in reverse order. All carriage returns on null strings
are ignored; however, it is possible to have multiple copies of
the same entry in the stack - this can happen only if an entry
already in the stack is ignored by you and entered manually.
STAK has been thoroughly tested and debugged by the author using
DOS 3.3, it should operate without incident under versions 2 and
after. I have no knowledge of whether this program will interfere
and/or be interfered with by other TSR programs, if you discover
any please let me know. If you have any problems, comments,
questions or suggestions please write to me at the address below.
Revisions, source code and/or technical information IS available
( a $5donation is requested, please indicate disk type ) - I will
gladly include some other handy utilities as well as the revised
version of STAK.
Enjoy!
Marc Kinsey
270 E Susquehanna Ave
Towson MD 21204
January 2, 2018
Add comments