TestDisk does exactly that - it scans the whole disk looking for pieces of data that look like they were JPG images (or whatever you're searching for - it has a bunch of prebuilt filters) - which is why I recommended it. However different filesystems lay out files in different places - e.g. at multiples of 512bytes or other such things, but TestDisk might not have the rules for HFS+. I suspect it will do its best nonetheless, which is why I suggested it.
I've used TestDisk against both raw devices and dd images of devices before - it should do what you want without having to mount the image. The mount command was just in case you needed it, I'm sorry it confused my post.
Cheers,
Benjie.
On 24 Oct 2011, at 22:12, James Courtier-Dutton wrote:
> The problem is I am not interested in the mounting of the device.
> What the user has done is this:
> 1) Had a working system with all their pictures on it.
> 2) Put in the Mac OS X setup disk.
> 3) setup disk formats the system. equivalent of mkfs
> 4) setup disk installs OS files.
>
> I want to get at the pictures, which means I wish to examine any parts
> of the disk that have managed to escape the mkfs and the install of OS
> files. So, essentially scan free space.
>
> I am expecting that I will have to write my own recovery program, but
> just wanted to check here first.
>
> Kind Regards
>
> James
--
Please post to: Hampshire@???
Web Interface:
https://mailman.lug.org.uk/mailman/listinfo/hampshire
LUG URL:
http://www.hantslug.org.uk
--------------------------------------------------------------
