Microsoft Legacy OS
--
Questions
--
Followers
Top Experts
Windows OS seems to cache .exe file and not run a new one in the directory
I had an executable on a network shared drive and had some one on another WS rebuild it...
Let's call it a.exe
I run a.exe at the command line, while being in the folder on the shared drive and the executable that in fact was run was a "former version of itself" whil my buddy who made the exe on his machine was running the new one, is this because the OS on my machine cached it somehow and did not recognize that the file had changed? By rebooting my machine, I was able to have the "new" one run as I had hoped....
Is there any way to change this behavior (i.e. set OS to "always explicitly load exe file from disk regardless of its having been "changed").... This had us going for awhile.....thanks
Let's call it a.exe
I run a.exe at the command line, while being in the folder on the shared drive and the executable that in fact was run was a "former version of itself" whil my buddy who made the exe on his machine was running the new one, is this because the OS on my machine cached it somehow and did not recognize that the file had changed? By rebooting my machine, I was able to have the "new" one run as I had hoped....
Is there any way to change this behavior (i.e. set OS to "always explicitly load exe file from disk regardless of its having been "changed").... This had us going for awhile.....thanks
Zero AI Policy
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Interesting.
Suggestions only (I don't know if these will work or not).
Make a batch file that specifies path to the file and save this on the desktop and try that for accessing the file.
eg f:\work\a.exe
Or see the accepted solution in https://www.experts-exchange.com/questions/20677675/Quick-way-to-flush-RAM.html for freeing up memory (this might flush anything out of memory).
Suggestions only (I don't know if these will work or not).
Make a batch file that specifies path to the file and save this on the desktop and try that for accessing the file.
eg f:\work\a.exe
Or see the accepted solution in https://www.experts-exchange.com/questions/20677675/Quick-way-to-flush-RAM.html for freeing up memory (this might flush anything out of memory).
I read that thanks but it does not seem to apply to my "situation".....as far as I am concerned I am asking the OS to load an .exe file from a network drive as a windows executable and run it.....I cannot understand why it would do anything fancy like "cache" an older version of the exe file, even if it was built by another workstation on the network....it just seems fundamentally wrong somehow.....I certainly do not want an OS so smart that it runs an outdated version .....regardless of where it was built...thanks
I don't have a solution for your problem but I can explain what is happening. Windows does indeed cache files read from a network. This is a routine occurance that is done for performance reasons. All modern operating systems do this and have for a long time.
Files read from a local drive are also cached. When the file is changed the cache manager is notified and the cached copy is not used if the file is later requested. This feature is also supported for network files but for a variety of reasons it doesn't always work. When it doesn't the cache manager doesn't know the file has changed and you get the cached copy. The cache manager will eventually sync with the network source to correct the problem.
Files read from a local drive are also cached. When the file is changed the cache manager is notified and the cached copy is not used if the file is later requested. This feature is also supported for network files but for a variety of reasons it doesn't always work. When it doesn't the cache manager doesn't know the file has changed and you get the cached copy. The cache manager will eventually sync with the network source to correct the problem.
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
ASKER CERTIFIED SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
Wow.....I thought "we" had it, sent out a dept wide email and (cited EE as source) ....anyway....
So, are we left with the answer being " but for a variety of reasons it doesn't always work" ?
It seems this sort of thing would have had to been addressed (resolved previously) somehow.......
So, are we left with the answer being " but for a variety of reasons it doesn't always work" ?
It seems this sort of thing would have had to been addressed (resolved previously) somehow.......
I guess we never came up with an answer for this but figured I'd award points for the effort given...thanks
Microsoft Legacy OS
--
Questions
--
Followers
Top Experts
The Microsoft Legacy Operating System topic includes legacy versions of Microsoft operating systems prior to Windows 2000: All versions of MS-DOS and other versions developed for specific manufacturers and Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions, and Windows Mobile.