Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We write a programm. From some point we want to make all operations related to files like opening file, writting to file, reading from file (normal FS calls via standart c++ API) instead of calling some OS default FS api’s call our own functions. How to make such thing? How to protect it from assembler hacks? and how to make it undoable (meaning starting from some point in our programm we will not be capable to return to normal OS APIs?)
You might be interested in writing your own file system filter that would handle that. Such a filter could then decide if it should intercept the function call basing on your criteria or it should just forward the call down to the actual file system.