How to restart On Access Scanner

---

LDMartin1959 wrote:

...That being said, I do recognize that far too many -- perhaps not the majority, but still too many -- programmers and software designers operate in a fantasy world where every user only does things the way those software designers demand and any user who does anything differently than those software designers demand get what they deserve when the application misbehaves. Sorta like a car designer telling a driver that if the car misbehaves when the make a left turn it's obviously the drivers fault because, after all, the car was designed only to make right turns and don't expect them to "fix" the problem because there isn't a problem: drivers simply have to stop insisting on making left turns -- THAT'S the problem!!

I agree but I think that can go both ways. I have my computers set to run in verbose mode so I can see at least part of what's going on as they boot and as they shut down. On occasion, shut down will be delayed because some processes are still at work and the OS gives them a chance to end cleanly. I haven't tried that in a transition to sleep but I suspect that the OS is in more of a hurry to finish because, at least with laptops, the user assumes that with the lid closed, he can grab it and go, something which could be dangerous for a machine still in a transitional state. And with many processes needing to close at once, cooperation among them can become problematic, even assuming the every one of the programmers had concern for such cooperation.

I don't know what Developer Guidelines there are (if any) for programmers dealing with an abrupt sleep transition but it couldn't hurt for the user to have some appreciation for (if not understanding of) what goes on under the hood and give his computer a break.

And while the first defense of a manufacturer is often to blame the customer, I still remember a co-worker who thought that anti-lock brakes meant that he didn't have to steer out of danger either. There is a middle ground...

---

LDMartin1959 wrote:

...That being said, I do recognize that far too many -- perhaps not the majority, but still too many -- programmers and software designers operate in a fantasy world where every user only does things the way those software designers demand and any user who does anything differently than those software designers demand get what they deserve when the application misbehaves. Sorta like a car designer telling a driver that if the car misbehaves when the make a left turn it's obviously the drivers fault because, after all, the car was designed only to make right turns and don't expect them to "fix" the problem because there isn't a problem: drivers simply have to stop insisting on making left turns -- THAT'S the problem!!

I agree but I think that can go both ways. I have my computers set to run in verbose mode so I can see at least part of what's going on as they boot and as they shut down. On occasion, shut down will be delayed because some processes are still at work and the OS gives them a chance to end cleanly. I haven't tried that in a transition to sleep but I suspect that the OS is in more of a hurry to finish because, at least with laptops, the user assumes that with the lid closed, he can grab it and go, something which could be dangerous for a machine still in a transitional state. And with many processes needing to close at once, cooperation among them can become problematic, even assuming the every one of the programmers had concern for such cooperation.

I don't know what Developer Guidelines there are (if any) for programmers dealing with an abrupt sleep transition but it couldn't hurt for the user to have some appreciation for (if not understanding of) what goes on under the hood and give his computer a break.

And while the first defense of a manufacturer is often to blame the customer, I still remember a co-worker who thought that anti-lock brakes meant that he didn't have to steer out of danger either. There is a middle ground...