Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!usc!julius.cs.uiuc.edu!apple!agate!linus!linus!mwunix.mitre.org!jcmorris
From: jcmorris@mwunix.mitre.org (Joe Morris)
Newsgroups: comp.windows.ms
Subject: Re: Exiting Windows 3 after application
Message-ID: <125641@linus.mitre.org>
Date: 7 Nov 90 13:37:25 GMT
References: <BGONDERM.90Nov5162001@dante.nmsu.edu>
Sender: usenet@linus.mitre.org
Reply-To: jcmorris@mwunix.mitre.org (Joe Morris)
Distribution: comp
Organization: The Mitre Corporation
Lines: 55

In a recent article bgonderm@nmsu.edu (Bryan Gondermger) writes:
>We have four PC's (each with a copy of Windows 3 on the local hard
>drive) connected to a network and running a menu program.  When using
>Windows applications (PageMaker and WORD for Windows in particular),
>which are on the network, we set up the menu software to execute the
>following command:
>
>win -r w:winword
>
>This works OK - WORD for Windows is loaded and operates properly.  The
>"problem" is that when the user exits WORD, they are returned to
>Windows and not DOS (and the menu program).  Is there some way to make
>Windows automatically exit after an application (specified from the
>command line) is terminated?

You can do this (call it "run-time Windows simulation") by the following:

1. Create a new directory called \winwfw  (this doesn't *have* to be distinct;
   it could be your WfW normal directory.  Just so long as it isn't
   part of Windows 3 itself).

2. Copy the following files to the new directory from your Windows directory:

    win.com
    win.ini
    system.ini

3. In the new directory modify the [boot] section of 'system.ini' by
   changing the shell= line to point to the one-and-only program you
   want to run.  The original line should read:

   shell=progman.exe

   and the modified line in your case would be:

   shell=w:\winword.exe

   Remember to type the complete fileid of the program to be executed,
   including the '.exe' suffix.  I tried this technique as I wrote this note,
   and was rudely reminded of this by Windows when I just said 'excel'.

4. To execute the dedicated Windows session just put the new directory ahead
   of the normal Windows directory in your path and issue the 'win' command.

What we're doing here is making Windows think it's running on a network
where the actual executable files, fonts, etc. are on a network server, and
only the basic control files (and win.com) are on the user's local disk.

Note that this technique isolates any changes in WIN.INI and SYSTEM.INI made
in the dedicated task from any changes made in normal Windows; this may or
may not be desirable.  If you need to keep the two flavors of Windows in
sync you'll have to provide an outboard copy function to refresh the
files.

Joe Morris