Microsoft KB Archive/151912

NWRedir Returns Cached File Size Information

Q151912

The information in this article applies to:

Microsoft Windows 95

SYMPTOMS

If a file on a Novell NetWare network server is opened by a Windows 95 client running the Microsoft Client for NetWare Networks (NWRedir), and the size of the file subsequently changes, the new file size may not be reported by Windows 95.

CAUSE

If a file is being cached, the GetFileSize API returns cached file size information, instead of reading the actual file size from the server.

RESOLUTION

This issue is resolved by the following updated file for Windows 95 and OSR2, and later versions of this file:

For the Bindery (non-NDS) version of the Microsoft Client for NetWare Networks:
```
      NWREDIR.VXD  version 4.00.954  dated 5/20/96  123,987 bytes 
```
For the NDS version of the Microsoft Client for NetWare Networks (Microsoft Service for NetWare Directory Services):
```
      NWREDIR.VXD  version 4.00.969  dated 7/30/96  174,618 bytes 
```

STATUS

Microsoft has confirmed this to be a problem in Microsoft Windows 95 and OEM Service Release 2 (OSR2). An update to address this problem is now available, but is not fully regression tested and should be applied only to computers experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft does not recommend implementing this update at this time. Contact Microsoft Technical Support for additional information about the availability of this update.

This issue is resolved in Microsoft Windows 98.

MORE INFORMATION

In a situation where multiple clients access and make changes to a single network file without locking the file to enforce data integrity, NWRedir may not reflect the current file data due to its implementation of caching. In the absence of locking, some programs may check for changes in the file size using the GetFileSize API.

This update to NWRedir cause GetFileSize to read the current file data from the server, regardless of whether the file is currently being cached.

For additional information about issues resolved by updates to this component, please see the following articles in the Microsoft Knowledge Base:

Q177222 NetWare Printers or Volumes Unavailable in Windows 95

Q165402 Windows 95 Update to Encrypt Passwords in Memory

Q163673 "Exception 0E" Using MSNDS Over Dial-Up Connection

Q160897 NWRedir Reports Incorrect Free Space If Limited by Admin

Q160824 MSNDS Drops Connections to More Than Eight Servers

Q158058 MSNDS Client Does Not Prompt to Log On

Q153470 Incorrect Error Code Returned for Locked Files

Q152186 Possible Network Data Corruption If Locking Not Used

Q149606 Fatal Exception 0E in VNETBIOS Using NetWare Login Script

Q147838 Cannot Access Folders with Long File Names on NetWare Servers

Q143282 No Documents Appear in the File Open Dialog Box

Q139747 MS-DOS-Based Program Reports Not Enough NetWare Server Space

Q136303 Connecting to Schedule+ 1.0 Calendar File Drops Connections

Q132786 Known Issues with MS Print Agent for NetWare (MSPSRV)

For additional information about Windows 95 updates, please see the following article in the Microsoft Knowledge Base:

Q161020 Implementing Windows 95 Updates

Keywords : win95
Issue type :
Technology : kbWin95search kbWin95