Catch the output of PLINK.exe (PUTTY)

[admin]

I switched my system to Croatian but still can get no error.

Code: Select all

System Locale ID: 1050 (hr-HR)
Thread Locale ID: 1031 (de-DE)
Default ANSI Code Page: 1252  (ANSI - Lateinisch I)
Active ANSI Code Page: 1250  (ANSI - Osteuropa)
Default OEM code page: 850   (OEM - Multilingual Lateinisch I)
Active OEM Code Page: 852   (OEM - Lateinisch II)

What do I need to do to reproduce the issue?

[highend]

Maybe it's OS related?

01. Windows Server 2012 R2 U1 x64 German, English language pack installed (not active)
All regional settings are in German

Server 2012 R2 U1.png

02. Windows 7 SP1, x64 German, English language pack installed (not active)
All regional settings are in German

Windows 7.png

As you can see both settings are identical but:
on 01. the output of: text runret("cmd /c chcp", , 1);
is correct

while 02. shows nothing

It's definitely not the codepage alone. Which makes sense because PeterH uses 850 as well and it doesn't work for him, too.

[PeterH]

As I've written several times: my CP *is* 850, (I hope in general it's a) typical German installation. But I see the empty runcmd()!

Some more info:
System Locale ID: 1031 (de-DE)
Thread Locale ID: 1031 (de-DE)
Default ANSI Code Page: 1252 (ANSI - Lateinisch I)
Active ANSI Code Page: 1252 (ANSI - Lateinisch I)
Default OEM code page: 850 (OEM - Multilingual Lateinisch I)
Active OEM Code Page: 850 (OEM - Multilingual Lateinisch I)
Is DBCS Code Page: No

So, if I see it right, the problem is a bit more complex.
But no idea, what additional info I could supply
(To be sure: tested with fresh - no change.)

[admin]

As I've written several times: my CP *is* 850, (I hope in general it's a) typical German installation.

Sorry, I somehow overlooked that.

Well, out of ideas here as well. It's also weird that there is no error message.

[highend]

Addendum:

It doesn't work on Windows XP, Vista, Windows 7

It does work on Windows 8.1, 10

Windows 8(.0) not tested

All regional settings are the same for all operating systems...

It doesn't matter if it's a 32 or 64-bit OS. E.g. Windows 7 x86 + x64 -> Both don't work

---

On Win 10 x64 I switch all language dependent setting to english (united states) (formats, location, regional settings, ...) and change the on screen language to english as well (the systems have an english language pack installed).

Results in:

Win 10.png

Execute the runret() -> Works fine

It's not a codepage issue, it's an OS issue. PeterH is using Win 7 + XP, LittleBig Win 7. I'm Win 8.1 (Server version), Don Win 8.(0|1). Makes perfect sense...

[admin]

Cool, thanks!

But it does not help me. All APIs I'm using here (should) work fine under all those OSs.

In the meantime I had another idea. Let's see how the next beta does...

[highend]

Yeah, even an older version (v15.80.0200) doesn't work on Win 7 so you didn't cut off older OS support in the last 6 months

I've posted a few scripts that rely on runret. Wondering why I never got replies like "it's not working on my system"...

[admin]

Indeed, that's another mystery. ...shudder...

[highend]

v16.80.0012 - 2016-05-29 17:19
! SC runret: Issue on Windows XP, Vista, Windows 7. Fix attempt.

Doesn't make a difference on Win 7...

[admin]

Argh!

What if you place the script into a Custom Column (this changes one parameter for which I otherwise would have to upload a new beta to test)?

[highend]

With:

Code: Select all

return runret("cmd /c chcp", , 1);

?

Done, all cells empty (Browse trigger)

[admin]

OK, thanks.

So it remains a mystery.

[highend]

Porting the .ahk code to VB6 (http://www.autohotkey.com/board/topic/1 ... var/page-7) isn't an option? That one runs on Win 7 (x64 as well)...

[admin]

Porting the .ahk code to VB6 (http://www.autohotkey.com/board/topic/1 ... var/page-7) isn't an option? That one runs on Win 7 (x64 as well)...

Not bad, there is a call I did not use. I'll add it and we'll see what happens...

[highend]

013: Nope (neither as a single command, not in a CC with return)...