Angus Mackenzie

Noted above re admin privileges. I've also installed Process Hacker and resulting in finding out what the closing issue was. I can now close the drive letter every time with no warning popups being generated. :) Process Hacker was indicating that DiscUtilesDevio.exe had a file handle to the vmdk file which was expected but nothing else. The penny then dropped that ImDisk Virtual Disk Driver (IDVDD) was open on the screen at the time so it must also have some connection to it (cant see it though in...

Noted above re admin privileges. I've also installed Process Hacker and resulting in finding out what the closing issue was. I can now close the drive letter every time with no warning popups being generated. :) Process Hacker was indicating that DiscUtilesDevio.exe had a file handle to the vmdk file which was expected but nothing else. The penny then dropped that ImDisk Virtual Disk Driver (IDVDD) was open on the screen at the time so it must also have some connection to it (cant see it though in...

Wizard, v. helpful suggestions resulting in now being able to close the mounted disk with no warnings :) thank-you.

Noted above re admin privileges. I've also installed Process Hacker and resulting in finding out what the closing issue was. I can now close the drive letter every time with no warning popups being generated. :) Process Hacker was indicating that DiscUtilesDevio.exe had a file handle to the vmdk file which was expected but nothing else. The penny then dropped that ImDisk Virtual Disk Driver (IDVDD) was open on the screen at the time so it must also have some connection to it (cant see it though in...

Noted above re admin privileges. I've also installed Process Hacker and resulting in finding out what the closing issue was. I can now close the drive letter every time with no warning popups being generated. :) Process Hacker was indicating that DiscUtilesDevio.exe had a file handle to the vmdk file which was expected but nothing elseThe penny then dropped that ImDisk Virtual Disk Driver (IDVDD) was open on the screen so it must also have some connection to it (cant see it though in process hacker)...

tried creating the partitions in both Xp and Win 7 as suggested and it made no difference. Then tried to move the .vdi image between debian, xp and win 7 and found the same thing i.e. most of the time the disk was seen but not the partition details which was the same as seen in imdisk. Time to try different so decided to start with virtual disk types. VHD: - tried that in the hope of mounting it directlyon my pc after using it on a debian image but soon found that to do that you appear to need hyperV...

Attached are 2 files. 1) a screenshot of what it looks like when I load the .vdi into the mount image file software - note that Partition 1 is showing no name 2) a copy of the test .vdi file within a 7zip file. The vdi was created within Vbox as a 350MB fixed sized vdi and then formatted as ntfs within gnome-disks. It mounts fine in linux and I added a test file via nano. Linux was then powered down and ImDisk mount image file was then used to attempt to mount it. It would not mount using partition...

Thanks for the reply. The current partition is large and not really shareable so I'll make an other smaller one and will be able to share that. Thanks for the info re the use of partition '0'. I'm currently using VBox v6.0.14 with a Debian 10 image running within it and I created the .vdi using VirtualBox when setting up the Debian settinigs/ infrastructure. ImDisk is v2.0.10 running on the host PC which is a Windows 10 (10.0.18362.476) - 1903 version and fully patched.