|
PureBytes Links
Trading Reference Links
|
A couple of years ago I ran Ensign with DTN 8000 via satellite connected
via plain old serial port to a 128 meg P133 running NT4. Along with
Ensign, I kept about a dozen other apps up and running including several
TA packages, email, browser, and order entry software all running off
the 2nd serial port. Ran like a charm and tick loss, when compared to
T&S data posted nightly by the CME, was next to nil. Also none of the
other Win9X crap from resource problems to a crash in one app bringing
down the whole system. Trading professionals would be wise to rely on a
real OS. Win9X is an enhanced house of cards formerly known as the
Windows Operating Environment running on top of DOS. If Microsoft
couldn't make the thing reliable, there is little (software or hardware)
which any user can do to overcome the limitations. There is an old
saying "you can't make a silk purse from a sow's ear".
Earl
----- Original Message -----
From: "BobR" <bobrabcd@xxxxxxxxxxxxx>
To: <realtraders@xxxxxxxxxxxxxxx>
Cc: <realtraders@xxxxxxxxxxxxxxx>
Sent: Tuesday, April 11, 2000 4:45 AM
Subject: [RT] GEN - Tick counts
> This may be an old subject to some, news to others. I received the
DTN 8000
> receiver today and it was accompanied with a Chameleon software user
guide.
> Appendix C is titled "Solutions for Com Port Errors". Here are a few
quotes
> from it, "Users who have migrated from Windows95 to Windows98 have
reported
> that while there were no or few errors in Windows 95, errors increased
> sharply in Windows 98. A high number of CRC or overrun errors (more
than 2
> or 3 per hour) may result in lost or erroneous data. " Their
conclusion was
> that W95 or NT were better choices than W98. I suppose W2000 would
also be
> included, but it wasn't available when the book was written in 1999.
This
> is pretty much what traders have experienced. Some have changed data
feeds.
> Some have tried the TurboExpress card.
>
> The Appendix C recommended solutions are:
>
> 1.In the System Device Manager drop the FIFO recv and Xmit port
settings to
> the next to lowest setting.
> 2. In the Advanced Graphics Settings move the Hardware acceleration
slider
> to the second lowest setting. Restart computer to make the changes
> effective.
>
> Another suggested alternative for Win98 users is to use a USB to
serial
> converter. This along with an installation disk makes the USB port
look like
> a COM port. "In testing, there were zero errors from day to day, with
only
> an occasional CRC error over a week's time using the converter. The
> converter emulates a COM port but is actually a USB device, using no
IRQ or
> other resources. You do not have to open the computer case to install
the
> converter. You insert the installation disk that ocmes with the
converter
> in your flopppy drive, then plug the USB Type A conector into an
available
> USB port on your computer. Windows98 automatically displays a message
box
> "Unknown Device Found." Follow the instruction tat come with the
converter
> to install the device drivers from the floppy disk to your computer's
hard
> drive. Typically the converter installs as the next available
unassigned
> COM port. When installation is finished you can check Device Manager
to
> confirm the new COM port assignment.
>
> The next suggestion was the use of the TurboExpress card which many
are now
> familiar with.
>
> I would like to know if anyone on these lists has tried the USB to
serial
> converter. If so which make and model was used? What are the baud
> limitations?
>
> Thanks,
> BobR
>
>
>
>
>
|