Hey, Joel. I don't know - I tried every combination of network cable connected/disconnected and USB drive connected/disconnected - rebooting between each combination - and in every case it still takes right over 30 seconds for Eraser to come up with it's screen. I thought perhaps a service that is auto by default that I may have set to manual that is taking time to start but, then, I would think, after running Eraser once and then running it again without a restart, the service should already be running and Eraser would come right up - but it takes the 30 some seconds even in that scenario. I have Drivegleam and a network monitor running and have been watching processes in Task Manager as well. I always see the initial disk access when I run the program and Task Manager always shows only Eraser.exe using about 25% CPU time during the 30 seconds. Sometimes I see ongoing disk activity during that time and sometimes not. Sometimes I see a quick blurp of network activity during that time and sometimes not. I rarely see any program get above 15% CPU time starting up. Since no one else has chimed in, "Yeah, me too", if you don't want to mess with it, I don't blame you. But, if you do and you want any other info that might help, just let me know. I don't know if running on 64 bit has any bearing but just a reminder that this is the case for me.
BTW, every time I try to access the forum using any of the links in your emails (via Firefox 20) I get "The connection was interrupted". I haven't had a problem with any other https sights I try to access so I'm not sure what the deal is.
Thank you very much.