If you still did not check, NT forum is a good source about 32 vs 64 bit environment discussions. Personally I detected slightly less crashes with 64 bit during fast mkt but I'd not consider it reliable in every circumstances. Also I'm not so sure that multitastking features are really used with multicore CPUs aside when backtesting.
Kinetick (www.kinetick.com) does support 64-bit and is less expensive than eSignal. I suggest seeing if Kinetick could replace eSignal. Otherwise, you will have to just testing your systems to see where the memory limitations will be on 32-bit.
So they do. I didn't realize that. Not a bad price either. The reason I wanted to use the esignal feed with ninja 64 bit is because I wanted to be able to continue to run my EFS strategies in esignal while I ported, debugged and tested my code for ninja running both charting programs side by side. I imagine this process would take me a couple of months. I still should be able to do this running ninja 32 bit, but their is a chance i will run into memory problems. My scripts cache a lot of tick data so this is a real issue for me. But after I have ported my code, it would make sense to switch to a ninja 64 bit with the kenetic feed. Thanks for the suggestion. Runningbear