Newsgroups: bit.listserv.novell
Date:         Tue, 12 Jan 1993 09:38:32 EST
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
Comments:     Converted from OfficeVision to RFC822 by PUMP V2.2X
From:         "James E. Saunders DRSABAC@CFRVM.CFR.USF.EDU"
              <DRSABAC@CFRVM.BITNET>
Subject:      Need help with Windows 3.1 on NetWare server..

>1)  Installing new applications:

This isn't too hard, assuming that the new application does not want to
change the WIN.INI in it's installation process (most don't seem to, thank
goodness!).

I have created a H:\WINDOWS sub-directory under each users home drive (more
on that in a minute), and in it, among other things, I place a NETWORK.GRP
program group file with the icons for all applications available over the
network.  The master NETWORK.GRP file is mine and when new programs are
added, old programs deleted, or other changes are made, I simply run a
batch job which places a file named UPDATE.ME in each users H:\WINDOWS
sub-directory.  My network (considerably smaller than yours) is configured
to run a batch file which starts up Windows when the user logs in, and in
the process it checks for the presence of UPDATE.ME, if found it copies
my NETWORK.GRP file into the users home Windows directory and deletes the
UPDATE.ME file.  Keeping a copy of the NETWORK.GRP file in each users own
area allows each user to change/resize/iconize etc. the group window as s/he
pleases in between updates, and it almost guarantees that the thing will be
open and offset from the position the user left it in whenever it is up-
dated, thus bringing the update to their attention.

>2)  Using different workstations:

With a mixed bag of workstations like that (286, 386, 486, monochrome, VGA)
I will assume that we aren't talking about diskless workstations.  Unless they
each have the exact same applications loaded on them (a good trick) you are
going to have a hell of a time getting users to move freely from one
machine to another and load Windows from home directories on the network if
they are to be allowed/able to access any local programs.

I would strongly suggest installing Windows on the individual workstations
and then using a method similar to that which I outlined above to give each
user access to the network applications.  I know it is more work, but the
install is fairly painless if it is done over the network, and you're
going to have to spend some time with each user during this process anyway!

Also in my batch job which starts Windows when users login (and logs them
out when they exit Windows) is a test for an environment variable which is
set in the workstations AUTOEXEC.BAT which determines whether to start in
enhanced or standard mode.  This allows me to start the TBMI task switcher
for standard mode, and it allows users of 386/486 machines to choose to
start in standard mode if they wish.  Keeping all the other Windows files
on the workstation will solve the rest of the problems, I think, and will
also probably provide somewhat better performance.

Please feel free to let me know if there is any of this that needs
clarification, I'm sure there is!

James E. Saunders
Sr. Programmer Analyst
University of South Florida
Health Sciences Center Admin.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU