yes you are right,

Thanks, that makes it much easier to understand all of those oddly colour coded drives!

@lillucia well that explains it!

Yeah i think..but it is good to learn sometimes..just to have an idea

Sounds like a great project idea. Thanks for sharing.

@alexntg said:

@scottalanmiller said:

Looks like the hands are bleeding.

It's not a clap. It's stigmata.

LOL!!

I've always shied away from the option to "Login with your [Facebook/Twitter/Linkedin/etc] Account", mainly because of privacy concerns, but also because I've heard of design flaws with the OAUTH and OpenID systems (mainly from listening to Steve Gibson's podcast)

AWESOME!

I'm not denying that development costs aren't playing a role in it. I can see @Nic 's point about keeping the cost higher to weed out people, that makes sense to me.

It's usually management that causes that sort of problem, well except me of course 😉

Not much of Outlook licensing concerns now that Office 365 gives you five licenses per user. And you can use OWA anywhere.

@RAM. I am still reading the Linux book. Sad to say i haven't finished it yet until now.
BTW hows your Linux Learning?

Even more puzzling is that this problem seems to be caused by a video driver.

@Josh said:

Gotcha - If you care to monitor the logs, my suggestion would be to just look for ERROR or FATAL not INFO

It's Loggly. So the Info logs become part of our volume. We aren't looking for anything, the logs are all hosted online.

Cool. No have not seen that before.

@alexntg Oh, gotcha! I had forgotten about that. I never actually used the "staff" part.

@scottalanmiller Thanks i am reading on it 🙂

@Nic said:

I wonder if it was found by the same five year old who found the Xbox bug 🙂

I was totally thinking that too.