Hi Kai,
I have replaced the script in the original thread with an updated version that works on all platforms. The problem was the white space in "C:/Program Files" on Windows. This is now fixed by simply enclosing the executable name between double quotes. Thank you for detecting this problem.
The printer is now disabled on Windows and Mac OS X since build 1098 of the PixInsight Core application. Quoted from the
official release announcement:
The printing subsystem is now optional on all platforms. The global Printer object can be disabled with a new --no-printer argument to the PixInsight Core application. The printer is enabled by default on FreeBSD and Linux, and disabled by default on Windows and Mac OS X. This is a temporary situation while we design and implement a new printing system better adapted to all supported platforms. This should fix a long standing problem with network printers that we have not fixed yet; see for example: http://pixinsight.com/forum/index.php?topic=6994.0What that post does not explain well is that the printer
cannot be enabled on Windows and Mac OS X (there is no --no-no-printer or similar argument). Actually, this makes sense because the printing system is poorly implemented on these platforms, and in PixInsight we prefer not having something instead of having a mediocre implementation. This will be fixed in a future version.
