OK, I did some testing of IMDISK, very preliminary, but enough to get an idea of the basic workings.
Since Olof asked for it, the poor guy

most probably didn't fully envision the consequences of that action

, here are my suggestions:
1) FEATURE REQUESTS (IMPORTANT):
a. possibility to specify an offset for the bootsector counted in either bytes or sectors (better) from the start of the image file to the location of the bootsector.
this will allow, besides providing a workaround for point #2)a below, a way to mount a number of non-RAW images, most notably SDI, VMDK, Virtualbox and QEMU ones (only the fixed-size type), see this for a quick reference:
http://www.911cd.net/forums//index.php?sho...19155&st=22b. BE VERY CAREFUL, IMDISK will not recognize an image with a MBR, and thus once it is mounted, if you open the drive in Explorer it will prompt for FORMATTING it.
c. the IMDISK driver, UNLIKE filedisk and VDK, appears not create a \\.\PHYSICALDRIVEx link, thus this prevents direct access to it via a DISK EDITOR if not through the mounted letter.
2) FEATURE REQUESTS (that would be nice)
a. possibility, like VDK already does, to recognize and mount full hard-disk images, i.e. those with a MBR and hidden sectors, or, at least, have a dialog like WINIMAGE has to choose which partition to connect to
b. remove, switched by the .iso extension?, the right click option to "Mount as
writeable IMDISK Virtual Disk" for .iso images
c. autodetect, from size of file?, 1.44 and 2.88 Floppy images and mount them starting with B: letter
3) REQUEST FOR DOCS
a. it seems I cannot find ANY docs/examples/howtos for the non-basic functions.

4) Bugs or however reports of something strange
a. Right click menu, it seems like IMDISK thinks that EVERY drive is an IMDISK drive, and of course it cannot unmount a non-IMDISK one
b. file association appear to be a bit messy or however non-existant, i.e. you can tell IMDISK to mount ANY file with right click (and if the file is not recognized a prompt for formatting the drive once opened in Explorer will pop up, see above), additionally a floppy image named "something.bin" was mounted by IMDISK as a CDROM drive
I'll have to find the time to do some more testing, this thingy appears to work itherwise flawlessly
A bit, but not much

off-topic:
QUOTE (Alexei)
I'd like to have same thing for HDD, i.e. "physical drive over ethernet". Is it hard to implement?
Alexei, just a
crazy idea, which I just had and didn't have the time to even try, is the following:
1) httpdisk by Bo Branten:
http://www.acc.umu.se/~bosse/2) hfs tiny webserver:
http://www.rejetto.com/hfs/I am testing just HFS right now and it appears like a real winner for a small project I am having a look at for a friend of mine, if the two work together, you could use http as the internal protocol, since HFS can allow only some IP addresses, it should be easy to "limit" it to intranet.
jaclaz