in my experience,
you should remove the //u option (for unicode) on windows 10 or 2012r2.
cscript doesn't seem to return a value to stdOut and stdErr if you do.
- solution
#1 don't use //u, use ANSI
or
#2 use //u, but wrap the entire script with an "on error"
On Error Resume Next
{whatever}
Wscript.StdErr.Write Err.Description
On Error GoTo 0
> 2016/09/07 19:37、Douglas Cryer <[email protected]> のメール：
>
> How do I alter : $vt_Command:="CScript //nologo //U \""+ +Document+"\""
> To force it to run the 32bit CScript?
宮古 啓介
セールス・エンジニア
株式会社フォーディー・ジャパン
〒150-0043
東京都渋谷区道玄坂1-10-2 渋谷THビル6F
Tel: 03-6427-8441
Fax: 03-6427-8449
[email protected]
www.4D.com/JP
**********************************************************************
4D Internet Users Group (4D iNUG)
FAQ: http://lists.4d.com/faqnug.html
Archive: http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:[email protected]
**********************************************************************
