I had some time to do some more testing today.... I have my own stuff to write and test so I do this purely for the good of the scene.....
I tested Benq and Sammy and all was good IMHO with version 0.8.. as you know there was
small bug in 0.7 with Benq firmware...
I promised to take a look at hitachi spoofing, figured this would be Maximus's strongest area, no hurry, right! Had a look this evening... My target was to make my 79 ( the one I did all my testing on for 79Unlock, key location is 4E10...). My task to make it appear to be my Lite-On...
So DVDkey32'd my Lite-On as I don't have an Intel chipset or a spare IDE slot for a PATA-SATA adapter as my PC like so many others has a Hard drive on my primary IDE bus and a Burner and Kreon on the other...
Luckily, enough I have a Via 6421, I find it useful from time to time... for STUFF..
Lauched Maximus 0.8b, clicked "Perpare Spoofed Firmware"... picked up the 3 files and generated firmware...
Didn't open in FWTB... hardly a surprise... Max did say it wouldn't, but
Maximus: do you even know why???
I Opened the .bin file in Hexedit to have a little look.....
OMG, what a disaster...
small bit of background on hitachi
QUOTE
let me explain a small bit here.... when a Hitachi boots, it reads the checksum at 0x3E7FC... if its 0x00000000 (master checksum) it boots to normal code...
if it's not 0x0000000 it calculates the sum for range between 0x6000 and 0x3E800 in 32 bits and result should be zero.. the stored checksum at 0x3E7FC makes this happen
if the result is zero the drive boots to normal code.
if it's not is goes to Recovery code, this is in theory to allow you the fix up the drive...
this area also has an Inquiry and Identify string, but to all intents and purposes is unused, It can however be useful to say identify a spoofed drives original type...... see below
setting the master checksum is handy for modding as you can then effectively ignore it.
SO... heres what I found
The "Perpare Spoofed Firmware" left normal code untouched, so drive appears exactly as it did before the spoof...
Instead it patches the Recovery area.... As, I pointed out earlier this area could be useful for spotting the type of drive....
But guess what it now says Lite-On and FWTB can't identify that... ( maximus: no need to thank me for that, spotting it is thanks enough )
Now that's not all......
So guess where the "Perpare Spoofed Firmware" put my key, 4e10 you say....
NO!, 4f00, ... FFS Maximus... WTF is that about....
Did you even look at the code before you released... I mean did you even try it once...
As FWTB couldn't read the file, I sure most of you have not used this for Hitachi's so the damage is negligible
I manually spoofed my firmware and FWTB read it just fine and flashed the 2 sectors 4000 for the key and 3c000 for the identity/inquiry data without incident
ran DVDkey32 ( no key) and both strings were fine....
Oh and Maximus BTW....
If this was a pissing contest, I'd have let you go ahead and release FWTB 4.9 .... just to compound your mess....