Category : Alternate Operating Systems - Quarterdeck DesqView, CP/M, etc
Archive   : QWHITE13.ZIP
Filename : DVXNETWK.TEC

 
Output of file : DVXNETWK.TEC contained in archive : QWHITE13.ZIP

ID:XN DESQview/X: Network Installation
Quarterdeck Technical Note #112 Filename: DVXNETWK.TEC
by Quarterdeck Testing and Compatibility CompuServe: DVXNET.ZIP
Last revised: 2/08/92 Category: DVX

Subject: Notes on installing DESQview/X on a network drive so that multiple
users can access a single installation.


INSTALLING DESQVIEW/X SO THAT MULTIPLE USERS CAN USE ONE INSTALLATION

In this technote we explain how to install DESQview/X on a network drive
so that multiple users may share as many of the files as possible while
maintaining as much personal customization as possible.

LEGAL CONSIDERATIONS
You MUST have a license for DESQview/X for each user who uses DESQview/X
whether they install it on their own machine or share a single network
installation.

WHAT EVERY USER MUST SHARE

Due to the design of DESQview/X, every user must share a common DVX.CFG
(general DESQview/X configuration file) and a common virtual memory
configuration file, either XB16.VMC (16-color server) or XC16.VMC (256-color
server). See the two following sections on DVX.CFG and X?16.VMC.

DVX.CFG
DESQview/X always reads the DVX.CFG file in the directory in which
you store DVX.COM, so all users must share the same DVX.CFG file. In the
DVX.CFG file you specify the display server, font directories, keyboard
mapping, startup clients (like the window manager and network server), and
some configuration parameters, such as cursor type and backing store, all of
which you choose with DVX's setup program. These parameters are all explained
in the DESQview/X Installation manual. All users of the DVX.CFG must share
these characteristics. Alternatively, you may have a few different
installations of DESQview/X with different display servers (one for
640x480x16, one for 1024x768x256, one for 8514, etc.)
For maximum flexibility, you can choose to load no clients or network
managers in the DVX.CFG, allowing each user to load his/her own when he/she
starts DESQview/X.
If not all users wish to use the same window manager (i.e., some wish to
use Motif or Open Look instead), then see the section "LETTING USERS LOAD
DIFFERENT WINDOW MANAGERS" at the end of this technote.

