Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
mattz - that is just my opinion. nt7 is far from perfect as other platforms are. there is no perfect one. however nt7 is really unstable and has a lot of problems and therefore you nedd a customer service. here we are getting to the point - their sucks! you are waiting and waiting and after that you get a general answers like "reinstall ninjatrader, reinstall operating system, buy a new computer". there is a competiton and i had a chance to compare customer service from others (linnsoft, sierra chart, multicharts, etc.). it is simply not to compare!
someone has mentioned old telecom cs. it is really like that. maybe you get a better service from them as a broker, but most of us do not.
therefore, that really sucks!
rani
Can you help answer these questions from other members on NexusFi?
i know it is offtopic (sorry mike), but i really have to highlight cs from linnsoft (investor r/t). it is something needed to be experienced. not only they perfectly understand their software and therefore can give you exact anwer, their response time is like in minutes. not only they always help, they usually do it for you (i.e. code the custom indicator). even in case the mistake on your side, they still help (not make you an idiot). especially their chad payne is a master! i think it is a smaller operation than nt (probably with smaller user base), but nt cs should get some serious training from them
I am sorry for this experience. It is is our company policy that if someone requests a call or a remote login that we accommodate our customer immediately. I have no excuse as to why this did not happen and I will take immediate action to work to resolve your issue and follow up with Kyle to understand why the ball was dropped so it will never happen again.
If you could private message me your ticket #, I will have this reassigned immediately to another tech.
This is not accurate. We have 20+ people in our customer service facing roles that all provide technical support at varying levels and have different competencies including level II support for escalation. You say that this issue should have been resolve in a few hours and I disagree...It should have been resolved in minutes. That is our goal, to resolve issues in minutes and most of the time, that is the case.
Several years back when the US changed its Day Light Savings policy, XP came out with a patch to address this issue. Just hitting some bushes here....but are you up to date on XP patches? I just checked our support queue and could not find anyone else reporting this same issue yesterday or today.
I have researched this further and the issue is localized to your PC. The problem is that as NT loads historical data, the time zone conversion is not correct since your PC is not taking into account the recent change in day light savings. This is either since your PC is not up to date with the correct XP patch that addresses this problem OR maybe there is some windows setting in XP? I am not sure about the latter but I will forward to my IT manager and ask him to research the correct patch and if there are any user settings that can be tweaked.
First Thanks for taking the time to answer my post, this should not be the right modus operandi, but apparently futures.io (formerly BMT) is bringing problems on the surface. I do trust you have 20+ people in your CS but my thoughts are based on facts, latest my ticket 444316 which is still unsolved and not understood by the receiver, comunication and problem solving with your customers remain main issues.
After further research, it appears that the problem is that you don't have the correct patch that deals with the DST conversion. This is based on the information provided in your trace file.
Your best bet is to run Windows Update but what is important is that you install Service Pack 3 (you are currently on Service Pack 2) and this patch that address the DST issue for 2011 - Download details: Update for Windows XP (KB2443685).
