Seeking advice to cure freezing of Volume charts.
Came across this on esignal....
Buffer Overrun Error, Winsig.exe Crashes - Clearing Up a DBCAPI.DLL Conflict
Overview
The file dbcapi.dll is used by eSignal to operate within the Microsoft Windows environment. It's the principle file that manages the functions between the eSignal Data Manager and the eSignal Charting application. It's also used by all eSignal-compatible Third Party software. Each time you upgrade to a new version of eSignal, the older version of the dbcapi.dll is overwritten.
We have run across occurrences where when a third party software is installed, an older version of the dbcapi.dll appears in the Windows Directory. This can result in eSignal using the outdated version of the dbcapi.dll and can cause servere side effects when new functions are called. Typically, this is seen as either a buffer overrun error or a winsig.exe crash.
Solution
The remedy is to rename the outdated version so eSignal uses the more current version. We suggest renaming the older dbcapi.dll files to dbcapi.old. This is a safe procedure as all newer dbcapi.dll are backward compatible.
I have 3 dbcapi.dll files one in each of....
C:\WINNT\system32
C:\Program Files\eSignal
C:\Program Files\AmiBrker
I don't use Amibroker anymore but not sure whether to re-name all 3 as dbcapi.dll.old. easpecially the WINNT\syste32 ?
Also will esignal create a new file on next start up(not downlaod) if I delete all 3?
Appreciate any feedback.
thx
swan
Came across this on esignal....
Buffer Overrun Error, Winsig.exe Crashes - Clearing Up a DBCAPI.DLL Conflict
Overview
The file dbcapi.dll is used by eSignal to operate within the Microsoft Windows environment. It's the principle file that manages the functions between the eSignal Data Manager and the eSignal Charting application. It's also used by all eSignal-compatible Third Party software. Each time you upgrade to a new version of eSignal, the older version of the dbcapi.dll is overwritten.
We have run across occurrences where when a third party software is installed, an older version of the dbcapi.dll appears in the Windows Directory. This can result in eSignal using the outdated version of the dbcapi.dll and can cause servere side effects when new functions are called. Typically, this is seen as either a buffer overrun error or a winsig.exe crash.
Solution
The remedy is to rename the outdated version so eSignal uses the more current version. We suggest renaming the older dbcapi.dll files to dbcapi.old. This is a safe procedure as all newer dbcapi.dll are backward compatible.
I have 3 dbcapi.dll files one in each of....
C:\WINNT\system32
C:\Program Files\eSignal
C:\Program Files\AmiBrker
I don't use Amibroker anymore but not sure whether to re-name all 3 as dbcapi.dll.old. easpecially the WINNT\syste32 ?
Also will esignal create a new file on next start up(not downlaod) if I delete all 3?
Appreciate any feedback.
thx
swan
Comment