Topic: Ping Thespecialist Or Anyone Familiar With Hddhackr? (Read 70 times)

Boobers · « **on:** March 23, 2008, 07:44:00 PM »

I got a 120G hddss.bin off of the net... When I went to load the bin onto a 120G BEV Scorpio drive, I saw this:

(IMG:http://rvsmaps.us/temp/hddhackr1.jpg)

Can anyone confirm or deny as to whether I should proceed or not??

Thanx

B

This post has been edited by Boobers: Mar 24 2008, 02:47 AM

scuba156 · « **Reply #1 on:** March 23, 2008, 10:53:00 PM »

sorry boobers, downloading a SS.bin is illegal and you know the rules on piracy

Boobers · « **Reply #2 on:** March 24, 2008, 04:32:00 AM »

Ooops...

My bust.... I thought just asking for one was a no-no

Thanx for the heads up...

B

Boobers · « **Reply #3 on:** March 24, 2008, 05:11:00 AM »

OK, let me ask this... I am just talking in general about the hddss.bin file, rather than specifics. If this strays into verboten territory, mods feel free to delete the post and whack my wee-wee (Not too hard, please. I bruise easy

).

Anyways, I pulled my own hddss.bin file off of one of my own working 20G 360 HDs... When I ran it thru the HDDHackr process, it produced the same kind of info as shown above, except instead of listing FUJITSU info, it listed SEAGATE info. Which makes sense, since the stock 20G 360 HD was a SEAGATE.

So, my point is, since everyone who uses HDDHackr knows that you have to use a WD BEVS HD, there is precedence for taking an hddss.bin file that was from one brand of drive and writing it to a WD BEVS drive. Ergo, what I show above should work just fine...

Can anyone point out a flaw in that logic??

B

Boobers · « **Reply #4 on:** March 24, 2008, 05:29:00 AM »

For those who may have the same question, it appears to work just fine...

B

Author Topic: Ping Thespecialist Or Anyone Familiar With Hddhackr? (Read 70 times)