BUG: GetDiskFreeSpace() Fails with a UNC Path to Network Share

ID: Q137230

The information in this article applies to:

Microsoft Win32 Application Programming Interface (API), included with:
- Microsoft Windows 95

SYMPTOMS

The GetDiskFreeSpace() function fails with a universal naming convention (UNC) path to a network share. This failure causes problems for various applications. For example, WinHelp can neither load nor create a full-text index through a UNC path. The same operation works fine using a drive-relative path.

This problem does not occur under Microsoft Windows NT. However, you must include a trailing backslash, so that the UNC path looks like the following:


   \\server\share\

RESOLUTION

Use a drive letter instead. For example:


   GetDiskFreeSpace(<UNC name>)
   if <GetDiskFreeSpace fails>

      WNetAddConnection()    // Connect and get a drive letter.
      GetDiskFreeSpace(<drive letter>:)
      WNetCancelConnection() // Disconnect.

STATUS

Microsoft has confirmed this to be a bug in Microsoft Windows 95. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: win95fest


Keywords          : kbAPI kbKernBase kbGrpKernBase 
Version           : 
Platform          : 
Issue type        : kbbug

Last Reviewed: March 5, 1999