DOCUMENT:Q194079 22-APR-2002 [exchange] TITLE :XCLN: ODK:Some Hex Values Not Accepted for DWORD Registry Entry PRODUCT :Microsoft Exchange PROD/VER:WINDOWS:98 OPER/SYS: KEYWORDS: ====================================================================== ------------------------------------------------------------------------------- The information in this article applies to: - Microsoft Outlook 98 Deployment Kit - Microsoft Exchange Server, version 5.5 ------------------------------------------------------------------------------- SYMPTOMS ======== When assigning a hexadecimal value to a DWORD registry entry using the Outlook Deployment Kit (ODK), alpha characters are stripped from the entry. For example, a value of "1E", which represents the decimal number 30, is added to the registry as "1". CAUSE ===== This is currently a limitation of the Outlook Deployment Kit and the way registry values are entered for DWORD data types. WORKAROUND ========== Hexadecimal values must be entered as all numeric values. In the example above, hexadecimal values of 19 or 20 can be entered, representing the decimal values of 25 and 32 respectively. MORE INFORMATION ================ Additional query words: hex stripped character lost missing regkey convert ====================================================================== Keywords : Technology : kbOutlookSearch kbExchangeSearch kbExchange550 kbZNotKeyword2 kbOutlookDeployKitSearch kbOutlook98DeployKit Version : WINDOWS:98 Issue type : kbprb ============================================================================= THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY. Copyright Microsoft Corporation 2002.