I'd recommend using VerifyVersionInfo:
http://msdn.microsoft.com/en-us/library/windows/desktop/ms725492(v=vs.85).aspx.
It's supported from Win2k onward and isn't deprecated as of Win 8.1. I don't
remember for sure if it's present in Windows CE and unfortunately I don't have
my CE documentation
I'm looking into building OpenSSL 1.0.1e for use on embedded devices with
severely limited disk sizes (<20 MiB available). These devices run Windows CE 3
or 5 (EVC compiler) and are ARM, SHx, or x86 architectures. After applying a
few minor patches to fix compile/link errors, OpenSSL DLLs compil
Traditionally, there are 2 methods that immediately come to mind. One way is to
have the SSL version of the server listen on a different port than the plain
text version. Alternatively, your protocol could include a "STARTTLS" like
command that indicates that the system wants to communicate secu
Check out this page: http://www.openssl.org/docs/crypto/OPENSSL_Applink.html
Basically, you just need to #include in your application.
That file defines a virtual table like list of things related to stdout,
stderr, etc. This file only appears to be needed when you start using functions
that m
