This article applies to:
E-Prime requires direct control of your machine's hardware resources to present stimuli and record responses with millisecond accuracy. We do not support running E-Prime experiments through any remote desktop software, with active screenshare software, through any compatibility layer, or within any other virtualization/emulation software.
NOTE: We have had success obtaining timing data for running E-Prime on Mac hardware through Bootcamp (TIMING: E-Prime 3.0 Mac Timing Data ). If you need to video record an experiment run, we recommend you use a splitter and send one of the video outputs to a second machine with a video capture card.
The various issues that stem from unsupported Runtime configurations manifest themselves in Runtime errors, freezing/crashing behavior, generic Windows application error messages, sound playback issues, or inaccurate timing data.
These errors most commonly point to the line of the Full Script that open the Display or Sound Device and include "Unable to open DX Target", "Unable to Obtain a Valid Refresh Rate", "No display mode supported" (when you run at a resolution and refresh rate that your display adapter does in fact support), "An error occurred while attempting to open the device", "Unable to play" (in reference to the Sound Device), etc.
Some of these configurations still allow you to develop experiments in E-Studio (see LICENSE: Virtual and remote licensing limitations ) and test run your experiment in Windowed Mode if you have E-Prime 3.0 (see E-STUDIO: Windowed Mode ). As with all of these problematic configurations, Windowed Mode itself is not supported for millisecond accuracy.
NOTE: We recommend you host all experiment files (and resource files) on your local disk drive, rather than on any external drives, e.g., a flash drive, an external hard drive, a network drive, etc. This typically helps ensure the fastest read/write times possible. If you use a network or cloud drive, you run the risk of poor network connectivity or timing issues from network interference (see TIMING: Network connection can interfere with timing ).
ERROR: Troubleshooting error 10051 
Please sign in to leave a comment.