Glenn,
Firstly, DB locks are inevitable when you have more than one program accessing the same DB. The SQLite locking process is designed specifically to cater for this situation and others (eg where programs have multiple users), so in general terms is nothing to worry about.
SBSPopulate was built with additional processing to minimise problems in conjunction with the Kinetic Basestation programmer at the time (Will). AD uses the same logic which has proved very effective over the last 4 years.
Now the problem you reported in your first post looks very likely to be caused by a Basestation refresh (F5). Depending on how many aircraft Basestation is handling at that time, the Radar may well 'freeze' for a number of seconds. The assumption is that the program is single threading for this operation and the re-read of all its aircraft takes precedence over the screen repaints.
Now AD performs this function automatically for you to allow the display of data not available in Basestation (eg Routes). The Basestation refresh takes place while AD is in REFRESHING mode. This mode is triggered by the values you have set in your settings. If you look at Settings>>Set Display Formats>>Active, you will see an entry called Refresh Interval. This is set to 4 by default but you can change this. The number entered corresponds roughly to the number of new flights received since the last REFRESHING cycle. The lower the number, the more often the AD REFRESHING cycle and thus also the Basestation refresh occur.
The frequency with which AD thus triggers a Basestation refresh and thus an apparent Radar 'freeze' thus depends on the value you have set in the AD refresh interval AND the traffic which your SBS is receiving at the time.
One thing you shouldn't do in your situation is set the Refresh Interval to 1, especially if you are in a high traffic density area. This will force too many Basestation refreshes.
If you study the CPU (and memory usage) via your PC Task Manager, you should see that when AD is in REAL TIME mode, it chugs along at a fairly low level. This is mainly because it 'sleeps' a lot in this state. However when it is in CATCHING UP mode, usage will spike because it is doing a lot of intensive work and I/O. The same applies at startup where you probably notice a delay after you click start. At this point it is also working very hard, but that is what computers are for
Reading further through the thread it would appear you also have PC memory constraints if you keep getting those messages. I would increase your virtual memory initially but also take a close look at your memory usage. You may well benefit from adding some real memory. This will probably speed up all your PC operations if only because you won't need so much virtual memory for 'swapping'.
Absorb the above and see if your experiences match.
Gary