Thanks for the report.
I just removed this version. I forgot to remove various things from the code during my tests.
In some cases, RamDiskUI can cause copied files to have their archive attribute removed even if the synchronization feature is not used.
In RamDyn, the cleanup function may not work properly, but it would be difficult to say in which way.
In any case, I see nothing that could lead to a data loss.
Anyway, this is dirty enough to be removed. I will fix all that and upload a new version right away.
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just tried to recompile RamDyn.exe in version 20190407, and its size (and code) did not change. Are you sure to use the exact build of MinGW mentioned in the source (see readme.txt)?
About MinGW 8.1.0, I prefer to skip this version. There are various issues and bugs. One of these is that it is no longer possible to use an architecture target for only a specific function. For instance in RamDyn.c, this means that we would have to write a separate source file just for the "data_search_avx" function.
Besides, I have seen nothing in the release note about performance improvement.
So I will keep the version 7 of MinGW for a while and will wait for the version 9.
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Are you using simultaneously the dynamic ramdisks, a mount point and the cleanup function (so, not TRIM)?
I made a message here. And the documentation section also mention this bug. This is a bug of the system, and I see no workaround...
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just made tests in a virtual machine, and the system cannot even shutdown. I also seen RamDyn disappear from the list of process...
So I also removed the version I just uploaded.
This is giving me a headache...
❤️
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I installed the last update in 2 machines to check, and the last update freezes windows.
I could not even login into windows, I had to boot into safe mode to uninstall it.
Anyone?
Last edit: paradis pal 2019-04-19
Thanks for the report.
I just removed this version. I forgot to remove various things from the code during my tests.
In some cases, RamDiskUI can cause copied files to have their archive attribute removed even if the synchronization feature is not used.
In RamDyn, the cleanup function may not work properly, but it would be difficult to say in which way.
In any case, I see nothing that could lead to a data loss.
Anyway, this is dirty enough to be removed. I will fix all that and upload a new version right away.
I recompiled the file RamDyn.exe using MinGW 7.3.0 and until now seems to work just fine.
It has samlled size though, 1KB smaller!
BTW, only RamDyn.exe wouldn't be compiled using version 8.1.0!
Last edit: paradis pal 2019-04-19
Last edit: paradis pal 2019-04-19
New version uploaded.
I just tried to recompile RamDyn.exe in version 20190407, and its size (and code) did not change. Are you sure to use the exact build of MinGW mentioned in the source (see readme.txt)?
About MinGW 8.1.0, I prefer to skip this version. There are various issues and bugs. One of these is that it is no longer possible to use an architecture target for only a specific function. For instance in RamDyn.c, this means that we would have to write a separate source file just for the "data_search_avx" function.
Besides, I have seen nothing in the release note about performance improvement.
So I will keep the version 7 of MinGW for a while and will wait for the version 9.
I copmiled as it explained, all the files has the same size differenet CRC though, but only RamDyn was smaller.
UPDATE:
With the new veriosn I could log in, but windows freezed after a while, not windows, onlt explorer.exe and I couldn't run file explorer,
I restarted same thing happens, it freezed again. the whole windows
Now I can log in but it still freezes after a while.
that is odd
Are you using simultaneously the dynamic ramdisks, a mount point and the cleanup function (so, not TRIM)?
I made a message here. And the documentation section also mention this bug. This is a bug of the system, and I see no workaround...
No, I am using the same settings as before, and the veriosn 20190130 works fine.
I just made tests in a virtual machine, and the system cannot even shutdown. I also seen RamDyn disappear from the list of process...
So I also removed the version I just uploaded.
This is giving me a headache...
Same thing, couldn't shut down, but noow I can log in, still freezes after a while though.
No worries, you are always the man :)
Fixed. This time it should be the good one. :)
Been testing for 10 mintues now, no problem, loging on, reestrating, shuting down.
That was super fast. Again you prove you are the man :)
Happy Easter!