|
PureBytes Links
Trading Reference Links
|
Dear David:
I have the same problem as long as I run TS on NT-4.
The gentlemen who use to sell T-Ports had a "work around" paper to solve
the problem on his web site. I download the paper and lost it. When I
tried to find the paper again the it was not on the web site and the
T-Port was out of business.
As much as I recall (and my memory is not it use to be) Window NT
"confuses" mouse port with com port some times (and some times not). The
lost paper described how to "fix" that problem.
So for now when I do have to restart TS and get message "Com port is not
present" I rebut computer (without turning it off) and try to start the
TS server. I have to do it about 3 times on the average until TS Server
recognizes com port. If message says "failure to establish
communication" as opposite to "hardware is not present" then I do not
have to restart Windows NT I need only to restart TS server.
I know it is not much help, but that is all I can offer.
Very truly yours
Alexander Levitin.
Subject: TradeStation Server and Windows NT
Date: Tue, 13 Oct 1998 17:57:24 -0700
From: "David Powell" <dwpowell@xxxxxxxxxxxxxxxx>
Help - Has anyone had the problem described below and figured out a fix?
I've had the problem described below on two different machines. The
first was an IBM Pentium 166 with Windows NT 3.51 platform and
TradeStation 3.5, then 4.0 build 19.6 all the way up to build 21. Data
via cable, Com Port1, first by Signal (until the class action law suit
gave me a chance to switch), then (switched to ) BMI. I thought the
problem was the lousy, crumy IBM box and it would go away when I
upgraded (wrong). I now have a Dell Dimension XPS R400 with Windows NT
4.0 service pack 3, running TradeStation 4.0 build 21. Both machines
had cable data coming in on Com Port1 and the modem/internet coming in
on Com2.
The Problem - when I have to take the machine down, the Server gives me
the message: "Hardware not present FAILURE TO ESTABLISH COMMUNICATIONS
Unable to synchronize at 38400 about to try baudrate at 57600" Then it
cycles through all the baud rates with the same messages.
The only way I have been able to get the thing to work is to change the
com to com3, exit out of TS, Shut down the machine, turn it OFF, wait a
few minutes, power back up, fire up the server, let it get its nasty
fill of com3, change to com1, and then, if I'm lucky, I get:
"Communications established Baud rate is set" Otherwise, I have to
repeat the process until it works. This can take an hour, easy. Any
ideas? Omega doesn't support NT and vice versa.
Thanks !
|