|
PureBytes Links
Trading Reference Links
|
My first guess would be that the comcat.dll file is corrupt. Have you tried
copying one from somewhere else? Reboot and don't run anything else,
including the Server Timer or whatever that thing is that starts in the icon
tray. This should keep anything from loading the DLL and causing you a
problem trying to replace it or register it. Have tech support send you a
correct file if neccessary. Compare file sizes with them, though this is
not a guarantee that something inside the DLL isn't corrupt. Also, try
REGSRV32 /U COMCAT.DLL and see if you get the same or a similar message.
The /U option is "unregister".
Kent
-----Original Message-----
From: Chris Cheatham <nchrisc@xxxxxxxxxxxxx>
To: Omega List <omega-list@xxxxxxxxxx>
Date: Friday, May 05, 2000 1:47 AM
Subject: NT Question
Good morning,
I am stuck on a TS2000i install issue, and to date Omega's techs don't have
an answere short or reinstalling NT. Perhaps someone might have another
idea.
I installed the SP3 CD on Win NT4 SP5 on PII400 w/192M on its own hard drive
(D). Installed DBC broadcast/cable datafeed.
Installing the SP3 CD, all went well except I go an error message as
follows:
Files Failed to Self Register...
C:\Winnt\system32\comcat.dll
The file exists in that directory, though its date and I did a registry
search and it did appear in the registry. Omega says that this is problem
is related to the one application problem I have seen to date -- in the
charting/workspace application, the File/New command does not have the
normal icons present -- to create chart, quote page, browser, etc. The only
one there is to create a new workspace.
Omega suggested manually registering the file, by running regsvr32
c:\winnt\system32\comcat.dll. When I did this, I got the following
message...
C:\winnt\system32\comcat.dll was loaded, but the DLLRegisterServer entry
point was not found.
DLLRegistryServer may not be exported, or a corrupt version of
C:\winnt\system32\comcat.dll may be in memory.
Consider using Pview to detect and remove it.
Neither of these error messages appear in the lists in the NT4 Resource Kit.
Other than this 2000i issue, NT works perfectly. If anyone has any clues, I
would love to hear from you.
Thanks,
Chris
|