updated main README.md

Author: hvandermarel

README.md

@@ -48,12 +48,7 @@ are very old and only provided as-is in case there is still a use for them.
 
 You can install the full toolbox or select only a few scripts (with required modules) that you are interested in. 
 
-- scripts (with extension `.pl`) can be placed in a directory that is on your seach path (e.g. `~/bin`) or executed from the current working directory
-- modules (with extension `.pm`) should be installed in the same directory as your scripts or any other directory that is in the Perl search path (`@INC`) for packages
-
-If you don't like the `.pl` extension in the file name, please feel free to rename the script (removing the `.pl` extension). To use the `.pl` extension on scripts is my
-personal preference, but there are many that don't like this or type the `.pl` extension everytime they execute the script. My solution to this "problem" is to use a symbolic 
-link without extension. For the modules, never remove the `.pm` extension, Perl relies on this.
+To use the scripts you do not need to have any Perl knowledge, but you need to have Perl installed on your system. If you have Perl, the scripts will run from the command line like any other Linux, Mac or Windows command line or terminal application.
 
 ### Linux, Mac, other unix
 
@@ -65,6 +60,35 @@ Perl is not installed by default on Microsoft windows. To use the scripts you ha
 
 Another option is to use [Matlab](https://www.mathworks.com/products/matlab.html) if you have that already installed. Matlab comes with Perl on-board and you can use Perl from the Matlab command window.
 
+If you plan to use the Windows command prompt, please read on. 
+
+In the Windows command prompt (but *not* in a MSYS2/MinGW64 terminal or WSL) you have to run the scripts with a command like `perl script.pl .-options arg`. If you find this 
+inconvenient you can create a small (executable) batch file with the same name as the script but extension `.bat`, with the following content
+```
+@echo off 
+rem Wrapper around the rnxedit.pl script for the Windows command line. If perl is not 
+rem in your search path replace "perl" the full path to the perl executable. The 
+rem Perl script is expected in the same folder as this file, if not use the full 
+rem path name to the executable (without "%~dp0")
+
+perl %~dp0rnxedit.pl %*
+```
+You can then simply execute as `script`.  This is only necessary for the Windows command prompt, not under WSL or from a MSY2/MinGW64 terminal.
+
+### Hints and tips
+
+In order for the operating system to run the scripts it must first find them:
+
+- scripts (with extension `.pl`) should be placed in a directory that is on your seach path (e.g. `~/bin`) or run from the current working directory using the full path,
+- modules (with extension `.pm`) should be installed in the same directory as your scripts or any other directory that is in the Perl module search path (`@INC`).
+
+If you don't like to type the `.pl` extension everytime you run the script, please feel free to rename the script (removing the `.pl` extension). Using the `.pl` extension on scripts is my
+personal preference, but it is not necessary under Linux and there are many that don't like the use of this extension. My solution to this "problem" is to use a symbolic 
+link, without extension, to the actual script file with extension. 
+
+For modules this is completely different, never remove the `.pm` extension, Perl relies on this.
+
+
 ### Perl dependencies
 
 The main Perl dependencies are the modules `Getopt::Long`, `File::Basename` and `Time::Local`. These module are part of core Perl and included by most, if not all,