Romex Software Forum

i am trying the 5.7.0 version, and when use the remove ramdisk feature it is very common to obtain the windows warning about damage was produce and blablabla. Also some event error appears on the eventvwr...

The warning/event viewer entry can be avoided by using the Safely Remove Hardware option to remove the ramdisk first (see here for instructions on doing this in Windows 10).

You should see exactly the same thing happen if you unplug a USB memory stick (without doing "Safe Remove" first) so it's unlikely that Romex would consider this a bug.

but really damages were produced ? that's the important question on the background.
And the Ramdisk is configured to be Direct IO Disk, so i think that the safe unmont doesnt proceed on this question.

If you have any open files or folder on the ramdisk at the time of its removal (and this includes a Windows Explorer session displaying the contents of a folder on the disk) then it will qualify as "in use" (and Safe Removal will say it cannot safely remove it also). Process Explorer can be used to find out which program (or process) has a specific file or folder open.

Force-unmounting a ramdisk in Windows before removing it should avoid any such issues (two ways of doing this are given here) but doing so probably involves more effort than just acknowledging the error message and clearing the Event Viewer log.

^^ none of that, proceed. All is closed. The problem happen even if we use the save content function previously.

@arfgh, what's your Windows OS? Win XP? Did this issue happen in the 5.6.0 version?
Thanks.

yes in 5.6.0, but less times so far.

Windows XP X64 SP2

Can you upload screenshots of the Windows warning and the Windows event on this problem? Thank you!

01 - Ok, the problem is isolated now. Some times appears if we manually save the ramdisk content, and then remove it, with its own saving before to remove.

02 - But happen all times if we just remove it, where the ramdisk settings save the content before to remove it.

See all the errors that happen whith this last way to remove.
I am using the 5.7.0 Server shareware version, near to expire.

Write delayed error



Event Viewer events at once



event IDs are: 57 26 50 57 57 from top to down list.

Can you post the event messages that issued by "FancyRd"?
We tested again in Windows XP x64 on our platforms, but don't see this problem. It seems that some processes are still using the ramdisk when you remove it. Perhaps you may try the SCSI type instead of DirectIO type because Primo Ramdisk will do a force unmount before removing a SCSI ramidsk.