Error in RegWrite

| Leave a comment

Last Thursday, I guess our OL Monitor stopped working. I wasn’t at work when it happened, and have been away for a week. The person who initially installed the program tried to uninstall and reinstall but didn’t have PC permission to install. When I called our IS dept today for permission to reinstall, there was a part that it said it couldn’t uninstall but my Tech said go ahead with the new reinstall. Now I keep getting an error and it won’t run. The error is as follows:
“Error in: RegWrite # :-2147024891 Invalid root in registry key
“HKLM\Software\BasicScript Program Settings\OlMonitor\Status\MessageBar”
WshShell.RegWrite 0/0
I can’t get past this error. I click OK and it keeps returning again and again. Any help you can give me would be greatly appreciated. We do have OLMonitor currently up and running on a different PC and it is working Great!. It’s just this one PC that won’t work.

The uninstall is important, lately I have noticed the main program file sometimes does not get replaced if you don’t uninstall first. This may or may not be the problem. The root BasicScript key is actually installed with Smarterm. Is this program installed? It is important to have admin permissions when installing and setting up the program. After reinstalling with admin rights if you still have trouble you can try using a different location for your settings instead of the registry. If you can load the program and get past the errors to the options screen, you can select ‘ini file’ as the location under the ‘Misc’ tab. This may clear up any problems accessing the registry. If this does not work follow the steps on the troubleshooting page:
http://www.olmonitor.com/support.html
To generate a problem report for me to look at click help from the program menu and choose ‘generate problem report’. If this is a problem with your settings, which are not removed on reinstall, see how to modify the settings manually here:
http://www.olmonitor.com/settings.html
After you backup your settings you can try deleting the registry keys and restart the program to let it load with the defaults.

OL Monitor Installation

| Leave a comment

Where the settings will be saved: From reading the manual, and based on the fact that we are a Citrix site, I had to have a PC administrator install the software since I do not have administrator privileges on most PCs (I can get them for a particular PC, if needed, but have to make a special request) it appears that it would be best to save the settings to the Ini File. has indicated that she has problems with where her settings are saved and this has caused her some problems.
Login, etc: I have set up a specific user MONITOR, OL in Misys with a tech code and a login, and only one function–OL. I have also defined a group worksheet–OL. Is there anything else that needs to be defined in Misys?

Hi again, to answer your questions:
1. I don’t have any direct experience with installing and running over Citrix. I would expect that you would have more success using either the ..ini file or the current user setting. The ‘All Users’ section of the registry will most likely be completely off limits. ..ini file: I have no idea how Citrix will handle this setting. If it reads and writes to the server it may be that all your settings are shared between users. On the other hand, it may not work at all. ‘current user’: This has the most chance of succeeding, most programs need to read and write from the user portion of the registry to function, so surely Citrix has taken this into account. The only problem is that whenever a new user logs on, he/she will start out with the default settings. To get around this you can export your settings and have the user or a script import those settings when logging on.
2. You should probably have admin privileges to setup the program settings. For day to day operation you can have a power user logged on. But anytime you want to change a setting you may have to logon as admin again.
3. Login etc: no that should be it! As you experiment with the filters you may find you can add more things to the group worksheet and use filters to fine-tune what displays.
4. Read this only if you encounter weird problems: Inter-program read/write restrictions. I made this term up. Basically in some hospitals one program is not allowed to write any information to the folder of another program. IE, OlMonitor writing to the Smarterm directory and vice versa. Since the .ini file is in the OlMonitor directory it can be a problem when Smarterm can’t write to it. Usually any program can read from another folder, but writing may be restricted. If this happens, OlMonitor may not be notified when Smarterm can’t logon or needs to notify you about an error. Smarterm may hang and you may get some ‘sync error’ messages. More importantly, OlMonitor may not be able to send the macro codefiles to the Smarterm folder. This is a show-stopper and recently I had to show one site how to manually copy these files into the folder.

Version updates

| Leave a comment

Are there additional fees that apply to upgrade to new versions or patches?

There are no additional charges for UpDates to your current version or patches. Typically a software version change would require a new purchase (I.E. upgrading from Win98 to WinXP or Max OS9 to OS10). To make a version change the software has to have added a significant number of new features or have accumulated enough small feature updates to warrant a version change. But I think the question you are asking is whether you will be charged for updates, the answer is no. For example if you have an issue that we work through and it requires a change in the code and an update, this update is free. The update will change the make number (ie version 1.27 becomes 1.28) but not the version. This update will also be available to anyone else. For another example, I recently added an auto-updating feature to the software. This is a very useful feature but it is also just an update, it bumped the make number from 1.26 to 1.27. Now any 1.X license holders are free to update to that version.

Overview

| Leave a comment

Wednesday, June 13, 2007
What, briefly are the requirements and footprint of Ol Monitor. What are the major points in configuring and installing the program?

Here are some specs:
Program installer: 6.31 MB
Optional Sounds (in wav format):
Compressed: 12.6 MB
Uncompressed: 24.1 MB

Requirements:
Pentium 200 MHz or greater
Smarterm 11.0 or higher
Admin or power user permissions to install and configure
Regular users should be able to run the program fine, they may have difficulty changing settings depending on where the settings are stored: see: http://www.olmonitor.com/ManualM/window_3_6.htm for detailed information.

Installation:
Installation is a straightforward Windows program setup.

Configuration:
See link above for options on where settings are stored.
Settings can be exported to a .reg file for importing into the registry.
Settings can also be saved to an .ini file. The .ini file must be located in the OlMonitor folder in program files.
An install script or batch file can be written to deploy the program to each workstation. A default configuration can be applied before or after the install in the form of an exported .reg file that can be executed. Or an .ini file can be copied into the OlMonitor folder. If you plan to use an .ini file by default there is a line in the OlMonitor.stw session file that needs to be changed to instruct the program to use the ini file. So along with the .ini file you should also copy a modified OlMonitor.stw file to the same folder.

