it would only have been an issue on any copies edited to only use the cache 188.8.131.52, any set properly to use all caches would not have had a problem - many third party programs had a problem with the original version of my cache software (that was used for the first few days) - a few weeks ago i modified the backups on the server so if there was a problem launching the cache for whatever reason it would revert to a backup copy of the program (ie. in the event that the cache software became corrupted etc) every now and then due to bad timing it would fail and load from the backup copy for 10 minutes before restarting on the normal copy - not a problem in itself, except that the backup copy was the original version of the cache and not the fixed one that's been running for the last few months
i just copied the latest version in place of the backup one
however for unrelated reasons i will be doing some more testing on the new cache software rather than running the old cache software on that server - so the thing that caused the problem in the first place won't even be running for a few days now, however it would be a good idea to either use a correctly fixed version of shareguard, or to use the winmxgroup patch along with shareguard (which will fix it correctly - even a so-called fixed version will be fixed by the patch to use all caches properly)
however on the plus side, it did finally show to the users one fact that vladd and co have been denying - namely that the shareguard they released as "pie patched" was indeed the version from this site fixed to use a single winmxgroup cache, and nothing to do with any "pie"
something they still deny even though anyone can see it only using a single cache... but that's getting a bit off topic there