Buffalo![]() Elite ![]() ![]() Posts: 603 Joined: 7/11/2007 Location: Braintree, MA ![]() | http://www.omnitrader.com/omnitrader/proforum/thread-view.asp?threadid=1140&start=26&posts=36 Matt Having problems with new userinterface script, so I had to put old one back to get OT to stop crashing, but now I am back to square one - using OP-EOD trader under Interval trading My trades DO NOT GET SUBMITTED to broker. They "are ready for batch submission" (that's the email OP sends me every hour from 9AM till I shut OP down at 6pm) but that is all that happens, all day long. ***This is still an open issue*** Did you test the new scripts, esp the userinterface one? Waited till the weekend to test them. Doing nothing else to OT - OT was running just fine when I shut it down Fri night, I tried the new OP scripts to see if the modTWS would work. Not only did the scripts not work (TWS didn't come up and OT didn't load) but several of my databases got corrupted as I tried to get it working. OT.otd, symbol.mdb and brokerage.otd generated error messages that they were in a format OT didn't recognize. I replaced them with old versions and was able to get OT back. Replaced userinterface script with old version to get OP back. BTW something else that was going on with the computer as I had these OP/TWS/OT issues is some file/files/memory/?? kept balloning up until a low-space warning was issued by windows. When I started testing the new OP scripts the C drive had over 10 GB free on 60 GB drive (ok it's an older computer that's why drive is so small). But as these OP script tests were ran I got low space warnings and C was down to 80mb. I couldn't find the offending file(s) and windows XP makes it difficult to do anything with no free space. restarting the computer was the only way to fix. This happened several times, along with the database errors I was getting. Once I replaced the userinterface.txt, symbols.mdb, brokerage.otd and ot.otd with old versions everything seemes to work ok now |