Manual stim while recording causes NR to crash

[GoogleCodeExporter]

What steps will reproduce the problem?
1. While recording, start the manual stim with whatever parameters you're 
interested in.
2. No output results. Then try to stop the manual stim, which will cause NR to 
freeze and crash.
3. Note this doesn't happen if you start manual stim first, and THEN start the 
recording.

What is the expected output? What do you see instead?
Expected output is stimulation pulses from the DAQ, and the whole not crashing 
thing.

What version of the product are you using? On what operating system?
v0.7 (Riley's installer), Vista

Please provide any additional information below.
Jon mentioned it might have something to do with the clock and timing.
Potentially important: after the crash, it takes a few minutes before manual 
stim can be used again. Else it causes another crash.

Original issue reported on code.google.com by nlaxpat....@gmail.com on 15 Dec 2011 at 9:16

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Note, testing revealed that the open-loop experiment section works fine with 
predefined  stimulation files.

Original comment by nlaxpat....@gmail.com on 19 Dec 2011 at 5:35

[GoogleCodeExporter]

I just tried something very similar- namely, doing a raw recording, and then 
turning on manual stimulation during the raw recording.  Stimulation and 
recording proceeded as desired.  
the following info might be helpful:
hardware settings
approximately how taxed is your CPU when you are doing this
do you see the same behavior after a system reboot, with no other applications 
running?

Original comment by RZellerT...@gmail.com on 20 Dec 2011 at 3:29

[GoogleCodeExporter]

CPU is not taxed at all, and the behavior occurs after a system reboot. How 
long after starting NR did you start the recording and manual stimulation? I 
believe there is some sort of time delay from the start of the program that is 
responsible. If I wait long enough (on the order of a few minutes it seems) it 
proceeds normally with stim alone. Haven't gotten stim and recording to work if 
the latter is started first.

Original comment by nlaxpat....@gmail.com on 20 Dec 2011 at 4:13

[GoogleCodeExporter]

This issue is confirmed. 

It is occurring due to a conflicts between the impedance measurement daq and 
the stim daq. Because impedance measurement does not have a yes/no option, just 
a card to choose, it is taking resources that are needed by the stim daq.

Need to make impedance measurement a yes/no option and check to make sure user 
has not overbooked the impedance measurement or stim daq before committing 
settings

Original comment by jonathan...@gmail.com on 23 Jan 2012 at 9:36

[GoogleCodeExporter]

This issue should be resolved in the latest installer. Neal, please test and 
report if possible.

Original comment by jonathan...@gmail.com on 5 Apr 2012 at 5:04

[GoogleCodeExporter]

Neal, I am awaiting a response to close this issue. Please try the new 
installer and report your findings. Thanks!

Original comment by jonathan...@gmail.com on 21 Apr 2012 at 7:49