[cifs-protocol] [REG:117010415132041] Wrong value for PROCESSOR_AMD_X8664 in MS-RPRN.
nmanis at microsoft.com
Wed Jan 4 19:22:20 UTC 2017
Thank you for contacting Microsoft. We have received the report and reviewed the value documented in the MS-RPRN. The value in the public header files is showing this to be 0x21D8 versus 0x22A0.
Here is the value (0x21D8 in hex) from the Windows SDK header file winnt.h:
#define PROCESSOR_AMD_X8664 8664
Therefore, we will get a documentation update submitted to get the value updated. Thank you for the report.
From: "Bryan Burgin" <bburgin at microsoft.com>
Sent: Wednesday, January 4, 2017 12:35 PM
To: "Andreas Schneider" <asn at cryptomilk.org>
Cc: "cifs-protocol at lists.samba.org" <cifs-protocol at lists.samba.org>; "MSSolve Case Email" <casemail at microsoft.com>
Subject: [REG:117010415132041] Wrong value for PROCESSOR_AMD_X8664 in MS-RPRN
[Dochelp to bcc]
We created SR 117010415132041 to track this. An engineer will contact you soon.
From: Andreas Schneider [mailto:asn at cryptomilk.org]
Sent: Wednesday, January 4, 2017 7:25 AM
To: Interoperability Documentation Help <dochelp at microsoft.com>
Cc: cifs-protocol at lists.samba.org
Subject: Wrong value for PROCESSOR_AMD_X8664 in MS-RPRN
[MS-RPRN] <65> Section 126.96.36.199.1: Windows uses the following values:
PROCESSOR_AMD_X8664 0x000022A0 -- AMD x64 compatible
When talking to a Windows Server we see 0x000021D8 (8664) for the processor_type in a GetPrinter on the wire. It looks like the value documented in [MS-RPRN] is incorrect.
Could you please verify the value for PROCESSOR_AMD_X8664?
Andreas Schneider GPG-ID: CC014E3D
www.cryptomilk.org asn at cryptomilk.org
More information about the cifs-protocol