[DMDX] interrupt device didn't work! Hi,   I am a new user of DMDX. I learned to write the script file and corrected most of the errors by referring to the postings on the ListServ and the DMDX Help. However, when I tested myself (using a Compaq Presario 2800 laptop), I found the mice (both touchpad and USB) didn't work. The mice work in all other conditions but they seem to go to sleep when I run the experiment. The strange thing is the SpaceBar works. When all means failed, I tried to map the Shift buttons on the keyboard, instead of using a mouse. But they didn't work either. It appears that only the SpaceBar works.    I am not sure if it's caused by any mistakes I made in the script.  The laptop I use is one with some button names in Chinese. I found out the button names by doing the input test in the TimeDX. The number (#0, #1, #2) of the two input devices' buttons was not found on input devices when I ran a syntax check.    Here is part of my script.                     0 "Press SPACEBAR to start."; +1  / *   "sun" /  "sun" /  / ;  -2  / *   "lip"/  "book" /  / ;  -3  / *   "banana"/  "apple" /  / ; +4  / *   "ice cream"/  "ice cream" /  /;  .... ....   I suspect something might have gone wrong so I ran the diagnostics. Here's the info I've got.  .... .... EXPERIMENT READY 24 video memory buffers at 800x600 16 bpp Preparation A 48.63ms, B 0.00ms 0 "Press SPACEBAR to start."; Display error at msec 544.36, tick 32 in item 0, frame "Press SPACEBAR to start." moved into video memory 12 ticks late (previous frame's duration will have been longer) -- possibly caused by another process taking 1 tick Preparation A 0.18ms, B 3.26ms +1   "sun" / *  "sun" /!  /; DQ adjusted by 1 ticks to allow for sound Item  1 RT -7000.00 -- Error Rate 100% Preparation A 235.44ms, B 97.73ms -2   "lip" / *  "book" /!  /; DQ adjusted by 1 ticks to allow for sound Item  2 RT -7000.00 -- Error Rate 100% Display error at msec 21590.50, tick 1317 in item 2, frame "book" moved into video memory 250 ticks late (previous frame's duration will have been longer) -- possibly caused by another process taking 5 ticks Preparation A 310.88ms, B 129.13ms -3   "banana" / *  "apple" /!  /; DQ adjusted by 1 ticks to allow for sound Item  3 RT -7000.00 -- Error Rate 100% Display error at msec 29072.37, tick 1772 in item 3, frame "apple" moved into video memory 250 ticks late (previous frame's duration will have been longer) -- possibly caused by another process taking 5 ticks ... ...   I noticed that both the display error and tick increased as the experiment went on. But the number of ticks-late when a frame moved into video memory was ranged between 234 and 251.    Later I changed the header parameters to                    thinking that it might help. But it didn't. The result of running a diagnostics is about the same as mentioned above. Could anyone tell me what to do? Thanks a lot.     Cheers, Daphne 		 --------------------------------- Yahoo! Messenger  NEW - crystal clear PC to PC calling worldwide with voicemail