NT, Win 2000, and XP Problems
Installation hangs on completion
In Windows XP environments the install program usually hangs on completion
with two large white rectangular areas superimposed over the desktop. We
have never got to the bottom of this. The same install program closes perfectly
in Windows 95, 98, Me, and XP (usually), and we use Microsoft development tools to produce
both our software and its installation routines. All we can say is that, at this point, the install program
should have completed everything it needed to - it is just that NT or 2000
doesn't want to carry on from there. Simply "End Task"
(Ctrl-Alt-Del to bring up the Task Window) and don't worry about it.
OLE Error in Windows XP
Some XP users may encounter a problem: "OLE error ..., Class not registered" when attempting to run Print Preview or print a report to a printer. This information is provided for technically competent support agents or personnel. If you feel out of your depth on this and need assistance, we will gladly have a Remote support session with you. We are also happy to work with your own technical support agent, on any problem associated with running our software.
We have provided some tools to help overcome these sort of problems. If you have not already done so, please read and follow through the the instructions in our page on Low-Level Installation problems:
Click here for the page on Low-Level Problems (same window)
Click here for the page on Low-Level Problems (new window)
If you have already done this, and are still having problems, then the following information and instructions should help you (or your technical support contractor) work through these further:
1. Existence of correct files:
Using Windows Explorer, check that the following files exist in your "c:\WinNT\System32" folder (or "c:\Windows\System", or whatever you are using - which we will refer to as your "System32" folder in the rest of this page). Please also check their version numbers (by right-clicking on the files, selecting Properties, and then the Version tab) to ensure they are either the same files or more recent versions of them.
File Version Date Size RichTx32.OCX 6.00.8877 22 May 2000 200 KB RichEd20.DLL 5.30.23.1211 30 Aug 2002 414 KB RichEd32.DLL 5.1.2600.0 30 Aug 2002 4 KB MSMapi32.OCX 6.00.8169 24 Jun 1998 134 KB If the OCX files are not present, your install did not run correctly (which you probably already know by now).
If any of these files are missing or out-of-date, you will need to manually copy them into your local "System32" folder, register them, and see if this fixes the problem. (See immediately below for a more detailed expansion on this.)Warning: Do not overwrite any of these files (that are already installed in your "c:\Windows\System32" folder) with an older version. Doing so may cause other applications to not work correctly !!!
Use another instance of Windows Explorer to look at the files in your "\GECL\GESys" folder where the GECL software is installed. (They should be there if you have run a recent "WebUpdate", or worked through the "Low-Level Installation Problems" page referred to above.) Note that in the \GESys folder, the equivalent OCX files have a file extension of ".OOO" (all the letter 'O' not zeros). You can right-click on these and select "Properties" to check their version numbers against the values in the above table. If the version of any files we have supplied is newer than what is currently installed in your "\Windows\System32" folder (or is not, copy (repeat COPY) it into your "\Windows\System32" folder. (Don't forget to rename any ".OOO" files to ".OCX".) For added safety, it is very sensible to first rename the old files (or move them to another folder), rather than simply over-writing them.Note: If you encounter a "sharing violation" or similar problem, when trying to copy files into your "System32" (or "System") folder (especiallyRichTx32.OCX), then close down any applications that may be accessing the file (MS Outlook is often a culprit). If you still have "sharing violation" problems, try re-starting your computer (and not opening any other applications), and running the above procedures again. If this still does not overcome "sharing violation" problems, you may be stymied (unless a technical support person can work out what is causing the conflict). If you are running Windows 98 and encountering these problems (for some weird reason) you can copy the required files when Windows is not running. Do this as follows:
- Copy all the files into a temporary folder on the local hard drive, ("c:\Temp" say - you need to do this because you won't be able to access these files via your network when in DOS Mode),
- Re-start the computer in DOS Mode,
- Copy the file(s) that were causing problems into the "System32" folder
- Restart your computer again (in Windows)
- Register the new files in the Windows System Registry (see Section 2 below)
Additional assistance for obtaining up-to-date system files:
If your Internet security is such that you could not previously download and run "GESys.exe" on this (or any other) workstation (presumably you previously used a CD or an old and now retired workstation to download and install the main GECL software), then we have also provided the contents as a simple (non-self-extracting) ZIP file. Download this from:
Download low-level file installation program (GESys.ZIP - 814 KB)
Extract the contents of this ZIP file into a folder called "\GECL\GESys". Then run the newly extracted file "WkStnCheckSysFiles.exe" (in this new folder). If this seems to have run correctly (and you told it to upgrade any out-of-date system files), then run the tests identified in Step 3 of the page on "Low-Level Installation Problems". If these tests work OK, you don't need to do anything further.
If you were not able to obtain the desired files by downloading and extracting either variant of the "GESys" file from this current workstation, try doing so from another workstation, and saving and/or extracting its contents into a folder that is accessible from this (and any other) workstations that is having low-level problems. (A "\GECL\GESys" folder on your server should obviously be accessible by all workstations running GECL software.)
As a last resort, you can also download the system files directly from our website. However, we strongly advise against this, if you can obtain them from the normal "WebUpdate" or "GESys". (If you download the any files directly from a website, they will be be assigned a date/time stamp of the moment you download them. It is usually preferable to preserve the original date/times for any system files - which is what extracting them from "GESys" does for you.)
Please ensure you have read and understood the above paragraph first, and made every effort to use the other methods previously covered. The following links are provided for emergency and "quick-and-dirty" use only. If you really must, download whatever is required using the following links:
2. Try running GECL's Registration Batch File Again
A file "GECLRegi.bat" should have been installed into your "System32" folder. (Copy it from the \GECL\GESys" folder if it is not there.) Try running this again and see if it fixes the problem. (Use Windows Explorer to locate it, and then double click on its icon to run it, so it starts in the correct working folder.) For your background understanding, "GECLRegi.bat" is a batch file we have provided, that will ensure that all the classes and libraries (OCX and DLL files) needed by the GECL software, are registered in your local Windows Registry.
3. Check that "RichTx32.OCX" has in fact been registered
This next bit is particularly technical (and potentially damaging if you inadvertently press the delete or other keys in the wrong place). It is probably worthwhile, running the GECL software at this point and attempting to view a report on the screen using Print Preview. If it works fine, then you have fixed the problem and don't need to bother with the rest of these instructions.
- Run RegEdit (in c:\WinNT, or c:\Windows folder - you should be able to access it directly by typing "RegEdit" in the Start Menu Run option)
- Open up the "HKey_Classes_Root tree (Click on '+' sign)
- Skip down to the "RICHTEXT" class (type "RI" to jump down to it)
- There should be two nodes:
"RICHTEXT.RichtextCtrl" and "RICHTEXT.RichtextCtrl.1" - Open both of these (Click on '+' signs)
- Click on the CurVer & check that in the right hand window it says "RICHTEXT.RichtextCtrl.1"
- Check that under "RICHTEXT.RichtextCtrl.1" there is a node "CLSID"
- Open the CLSID node, it should show a horrendous ID in right window
- Move slider bar way up toward the top until you find a node called "CLSID"
- Open this "CLSID" by clicking on the '+' sign
- Use the slider bar to move down again until you find a CLSID with the same value as currently displayed in the right hand window
- Click on this node, and it should say "Microsoft Rich Textbox Control"
If this is the case, the OCX file has been properly registered.
If not, you will need further assistance from our Help-Desk.
If you need further assistance or have feedback you would like to give us,
please contact our Help-Desk:
E-Mail now to: Support@Adminsoft.com
Phone: (09) 262 2010, Fax: (09) 262 2021 (within New Zealand)
(From overseas +64 9 262 2010 or +64 9 262 2021)