I normally trade via a windows NT machine with no problems. Am currently on vacation trading from relative's XP Home version. When I cancel an alarm the system freezes. Any similar experiences? I'm planning to upgrade my NT to 2000 Pro when I return. Any similar problems out there? TIA
Others (including me) have seen this problem too. Unfortunately, it seems difficult to reproduce, so it isn't getting fixed.
I've seen it on NT4 and Win2K, but quite some time ago. I've seen others complain about it periodically. It doesn't come up for me any more because I just don't use the alarms.
Forget it, I don't think they will ever fix it. I've had "freezing" problems with those alarms on 98SE, ME, XP. Just don't use them.
yep.. just don't use them. code your own alarms, or use another data provider on the side for that. nothing like the feeling you want to crash your monitor when TWS dies with 10 orders active because a stupid alarm triggered.
FWIW, I'll pass this info to our programming guys and hopefully they'll take a look. The problem with these kinds of issues is that they need to replicate it in order to solve it. Since it doesn't seem to be occuring for the vast majority of people, they may have trouble trapping it.
Maybe we can look at it from a different angle. People who are using TWS alarms: please post your system configuration (video card/driver version, OS, java version, sound card/driver version). It might be helpful to know from IB exactly how the sounds are triggered. Which API and what params are being used in the call? I do know that my sound files do not sound the same when fired by TWS compared to when they are played otherwise.