Using Swap Files on Networks in WindowsLast reviewed: November 23, 1994Article ID: Q89141 |
The information in this article applies to:
SUMMARYThis article discusses the use of Microsoft Windows and swap files on network drives. The following topics are included:
MORE INFORMATION
Can Swap Files be Created on a Network Drive?Network drives do not support the INT13h calls needed to set up a permanent swap file. A temporary swap file can be set up on a network drive where you have full privileges (rights) including creation rights if you are on a Novell network. Approximately 2 MB of free hard disk space is required. You cannot have multiple workstations using the same swap file; therefore, if you set up a swap file on a network drive, it should be in the user's directory where no one else but the user can access it. If possible, set up the swap file on your local workstation's hard drive. Benefits of this configuration include the following:
Why Does Windows Take So Long to Start in 386 Enhanced Mode?Temporary swap files on a network can make the loading of Windows slow. This can also affect the speed at which Windows runs in 386 enhanced mode while Windows tries to swap files. This affects both Windows and non- Windows-based applications. When you load Windows, the temporary swap file is initialized in the startup location of WIN.COM. Because a network drive normally has a large amount of free disk space, this swap file can become large. 386 enhanced mode initializes the temporary swap file to about half of the available contiguous free disk space. Initializing this large swap file can take a long time and can cause Windows to take more than one minute to load. There are three ways to avoid this problem:
|
KBCategory: kbnetwork kb3rdparty kbusage
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |