home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Shareware 1 2 the Maxx
/
sw_1.zip
/
sw_1
/
DESQVIEW
/
DVSI2_00.ZIP
/
MANPAGES.DOC
< prev
next >
Wrap
Text File
|
1992-02-22
|
109KB
|
2,469 lines
DV System Information
Version 2.00
The DVSI utilities and this manual are
copyright 1991, 1992 by
Daniel J. Bodoh
The DVSI Manual was last updated on February 22, 1992
OVERVIEW
As described in the file README.1ST, this package has been
designed with Unix in mind. For people familiar with Unix, that
should be no problem. However, users who don't know a grep from an
egrep may be confused at the Unix conventions.
This manual is designed to look similar to a Unix manual. A Unix
manual has eight separate ``sections''. Each section contains
``manual pages'' (or ``man pages'' for short). Each manual page
describes one command or system call or subroutine.
Each manual page is given the name which is constructed from the
item it describes and the section number. For example, if the command
dir is described in section 1, the title at the top of its man page is
DIR(1).
The DVSI man page is made of several sections. First, the
``NAME'' section gives the program name and a one-line description.
Following it is a ``SYNOPSIS'' which gives the syntax of the command
and the command-line options. The behavior of the command is
described in, oddly enough, ``DESCRIPTION''. The command line options
are described more completely in ``OPTIONS''. Other sections may
follow, such as ``FILES'' which list the files that are created or
used, and ``SEE ALSO'' for cross references.
Three separate sections are included here: 1dvsi, 2dvsi and
5dvsi. By far the most important section is 1dvsi, for it describes
each of the DVSI utilities in detail. Section 2dvsi is for
programmers - it explains how a programmer can use the functions of
DVSIXDI.COM. Section 5 describes file formats; in 2.00 the only two
files described are PRINTCAP and DVP files.
The installation procedure is described in the file README.1ST.
You should take a look at that file before attempting to use DVSI.
WHAT UTILITIES ARE AVAILABLE?
There are 15 separate DESQview-specific utilities in this
package. Each utility can be run from the DOS command line or
included in a batch file just like any other DOS utility. You can
redirect the output of the utilities to a file or pipe the output to
other programs. The ability to use the output in other programs can
be useful if you have a particular problem to solve and you don't want
to write a big program to solve it.
The oldest and probably most useful utility is PS. The PS
command will displays information about each window that is currently
open in DESQview. PS will tell you how much memory each window uses,
the window handle, the Switch Windows number and much more. The
feature that many users really find informative is the CPU Time and
CPU Utilization fields of PS. These numbers tell you which programs
are making your system run slow. You can use these numbers to tweak
your system for best performance.
PERF is a close relative of PS. It displays overall system
performance numbers, rather than performance on a window-to-window
basis.
The MEMSTAT program displays the same information as DESQview's
Memory Status program, and also computes the percentages of used
memory. It takes up less screen space and CPU Time than Memory
Status.
Did you ever want to watch your disk space decrease as you
downloaded a big file? With DF you can do just that. DF displays
free and used space and other information for each logical drive in
your system (including network drives). DF can even be run outside of
DESQview.
A small but sometimes useful utility is UPTIME. It will tell you
how long DESQview has been running.
Resizing, raising, lowering, hiding, etc. windows from a batch
file or command line is possible with the window manipulator WN. WN
has many subcommands for doing many of the things that your Rearrange
menu does. You tell WN which window to act on by using the window's
handle (given by PS), Switch Window number, or Open Window keys. This
ability gives the DVSI utilities many advantages over other utility
packages (notably DV Commander).
One of the subcommands of WN, KILL, was given its own program for
the sake of Unix types. KILL will simply close any window given its
handle, Switch Window number or Open Window keys.
A relatively new but very useful utility is RUN. The RUN utility
allows you to open windows right from the DOS command line. And it
doesn't require you to make a DVP with Change A Program - you can RUN
plain old EXE, COM and BAT files. The DVP memory usage, directories
and much more can be changed on the fly.
Five separate utilities make up the print spooler package. These
are LPD, LPR, LPRM, LPQ and PRCC. Background printing is described in
detail in BACKGROUND PRINTING(1dvsi). (Did you understand that? The
name is ``Background Printing'' and it's in section 1dvsi).
The DVSTUFF program will allow you to ``stuff'' keystrokes into
any other window or into the DESQview menu, just as if they had been
typed directly into the window. Used from batch files, this can be a
good replacement for DESQview scripts.
And finally, the DVSIHELP program is a menu-style help program
for each of the utilities. It is opened automatically whenever you
use a ``-?'' or invalid option on the command line.
CONTACTING THE AUTHOR
I am very interested in hearing any suggestions, criticisms or
bug reports that you may have. For the fastest reply, use electronic
mail. I respond almost immediately to all email; if you do not
receive a reply within a few days your message or my reply may have
gotten lost. If nothing else works, try the good old-fashioned paper
and envelope. You can reach me via email from many networks:
From the Internet: write to ``bodoh@xraylith.wisc.edu''.
From Compuserve: write to ``>INTERNET:bodoh@xraylith.wisc.edu''.
From Envoy: write to
``[RFC822=\"bodoh(a)xraylith.wisc.edu\"]INTERNET/TELEMAIL/US
''.
From Fidonet: send mail to the user ``uucp'' at the nearest UUCP
or Internet gateway; use
``To: bodoh@xraylith.wisc.edu'' as the first line of the
message.
From Applelink: write to ``bodoh@xraylith.wisc.edu@internet#''.
From DECnet: write to ``cxrl::bodoh''
From Bitnet: write to ``bodoh@xraylith.BITNET''
It is currently not possible to send mail to the Internet from
Genie or Prodigy.
I also participate in the Usenet newsgroup
COMP.OS.MSDOS.DESQVIEW and I occasionally scan the DESQview Echo
on Fidonet.
Please include a return address if sending email, as not all
mailers generate correct reply addresses.
My old-fashioned address is
Daniel Bodoh
1402 Regent St. #417
Madison, WI USA 53711
After June 1, 1992, do not contact me at the above address. Use
Daniel Bodoh
3731 Schneider Drive
Stoughton, WI USA 53589
INTRO(1dvsi) INTRO(1dvsi)
DVSI Manual
NAME
Introduction to DVSI commands
DESCRIPTION
Section 1 of the DVSI manual describes each of the commands
provided in the DVSI package. This manual page explains some of
the conventions used as well as information common to most or all
of the utilities.
The utilities accept one-character options which modify the
behavior of the command. Except in the case of DVSIHELP(1dvsi)
and DVSIXDI(1dvsi), the options can be introduced with the ``/''
or the ``-'' characters.
Some options require an argument. For example, a common
option is ``-c'' which puts the utility in a continuous-update
mode. The ``-c'' option requires a numeric argument which
specifies the number of seconds between updates. The argument
can either immediately follow ``-c'' with no intervening white
space, or you can separate ``-c'' and the numerical argument with
white space.
Options can be strung together, but an option that requires
an argument must be the last in a strung-together list. For
example, if the command ``foo'' has options ``-c5'', ``-p'' and
``-j'', each of the following are legal:
foo -c5 -p -j
foo -c 5 -pj
foo -pjc5
foo /c5 /p /j
foo /pjc5
All options are case sensitive. You can use the ``\'' or
the ``/'' character in filenames. Unfortunately, the first
character of a filename cannot be a ``/'', because the utilities
will then interpret it as an option.
Some programs require a process id which determines which
window the utility acts on. The process id can either be a
window handle, a Switch Windows number, or the Open Window keys.
In order for the utilities to figure out which type of
process id you used, you must follow some simple rules. If the
window handle is used, it must be exactly 4 hexadecimal digits
long (just as you see in PS(1dvsi)).
If you use the Switch Window number, it can optionally be
preceded with a ``%'' character. Although the Switch Windows
menu uses alphabetic characters when the number of windows is
more than 9, the DVSI utilities use numbers. If Switch Window
says ``A'', use 10.
One- or two-character Open Window keys are recognized.
However, if the first Open Window key is actually a digit, you
should precede it with an ``o''. For example, if your Open
Window menu has the entry ``WordPerfect 5.1 51'', you must
use ``o51''. If a numeric Open Window key is not preceded with
``o'', it will be interpreted as a Switch Window number. If two
or more windows have the same Open Window keys, the one with the
smallest Switch Window number is used.
NOTATIONS
Text that should be typed literally is enclosed in ``'' or
is in plain text (in Courier for those with a printed manual).
INTRO(1dvsi) INTRO(1dvsi)
DVSI Manual
Option or argument descriptions appear <like this>.
[Brackets] indicate optional items.
KEY BINDINGS
Some of the utilities can be run continuously in a dedicated
window. These programs can be controlled from the keyboard.
To type
redraw the window: ``r'' or control-L
hide the window: ``b'', ``h'', or the spacebar
get help: ``?''
quit: Escape, ``q'', or ``e''
REGISTERED VS. UNREGISTERED
There are only two differences between same-version
registered and unregistered copies of the DVSI utilities:
The ``-q'' option is disabled in the unregistered
copies. This forces you to see the ``UNREGISTERED
COPY'' message, but it doesn't beep or require any
annoying keystrokes.
A registered copy displays the serial number in place
of ``UNREGISTERED COPY''.
If you find the DVSI utilities useful, please pay for them
and receive a registered copy. For more information, see the
files README.1ST and ORDER.TXT.
DIAGNOSTICS
If any of the utilities encounters an invalid option or can't
figure out its command line tail, it will launch DVSIHELP and
exit with DOS error level 1.
If a process is specified and it does not exist, the utilities
exit with error level 1. This can be useful in batch files; for
example:
rem check if a window with Open Keys ``BB'' is open
:CHECK_EXISTENCE
ps -q bb
if ERRORLEVEL 1 GOTO PROCESS_GONE
Most programs can generate the following errors:
``This program requires DESQview 2.26 or higher''
You need to either run DESQview or get a newer version.
``This program requires DVSIXDI version 2.00''
You need to either run DVSIXDI.COM before starting DESQview or
you need a newer version of DVSIXDI.
``DVSIXDI not installed or not enough Common Memory''
Either install DVSIXDI.COM before running DESQview or increase
the amount of Common Memory in the DESQview setup program.
``Allocate more system memory to this window''
Use Change A Program to increase the amount of System Memory
available to the window. After doing so, you must close the
window and restart it.
INTRO(1dvsi) INTRO(1dvsi)
DVSI Manual
``Process not found''
The specified process does not exist.
``Cannot open DVSIHELP.DVP''
In order for DVSIHELP to be spawned, the file DVSIHELP.DVP must
exist in the same directory as the program spawning it.
``Cannot spawn DVSIHELP''
DESQview reported an error when the program attempted to launch
DVSIHELP.
Check the values in DVSIHELP.DVP.
``UNREGISTERED COPY: -q not available''
Register DVSI and ``-q'' will work.
FILES
DVSIHELP.DVP
This file must exist in the same directory as the program that
launches DVSIHELP. The ``Directory'' field must also contain the
DVSI directory name.
BACKGROUND PRINTING(1dvsi) BACKGROUND PRINTING(1dvsi)
DVSI Manual
NAME
Background printing utilities
DESCRIPTION
This manual page gives an overview of the DVSI utilities
provided for background printing. More information is available
in LPD(1dvsi), LPR(1dvsi), LPRM(1dvsi), LPQ(1dvsi), PRCC(1dvsi)
and PRINTCAP(5dvsi).
The utilities for background printing are very similar to
their Unix counterparts. Each one of the utilities requires that
one LPD window is open.
LPD is not a memory-resident program. It must be run in its
own dedicated window. This window will not accept any keyboard
input so it will look as if the window is ``locked up''.
However, LPD is waiting for a request from the other utilities.
As LPD receives and processes requests, it will print the date
and time as well as a description of the request in the window.
LPD is the main workhorse: it does all the printing, but does
not directly interact with the user.
You should probably start LPD from your Startup script so
you don't have to open the window by hand.
LPR sends files to LPD for printing. Even though you can
specify multiple files or print multiple copies from LPR, each
run of LPR only submits one print ``job'' to LPD. In other
words, a job can consist of one or more copies of one or more
files submitted by one LPR command. Each job is assigned a
unique number.
LPQ lists the jobs that are currently in the LPD queue.
Since LPD can only be printing one job at a time, other jobs must
wait in line for their turn at the printer. Each row of the LPQ
display lists information on one file, including the job to which
the file belongs. The file which is currently printing is
labelled ``active''.
LPRM removes a job from the queue, whether or not the job
contains an ``active'' file.
The job of PRCC is to read the PRINTCAP file, process it,
and send the results to LPD (see below). You can use PRCC when
you make a change to PRINTCAP. However, PRCC is automatically
run when LPD starts up.
Printers are defined in the text file named PRINTCAP. This
file maps ``logical'' printers onto ``physical'' printers. A
physical printer is how you know the printer on a day-to-day
basis: LPT1, COM1, print-to-file, etc. A logical printer is just
a name given to a physical printer and formatting
characteristics. More than one logical printer may use the same
physical printer.
You must edit the PRINTCAP file with any text editor to
define the printers available on your system. The format of this
file is described in PRINTCAP(5dvsi). A sample PRINTCAP is
provided.
For example, the simplest PRINTCAP entry simply assigns the
name ``lp'' to ``LPT1''. That means that when you type
LPR -Plp autoexec.bat
your AUTOEXEC.BAT file is sent to LPT1. LPD can print to 4 types
of physical printers: LPT, COM, FILE and DVP.
The LPT and COM physical printers are simply printers
BACKGROUND PRINTING(1dvsi) BACKGROUND PRINTING(1dvsi)
DVSI Manual
connected to your LPT and COM ports. The FILE physical printer
type is just like the ``print-to-file'' option available in
applications. A logical printer mapped onto a physical printer
of type FILE copies the file to a DOS device driver or file.
The DVP physical printer type is a different concept. Let's
say you have a special program for printing to your network
printer, called NETPRINT. You can create a DVP (DESQview Program
information File) with Change A Program that runs NETPRINT. Then
you can create a logical printer in PRINTCAP called, say, ``net''
which is a DVP-type printer. Whenever you print to the logical
printer ``net'', a window will be opened to run NETPRINT. The
background printing utilities will easily replace NETPRINT.
SEE ALSO
LPD(1dvsi), LPR(1dvsi), LPRM(1dvsi), LPQ(1dvsi), PRCC(1dvsi),
PRINTCAP(5dvsi)
DF(1dvsi) DF(1dvsi)
DVSI Manual
NAME
df - display free and used disk space
SYNOPSIS
df [<options>] [<drive list>]
DESCRIPTION
The DF utility will report the current free and used disk
space for each of the logical drives in the system. It
identifies networked, JOINed and SUBSTituted drives. Without a
<drive list> DF finds and displays information on all drives ``C:''
and higher.
If <drive list> is specified, DF report only on the drives the
list. The list must contain 1 or more drive names with no
separating blanks. Case is not important. For example, to
report only on drives A:, E: and F:, <drive list> would be ``AEF''
or ``A:E:F:''.
DF can be used outside of DESQview. However, only the ``-
q'', ``-t'', ``-w'' and <drive list> options are available.
DF is known to work with
■ Digital Equipment Corporation's PathWorks 3.0 and 4.0,
■ IBM PC Lan, and
■ Novell Netware.
If you successfully or unsuccessfully run DF on another network,
please let me know.
FIELDS
There are several columns of information presented for each
drive:
DR
The logical name of the drive, such as C:.
FLGS
Flags, indicating the drive type. The flags are
l Local drive
n Network drive
j JOINed drive
s SUBSTituted drive
TOTAL KBYTES
The total capacity of the drive in kilobytes.
KBYTES USED
The amount of space that is in use on the drive, in kilobytes.
KBYTES FREE
The available space on the drive, in kilobytes.
% USED
Percentage of total space on the drive that is in use.
VOLUME LABEL
The label given to the drive. If no label exists, ``(none)'' is
printed.
DF(1dvsi) DF(1dvsi)
DVSI Manual
MOUNTED ON
If drive is JOINed, this is the directory that the drive is
JOINed under. If the drive is a SUBST drive, this is the
directory that the drive letter refers to. If the drive is a
network drive, this field is the network drive name. Otherwise,
this field is the root directory name (like ``C:\''). The
``MOUNTED ON'' field can be replaced with ``CURRENT DIR'' if the
``-w'' option is used.
CURRENT DIR
The current directory field replaces the mounted on field if ``-
w'' is used. This column contains the current working directory
on each drive.
OPTIONS
-c<n>
Continuously update the list every <n> seconds. Normally, DF lists
the disk space and exits. This option is most useful when DF is
used in its own window. The value of <n> must be an integer
between 0 and 65535. See ``KEY BINDINGS'' in INTRO(1dvsi).
-r
Resize the window to fit exactly the number of drives in the
system. Useful with ``-c''.
-p
Print ``Press any key to continue...'' and wait for keystroke
before exiting.
-w
Replace the ``Mounted On'' field with ``Current Dir''.
-q
Quiet - does not print banner.
-t
Terse - does not print column headings.
-?
Launches DVSIHELP(1dvsi). The help program is also launched if
any invalid option is used.
CAVEATS
Using ``-w'' if DF is run continuously in its own window
with ``-c'' will only report on the current directories for that
window. DESQview maintains separate current directories for each
window.
BUGS
If using ``-c'' and ``-r'', the maximum size of the window
must be as large as the (max number of drives+1) or strange
things will happen.
The volume label on a JOINed drive is reported as "(none)".
This is a DOS bug.
DF(1dvsi) DF(1dvsi)
DVSI Manual
DIAGNOSTICS
See INTRO(1dvsi)
``Bad command line; help not available outside of DESQview''
An invalid option was found on the command line.
FILES
DF-PIF.DVP
DVP to use for opening DF from the Open Window menu.
SEE ALSO
INTRO(1dvsi), DVSIHELP(1dvsi)
DVSIHELP(1dvsi) DVSIHELP(1dvsi)
DVSI Manual
NAME
dvsihelp - Help for DVSI utilities
SYNOPSIS
dvsihelp [/s]
DESCRIPTION
DVSIHELP is a quick way to find the command line arguments
for a DVSI utility. The DVSIHELP utility displays a menu
containing the name and description of each ofthe DVSI programs.
Pressing ENTER will display the command line options to use for
the highlighted program. Use the arrow keys to navigate through
the menu.
DVSIHELP was compiled with Dave's Readme Compiler (DRC) by
David Harris, Dunedin, New Zealand.
The DVSI utilities launch DVSIHELP through DVSIHELP.DVP if
``-?'' is used or an invalid option is found.
OPTIONS
/s
Do not clear the screen or change the background.
BUGS
Unfortunately, DVSIHELP is not very nice to DESQview. It is
completely DESQview-oblivious, and writes directly to the screen.
Therefore, you must run it from the provided DVSIHELP.DVP or make
sure the window you run it in is set to ``Writes Directly to
Screen'' and ``Virtualize Text''. Non-386 users will have to
deal with it in full-screen mode. I'm working with the author of
the compiler to make it DESQview-aware.
DVSIHELP does not know about window sizes that are larger
than 25 lines, so it may put the cursor in the wrong place when
it terminates.
FILES
DH-PIF.DVP
DVP used to open DVSIHELP from the Open Window menu.
DVSIHELP.DVP
This file must exist in the same directory as the program that
launches DVSIHELP. To edit DVSIHELP.DVP, type ``INSTLAC
DVSIHELP.DVP'' at the command line or get DvpEdit (see
README.1ST). INSTALL.EXE will automatically put the proper
``Directory'' name into this file.
DVSIXDI(1dvsi) DVSIXDI(1dvsi)
DVSI Manual
NAME
dvsixdi - External Device Interface for DVSI
SYNOPSIS
In autoexec.bat:
[loadhi or loadhigh] dvsixdi.com [-p<n>] [-t]
DESCRIPTION
DVSIXDI is the heart of DVSI. It keeps track of the
processes that DESQview starts and stops, as well as the CPU time
of each process and other information. Basically, whenever
DESQview does something important, it calls DVSIXDI to record
what is happening.
DVSIXDI should be installed before DESQview is run. It is
best to put it in AUTOEXEC.BAT. Without the ``-t'' option, it
will take up about 1.4K of memory after it terminates. To
minimize the memory it requires, load it (and any other TSRs)
before you set your PATH and other environment variables.
Preferably, it should be loaded in high memory, but this is not
required.
DVSIXDI requires at least version 2.26 of DESQview. If you
have an earlier version, some of the DVSI programs will not work
because DESQview will not communicate with DVSIXDI.
If it loads successfully, the amount of Common Memory that
DVSIXDI will require is displayed. You must go into DESQview's
setup and set the Common Memory field to at least this many
kilobytes above the minimum value that SETUP will allow. If
there is not enough Common Memory, running any of the programs
that use DVSIXDI will display an error message and exit.
Since Common Memory is allocated in conventional memory, too
much of it will reduce your maximum window size. The ``-p''
option is provided to tailor DVSIXDI to your DESQview load.
Users of Mike Weaver's DVTree and DV Task Manager can use
DVSIXIDI.COM to replace Mike Weaver's DVTXDI.COM by using the ``-
t'' option. This causes DVSIXDI.COM to also act as DVTXDI.COM.
The code that emulates DVTXDI.COM is directly from Mike Weaver
and he tested the ``-t'' option. Using ``-t'' instead of
DVSIXDI.COM will save you about 1.9K over loading both
DVSIXDI.COM and DVTXDI.COM. With the ``-t'' option DVSIXDI.COM
will require 1.6K resident.
OPTIONS
-p<n>
Set the number of processes that DVSIXDI keeps track of to <n>. If
``-p'' is not specified, <n> defaults to 15. The value of <n> should
be a decimal number between 0 and 64. Processes started after <n>
processes exist (counting the DV System Task) will never be seen
by DVSIXDI. Once the number of processes drops below <n>, DVSIXDI
will start seeing new processes.
DVSIXDI will use 39*<n> bytes of Common Memory. The number
displayed on the DVSIXDI startup screen is rounded up to the next
integer kilobyte value.
-t
Act like Mike Weaver's DVTXDI.COM in addition providing support
for DVSI utilities.
DVSIXDI(1dvsi) DVSIXDI(1dvsi)
DVSI Manual
CAVEATS
Mike Weaver's DVTXDI will track up to 64 simultaneously-open
DESQview windows, but DVSIXDI -t will only track the amount
specified with ``-p'' (or 15 if not ``-p'' not used).
Loading DVTXDI.COM after DVSIXDI.COM will nullify ``-t''.
However, if DVSIXDI.COM with ``-t'' is loaded after DVTXDI.COM,
DVTXDI.COM will be ignored.
DIAGNOSTICS
DVSIXDI may display an error message and not load. If it does
not load, it sets the error level to 1. If DVSIXDI load
successfully, the DOS error level is set to 0. The possible
error messages are:
``Error: Already Installed''
You can only load DVSIXDI once.
``Error: No available slots''
You have too many TSRs loaded that use the Multiplex interrupt
2F. DVSIXDI cannot be loaded until an interrupt 2F slot is
available.
SEE ALSO
DVSTUFF(1dvsi), KILL(1dvsi), MEMSTAT(1dvsi), PERF(1dvsi),
PS(1dvsi), RUN(1dvsi), UPTIME(1dvsi), WN(1dvsi), DVSIXDI(2dvsi),
documentation provided with Mike Weaver's DV Tree and DV Task
Manager
DVSTUFF(1dvsi) DVSTUFF(1dvsi)
DVSI Manual
NAME
dvstuff - Stuff keystrokes into any window
SYNOPSIS
dvstuff [-d] [-e] <process id> [<key ...>]
DESCRIPTION
DVSTUFF will stuff keystrokes into any window as if they had
been typed by the user; if ``-d'' is used the keystrokes will be
sent to the DESQview menu. The <process id> argument must not be
present if ``-d'' is used. Any scripts that are attached to the
key are ignored.
The <process id> argument is a window handle, Switch Window
number, or Open Window keys. See INTRO(1dvsi). Using the handle
of the DV System Task is equivalent to ``-d''.
The <keys> argument is a list of the keystrokes to send to the
window. Most keys are sent as-is. That means that an ``A'' is
sent as an ``A'' and an ``a'' is sent as an ``a''. However some
keystrokes, like the function keys, cannot be inserted on the
command line.
To solve this problem DVSTUFF accepts ``metacharacters''.
Metacharacters are two- or three-character sequences that
represent another non-printable character. Using metacharacters
you can send function keys, cursor movement keys, alt-keys and
control keys to another window.
Spaces may be inserted on the command line for readability.
Since the space character is not sent as-is, it has its own
metacharacter: ``$s''.
If you don't specify any <key> argument, DVSTUFF reads
keystrokes from the standard input. You may pipe input to
DVSTUFF or get input from a file with the usual ``|'' and ``<''
characters. Input is terminated by pressing Control-Z and
hitting RETURN.
DVSIXDI 2.00 must be installed to use DVSTUFF.
METACHARACTERS
$S Shift the next key, ignored if key is not a function key
$A Alt the next key, ignored if key is not a function or
alpha key
$^ Control the next key
$F01 to
$F12 Function keys 1 through 12. The leading 0 must be
present.
$K0 to
$K9 Keypad 0 through 9.
$K. Keypad dot
$K* Keypad *
$K- Keypad -
$K/ Keypad /
$KE Keypad enter
$K+ Keypad +
$~<aass> Two-digit hex ASCII code in <aa> and two-digit scan code
in <ss>
$u Page up
$d Page down
$h Home
$i Insert
DVSTUFF(1dvsi) DVSTUFF(1dvsi)
DVSI Manual
$l Delete
$e End
$U up arrow
$D down arrow
$L left arrow
$R right arrow
$r ENTER or RETURN
$s space bar
$E Escape
$T tab
$B backspace
$$ Dollar sign
OPTIONS
-d
Send keystrokes to DESQview menu. If ``-d'' is used, the <process>
<id> must not be present.
-e
Simulate enhanced keyboard with $u, $d, $i, $l, $h and $e.
EXAMPLES
Use DVSTUFF to run PS in a Big Dos window with Open Window keys
``BD''
dvstuff bd PS $r
Use DVSTUFF to do a Rearrange-Hide
dvstuff -d R H
CAVEATS
If the process specified by <process id> is set to ``Runs In
Background=N'', the window will not act on the keys until you
switch to it.
Applications that read the keyboard directly or monitor the
shift states will not work properly with DVSTUFF.
SEE ALSO
INTRO(1dvsi), DVSIXDI(1dvsi), PS(1dvsi)
INSTALL(1dvsi) INSTALL(1dvsi)
DVSI Manual
NAME
install - Installation program for DVSI
SYNOPSIS
While running DESQview:
install
DESCRIPTION
INSTALL is the optional (but recommended) installation
program for DVSI. It is intended to be as flexible as possible.
Each of the installation steps may be skipped. INSTALL explains
the consequences of skipping each step.
The file README.1ST describes the manual installation
process. This process is essentially what INSTALL does
automatically.
FILES
INSTALL copies each file in the DVSI package to a user-specified
destination directory.
AUTOEXEC.DVS
Created by INSTALL as a template for the user to edit
AUTOEXEC.BAT.
DVSIHELP.DVP and PRCC.DVP
INSTALL changes the ``Directory'' field to the DVSI destination
directory.
SEE ALSO
The file README.1ST
KILL(1dvsi) KILL(1dvsi)
DVSI Manual
NAME
kill - Kill a DESQview process
SYNOPSIS
kill [-p] [-?] <process id>
DESCRIPTION
KILL ``kills'' a DESQview process. It works just like
``Close Window'' except that it will kill the process even if the
``Allow Close Window Command=N'' in the DVP file. This command
is dangerous, because you could easily lose data if you don't
save before using kill. It is much better to exit a program
(especially non-DESQview programs) from the program itself.
The process to be killed is unswapped, brought to the top,
and killed. Kill then displays the handle of the killed process.
KILL requires DVSIXDI 2.00 to be installed.
The <process id> argument identifies the window to be killed.
It can either be a window handle, a Switch Window number, or the
Open Window keys. See INTRO(1dvsi) for more information.
OPTIONS
-p
When the process is killed, print ``Press any key to
continue...'' and wait for a keystroke.
-?
Opens a DVSIHELP window.
SEE ALSO
INTRO(1dvsi), DVSIXDI(1dvsi), WN(1dvsi)
LPD(1dvsi) LPD(1dvsi)
DVSI Manual
NAME
lpd - line printer daemon
SYNOPSIS
lpd [-e<file>] [-l<file>] [-p<file>] [-c<file>] [-s]
DESCRIPTION
You should read BACKGROUND PRINTING(1dvsi) before reading
this man page if to get an overview of the printing suite.
The line printer daemon is the heart of the background
printing suite. Each of the LP-utilities communicate with LPD,
so they require that an LPD window be running.
For those of you not familiar with Unix, a ``daemon'' is a
program that runs in the background. It's kind of like a genie
in a bottle, just sitting there content to do nothing. However,
at any time you can ``make a wish'' and the genie-daemon will
fulfill that wish.
The LPD utility is a genie that can only fulfill wishes that
involve printing. In fact, its powers are pretty limited: it
maintains a list of files for printing, to which you can add a
file, delete a file, or view the list. The LPD-genie chugs away
in the background printing the top file on the list.
Unfortunately, this LPD-genie doesn't understand English, so
you can't type commands to it. Your translators are the
utilities LPR, LPRM, LPQ and PRCC.
Enough with the genie analogy. The sole purpose of LPD is
to print files. It does not accept keyboard commands. It only
accepts requests from the four other LP utilities.
LPD accepts requests to print to ``logical'' printers, and
maps these requests onto ``physical'' printers as discussed in
BACKGROUND PRINTING(1dvsi). The logical-to-physical printer
mapping is contained in the PRINTCAP file. You must edit the
PRINTCAP file with a standard text editor to define the printers
on your system.
In order to reduce memory overhead, LPD does not directly
read PRINTCAP. Instead, it opens a PRCC(1dvsi) window to compile
and send it the data in PRINTCAP. If PRINTCAP is updated, LPD
will not see the changes until PRCC is next run. See
PRINTCAP(5dvsi) for the PRINTCAP file format.
LPD is different that its Unix equivalent. In Unix, each
printer has its own list (commonly called a queue). With DVSI's
LPD, there is only one queue; but each job in that queue can go
to a different printer.
Only one copy of LPD can be running at a time. A running
LPD does not let another LPD start. A running LPD can be shut
down by typing ``lpd -s''.
LPD can be opened from a startup script, so it is always
active.
PHYSICAL PRINTERS
LPD knows about 4 types of physical printers:
LPT
A printer connected to LPT1 or LPT2.
COM
A printer connected to COM1 or COM2.
LPD(1dvsi) LPD(1dvsi)
DVSI Manual
FILE
This physical printer is actually not a printer. If you use the
FILE printer type, you also specify the name of a file or device
in PRINTCAP. Then, a file submitted with LPR is copied to this
file. The FILE printer is just like a ``print-to-file'' option
in an application.
DVP
The DVP printer type is again not actually a printer. In the
PRINTCAP file, you must specify the name of a DESQview Program
information File (DVP) created by Change a Program or another DVP
editor. When LPR submits a file, the filename is copied into the
``Program Parameters'' field and a window is opened to run the
program specified in the DVP. This physical printer can be used
to start network printer programs, etc. The launched program
must not print to a logical printer that maps onto the same DVP,
or infinite recursion will result.
For examples, see PRINTCAP(5dvsi).
OPTIONS
-e<file>
Change the error log file to <file>. The default is CON, which
means errors are printed in the LPD window.
-l<file>
Change the log file to <file>. The default is CON, which means
that messages are printed in the LPD window.
-p<file>
Read printer capabilities from <file>. The default is PRINTCAP.
-c<file>
Defines the printcap compiler's DVP, default is PRCC.DVP in the
current directory.
-s
Shut down another LPD window that is currently running.
DIAGNOSTICS
See INTRO(1dvsi)
The following errors are written to the error log file.
``Cannot start PRCC''
The printcap compiler could not be launched. Check the values in
PRCC.DVP.
``Printer <pr> doesn't exist''
An operation was attempted on printer <pr> which is not in
PRINTCAP.
``Cannot open <file>''
The specified file could not be opened by LPD.
LPD(1dvsi) LPD(1dvsi)
DVSI Manual
``Printer <pr> is out of paper''
The out-of-paper signal was seen on the LPT port onto which <pr>
maps.
``Printer <pr> is offline''
The offline signal was seen on the LPT port onto which <pr> maps.
``Printer <pr> I/O error''
An unidentified error was detected on the LPT port onto which <pr>
maps.
``Printer <pr> timed out''
The printer <pr> is not accepting characters.
``Error writing to device or file''
An error occurred while LPD was writing to a file or device.
``Cannot open DVP file''
LPD could not open the DVP for reading.
``Cannot start DVP''
DESQview returned an error when the DVP was launched.
``Cannot initialize printer <pr>, deleting''
A printer error occurred during initialization.
``Cannot open output device or file''
The output device or file could not be opened by LPD.
``Cannot delete <file>''
LPD could not delete the file <file>.
``Not enough system memory''
Allocate more system memory to the LPD window.
``Attempt to use R_RM, not supported''
You cannot specify ``lpr -r'' if the physical printer is type
DVP.
``PRCC exited with error''
PRCC found a syntax error in the PRINTCAP file. The current list
of printers that LPD knows about may be incomplete.
FILES
CON
Default device for log and error log.
LP-PIF.DVP
DVP used to open the LPD window from Open Window.
PRINTCAP
Default printer capabilities file.
PRCC.DVP
Default DVP for launching PRCC.
LPD(1dvsi) LPD(1dvsi)
DVSI Manual
DVSIHELP.DVP
Used to launch DVSIHELP if a bad option is given.
SEE ALSO
BACKGROUND PRINTING(1dvsi), DVSIHELP(1dvsi), LPR(1dvsi),
LPRM(1dvsi), LPQ(1dvsi), PRCC(1dvsi), PRINTCAP(5dvsi)
LPR(1dvsi) LPR(1dvsi)
DVSI Manual
NAME
lpr - Submit files to LPD for printing
SYNOPSIS
lpr [-P<printer>] [-n] [-z<n>] [-#<c>] [-r] [-f] [<file ...>]
DESCRIPTION
LPR submits the files to LPD for printing on the logical
printer <printer> defined in PRINTCAP. If ``-P'' is not specified,
the PRINTER environment variable is read. If it is not set, the
files are submitted to the logical printer ``lp''. There must
always be an ``lp'' printer in PRINTCAP.
The <file> argument can contain the wildcards ``*'' and ``?'',
and can contain the Unix-style directory delimiter ``/'';
however, the filename must not start with ``/'' or it will be
interpreted as an option.
Up to 20 files (after wildcard expansion) can be specified.
If no files are specified LPR reads from the standard input.
An invalid argument causes a DVSIHELP window to be opened.
OPTIONS
-P<printer>
Submit the file to logical printer <printer>. Defaults to the
value of the PRINTER environment variable or to ``lp''.
-n
Notify when the print job is completed. LPD pops up a small
window and beeps.
-z<n>
Set the pagelength to <n> lines. Overrides the value of ``pl'' in
PRINTCAP, but has no effect if ``sf'' is set.
-#<c>
Print <c >copies of each file.
-r
Delete (remove) the files when done printing. This option cannot
be used with logical printers that map onto the DVP physical
printer type.
-f
Tell LPD to print the file as fast as it can. Normally, LPD
tries to be nice to DESQview and not degrade system performance.
However, if another window is taking a lot of CPU time, the
printing may go very slow. The ``-f'' option speeds up printing
at the expense of system performance.
DIAGNOSTICS
See INTRO(1dvsi) and LPD(1dvsi)
``LPD daemon not present''
The LPD program must be running.
``Cannot access file <file>''
The specified file could not be opened and will not be submitted.
LPR(1dvsi) LPR(1dvsi)
DVSI Manual
``-r not supported on requested printer''
The printer is of type DVP.
FILES
PRINTCAP
Contains descriptions of the logical printers.
SEE ALSO
BACKGROUND PRINTING(1dvsi), LPD(1dvsi), LPRM(1dvsi), LPQ(1dvsi),
PRINTCAP(5dvsi)
LPRM(1dvsi) LPRM(1dvsi)
DVSI Manual
NAME
lprm - Remove jobs from the printer queue
SYNOPSIS
lprm [-P<printer>] [<job ...>]
DESCRIPTION
LPRM removed jobs from the printer queue that were
previously submitted by LPR. The job id's can be displayed with
LPQ and are printed when LPR submits the job.
The ``-P'' argument is ignored; it is provided for Unix
compatibility.
DIAGNOSTICS
See INTRO(1dvsi)
``LPD daemon not present''
The line printer daemon must be running.
SEE ALSO
INTRO(1dvsi), BACKGROUND PRINTING(1dvsi), LPD(1dvsi), LPR(1dvsi),
LPQ(1dvsi)
LPQ(1dvsi) LPQ(1dvsi)
DVSI Manual
NAME
lpq - List the jobs in the printer queue
SYNOPSIS
lpq [-P<printer>] [+[<n>]] [-c<n>] [-q] [<job ...>]
DESCRIPTION
The LPQ command displays a list of the current print jobs
that are queued to LPD. The list is somewhat similar to its Unix
equivalent. If there are no jobs in the queue, ``no entries'' is
printed.
The list contains one line for each file in the queue; a job
containing multiple files spans more that one line.
The ``-P'' argument is ignored; the entire queue is
displayed. If one or more jobs is specified, only those jobs are
displayed.
FIELDS
The columns displayed include
RANK
The number of jobs ahead of this job. The currently-printing job
is labelled ``active''.
PRINTER
The logical printer to which this job will be sent.
JOB
The job to which this file belongs. Use this number with LPRM.
FILE
The file name of the file to be printed.
SIZE
Number of bytes in the file multiplied by the number of copies
that will be printed.
%DONE
The percentage of the file that has been sent to the printer.
OPTIONS
-P<printer>
Ignored; provided for Unix compatibility.
+[<n>]
Clear the screen and continuously display the queue, updating the
list every <n> seconds. If <n> is not given, the queue is re-
displayed every 30 seconds. If the queue is emptied, LPQ will
terminate.
-c<n>
Almost a synonym for +<n>; <n> must be specified. Also, LPQ will not
terminate when the queue is emptied.
-q
Quiet - don't print the banner
LPQ(1dvsi) LPQ(1dvsi)
DVSI Manual
DIAGNOSTICS
See INTRO(1dvsi)
``LPD daemon not running''
LPD must be running.
``no entries''
There are currently no jobs in the queue.
FILES
LQ-PIF.DVP
DVP used to launch LPQ from the Open Window menu.
SEE ALSO
INTRO(1dvsi), BACKGROUND PRINTING(1dvsi), LPD(1dvsi), LPR(1dvsi),
LPRM(1dvsi)
MEMSTAT(1dvsi) MEMSTAT(1dvsi)
DVSI Manual
NAME
memstat - DESQview memory status
SYNOPSIS
memstat [-c<n>] [-p] [-q] [-t] [-?]
DESCRIPTION
MEMSTAT is an alternative to DESQview's Memory Status
program. It takes up much less CPU time and screen space,
although it requires more memory than Memory Status. It can also
be used at the DOS command line, while Memory Status cannot.
MEMSTAT displays the same information as memory status, and
adds another column. The output looks like this:
TYPE TOTAL LARGEST AVAILABLE USED
Conv 590K 345K 375K 36%
Exp 2912K 576K 1184K 59%
Com 25600 10668 10804 58%
The columns include
TYPE
The type of memory described in this row. ``Conv'' is
conventional memory, or memory between 0 and 640K. ``Exp'' is
expanded (EMS or EEMS) memory. ``Com'' is DESQview's common
memory area.
TOTAL
The total amount of memory in the system.
LARGEST
The largest block of available memory.
AVAILABLE
The total amount of memory currently available.
USED
The percentage of memory that is currently being used.
OPTIONS
-c<n>
Continuously update the statistics every <n> seconds. Normally,
MEMSTAT lists the statistics and exits. This option is most
useful when MEMSTAT is used in its own window. The value of <n>
must be an integer between 0 and 65535. See ``KEY BINDINGS'' in
INTRO(DVSI1) for a list of the valid keystrokes in ``-c'' mode.
-p
When the listing is complete, print ``Press any key to
continue...'' and wait for a keystroke. Helpful if you are not
using ``-c'' and you want to use MEMSTAT in its own window.
-q
Quiet - does not print banner.
-t
Terse - does not print column headings.
MEMSTAT(1dvsi) MEMSTAT(1dvsi)
DVSI Manual
-?
Launches DVSIHELP.
FILES
MT-PIF.DVP
DVP used to open MEMSTAT from the Open Window menu.
SEE ALSO
INTRO(1dvsi), DVSIHELP(1dvsi)
PERF(1dvsi) PERF(1dvsi)
DVSI Manual
NAME
perf - DESQview CPU performance statistics
SYNOPSIS
perf [-c<n>] [-p] [-q] [-t] [-?]
DESCRIPTION
PERF displays DESQview performance statistics. It requires
DVSIXDI 2.00 to be installed.
The PERF statistics are system-wide statistics and represent
a summary of some of the information presented by PS(1dvsi). Two
columns of information are presented. The first column, labelled
INSTANT, gives you a picture of the current system performance.
The second column, labelled TOTAL represents the long term system
performance.
Here's a sample PERF display:
INSTANT TOTAL
CPU Utilization 5% 36%
Task Switches 10 500
Task Switches/s 1.0 1.5
Time (1/100 s) 10.11 2:23:45
The INSTANT column statistics are measured and averaged over
the last 10 seconds, while the TOTAL column is measured and
averaged over the entire time DESQview has been running. Each
row of the display is explained below.
FIELDS
CPU Utilization
The percentage of time spent running programs other than the DV
System Task.
Task Switches
Number of times that DESQview has switched to a different task.
This number can be increased or decreased with the Tune
Performance-Set Foreground/Background ticks menu.
Task Switches/s
Number of task switches per second during the measurement period.
Time
The amount of time in seconds of the measurement period. The
TOTAL column is expressed in hh:mm:ss notation.
OPTIONS
-c<n>
Continuously update the statistics every <n> seconds. Normally,
PERF lists the statistics and exits. This option is most useful
when PERF is used in its own window. The value of <n> must be an
integer between 0 and 65535. See INTRO(1dvsi) for a description
of the keystrokes available in ``-c'' mode. A good value for <n>
is 10 seconds, since DVSIXDI updates the INSTANT information
every 10 seconds.
-p
When the listing is complete, print ``Press any key to
continue...'' and wait for a keystroke. Helpful if you are not
using ``-c'' and you want to use perf in its own window. Will
work with the ``-c'' option.
PERF(1dvsi) PERF(1dvsi)
DVSI Manual
-q
Quiet - does not print banner.
-t
Terse - does not print column headings.
-?
Launches DVSIHELP.
BUGS
Integer math is used for the calculations; truncation rather
than rounding occurs in the least significant digit.
The INSTANT column gives strange numbers during the first 10
seconds after DESQview is started, and can be up to 10 seconds
old.
FILES
PF-PIF.DVP
DVP used to launch MEMSTAT from the Open Window menu.
SEE ALSO
DVSIHELP(1dvsi), DVSIXDI(1dvsi), PS(1dvsi)
PRCC(1dvsi) PRCC(1dvsi)
DVSI Manual
NAME
prcc - PRINTCAP compiler
SYNOPSIS
prcc <infile>
DESCRIPTION
PRCC compiles <infile> as a printer capabilities file and
sends the results to a currently-running LPD. The file <infile> is
usually PRINTCAP. PRCC is launched automatically when LPD starts
through the PRCC.DVP file.
When LPD receives the compiled <infile>, it removes any
previously defined printers before adding the new printers. If a
change is made to PRINTCAP, PRCC must be run to update the active
LPD.
See PRINTCAP(5dvsi) for a description of the PRINTCAP file.
DIAGNOSTICS
If PRCC encounters an error in <infile>, it prints an error
message and line number,and exits with DOS error level set to 1.
If PRCC fails, the printer list sent to LPD will be incomplete.
``LPD Daemon not present''
The LPD program must be running.
FILES
PRINTCAP
The usual printer capabilities file
PRCC.DVP
The DVP used to launch PRCC from LPD. From the command line,
type INSTLAC PRCC.DVP to edit it, or get DvpEdit (see
README.1ST). The INSTALL program automatically fills in the
``Directory'' field.
SEE ALSO
BACKGROUND PRINTING(1dvsi), LPD(1dvsi), PRINTCAP(5dvsi)
PS(1dvsi) PS(1dvsi)
DVSI Manual
NAME
ps - DESQview process status
SYNOPSIS
ps [<options>] [<process id>]
DESCRIPTION
PS provides information on the current DESQview windows. It
requires DVSIXDI 2.00 to be installed. Without the ``-l''
option, PS's output looks like this:
HNDL SW TK MAP TTLMEM SYSMEM L SYS CPU TIME CPU UT KY NAME
d662 ? 0 95f6 641680 278512 276144 02:23:42 89.2% DV System Task
cf9b 1 1 0fe8 16464 1632 1088 00:00.05 0.0% CC Clock
d027 2 1 1c34 ?????? Swappds ?????? 01:07.64 5.1% WP WordPerfect 5
cfe1 3 1 1b52 Swappd 592 1088 00:03.44 6.7% MF QOS Manifest
???? ? 0 0c5d ?????? ?????? ?????? 00:00.00 0.0% KT (starting)
Question marks in a column represent unknown information.
In the ``WordPerfect 5'' line, the memory information is not
available because the process is swapped to disk. In the
``(starting)'' line, most of the information is unknown because
that process has not completed its initialization.
If <process id> is specified, PS only displays information on
that processes. If the process does not exist, PS terminates
with DOS ERRORLEVEL set to 1. The <process id> can be the window
handle, the Switch Window number or the Open Window keys.
FIELDS
The columns in the PS display include:
HNDL
The hexadecimal segment of the process's handle, similar to
UNIX's PID.
SW
The number appearing on the Switch Windows menu for this task.
Applications which are "orphaned" and do not appear on the Switch
Windows menu, as well as the DV system task, will contain a ``?''
in this column. If more than 9 windows are open, the windows
above 9 are labelled ``10'', ``11''... rather than ``A'',
``B''...
TK
The number of separate tasks, including itself, that the
application has started. For most programs, this will show 1,
but some DESQview-specific programs may use more than one
task.
MAP
The hexadecimal mapping context of the application. This number
is used with a DESQview API call to guarantee that the program is
in conventional memory.
TTLMEM
The total memory, in bytes, used by the application. If
``Swappd'' appears in this column, the process's memory is
swapped out. If system memory is swapped out, a ``??????'' will
appear in the field because the real value cannot be determined.
The TTLMEM value is constant and represents the amount of
PS(1dvsi) PS(1dvsi)
DVSI Manual
conventional memory required by the process. See ``MEMORY''
below.
SYSMEM
The remaining system memory, in bytes, available to application.
If ``Swappd'' appears in this column, the process's system memory
is swapped out. If an ``s'' is appended to the value, the system
memory resides in shared memory (see ``Wordperfect 5'', above).
See also ``MEMORY'' below.
L SYS
The largest block of system memory, in bytes, available to the
application. A "??????" implies that the value cannot be
determined. See ``MEMORY'' below.
CPU TIME
Approximate amount CPU Time accumulated by the process. If less
than an hour, it is expressed in minutes:seconds.hundredths
format. If more than an hour, it is expressed in
hours:minutes:seconds format. The time is actually only accurate
to about 6/100 of a second.
CPU UT
The number represents how much load the window is putting on the
system at the current moment. It is calculated by counting the
amount of CPU time the window receives in a 10-second interval.
This number is the fraction of that 10 second interval that the
process actually had the CPU.
Example: if a process accumulated 6 seconds of CPU time in
the last 10 seconds of real time, its CPU UT column will read
``60%''.
The CPU UTilization number for the DV System Task is unused
CPU time.
KY
The keys used to open the application.
NAME
The name of the application, as shown on the window's frame. If
``(starting)'' is displayed here, the process has not completed
its initialization. Display of ``(starting)'' processes can be
suppressed with the ``-s'' option.
PS(1dvsi) PS(1dvsi)
DVSI Manual
If the ``-l'' option is used, the output looks a little messier:
HNDL SW TK MAP TTLMEM SYSMEM L SYS CPU TIME CPU UT KY NAME
kbd mbx obq cursor positn visible logcl dispd
d3e2 ? 0 0249 654016 384752 354128 01:12:30 97.2% DV System Task
014d d3e2 0197 ( 1,17) ( 0,56) ( 0, 0) 17x24 17x24
ce55 ? 1 1044 16448 1632 1088 00:00.06 0.0% CC Clock
014d ce55 0197 ( 0,33) (58,15) ( 0, 0) 1x45 1x35
cefe 2 1 1aca 589808 480 432 00:12.45 0.0% BD Big DOS
014d cefe 0197 (39, 6) ( 0, 0) ( 0, 0) 60x80 60x80
cf4f 3 1 1fe0 32736 208 208 00:03.14 2.8% PS DVSI ps
014d cf4f 0197 (16,15) (11, 0) ( 0, 0) 50x80 28x80
The additional columns in the second line for each process are:
KBD MBX OBQ
The hex offsets for the process's default keyboard, mailbox and
objectq. The segments are the same as the process's handle.
CURSOR
The position of the cursor relative to the window's origin, (row,
column).
POSITN
The upper left corner of the window on the screen, (row, column).
VISIBLE
The coordinate of the upper left corner of the displayed window,
(row, column). This number can be changed by using ``Rearrange -
Scroll''.
LOGCL
Logical, or maximum, size of the window, in rows by columns.
DISPD
Displayed size of the window, in rows by columns.
MEMORY
Using the values listed in the TTLMEM and SYSMEM columns, a
program's memory usage can be optimized. The TTLMEM column
represents the total number of bytes of conventional memory that
the program requires. This includes explicit memory declared in
the Change A Program ``Memory'' field, explicit System memory
declared in the ``System Memory'' Change A Program field, and
System Memory allocated by DESQview to store the text screen,
controlled by the ``Maximum Width'' and ``Maximum Height''
fields.
The SYSMEM column represents the number of bytes of System
Memory REMAINING. If this number stays high while running the
program, you can safely decrease the ``System Memory'' field in
Change A Program. To trim it down even more, decrease the
maximum height and width of the window. Every byte you take away
subtracts one byte from the TTLMEM column, unless you are using
PS(1dvsi) PS(1dvsi)
DVSI Manual
the ``Maximum Memory'' field in Change A Program. In that case,
you maximum window memory size increases.
OPTIONS
-c<n>
Continuously update the list every <n> seconds. Normally, PS lists
the status and exits. This option is most useful when PS is used
in its own window. The value of <n> must be an integer between 0
and 65535 (I don't know why you'd want to wait 18 hours, but you
can!). While in the ``-c'' mode, certain keystrokes have special
meanings. See ``KEY BINDINGS'' in INTRO(1dvsi) for more
information.
-p
When the listing is complete, print ``Press any key to
continue...'' and wait for a keystroke. Helpful if you are not
using ``-c'' and you want to use PS in its own window. ``-p''
will work with the ``-c'' option.
-d<path>
Ignored. Provided for compatibility with previous version of
DVSI. PS no longer uses DESQVIEW.DVO; it gets window names
directly from the window.
-r
Resize the window according to the number of processes in the
list. The window is made 80 columns wide and high enough for all
the processes to be displayed, and is moved left to column 0.
If using ``-c'' and the number of processes changes, the window
size is changed also.
-l
Long listing: more information than you really wanted to know
about each process.
-s
Do not print processes that would display ``(starting)''.
-q
Quiet - does not print banner.
-t
Terse - does not print column headings.
-?
Launches DVSIHELP.
SEE ALSO
INTRO(1dvsi), DVSIHELP(1dvsi), DVSIXDI(1dvsi)
RUN(1dvsi) RUN(1dvsi)
DVSI Manual
NAME
run - Open one or more windows from the command line
SYNOPSIS
run [-v] <program> [<program options>] [; [<launch options>]
[<program...>]]
DESCRIPTION
RUN will one or more programs in one or more windows. It is
capable of running DVP, COM, EXE, and BAT files.
The <program> is searched for in the current directory or in
the drive and directory specified in <program> first, according to
the search strategy explained below. If <program> is not found AND
a drive or directory was not specified, each directory in the
environment variable ``PATH'' is searched using the search
strategy outlined below. If <program> is still not found, RUN
fails with DOS error level 1.
The search strategy is very similar to COMMAND.COM's search
strategy. If <program> contains an extension (e.g. ``.DVP''), then
the filename must match exactly. However, if no extension is
specified, RUN looks first for <program>.DVP, then <program>-PIF.DVP,
then <program>_-PIF.DVP, then <program>.BAT, then <program>.COM and
finally <program>.EXE. If no match was found, RUN continues with
the next directory as described above.
With the ``-v'' option, RUN ignores ``.BAT'', ``.COM'' and
``.EXE'' in the search.
To run non-DVP type programs, RUN uses ``RUN_DEF.DVP'' which
must exist in the same directory as RUN.COM. Users can edit this
DVP to suit their needs; it makes very conservative assumptions
about the program. Note that RUN overrides the ``Memory Size''
and ``Maximum Program Memory Size'' fields so changing these will
have no effect. See ``NON-DVP PROGRAMS'' below for more
information.
Any <program options> override any options in the DVP.
Otherwise, the options in the DVP are used.
RUN can launch more than one program. Programs are
separated by the ``;'' character, which must be completely
separated from anything else by white space. If a ``;'' must be
passed as a program option, use ``;;'' instead.
Immediately following the white space after the ``;'', zero
or more launch options may be specified. These options modify
how the program is run.
Following the launch options another <program>, <program>
<options> and <launch options> can be specified. There is no limit
to the number of programs that can be started with one RUN
command.
NON-DVP PROGRAMS
RUN has the ability to launch COM, EXE and BAT programs, but
it must make conservative assumptions about the program's
operation. Most of the assumptions can be overridden by modifying
RUN_DEF.DVP or by using launch options.
The filename (without the path) becomes the title on the
window.
COM programs are run with 64K of memory. BAT programs are
run with a minimum of 128K memory and a maximum of 640K memory.
Memory requirements for an EXE program are calculated from the
EXE header. However, you may want to use the ``-m'' launch
options to guarantee that enough memory will be available to run
RUN(1dvsi) RUN(1dvsi)
DVSI Manual
the program.
COM and EXE windows have ``Close on Exit'' set to ``Y''; BAT
files are run with the same field set to ``N''.
The ``Directory'' field is set to the directory where the
program is found and only the filename (without the path) is
placed in the ``Program Path'' field.. However, if ``-d'' is
specified, ``-d''-specified directory is placed in the
``Directory'' field and the full program pathname is copied into
``Program Path''.
All other DVP fields are read from the RUN_DEF.DVP file.
Any launch options override any value that RUN or RUN_DEF.DVP
uses.
OPTIONS
-v
Only search for DVPs and ignore COM, EXE and BAT files.
LAUNCH OPTIONS
-e
Signals the end of launch options. Not required unless the next
<program> starts the with character ``-'' or ``/''.
-1o
Do not launch the program if a window with same Open Window keys
is running.
-1n
Do not launch the program if a window with same Program Name is
running.
-n<name>
Assign <name> to the program after it is launched. The value of
<name> is used with ``-1n''.
-w<n>
Wait <n> seconds before launching the next program. The wait
occurs before the window is hidden with ``-h''.
-h
Hide the window.
-m[<min>[:<max>]]
Set the minimum memory value to <min> and the maximum memory value
to <max>. The values of <min> and <max> must be in kilobytes.
-b
Block RUN until the new program exits. With ``-b'', RUN will not
launch the next program or return to DOS until the new window is
closed. RUN may not respond for up to 5 seconds after the
program terminates.
-=<offset>=<value>
Sets the byte at the hexadecimal offset <offset> to the hexadecimal
value <value> in the DVP.
See DVP(5dvsi) for the format of the DVP file.
RUN(1dvsi) RUN(1dvsi)
DVSI Manual
"-|<offset>=<value>"
Logically OR the byte at the hexadecimal offset <offset> with the
hexadecimal value <value> in the DVP. See DVP(5dvsi) for the
format of the DVP file. You must enclose at least the ``|''
character in quotes so COMMAND.COM doesn't think it is a pipe
character.
-&<offset>=<value>
Logically AND the byte at the hexadecimal offset <offset> with the
hexadecimal value <value> in the DVP. See DVP(5dvsi) for the
format of the DVP file.
EXAMPLES
Assume KT.DVP exists in the current directory, WP-PIF.DVP exists
in C:\DV which is in the PATH, and KT-PIF.DVP also exists in the
current directory.
C:\> run kt (launches KT.DVP)
C:\> run kt-pif (launches KT-PIF.DVP)
C:\> run wp (launches C:\DV\WP-PIF.DVP)
C:\> run kt ; -h wp (launches and hides KT.DVP, launches WP-
PIF.DVP)
C:\> run kt ; -w4 wp (launches and hides KT, waits 4 seconds,
launches WP)
C:\> run kt ; -w10 -h wp (launches and hides KT, waits 10
seconds, hides KT, launches WP)
Assume KT.DVP and KT.EXE both exist in the current directory.
C:\> run kt (launches KT.DVP)
C:|> run kt.exe (launches KT.EXE)
DIAGNOSTICS
``Cannot open <file>''
<File> could not be opened for reading.
``Cannot launch <file>''
DESQview returned an error when the program was launched.
FILES
RUN_DEF.DVP
The template DVP used to launch EXE, COM and BAT programs.
*.DVP
DESQview Program information File, which describes a program to
DESQview.
*.COM, *.EXE, *.BAT
DOS program files that RUN can launch.
SEE ALSO
DVP(5dvsi)
UPTIME(1dvsi) UPTIME(1dvsi)
DVSI Manual
NAME
uptime - Print amount of time DESQview has been running
SYNOPSIS
uptime [-p] [-q] [-t] [-?]
DESCRIPTION
UPTIME reports the amount of time that DESQview has been
running and the time DESQview was started.
UPTIME requires DVSIXDI 2.00 to be installed.
OPTIONS
-p
After the time is displayed, print ``Press any key to
continue...'' and wait for a keystroke.
-q
Quiet - does not print banner.
-t
Terse - does not print extra text, and prints run time as
hh:mm:ss.hh.
-?
Launches DVSIHELP
SEE ALSO
INTRO(1dvsi), DVSIHELP(1dvsi), DVSIXDI(1dvsi)
WN(1dvsi) WN(1dvsi)
DVSI Manual
NAME
wn - Manipulate DESQview windows
SYNOPSIS
wn [-?] <command> <command-options> [<process id>]
DESCRIPTION
WN contains a set of commands for manipulating DESQview
windows. It gives much of the functionality of the DESQview
menus at the command line. WN, unlike other command-line
DESQview window manipulators, can work with ANY window, not just
the current window.
Commands are case-insensitive and may be abbreviated to one
or two characters. Some commands require arguments; these follow
the command.
The <process id> specifies the window to operate on. If
<process id> is omitted, the window in which WN is run is used.
The ``KILL'' command requires <process id>. The <process id> can be
a window handle, a Switch Windows number, or the Open Window
keys. For more information, see INTRO(1dvsi).
A suspended or hidden window may be seen again by using
``RAISE'' or ``TOP''.
OPTIONS
-?
Launches DVSIHELP
COMMANDS
Command abbreviations are listed in parenthesis following the
command.
KILL (K)
Kill the window. Operates exactly like KILL(1dvsi). The <process>
<id> must be specified; the current window cannot be killed unless
its <process id> is explicitly used.
RAISE (R)
Bring the window to the top of the window stack and give it the
keyboard.
LOWER (L)
Put window at the bottom of the window stack.
TOP (T)
Bring window to the top of the window stack but do not give it
the keyboard. The window may not be entirely uncovered because
DESQview requires that the window with the keyboard must be
entirely uncovered.
HIDE (H)
Hide the window just like ``Rearrange - Hide''.
SUSPEND (SU)
Hide the window and don't give it any CPU time.
FRAME (FR)
Turns the window's frame on or off. Requires an argument:
FRAME Y Turn frame on
FRAME N Turn frame off
WN(1dvsi) WN(1dvsi)
DVSI Manual
FOREONLY (FO)
Does or doesn't allow window to run in the background. Requires
an argument:
FOREONLY Y Don't run in background
FOREONLY N Allow running in background
MBOX <name> (M)
Give the window's default mailbox the name <name>. The <name>
argument is required.
SIZE <r c> (SI)
Make the window <r> rows high and <c> columns wide. If a ``-'' is
used in place of <r> or <c>,the size in that direction is unchanged.
Both arguments are required. Setting the window size to the
current screen size will ``zoom'' the window.
NAME <name> (N)
Change the window's title to <name>. The argument is required.
The maximum name length is 30 characters. Additional characters
are ignored.
SEE ALSO
INTRO(1dvsi), DVSIHELP(1dvsi), DVSIXDI(1dvsi), KILL(1dvsi)
DVSIXDI(2dvsi) DVSIXDI(2dvsi)
DVSI Manual
NAME
DVSIXDI - Get info on DESQview processes
SYNTAX
mov AX, 0DE01h
mov BX, 7575h
mov CX, <function>
int 2Fh
DESCRIPTION
DESQview does not provide any API call to get a list of the
current processes. Fortunately, it does provide a hook by which
a TSR like DVSIXDI can keep track of the current open windows.
The purpose of DVSIXDI is to allow programs to easily get a
list of the processes and information on each process that is not
otherwise available. I decided to publish the programmer
interface so that other programmers wouldn't have to go through
all the work to create an XDI of their own.
You can use the interface in any way you choose. However,
you cannot include DVSIXDI.COM as part of any package you
distribute, and you cannot include any programs you write in the
DVSI package. See README.1ST for more information.
Make your program DVSIXDI-version-aware, because I may make
changes in the future that could break your program. Every
attempt will be made to maintain compatibility with earlier
versions (I don't want to rewrite all my code either!), but I
can't guarantee that I won't make significant changes. However,
I do guarantee that functions 0000h and 0004h will always be
compatible.
FUNCTIONS
The value of <function> can be
0000h
Installation check.
ENTRY:
nothing
EXIT:
AX=00FFh if DVSIXDI is installed
0003h
Get application records
ENTRY:
(v1.10+) Should be in a DESQview critical section on entry
if the application records will be read (see below).
EXIT:
AX=0 if error occurred
AX=1 if OK
BX=Last instantaneous time length (v1.10+)
CX=number of records with valid window handles
DX=number of ``(starting)'' records (v2.00+)
ES:DI pointer to array of all application records (see
``APPLICATION RECORDS'')
SI=value of DVSIXDI's ``-p'' argument (v2.00+)
(v1.10+) ES:DI points to the actual DVSIXDI data structure
in use. The application should enter a DESQview critical
section before making this call, make the call, copy the
DVSIXDI(2dvsi) DVSIXDI(2dvsi)
DVSI Manual
records, and end the DESQview critical section. In (v1.x),
there are 15 total records; (v2.00+) has the number of
records reported in SI.
(v1.00) ES:DI points to a copy of the records in allocated
Common Memory which the caller should deallocate when done.
Only the currently valid records are placed in this buffer.
The number of records in the buffer is reported in CX.
(v1.11+) BX is in units of 1/18.206 seconds
(v1.10) BX is in units of 1/100 seconds
0004h
Get version
ENTRY:
nothing
EXIT:
AH=Major version
AL=Minor version (0Ah=.10, etc.)
0005h (v1.10+)
Get time since DV start
ENTRY:
nothing
EXIT:
DX:AX 1/100s since DV start (v1.10)
DX:AX 1/18.206s since DV start (v1.11+)
0006h (v1.10+)
Get task switches
ENTRY:
nothing
EXIT:
CX=number of task switches during last instantaneous time
DX:AX=total number of task switches since DV start
APPLICATION RECORDS
Function 0003h returns a pointer to an array of application
records. These records contain information on each currently-
running process. The format of these records are
(v1.00)
Offset Size Description
00h BYTE Flags
01h WORD Offset into DESQVIEW.DVO of programs's record if
program started from Open Windows menu; else undefined
(this was a bug).
03h WORD Switch windows number
05h WORD Segment of handle
07h WORD Number of tasks owned by process
09h WORD Mapping context of process
0Bh DWORD Hook for other programs
(v1.10-v2.00)
Offset Size Description
00h BYTE Flags
DVSIXDI(2dvsi) DVSIXDI(2dvsi)
DVSI Manual
01h WORD Open Window keys
03h WORD Switch window number
05h WORD Segment of handle
07h WORD Number of tasks owned by process
09h WORD Mapping context
0Bh DWORD Time of process start relative to DV start
0Fh DWORD Time that process last got CPU relative to DV
start
13h DWORD Time that process last gave up CPU relative to DV
start
17h DWORD Accumulated CPU time
1Bh DWORD Accumulated CPU time instantaneous number of
seconds ago
1Fh DWORD Accumulated CPU time over last instantaneous time
slice
23h DWORD Hook for other programs
The Flags byte:
bit 7 Record contains a valid process id
bit 6 Record is allocated: if bit 7 not set, is
``(starting)'' and only offsets 01h and 09h are valid
(v2.00+)
Reserved, 0 (v1.x)
bit 5 This application is currently owns the CPU (v2.00+)
Reserved, 0 (v1.x)
bit 4 Reserved, 0
bit 3 This process is the DV System Task
bit 2 Reserved, 0
bit 1 Reserved, 0
bit 0 Reserved, 0
(v1.10) The times at offsets 0Bh through 23h are in 1/100s
(v1.11+) The times at offsets 0Bh through 23h are in 1/18.206s
SEE ALSO
DVSIXDI(1dvsi), PS(1dvsi), the file README.1ST
DVP(5dvsi) DVP(5dvsi)
DVSI Manual
NAME
DVP - DESQview Program information File
DESCRIPTION
The DVP file is used by RUN to launch programs, similar to
Open Window. With the ``-='', ``-|'' and ``-&'' individual bytes
can be changed on the fly.
This description is reprinted with permission from Release
28 of Ralf Brown's Interrupt list, copyright 1989, 1990, 1991 by
Ralf Brown.
Offset Size Description
00h BYTE reserved (0)
01h BYTE checksum of bytes 02h through 170h
02h 30 BYTEs blank-padded program title
20h WORD maximum memory to allocate to partition in K
22h WORD minimum memory required in K
24h 64 BYTEs ASCIZ program pathname
64h BYTE default drive letter ('A',...)
65h 64 BYTEs ASCIZ default directory name
A5h 64 BYTEs ASCIZ program parameters
E5h BYTE initial screen mode (0-7) (see also offset 189h)
E6h BYTE number of text pages used
E7h BYTE number of first interrupt to save
E8h BYTE number of last interrupt to save
E9h BYTE rows in virtual screen buffer
EAh BYTE columns in virtual screen buffer
EBh BYTE initial window position, row
ECh BYTE initial window position, column
EDh WORD system memory in K
EFh 64 BYTEs ASCIZ shared program name
12Fh 64 BYTEs ASCIZ shared program data file
16Fh BYTE flags1
bit 7: writes text directly to screen
bit 6: runs in foreground only
bit 5: uses math coprocessor
bit 4: accesses system keyboard buffer directly
bits 3-1: reserved (0)
bit 0: swappable
170h BYTE flags2
bit 6: uses command-line parameters in field at
A5h
bit 5: swaps interrupt vectors
---information unique to .DVP files---
171h 2 BYTEs keys to use on open menu
173h WORD size of script buffer in bytes
175h WORD automatically give up CPU after this many tests
for keyboard input in one clock tick (default 0 =
never)
177h BYTE nonzero = "uses own colors"
178h BYTE nonzero if application swappable
179h 3 BYTEs reserved (0) according to Quarterdeck
documentation in actual .DVP files, frequently 01h
17Ch BYTE nonzero to automatically close on exit
17Dh BYTE nonzero if copy-protect floppy is required
DVP(5dvsi) DVP(5dvsi)
DVSI Manual
---information unique to DESQview 2.0+---
17Eh BYTE .DVP version number
00h DESQview 1.2+
01h DESQview 2.0+
02h DESQview 2.2+
17Fh BYTE reserved (0)
180h BYTE initial number of rows in physical window
181h BYTE initial number of columns in physical window
182h WORD maximum expanded memory to allow, in K
184h BYTE flags3
bit 7: automatically assign window position
bit 5: maximum memory value has been specified
bit 4: disallow "Close" command
bit 3: foreground-only when doing graphics
bit 2: don't virtualize
bit 1: ??? set by DV 2.31 when "Runs in
Background" = "D"
185h BYTE keyboard conflict level (0-4 for DV<2.26, 00h-0Fh
for DV2.26+)
186h BYTE number of graphics pages used
187h WORD extra system memory size
189h BYTE initial screen mode (FFh = default) (overrides
offset E5h)
---information unique to DESQview 2.2+---
18Ah BYTE serial port usage
FFh uses all serial ports
00h no serial ports
01h only COM1
02h only COM2
18Bh BYTE flags4
bit 7: automatically close application on exit if
.COM or .EXE specified
bit 6: swappable if not using serial ports
bit 5: start program with window hidden (v2.26+)
bit 4: start program in background (v2.26+)
bit 3: virtualize text
bit 2: virtualize graphics
bit 1: share CPU when foreground
bit 0: share EGA when foreground and zoomed
18Ch BYTE protection level for 386 machines
18Dh 19 BYTEs reserved (0)
SEE ALSO
RUN(1dvsi)
PRINTCAP(5dvsi) PRINTCAP(5dvsi)
DVSI Manual
NAME
PRINTCAP - printer capabilities file
DESCRIPTION
The PRINTCAP file contains entries that describe each
logical printer available to LPD. It is read by PRCC(1dvsi) and
sent to LPD.
The format of PRINTCAP is very similar to the Unix
equivalent. Each entry contains tokens delimited by the ``:''
character. The null token is ``::''.
Each line in the PRINTCAP file is either blank, a comment
line a printcap entry, or a continuation of a printcap entry.
The comment character is ``#'' and must be in the first column.
A printcap entry is continued by terminating the previous line
with ``\''.
The first token in an entry is the logical printer name. At
least one entry must be named ``lp''. Multiple printer names for
one entry is NOT currently supported.
The remaining tokens are described in ``TOKENS'', below.
Tokens can be of three types: boolean, string, or number.
Boolean tokens do not need an argument; the presence of the token
implies TRUE and the absence implies FALSE. String tokens must
be concatenated with ``=<str>:'' where <str> is the string argument.
Number tokens must be concatenated with ``#<num>'' where <num> is the
value to assign to the token.
The string tokens ``hr'' and ``tr'' can have metacharacters
embedded. The following metacharacters are recognized:
Metacharacter Translates to
^<c> Control-<c>
\E Escape
\f Form feed
\n Line feed
\r Carriage return
\t Tab
\b Backspace
\0x<nn> Hexadecimal number <nn> is sent. Leading
0 must be present.
\\ \
\^ ^
The best way to learn what the PRINTCAP file is all about is
to look at examples. Some are provided here, and more in the
sample PRINTCAP file packaged with DVSI.
For a description of the four physical printer types, see
BACKGROUND PRINTING(1dvsi) and LPD(1dvsi).
TOKENS
Token Type Default value Description
br num 110 Baud rate if ``lp=COMx''
pp str (none) Filter program, not currently
supported
pb num 132 Max number of bytes printed at once
tr str (none) String to send when job completes
hr str (none) String to send at start of job
pl num 66 Pagelength if ``sf'' not specified
sf boo FALSE Suppress form feed at end of page
lp str LPT1 Physical printer type: can be one of
LPT1 printer is connected to LPT1
LPT2 printer is connected to LPT2
PRINTCAP(5dvsi) PRINTCAP(5dvsi)
DVSI Manual
COM1 printer is connected to COM1
COM2 printer is connected to COM2
DVP printer is a program launched
by LPD
FILE printer is a file or DOS
device driver
fi str nul If ``lp=DVP'', filename of DVP to
launch. The to-be-printed file is
passed as the only argument.
If ``lp=FILE'', filename or device to
print to. SEE NOTE BELOW ON DRIVE NAME.
se str (none) Serial port setup parameters:
1st character:
8 8 bits
7 7 bits
2nd character:
N No parity
O Odd parity
E Even parity
3rd character:
1 1 stop bit
2 2 stop bits
4th character:
X XON/XOFF handshaking (not
currently supported)
N No handshaking
D DSR handshaking
C CTS handshaking
H DSR or CTS handshaking
Here's what's important:
The ``lp'' token must be present in every entry. It defines
the type of physical printer maps onto the logical printer for
this entry.
If you are using an LPT-type printer, no other tokens are
required.
A COM-type printer requires the ``br'' token to define the
baud rate, and the ``se'' token to define the port settings.
A FILE-type printer only requires the ``fi'' which must
contain the filename to copy the print job to.
A DVP-type printer also requires ``fi'' which must contain
the DVP filename.
All the other tokens are used for formatting or printer
control. You must use ``sf'' if you don't want LPD to format the
output to a certain number of lines per page.
If you want to specify a drive name in the ``fi'' argument,
you must use a semicolon rather than a colon, because the colon
is used for separating tokens. For example, instead of
``fi=C:\PRINT.OUT'', use ``fi=C;\PRINT.OUT''.
EXAMPLES
The basic printer with no formatting on LPT1 is defined as
dumb:pr=LPT1:sf:
To print unformatted to the file ``C:\PRINT.OUT'',
fileprint:pr=FILE:fi=C;\PRINT.OUT:sf:
Initialize printer at beginning of job and print form feed at
end, assuming printer is Epson-compatible. Also format page to
60 lines per page:
PRINTCAP(5dvsi) PRINTCAP(5dvsi)
DVSI Manual
epson:pr=LPT1: \
:hr=\E@: \
:tr=\f: \
:pl#60:
Launch the program in C:\DV\PRINT.DVP to print the file.
launch:pr=DVP:fi=C;\DV\PRINT.DVP:
SEE ALSO
BACKGROUND PRINTING(1dvsi), LPD(1dvsi), PRCC(1dvsi)