Wierd Problem … New Feature?
Hello,
I have found the problem in the cache problem.
I was tampering with a vital Windows System File, ntdll.dll, because I needed to get my program to work that I’m making. I realized later that I forgot a . in a line in the code, after numerous BSODs. Then after correcting the file, later on that day I randomly got a BSOD and then 3 hours later I got another BSOD. After analyzing the ntdll.dll file and finding no error, I remembered, “I have eBoostr running…” and then I removed the device and rebuilt cache. So far no problems!
I guess the problem was that it cached the bad ntdll.dll and never updated with the new one.
As a windows programmer, I can’t think of a way around this except I remember reading somewhere that windows has a value for the rarity of a file being changed. However, there should be a way in settings to automatically or manually check for updated cache files. Not to rebuild cache just check for updated versions of files.
Oct 08, 2007
We are using size, time and index of the file to check its version. If any of these fields is incorrect we remove such file from the cache. Our driver catches every write operation and updates this file in cache if necessary.
It seems that there only one way to break the cache is to change the file outside OS and leave all attributes the same.
Oct 08, 2007
My bad actually what I did was modify the file outside the OS and replace, as you said. I needed to replace the file but Windows wouldn’t let me if I replaced it from within.
How often does it do this check???
Oct 09, 2007
eBoostr checks the file at every file open operation. We will try to implement an option to delete the selected file from the cache in the next release.