|
PureBytes Links
Trading Reference Links
|
Pundits of TS running under NT will tell you that TS is not optimized for
NT. They'll wine about how the 16-32bit conversion process hampers TS
charting performance so you don't get your ticks updated as fast. They'll
makes inferences about how that can affect your bottom line. NT has to
convert therefor you don't the information as fast, therefor you don't the
information you need to trade with as fast. That's balloney! Don't listen
to that (like I did). I've run TS4.0 under both and I'm here tell you that
it seems as if TS4 was made for NT not Win95. There's no perceptable
difference in charting performance or any other feature of TS under NT.
Under NT I could go away for a week, or two, or three, leave my server
running and rest assured my system was collecting data. In Win95 I get a GP
every 2 days so I can't leave knowing my machine will collect data. Under
Win95, the hassle factor has gone through the roof!
Hopefully Win98 will alleviate this and work more like NT. I suspect
however, that for the kind of rock solid performance I need, going back to
NT is my only option.
Brian.
-----Original Message-----
From: Carroll Slemaker [SMTP:cslemaker1@xxxxxxxx]
Sent: Thursday, March 12, 1998 12:38 PM
To: omega-list@xxxxxxxxxx
Subject: Re: Falure to establish communication & NT 4.0
I am running TS on Win NT and have been for quite some time. I'm
currently using TS 4.0 running on NT 4.0 service pack 1 (I've read too
many horror stories about service packs 2 & 3).
I, too, leave NT and TS running for five or six days uninterrupted and
have NEVER had TS bomb out with a GP or any other fault. I shut down
and reboot on the weekend, primarily to eliminate the consequences of
"memory leaks" (gradual increase in the size of the virtual-memory
requirement due to failure by someone - app or OS - to return memory to
the available pool when the app terminates). Also, although I routinely
have several other programs running concurrently with TS, I am careful
to run TS in its own, separate memory space.
Communication problems are most likely due to subtle incompatibilities
among the particular hardware devices on a particular system, their
corresponding drivers, and their particular configurations. I had to
buy a separate I/O card to get my system to work, not because I needed
another I/O port but because I needed a port on which I could configure
the IRQ and the interrupt address independently and which could use
higher IRQs.
Bottom line - NT is a VERY stable and dependable OS and handles almost
all of my old DOS programs very well (the only exceptions being some old
communications and backup programs - now discarded).
Carroll Slemaker
|