I posted a comment about the macro warning in the wrong list by mistake.. next time I'll be sure to drink 5 gallons of coffee before posting.......
this next comment is "build/update" related.. its across the board for all builds... your update process... should be separate from the hfs.exe process... I have noticed that it updates without suspending the current process.. and if you do it manually it kills the update in progress.... can you fix that?
it's really "A N N O Y I N G!"
I have other programs that do the same thing... the update runs.. detects the current running process... shuts it down.. updates.. then reloads the process with the update.... it also does a check against the file version to make sure the update actually loads.
this would be much more efficient where the auto-update feature is involved... pretty much hassle free and minimum downtime for HFS... also maybe somethign that serves a warning to any logged in user? something like:
[the server is updating, please be patient...]
then to confirm to logged in user
[the update is complete, you may continue browsing...]
the way it works now is that it disables hfs without shutting it down.. then runs an additional copy ...... which isnt always the new version.... sometimes the command window gives a conflict error message for a memory address.
I figure this suggestion would help minimize the problem.