Path: utzoo!attcan!uunet!samsung!sdd.hp.com!elroy.jpl.nasa.gov!turnkey!orchard.la.locus.com!prodnet.la.locus.com!jta
From: jta@locus.com (JT Anderson)
Newsgroups: comp.windows.ms
Subject: Re: Using Win 3.0 on Shared-Use Machines
Summary: Starting window apps in a "docs" directory.
Keywords: Windows 3.0, File Properties
Message-ID: <12345@oolong.la.locus.com>
Date: 9 Jul 90 18:59:18 GMT
References: <1990Jul6.152405.929@athena.mit.edu> <7768@fy.sei.cmu.edu> <1433@epd74hp.nluug.nl>
Organization: Locus Computing Corp., Los Angeles
Lines: 23

In article <1433@epd74hp.nluug.nl>, geoff@nluug.nl (G. Coupe EPD/74 O75/1435) writes:
> In article <7768@fy.sei.cmu.edu> bwb@sei.cmu.edu (Bruce Benson) writes:
> >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?  

I have had some success with the following approach.

1.  Make sure the document type for the application is registered in the
    extensions section of WIN.INI.

2.  Put an empty document in your data directory.

3.  Set up a PROGMAN icon that runs the document.

4.  Go to PROGMAN, PROPERTIES, Change Icon and give the path to the actual
    .EXE file for the windows app.  You can get the proper icon.