WinWarbler slow start
|
This is a follow-up to another thread ("WinWarbler callbook lookup issue") but about a different problem: WinWarbler's slow startup (sometimes as long as two minutes). In the previous thread Dave AA6YQ (post 212477) advised configuring anti-malware to cure the slow start. This didn't cure WinWarbler's slow start.
I don't use any anti-malware except for Microsoft Defender, it's definitions are up-to-date and I've defined the DXLab folder as an exclusion in Defender. There are no quarantined items. I've tried disabling all startup applications, including Launcher. None of these cured the slow start.
But, after much experimentation, what I've discovered is that WinWarbler starts promptly (between 3 and 6 seconds) when I open it first by clicking either on its .exe file in the WinWarbler folder or, if Launcher is running, by clicking on its button in Launcher's panel. But when I click on "Start" in the Launcher and all the programs start in sequence, WinWarbler (the last one) takes between 1' 30" and 2 minutes to start. If I start only SpotCollector first, and then start WinWarbler, it takes WinWarbler about 15 to 20 seconds to start.
So starting the programs separately takes much less time than using Launcher's "Start" button to start the whole sequence.
As I described in the earlier thread, when I run the computer in safe mode with networking, except for an error message about port problems, Launcher's "Start" button launches all programs fairly quickly. I haven't been able to discover how to achieve the same result in normal mode.
Any help will be much appreciated! Thank you!
--Daniel W9DGI |
|
|
|
Dave AA6YQ
+ AA6YQ comments below
+ The implication of your report is that WinWarbler only starts slowly when your system is busy starting the other DXLab applications that the Launcher started as your direction. Use the Windows Task Manager to monitor CPU consumption and memory utilization while directing the Launcher to start all of your DXLab applications; perhaps that will reveal the bottleneck. + SpotCollector can be consumptive of both memory and CPU resources; take a look at https://www.dxlabsuite.com/dxlabwiki/OptimizeSCPerformance + Before each update of a DXLab application, that application is sent to Microsoft Security, which checks for malware, and then updates the Windows Defender definitions to indicate that the application is "safe". Be sure you have updated to their current definitions: https://www.microsoft.com/en-us/wdsi/definitions 73,
|
|
|
|
w6de
You need to check all the programs installed on your computer! For this purpose, I use Glary Soft Absolute Uninstaller. Microsoft Windows provides an uninstaller, but I do not trust it to remove all remnants of a program and to show all the Microsoft garbage I don’t want on my computer.
I have found that several Performance Monitoring applications I previously installed on my computer caused a slow down of some DXLab applications. Specifically, Apps monitoring graphics card performance and CPU performance. My recommendation is to check all the programs installed on your computer and delete programs YOU have specifically installed and no longer use. For all programs you don’t recognize, run a web search to see if deleting it is OK. There will be a lot of Microsoft programs listed, be extra cautious about deleting them—any doubt leave them alone. Note: installing some applications also install additional programs that you may not want. I run a program check at least once a year to check and eliminate unwanted programs.
Use caution in this process, this process is only for the computer literate. As I comment above—do not remove unknown programs without a web search to see if you can/should remove the program/application.
73, Dave, w6de
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of
Daniel W9DGI via groups.io
Sent: 27 January, 2023 19:02 To: DXLab@groups.io Subject: [DXLab] WinWarbler slow start
This is a follow-up to another thread ("WinWarbler callbook lookup issue") but about a different problem: WinWarbler's slow startup (sometimes as long as two minutes). In the previous thread Dave AA6YQ (post 212477) advised configuring anti-malware to cure the slow start. This didn't cure WinWarbler's slow start.
I don't use any anti-malware except for Microsoft Defender, it's definitions are up-to-date and I've defined the DXLab folder as an exclusion in Defender. There are no quarantined items. I've tried disabling all startup applications, including Launcher. None of these cured the slow start.
But, after much experimentation, what I've discovered is that WinWarbler starts promptly (between 3 and 6 seconds) when I open it first by clicking either on its .exe file in the WinWarbler folder or, if Launcher is running, by clicking on its button in Launcher's panel. But when I click on "Start" in the Launcher and all the programs start in sequence, WinWarbler (the last one) takes between 1' 30" and 2 minutes to start. If I start only SpotCollector first, and then start WinWarbler, it takes WinWarbler about 15 to 20 seconds to start.
So starting the programs separately takes much less time than using Launcher's "Start" button to start the whole sequence.
As I described in the earlier thread, when I run the computer in safe mode with networking, except for an error message about port problems, Launcher's "Start" button launches all programs fairly quickly. I haven't been able to discover how to achieve the same result in normal mode.
Any help will be much appreciated! Thank you!
--Daniel W9DGI |
|
|
|
Thanks again, Dave, for your helpful suggestions. Looking at Task Manager showed only DXLab programs with significant activity during startup. So I went into the configurations for SpotCollector and checked "clear database on startup." That did it. WinWarbler now starts quickly.
73 Daniel W9DGI |
|
|
|
Dave AA6YQ
+ AA6YQ comments below
Thanks again, Dave, for your helpful suggestions. Looking at Task Manager showed only DXLab programs with significant activity during startup. So I went into the configurations for SpotCollector and checked "clear database on startup." That did it. WinWarbler now starts quickly. + This article explains how to configure SpotCollector to maintain the Spot Database at a size that you have the computing resources to support: https://www.dxlabsuite.com/dxlabwiki/OptimizeSCPerformance 73, Dave, AA6YQ |
|
|