Graphics Workshop

These are the files you need. You can send them from the package contents below.

• GWS.EXE → A:\SOFT programa de DOS 188.0 KB
• GWSINSTL.EXE → A:\SOFT programa de DOS 40.1 KB
• VGACARD.COM → A:\SOFT programa de DOS 3.9 KB

No need to put GWS.DOC, GWSDRV.RES, GWSPDR.RES, GWS.RES, EXAMPLE2.GIF, EXAMPLE3.GIF, GWSSCN.RES, ORDER.FRM and 3 more: they are manuals, source code or supporting material. Read them here and save 788.6 KB on a 1 MB disk.

1. Copy GWS.EXE, GWSINSTL.EXE, VGACARD.COM to A:\SOFT. They are DOS programs: run them from the DOS icon, or add A:\SOFT to the PATH in C:\AUTOEXEC.BAT to call them by name.

Derived from the package contents and the 200LX conventions. It installs to A: on purpose: C: is a RAM disk and every byte there is memory taken from the system.

The manual mentions these files, which are in the archive:

• MSC Mouse Driver MOUSE

when you install it. See the section on installation.

In addition to the three foregoing types of extra memory,
Graphic Workshop can be configured to use "extended or virtual" or
"expanded or virtual" memory. If one of these options is chosen,
Graphic Workshop will attempt to allocate a buffer from extended
or expanded memory if it can't do so with DOS memory. If it's
unable to allocate a buffer in extra memory, it will switch to
virtual memory and see if its luck improves. If there's no room
for a virtual memory buffer, it will give up and return an error
saying that it can't allocate memory.

By default, Graphic Workshop configured to use virtual memory
will use the current drive and directory to write its temporary
files. You can change this by adding a line to your environment
with the SET command such as:

        TEMP=H:\

In this case, any virtual memory temporary files which
Graphic Workshop wants to create will be written to the root
of drive H:. If you have a RAM disk, you should use the TEMP
environment variable to tell Graphic Workshop to use it for virtual memory
operations, as this will speed things up considerably.

Graphic Workshop can run in restricted memory, such as that
which is found on a really old PC or when running "shelled out"
of another program. However, it can do nasty things when it's
really starved for memory. Some virtual memory operations will
not work in this condition, and if it's really stuck for RAM...
if there's only a few tens of kilobytes free... it may manage to
crash. Try not to run it when there's almost no room left for it
to store things. The help menu will tell you how much memory is
free.

Graphic Workshop frequently swaps blocks of code and data in and
out of memory. In addition to the memory required for your
…

Literal excerpt from GWS.DOC, exactly as it came in the package.