Anybody got this beast running?
I'm trying with Kubuntu 14,10 and Wine 1,7,38 (it's a beta) with Winetricks
I installed .net 3,5 and .net 3,5 sp1 (in this particular order, the instalators get the previous .net packs they need), visual c++ libraries, VB 6 sp6 runtime, jet40, xml parsers 3, 4 and 6, rich edit controlls and wininet.
Ninja 7 installs and starts just fine, but when I try to connect to get quotes it gives errors 12017 and 12152 (MS http connected) and either a crash or just not connecting.
Platform license is free demo, quotes are free demo FXCM and free Kinetick end-of-day.
I installed internet explorer 8 and till it was running ninja connected to the FXCM server and got the instrument list. It couldn't build a chart, but it is weekend now and I think ninja couldn't work in weekends (I remember seeing a similar message some time ago when I started ninja once in the weekend, but it was a long time ago and I don't watch charts on weekends so I'm probably wrong). It didn't show any message this time and couldn't repeat the connection also.
I think the problem is somewhere in the wine dll-s responsible for the secure connection, parsing and crypting the communication with the quote server, but I can't figure out exactly what to do to fix em.
The .exe setup downloads and starts the actual msi installer without any problem.
It is also possible I have installed the win stuff in wrong order and wine is using an older version of some library.
What is also probably important - it's a 64bit linux and a 32bit wine prefix configuration, there is mono 4.5.6 package included, but the .net installers put a .net package in its place.
Without installing wininet ninja just crashes immediatly on the first try to connect, with wininet it gives a message in the log that it is connecting to ninja servers and later (sometimes at least) returns error code and 'not connected' response without crashing.
The setup.exe connects both with and without wininet.
Apparently Kubuntu is still one of the not so lucky to not want to instal msi in wine1.6.
I tried some other stuff - first installed wine1.7, then put in dotnet, visual c++ and the other things (see post #31), then ninja, then installed wine1.6. It removed wine1.7 automatically.
Ninja gave an error upon starting that it can't connect to its server to verify the license.
After that it actually started, but some of the connection options were missing - fxcm included.
Kinetick connection was there and actually worked - all the instruments, some demo sum in the account, I could build a chart with indicators, tools etc. etc. - I couldn't see anything not working.
I still think it is something in the security protocols and comunication parsing, I installed winbind and I checked samba, but it's still not happening
All works like a charm now. 13 happens in Windows as well, not really Linux issue.
I can confirm FXCM demo connecting in Wine 1.7.49 without any issues.
Davidbrooke has a thread in ninjatrader forums also, same nick.
Summary of what's needed:
1. Wine - as new as possible;
2. Winetricks - as new as possible;
3. If 64bit system - 32bit Wine prefix and 32bit versions of libxslt and isdn4k-utils;
4. .Net environments up to 3.5 sp1 - command "sh winetricks -q dotnet35sp1" should install all necessary;
5. Some additional dlls - command "sh winetricks -q gdiplus mdac27 mdac28 msftedit msxml4 msxml6 riched20 riched30 vb6run vcrun2003 vcrun2005 vcrun2008 vcrun2010 vcrun2012" should install all necessary;
1. cabextract must be installed;
2. msxml3, mdac27 and dotnet30 must be downloaded manually before running the winetricks commands
The following 2 users say Thank You to kypa for this post:
Since Wine version 1.7.51 (probably 1.7.49 or even earlier) 32-bit libxslt and isdn4k-utils (for 64-bit Linux) are not needed anymore.
The issue "Failed to retrieve processor information to build machine ID: 'ProcessorNameString' not found" is also fixed in Wine 1.7.51.
Wine guys the best!!
The following user says Thank You to kypa for this post:
Virutalbox works good, I had NinjaTrader running with live trades on my box and I had 3 instances running in virtual box for testing. It all runs smoothly together without a problem, very stable and fast.
The following 2 users say Thank You to rleplae for this post: