|
PureBytes Links
Trading Reference Links
|
Just to confuse the issue a little further-- since your original problem
stemmed from having your computer clock set to PM instead of AM, there is a
cute little program called ATOMTIME.EXE which synchronizes your CPU clock
with the U.S. Naval Observatory clock via the Internet. You should be able
to find it at http://www.komando.com/ or let me know & I can send it to you.
--------------------------------
At 12:35 PM 5/12/98 EDT, you wrote:
>In a message dated 98-05-12 11:39:48 EDT, you write:
>
><< I bought a new computer this weekend.. Copied all the Omega directories
> from my old computer, then Installed TS build 18 and then upgraded to build
> 21 from the web site.
>
> Seemed to work fine on Monday (5/11), but today (5/12) it's really acting
> strange. With my 5 minute charts all of today's data so far is compressed
> into one bar at the right-hand edge of the chart, stuffed on to the end of
> yesterday's data. According to the chart, today hasn't started yet.
>
> Editing the tick file from the server, it says the last available date is
> 5/11 (yesterday). But this morning's ticks are showing up there, in
> yesterday's data. Near the end of the file the time stamp rolls over, from
> 16:25 to 9:30 (today's ticks)
>
> What could possibly be going on here??? >>
>
>Omega won't help you. Call Signal.
>
>As I told you in my first response to your request for help, you
>should check your datafeed reception. You were probably getting
>a lot of bad packets yesterday after the close of trading, causing the
>server to miss the date change. Consequently, all entries in the
>server's System made today are showing the yesterday's date.
>
>In your case, to begin proper collection, you must first delete
>all ticks in the yesterday's file received past 16:20, that is, all
>today's ticks.
>
>The restart the server to reset it to show the correct day. The server
>will then begin collect data properly -- at least until midnight.
>
>You can check at midnight tonight to determine whether you are
>going to have the same problem tomorrow. Use a Globex contract
>to see if the incoming ticks are properly stamped. If not, restart
>the server to reset it.
>
>At any rate, the culprit is your datafeed. (Here is an easy way to
>prove it -- how many list members had the same problem today???)
>
>Igor Uhrik
>
>
>
|