INIT and MAKEBAD commands in MHDD

[Thatch]

My question is about the INIT and MAKEBAD commands in the MHDD utility software. In particular, I have found bad blocks by first running SCAN. I have read the docs which say to run ERASE followed by SCAN + erase delays ON, then + remap ON. I have not found any reference in the docs to INIT or MAKEBAD and would like to learn when it is appropriate to use those functions. INIT, for example, says that it resets and recalibrates the drive. "Recalibrate", that sounds important. In what cases and in what order should INIT be performed with respect to other repair related commands like ERASE and SCAN?

Regarding MAKEBAD, I think I understand that this generates a new bad block table? How does this differ from the remap ON function found in SCAN? Also, what exactly does it mean to "reset" the drive as described in the INIT command?
Thanks, -- Thatch

[N.C.]

Init makes the initial recalibration, wich is done by the powerup.
This is almost equal with the case if you press RESET button while you are using PATA drive.

Janos

[koolezt]

It's been over a year, and these questions are still pertinent. AFAIK, ATA and SMART haven't changed.

Thanks for the good info, N.C.

INIT ... is almost equal with the case if you press RESET button

explains a bit. For the benefit of us less-knowledgeable mortals, could you please elaborate and say a little more explicitly what specifically happens?

I've looked through all the documentation I could find, browsed all over the forums and googled my mouse to bits, all with no clear explanation. In fact, it seems I'm far from alone in my ignorance.

Any chance of more help from you gurus about this and the other commands?

For example,
• In the advice

  run ERASE followed by SCAN + erase delays ON

  If the first ERASE clears the entire disk, what's the point of the second erase?
   
• Do MAKEBAD and REMAP work sector-by-sector or 255-sector-block by 255-sector-block, and do they make them bad by UNC-marking or by G-List entry? In the case of the G-List option, what happens if the list fills, especially if it works by 255-sector-blocks?

Link(s) to good information sources would be welcome.