Category : Word Processors
Archive   : QEDIT215.ZIP
Filename : QEDITTSR.DOC

 
Output of file : QEDITTSR.DOC contained in archive : QEDIT215.ZIP
SEMWARE IS PLEASED TO OFFER QEDIT TSR!

QEdit TSR is a MEMORY-RESIDENT version of QEdit. QEdit TSR includes all the
features of QEdit Advanced, and it is available at the touch of a key, while
you are still running most other applications. Imagine the power and utility
of having QEdit available at anytime, regardless of what application your
computer might be running!

QEdit TSR uses a unique swapping technology to give you the benefits of a
fully featured TSR editor that can edit 300k+ files, but requires only 9k of
your precious DOS memory.

Even more amazing, QEdit TSR features a DOS shell! You can popup QEdit TSR
over your favorite application, and then shell to DOS! Imagine the
possibilities!

System requirements for QEdit TSR:

While QEdit TSR will run without these minimums, we strongly recommend them
for optimum performance:

192k of expanded memory, and an EMS 3.0 or later driver,
or
384k of extended memory, with an XMS or compatible driver,
or
384k RAM disk
or
A VERY FAST hard disk with at least 384k of free space.

We strongly recommend going the expanded/extended/RAM disk route if at all
possible. While QEdit TSR can swap to a hard or even floppy disk, the loading
time can take many seconds from these slower devices.

Note that in order to use QEdit TSR's Shell and Dos commands, and to edit
large files, additional expanded memory, extended memory, RAM disk, or
hard-disk space must be available.

QEdit TSR is priced at $99 plus shipping ($3 US/Canada/Mexico, $10 overseas).
And, for a LIMITED TIME, QEdit TSR includes a copy of QEdit Advanced V2.15!


  3 Responses to “Category : Word Processors
Archive   : QEDIT215.ZIP
Filename : QEDITTSR.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/