|
#1
|
||||
|
||||
|
autorun.exe CPU utilisation and delay
Just for your interest, this issue occured a couple of weeks ago with APMS5 V5.5.6 I recall.
With v5.5.10 up until today, all seemed fine. When starting auotrun.exe in a revised project, there is a significant delay at startup time. The installer interface doesn't appear immediately, and the area prior to it's appearing appears active but invisible. It hasn't always been like that, and I'm not sure what's causing it. I tried to replicate it when this occurred a couple weeks ago, but couldn't. (I am not using transitions). Today, after replacing the *.btn files, the startup time is significantly slower with a CPU utilisation of around 50% Is this to be expected as a project develops? I've attached a screen capture of the project, and highlighted in red the corresponding TaskManager graph on this P4 3Ghz 2048Mb DDR machine. Any ideas? Need more info? Regards, John |
|
#2
|
||||
|
||||
|
Further info
Some scenarios are difficult to nail.
I can now run the app without any delay. Now I haven't done anything different, no reboot, nothing. I had experienced the same delay problem running the app across the network from another PC. However, half an hour later, it's running fine. Now, I can't replicate the delay. So it might be one of those strange glitches. (Last time I experienced this issue, I had burned the app to CD, and the problem existed on every computer I tested it on. But, I've now lost the CD - must have walked out in a customer's machine). Have a great weekend, and a happy release of V5. I'm sure there'll be a few beers going around. Cheers, John |
![]() |
«
Previous Thread
|
Next Thread
»
| Thread Tools | |
| Display Modes | |
|
|
All times are GMT -6. The time now is 06:47 AM.








Linear Mode
