[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re[3]: Global Server and Tradestation 2000i acted weirdly



PureBytes Links

Trading Reference Links

I am able to download the symbol using UniServer now and connected to
eSignal with no problem. The reason is my local date is Dec 12 while
exchange date is Dec 11 and I try to test it by downloading the 1 day
data only. Now the only thing left is how to get my old data back into
this so call "New" symbol. Anyway I am downloading the historical data
now using UniServer but limited only to 60 days tick data since  this
is the limit of eSignal.


Thursday, December 12, 2002, 12:19:56 AM, you wrote:

A> Thanks for the help. Now I face another problem that is to convert the
A> ES #F=2 from Future category  to Index category. I 1st export the data
A> out to an .xpo file then delete the symbol in Future category and
A> create a new symbol with the same name as Index but when I try to
A> import the exported .xpo file it doesn't recognize the existent of the
A> symbol. Now I try to download the data under Index using UniServer and
A> it show no data downloaded.

A> Wednesday, December 11, 2002, 11:53:15 PM, you wrote:

JW>> I think I had that same problem when I had ES #F=2 setup as a future. If you
JW>> set it up as an index
JW>> you will not see it. It has something to do with the volume.

JW>> Jerry
JW>> ----- Original Message -----
JW>> From: "AceTrader" <tradersh@xxxxxxxxxxxx>
JW>> To: <omega-list@xxxxxxxxxx>
JW>> Sent: Wednesday, December 11, 2002 10:47 AM
JW>> Subject: Global Server and Tradestation 2000i acted weirdly


>>> I am using eSignal with UniServer and when I insert the ES #F=2 or NQ #F=2
JW>> which are
>>> day session only symbol during the market start/active, these two chart
JW>> keep on
>>> refreshing itself and eating up the CPU resources.
>>>
>>> 1st I thought I had loaded too much charts and studies on it so I remove
JW>> all
>>> charts and left these two, the problem still persist. Then I change
>>> the symbol to ES #F and NQ #F, the funny part it the problem gone but
>>> this doesn't make sense.
>>>
>>>
>>> I am using AMD DUAL Athlon MP 1600+ with 512MB RAM and running on
>>> Windows 2000 Professional.
>>>
>>> This had not happen before and I just can't figure out why.
>>> Anyone have any ideas?
>>>
>>>
>>>
>>> --
>>> Best regards,
>>>  AceTrader                          mailto:tradersh@xxxxxxxxxxxx
>>>
>>>






-- 
Best regards,
 AceTrader                            mailto:tradersh@xxxxxxxxxxxx