The information in this article applies to:
IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe. SYMPTOMS
The Windows 95 Remoteboot Client will record an incorrect timestamp for
files that it saves to the Windows NT Remoteboot server. The timestamp is
offset by an increment equal to the difference between Greenwich Mean Time
(GMT) and the time zone of the Remoteboot client and server. Essentially,
the timestamp of the file is GMT.
CAUSEThe problem occurs when you build the server message block (SMB) to save a file to the remote initial program load (RPL) server. The timestamp is obtained, and the time zone offset is used to calculate the local time, which is placed in the SMB and used as the timestamp for the file. The problem is that the time zone offset, which is normally obtained from the registry, is unable to be obtained there in RPL situations. Instead, for an RPL client, the time zone offset is read from the registry during startup and saved in a global variable. This variable is then used when building the SMB. In this case, the variable is initialized prior to use. RESOLUTION
STATUSMicrosoft has confirmed this to be a problem in Windows 95. Additional query words: rpl remote boot win95 timezone GMT
Keywords : ntdomain |
Last Reviewed: July 1, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |