Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!pt.cs.cmu.edu!sei!bwb
From: bwb@sei.cmu.edu (Bruce Benson)
Newsgroups: comp.windows.ms
Subject: Re: Using Win 3.0 on Shared-Use Machines
Message-ID: <7768@fy.sei.cmu.edu>
Date: 6 Jul 90 17:54:51 GMT
References: <1990Jul6.152405.929@athena.mit.edu>
Reply-To: bwb@sei.cmu.edu (Bruce Benson)
Organization: Software Engineering Institute, Pittsburgh, PA
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.

My solution:  I need word for windows to start in the subdirectory that
contains this months letters (\wp\90-07).  Using properties I specify:
\wp\90-07\winword.exe as the program to run. Since winword.exe is not
found in that directory, the program manager complains that the file is
invalid BUT allows me to select OK.  As winword.exe is on the path,
winword.exe will still be found and started, but the starting directory
will be \wp\90-07. 

A kludge, but it does what I need.  Anyone have other approaches?  

* Bruce Benson                   + Internet  - bwb@sei.cmu.edu +       +
* Software Engineering Institute + Compuserv - 76226,3407      +    >--|>
* Carnegie Mellon University     + Voice     - 412 268 8496    +       +
* Pittsburgh PA 15213-3890       +                             +  US Air Force