X?16.VMC
DESQview/X always reads the X?16.VMC file in the SERVER subdirectory of
the directory in which you store DVX.COM. This means that all users must
share the same virtual memory setup. The MAXMEM parameter determines the
amount of physical memory that your display server will use before it begins
to swap to disk. DESQview/X sets this value to 1024K by default. To
accommodate most users, make thie MAXMEM number small, like 1200. If you set
this number higher than the available memory on some user`s system, DESQview/X
will hang on entry.

WHAT EACH USER MUST HAVE
* Each user must have a unique directory to hold his/her virtual memory
swapfile. In this technote, we will call this directory C:\MY_DVX
* Each user must have a unique swapfile. See the SWAPFILE section below
for instructions on how to make each user have a unique swapfile.
* Each user must set the environment variables DVPPATH and HOME. See the
ENVIRONMENT VARIABLES section below for instructions on how to do this.
* Each user who wants his/her own menus, hotkeys, and scripts must put
them in a personal directory, either on their own computer or in a
personal directory on the network. In this technote we will call this
directory C:\MY_DVX.

SWAPFILE
For each user to have individual virtual memory swapfile, he/she must
change the "SWAPNAME" entry in the XB16.VMC (16-color server) or XC16.VMC
(256- color server) file. You find this file in DVX\SERVER. Change the
default:

SWAPNAME=TMP\SERVER.SWP

to:
SWAPNAME=C:\MY_DVX\SERVER.SWP

If any of the users wants to use a swapfile, everyone must set up a
directory (in this case, C:\MY_DVX), since they will all be sharing the same
.VMC file. This is needed whether the local user is actually using a swapfile
or not.

Since all users will use the same X?16.VMC file, set the MAXMEM parameter
to a low value, like 1200.

ENVIRONMENT VARIABLES
Each user must point the environment variables "DVPPATH" and "HOME" at
C:\MY_DVX. He/she may do this by adding these lines;

SET DVPPATH = C:\MY_DVX
SET HOME = C:\MY_DVX

to his/her AUTOEXEC.BAT or to a batch file that starts DESQview/X.
Sample batch file:

F: (the network drive on which you store DVX)
CD \DVX
SET DVPPATH = C:\MY_DVX
SET HOME = C:\MY_DVX
DVX

WM.CFG
Each user can configure his/her menus, hotkeys, scripts, and many other
features through the WM.CFG file. Each user can load his/her WM.CFG file by
modifying the DWM.DVP. Go to the common DVX\DVPS directory, then, inside
DESQview/X, run:

DVPMAN DWM.DVP

change the "Program" line to read:

WM.EXE -I C:\MY_DVX\WM.CFG

and save this modified DVP. Every user must have a directory named
"C:\MY_DVX" which contains his/her own WM.CFG. If you want to put the
personal WM.CFGs on the network drive, use the mapping facility of the network
or the SUBST command of DOS to make each user have the drive\directory to
which this argument points. You could take an unused drive letter, say X, and
use "WM.EXE -C X:\WM.CFG" and use the mapping facility of the network or DOS's
SUBST to make X point to the drive\directory where the WM.CFG file resides for
each user.
For each user to have his/her own DVPs and scripts, he/she must change
the "DVPS" line in his/her own WM.CFG to point to his/her personal directory.
For example, the default DVPS line is:

DVPS "DVPS\"

Change it to:

DVPS "C:\MY_DVX\"

The user may then personalize his/her menus, DVPs, scripts, etc. to his
/her heart's content.

APPMAN

APPMAN has its own set of configuration files. For each user to have a
different APPMAN configuration, change APPMAN.DVP so it points to an
individual APPMAN.CFG. In the network DVX\DVPS directory, run:

DVPMAN APPMAN.DVP

and change the "Program" line to:

APPMAN.EXE -C C:\MY_DVX\APPMAN.CFG

In the personal copies of APPMAN.CFG, personalize these entries:

layout_file = (Appman .LYT layout file)
icon_dir = (directory where you store icon .XPMs)
pattern_dir = (directory where you store pattern .XPMs)
group_dir = (directory where you store .GRP group files)
dvp_dir = (directory where you store Appman .DVP files)
dvpbackup_dir = (directory where you store backups of deleted Appman .DVP
files; cannot be the same as dvp_dir)

Quite possibly you may wish to make all of these, except dvpbackup_dir, point
to C:\MY_DVX. The dvpbackup_dir cannot be the same as the dvp_dir.

LETTING USERS LOAD DIFFERENT WINDOW MANAGERS
Have each user copy the DVP for the window manager he/she prefers
(DWM.DVP for the DESQview/X window manager, MWM.DVP for the Motif window
manager, OLWM.DVP for the Open Look window manager) to his/her personal
directory, C:\MY_DVX. Then have each user rename this DVP to MY_WM.DVP in
his/her personal directory. Then each user must change the program line in
their personal MY_WM.DVP to point to the network's copy of the window manager
(F:\DVX\WM.EXE for DESQview/X window manager users, F:\DVX\MWM.EXE for Motif
users, F:\DVX\OLWM.EXE for Open Look, where you replace F with the letter of
the network drive) and the directory field in MY_WM.DVP to C:\MY_DVX. Motif
users must copy the files MWM.RES and MWM.RC to C:\MY_DVX; Open Look users
must copy the files OPENWIN.MEN and OLWM.RES to C:\MY_DVX. You may find the
.RES files in \DVX\APP-DEFA. In the DVX.CFG file on the network, change the
client line to read C:\MY_DVX\MY_WM. This way, when each user starts
DESQview/X on his/her personal machine, DESQview/X will start the client
C:\MY_DVX\MY_WM, which can be different for each user. Of course each user
must still use the the "-I C:\MY_DVX\WM.CFG" parameter on the program line of
MY_WM.DVP to point to their personal WM.CFG, as discussed in the WM.CFG
section above. For this to work, ALL users must have a MY_WM.DVP in the
directory C:\MY_DVX, even if it points to the default configuration you
install on the network.

************************************************************************
* Trademarks are property of their respective owners. *
*This technical note may be copied and distributed freely as long as it*
*is distributed in its entirety and it is not distributed for profit. *
* Copyright (C) 1993 by Quarterdeck Office Systems *
************************ E N D O F F I L E *************************