When I've seen it work is when it disables and reenables the adapter, which is pretty much the equivalent of turning it off and on again. So, yes, it has "fixed" things in my experience, though it hasn't done anything particularly "special" to make it happen.

Fool me once, shame on you; Fool me twice, prepare to die. --Klingon proverb

The "obviousness" is a feature, not a bug. Anyone that is paying attention enough to notice the scam is likely to be harder to con in the next step. They're phishing for someone oblivious, who is less likely to question when they are next asked to go buy a bunch of Apple gift cards with the company credit card and email all the codes.

Fool me once, shame on you. Fool me twice, prepare to die. --Klingon proverb

> No, that's incorrect, because when I do a Restart the value changes. Actually, that's also correct. The "fast startup" causes it to not reset uptime when doing a shutdown, but restart actually does reset uptime. It is thoroughly confusing.

I agree that you shouldn't have to deal with it, but you can hold CTRL and use your mouse scroll wheel, or CTRL and the +/= and -/_ keys (the ones on the top row of the keyboard, not the numeric keypad) to zoom in and out in some apps (including most web browsers that I know of). Windows also comes with a Magnifier tool to zoom in on apps that don't support a zoom function. I say this because of experience. My eyes aren't what they used to be (which may be a result of years of staring at 4pt fonts on screen).....

I love working with .Net. I hate SharePoint. Took that one off my résumé as well.

Well, this link works. The one in the email just went to a "Group not found" page.

Exactly what I was thinking. Microsoft *has* been the big bully, and what did it get them? http://en.wikipedia.org/wiki/Microsoft_litigation[^]

Reading the Steve Jobs biography, I was impressed with an anecdote about an illiterate boy who was able to pick up and start using an iPad without any instruction. I've also noticed my own kids use my Windows Phone and my wife's Android tablet. While I'm sure a large part of it is how little kids have no fear of trying new things to figure it out, what struck me was how truly intuitive these devices are, how they are usable without any instruction. Windows 8 is going in the wrong direction. For all they talk up how "intuitive" it is, the fact that they are having to put in a tutorial for the most basic functionality is completely backwards.

Right-click on an empty area of the start screen, and click the "All Items" button that appears at the bottom. I discovered that on accident when I was looking for the same thing. Which is a major part of the problem I've had with Win8. In their quest for "simplifying" the screen, they've eliminated so many visual cues as to where things are, that I've found many of them "by accident". There's an excellent video floating around on YouTube where a guy showed his father Windows 8 (Customer Preview), and he spent 20 minutes looking for the "Start Button". There's nothing on the screen that tells you that you need to move your mouse to the lower left to bring up the start menu. There's nothing telling you that you need to right-click on an empty area of a web page to bring up the Metro version of Internet Explorer's tab menu, address bar, etc. There's nothing showing you that you *can* snap windows side-by-side, let alone *how*. Besides that, I may be comfortable experimenting with the system to see what it can do and how it works, but (1) I'd rather spend my time *doing* instead of trying to figure out *how* to do, and (2) my mother certainly won't be, and will be very confused as to how to do things (even if they have a "tutorial" when the OS first starts, do you think anyone is going to remember everything it has to teach?).

There are a few ways to get around Razor methods - partials, @helper sections, static helper classes, or extension methods - depending on what exactly you're trying to do. One thing I strongly dislike about Razor is the lack of documentation. MSDN works great navigating the C# class library, but the Razor reference just isn't there yet. I have to find method and syntax docs on offsite personal blogs. There are other things about Razor that cause me daily pain, but I don't want to get too far off topic here. ;)