BGman wrote:
fzabkar wrote:
The confusion in my case is due to the fact that, while WD uses the SMART feature set, 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).
Why do you want to see VSC everywhere? WD is using SCT for more than 10 years. It started with the new generation ROYL drives, Seagate started with F3> dtives, Samsung started with Trinity drives, Hitachi with ARM drives, Toshiba with xx46GSX, etc. VSC generations of drives were replaced by the SCT generation.
Try to "sniff" VDMarvel for example. You'll get nothing because all VSC's are encapsulated in a small piece of data transfered between the host and the drive...
I think you are making a big confusion.
VSC = Vendor Specific Command(s) and those are the commands that are specific to the maker and not standard ATA.
SCT is a "standard". Just because some vendors are using SCT to transmit and recieve Vendor Specific Commands and data it doen't mean that SCT is vendor specific.
Native Quantum and native Maxtor were using encapsulated commands way back .... WD used encapsulated commands even on older WDC based MCU, prior to Marvell. Marvell MCU uses encapsulated commands and even on drives prior to ROYL like Sabre, etc ... Samsung Trinity uses LBA 48 VSC and NOT encapsulated commands. I can show you oif you want. Check my Samsung research thread. There are no SCT generation when we talk about VSC.
Try to sniff WDMarvel with IDE Grabber hardware and we talk later. Just use IDE GRABBER hardware in the middle of your IDE cable and use IDE - SATA adaptor. You will be able to see the data inside the buffer and that includes the SCT or whatever "packet" of data the tool sends to the drive.
This is how one would load VSC (encapsulated) to Maxtor and Quantum using HRT :
Attachment:
1.jpg [ 25.34 KiB | Viewed 12218 times ]
Attachment:
2.jpg [ 36.3 KiB | Viewed 12218 times ]
Those VSC would be "encapsulated" as data sectors send and recieve to the buffer. If to trigger the DRQ you use some command that is SCT or SMART based or whatever it doesn't matter. As long as you make the drive accept "buffer" (DRQ) you can then send the VSC as "data" to the buffer ...
_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.