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

OSD error

Discussion in 'Support' started by Joe Caverly, Nov 18, 2011.

  1. Joe Caverly

    Joined:
    Aug 28, 2009
    Messages:
    680
    Likes Received:
    8
    Hi,
    I am using;

    Code:
    TCC  13.01.31   Windows XP [Version 5.1.2600]
    TCC Build 31   Windows XP Build 2600  Service Pack 3
    Registered to me
    
    For the past month or so, I have been getting an un-reproducable error when using the OSD command.

    TC does not close down, nor does TCC.

    No TCMD.GPF file is created.

    I use the command thus;

    Code:
    osd /Font=36 /TIME=30 /HCENTER /BOTTOM 06012867-99 &
    
    This command is used in a .BTM file, and is detached so that processing can continue while the text is visible on the monitor.

    I have been using it since TC11, but have not experienced this problem until this version of TC.

    When the error occurs, a dialog box pops up on the screen, wanting to send a debug report. It contains the following;

    Code:
    Error signature
    
    AppName: tcc.exe   AppVer 13.0.1.31   ModName: tcc.exe
    ModVer: 13.0.1.31  Offset: 000067c4
    
    As I say, the occurrence is random, and usually works if I execute the batch file again.

    Joe
     
  2. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,859
    Likes Received:
    83
    batch

    Not reproducible here. The reason you don't see a TCMD.GPF is because it's
    crashing in the Microsoft startup code, before any of the TCC code is
    executed. Without a reproducible failcase or a stack trace it will probably
    be impossible to trace or fix it (or more likely to kludge around whatever
    MS bug it's triggering).

    But I don't understand your underlying intent here -- is there some reason
    you're detaching a process instead of just using the /N option?
     
  3. Joe Caverly

    Joined:
    Aug 28, 2009
    Messages:
    680
    Likes Received:
    8
    The reason I am detaching a process instead of just using the /N option is because I missed this in the command line help, that is;

    Code:
    osd /?
    
    On Screen Display.
    
    OSD [/C /FONT=n /N /POS=n,n /RGB=r,g,b /TIME=n /TOP /LEFT /BOTTOM /RIGHT /HCENTER /VCENTER /V] text
        /C(lose)        /RGB (text color)
        /FONT (font height)    /TIME (display time)
        /POS (top left)        /V(ertical)
    
    As the /N option is not documented in the same amount of detail as when I use

    Code:
    help osd
    which shows

    Code:
    /N Don't wait for timeout before returning to the prompt 
    I completely missed it. I have modified my batch file so that the OSD command uses /N, and not one failure yet after three successful runs. Many thanks for pointing this out.

    Joe
     
  4. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,859
    Likes Received:
    83
    The quick help has never had (and will never have) all the options in all
    the commands. The only guaranteed, authoritative help is the html help.
     
  5. Joe Caverly

    Joined:
    Aug 28, 2009
    Messages:
    680
    Likes Received:
    8
    Understood. I've become too used to using the cli and man pages in Ubuntu. Using

    Code:
    alias man=help
    might make things more gui for me.

    Joe
     

Share This Page