Part of your problem lies right here:
Quote:
g++.exe -D__DEBUG__ "../codeProject code/myClient.o" -o "sunday222.exe" -L"C:/Dev-Cpp/lib" -L"C:/Dev-Cpp/lib" "../Program Files (x86)/Microsoft SDKs/Windows/v7.0A/Lib/WSock32.Lib
" C:/Dev-Cpp/lib/debug/libstdc++.a -g3
GCC and VC (static) libraries are NOT compatible. Here you're trying to include a VC lib into a GCC project. Whenever I use Winsock and GCC, I include ws2_32.a (it'll be in the /Dev-Cpp/Lib folder (have a close look - they're all .a files)
Something you may like to consider - Code::Blocks can be downloaded with the MinGW compiler suite (just as DevCpp can) It is however, still in active development, cross-platform (irrelevant to you, I assume) and
(*) It can load VS projects - you'd be surprised at just how much pain can be caused when you don't have all of the project settings. Importing a VS project is considerably faster and more reliable than re-creating a project from source code and trying to guess all of the build settings.
I also note from the first compile error that it seems likely that you need to include(in the build process, NOT via #include directives) a number of files called something like "myException.cpp" also "myTcpSocket.cpp".
I started with DevCpp, but after someone shared Code::Blocks with me haven't looked back (except for the odd devPak, which I can import using C::B anyways)
You can download the IDE on it's own for about 10-20 meg or so, you can even use the minGW compiler you already have (though it's likely the CB package with compiler included contains a more recent version of the compiler)