Microsoft KB Archive/935060

= How to release NTFSDOS Professional from memory to accommodate other applications and to avoid conflicts =

Article ID: 935060

Article Last Modified on 7/27/2007

-

APPLIES TO


 * Winternals Administrator's Pak 4.2
 * Winternals Administrator's Pak 5.0

-



SUMMARY
This article describes how to enable NTFSDOS Professional to do the following:
 * Stop
 * Exit
 * Free memory after the spawned process exits

Note NTFSDOS Professional is a component of Winternals Administrator's Pak.



MORE INFORMATION
Sometimes you must release NTFSDOS Professional from memory so that other applications that have large memory requirements can run. Additionally, NTFSDOS Professional may conflict with other applications. In this case, NTFSDOS Professional must be released from memory in order to avoid this conflict.

For example, on a computer that is running Power Quest DriveImage, a conflict may exist between NTFSDOS Professional and Power Quest DriveImage. The conflict prevents you from running a batch file that consists of the following actions:
 * 1) Mount NTFS partition A and NTFS partition B.
 * 2) Move some files from partition A to partition B.
 * 3) Run NTFSCHK on both partitions.
 * 4) Run Power Quest DriveImage to image partition A.
 * 5) Move the files back from partition B to the newly imaged partition A.

Power Quest DriveImage conflicts with NTFSDOS Professional, and NTFSCHK will not run with NTFSDOS Professional resident in memory. Therefore, you must remove NTFSDOS Professional from memory before you run NTFSCHK and Power Quest DriveImage.

To remove NTFSDOS Professional from memory before you run NTFSCHK and Power Quest DriveImage, you must use the spawn switch (/s). The spawn switch is used with NTFSDOS Professional to spawn the batch file that moves the files. However, Command.com also interprets the COPY (copy file) command, the DEL (delete file) command, and the MD (make directory) command. Therefore, NTFSDOS Professional must spawn a new Command.com to interpret the DOS commands. Then, Command.com must exit after the batch file is finished. The newly spawned Command.com must exit as soon as the move and the copy operations have finished. Command.com must then signal NTFSDOS Professional to stop and then to exit memory. This process is achieved by recursively spawning two processes, the Command.com process and the batch file process.

In the following example, the Movefile.bat file is spawned from Command.com:

A:\NTFSPRO &quot;/s command.com /c movefile.bat&quot;

Notes
 * The /s switch is tied to NTFSDOS Professional, and the /s switch spawns Command.com.
 * The quotation marks enable the /c switch to be tied to Command.com which spawns Movefile.bat.

The Movefile.bat consists of the following lines of code. C: Md test D: Copy D:\testfiles\*.* C:\testa: As soon as Movefile.bat finishes, the following causally linked events occur:
 * 1) Movefile.bat exits.
 * 2) Command.com exits.
 * 3) NTFSDOS Professional exits.
 * 4) Memory is freed for other applications.



MORE INFORMATION
You can create a batch file that is based on the example in this article. However, you must modify the batch file to fit your specific requirements.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Additional query words: Winternals 30163 memory applications NTFSDOS Professional

Keywords: kbinfo kbexpertiseinter KB935060

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.