|
PureBytes Links
Trading Reference Links
|
a single beep when the computer is emitting POST code
failure is one thing. Simply consult your motherboard
users manual to reference the Brand CMOS your board
holds and go from there. However, beep(s) after
crash... hummm.
Sounds like hardware failure to me, but can't be
positive. You've checked your CPU fan to make sure
there is no intermitent failure of cooling taking
place. Assuming there is a fan.
Memory is a huge culprit many times in the many 1000's
of systems I've worked on. If doable, you might want
to swap out the memory banks and run the check again.
I used to use a 16650 UART chip at my comm. port, via
a lavalink card, for increased data throughput.
I don't have enough of an understanding of the
dyanamics of DDE porting to understand if this would
affect increased efficiency of data.
best of luck.
mike ball
--- indextrader <indextrader@xxxxxxxxxxxxx> wrote:
> Actually, I've had as many as 900 symbols collecting
> real-time data in a
> different machine. Of course, the tick count
> averages out to normal on that
> many symbols.
>
> As to why DDE, well, I guess it's partly because of
> the ease of use for
> non-programmers like myself. Its possible to do a
> lot of interesting stuff
> with DDE, excel and live data that one can't do once
> it's already in the
> tradestation globalserver.
>
> Can anyone shed some light on the possible cause of
> a single "beeeeep" every
> minute or so comming from a computer that crashes?
>
> I read somewhere that maybe its faulty memory?
>
>
>
>
> > That sounds like quite a log of 'stuff' for a
> program to be getting
> through
> > DDE. DDE is a notoriously buggy transport
> mechanism (as a former
> programmer
> > I know this) - Microsoft actively discourages
> people from using it,
> > prefering to steer them in the direction of newer
> technologies. God knows
> > why so many Fin. Market apps still insist on
> exporting realtime data only
> as
> > DDE - they should have migrated to more stable
> technologies by now.
> Vicious
> > circle I suppose - Charting apps use it because
> datasources export it,
> > datasources export it because charting apps use
> it.
> >
> > Anyhow I don't think I've answered your question,
> but am merely expressing
> > surprise that DDE holds up as well as you've
> depicted...
> >
> > Regards,
> >
> > Ron W
> >
> > -----Original Message-----
> > From: indextrader
> [mailto:indextrader@xxxxxxxxxxxxx]
> > Sent: Friday, December 19, 2003 5:30 PM
> > To: omega-list@xxxxxxxxxx
> > Subject: Computer tick-handling capability
> >
> >
> > I use a DDE program to feed 1 of the tradestation
> machines.
> > It collects data on about 300 symbols.
> > Quite a few symbols are in the 30,000 to 50,000
> tick range per day.
> > My problem is that the data vendor's program seems
> to be crashing during
> > periods of high volume (at the open and close of
> the session).
> >
> > I'm trying to narrow down the culprit of the
> crashes (could it just be too
> > much data being processed)?
> >
> > I remember a while back something about a Pacific
> commport adapter card?
> > Is this something that would be helpful is
> resolving issues of too much
> > data/data bottling up somewhere?
> >
> > When the machine crashes, it emits 1 single
> "beeeeep" roughly every
> minute.
> >
> > Any help is appreciated.
> > Thanks.
> >
> >
>
>
|