I started using Code::Blocks months ago (August of last year), and I haven't had any problem with it until now. I started working on a project a few months back, but stopped it about 3 months ago. I never opened Code::Blocks except to play tetris and snake under the BYO Games plugin. Just recently, I opened Code::Blocks back up to do some actual work, and I hit Ctrl+F9 to build the file. (I'm programming in C, btw) Nothing happens. I hit F9 to build the file then run it. Nothing happens. I move the file that I had built previously (yes, I KNOW that it builds because I have built it before) into a different directory, and selected the "Run" option under the "Build" menu. It asked me if I wanted to build the file before I tried to run it, and I selected "Yes". Nothing happens!(*) whenever I try to build any .c file, it doesn't do it. No "building" message pops up (which at this point is a vague memory, but I'd recognize it when I see it). I thought maybe something got messed up with my computer, so I re-installed the binary release 10.05 (which i already had installed before) and that didn't fix anything.
(*) Actually, something weird happens when I select "No". It tries to run the program for a few milliseconds, then returns 0x00 with the usual "Press any key to continue". I'm not sure of the order, exactly, but when I ask it to just run the file and pressing "No" when it asks me to build, it goes through two cycles of that. e.g., I pres Ctrl+F10, and I select "No", it'll try to run the program and then automatically ask me if I want to build it again after I exit the command prompt style executable. If I hit Ctrl+F10 again, it only asks me once. If I hit either Ctrl+F9, F9, or select the corresponding options in the menu (nothing happens), then press Ctrl+F10 or select the "Run" option, It'll ask me to build it, and try to run it, twice.
So here's the real question: How can I fix this problem?
Your help is greatly appreciated.

-Mevans
NOTE: I am running Windows 7 on my emachines netbook, if that is usefull in solving this problem.