I'm trying to put version 3.11 (or the latest) onto a new computer.
I've used the software for ages on the old one.
I have Windows XP Pro with SP 2 and all the updates installed. I also have Avast anti-virus installed.
When I click on the Absolute.exe to install I get an initial box asking me if it's ok to install it. When I click yes, a new window flashes up for an instant but then vanishes and nothing else happens.
This happens with both 3.11 and 3.13 and when I pause Avast and disable window's firewall.
Help- I need to install quickly!
Thanks.
[size=1][ October 19, 2004, 08:24 AM: Message edited by: Brian T. Pence ][/size]
Any chance of a reply?
Stuart, there's a bug in the installer (InstallShield) that can cause something like this. The solution has always been to reboot and install the software first before you run other stuff.
Let me know if this helps.
Brian
It doesn't Brian, I'm afraid.
I even went into the task manager and closed every application I could.
So I have Windows XP Pro with SP2 installed and I can't get the latest version of Absolute Telnet to install.
I would very much appreciate some help because the only reason my old computer is still up and running is because I need it to Telnet.
Stuart,
Closing the other apps isn't good enough. There's some resource that InstallShield needs that can only be freed by a reboot. I've never been able to pinpoint precisely what InstallShield's problem is, but a reboot should always work.
Brian
Tried that Brian with no difference.
I think the only way this is going to work is if you can rebuild the app using a new (working) version of Installshield. Or something better.
Is that possible?
Brian I appreciate it's not your responsibility to fix problems on other people's computers.
But this is a brand new top-specification PC with a fresh install of XP SP2 and about 30 other applications without any problems.
I really think this is an issue with the installation software you are using.
I even booted into safe mode and tried installing and it made no difference.
[size=1][ October 25, 2004, 04:19 AM: Message edited by: Stuart Wright ][/size]
Stuart, I KNOW for a fact it is an installshield problem. Switching to another installer *is* the solution, but not one to be taken lightly. Meanwhile, I'll try to do some more research on this. If you could, please try the new beta.
I'm not sure if it'll be more successful for you, but it's worth a try.
Brian
Hi Brian, you sound upset.
Sorry if my post upset you. I was just trying to clarify the situation for you.
Having 20 years experience programming computers and having experienced Install Shield once, I know that doing a new exe build is a timely and potentially expensive exercise.
Stuart,
I've found a bunch or references to this issue, but no solution. Some references refer to a problem with Outlook, so make sure that you're not running Outlook (or any MS apps such as Office, Office quicklaunch bar, media player, etc)
All of the theories on this problem point to *SOME* other product not allowing the 16bit installer to run. The real problem is that it's probably not only just one culprit in all cases, so it's hard to point to a solution that always works.
Perhaps I can write a small test app that will try to identify the offending application so you could terminate it.
I'll be looking into this more...
Stuart,
I've found one possible solution (finally). There might be a way to rig the install to bypass the 16bit portion.
The 16bit installer stub is a throwback to the Win31 days. Its purpose is to detect the OS version, then run the appropriate install depending on whether you're running on 16bit or 32bit windows. This 16bit stub is where I suspect the hang to occur. It's really an unnecessary step and there may be a way to call the 32bit installer directly, but I'll have to do some testing before I make this change.
One drawback of the proposed solution is that the install would have to be run from a place where you have write permission. While generally not a problem if you've downloaded from the internet, this could cause a problem if you burn the installer to CD, for example. The issue is that with the proposed soultion, the installer will try to unpack itself into a subdirectory in the same directory where it is run. If run from CD, this is not possible and the install will fail.
While not a permanent solution, this may at least get you past your particular problem quickly. I'll let you know when I have something to test.
Brian that would very much be appreciated.
Only today my server started slowing down and I would normally use Telnet to log in and restart Apache.
I had to email the support staff and ask them to do it.
Many thanks.
That worked just fine, thanks, Brian.
I have emailed you asking for a new unlock email as I can't find the previous one.
Many thanks.
FYI I am having the same problem with the the newest release of Absolute Telnet,
My notebook crashed on Sunday and I've had to completely reinstall all of my software. I am running WinXP SP2 and am getting this error when I try to install Absolute Telnet.
*******************************************
16 bit MS-DOS Subsystem : Command Prompt - edit autoexec.nt
C:\\WINDOWS\\SYSTEM32\\AUTOEXEC.NT. The system file is not suitable for running MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the application.
*******************************************
the release canidate that you posted in this post did install But it is out of date and I cant use it. I have my License file handy
any way to help.
Thanks
