Comments on: Win32 odyssey: who needs documentation? http://www.iovene.com/86 The thoughts of a computer programmer, open source supporter and free-thinker. Mon, 19 Jul 2010 23:38:11 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Eugene http://www.iovene.com/86#comment-41838 Eugene Wed, 22 Oct 2008 17:00:57 +0000 http://www.iovene.com/win32-odyssey-who-needs-documentation/#comment-41838 looking forward for more information about this. thanks for sharing. Eugene looking forward for more information about this. thanks for sharing. Eugene

]]> By: John http://www.iovene.com/86#comment-41546 John Sat, 18 Oct 2008 21:23:35 +0000 http://www.iovene.com/win32-odyssey-who-needs-documentation/#comment-41546 Well that's just silly. It sounds to me like you're upset because you don't know how to use Windows, rather than something being intrinsically wrong with Windows itself. For the sake of argument, I assumed your problem with the WSA* call was from not properly linking in the ws2_32.lib. Whether or not that was the case, I found a solution to that in no more than 2 steps knowing nothing more than cl is the compiler. Searching my local copy of MSDN for cl offers "Compiler Options (C++)" as its first suggestion for what you're looking for. Seems like a pretty good suggestion to me. A quick find on the subsequent page led to me to the correct flag. Further, I did all of this without ever taking my hand off the keyboard. In fact, the machine I did this from doesn't have a mouse hooked up to it. And I agree that using a mouse does result in a time waste. But AFAIK, to do these same steps using Fluxbox would require me to use the mouse to load MSDN if a terminal wasn't all ready open. Well that’s just silly. It sounds to me like you’re upset because you don’t know how to use Windows, rather than something being intrinsically wrong with Windows itself.

For the sake of argument, I assumed your problem with the WSA* call was from not properly linking in the ws2_32.lib. Whether or not that was the case, I found a solution to that in no more than 2 steps knowing nothing more than cl is the compiler. Searching my local copy of MSDN for cl offers “Compiler Options (C++)” as its first suggestion for what you’re looking for. Seems like a pretty good suggestion to me. A quick find on the subsequent page led to me to the correct flag.

Further, I did all of this without ever taking my hand off the keyboard. In fact, the machine I did this from doesn’t have a mouse hooked up to it. And I agree that using a mouse does result in a time waste. But AFAIK, to do these same steps using Fluxbox would require me to use the mouse to load MSDN if a terminal wasn’t all ready open.

]]>