I have a table whose .frm file is gone, but the .MYD and .MYI files are intact. Working on Windows under XAMPP-MySQL, I already understand basic MyISAM administration yet I need an intermediate-to-advanced walkthrough, starting as soon as we can schedule it. The goal is for you to mentor me, live, through every stage a professional would follow when a client hands over orphaned .MYD and .MYI files. I want to grasp the internal structure of each file type, learn how they interrelate, and practise the forensic techniques used to inspect raw blocks, recognise record boundaries, and reconstruct a usable table definition or at least extract the rows safely. Along the way I also need clear guidance on the limits of what is realistically recoverable and the safeguards that prevent making things worse. Please be ready to demonstrate the tooling you rely on—whether that’s MySQL utilities, hex editors, Percona Toolkit components, or your own scripts—and explain each command so I can rerun it myself after the session. By the end of the training I should be able to: • map out the structure of a typical .MYD/.MYI pair • rebuild or re-create an .frm definition when possible • dump data cleanly even when the index file is damaged • document a prevention checklist to avoid similar loss in future We can work over Zoom, Teams, or a screenshare platform you prefer; recordings of the sessions must be allowed so I can rewatch them. Time is critical, so propose your earliest slot and an outline of how many hours you anticipate we’ll need to reach competence.