 
  InUse.exe - For Replacing System files already in use under Windows NT.
(VERSION 1.3)    See notes below about version 1.4 (and 1.31?) which are
                 for use by Windows 2000 only(?).

 DISCLAIMER
 ==========

    Please understand that this is an unsupported utility and typical
 safeguards should be taken when using the utility, such as ensuring
 that you have a copy of the DLL from the original installation source.
 This is "use at your own risk" and support for the utility is not
 available from Microsoft (or anyone else!) at this time. 

 MORE INFORMATION
 ----------------
 InUse is a Win32-based command-line utility that can be used by and
 within automated tasks, scripts, or other programs. 

 Syntax:
 ======

 c:\inuse.exe /?
 InUse - version 1.3
 ---------------------------------------------------------------------------
 Copyright (c) 1994-1999 Microsoft Corporation. All rights reserved

 Replaces files that are currently locked by the OS

 INUSE  source  destination  [/y]

 source         Specifies the updated file
 destination    Specifies the existing file to be replaced
 /y             Suppresses confirmation prompt to replace file
 /?             Displays syntax help

 Source and destination must include the complete physical or UNC pathname


    In Windows 2000 the version of the Inuse.exe program is 1.4. The tool
 works the same way but the Help window has changed slightly. Instead of
 'source' they use the term "replacement."

 Comments
 ========

    The destination is the currently locked file that you want to replace
 on the local drive. Please note that after you commit INUSE to replace a
 file, you cannot run it again to reverse the transaction.  This may be
 considered in a newer version.

 Examples

    Basic operation of INUSE is quite simple; just tell it the file you
 want to replace and where it's updated replacement is located. It also
 has an additional parameter that allows the supression of the actual copy
 comfirmation. This may be useful if you intend to use INUSE as part of
 some automated processes. The following examples shows simulated INUSE
 output as well as its operation in both a local and also a network-based
 file replacement scenario.


Example 1: Promptless Install

c:\tools\inuse.exe \\updates\prodmod.dll c:\program files\prodsys\prodmod.dll /y
InUse - version 1.3
--------------------------------------------------
InUse is about to replace the following file

Existing:    c:\program files\prodsys\prodmod.dll
Version:     1.31

Replacement: \\updates\prodmod.dll
Version:     1.34

\\updates\prodmod.dll is replacing --> c:\program files\prodsys\prodmod.dll

Changes do not take affect until you reboot


Example 2: Prompted Install

c:\tools\inuse.exe \\updates\prodmod.dll c:\program files\prodsys\prodmod.dll
InUse - version 1.3
--------------------------------------------------
InUse is about to replace the following file

Existing:    c:\program files\prodsys\prodmod.dll
Version:     1.31

Replacement: \\updates\prodmod.dll
Version:     1.34

Do you want to continue?(y/n)

\\updates\prodmod.dll is replacing --> c:\program files\prodsys\prodmod.dll

Changes will not take affect until you reboot 


    You will notice the only difference with the examples is the fact the
 user will be prompted to confirm or cancel the operation on the latter.


Example 3: Batch Operation

   The following example represents how an administrator can nest multiple
 updates in a single script:


batch.cmd
@echo off
inuse test.dll c:\winnt\system32\test.dll /y
inuse test2.dll c:\winnt\system32\test2.dll /y
inuse test3.dll c:\winnt\system32\test3.dll /y


 Note: that this executable actually does an edit to the registry to
 perform a "PendingFileRenameOperations" on the next reboot.



