Yes, when I explicitly call ruby rather than rely on the file
association it works as I would expect. I don’t understand why the
exception is thrown when ruby isn’t explicitly invoked - as x1 mentioned
it got to Ruby. The file association step seems to mess everything up.
Windows never was very good with its command line - ho hum.
This now does what I’d like so I’m very happy. Chris, Robert, A LeDonne,
x1 and Pit Captain - Thanks!