Techie,
http://www.net-integration.net/cgi-bin/forum/ikonboard.cgi?s=89becbcadd4990ac60a2d58c7e98b60f;act=ST;f=28;t=5033
I'm with you, but not completely. I did notice that the dates on the thread were from August. This may be an indication of an ongoing problem with servers being unable to handle the load. I did succeed in getting SB S&D to update a few minutes ago, though it was through no effort of my own. Since SB S & D reports no new updates are available only for some but not for others, especially since it behaved both ways for me, ruling out differences in system configurations, I'm willing to consider that it may just be a server issue combined with poor error detection and/or reporting on the program's part.
Referring to my previous post about updating with limited vs. administrator accounts, logged on as a restricted user I told the program to check for updates, and it did find an update for detections available. Remembering Jarron's post, I selected another server (changed from Unido in Europe to FXClips in the USA) and initiated the download, which failed. An error message was displayed in what appearred to be German. I guessed that it was telling me that access was denied to
downloads.ini. I remembered at this point that this always happened in the past when I tried to update when running under a limited account. Checking the update directory for timestamps and my access rights to the directory, I saw that this was the case.
After giving my account the proper permission to access the file, I restarted the download without an error notification; however, SB S & D was still reporting the that it was using an older update. Checking again, I saw that the timestamp on
includes.zip was unchanged. I changed the permissions and restarted the download. It appeared to work this time, with a new archive file present and SB S & D reporting that it was using the new updates.
I wasn't satisfied with success, however. I opened the Zip file and looked at the contents. Comparing the timestamps of the archived files with those of the corresponding files in the
Includes directory, I saw that they hadn't been updated. Again I modified the permissions, but when I tried to reinitiate an update, of course SB S & D reported that no new updates are available. Doh!
Checking the timestamp on the archive files instead of checking those on the individual files is causing me some grief, but it's my own fault. It is a nice shortcut though, clever and efficient, and of course the developers didn't count on some smart ass circumventing the standard update procedure. I guess I can just extract the files to the
Includes directory, but I'm holding off on that for the moment to think it through. I'm also going to give the user account the correct permissions for the program's entire directory tree to prevent partial update problems in the future if I decide to update as a restricted user. (I just can't help myself and stop playing with fire sometimes.)
MacLover,
I run
Ad-aware build 181 also. It scans my hard drive with approximately 14 GB in 15 minutes, give or take.
This application has some update issues too. Just after my recent SB S & D "update," I ran Ad-aware and attempted an update, just to see if it would work under a limited account. It went through the motions reporting that the update was downloaded and installed successfully. But, it is still using the old reference file; the new file was never downloaded according to its timestamp. During subsequent attempts, it found the same new reference file and "downloaded" it. It reported erroneously that I cancelled two updates. The same lack of access permissions is causing this problem too, but
for the time being I'm going to leave it alone.
The other day, running with administrative priveleges, I successfully updated the reference file, but it took a couple of attempts. One update attempt hanged the program. I ignored it and continued to use the computer for another hour or so to finish the projects I was working on, then I killed it with the task manager. Within minutes, Explorer crapped out and had to be restarted, and subsequently I had to restart Windows. (When Explorer dies sometimes I can continue working, once a couple of hours, but within minutes strange things start to happen, usually quickly snowballing. I've learned that whenever Explorer or Internet Explorer fail -- they're heavily intertwined -- it's best to save my work and reboot.)
Regards,
Hornus
