Windows

• Can you do symlinks in Windows? Yes, yes you can (NTFS anyways)
  • guzie links to a bunch of good resources

Visual Studio

• The procedure entry point freeaddrinfo could not be located in the dynamic library WS2_32.dll — This happened to me when I compiled my app on WinXP (which used the Winsock2 *addrinfo functions via Ws2tcpip.h) and then tried running the resulting binary on Win2k. According to the freeaddrinfo page on MSDN the *addrinfo functions moved from Wspiapi.h in Win2k to Ws2tcpip.h starting with Win2k server. The solution is to #include <Wspiapi.h> after #include <Ws2tcpip.h>. When compiled on WinXP seems to play nice on Win2k.
• output/print functions like fputs(), vfprintf(), etc. crash! in multithreaded apps, the _lock_file function tries to figure out how to lock filehandles, and if you mix c-libraries the type of filehandles are incorrectly detected and the incorrect method to lock them is run (EnterCriticalSection), resulting in a crash.
• error LNK2019: unresolved external symbol _WinMain@16 referenced in function _WinMainCRTStartup. You've picked Subsystem: Windows when you really want Subsystem: Console. GUI Win32 apps want the hideous int WinMain() function while Console apps will run fine with the standard int main().

  Subsystem setting is located: Project > Properties... > Configuration Properties > Linker > System

• Run-Time Check Failure #2 - Stack around variable 'somebuf' was corrupted. Congratulations, you've smashed the stack, meaning you've overrun a statically allocated buffer and have written data to the call stack! Lucky for you, the debug runtimes Visual Studio uses can detect this. What you need to do is figure out where you're overrunning the buffer; in my case I passed an incorrect size arg to _vsnprintf()

Linux

• Argh?! Why does gentoo's portage invoke wget with a completely useless progressbar-scheme where the progress bar just slides back and forth. I can't seem to replicate this behavior, all i can find are --progress=dot and --progress=bar and they are both very sane.
• Getting a USB "jumpdrive" to work

  In win32, when you insert a USB stick it is magically detected, mounted to Letter:/, a window pops up and you can just use it. On my install of Gentoo Linux this was not so... do /dev entry would appear so I could not mount the thing

  Here's what I did (Linux 2.6.x kernel btw):

  • emerge coldplug (install coldplug for monitoring usb)
  • /etc/init.d/coldplug start (start coldplug)
  • cd /usr/src/linux
  • make menuconfig
    • enable 'generic SCSI' device driver (<M>odule)
    • enable 'USB mass storage' device driver (<M>odule)
    • save settings and quit 'make menuconfig'
  • make modules modules_install (compile and install modules)
  • plug jumpdrive back in
  • tail -n 20 /var/log/messages, you should see the device detected and assigned a SCSI device
  • ls /dev/sda*, if you have no entries it didn't work
  • mkdir /mnt/jumpdrive (create a mountpoint for the jumpdrive)
  • mount /dev/sda2 mnt/jumpdrive
• Getting a Lucent Wifi Card to work (Orinoco)
• bootloader-change-default-kernel.txt
• crontab-e-Permission-denied.txt
• perl-cpan-wont-work.txt
• vixie-cron-vs-vcron.txt