MHDD

[bigal.nz]

Hiya All,

I was hoping to get some help with MHDD - which I am trying to learn better.

I am interested to know how it could be used to create a raw image of a disk?

I currently run MHDD off a CD and while it detects all my disks I have no where to write a output file to, and if I can only do it in 2Gb chunks it will take a long time!!

Any answers, PM or otherwise gratefully accepted.

Cheers

-Al

[N.C.]

Hi,

MHDD is generally for diagnosing and testing purpose, not for making images.
I think your answer is simple no.

Janos

[bigal.nz]

Hi,

MHDD is generally for diagnosing and testing purpose, not for making images.
I think your answer is simple no.

Janos

Well it does have the TOF and ATOF commands......

-Al

[foo]

i created a bootable grub usb drive, and i have it loading MHDD from there, which i can write to

[masterpiece]

sure you can use tof and atof ... you could join raw image into a linux box simply with emebedded commands

[HDDME]

i created a bootable grub usb drive, and i have it loading MHDD from there, which i can write to

sure you can use tof and atof ... you could join raw image into a linux box simply with embedded commands

Can you guys or anyone else tell me how to use the series of image files MHDD made with ATOF... to transfer onto the donor?

I would of thought the BINS had embedded Sector addresses like META tags; or MHDD could use the LOG to auto address's their respected starting location..
but the log doesn't even have the Start points for the files.. when I BREAK'd ATOF after 8 (2GB) files were made...
I have to manually figure out the consecutive Image file's starting points... I wrote down the starting points and image file name given, when it made them, but the displayed Sector/LBA numbers for the consecutive Image files don't lineup.. Is it displaying where the last image ended or where the new image file began? if its displaying where the last ended do you add the sector size to get the next starting point? or do you just add "1" byte to the number...? and FF them (other than batching.).
Basically the problem is MHDD isn't clear about what the "sector/LBA" means: START or ENDING?
For example, you ATOF'd starting 11,264,000 but it lists 13,361,374 as the ending point of the first image; or the starting point of the next file..?
While on the 2nd donor, another test run reveals 13,361,495 after it says Opening:....
I don't want to cause a shift... and the patient is d34d. Now what? How do I reassemble? there should be an "AFF" as there is an ATOF... butt I guess not.

Anyone have any guidance on this? PM me if need be. Thanks

[HDDME]

If its displaying where the last ended do you add the sector size to get the next starting point? or do you just add "1" byte to the number...? and FF them (other than batching.).

I meant to say:

If its displaying the last sector copied in the 2GB file, or the next sector's start? So do you image to the address displayed or do you add an additional digit to the displayed sector number and FF the next image file?

Another very important thing I noticed, is some of the image file sizes are smaller then the group... and when checking the consecutive image file, it begins where the previous smaller image file left off... so basically in theory if you would image the next Normal file, to the next sector you would cause a negative shift... because the previous file was missing data but DID NOT DO A FILL IN IN THE BIN FILE.
Is there some JUMP CODE embedded in the image file where MHDD would skip the ERROR Areas and continue?
Or must you keep your own log of every error and figure out start points... perhaps I need to add a FILL IN OR SKIP extension or Configuration? I thought it did that by default.
Ideally it would be great if it wouldn't touch the areas where it doesn't have data (because of a bad read or skip)... so if a previous partial clone existed on the donor the data successfully cloned wouldn't be touched (or 00'd out), but what has been recovered would be written... Obviously starting with a donor that has been ZEROED OUT, then you keep building the clone with recovered bits...

I guess now my biggest concern is shift.. and making a BATCH..

Another is how to effectively.. cause ATOF to skip a number of BLOCKS... upon hitting a bad spot.. Other than a batched TOF.

thanks