sob, there are a few ways to hide partitions. It can be just an honor system partition type, or redefining start/end, or other nefarious captain crunch decoder ring tricks so utils can't get to files. I never used that turkey (goback) but do remember it causing lots of headaches for people. I tend to be very careful of allowing anything unnatural under my filesystems except tried & true boot managers with source code.
We could keep playing remote control & try things, (I started writing a testdisk answer) but messing with an MBR/MFT this way can be dangerous. It's easy to make a typo or misunderstanding and munge it completely. If someone here knows a proven goback unhide fix then go for it. Otherwise I'd download the ntfs version of <a href="http://www.runtime.org/gdb.htm">getdataback</a>, grab all your files, and once you're sure everything is safe just blow away the drive & start fresh. It's a very good recovery program with a 30day eval. Should be fairly self explanatory but feel free to ask.
Edit: Oh, if it's still connected internally then leave it for now. The recovery scans will go much more quickly vs. USlowB.