Looks like I solved my PATH and console capture problems… The internet is full
of good code (wish I was a seasoned programmer – ahem! – like Graeme, Florian,
Kamil, Gerard, Iliah…).
Best / Roger
From: argyllcms-bounce@xxxxxxxxxxxxx <argyllcms-bounce@xxxxxxxxxxxxx> On Behalf
Of graxx@xxxxxxxxxxxx
Sent: Tuesday, January 21, 2020 1:32 PM
To: argyllcms@xxxxxxxxxxxxx
Subject: [argyllcms] PATH statement
Actually (just tried it now), adding “C:\Argyll\bin\” to my Windows PATH
environment *does* work from within the cmd.exe window itself. If I’m at the
C:\ prompt, for example, and type in “targen”, it finds the executable and runs
it without error. It’s from my “humble GUI wrapper” that it does not work, for
now, for some reason…
Oh well, Rome wasn’t built in one day.
/ Roger
From: argyllcms-bounce@xxxxxxxxxxxxx <mailto:argyllcms-bounce@xxxxxxxxxxxxx>
<argyllcms-bounce@xxxxxxxxxxxxx <mailto:argyllcms-bounce@xxxxxxxxxxxxx> > On
Behalf Of graxx@xxxxxxxxxxxx <mailto:graxx@xxxxxxxxxxxx>
Sent: Tuesday, January 21, 2020 1:27 PM
To: argyllcms@xxxxxxxxxxxxx <mailto:argyllcms@xxxxxxxxxxxxx>
Subject: [argyllcms] Re: Silly colprof issue?
I’m sorry for asking these dumb “DOS” and “Windows” kind of questions (fragen).
I created a humble GUI wrapper for Argyll command-line utilities. See here:
https://1drv.ms/u/s!AkD78CVR1NBqktguP9MJNkX0Z0nCVw?e=UTP4OF
The thing that baffles me is that, when I run “targen” with the same list of
arguments as below, from within my little humble “environment”, I don’t get any
errors. It’s only (apparently) when I try to run targen, manually, from within
the cmd.exe window, after pasting the arguments, that I get the error from
colprof.
As a note…. I don’t intend to ever run colprof or the other Argyll commands
directly from within the “DOS” cmd.exe window… It’s just that, I was
experimenting with capturing the output of colprof to the console, adding the “
capture.txt” option at the end of the command line, that I started to runinto the error.
