Yesterday the startup time of the PicoScope 6 program got annoying, while I was showing some pre recorded samples to my colleges.
So today I decided to measure the start-uptime without the USB scope connected.
It took about 30 seconds before the main screen appeared, the splash screen was there immediately.
Then I compared the startup time in a Clean Virtual windows machine and it was only 2 or 3 seconds.
Already tried complete reinstall of the PicoScope program, but that did not solve the problem.
6 different references to the USB scope (I have attached a registry dump of this part in a .rar file)
Windows wont let me remove these entry's so I can not test what the effect is if I remove these entry's
I let task manager dump the memory of picoscope6.8.10 during startup
All this time the PicoScope process uses 100% CPU.
The 4 memory dump files are in a single RAR file.
Hitesh wrote:When you try to run PicoScope 6 on the Host Windows 7 PC is virtualbox shut down and has it relinquished access to the USB ports?
Yes it is shut down.
Hitesh wrote:What is the startup time on the Host PC when a device is connected?
With 4424 connected the startup time is 6 seconds.
With no device connected the startup time is 23 seconds.
Also double clicking on a .psdata file it takes 23 seconds before the main screen appears.
Upgrading to 6.8.10.13 and removing the beta version reduced the 30 sec to 23 seconds.
Witch is still a lot of time compared to the start uptime in the virtual box.
in the virtual box (win XP) startup times
no scope connected 6 sec
4424 scope connected 9 sec
Any progress on this item.
It seems the time between ApplicationInfo and TestMenu is the bottle neck in this case.
There is almost 17 seconds of nothing (waiting for some thing ?)
Settings file version - 11.1.0Preferences file version - 2.0.0Probes file version - 1.0.0Data file binary header version - 1RemovingNo test menu file foundCreatingDone CreateSplash screen closed after 21552,2327ms