All Things WinBatch > WinBatch

Compiler setting changes ignored


I have a script that was written and updated many times. The last time was 3 years ago on a Win7 device.
I now have a Win10 device and have to update the script.
I am changing some settings in the compiler -- from Small EXE to Large EXE as well as the target.
When I click OK to initiate the compile, it runs to completion with no error, but the compiler option changes seem to be ignored.
The EXE is created in the location previously specified and it is a Small EXE rather than "Large" as specified.

I have tried creating new folders - no difference.
I tried creating the Large EXE in the current location - no difference.

I don't know what could be causing this or what to try next...

The compiler must be able to read and write to the ".cmp" file associated with the source being compiled in order to use the settings you specify in with the Compiler's UI.   If it can't, it will use the current settings in the www-prod.ini file that is located in your user AppData/Roaming/WinBatch/settings directory.  The ".cmp" file must be in the same directory as the source because the compiler uses the source path and name root for the ".cmp" compiler options file.

So the most likely cause of your problem is that the compiler cannot write to the ".cmp" file because of permission issues of some kind.  However, you have not provided enough information to say what the permission issues might be.   One test might be to create a script that creates and then reads from an ".ini" file in your source directory using the WinBatch "ini" functions.  You must make sure that you are executing the script with least privilege as that is how the compiler executes.  To do that you should run the script by supplying it as a command line parameter to the WinBatch_IF.exe version of WinBatch.  If the write/read does not work, you have the answer to your problem.

With the Win10 migration came some changes to access.
The process did modify the perms on some files/folders including the one you named.
Updating the perms did resolve the issue.

Thanks for the quick and effective response.


[0] Message Index

Go to full version