Via: uk.ac.coventry.cck; Tue, 18 Aug 1992 11:18:58 +0100
X-Mailer: ELM [version 2.3 PL6]
Newsgroups: bit.listserv.novell
Date:         Tue, 18 Aug 1992 06:32:12 -400
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         James Nash <ccx020@CCH.COVENTRY.AC.UK>
Subject:      re: Windows local permanent swapfile (or temporary?)
X-To:         MICHAEL@bmgtmail.umd.edu
X-cc:         NOVELL@suvm.acs.syr.EDU, jbeck@bmgtmail.umd.edu,
              ccx020@cck.coventry.ac.uk
              "MICHAEL@edu.umd.bmgtmail" at Aug 14, 92 11:54 am

MICHAEL@edu.umd.bmgtmail wrote:
> It is my understanding that a swapfile should be created locally
> to save the server.  If you have a number of users trying to work a
> networked version the harddisk will crawl to a halt without a
> swapfile.

Yup, if Windows creates temporary swapfiles on the network (1Mb min.)
it slows startup, hammers the network and takes up space on the file
server's hard disk. Fun!

> [More swapfile stuff del'd]
> As for your old local copies of windows with swapfiles, reinstall
> Windows (using /n or not).  You should be prompted, stating that an
> old swap exists and you will have the chance to delete it and create
> a new one.  I see no reason to bother with "spart.par".

So we can have bigger swapfiles, more space for local data & temporary
files, I do want to kill the local Windows. [See below for more on
SPART.PAR] I used "setup /n" to initially create the INI/GRP files.

> Ideally, if you have the space on the harddisks, your best bet is to
> install windows locally with a permantent swapfile and use a shared
> network group.  This minimizes the use of the server and gives
> maximum performance to the user.

In a tight, administration (finance depts, etc.) network, we do need
a great deal of control and the problems with the local copy of
Windows (full version that is) are many. Mostly to do with updating
Netware files, DLL files, video card files; the list goes on. Also we
cannot guarantee that a user has not messed up their local setup.
When we go on a support call, it will take 10 minutes just to check
Windows. I know that getting most of WIndows' files from the network
will hit performance but is a price worth paying.

> If the drive behind all of this is for the supervisor to keep
> control of the windows system, doing the following will disable
> the ability for modifications by the local user:
> in Progman.ini, place the following
> [restriction stuff del'd]

Is this in 3.1 only? We are currently 3.0a but moving towards 3.1.
(I hope!)

> The last note is that the .ini files for each user will need to be
> updated when new software is installed.  This is a problem when you
> use either server home directories or local windows directories.

We currently store the "setup /n" files (INI, GRP etc.) in a directory
under the user's home area on the server (although it could just as
well go on the hard disk). A very nice program that comes with Saber
Menu for Windows is INIMAN. This allows you to make modifications to
INI files before you go into Windows. For example, you can add a
section, say [Microsoft Word], on a one-time basis in WIN.INI; or you
can always reset the user's SYSTEM.INI so it points to the correct
VGA drivers for that machine. This then allows the user to customise
their setup without losing system integrity and do it from differing
machines!

[The only real problem is GRP files: what if the user deletes them?
 (or whatever). If the menu program from Saber - or anyone else - is
 used, Program Manager becomes obsolete. Sad but true.]

As for using SPART.PAR; because we store INI/GRP files on the server,
Windows looks there for SPART.PAR and won't pick it up locally
(although C:\WINDOWS when in the path seemed to work a couple of
times - not fully investigated that one). So, created SPART.PAR
on network, copied it down to hard disk and every time Windows is
run, copied back to user's Windows' directory. It does work and lets
us use permanent swapfiles within our setup.

> [Master WIN/SYSTEM.INI stuff del'd]

> I hope this all makes sense.  Good luck!
> Michael@bmgtmail.umd.edu  :)
> College of Business and Management
> University of Maryland, College Park

Thanks for your input and keep up the good work...
--
James Nash, Computing Services, Coventry University, England
ccx020@uk.ac.cov.cch
--That's forward slash (bottom left to top right) 'user', spelt u-s-r...
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU