Wouldn't 10a (subtract) .999 be exactly 8.991...which breaks the whole "breakthrough"? Given that 'a' is a known value of .999... Math...it's so simple, only a mathemtician can't do it.

Someone disproved math. Kids around the world celebrating. Accountants are lighting themselves on fire. Corporate greed accellerates. 'Office Space' now seen as a prophecy.

I'd be happy with documentation that gives all the CLI commands and what they do in plain english (or your language of choice)... Nothing worse than getting a new piece of equipment that upper-management was sold on as the best thing "evah!", only to discover that you have to use the GUI for part of it, the CLI for another part, and then call the manufacturer (whom, without a maintenance/support agreement would otherwise charge a rediculous fee), whom requests remote access (lol-right...) or uses the CLI via remote-desktop-web-session and uses undocumented commands...and can't speak (your language here) well enough to explain what they just did and why. As for the article - Exchange 2007 does this pretty well - it gives you the exchange powershell command script when doing things with the GUI as part of the last step - kind of like holding one's hand and saying, here, try this as a script next time (not that I do)...there's some things that you can't do with Ex2007 without using the powershell - such as exporting a mailbox to PST, or changing SSL certificate info...

Why is it so hard to have 2 completely seperate networks? One for running everything (critical network) One for connecting to the rest of the world for email, etc. If you need to remotely monitor something - put an IP camera on it and connect it to the non-critical network...

I'd never puked from drinking until this past fall, me, at 31yrs old, until I had 1 and a half pints of Jeager, 2 Vicodin, and 6 malt beverages and 3-4 mixed shots, in the time span of around 3 hours.
I can't imagine hurling on a 6 pack + half a bottle (however much that is) of Absinth.

I'm the only "IT" guy, we have 5 others (1 manager/programmer, the others programmers) that are upgrading/developing internal applications. I take care of all the support issues (except for those internally developed apps). We've recently hired a sort of level-1 person, that is here part time. Job demand is such that we can just barely jusify having the part-timer - as this person's position has to be "billed out" to the other departments. Myself, I'm not billable for most of them. Strange, I know. Overall, we have around 200 users, according to active director. We have around 20 servers. Computers, we have around 300 or so. Why, you might ask? We have computer labs that the public can use...that we have to maintain. By myself, I get more and mroe behind, projects get delayed, ideas are never fleshed out. With the part-timer, I get enough breathing room that I can do more, even though I have to walk this more technical person through things...at least they get it, where our users don't.

Sorry, minor clarification - keep the systems off the same network as their desktops - I realize there is a trend towards IP-based management, but, in that instance, it's pretty simple - keep the networks seperate. Sure sucks for doing RDP to a desktop-controller computer, but, for the sake of security and "insurance" against unauthorized access, it's the best method.

There was an ice storm here in Oklahoma a few years ago. Power gone for 3 days for a few people, up to 3 weeks for some unlucky ones. Most averaged around a week without power, in the middle of winter. From what was reported, there wasn't any increase in crime. Everyone was screwed, criminals too. After the batteries ran out for cell phones (towers too), there was little to no communication. The worst things that happened were people stealing generators left unattended. There was a lot of tension "in the air" at places that did have power, but, in the end, it was calm, quiet, and pretty damn boring.

Such a simple solution...keep at least 1 staff person there (3 shifts) and have a computer that connects their desktop system to where-ever it needs to go - but leave the systems that manages the critical systems off the internet...100% hacker proof. There is plenty of room in a profit-margin to employ someone to sit there and watch a screen.

How long before one of the blades snaps off and kills someone, or there's lead in the paint, or the turbines themselves are "rigged" by China for debt-collection purposes? I know here in Oklahoma I see huge wind turbine blades being hauled all the time - well, at least in summer. I don't know where they come from or going to, but the going along the highway that goes from Tulsa to Dallas (state HWY 75) Why not buy American...and help OUR economy for once? Seems there needs to be an increase on taxes for imported goods...maybe we could use that to supliment health insurance (either by lowering income taxes, or by paying for it...)

For some reason, I read this article and immediately thought about a 15-bladed hsaving razor... My point being that 100 cores, while it sounds impressive, you get a diminished return after a few cores. Even if software was written for multi-core use (and not enough of it is, IMO), you still can't possibly, effectively, use 100 cores...not before this processor is already extinct due to technological progress. Even my quad core Intel CPU, hardly uses all 4 cores...and most commonly hits CPU1 for processes.

I have access to my corporate portal for Microsoft Select License downloads. Don't worry, I have it on order from newegg and will have it well before the 30 days is up w/o activation :) So far I've seen a lot of improvements over Vista, which I moved to recently as well. I didn't find Vista all that annoying except in one minor aspect - you do anything and the search components would go into overload and it'd reindex everything, making the whole system sluggish. 7 is a lot better in that regard. I've also not noticed a whole lot of other over the top improvements, other than just simple junk like adding a frequent-files/sites/etc to a start menu object, which is kind of neat but it doesn't work with any consistency with something like IE. One other annoyance that I found was that firewire support isn't "right" - I have a pair of Presonus Firestudio devices that I use with it, and the driver it loaded would not allow them to sync. Changing it to a "legacy" driver (included with OS) resolved the issue there, though, I've not recorded with it yet. Oh, and my AV software wouldn't work - but i got a free version upgrade since my subscription is current. Everything else I ran on Vista runs fine on 7.

Maybe it's just me, but, I would think the moon would be THE best place to put a solar array. We know the distance, we know it's movements, and it doesn't involve putting up more floating space junk, it's surface is always facing the sun (which unlike a synchronous satalite, would be our of the sun for at least a few hours (depending on distance) - and it's far enough that's visible from the poles, which is where I'd put the recieving stations - the sending stations would be on the moon's poles, so power coudl be recieved even with a "new moon" - the only exception would be in the case of a lunar eclipse... I'd also make sure there was a way to turn it off...quickly...from someone near the equator, just in case!

So, you mean they'll copy off all the space-porn to a central repository and do nothing?

Until they figure out how to implement Wireless PoE for VoIP Phone Systems...I don't see why anyone could say that wireless will replace copper.