Path: utzoo!utgpu!watserv1!watmath!att!ucbvax!pasteur!tureen.berkeley.edu!craig
From: craig@tureen.berkeley.edu (Craig Lant)
Newsgroups: comp.windows.ms
Subject: Re: Using Win 3.0 on Shared-Use Machines
Message-ID: <26192@pasteur.Berkeley.EDU>
Date: 13 Jul 90 22:27:34 GMT
References: <1990Jul6.152405.929@athena.mit.edu> <7768@fy.sei.cmu.edu>
Sender: news@pasteur.Berkeley.EDU
Reply-To: craig@tureen.berkeley.edu (Craig Lant)
Organization: University of California, Berkeley
Lines: 24

In article <1990Jul6.152405.929@athena.mit.edu> robf@athena.mit.edu
(Robert E Fellows) writes:
|>
|>As far as I can tell, Windows 3.0 throws this concept away, in the sense
|>that there is no ability to set and maintain a "current" default
|>directory for data files.  If you start a windows app from DOS, (i.e.
|>'win excel'), then the File Open dialog will default to the current
|>directory.  But if you start Windows and launch applications from the
|>program manager, the default directory for all apps (including a DOS
|>shell) is changed -- at least on my machine -- to the windows directory.

What I did was to install windows as if on a network.  That is, I installed
everything on my machine as if it were a file server (it's not).  Then I
installed windows from the windows directory into my home directory as
if I were
my own client.  Now when I start windows from my home directory, thats where
apps get launched from yet most executables are still kept in the windows
directory.  By reinstalling for each user on my system everyone gets there own
environment and stuff launches from there home directories.  I haven't had any
problems with this yet.


						Craig Lant
				    University of California, Berkeley