Very ingenious, thank you. It works perfectly.

I'm writing a Windows Explorer-like clone for myself, and I'm running into a problem with empty disk drives. When I run the application, by building the project, it works as expected. However, if I run the executable directly, I get an error window titled: ".NET-BroacastEventWindow.1.0.3300.0.1: ExplorerPlus.exe - No Disk." Normally, this error references drive A:. (Which, of course, is empty.) However, I wrap the appropriate calls in try...catch blocks. In fact, if I remove the try...catch blocks, this error will pop-up before .NET displays its message about the un-caught exception. This happens for both debug and release versions of the executable. Running the executable directly results in these errors whenever the application accesses an empty drive. However, when the executable runs as a result of the project being built, it runs just fine.

Edit: Your response got me thinking that I may be looking at this the wrong way. The window that pops-up is titled ".Net-BroacastEventWindow.1.0.3300.0.1: ExplorerPlus.exe - No Disk." When I remove the try block, this error pops up before .Net complains about the un-caught exception. So, I think I need to ask a different question. Thank you for the obvious answer, as it's made me rethink the problem.

3 days on 3 days off

Regardless, if people want to waste time, they'll waste time. The question is why are they wasting time. Why aren't they motivated to be as productive as possible? Typically, the reason is because of the work environment. They may not feel that their knowledge/experience/participation is valued. They may not feel like they're respected by their employer. They may not like their job. There's a whole slew of possible reasons. It's easy to dismiss some of those reasons. For example, if someone doesn't like their job, it's easy to tell them that it's their problem. However, maybe the work is terrible, and there is some way to improve it. Or, it might be possible to use this person in a different position. Immediately "blaming" them is a sign of disrespect, which may be the root cause of the problem. Bradml is suggesting a holistic approach to the problem. Respect them and they'll respect you. One of the ways that they'll respect you is by looking at their productivity from your viewpoint. Notice, that he does monitor his employee's websurfing. However, he tactfully asks them to cut it down, instead of simply blocking access.

I'm writing a Windows Explorer-like clone for myself. I'm running into a problem where I still get an exception when I try to access empty drives (e.g. the floppy drive), despite having wrapped all the appropriate calls in try...catch blocks. The odd thing is that this doesn't happen when I build the project. However, if I try to run the executable directly, I get several exceptions. Same thing happens with a release version for the executable. Another odd thing is that sometimes I'll get 4 exceptions, all for drive A:. Other times, I'll get 2 exceptions, one for A: and one for an empty CD drive. Any ideas?

Now that's the elegant solution! Try it for some numbers: 010b: 010b - 1 = 001b 010b & 001b = 0 100b: 100b - 1 = 010b 100b & 010b = 0 110b: 110b - 1 = 101b 110b * 101b = 100b so, if (bitFlag & (bitFlag - 1) == 0) { }