Sorry for the "Captain Obvious" fly-by but...
If you have the database at a point where it's barking about running DBCC CHECKDB, have you given that a shot? Let DBCC put the pieces together if it can. If it can't, well, you may be out of luck.
Regarding the "recovery software" I'd avoid getting my hopes up. I'm no expert but I believe most of this type of software is "file recovery" not "database recovery" so simply having a [copy] of a corrupted file won't be enough - you'll need to give the software access to the physical box (or drive) that crashed (read: the original drive will need to be available). Good luck and godspeed.
<my two cents>
If the database was on a server that is [several versions] out of mainstream support (did I get that math right? 2000, 2005, 2008, 2008 R2, 2012) I'd consider this recovery exercise to be directly related to the decision not to upgrade [12-year-old] software. I'd report the database to be irreparable and irrecoverable since you have no backup. This jab is .:[NOT]:. directed at you, but at the decision-makers that allow this situation to happen. There. I'm done ranting now. My apologies to all the gentle readers of SQLServerCentral.com. This stuff just fires me up. I wish you the best of luck.
</my two cents>