[Ham-Computers] TSR Order

[Duane Fischer, W8DBF]

For the primary benefit of Phil Atchley, but others as well. The order in which
TSR (terminate and stay resident) routines are loaded into the system memory,
can cause all sorts of conflicts. Because not all programs are executing at boot
up, some of these conflicts may not surface until a particular program is
executed. 	
	
Sometimes if one is able to identify the proper tsr, it can be moved to a
different order of loading. This may, or may not, remedy the conflict. Many
times it does.	
	
The notion that all programs work on all computers, just because the
manufacturer says they will, is pure marketing hype, not reality. They are in
too big of a rush to get them to market to bother to properly debug their own
software, let alone test it for compatability with other programs. 	
	
Many times when a program is supposedly uninstalled, fragments remain on the
system. These often times cause conflicts too. But again, it takes a particular
set of conditions to cause the conflict to surface! 	
	
In some cases, the virus program is configured by the user to scan specific
files at specific times during routine operation, this can cause the locking up
when the right set of conditions exist. I believe the user is better off to scan
only for major problems on boot up and when downloading attachments or from web
sites, and manually scan the reast as needed. Too much of the computer doing
these pre-set functions is often the cause of the conflict. Wrong thing at wrong
time.	
	
Duane Fischer, W8DBF