I've been developing Python code for dealing with .IMD files off and on. It's not complete by any stretch of imagination, but if you're comfortable with Python then you might be able to use it to do what you want: https://github.com/NF6X/pyImageDisk At this time, extracting meaningful data would require more coding. Using the provided classes to pull out raw sector data would be easy, but it does not yet have any understanding of filesystems. I do play to add support for at least some filesystems in the future, but at this time the filesystem code is just some nonfunctional skeleton classes that I'm still working on. The provided command-line utility will at least reveal details about the low level format, such as sector sizes, interleave factors, use of different sector address marks (i.e., the use of DDAM marks on the directory track of some TRS-80 formats), or weird cylinder and head numbers in the headers. It'll also do hex dumps of the entire disk image or individual sectors. And it can change interleave factors and first sector after the index pulse if that might be helpful. -- Mark J. Blair, NF6X <nf6x at nf6x.net> http://www.nf6x.net/

"Data"??!? Well, you already have the DATA, every last bit. Maybe what you want is the INFORMATION, in the form of the FILES. All too often, people will use "data" to describe the contents, which could be at MANY different levels. And, of couse, some will be shocked, amazed, and offended that anybody could possibly interpret something so obvious in any way other than as they do. recreate a "clone" duplicate on a disk, a binary image file of all of the bytes on the disk (in the order that they appear on the track), as mentioned next: On Thu, 4 Feb 2016, curiousmarc3 at gmail.com wrote: OR, a copy of one or all of the sectors on the disk (with or without the "metadata" of the headers), the files from the disk (requires software that understands the filesystem), or the information within the data within the files (obvious with a glance at a Wordstar file without Wordstar, and grossly and horribly apparent trying to derive text from Weird, WordPervert, or any other "modern" word processor) [And, of course, in situations OTHER than this one, one can not always look at the world as "files" consisting of a sequential stream of bytes.] While it is, of course, obvious [to you] what you mean, you need to be aware that some of us have bizarre alternate interpretations of what it means to extract the "data" from a disk or disk image. curiousmarc3 seems to assume that you want a file containing the bytes on the disk in the order that they are on the disk (BTW, sectors are not always in consecutive order, and files can be fragmented all over a disk), whereas I am assuming that you want a bunch of separate files, each of which contains the bytes that were in a file on the original disk, and rearranged into the sequence that they were within those files on the original disk. (That is the "DWI pyramid" of Information Science.) Most of us have extended that to include: independently derived postulates) A few of us have extended that to include that Data is derived from Chaos, and that Chaos is derived from Enlightenment. -- Grumpy Ol' Fred cisin at xenosoft.com

If you want raw data from an IMD file in some order other than the physical ordering on the original media, my Python package that I linked to previously may be helpful. It may also require some coding, but the supplied classes make it pretty easy for somebody with Python familiarity to access the contents of arbitrary sectors in a .IMD file. Even without Python programming experience, the command-line utility that comes with the package makes it easy to take a .IMD file, remove sector interleave so that the physical and logical sector ordering are the same, and then write out a new .IMD file to be processed by any other .IMD-aware programs. For example, to convert "foo.imd" to a new file "bar.imd" with no sector interleave: imdutil.py --load foo.imd --interleave 0 --save bar.imd It doesn't understand any filesystems - yet - but it may still be helpful. Documentation is admittedly lacking... the command-line utility has built-in help which can be accessed by the typical -h or --help arguments, and the classes have embedded docstrings which (savvy Python folks) can access with pydoc. And it has a unit test suite which I think tests it all out with reasonable thoroughness. Here's the --help output from the included utility script, to give y'all an idea of what it does: ~% imdutil.py -h usage: imdutil.py [-h] [-l FILENAME] [-s FILENAME] [-S] [-D] [-i SKIP] [-k SECTOR_NUM] [-u C.H.S] [-U] ImageDisk (.IMD) utility version 1.0.0a1 Copyright (C) 2016 Mark J. Blair, released under GPLv3 https://github.com/NF6X/pyImageDisk https://github.com/NF6X/pyImageDisk Arguments are processed in the order encountered, with cumulative effects upon the disk image buffer. The disk image buffer is discarded at program exit. Arguments may be abbreviated. optional arguments: -h, --help show this help message and exit -l FILENAME, --load FILENAME Load disk image buffer from file, replacing previous buffer contents. -s FILENAME, --save FILENAME Save disk image buffer to file. -S, --summary Print summary of image contents. -D, --details Print detailed description of image contents. -i SKIP, --interleave SKIP Interleave sectors with specified skip factor. -k SECTOR_NUM, --skew SECTOR_NUM Rotate sector order to place sectors with specified sector number after index pulse. -u C.H.S, --dumpsector C.H.S Print hexadecimal dump of sector. Specify the sector in cylinder.head.sector format. Use physical cylinder and head numbers, and logical sector number. -U, --dumpall Print hexadecimal dump of all sectors, in physical order. Example: imdutil.py --load mydisk.imd --summary -- Mark J. Blair, NF6X <nf6x at nf6x.net> http://www.nf6x.net/