Advanced tab left

Advanced tab left

If the program is having problems getting the log or starting/communicating with Smarterm, you may be able to solve the problem with the advanced tab.

1 . Smarterm exe pathSmarterm exe path

Smarterm exe path

This should list the full path to the stoffice.exe program file.

Normally you shouldn't have to mess with this setting.   OL Monitor automatically locates the stoffice.exe file.

You can click Find to have OL Monitor do a search for Smarterm, Browse to try and locate it with file explorer.

If the exe is not found, have you installed Smarterm?   Is Smarterm installed as a citrix app/virtual server?


*Sunquest/CPL versions of Ol Monitor only.

HMS does not have this.


2 . Precompiled filesPrecompiled files

Precompiled files

The precompiled files contain the macro code necessary for interacting with Smarterm.   Smarterm loads this code if it is present when it runs.  

This box shows the PC files if found in green when they are present and the right version.  

Red indicates a problem:

-If Smarterm is started and the files are not present,

-classic precompiled files are present instead, or

-the files are hidden.

If the PC files are not present in the StOffice dir OlMonitor will not refresh.

If you install as a limited rights user, these may not install.   More info.


The "Fix", "Start", and "Stop" buttons previously found here were redundant and removed in version 1.88q.

*Sunquest/CPL versions of Ol Monitor only.

HMS does not have this.

3 . ST control boxesST control boxes

ST control boxes

Attempt PC files copy: Every time OL Monitor starts, it checks to ensure the Precompiled files are present and the right version in the StOffice folder.   If they are not, OlMonitor will attempt to copy them into the folder.   This can be a problem because Windows 7 does not like it when a program decides to poke around another program's folder and then have the audacity to put files in there.   So it may block both the attempt to check the files and the attempt to copy the files.   So this option is present to prevent OL Monitor from trying.


Alternative ST launch: OL Monitor accomplishes the lauch of Smarterm via OLE automation.   However this

4 . Logfiles pathLogfiles path

Logfiles path

This is where the Smarterm script/macro places the captured logfiles containing current test info.  

In most cases this will be the Smarterm Sessions directory.

OL Monitor makes an attempt to get Smarterm to use the "Public\Documents\OlMonitor" folder captured logs.   However depending on what version and how you have Smarterm installed it may not allow that change.

So the folder location may vary depending on what version of Smarterm is installed and what options were used.   OlMonitor automatically searches multiple locations to find the logfiles but occasionally fails to locate the right folder.


*Sunquest/CPL versions of Ol Monitor only.

HMS does not have this.

5 . Smarterm macro folderSmarterm macro folder

Smarterm macro folder

Believe it or not OLMonitor does not use the Smarterm macro folder.

OlMonitor places it's macro code directly in the Smarterm application folder (Smarterm stoffice.exe folder).  

The only reason this is here is to avoid a Smarterm error that can occur: "Cannot find specified file" or

"UserVT.stm not found".   When Smarterm loads it searches for the default macro file, if there is no file Smarterm has an error box that has to be clicked every time.

OlMonitor checks before launch and will try to place a 'dummy' macro file in this folder if there is no macro file there already.


*Sunquest/CPL versions of Ol Monitor only.

HMS does not have this.


6 . Operating SystemOperating System

Operating System

This is more for your information.   Ol Monitor detects the operating system it is on and changes it's behaviour accordingly.

Ol Monitor v1.77 and above is designed to work with Windows 7 NOT using compatibility mode.   However if compatibility mode has been engaged, it is impossible for OL Monitor to correctly determine the actual operating system, and may start trying to do things, use folders, that are disallowed in Windows 7.   So if for some reason you decide to engage compatibility mode on Windows 7, you may also want to let Ol Monitor know about it to avoid potential problems.

7 . Lab SystemLab System

Lab System

Select your LIS system.   Sunquest is the default on a new install.


HMS users: After you select HMS for the first time click 'OK' and then go back into options.   You will notice that many options that are not relevant to HMS are no longer visible.  

*Although Smarterm is mentioned a lot in the documentation, Smarterm is NOT required for HMS.  

HMS folder options are explained here.

8 . SecuritySecurity


Encrypt PID/processlog: OL Monitor will encrypt both the captured test logs as well as the debug/error OlProcesslog file used for troubleshooting.


No PID in processlog:     During troubleshooting, we may need to look at the OlProcesslog file which can contain PID.   Enabling this option will prevent any PID from being put into OlProcesslog.   Whenever you save this option the current OlProcessLog will be deleted since it might contain previous PID.


Private patient name:     This will remove the patient last name and replace with just the first letter of the last name.   I.E.   "SMITH, JAMES" would display instead as: "S, JAMES"

9 . AutoscrollAutoscroll


The default is automatic interval, but this can sometimes be problematic.   You can select a fixed interval or just turn autoscroll off.

10 . Keep Smarterm hiddenKeep Smarterm hidden

Keep Smarterm hidden

Techs may find it distracting to have the Smarterm window flashing in the toolbar.   Check this option to hide the Smarterm session completely.

If you are troubleshooting you may want to Un-check this option so you can switch to the Smarterm window and check the macro.


*Sunquest/CPL versions of Ol Monitor only.

HMS does not have this.

Created with DrExplain