1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Non-conforming @Script

Discussion in 'Support' started by Joe Caverly, Nov 19, 2016.

  1. Joe Caverly

    Joined:
    Aug 28, 2009
    Messages:
    680
    Likes Received:
    8
    I am using;
    Code:
    TCC  20.00.25 x64   Windows 7 [Version 6.1.7601]
    TCC Build 25   Windows 7 Build 7601  Service Pack 1
    This is a new installation, on a new system.

    I cannot get the @Script function to work for me. As an example;
    Code:
    echo %@script[vbscript,dim objShell:set objShell=CreateObject("shell.application"):objShell.FileRun:set objShell=nothing]
    does not result in anything, that is, the code does not execute.

    It works fine when run as;
    Code:
    cscript //nologo filerun.vbs
    where the contents of filerun.vbs are;
    Code:
    dim objShell:set objShell=CreateObject("shell.application"):objShell.FileRun:set objShell=nothing
    Again, this is just an example.

    None of my other @Script code works anymore.

    On my previous Vista system, all of my @Script code worked.

    Am I missing something simple?

    Joe
     
  2. Joe Caverly

    Joined:
    Aug 28, 2009
    Messages:
    680
    Likes Received:
    8
    I have installed TCMD20 on another Windows 7 (64-bit) system, and have duplicated the @Script problem.

    Can others please verify that @Script does not work properly on their Win7 (64-bit) TCMD20?

    Joe
     
  3. MaartenG

    Joined:
    Aug 3, 2016
    Messages:
    355
    Likes Received:
    8
    Confirmed. Not working on Win7 x64 and Win10 x64
    Output: "0"; errorlevel "0". That's all.

    EDIT: Even with a bogus command like: echo %@script[vbscript,qwewqeweqwq]
     
    #3 MaartenG, Nov 24, 2016
    Last edited: Nov 24, 2016
  4. Joe Caverly

    Joined:
    Aug 28, 2009
    Messages:
    680
    Likes Received:
    8
    Win7 64-bit has two cscript.exe;
    Code:
    C:\Windows\System32\cscript.exe
    C:\Windows\SysWOW64\cscript.exe
    Maybe @Script is using the incorrect VBScript engine for 64-bit OS.

    I know that @Script worked fine on my Vista 32-bit OS.

    Joe
     
  5. MaartenG

    Joined:
    Aug 3, 2016
    Messages:
    355
    Likes Received:
    8
    My thoughts exactly :-)
    That is why I also tested with 32-bit Take Command on 64-bit Windows.
    This will call the SysWOW64 version of vbscriupt.dll. Same results.
     
  6. vefatica

    Joined:
    May 20, 2008
    Messages:
    7,971
    Likes Received:
    30
    I think it's just broken. Joe, your original example,
    Code:
    echo %@script[vbscript,dim objShell:set objShell=CreateObject("shell.application"):objShell.FileRun:set objShell=nothing]
    does not work in Win7/32 with TCC v20. It does work with TCC versions 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 9, and with 4NT v8.
     
  7. Joe Caverly

    Joined:
    Aug 28, 2009
    Messages:
    680
    Likes Received:
    8
    Vince,
    I must have been using a version lower than TCC v20 on my Visita 32-bit, although I know I did have TCC v20 installed.

    I just tested with the TCC RT, and got the same fail;
    Code:
    c:\utils>tccrt filerun.btm
    
    TCC RT  20.00.25 x64   Windows 7 [Version 6.1.7601]
    Copyright 2016 JP Software Inc.  All Rights Reserved
    echo 0
    0
    I will patiently wait for Rex to make repairs to @Script.

    Joe
     

Share This Page