Wednesday, August 30, 2006
I am having a problem with older machines that still have some remnants of SmarTerm 7.0 on them. When I run your install program it changes the smarterm program to version 7.0 and then we get an stoffice.exe error. We are running version 12.1.1 but there is still a “Persoft” directory on the C: drive and there must be some ini files or registry entries that are re-pointing smarterm to version 7.0, which then errors. We have uninstalled and reloaded several times (that is the only way to get smarterm working again) and have verified that we are installing to all the right folders but there is still a problem somewhere. Aside from re-formatting the hard drive, are there any ideas you have? We don’t have an uninstall program to run on version 7.0.
You might try logging on as an adminstrator, then go into regedit and delete all the smarterm entries from the HKEY_CLASSES_ROOT branch:
If you can uninstall smarterm 7.0 that would be good. If the uninstaller is missing you could install 7 over the old one again and then uninstall.
Then make sure to delete the smarterm 7 folder from the program files folder.
After leaving nothing but scorched earth where 7 once was, you can install the 12.
The problem is that previous versions of smarterm would automatically ‘repair’ any broken components as soon as the program runs. This would result in the behaviour you described.
To un-repair 7’s modifications you can go to add remove programs and attempt to repair the 12.0 installation. But if the 7 executable is still sitting around anywhere and gets run, it will break 12 again. Back when I had to ensure compatibility between 7 and 9 and above, I would repeatedly go through this process while testing the different versions.
7 and 12 will never play nice and you have to eradicate 7 from your system manually if the uninstaller fails to do so.
Thursday, June 29, 2006
I’m trying to install the demo software for our lab manager and I ran into a problem. After selecting the SmarTerm version, I can go no further because the “next” button is grayed-out. (See attached screen shot.) Any ideas on how to complete the install?
I tried to duplicate the problem but was not able to. Is it possible that there is not enough space on the drive you are installing to? Are you logged on as an administrator or as a user with install rights on the computer? I have re-compiled the setup program, try downloading it and installing again.
I see why it doesn’t work. It’s because SmarTerm is accessed on a network share, rather than the local drive. The SmarTerm executable location field currently looks like this: \serversoftwarelabsmarterm . When I put a drive letter in front of it, like “C:serversoftwarelabesmarterm” the “Next” button appears. Since our network share isn’t associated with a drive letter, however, the “Next” button will remain grayed-out. I was able to map a drive to the network share to complete the install, but I don’t know if we’ll want to do this for a system-wide implementation.
Sent: Wednesday, March 15, 2006
Okay, I’ve installed on new machine and can’t run OLM because I can’t get to WrkgvtCurrent. I can see that file in the ….PersoftSTOfficeMacros directory when I explore, but not when I browse from within SmarTerm.
Well, with the new one (gui beta) you should just be able to start the program from the start menu and it will handle starting Smarterm for you and loading the necessary files.
Eric, our site has only ever used function PL-pending log, instead of the function OL. Will your program work with PL, or is there maintenance I need to do to utilize OL?
The OL only needs a worksheet to call up. The worksheet can be a group worksheet. Most labs end up creating a special worksheet with only the tests/departments they are interested in. But you can use any worksheet to try out the program. If typing in “OL” at the function prompt does not call up the outstanding log, you might need to get in touch with Misys to give you the program tag for OL. Alternatively, OL Monitor will try “LO” which usually brings up a report menu, then it chooses the outstanding log from that menu. If this works for you there is no need to get the program tag.
Our Misys labs use WRQ Reflections, does your product work with Reflections?
OL_Monitor uses Smarterm’s macro language to retrieve the data from Misys. So unfortunately no, it will not work with Reflections. However there are at least 2 other labs I know of who use Reflections but also have OL_Monitor running on Smarterm. You can download a free trial of Smarterm from Persoft’s website. I have a couple of links to their download site on my website here: http://www.olmonitor.com/Requirements.html
Let me know if you have any more questions.