Security description: how works. Or better yet: how make working a legacy FS for a noob

[Riccardo Cecchini]

I'm working on a open-source software in C# for creating a hybrid virtual drive.

However, I miserably lack deep knowledge about the working of FS in Windows.

Happens no sense errors, like the impossibility to read the properties of the files after the third file in a directory, for example, that corrected themselves out of nowhere without having consciously corrected anything.

One of my perplexity are the security descriptions: they work correctly until... the restart of the application. Then if I try to open a file I receive an "Incorrect memory address". The solution? Substitute them with an empty array. 

To be honest, for this project, security descriptions are not important, I think. But it is a question of principle. 

This is the file where the WinFsp service is handled: https://github.com/Geckos-Ink/Virtual-Hybrid-SSD-Windows/blob/main/VHSSD-dotnet/Program.cs

Yes, it's a mess to check directly the code, so I hope that these words are enough. 

I already checked the validity of the saved array and they should be correct. I don't handle the concept of "sections", but immediately seems not a problem (maybe because are cached?). 

Finally, the question of principle is also about the fact that I think that the mishandling of these aspects could bring to other errors.

For example: I checked the emulation on the virtual disk of a Crash Bandicoot rom (its used to load very rapidly the chucks to load the levels). But is used to freeze. If I compare the file on the HD and the one on the VHD the files result identical. If I try to pre-load the image on the ram (it's an option of the emulator) the game runs fine. But also: if I put a "Sleep(1)" after every read... it works slowly but, again, fine.  

I think (and I hope) that these problems, a part of bugs in my program that I've checked, could be common to a noob, due to the lack of implementation of all fundamental features.

I tried also to implement the Ex/Ea overrides, but they never will be called.

Well, I don't know how to ask this question, but do you have some guidelines to obtain the strictly necessary for a legacy working of the virtual drive? I need it to execute a VM, so are not requested immediately all features. Just strictly necessary to obtain a working hybrid drive system for reading files with stability. 

Uhm, now I have the doubt that for VM images, that are big files, I have to implement EX/EA functions, isn't it?

Thank you!

[Riccardo Cecchini]

Relatively off topic, but for security I just want to confirm that I possess the original copy of Crash Bandicoot for PS1.