The day Sir John A. McDonald brought the four colonies of Upper Canada (Ontario), Lower Canada (Quebec), NewBrunsick, and Nova Scotia together in 1867 ! The day to celebrate the nicest country in the whole world ! Happy Birthday Canada ! :) :) :) :-D :-D :-D int f,r,a,c,t,A,l=42;main(){while(--l>-42)for(t=-60;t++<20;putch('J'-f))for(A=a=r=f=0;++f<42&&r*r+A*A<7056;c=r+t,a=l+A,r=(c*c-a*a)/42,A=c*a/21);}

Well if you really want to work for Microsoft, it couldn't hurt to apply http://microsoft.com/jobs int f,r,a,c,t,A,l=42;main(){while(--l>-42)for(t=-60;t++<20;putch('J'-f))for(A=a=r=f=0;++f<42&&r*r+A*A<7056;c=r+t,a=l+A,r=(c*c-a*a)/42,A=c*a/21);}

ESP is the stack pointer register E stands for 32 bit (as opposed to the 16 bit pointer on the 80286 many years ago. The error message is usually correct, but sometimes something really bad happened like you whacked something on your stack (buffer overrun), and sometimes you can get this message by stepping over code in the debugger using "set net statement". If you know that you haven't been writing to memory off the end of an array thats a stack variable, take a look at the Docs on "calling convetions". what typically happens in these cases is that you have 2 funtion prototypes that declare the function to have differing calling convetions. You need to make sure that the person who implements the function agrees with the person who calls the function as to things like where function arguments are passed on the stack or in registers, etc. int f,r,a,c,t,A,l=42;main(){while(--l>-42)for(t=-60;t++<20;putch('J'-f))for(A=a=r=f=0;++f<42&&r*r+A*A<7056;c=r+t,a=l+A,r=(c*c-a*a)/42,A=c*a/21);}

Yes it probably is the project system attempting to scan the dependencies of your project. One possible solution to this is to try to reduce the complexity of your code. There is a good book on this "Large Scale C++ Development" I think is the name. Its a few years old and only a little out of date, but I found it useful when it came to compile time complexity issues. The check list of easy things to do to reduce this scan time is ... Check to make sure none of the h files are on network drives Check to makesure every path on your include path (tools.options.directories) exists, and that there are no duplicates. Try moving more headers into your pch files. Check if you are using the /Gm compiler switch and remove it. ( mimimum rebuild, the IDE will automatcally throw /FD instead if you get rid of /Gm, and scanning a /FD created idb file is faster ) Take a look at your h files and declare some of them "system headers" so they don't get timestamp checked, do this by adding those files to the "sysincl.dat" file. Always backup your sysincl.dat file before modifying it. Eliminate some of the header files from your sysincl.dat that you "know" you don't use. Be careful if you do this, you might be including them and just not know it, if you remove entries and you were using them, this will actually make things slower. Always backup your sysincl.dat file before modifying it, just in case. I have a couple of other tricks that might work if this doesn't work. Hope this helps :) KiP int f,r,a,c,t,A,l=42;main(){while(--l>-42)for(t=-60;t++<20;putch('J'-f))for(A=a=r=f=0;++f<42&&r*r+A*A<7056;c=r+t,a=l+A,r=(c*c-a*a)/42,A=c*a/21);}