Millisecond Forums

I am getting the following error message when I attempt to run my script:

Stimulustimes: Event number must be greater than 0

I have not seen this error message before and I cannot figure out what the problem is... Here is an example of my trial code:

<trial 001EmSm>

/validresponse = ("1", "2")

/trialcode = "SEmSm"

/pretrialpause  = 500

/postrialpause = 500

/stimulustimes = [0=001; 1000=this; 1500=person; 2000=is; 3000=honest, S_EmSm; 4500=answer]

</trial>

NOTE: the S_EmSm at 3000 is an EEG trigger with the following code:

<port S_EmSm>

/port = LPT2

/subport = data

/items = ("00000001")

</port>

If you change

/stimulustimes = [0=001; 1000=this; 1500=person; 2000=is; 3000=honest, S_EmSm; 4500=answer]

to

/stimulustimes = [1=001; 1000=this; 1500=person; 2000=is; 3000=honest, S_EmSm; 4500=answer]

the error message should go away. I remember Inquisit once accepted stimulustimes starting with zero, but that just isn't the case anymore.

~Dave

Error message remains -- I originally had it as "1" but then changed it to "0" when the message came up (but, just to test, I changed it back and tried to run it) -- same message.

Hmm, odd. It's just a hunch, but I'd suggest you  change the name of the '001' stimulus (whatever it is) to something starting with a letter (e.g. STIM001):

/stimulustimes = [1=STIM001; 1000=this; 1500=person; 2000=is; 3000=honest, S_EmSm; 4500=answer]

Didn't care for that either... changed the stimuli to P001 -> P040

I deleted the EEG trigger (thought that perhaps that was an issue), but the same message comes up...

I should also say that this program ran previously, but I have replaced the computer that it was running on (transfered the license to the new one)... The new computer is a presentation computer only and has basically been wiped clean of anything other than Windows XP, Inquisit 2, and E-Prime. Might there be some software that was cleared off that is causing the problem?

It's all good --- was missing a Windows component. Is now installed and running fine.

Thanks for the follow up. In case others run into this, what was the missing component?

-Sean