Hey all
I’m the developer for Sentinel over at Runtimeware.com - My product is basically an anti-virus supplement that will help the AV product find hidden threats.
A customer emailed me asking me for support for Avast concerning the ashQuick.exe file (which is used by Avast to scan files on demand). His problem was that he was receiving an “Dialog error 1400” whenever ashQuick.exe was shelled. After installing Avast and testing it myself, I found that ashQuick.exe would generate that error if it was shelled but not given focus. To reproduce the error, all you need to do it shell the ashQuick.exe and not give it focus (IE: let it open minimized). To get around this problem with existing versions of my product, a user is required to click on the titlebar in the systray of ashQuick before that error is received.
I found that similar errors will pop up if the window is sometimes minimized before the scanning completes (I have seen other similar bug submittions these forums - and may be generated from the same sort of behavior).
Derek