Oy. Filesystem recovery can be tough in person. It's almost impossible remotely other than pointing to alternate tools. I dislike checkdisk. It has "checked out" too many customer GB's. Good opportunity for third party recovery software though.
I presume the problem was caused by the earlier drive configuration. When drives and the system can't agree on master & slave bad things can result.
If the files are important start by isolating the drive. Image it to another drive and work on the copy. <- disclaimer for an ideal world with many extra drives.
Most important, be careful not to write anything more to the problem drive. The more that's written/changed, the less your chances of recovery.
Does Disk Management say it's a basic or dynamic disk? (As a tip, avoid dynamic unless you know clearly why you're using that type. It is rarely the right choice and can lead to data loss when drives are moved between systems.)
With the problem drive powered off (and master jumpers set appropriately), download <a href="http://www.runtime.org/gdb.htm">getdataback for NTFS</a>. Install it on your main drive. Shut down, plug in the problem drive, do the jumper thing, boot again and if Jack the Ripper...er... checkdisk tries to run, stop it. Assuming you have enough space to recover your files, run GDB.
GDB doesn't modify the existing disk. It analyzes and copies what it can find. That means you'll need as much free disk space on another drive as the files you want to recover. It has a 30day eval period which should be plenty to attempt this recovery and be happy, or curse random internet forum assistance.
Little consolation, but I've noticed an interesting phenomenon that the longer you wait to recover critical data the less critical the data becomes.
