Hello, The problem is that whenever people are having problem they speak up here, but as soon as problem is solved they do not bother to mention that.
That was the case countless times and that was the case too. Two people having problem installed the Data Manager from here: http://www.amibroker.com/bin/eSignalDMClient.exe as I told them, and they are fine now. But they of course FORGOT to tell that on the list, because happy user is SILENT user. And saying that something works after problem is resolved "not worthwhile" for most people. So INSTALL THIS eSignal DATA MANAGER: http://www.amibroker.com/bin/eSignalDMClient.exe You need to understand that the plugin is written and tested with CERTAIN VERSION of 3rd party API. If third party API data vendor chooses to CHANGE THEIR API and make some incompatible changes, and do not announce changes or test their API against compatiblity issues, it can cause the problems. So you should use the data manager that has been tested and proved to be working correctly. And that means this one: http://www.amibroker.com/bin/eSignalDMClient.exe Best regards, Tomasz Janeczko amibroker.com ----- Original Message ----- From: larypowell To: [email protected] Sent: Saturday, February 07, 2009 8:13 AM Subject: RE: [amibroker] Anyone else with slow eSignal? I have to keep doing a "force backfill", and / or shutting down the data manager and starting it again. I thought it was just me. Larry M Powell ------------------------------------------------------------------------------ From: [email protected] [mailto:[email protected]] On Behalf Of Gordon Rose Sent: Thursday, February 05, 2009 6:43 PM To: [email protected] Subject: Re: [amibroker] Anyone else with slow eSignal? Hi Tomasz, Thanks. I will try this. I did some detailed troubleshooting by uninstalling eSignal 10.2 and installing 10.3. Same problem. Then I uninstalled 10.3 and went back to 8.0R2 (from 2006 -- poked around my downloads). Interesting, this version is fine. I did this testing on two separate machines with identical results on both. I will try the data manager you sent with 10.2 and see what the results are. Side note -- I believe you've weighed in on ZenFire -- any changes in your plans to add or not add support? Regards, Gordon ----- Original Message ----- From: Tomasz Janeczko To: [email protected] Sent: Tuesday, February 03, 2009 6:50 PM Subject: Re: [amibroker] Anyone else with slow eSignal? Hello, You may try using this Data manager version: http://www.amibroker.com/bin/eSignalDMClient.exe and see if it helps. Best regards, Tomasz Janeczko amibroker.com ----- Original Message ----- From: Gordon Rose To: [email protected] Sent: Tuesday, February 03, 2009 4:02 PM Subject: Re: [amibroker] Anyone else with slow eSignal? Hi, I meant to add that I'm running AB 5.2.0, eSignal plugin 1.9, and eSignal 10.20 (build 396) (I've heard there are issues with 10.3, sticking with 10.2 for the time being). OS is XP SP3 and machine has 4GB RAM and a dual-core CPU. Regards, Gordon ----- Original Message ----- From: Gordon Rose To: [email protected] Sent: Tuesday, February 03, 2009 9:53 AM Subject: [amibroker] Anyone else with slow eSignal? Hi, Recently I noticed that the eSignal plug-in was losing ticks. Sometimes the chart stopped updating altogether. eSignal itself flies along along, so that hasn't been the issue. I emailed support, and the response was essentially that that shouldn't be happening. Since then, I used the faq to make sure my charts were updating sub-0.1 second and that I had the latest plugin version. I also went so far as to temporarily uninstall my anti-vius and -spyware software. No luck. I emailed again, but no response this time. (I usually get an excellent response from support, hopefully my response email just got lost somehow). Today I tried it on a different machine -- same chart, etc. and unfortunately, same result. There are clearly many missing ticks, and the chart has stopped updating completely a couple of times. If I force backfill, it fills in the missing ticks and volume, but the problem doesn't go away. Since I've tried it on two computers now with identical results, I'm wondering: a) has anyone else seen this? b) does anyone have any ideas for troubleshooting thoughts that might help get at the root cause? Thanks for any thoughts anyone might have. Regards, Gordon
