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

take command 19 not doing well under windows 10 build 14295

Discussion in 'Support' started by covici, Apr 3, 2016.

  1. covici

    Joined:
    Jun 25, 2008
    Messages:
    15
    Likes Received:
    0
    Hi. I just updated windows to take command 14295 and I am not getting the cursor in the correct place under take command v19. I am using a screen reader and this may have something to do with it, but I was wondering if there are any strange things going on with console apps under this build?

    Any suggestions would be appreciated.
     
  2. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,812
    Likes Received:
    82
    I've been running 14295 for a couple of days and haven't had any issues (but I'm not using a screen reader).

    Anybody else having problems with 14295?
     
  3. Rod Savard

    Joined:
    May 26, 2008
    Messages:
    481
    Likes Received:
    3
    I didn't have any problems under 14295.

    Just updated to 14316 and it seems ok as well. I installed the Linux subsystem and tried running bash inside TCMD. Seems to work sort of, but the default prompt must have ascii escape codes that cause TCMD to "ding" every time it's displayed.
     
  4. Ruud Uphoff

    Joined:
    May 22, 2013
    Messages:
    21
    Likes Received:
    0
    YES There is a problem in Windows 10 14279 and later. Even in 14316. At start of a TCC window, I display a header like this:
    sample.jpg
    Under build 14279 and later, the border is not displayed. (replaced by blanks) In addition e.g. [ALT] [2][4][0] should produce ≡ but under builds 14279 and later, it is unpredictable what it will do. This is not a problem caused by TCC, but must be a bug in Windows.
     

Share This Page