x64 eSignal

[gomifromparis]

Hi,

eSignal connectivity doesn't work on x64 NT.

Is this currently in progress, or is it a good occasion to switch to another data feed ? Could you list which ones you support ?

Thanks

[NinjaTrader_Ray]

Correct, eSignal API is not native 64-bit.

Here is a list of providers.

http://www.ninjatrader.com/webnew/trading_software_brokers_data.htm

I believe at this time, BarChart maybe the only real-time market data vendor that runs natively in 64-bit.

[gomifromparis]

Hi,

My question is not "which providers run natively in 64 bits".
Question is "which providers work with NT7 x64".

For example, IB is not native x64, but it will work in NT7 x64 because it uses TCP/IP as a middleware.

So can you please list which data feed WORKS with NT7 x64 ?

Thanks

Correct, eSignal API is not native 64-bit.

Here is a list of providers.

http://www.ninjatrader.com/webnew/trading_software_brokers_data.htm

I believe at this time, BarChart maybe the only real-time market data vendor that runs natively in 64-bit.

[NinjaTrader_Ray]

Sorry for the misunderstanding. I will have to get back to you sometime next week on this.

[gomifromparis]

OK thanks.

[hawks67]

Correct, eSignal API is not native 64-bit.

Here is a list of providers.

http://www.ninjatrader.com/webnew/trading_software_brokers_data.htm

I believe at this time, BarChart maybe the only real-time market data vendor that runs natively in 64-bit.

I apologize for being severely clueless here, but if Win7 Professional 64-bit can recognize 32-bit apps like NT6.5 and run them as 32-bit apps, why can't it run the 32-bit eSignal Data Manager in 32-bit as well, so that NT and eSignal data are happily working together in the 32-bit "sub-architecture" inside Win7 64? I know this is essentially a Windows/Microsoft question, but I figured I'd throw it out there to you Ninja wizards...

Thanks in advance!

[gomifromparis]

You can run Ninja 7 32 bit with eSignal 32 bit on Windows 7 x64 using the 32 bit sub system.

But to use Ninja 64 bit requires a 64 bit data provider. From what I understand only barchart offers it. You can also use IB which provides an IP gateway so is platform-independant.

[piersh]

on x64 windows you can have two types of processes: 32-bit & 64-bit. 32-bit processes can only load & run 32-bit code, 64-bit processes can only load and run 64-bit code. so even though windows supports both 32-bit & 64-bit running simultaneously, it doesn't support running both in the same process.

so... when NT7 is running as a 64-bit process it can only load .DLLs that support 64-bit (either compiled with a 64-bit compiler, or .NET DLLs marked as 64-bit compatible, or .NET DLLs obfuscated with a 64-bit obfuscation tool). it cannot run 32-bit DLLs such as the eSignal connection support. the reason IB works is that the 32-bit IB code runs in a separate (32-bit) process and the communication between NT7 and IB is over a network channel which is unaware of the 32/64-bit difference.

[NinjaTrader_Dierk]

@piersh: Your explanation is correct. Thanks

[jupiejupe]

"the reason IB works is that the 32-bit IB code runs in a separate (32-bit) process and the communication between NT7 and IB is over a network channel which is unaware of the 32/64-bit difference."

this should than be very same process in which nt7 communicates with esignal, it does not take i hack to figure this out.

it is far more important that nt7 works than how it get the job done, so far i am very depressed with what i was hoping would be a fix to some of the lack of insight in nt6.5.

[NinjaTrader_Dierk]

Incorrect. eSignal provided a 32bit API which needed to be accessed by a 32bit process, whereas IB TWS communicates by sockets which could be accessed by either 32bit or 63bit apps.