ilia ivanov wrote: > Hi Andrew, > > If I double click I see the Python console to show up for a sec and then > nothing. This is the reason to write the code in the console mode, so I > can track the point at which I get an error. So far I`m stacked at the > > import _vegl >> Traceback (most recent call last): >> File "<stdin>", line 1, in <module> >> ImportError: No module named _vegl > > Does this mean that the VisionEgg is incompatible with win32? VE is compatible with win32. If you're getting an error on double click it means something is going wrong. You can try one of two things: 1) keep that error around longer. Open a shell console: Start->Run->type "cmd.exe". Then "cd C:\Where\the\VE\demos\are". Then "python multi_stim.py". 2) Run the demos from within the Python console: type "os.chdir(r'C:\path\to\VE\demos')" then type "execfile('multi_stim.py')" when in the VE demos directory and report back the error you see. The problem you're encountering is that _vegl is an internal module to the VisionEgg and you shouldn't import it directly. How did you install the Vision Egg? -- Dr. Andrew D. Straw California Institute of Technology http://www.its.caltech.edu/~astraw/ ====================================== The Vision Egg mailing list Archives: //www.freelists.org/archives/visionegg Website: http://www.visionegg.org/mailinglist.html