There are several common errors that can occur due to the differences in the underlying systems. Here are a few examples:
1. Line Endings: Linux and Windows use different line-ending characters in text files. Linux uses the newline character (LF), while Windows uses a combination of carriage return and newline characters (CRLF). If you edit a Linux script or file in Windows without converting the line endings, it can lead to syntax errors or unexpected behavior when running the script in a Linux environment.
2. Shell Differences: Linux uses various shells like Bash, Zsh, or Csh, whereas Windows uses the Command Prompt or PowerShell. These shells have different syntax, built-in commands, and environment variables. Scripts written for one shell might not work or produce errors when executed in a different shell.
Consider the platform differences and make necessary adjustments or use tools that enable Linux compatibility on Windows, such as Windows Subsystem for Linux (WSL) or virtual machines.
Wait... the screenshots you provided - first one is .sh script which you start, and the second one results? I see no "connection" to slurm_script that is reported to have issues with line 23 and 24.
Could you provide text/source of the scripts that would allow us to check any links and starting other scripts? Also, I can see some progress.log file should be created too, is that available?
You just took the scripts from Linux and started in Windows or have you made any changes and debuging? Have you tried to execute in Linux (you can quite simply install virtual instance of Linux using VirtualBox or any other hypervisor software under WIndows...)