Re: Catch the output of PLINK.exe (PUTTY)
Posted: 29 May 2016 19:56
IN the next version I will add step by step debugging... 
XYplorer Beta Club
Forum for XYplorer Users and Developers
https://www.xyplorer.com/xyfc/
Catch the output of PLINK.exe (PUTTY)
Page 5 of 6
Re: Catch the output of PLINK.exe (PUTTY)
Posted: 29 May 2016 20:15
Re: Catch the output of PLINK.exe (PUTTY)
Posted: 29 May 2016 21:34
v16.80.0014: Pass 2 as flags in runret, and you see some debug info.
Code: Select all
text runret("cmd /c chcp", , 2);Re: Catch the output of PLINK.exe (PUTTY)
Posted: 29 May 2016 21:37
That's the output:
Re: Catch the output of PLINK.exe (PUTTY)
Posted: 30 May 2016 09:11
OK, next beta tries a new idea...
Re: Catch the output of PLINK.exe (PUTTY)
Posted: 30 May 2016 11:56
Well, I could not do much. Just the debug notes might be more telling... 
Re: Catch the output of PLINK.exe (PUTTY)
Posted: 30 May 2016 12:10
Let's see what happens with the next beta...
Re: Catch the output of PLINK.exe (PUTTY)
Posted: 30 May 2016 14:41
The posted .ahk code btw works on all systems, from XP up to Win 10, regardless if it is a 32 or 64-bit OS and which codepage is used
v0015:
v0015:
Re: Catch the output of PLINK.exe (PUTTY)
Posted: 30 May 2016 15:00
You mean this? http://www.xyplorer.com/xyfc/viewtopic. ... 73#p138973
Re: Catch the output of PLINK.exe (PUTTY)
Posted: 30 May 2016 15:10
YepYou mean this? viewtopic.php?p=138973#p138973
Re: Catch the output of PLINK.exe (PUTTY)
Posted: 30 May 2016 18:43
v0016: Exactly the same (output + screenshot) as in v0015. Sorry...
Re: Catch the output of PLINK.exe (PUTTY)
Posted: 30 May 2016 19:10
Too bad. Gotta stop here. So, SC runret is Win8 and later only from now on.
Re: Catch the output of PLINK.exe (PUTTY)
Posted: 30 May 2016 19:15
Re: Catch the output of PLINK.exe (PUTTY)
Posted: 30 May 2016 19:17
Re: Catch the output of PLINK.exe (PUTTY)
Posted: 30 May 2016 22:23
While I understand that this must be frustrating, cutting off the support for systems older than Win 8 can't be the final solution. In that case the command gets unusable (apart for your own personal scripts) because I don't think that 99% of the userbase migrated to Win 8 +