WinBAtch and Win7

Started by cfann, February 08, 2017, 08:36:26 AM

Previous topic - Next topic

cfann

I just installed WinBatch on Windows7.  Everything seemed the same as on XP until I tried to compile a second time.  The first time was fine, but get this on second try....

Compiler Error - Unable to create(then it gives the path).  The file may be in use, or marked read only or the specified output directory may not exist.

NONE of these are true.  I'm compiling the same as I did on XP.

I can create a new directory to save it in and it works...but I CAN NOT do that each time I need to recompile!

Please help!

td

Please indicate the version of WinBatch+Compiler you are using and the UAC settings on your Windows 7 machine.  Also does the error message show the file name of the exe or the .cmp file?
"No one who sees a peregrine falcon fly can ever forget the beauty and thrill of that flight."
  - Dr. Tom Cade

cfann

WinBatch 2004F and WBC 2004F dll(5.4fed)

It displays the .exe

Thanks!

cfann


td

It could be some kind of permission issue related to UAC and  folder or file security, or it could have something to do with any anti malware software taht might be on the system. 

I suppose you could try temporarily turning off  UAC to see if that fixes the problem.  That would at least give you some idea of the cause and suggest some possible workarounds.  You may also want to check the file (both .exe and .cmp) and folder permissions to make sure you have Read, Write, and Modify access.

So much has changed in both Windows and WinBatch in the last 12+ years that any suggestions are little more than somewhat educated guesses.       
"No one who sees a peregrine falcon fly can ever forget the beauty and thrill of that flight."
  - Dr. Tom Cade

td

There was a fix to the WB 2013C version of the compiler that addressed an issue involving the writing of version information to the exe on some Windows 7 systems.  I don't recall if that problem produce the error you are receiving or some other error message.
"No one who sees a peregrine falcon fly can ever forget the beauty and thrill of that flight."
  - Dr. Tom Cade

td

The WB 2013C fix was actually a Window 7 bug but the compiler did not produce an error message as a result of the bug.  It just didn't write version information to the compiled executable.  So that can't be the cause of your problem.
"No one who sees a peregrine falcon fly can ever forget the beauty and thrill of that flight."
  - Dr. Tom Cade