Drive List Shows Only Program Drive in 16-Bit and 32-Bit Programs (241210)



The information in this article applies to:

  • Microsoft Windows NT Server 4.0 Terminal Server Edition
  • Microsoft Windows NT Server 4.0 SP4
  • Microsoft Windows NT Server 4.0 SP5
  • Microsoft Windows NT Workstation 4.0 SP4
  • Microsoft Windows NT Workstation 4.0 SP5

This article was previously published under Q241210

SYMPTOMS

On a computer running Microsoft Windows NT 4.0 Service Pack 4 or Service Pack 5, when you attempt to open a file you may be able to see only the drive of the program you are running in the Open box in the following program types:
  • 16-bit programs that uses the common dialog box
  • 32-bit programs that uses the old-style user interface instead of the new Windows NT Explorer-style user interface

CAUSE

This behavior can occur if the network adapter and network protocols are not installed or disabled. Without a network loaded, WNetOpenEnum does not succeed at the beginning of the GetNetDrives function, the function exits, and the drive list is never initialized.

RESOLUTION

Windows NT Server or Workstation 4.0

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:
For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

Windows NT Server 4.0, Terminal Server Edition

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

152734 How to Obtain the Latest Windows NT 4.0 Service Pack


STATUS

Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition.

This problem was first corrected in Windows NT Server 4.0 Service Pack 6 and Windows NT Server 4.0, Terminal Server Edition Service Pack 6.

Modification Type:MajorLast Reviewed:5/14/2003
Keywords:kbbug kbfix kbinterop KB241210