I am running Slackware now, but I when I originally looked at it, I looked at it while running Debian Jessie. I have looked at the partition in Gparted, fdisk, cfdisk and I have also tried to reformat/unlock/reset password with the hdparm program. To no avail.

Have you tried hiren's bootcd?

If you use "dd" write at least 20 MBs of zeroes. I repeatedly found that bootloaders use the free space between MBR and the first partition (cylinder?), which produced unwanted effects later or even prevented a re-formatting.

Just to clarify for you, I know how to boot Windows. The drive I am talking about is an encrypted NTFS formatted backup drive with a hardware chip built into it that freezes the drive until it is unlocked from Windows using the device driver software in Windows.

There is NO master boot record or failing boot of any operating systems.

Please see the OP for further details. I also mentioned previously this drive has been put to the side to gather dust since I don't know the decryption password. The drive has firmware encryption. It's difficult to circumvent this encryption to wipe the partition table.

I understand. I just wanted to point out one possible source of errors if you use "dd" as suggested by some other posters.

Wonder what would happen if you took the drive out and then partitioned it? Would it simply begin to work as expected once returned?

It is likely I would probably need device drivers to read it but I could definitely wipe the drive and put it into a new external enclosure case.

Every enclosure has it's own software, so maybe it would be possible to delete partition outside of enclosure.