Search results

The Unix release has now been brought up to 858.

It sounds like your tws.xml file cannot be overwritten. Make sure this file is not read-only or locked by another process. Also, I suggest you delete your settings.xml file, which is no longer used. To find the directory containing these files, run TWS, select a ticker row, and press ctrl-alt-U.

What build TWS are you running (check from Help/About)? All known BookTrader problems are fixed in TWS 858. If you are running 858, please describe how to reproduce the problem and we'll look at it. Thanks.

P.S. - The problem only occurred with Java 1.4.

This problem is now fixed.

Yes, it may be the case that the shortcut is still trying to pull Java from the old install. The easiest way to fix this is to remove the shortcut and resintall TWS.

Thanks to help from Catoosa, the problem has been identified. There is a bug in Build 851.6 which prevents it from upgrading from certain previous versions. The bug will be fixed and a new build (851.7) will be posted later today.

Please zip up and send me the settings directory from before you upgraded (this is the subdirectory of c:\jts with the jumbled name) so we can diagnose the problem you encountered while upgrading. Thanks.

If you select "File/Manage Workspaces" from the main menu, you should see a workspace listed called "pre-upgrade." If you select it and click "Apply Workspace," it should restore things to the way they looked before the upgrade. Please let me know if that doesn't work.

Just make sure to backup your settings directory before upgrading. For stand-alone users, the settings directory is a subdirectory of c:\jts and has a jumbled name such as "dhingdg." To verify the name of your settings directory: run TWS, select a ticker row, and press ctrl-alt-U; a message box...

It may be the case that you have the following setting in your jts.in ifile: [communication] debug=1 If so, remove the "debug=1" line. Or, try running build 849.8 (currently in beta); starting with this build, we will ignore the debug setting. (The jts.ini file is located in either the...

Do you have any Option Trader pages open, or just regular old market data pages?

TWS Build 849 is scheduled to be promoted from beta to production for browser users tomorrow (8/10). If anyone is aware of any problems with this build that have not been fixed yet, please let me know. Thanks.

A log file of this size indicates that something is not as it should be. Could you please send me the entire log file, or at lease 100-200 repeating lines from it? Thanks.

We've successfully replicated this problem. It will be fixed in the next release of TWS (850).

This is not quite right--the setting you mention applies to limit orders. To configure stop orders to trigger outside regular trading hours, select "Configure/Order/Stop Trigger Method" from the top-level menu and check "Allow triggering outside of regular trading hours."

The extended API backfill is now released in TWS build 848 and API components release 851. In addition, there are extensive new charting features in this TWS release as well.

Actually, we're very open to this idea, but according to their web site they do not offer support (http://www.object-refinery.com/jfreechart/support.html) and there is no contact info for any of their programmers.

Can you please tell me the exact steps to take to get TWS to lock up while making a spread order so I can reproduce the problem? Thanks.

Can you please tell me the legs you were dragging in so I can attempt to reproduce the problem?