That fixed it, thanks!

First off, I have an encrypted backup of my wallet.dat file, so hopefully I am safe. That said, I made a stupid, and appeared to have borked bitcoin QT.  I was working on visualizing a program, and the final build ended up being larger than by root drive (a SSD) could handle. As it was in the middle of saving a 20+ gig file, I realized that it would hit a wall, and crash. So I opened spacesniffer to find a large file, and saw the 15 gig Bitcoin QT blocks file. I closed Bitcoin QT, and deleted its file of blocks, assuming that as the wallet.dat file was elsewhere, the next time it opened, it would just have to redownload the blocks.

Now the next day, I start up Bitcoin QT, and as I had expected, it saw that it had no blocks, and looked like it was going to start downloading. First it said that it needed some 25k blocks, as a rough estimate, then later it said it needed 285393 blocks, indicating that it had connected to the servers and that it now knew what it needed.

Here is where the problem begins. You see it has been 2 days, and it has not downloaded anything. At least in Bitcoin QT, it shows 0 blocks. The weird part is that if I point spacesniffer at my SSD, I can see that the 15 gig blocks file is back, looking fully rebuilt. As this is happening, I don't believe it is a connection issue, it clearly saw what it needed, and from the perspective of my filesystem, it looks like it got what it needed. Why does the program not see the blocks that it has downloaded?