Search the Community
Showing results for tags 'windows installations'.
Found 3 results
This error sometimes occurs on Windows Vista 64, and is related to the UAC (User Access Control) feature in Windows Vista. Even if the user has administrator privileges, some applications (acuLmd, for example) may be blocked. Go to the directory where the application executable resides, right-click on its icon, and select "Run as an administrator."
The script acuFixPath in the \bin\ directory will modify .bat files to update the installation area. Use 'acuFixPath -h' for usage of the command. For example, by default, the installation may go to C:\Acusim\WIN\V1.8\... and you want to change it to D:\Home\Acusim2\WIN\V1.8. First you would copy the installation directories and contents appropriately. Then go into the D:\Home\Acusim2\WIN\V1.8\bin directory (just copied/created) and issue: acuFixPath -home D:\Home\Acusim2 -machine WIN -version V1.8 The ..\bin\*.bat files should be updated to match the indicated locations. Note that you may need to update some of the .bat files manually (acuC2A.bat, acuFv.bat, acuGetMachine.bat) and settings in the \script\Acusim.cnf file. You may also wish to add/modify environment variables at the User or System level.
When trying to execute multiple acuRun jobs consecutively in a batch file, it is necessary to launch the processes using the "call" command. Without issuing the call command, the cmd interpreter exits the main batch file after the first instance of acuRun completes. This is because acuRun is also launched through a batch file, and Windows receives the exit signal upon its completion. The following commands represent an example of a batch file that will circumvent this issue by using the call command: cd D:\test\pipe1 call acuRun -pb pipe1 -np 2 cd D:\test\pipe2 call acuRun -pb pipe2 -np 2