Hello, everyone.
There is a cache (storage) on Windows files (bat) memory that were executed?
Thank you.
Cache - *.BAT
Moderator: DosItHelp
Re: Cache - *.BAT
Could you explain your problem with a little more detail or give an example of what you are referring to.
-
alexandredneto
- Posts: 39
- Joined: 28 Feb 2013 13:40
Re: Cache - *.BAT
This occurred a few times.
And it's kind of confusing.
When I make a functional version of the code (no errors) in c:\Programs\A.
And develop another version of the code.
I suddenly realize that the development is not going well, there are errors.
And go back to develop the previous version (which worked). Surprisingly, sometimes the execution shows the same flaws. It makes me think that there is a cache of the code that is allocated to the operating system.
Strange, because the file names are different.
Has anyone experienced this. Sometimes when I change directory failures of previous version of code stop occurs.
This occurred in about 5 servers.
And it's kind of confusing.
When I make a functional version of the code (no errors) in c:\Programs\A.
And develop another version of the code.
I suddenly realize that the development is not going well, there are errors.
And go back to develop the previous version (which worked). Surprisingly, sometimes the execution shows the same flaws. It makes me think that there is a cache of the code that is allocated to the operating system.
Strange, because the file names are different.
Has anyone experienced this. Sometimes when I change directory failures of previous version of code stop occurs.
This occurred in about 5 servers.
Re: Cache - *.BAT
99 times out of 100 when something unexpected happens you will find that there is a flaw in the code.
Your description is vague and without code it's pretty hard to help you.
From the MSDOS days up until the present: when you launch a batch file the OS opens the batch file and reads a line, closes the file and executes the line, reopens the file and from the saved pointer it will read the next line and execute that, and repeat. It may read more code if there is a block in parentheses - and the guys here will chime in to give you better details.
There is a disk cache in Windows but you can prove the above behaviour by editing a running batch file that is in a classic loop, and you will get errors or unexpected behaviour. It's not running from the cache.
Your description is vague and without code it's pretty hard to help you.
From the MSDOS days up until the present: when you launch a batch file the OS opens the batch file and reads a line, closes the file and executes the line, reopens the file and from the saved pointer it will read the next line and execute that, and repeat. It may read more code if there is a block in parentheses - and the guys here will chime in to give you better details.
There is a disk cache in Windows but you can prove the above behaviour by editing a running batch file that is in a classic loop, and you will get errors or unexpected behaviour. It's not running from the cache.
Re: Cache - *.BAT
If I had a dime for every time I had a batch file in two different directories and was editing one and running the other I would be a rich man.