I notice on the MSDN page for CryptBinaryToString there's this bit of info about one of the flags that can be used with this function:
Value Meaning
CRYPT_STRING_NOCRLF
0x40000000
Do not append any new line characters to the encoded string. The default behavior is to use a carriage return/line feed (CR/LF) pair (0x0D/0x0A) to represent a new line.
Windows Server 2003 and Windows XP: This value is not supported.
One thing that stands out is the fact that it says that it's not supported under Windows XP. Does that mean the base version of XP? Or does it mean that it won't work even with any service pack (up through SP3)? I have noticed that other pieces of info about various other functions on other MSDN pages say some things won't work under XP with SP1 or SP2, so I'm trying to figure out if when it says won't work under XP, if this means all XP regardless of service pack, or only that it won't work under the original version of XP, but that with an upgrade (possibly just requiring SP1) it will work.
Quote:
Value Meaning
CRYPT_STRING_NOCRLF
0x40000000
Do not append any new line characters to the encoded string. The default behavior is to use a carriage return/line feed (CR/LF) pair (0x0D/0x0A) to represent a new line.
Windows Server 2003 and Windows XP: This value is not supported.
One thing that stands out is the fact that it says that it's not supported under Windows XP. Does that mean the base version of XP? Or does it mean that it won't work even with any service pack (up through SP3)? I have noticed that other pieces of info about various other functions on other MSDN pages say some things won't work under XP with SP1 or SP2, so I'm trying to figure out if when it says won't work under XP, if this means all XP regardless of service pack, or only that it won't work under the original version of XP, but that with an upgrade (possibly just requiring SP1) it will work.