I have been searching endlessly to find the source code for "Programming a Multiplayer FPS in DirectX." I have not yet been able to find any websites that will give me the source code. Please do not tell me to throw away or sell the book because I just bought it. 

Please help me because the current source code is badly arranged and has lots of errors... It also seems to be missing files or they are out of place in the source code... 

There were two editions? 

And here is the error that I get when I press play.

Program: Game.exe

Module:

File: f:\dd\vctools\crt\crtw32\misc\i386\chkesp.c

Line: 55

The value of ESP was not properly saved across a function call. This is usually a result of calling a function decleared with one calling convention with a function pointer declared with a different calling convention.

(Press Retry to debug the application)

When I click retry in the popup, I get sent to a window that claims that chkesp.c was not found, but when i check out the call stack, it says that the error is coming from the following:

>    Game.exe!_chkesp(...) Line 64    C
     Game.exe!Mesh::Mesh(char *,char *)    Unknown
     Game.exe!_GetFileAttributesExW@12()    Unknown
     Game.exe!_GetFileAttributesExW@12()    Unknown
     Game.exe!_GetFileAttributesExW@12()    Unknown
     Game.exe!_GetFileAttributesExW@12()    Unknown
     Game.exe!_GetFileAttributesExW@12()    C++
     Game.exe!_GetFileAttributesExW@12()    C++
     Game.exe!__except_handler3()    Unknown
     ntdll.dll!770a2500()    Unknown
     [Frames below may be incorrect and/or missing, no symbols loaded for ntdll.dll]    
     ntdll.dll!77092fba()    Unknown

Im pretty sure this means that something went wrong in the Mesh class, because in Windows XP, I get the same error...
 

Here is what I have tried:

I put all the files in the Engine folder into the normal project, but the Engine folder has not source files, just a static link library file. Perhaps this could be solved if I just link with the lib and not try to include all of the project files?

As a side note, I am not just starting off in programming, but I, as you have probably seen in other posts, was still using VC++ 6, VC++ 4, VS 2003, Borland 3, and Watcom... I still have those on my computer, believe it or not haha!

My reason for using DX9 is because I do not like dealing with the shaders... They are too annoying and do too little things in exchange for 20 mins of work... I can program in DirectX 12, but I choose not to because of the lack of documentation. (I learned from Frank Luna's book) 

I also know how to use OpenGL 3 - 4.5, but choose not to because I have difficulties with rendering fog, terrain, and other things that require a shader... 

1 hour ago, rjhwinner03 said:

They are too annoying and do too little things in exchange for 20 mins of work...

That's not very much work at all. I think I spend more than double that time just compiling my code (ie. not actually working) every morning.You'll find as you gain experience that 20 minutes is a trivial amount of time - 20 minutes is well in the noise in the lifetime of any substantial project. It's certainly not an excuse I would accept to not to do things properly.

If you're not willing to accept that the book you're using won't actually be all that helpful to you, you might try not bothering trying to find the source and instead reconstructing it from the book. I suggest that you will probably learn more that way. And yes, get rid of the old compilers. You mentioned in another thread that you got some code working in VS 2017, just use that.

Good news:

I got the source code for the book working... 

Bad news:

I used VC++ 6, and I plan to continue using it for this project...

Again my advice is stop messing around with DX9. I literally had a working a working program that complied and ran on Windows 7 using DX9.  When I took to over to Windows 10 with the latest version of Visual Studio, I got a bunch of compiles errors.  The old executable itself actually stopped running after a particular Windows 10 update. I messed with it for a while trying to get it to compile and run and then decided it was a waste of time ...... and this was my OWN code! Rather than keep dicking with it further, I decided just to take the code that I needed from it and move to DX11.  Yes it took some doing but now I have a running program on the latest version of Visual Studio and I feel it was way worth it.

Really you should bite the bullet and make the move.  I admit that Microsoft has changed too much stuff with Direct X and provided too little help as far as documentation goes. Even most DX11 books are out of date. However at this point you just need to get over that hump. Take an up to date working DX11 or 12 program and go from there. It wont be a ready to go FPS but you should really learn to program that from the ground up, instead of just taking someones ancient code and tacking crap on to it which will give you more headaches in the long run.

Seriously, start here:

https://www.3dgep.com/introduction-to-directx-11/

You will have working code with a good tutorial.  This is exactly what I did. Now I'm building my engine and making progress every day without suffering with strange compile errors, run errors, bla bla bla......If this was your first post about this, it might be worth it to fix the old DX9 stuff, but clearly it's giving you trouble (which again is somewhat understandable given the the changes in Direct X). It seems you've been stalled for weeks, so IMHO it's time to move forward.

If I read this correctly, this website is a tutorial on how to make a game engine with DirectX 11?