Regarding MikeC earlier post.
RadarBox can happily run on low end machines without out the network. We have a machines in London which are only P4 2Ghz which is 5 years + old and it can happily pick up 200 miles around London Traffic with any issue.
You have mentioned sharing, sharing does not affect the cpu cycles, it is only 2% of the process that RB requires. Anyone spreading such information that this is causing an issue is totally wrong and a myth. We will come down harshly on those who continue to suggest this as we suspect its being done to cause damage to RadarBox.
Turning on the network, means every 20/30 seconds, the software now has to process 800+ extra flights very quickly. Of course this put pressure on any system.
RadarBox software is different to other software in terms of it depends on various conditions, such as the amount of traffic your receiving, what options you have turned, your database size etc..
RadarBox has been run on very low end machines (500mhz less) used just for data purposes and its works very well.
Going back to the point of this thread we have over 3000 customers now and most have used the network. If there was such a serious issue it would have caught by now and mentioned a lot but the reality is that isn't the case.
In Viking9 case, we can only point at whether other software was running in the background causing RB to slow down or whether its just different weather has improved reception lately since his network expired. We have done extensive tests indoor and our beta team and we never found the network having any degradation of local flights being picked up.