Hello Mr Zezula,
Thanks for Responding. I apologise for my late response as i was away.
I have actually found that this type of behavior happens only when my Exe
file is placed in the folder whose path has “Space” between them.
FOr example .
If i have my file system filter driver mapped to two folders say “c:\temp”
and “c:\my sample folder” and i copy a particular exe file say in my case
winhelp.exe into both the
folders i can see that after copying i can execute the exe file perfectly
from c:\temp but never from “c:\my sample folder”.
But when i use WinHEx or Windiff to compare the contents of the file in both
the folders they are exactly the same each and every byte.
Has anyone seen something like this?
I can reproduce the issue several times now if the folder path has space
between in them then some exe files just fail to execute.
Any tips from your side will be overly helpful…
Thank you very much
Regards
Shal.
“Ladislav Zezula” wrote in message news:xxxxx@ntfsd…
> You have to map all requests going to your filter in that
> “corruption” case and thoroughly check if all of them are
> handled correctly by your driver. This is including the
> returned values and data. Compare them with the actions
> on the clean system.
>
> Try to find the as small executable as possible, it will ease
> comparing of data loaded into memory.
>
> L.
>
>
>