Ver 6.3.16 Bug In Seagate [ Rom Working ]

[Amarbir[CDR-Labs]]

Hello,
Today i Got a 3F Code Seagate ST3100524AS Drive That Was Clicking .I Wanted To Manipulate The Rom So That To Be Sure Its a Head Issue .The F3 Common Utility Was Loaded And ROM Was Read ,Its Saving a 512KB Rom As 1024KB . Two To Three Days Earlier i Was Traning a Canadian Based Company And i Imported Head Adaptives And Wrote To Patient Rom And The Rom Gave Errors after it was written ,Writing original rom was ok but rom in which head adaptives were imported was not ,So i Find The same rom routines to be very buggy can you folks also give your inputs .The head adaptives drive was not the 3F i no not remember which family but i can ask .I do not want to go back to ver 6.1 from 6.3

[digitalsupport]

Thats becourse F3 common util has default minimum image size 0x00100000 = 1.024 KB
If you want to use F3 common util you can set autodetect of ROM size by setting 0x00000000 and your ROM will be detected as 512KB
You can also select the correct family 3F Pharaoh where autodetect is set by default.
So from my point of view its not a bug, but a feature

[Nick_TS]

Source of the post If you want to use F3 common util you can set autodetect of ROM size by setting 0x00000000 and your ROM will be detected as 512KB

Also, you can set ROM size by 0x00080000 = 512 KB or divide the ROM by two parts (512 KB).
And yes... it's a feature

[Amarbir[CDR-Labs]]

Come On Guys ,
How Can It Be a Feature ,In The Common Utility The Default Should Be 0x0000000 So That Rom Is Auto detected .Why On Earth Should It Be 0x00100000

[Amarbir[CDR-Labs]]

Dimitry ,
Please Look Into This Please Tell the coding team to set it 0x00000000 So that its auto detected ,If a Person wants to change it to a particular value he can