Search results

Yes Linux and all modern Unices (Solaris, AIX etc) support multiple CPUs and have done so for quite a few years.

Yes I believe that is the case. Somewhere in a subdirectory under IBJts there are files called settings.*.xml where * is a day of the week. Not sure where it is on windows, as I use Linux.

I think you will find the settings are saved on the local machine. The browser and stand alone TWS are basically the same thing.

Actually I think it's BSD with a micro kernel not Linux. rsync should work. It's a very good piece of software from the key Samba developer. I think you can run rsync on windows, possibly via cygwin.

The spread on the euro is normally 1 pip. Attached is the market depth from IB book trader.

Don't know. However I do know that the Globex currency futures have months of backfill available. Depends on expiry of course.

My software. The historical data request in the API was changed in the latest release to support this functionality. Any software vendor should be able to support this.

This is not correct. An application can make repeated requests for historical data, specifying the end date in each request. Total of six months max is available. If software vendors are not supporting this you should get on their case.

The release notes for the API say six months. I have tried over three months of one minute bars and it works as stated.

Interactive Brokers has Eurex and also streaming data feed and 6 months historical data for charts.

I should qualify what I said about stops on IB servers. This is the case if you use TWS for order entry. Of course third party applications using the API can do what they please, but it would be pretty stupid for an application to replicate on the PC functionality that is provided by order types...

If you are using IB, stops are held on their servers and not on your PC for exchanges that do not have native stops ie most exchanges.

In fact many Java applications are multithreaded and TWS certainly is - just look in the log file. The only catch is that all updates to the screen in Java/Swing applications such as TWS are (or should be) done by a single thread - the AWT thread. If this one thread is consuming most of the CPU...

Probably not. One thing you could do to check the performance of the client side (computer router/modem combination) is to ping or traceroute your ISP ie a mail server or time server at the ISP. On my machine I get about .5 msec to the router/modem, about 10 msec from modem to first external...

Unfortunately this isn't going to be of much use. A screenshot of a 17" CRT at 1280x1024 will look exactly the same as that of a 19" LCD at 1280x1024. Only the resolution and colour depth matters in a screenshot, not the monitor size or type.

I'm having no problem with API orders.

Please update the online API documentation. The documented error code list in particular is out of date. A comprehensive list of error codes is very important to developers trying to produce robust applications using the API. Here is one example that needs to be fixed immediately. Not only is...

I have two identical model 19" flat screens. One DVI from Matrox G200 MMS, one VGA from Nvidia MX4000. I can see no difference whatsoever. Some claim that DVI is superior on 1600x1200 and higher screens.

Actually XEN is from University of Cambridge http://www.cl.cam.ac.uk/Research/SRG/netos/xen/ Apparently new CPUs from Intel and AMD will have better support for virtualization, so possibly XEN might also support Windows as well as Linux, BSD and Plan 9 in the not too distant future.

Actually my XP box has been turned off for a couple of months. Hopefully it will stay that way. As for what I have used in the past Win 3.1, Win 98, NT, 2000, XP, DEC Unix, AIX, SCO Open Server, SCO Unixware, Solaris, HP Unix, Linux, CP/M, CP/M-86, MS-DOS, RSTS and some mainframe and...