Here's quote from the FAQ... FAQ, help and samples are your friends - don't ignore them. Thanks!
Q8: I have VC6 and have problems building full static StarBurn applications. Compiler says about unreferenced __security_check_cookie, __security_cookie, __SEH_epilog, __SEH_prolog, __alldvrm, __aulldvrm and so on. VC7 works just fine but we really need VC6 builds for our customer! What should we do?
A8: This problem is confirmed Microsoft bug. Starting from Windows 2003 Server IFS Kit (this one is used to build StarBurn SDK binaries and libraries and whole moderns Microsoft OSes core) inserts special stack frame validation code into all of the binaries and libraries. VC7 has
support for such a stuff out-of-box, VC6 has no such thing... To build static StarBurn applications in VC6 you need to link with these obj files that are in VC7 directory Vc7\crt\src\intel\mt_lib (when you choose to install CRT source code): sehprolg.obj, lldvrm.obj, ulldvrm.obj. And also link with BufferOverflowU.lib from Platform SDK or DDK for Windows Server 2003 Service Pack 1. With this approach you can only build release static builds, because when building with debug info linker says that debug info is corrupted in the obj files. Please check DataBurner MFC GUI sample. It contains VC6 project with release static configuration.
|