In-depth technology research: finding new ways to recover data, accessing firmware, writing programs, reading bits off the platter, recovering data from dust.
Please do not post
questions about data recovery cases here (use this forum
instead). This forum is for topics on finding new ways to recover data. Accessing firmware, writing programs, reading bits off the platter, recovering data from dust...
June 14th, 2017, 17:16
fzabkar wrote:WD's vendor specific command format in log BEh is identical to that used in SCT command/status log E0h (ie Action Code + Function Code + parameter list).
On disks with the WDC mPU (eg Egle), 2 (!) Command systems worked through the 0BEh log
TRUE !!!! Later models of WDC mPU would accept commands by 0xBE
June 14th, 2017, 17:22
Example of IDE Grabber "sniffing" VSC inside "encapsulated" commands :http://www.hddoracle.com/viewtopic.php? ... 1735#p9406
June 14th, 2017, 23:18
Spildit wrote:TRUE !!!! Later models of WDC mPU would accept commands by 0xBE
With 0BEh worked even PATA drives. (even 10GB)
But the first system of SCT is quite specific.(аnd the "instruction"- command set was small)
Powered by phpBB © phpBB Group.