Well, if it’s looking for ntldr, then I don’t think fixboot or fixmbr from the recovery console is going to help. Those just set up the boot records on the hard drive, which exist, or it wouldn’t even know to look for ntldr. Do you have a way to verify if the ntldr file is really on the current drive? I would usually use something like BartPE, Knoppix, or some other bootable CD to see if the files are really there. If you don’t have a way to make one of those, you can put the hard drive in a different system.
If they are there, then it could be an issue with your C:\boot.ini. If it was booting from what it saw as the second drive in the system, and is now booting from the first drive, it will be looking for ntldr on the wrong drive. To fix this, though, you’ll need write access to the partition, which is probably an NTFS file system. I could be wrong, but I don’t think Knoppix supports writing to NTFS, so you would need either BartPE or to hook the drive up to a different system. The important lines are the ones with something like:
If it says disk(1), this is most likely your problem. Change that to disk(0) and it may just boot.
If the ntldr and other boot files aren’t on your now C:\ partition, then the easiest way to fix it is to do a repair install of Windows. There’s probably a number of files you could just copy over, but I’m not sure what they are off the top of my head.