pninja wrote:
Clearing P&G lists and doing translation can undo some effects
of the selfscan (like limitting the Max/Min Cyl. range).
This a tested solution for Ares64 drive. It worked for me once.
The resulted drive that has original size may or may not be usable.
That is the another problem which was present before geometry
information loose.
BTW, I said you can go back to the original geometries. Does this mean
you can play with translator and make the drive BIGGER ?
Why are you making fun of people?
Well, well, well...
All maxtor single head drive have the same capacity after servowriter, i.e. all athenas 20Gb, all Ares 40Gb etc.
After that, selfscan may cut drive to less capacity if he think what drive bad or marketing reason etc.
Drive with different size have many differense, and translator be here at very last stage, look like you don't understand how all of this work.
1. Lets think a little. If selfscan finished ok, then 0x33 (P LIST) and trŠ°slator _MUST_ have identical info. If you clear translator (things called by acelab p-list
) then HOW right tools can create other translator???
( really acelab create not the same translator, they have difference with track skip )
2. Max LBA stored in other place (not in translator)
3. [censored]
4. did you think what 20GB drive have the same adaptive data as 10GB ( on same physical drive )?
PS usually, if maxtor slim drive don't have serious problem with surface i make him at max capacity, i.e. Athena 10Gb -> 20Gb etc.
PS2 from you post also follows, that if we "clear P&G" & 0x33 we get drive at max capacity (this is thing i called "playing with translator to make drive BIGGER")...