Keyboard, Mouse, and Chronos inputs not working

397 views
Skip to first unread message

Linda

unread,
Jul 30, 2019, 12:27:27 AM7/30/19
to E-Prime
Hello,

Well, it's been one of those days. I'm working on an experiment in 2.0 Pro. It was working perfectly last week. I have made no changes to the program. I was trying to run it again today. Same computer, same key, same experiment. I'm not having luck.

This weekend I received updates to Windows 10. My updates were: "2019-07 Cumulative Update for .NET Framework 3.5, 4.8 Windows 10 Version 1903 for x64 (KB4506991)" and "2019-06 Security Update for Adobe Flash Player for Windows 10 Version 1903 for x64-based Systems (KB4503308)"

Today I loaded up Chronos using the installation CD and following the instructions. I went to my experiment and toggled the SRBox on (checked it). The experiment worked fine with the old SR Box last week. (In case you were wondering why i unchecked the SRBox, it was because I ran it this weekend using the keyboard only and no SRBox attached.)

Now, when I run the experiment, I can use the keyboard to enter the Subject Number and hit [Enter] a couple times to get the first display up on the experiment. But, at this point, once I'm actually with a slide on the display prior to the start of the experiment sequence, I can no longer use the keyboard keys to proceed, nor the Chronos keys.

I tried running the Features Explorer program that downloaded with the Chronos install. Same thing. I get past the 'startup' popup using the keyboard, but at the Chronos introduction screen telling me to use any key to proceed, nothing works; not the keyboard, not the mouse, not Chronos.

I have never had this issue before and so hoping somebody has encountered it and knows the fix (or at least the issue).

I'm using a brand new Dell Workstation running Windows 10.

Is there an update I need or something I might be missing?

Thank you.
-Linda

Linda

unread,
Jul 30, 2019, 12:58:52 AM7/30/19
to E-Prime
Okay. It does not seem to be an issue with my Chronos install. I uninstalled Chronos and rebooted the computer. None of my previously working experiments are working now once I get past the Subject Info pop ups. I have a "Please wait for the experiment to begin." display prior to initiating the sequence. Any keyboard key used to work to continue to the experiment sequence. Nothing was changed in the devices or any other settings. No key on the keyboard works now. The keyboard is working fine, since it is recognized for the starting pop ups (e.g., subject number). I'm using it to type this email.

Any help would be appreciated.

Thank you.
-Linda

McFarlane, David

unread,
Jul 30, 2019, 10:05:25 AM7/30/19
to e-p...@googlegroups.com
Linda,

Sorry you are having more trouble. First & foremost, you should submit
this to PST Support, they should be better prepared to help you with this.

That said ...

Offhand, I suspect that the Win10 update did something to mess up your
.NET Framework 3.5 setup. .NET 3.5 is an older framework from Microsoft
that E-Prime uses for its high precision I/O once it gets started -- EP
does not use .NET for the opening screens (Subject, Session, etc.), but
.NET kicks in once EP takes over the video settings, which is where your
program starts having trouble. Windows 10 no longer enables (or
sometimes even include) .NET 3.5 by default, so whenever I install EP on
a Win10 machine I have to jump through extra hoops to manually enable or
install .NET 3.5, and I have to do that before the EP installation will
even run. I mentioned this earlier at
groups.google.com/d/topic/e-prime/Dqb3oYGoHLw .

So if it were me, I would check into the .NET 3.5 setup, maybe reinstall
or reenable that, and maybe even reinstall EP after that. In your case,
take this information to your IT folks and have them deal with the
problem. And submit this to PST Support.

Best,
-- David McFarlane

Linda

unread,
Jul 30, 2019, 3:58:53 PM7/30/19
to E-Prime
Hello again,

PST informed me that the issue is with the Windows 10 Version 1903 update (called the May Update) that just recently rolled out to users. PST is aware of the issue and working on a fix, but unsure of the date for the fix.

It seems I was just 'delayed' in getting the update, as it has been rolling out for a couple months now from Microsoft. The PSY suggested workaround is to NOT update to the Version 1903 and instead stick with the previous version.


Thank you again.
-Linda
Reply all
Reply to author
Forward
0 new messages