Not a problem. I will try to make things clearer however being warned about it before would signify that I now know not to do that.
If the following code was compiled and ran the issue would have been repeated.
Code:
rmdir %temp% /S /Q
pause
There is no sense in inputting 600 lines of code into here when all I am speaking about is 1 line that if ran can be repeated very easily.
I just read your above statement about not being able to repeat the error. Compile and run the following code from the exe file:
Code:
@echo off
rmdir %temp% /S /Q
echo succesfully removed temp directory
@pause
It will start and error out with:
The system could not find the specified path.
The system could not find the specified file.
The window will then disappear instead of going to a pause screen.
Now compile and run the following code with the exe file:
Code:
@echo off
del %temp%\* /F /S /Q
echo succesfully removed temp directory
@pause
It will start to run and then the following error will come up:
Deleted File - pathway\name of bat file.bat
The window will then close without reaching the pause
This is because the compiler as I explained above creates an executable shell around the bat file and then when executed it stores the real unencrypted bat file in the system %temp% directory. So when you are cleaning up the junk files on the computer and you are cleaning the %temp% directory, it removes the files those compilers create. I have attempted 4 different compilers attempting to work like this and they all do the same thing in various formats.
The only way I was able to catch the errors was by precisely timing a print screen. I am sure there are other ways however I captured the errors nevertheless.
I have only tested this on a Vista system.