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

Take Command v12 beta 12.0.29 uploaded

Discussion in 'Support' started by rconn, Oct 17, 2010.

  1. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,730
    Likes Received:
    80
    I've uploaded build 29 of the beta to the web and ftp sites.

    No new features; a few internal (unreported) bug fixes, updated help, and a reset of the trial period to an additional 45 days.

    We hope to have the final release ready in the next few days.
     
  2. Steve Fabian

    Joined:
    May 20, 2008
    Messages:
    3,523
    Likes Received:
    4
    rconn wrote:

    | I've uploaded build 29 of the beta to the web and ftp sites.

    I tried to download from the ftp site. It reported all files were build
    28, dated Oct. 2nd. How can I force not using the cached earlier build? I
    use TCC's COPY command to download.
    --
    Steve
     
  3. Howard Goldstein

    Joined:
    Jun 1, 2008
    Messages:
    111
    Likes Received:
    1
    The first time I ran TCC after installing build 29 it worked fine, telling
    me that I had a 45-day trial period. All subsequent attempts to start it
    have resulted in the "trial expired" message. My registered copy of TCC
    11.0 is still working properly. How can I get 12.0 working again?

    --
    Howard
     
  4. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,730
    Likes Received:
    80
    me that I

    resulted in

    Depends on your Windows version, and whether you're running the 32-bit or
    64-bit version of TCC.

    Are you invoking TCC from a shortcut you created?
     
  5. Howard Goldstein

    Joined:
    Jun 1, 2008
    Messages:
    111
    Likes Received:
    1
    Rex Conn wrote:


    Sorry. It's the 32-bit version under XP. I am invoking TCC from a shortcut
    that I created. However, invoking TCC12 from a TCC11 prompt fails the same
    way. The invocation is simply the program path, no switches.

    --
    Howard
     
  6. Googer

    Joined:
    Aug 23, 2010
    Messages:
    2
    Likes Received:
    0
    I'm having the same problem as Howard - upon trying to start TC I'm getting the message that my trial has expired. This is from any shortcut or by invoking tcmd.exe directly. Also the same as Howard, this is 32-bit on XP.
     
  7. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,730
    Likes Received:
    80
    getting

    XP.

    Make sure you don't have an old "takecommand12.key" file hanging around.
     
  8. Googer

    Joined:
    Aug 23, 2010
    Messages:
    2
    Likes Received:
    0
    I've tried that as well as deleting the key and name registry keys under HKCU\Software\JP Software\Take Command 12, and upon starting Take Command, I initially get a message about 45 days remaining in the beta version, but then after that when the actual Take Command window comes up, I get the message about the Take Command trial being expired and the registry key (as well as takecommand12.key file) are back with the same values as what I'd just deleted...
     
  9. drrob1

    drrob1 Guest

    Seems to me this is a no win situation on WinXP sp2 32 bit

    I cannot start v12 beta to have it update itself.

    I cannot run the updater.exe by itself as I am getting a parameter error.

    I cannot d/l the new one since I donn't remember where it is on your server.

    You don't seriously expect me to edit my registry now, do you? Who's
    problem is it if I screw up my registry?

    There needs to be a better way.

    Perhaps the betas needed more time before they expired in the first
    place and created this problem.



    On 10/18/2010 11:49 AM, rconn wrote:

     
  10. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,730
    Likes Received:
    80
    Uninstall the 12.0 beta, and download it from ftp://jpsoft.com/beta/tcmd.exe
    (or tcmdx64.exe) & install again.

    Or just wait a few days until the final release.
     
  11. drrob1

    drrob1 Guest

    No Go.

    Uninstalled the 12.0 beta and d/l'd the new version. I could not start
    v-11 as it said I needed to register-exit whatever. Didn't realize that
    v-12 could spill over into v-11 registrations.

    I had to resort to good ol' cmd.exe to start tcmd.exe v12. Now it says
    register-exit whatever and won't start.

    But v-11 works again.

    I can wait a few days.

    I anticipated these registration related problems so I've been testing
    in a virtual WinXP. I don't typically test beta software in a
    production environment. Not work the risk of breaking something.



    On 10/18/2010 05:36 PM, rconn wrote:

     
  12. Howard Goldstein

    Joined:
    Jun 1, 2008
    Messages:
    111
    Likes Received:
    1
    Googler wrote:

    Essentially the same here, except that I'm starting stanalone TCC rather
    than TCMD. TCC will start fine when the registry values and
    takecommand12.key have been deleted, but once the values and file have been
    recreated TCC gives the "expired" message and will not start.

    --
    Howard
     
  13. oldjet

    Joined:
    Oct 1, 2010
    Messages:
    7
    Likes Received:
    0
    Hi Rex,

    Does that mean that v12 will be available for sale in the next few days? I was about to place an order for TC/LE (my 30-days trial is almost over), but now that v12 sounds around the corner perhaps I'd better wait a little; Unless of course purchases now would be licensed for v12 as well?

    Thanks for your feedback.

    Jet
     
  14. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,730
    Likes Received:
    80
    was

    now

    of

    Any orders within 60 days of a new release automatically get the upgrade
    free.

    Rex Conn
    JP Software
     
  15. drrob1

    drrob1 Guest

    My one year of upgrades expired 10/18 (I think). Does that qualify for
    the v 12 upgrade?




    On 10/18/2010 09:52 PM, rconn wrote:

     

Share This Page