May 5th, 2019, 8:13
May 5th, 2019, 10:12
May 5th, 2019, 11:29
May 8th, 2019, 6:06
Spildit wrote:Reading by ID the firmware tool will issue a VENDOR SPECIFIC COMMAND with the module ID number and the drive will retrieve that to the buffer to be fetched by the tool.
Reading by COPY 0 / COPY 1 the tool will issue a VENDOR SPECIFIC COMMAND to read PHYISICAL locations of the drive. The tool itself will chek DIR to know where the modules are located and will issue a command to read those exact places on SA rather then issuing just a command with the module ID number to read and let the drive send the data. On module reading by ID you don't care for the place where the modules are stored as the drive will handle that for you but the drive must have a valid loaded DIR so that the drive knows where to get the modules from. When reading by copy 0, copy 1, etc you just need for the drive to be able to retrieve the data on those spots but you do need to know how to parse DIR yourself so that you know what sectors to read for whatever module.
Composite reading is when you set the tool to read from head 0 and when it finds spots that it can't read it shitch to head 1 so that it will read portion that can't be read with head 0 from head 1 or copy 0 and copy1 ... Idea is to make good module from portion that can't be read on one copy but can be read on the other.
Tracks readin will use even another VSC (vendor specific command). That one you inser the number of the (firmware) track that you want to read and the drive will retrieve all the data on that track. This is of use for example if DIR is damaged and drive can't retrieve anything by ID as it no longer knows the locations of modules but a track reading command will still send to your tool all the data on that track. From there you can search/CRAVE modules on the tracks, get native module 01 to load to RAM and drive wll be aware of module location now to work by ID ...
May 8th, 2019, 20:24
May 10th, 2019, 14:26
July 30th, 2019, 14:29
July 30th, 2019, 15:17
July 30th, 2019, 15:33
Amarbir[CDR-Labs] wrote:Hi ,
First Bye a Better Tool Like PC3K ,You Will Have More Control Over Hard DRives ,Secondly in The Location of The DIR Module Is Wrong In Rom You Can Get The Issue You Stated Above ,In That Case You Have To Carve ABA Location FRom Tracks For DIR Module And Then Update ROM For The Same
July 30th, 2019, 15:51
HddDonorMarket wrote:Amarbir[CDR-Labs] wrote:Hi ,
First Bye a Better Tool Like PC3K ,You Will Have More Control Over Hard DRives ,Secondly in The Location of The DIR Module Is Wrong In Rom You Can Get The Issue You Stated Above ,In That Case You Have To Carve ABA Location FRom Tracks For DIR Module And Then Update ROM For The Same
Thanks för response.
I know I should buy pc3k. But money problem for for me now. I hope In future.
So.
Is it solution to ofset that module to another track. I could do it with MRT . I did before sometime when bad track in sa . It would make adjustments automatically that you told. I hope It's a way . I don't know manual way that you told above.
Powered by phpBB © phpBB Group.