SYSDIFF /dump Displays Some Registry Data Types IncorrectlyLast reviewed: August 1, 1997Article ID: Q151908 |
The information in this article applies to:
SYMPTOMSWhen you use SYSDIFF /dump to view the contents of your difference file, you may notice that some of the registry data types (such as REG_BINARY, REG_MULTI_SZ, and REG_DWORD) are not displayed correctly. An example is listed below:
Regedt32 shows SYSDIFF /dump shows ---------------------------------------------------------- LogEvents REG_DWORD: 0x1 LogEvents: REG_DWORD: 0x3018f0 Dcache REG_MULTI_SZ: 20 Dcache REG_MULTI_SZ: Binary Data type 7 DCacheUpdate REG_BINARY: f0 b6 45 8a DCacheUpdate REG_BINARY: Binary 26 9d bc 00 data of type 3 RESOLUTIONTo resolve this problem, obtain the hotfix below, or wait for the next service pack. Please note that you must rebuild any packages that were built using the previous Sysdiff.exe. This hotfix has been posted to the following Internet location:
ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40/ utilities/Sysdiff-fixNOTE: This version of Sysdiff replaces the version that ships with Service Pack 3.
STATUSMicrosoft has confirmed this to be a problem in Windows NT version 4.0. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.
|
Additional query words: 4.00 zak unattend deployment
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |