have you tried testing this by downloading it from some other domain? i still don't buy it, imho it would be flagged no matter what, i had the exact same problem with a .net.dll (managed machine) sent to me trough dropbox. buzz even threw up an error saying that the dll could not be loaded, i'd like it to show this error for gui.dll too please. also that winrar works points to something else, obviously winrar somehow ignores the stupid "evil" flag. it also never seems to be a problem with native .dll, only .net so that points to something in windows security model regarding the handling of .net dll imho. Note that the NATIVE mixio.dll ALWAYS works, but ONLY the .GUI.DLL sometimes has this problem! Pure .net.dll machines ALSO have this problem. The zip was created with winrar, i doubt winrar would put in the flag when its one of the apps that ignores it when unzipping it...mute wrote:1) IE/Chrome/FF, doesnt matter.. checked all of themUNZ wrote:no, where do you see a redirect? and even if, i doubt its caused by that.mute wrote:after looking into it a bit, i believe it is happening because your download urls are technically redirects
i'd like to reproduce this for myself but i need some info:
1) what browser used to download ?
2) what unzip app used ?
3) unzipped to what path exactly ?
2) Winzip. 7zip and WinRAR are ok.. but that's not a solution, just a bandaid
3) Directly to Buzz/Gear directory, or anywhere else, doesn't matter
I would still guess it's likely due to the ddns setting off ms's security zone for one reason or another. DLL's and Zip's aren't even "high risk" files according to MS.., so something is setting it off into high-risk territory. Plus, as you can reasonably assume.. I download shitloads of zips and dlls (not just buzz related). Maybe theres also a possibility in how the zip was created.. not sure, haven't looked into that (quite possible.. t appears zone information is stored with the file on NTFS systems, so those using XP or vista without NTFS should never experience this).
the path where you extract to could very well matter, it may just work if its a path where you have full control / are the owner, but not if its like in programfiles and you are running the unzip as non-admin or shit like that. if you extract to a path where you have full access and then copy to programm files, windows will even show a message that you need elevated privileges (UAC) to do this, and if you then aknowledge this i guess the evil bit is not set.
whatever it is, buzz needs to either ignore this flag or at least show an error informing the user what went wrong. i dont think i can fix this by doing anything different.