Comments on: Windows 2003 SP1 DDK with a little annoyance … http://blog.assarbad.net/20060708/windows-2003-sp1-ddk-with-a-little-annoyance/ Programming, reverse engineering and anything else as well ... Sat, 30 Aug 2008 04:43:16 +0000 http://wordpress.org/?v=2.3.3 By: Oliver http://blog.assarbad.net/20060708/windows-2003-sp1-ddk-with-a-little-annoyance/#comment-1253 Oliver Fri, 16 Mar 2007 16:18:57 +0000 http://blog.assarbad.net/20060708/windows-2003-sp1-ddk-with-a-little-annoyance/#comment-1253 Just as a side-note: DDKWizard handles this case and creates the file described here for you. Just as a side-note: DDKWizard handles this case and creates the file described here for you.

]]> By: Jeff http://blog.assarbad.net/20060708/windows-2003-sp1-ddk-with-a-little-annoyance/#comment-1225 Jeff Fri, 16 Mar 2007 02:08:21 +0000 http://blog.assarbad.net/20060708/windows-2003-sp1-ddk-with-a-little-annoyance/#comment-1225 Yes, thank you for posting this. I am proof that it continues to be useful. You saved me a lot of time today! Yes, thank you for posting this. I am proof that it continues to be useful. You saved me a lot of time today!

]]> By: Oliver http://blog.assarbad.net/20060708/windows-2003-sp1-ddk-with-a-little-annoyance/#comment-26 Oliver Wed, 02 Aug 2006 20:34:52 +0000 http://blog.assarbad.net/20060708/windows-2003-sp1-ddk-with-a-little-annoyance/#comment-26 Good to hear it has been useful for someone already :-) I have wrapped the code into pre and code tags so it will show with fixed font size, just in case you wonder. Good to hear it has been useful for someone already :-)

I have wrapped the code into pre and code tags so it will show with fixed font size, just in case you wonder.

]]> By: CMK http://blog.assarbad.net/20060708/windows-2003-sp1-ddk-with-a-little-annoyance/#comment-25 CMK Wed, 02 Aug 2006 14:51:10 +0000 http://blog.assarbad.net/20060708/windows-2003-sp1-ddk-with-a-little-annoyance/#comment-25 Thanks for this post. I actually just ran into this problem yesterday, and you saved me a bit of investigating. I ended up using you 2nd suggestion to create a file called NtProcessStartupForGS_fix.c and I wrapped it in ifdefs so that it is only used when being compiled in the Win2K environment: <pre><code>// only use this file if we are building under/for a Win2K environment #if _WIN32_WINNT == 0x500 extern void NtProcessStartup(void * StartupArgument); extern void NtProcessStartupForGS(void * StartupArgument); void NtProcessStartupForGS(void * StartupArgument) { NtProcessStartup(StartupArgument); } #endif</code></pre> Very useful. Thanks! Thanks for this post. I actually just ran into this problem yesterday, and you saved me a bit of investigating. I ended up using you 2nd suggestion to create a file called NtProcessStartupForGS_fix.c and I wrapped it in ifdefs so that it is only used when being compiled in the Win2K environment:

// only use this file if we are building under/for a Win2K environment
#if _WIN32_WINNT == 0x500

extern void NtProcessStartup(void * StartupArgument);

extern void NtProcessStartupForGS(void * StartupArgument);

void NtProcessStartupForGS(void * StartupArgument)
{
	NtProcessStartup(StartupArgument);
}

#endif

Very useful. Thanks!

]]>