Microsoft KB Archive/70039

{|
 * width="100%"|

Passing an Application's Start Up Directory via SETUP.INF

 * }

Q70039

-

The information in this article applies to:


 * Microsoft Windows versions 3.0, 3.0a

-

SUMMARY
This article discusses setting up the Microsoft Windows version 3.0 SETUP.INF file to pass an application's default start up directory via the SETUP.INF file when you run the Windows Setup program, SETUP.EXE.

MORE INFORMATION
If you edit the Windows 3.0 SETUP.INF file, you need to use the following procedure to pass a startup directory other than the program's directory if you want to add a new program item to a default group. For more information, see pages 555-556 of the &quot;Microsoft Windows User's Guide.&quot;

 Confirm that the application is in the DOS PATH.  Edit the SETUP.INF with a standard ASCII text editor and locate the group you want to add the new program item to:

Example   [Main] &quot;File Manager&quot;, WINFILE.EXE &quot;Control Panel&quot;, CONTROL.EXE &quot;Print Manager&quot;, PRINTMAN.EXE &quot;Clipboard&quot;, CLIPBRD.EXE &quot;DOS Prompt&quot;, COMMAND.COM, PROGMAN.EXE, 1 &quot;Windows Setup&quot;, SETUP.EXE &quot;Read Me&quot;, &quot;NOTEPAD.EXE README.TXT&quot;   Add a new line to this section (the example is Word for Windows): "&quot;WinWord&quot;, C:\DATA\WINWORD, WINWORD.EXE" Explanation

 &quot;WinWord&quot; is the icon label. &quot;C:\DATA\&quot; is the startup directory. &quot;WINWORD&quot; is the executable file. Windows automatically adds the .EXE extension. WINWORD.EXE is the location for the icon that represents the program item.

NOTE: If this is entered as &quot;C:\DATA\WINWORD.EXE&quot;, Setup truncates the statement to &quot;WINWORD.EXE&quot; and the startup directory is not specified.   Find the section [dontfind] in the SETUP.INF and add a new line: "WINWORD.EXE"</li></ol>

The SETUP.INF file is a comma-delineated text file formatted for 160 columns that supplies customized directions to the SETUP.EXE.

The preferred workstation installation method is to install Windows 3.0 on a network (see &quot;Microsoft Windows User's Guide,&quot; pages 543-556), and then go to each workstation and run the SETUP /N command. In large workstation groups, it may not be efficient to do this; in this case, customize each workstation individually. By editing the SETUP.INF file with a text editor, you can enhance the SETUP /N command so that it customizes each workstation to a company standard.