Thanks for testing 8)
Update: To my post in reply #32 http://forum.avast.com/index.php?topic=27213.msg221910#msg221910.
I tried running the avast! at logon scan after boot. I opted to run the scan just before shutting down my system for the night, this morning when I logged on the SUI was displayed and I started the same Standard Scan no archives scan.
Prior to the scan I checked Task Manager and there were 27 running processes (including ashsimpl.exe). The scan took 9min 28sec for the same data size, slightly slower again than the previous one in reply #32.
Closing the SUI allowed the logon to complete, when all had settled the Scanned total: was 117, so a big difference in the scanned total when avast at logon was run having only logged off/on to initiate the scan. So it is strange that even though there are less files scanned in the background by standard shield the on-demand scan was slightly slower.
I checked the task manager processes and that was at my usual of 30 after boot (obviously no ashsimpl.exe), so the avast at logon isn’t getting in much before my normal processes, this I have no non-essential programs running at boot.
So overall for me there doesn’t appear to be much difference if I do a normal on-demand scan or use the avast on logon scan, it may well make a difference for someone with more programs running on boot/logon.
Tech,
forgive my ignorance :-[ but does it include an uninstaller? i.e: could we uninstall it? ???
I’d already asked Tech about this via IM - he says just delete the files and folder, since it’s not installed as such, simply a stand-alone.
Tech -
This program ran when I started my computer this morning without any problems. As others have reported, there is not much different in scan time. Checking the Taskbar after scanning, nothing was there to begin with except avast which always loads first on my computer and probably loaded as I was moving my mouse to bring up the Taskbar which is normally hidden.
On my computer, this application seems to work as expected. 
Seems that all tests are conclusive: scanning speed is not higher.
It’s difficult to make a correlation between speeds right now.
I think defragmentation at logon time was significantly better with Windows 9x and Me.
Maybe things are different on NT platforms.
My case is, obviously not yours, I have a lot of background processes.
It’s a standalone. If you want to disable scheduling you could: boot and cancel the scanning or just schedule it twice. An option to unschedule will appear.
First try, it gave me the “unknown error message - Application cannot load skin. Function usiGetSkin Failed” error. Never had it before… (although I know about the problems other users had and the FAQ solution about it).
Strange that only you get this… can you start avast Home at any time or you can’t? I mean, will you see this error when you open avast normally?
No, it just happened when I tried your program. Never saw it before.
Any other message on avast logs?
Again, the program only launches the same avast executables (ashSimpl.exe or ashEnhcd.exe)…
OK, I re-registered “ACTSKIN4.OCX” and this time it worked. The scanner was skinned, although I use the skinless GUI. After logon, I started avast again and it was skinless again. I don’t know if this had something to do with the problem, but everything works OK now.
I see… I do not prepare the tool to use the skinless version. I don’t think there are that many people using it… although it is possible to ‘read’ the status of avast and then run the desired version. Do you think it will worth the programming work for it?
Sure, if you have the time, go for it 
My leisure time is crying… eh eh… I’ll give a try. It will take one hour to do and test…