Considerations:
The majority of problems that people encounter are:
Program works fine during installation and initial configuration by user with admin rights, but when a user with restricted permissions attempts to use the program they have problems. The program needs to constantly read and write from the registry or alternatively the .ini file. The ‘all users’ section of the registry can be read or written by admins but not restricted users.
Most Misys users who are familiar with the ‘roll and scroll’ vt interface are aware of what needs to be entered to logon to the system, but they may not remember the ip address or shortname to the Misys user. User is prompted for the ip after 30 seconds by default if it is not already saved. This item cannot be skipped over.

Installing over previous version

| Leave a comment

Thursday, June 28, 2007
Eric, should I uninstall the existing program when it tells me to? or just leave it there and install the new one also?
If I uninstall the old, will I lose my settings?

No don’t worry it will keep your settings. (It’s getting rid of them that’s difficult). You can install over the current version in most cases without uninstalling first.

Outlook.jpg

Copying over classic version to new pc (not upgrading to VIM)

| Leave a comment

I recently installed three new PCs in one of our labs. The old PCs were running SmarTerm 10.0 which was using for Misys. They had a macro configured to use OL_Monitor. I was not successful moving that macro over to the new PCs which are running SmarTerm 12.0. Do you have any documentation on how to setup that macro or how I can copy files from the old PCs? Thanks in advance for you help!

Along with the wrkgvtcurrent.stm file which should have been in the Smarterm macros directory you also need these files:
Uservt precompiled A current.pcd
Uservt precompiled A current.ppc
Uservt precompiled B current.pcd
Uservt precompiled C current.pcd … <– these are located in the Smarterm program folder in
c:\program files\Esker\Smarterm\StOffice
(this is more or less what it might be, you get the idea)
3 other non-essential files are also in the program files directory:
Yes.txt,
Gatherer.exe, and
zip.exe.
Finally there may be a couple of files in the Smarterm sessions directory: OlMonitor.stw and possibly
OlMon.ini (if it was an older version)
Copy these files back to their respective locations on the new pc. You may find that Smarterm has slightly different folders in the new version, instead of using the Program Files folder to store the Macros and Sessions folders, it puts them in the C:\Documents and Settings\All Users\Documents\Smarterm
directory.
You may also want to export some registry keys:
HKEY_CURRENT_USER\Software\Basicscript Program Settings\OlMonitor
and
HKEY_LOCAL_MACHINE\Software\BasicScript Program Settings\OlMonitor

This will save them from having to setup the whole thing again and believe me it’s no picnic.
On the website there is some information on the registry settings: http://www.olmonitor.com/settings.html

Phantom filters

| 2 Comments

Monday, May 21, 2007
I have noticed a couple of times (most recently) That if I put in filters one day and come back to the monitor a few days later nothing will show up until I turn the filters off. When I go under the filters, a lot of the ones I built are blank and the ones that actually have things in them, don’t work. Do you know the problem. It doesn’t show any errors, but nothing works until I rebuild the filters again.

Does anyone else have access to the computer you are testing on? It’s very easy(too easy) to accidentally create a blank filter that fouls everything up if you right-click on the patient list which brings up the quick filter dialog. I had one user tell me he fixed this problem by removing the keyboard from the olmonitor computer. A filter that has no name defined or one of the fields is blank can throw off the whole set.

Division by zero error when moving columns

| Leave a comment

Monday, April 23, 2007
Thanks for setting up the condensing on collected specimens. That seems to be working okay.

Because of security issues here, we had to move OL-monitor to XP. The program seems to work okay except for one little hitch. When we try to move a column to have the display set up in an order which we would prefer, we obtain a division by zero error which closes the program but leaves SmarTerm open. When we move a column in Windows 2000, this error does not occur. Is this fixable? Thanks

It was a microsoft bug, here is the fix:
http://support.microsoft.com/kb/896559

I applied the update to my installer as well so you can also get the update by simply downloading OlMonitor and installing again.

OL Monitor with Cerner

| Leave a comment

Monday, April 30, 2007
Is there any similar functioning OL Monitor for Cerner? Our lab has Cerner Classic, and we are getting Middleware Solutions 8.04 by Roche. I have been wanting for some time, functionality that alerts me when out targeted TAT for STAT samples is approaching or is exceeded.

I have actually developed a version for Cerner Millenium for my hospital which had converted over from Misys to Cerner. Although my knowledge of Cerner Classic is pretty limited, I am sure it would be possible to adapt the program.

DDE Server error

| Leave a comment

Thursday, April 12, 2007 12

Hi Eric – I’ve downloaded the trail of VIM and am coming up with the following error.

I am running v8.0 Smarterm. I realize it’s not been tested with this version but do you know if other users have reported a similar error or do you know what this error is caused by? I seemed to be okay then tried to open a new session of Smarterm to view Misys on the same machine.
It seemed to give me problems after that. Do you think this could be related to that and does OLM have to run on a dedicated machine?

Yes normally you should be able to open another Smarterm session and continue as usual… Although OlMonitor can be sort of a screen hog and tends to get in the way. I think it must be due to your Smarterm version. I’m not sure whether 8.0 was affected but 10.0 had a bug in the macro engine that caused errors, there is more info on that in the faq page:
http://www.olmonitor.com/FAQ.html
There may be other patches available for 8.0 on the Esker website. Try going to :
ftp://ftp.esker.com/32-bit_smarterm/ver8/
There look for the Index.txt file which tells what all the patches are in that directory. The macro patch might fix the problem.

pic31673.jpg