Memory probs and sloth. Is it a TSR?

I tried Fences a longish time ago. I removed it very shortly after installation because my machine slowed down noticeably (XP). I also noticed that when I changed things in Fences there was no Save subsequently offered (to a Config file, for example). This can only mean that Fences is always current, always polling the mouse and keyboard to see what is changed. Nothing nasty, but this program type loads and stays in memory - always watching the system - just like an anti-virus or anti-adware program will do, and so they take up memory and resources. Anti-virus progs are important, Fences is just a facility.

I may have this wrong. But the difference in system speeds from not installed to installed and then uninstalled were very noticeable. If I am wrong here, then an explanation for the very noticeable slowdown following installation is required.

Am I right in thinking that Fences behaves in this way, and continually polls the system? If so, perhaps a change of approach. Accept input, then save to a config file, stop the the polling, and all will be well.

Fences is a nice idea and well executed, but it must not install and remain in memory - constantly monitoring the system. Windows has supplied us with enough "Services" continually running in the background taking up resources already, we need no more.

 

 

 

 

 

 

4,861 views 6 replies
Reply #1 Top

It might help if you posted your System Information. I have fences on systems from XP to Win7 and have had no issues with it.

Reply #2 Top

If you can determine a slow-down in your system when Fences is installed then you clearly have something on your system which conflicts with Fences.

Fences installed and functioning as intended will have zero discernible affect [other than the tidying up of your desktop icons, of course]...;)

Reply #3 Top

I ran Fences for a long time and never had any problems. Something is amiss on your system.

Reply #4 Top

I've seen Fences run on 2 very old & slow computers without a problem or slowdown

Reply #5 Top

Thanks for the flashback.  I've not heard the term TSR in 15 (?) years.

<X3

http://en.wikipedia.org/wiki/Terminate_and_Stay_Resident

Reply #6 Top

Give support@stardock.com a ring and maybe we can look a little deeper at what's on your system.