Brian,
Do we have to pay for this upgrade to version 3. We have version 2.0 currently installed and probably purchased it prior to 2001.
Any patch in sight for this bug..?
Thank you...
Brian,
Our operations manager states since this is a bug. We shouldn't be forced to pay for an upgrade to version 3., to fix the issue. Can you please reply so we can move on. This is a hassle to re-install Absolute Telnet every week for more than a dozen users.
Thanks for your help.
I get this issue, sometimes a few times a day. Having watched it for a while, I'm pretty sure that it only occurs when you get the 'checking for updates' dialog. Something that does corrupts something else that then causes AT to barf on the next load.
I've looked through the options and can't find anywhere to switch off update checks altogether. If someone can tell me how to do this then I would be very grateful as I'm 99% certain that would fix the problem of having to reinstall every day or so! I have v2.13 by the way, and apart from this problem am perfectly happy with it (apart from broken xmodem but I can live with that).
Phil
I'm not sure when the problem started for me, but November 2005 sounds right.
I'm using version 2.12. Interestingly, I just installed my original downloaded version on a new laptop, and it worked fine the first time I used the program. But the second time, the registry error occurred.
I run windows update, so I've installed various stuff from Microsoft recently. I probably was not running Absolute when it installed.
I'm running Win XP Professional version 2002 SP 2.
I tried to do the register-under-my-old-email-address fix, but it told me: "Someone else has already registered with that email address. Please try again. Use your back button."
I used your link to version 3.00 and edited it to version 2.12, downloaded a new copy, installed, unlocked with my license, and ran it several times successfully. This seems to be working for me.
My registration, by the way, was from New York (or Brooklyn), NY. My username is brw12.
Update on my efforts to get Absolute 2.12 working again --
Nope, didn't work. Just like others are reporting, after reinstall it worked fine -- for a little while. After that the registry error reoccurred.
Please, could a license for version 3.X be issued to all the people on this list who paid for 2.X but can't use it anymore?
-Ben Wheeler
My boss couldn't wait any longer and so recently purchased version 4.01. from another vendor, at same price. We'll see if that'll fix problem.
Another Vendor? Who?
Brian
Brian -
I am willing to pay $19.95 for an updated version (even though I don't need the updated features, just the non-bugginess), but what I worry is that if the same thing, or something else, happens with the program in another year, will I have to do the same again? I understand your reluctance to give away for free what you work hard for, but it would instill confidence in your product if you would provide a license upgrade to those of us experiencing the problem.
Thanks,
-Ben Wheeler
but what I worry is that if the same thing, or something else, happens with the program in another year, will I have to do the same again?
I guess my track record will have to speak for itself. I've been doing this for the last 10 years, and this is the first time a bug has surface like this in an older piece of software. I apologize about this, but I do my best.
My premise is that most bugs will surface rather quickly, which gives me time to get out fixes within the first year you own your license. This works in most cases, and is manageable for me. I can't reasonably maintain separate source code for every version of Absolute I ever release. Bug fixes are always made in the new version and we move on.
For example, the new beta is shaping up nicely here:
[url= http://www.celestialsoftware.net/telnet/beta_software.html ]http://www.celestialsoftware.net/telnet/beta_software.html[/url]
Some people will get this for free. Others will pay a modest upgrade fee. Is $19.95 really too much to ask? I put a lot of time and effort into this stuff.
Brian
Look, I don't mean to be rude here, but I'm a programmer as well, and this is the sort of thing that, while it falls squarely in a grey area, I would like to see my software vendor patch for me (or upgrade to a reasonable version - maybe not even the newest) for free.
This is not like the case I reported to you earlier, where (I suspect) the SSH library you are using is not playing nicely with SuSE's latest SSH daemon / SSL stack. That I would consider a "new bug".
This is more like a time bomb, and while I'm not for a minute insinuating that this was done deliberately, the net effect is that your program has ceased to be useful to registered customers.
I'm disappointed that this much time has elapsed with no action, but I hope you'll reconsider and fix this problem for your paying customers.
So, where are we regarding this problem? It sounds like a lot of paying customers have had this issue, and I think that we deserve an answer.
