G
Guest
Hello Everyone,
The problem itself seems to be not on the system side but it still is not
quite obvious.
My system has 2 volumes: 1st C: with system/drivers only and 2nd D: with our
custom software. C: is always protected, D: has 2 write through folders. I
need to be able to modify one additional file (located outside write through
folders) from time to time without disabling write protection for the whole
volume D:.
FbwfCommitFile works fine when called from my MFC application as long as my
file was modified and save in eg. Notepad/Wordpad.
If my file was modified and saved inside my MFC application then
FbwfCommitFile returns error code 53. I'm not sure if I found the correct
error definition: ERROR_BAD_NETPATH. Ethernet controller in my system is
disabled. There are some network related components but I tried to remove as
many of them as I could.
As for saving the file in my MFC application it is performed by one
subsystem - I call a function provided by a custom library. It uses fopen,
fputs and fclose functions. There might be something wrong there but I can't
tell - this is not my library. I only remember having similar issue with the
old EWF when it was allowed to write through it if the file was of the same
size.
Does anyone have any suggestions. I would appreciate any help.
Best regards,
Tom
The problem itself seems to be not on the system side but it still is not
quite obvious.
My system has 2 volumes: 1st C: with system/drivers only and 2nd D: with our
custom software. C: is always protected, D: has 2 write through folders. I
need to be able to modify one additional file (located outside write through
folders) from time to time without disabling write protection for the whole
volume D:.
FbwfCommitFile works fine when called from my MFC application as long as my
file was modified and save in eg. Notepad/Wordpad.
If my file was modified and saved inside my MFC application then
FbwfCommitFile returns error code 53. I'm not sure if I found the correct
error definition: ERROR_BAD_NETPATH. Ethernet controller in my system is
disabled. There are some network related components but I tried to remove as
many of them as I could.
As for saving the file in my MFC application it is performed by one
subsystem - I call a function provided by a custom library. It uses fopen,
fputs and fclose functions. There might be something wrong there but I can't
tell - this is not my library. I only remember having similar issue with the
old EWF when it was allowed to write through it if the file was of the same
size.
Does anyone have any suggestions. I would appreciate any help.
Best regards,
Tom