I have not been using PicoScope for a year or so. In the mean while I got a new laptop with 64-bit Windows 7. But now I can hardly use PicoScope 6. From the Help, About PicoScope 6 menu:
Model: PicoScope 5204
Serial Number: QJY29/60
USB Version: 2.0
Calibration Date: donderdag 19 juli 2007
Hardware Version: 1
Driver Version: 1.4.2.80
The problem is that the scope traces do not start again after I change e.g. the vertical scale or change the trigger or start capturing after stop capturing. The user interface seems to continue to respond, but no traces appear.
When I remove the power of the scope, a window pops up ("check USB and power cables..."). After powering again, the scope reacts: the fan starts and some relays click, but no traces. I cannot close the program normally, I get a message "PicoScope not responding". After a restart, within a few clicks the traces disappear again. Looks like the software is waiting for the 5204 to respond.
Unfortunately, I cannot find a 100% reproducible erratic behavior...
I also experienced similar trouble with running PicoScope 6.5.78 even in the Demo mode. So I made try-and-error to find out the cause of trouble by using PCs in my Lab. The results was as follows;
Worked Fine: ThinkPad X201i, X61 Tablet, X60 Tablet, and Lenovo Edge 13 running Win7 Pro 64bits. EeePC901X running WinXP Pro 32bits.
"Not Responding" eroor appeared; ThinkPad X31 and X41 running Win7 Pro 32bits, X100e running Win7 Pro 64bits.
First, I assumed that the trouble comes with the graphics card, but above results denied this assumption. What was the difference through these systems? I think it may be attributed to the CPU core. PCs using Pentium-M and AMD Athlon Neo MV-40 had trouble. Is it due to the CPU power or single core? Can you fix the problem?