I got the dxdiag.txt file. I am not sure if it will provide any info
I got the dxdiag.txt file. I am not sure if it will provide any info
The dxdiag.txt file indicates you are still running Vista on this machine. Is this the one that was supposed to have been converted back to XP? If not, do you have that one for comparison?
Actually, that dxdiag.txt file is from a Vista desktop machine. The laptop computer that had vista and was rebuilt with XP and was giving us problems, has since been rebuilt again back with Vista. Is everyone who is running medialab on Vista computers having this same problem? or is it just a few people?
Well at least that makes sense--I had never heard of anything like this on XP. We are working on a fix for this for Vista. In the mean time, all I can suggest is to either run it on XP or split the experiment as described above. As of this time I do not know the extent to which this is happening across Vista machines. I can at least say we have had many more requests for Vista authorization codes that we have had reports of this problem. But then that may simply be due to the fact that most experiments maybe be shorter than 150 items, or that the problem is not be reported by most users.
Another count for the Vista problem.
As described above. It seems to be happening in longer experiments (100+ trials). And yes, dividing the experiment into two or more smaller ones (with a restart of medialab) seems to help. Also, running on an XP machine avoids the whole problem. However, we've purchased a dozen laptops with vista to run subjects, and we can't reliably use them.
Any updates or news on this issue would be greatly appreciated
Bonus information:
Running all the medialab software (and Excel) in Windows XP (SP2) compatibility mode does not solve the problem.
I am having the exact same problem. Please let me know when there is a salution to this problem.