Mario Pilesi

Maybe because you use the flag IMDISK_API_NO_BROADCAST_NOTIFY that does not give time to completely close the handle? I get a similar behavior when I use API before turning off: - ImDiskSetAPIFlags(3) hang shutdown - ImDiskSetAPIFlags(2) fine shutdown It seems related to the 5 second limit for the shutdown. It seems related to this and this.

Maybe because you use the flag IMDISK_API_NO_BROADCAST_NOTIFY that does not give time to completely close the handle? I get a similar behavior when I use API before turning off: - ImDiskSetAPIFlags(3) hang shutdown - ImDiskSetAPIFlags(2) fine shutdown It seems related to the 5 second limit for the shutdown.

Following the instructions more carefully I managed to fill in Ramdyn with extract drive in files folder and DiscUtils in MountImg folder. Ty.

The driver (http://www.ltr-data.se/opencode.html/#ImDisk) must be extracted in the "files" folder. I don't understand which file should be downloaded and extracted with precision. The DiscUtils library and related tools must be copied in the "MountImg" folder. See the FAQ of the driver for the links: http://reboot.pro/topic/15593-faqs-and-how-tos/ Also here, I don't understand which file should be downloaded and extracted with precision. RamDyn.c: In function 'do_comm': RamDyn.c:458:40: warning:...

The driver (http://www.ltr-data.se/opencode.html/#ImDisk) must be extracted in the "files" folder. I don't understand which file should be downloaded and extracted with precision. The DiscUtils library and related tools must be copied in the "MountImg" folder. See the FAQ of the driver for the links: http://reboot.pro/topic/15593-faqs-and-how-tos/ Also here, I don't understand which file should be downloaded and extracted with precision. RamDyn.c:243:34: error: unknown type name 'DEVICE_DATA_SET_RANGE'...

Do it is difficult for me to use API after mount instead of command line switch in RamDyn? f.e. how convert this to API? -t proxy -o shm -f RamDynXXX -m "Z:" -o fix -o hd -o rw -p "/FS:NTFS /A:512 /Y /V:Test" f.e. I convert -D -m Z: to ImDiskSetAPIFlags(2) ImDiskRemoveDevice(0, 0, "Z:")

Do it is difficult for me to use API after mount instead of command line switch in RamDyn? f.e. how convert this to API? -t proxy -o shm -f RamDynXXX -m "Z:" -o fix -o hd -o rw -p "/FS:NTFS /A:512 /Y /V:Test" f.e. I convert -D -m X: to ImDiskSetAPIFlags(2) ImDiskRemoveDevice(0, 0, "X:")

Do it is difficult (p.e. complex structured data) for me to use API after mount instead of command line switch in RamDyn? f.e. how convert this to API? -t proxy -o shm -f RamDynXXX -m "Z:" -o fix -o hd -o rw -p "/FS:NTFS /A:512 /Y /V:Test" f.e. I convert -D -m X: to ImDiskSetAPIFlags(2) ImDiskRemoveDevice(0, 0, "X:")