That doesn't make sense. NTLMv2 and Kerberos make use of the system time during authentication. If the clock is off by more than a certain period (configurable, 5 minutes default) then authentication will fail.
Unless, of course, domain policies are intentionally configured to allow replay attacks.

Your issue is with the fact that the Windows installation media doesn't come with all these nice programs. Well, how do you think that happened?

Windows is a a proprietary product that will never in its life come with KeePass, Notepad++, ImgBurn, TrueCrypt and Firefox unless you make it so (it's easy to customize a Windows image file with a custom answer file, so you actually can).

You're going to have to make a choice: people whine about Windows having too many features that results in the community yelling "Bloat!" or even leads to anti-trust lawsuits if Microsoft includes a proprietary version of said software, or: look at it as a bare operating system that can run the applications you want to run. You can't have it both ways.

By the way, msiexec /i FavoriteSoftware /qb! is not that difficult, as long as it's packaged decently. Any environment where user's time is valued over system deployment time has a multitude of options to automate OS and application deployment, with free toolkits (the most recent one being MDT).

FTFY.

That is true as long as an adversary does not have access to the disk contents already. If you were able to look at the encrypted volume and its free space over the course of time, you would see changes in "free space" every time the hidden volume is used.

You ever got home and your computer was suddenly turned off?

His beef is probably with the expression "regular automatics", and not with the reason why a manual shift cars are more expensive.

That just says you're not the target audience, mr. AC. Then why would anyone listen to you when it comes to making design decisions?

It isn't that bad. If it takes any longer than 4-5 seconds to authenticate and process your user policies and scripts then you're doing it wrong.

It kinda depends on what you mean by 'there'. In smaller environments, additional time is usually caused by:
* incorrect network setup (dns, usually)
* insane synchronous startup/logon scripts or those that do "software deployment". Those are a damn joke.
* roaming profile that has become way too big.

The "always wait for the network at startup" setting in computer policies may help. It ensures that all services are started and GPO processing has completed before the logon screen is presented. It may take a while longer before the user may enter his credentials, but the desktop then appears more responsive sooner. A particular example is when there are instances of SQL Express installed on a laptop, for whatever purpose, that can really stall the logon process as the database server is still starting.
Also, first logging on and then leaving for hot beverage is not always an option because of company policy against unlocked desktops.

In some cases, like very large corporate environments, there is a lot to take care of at logon time. In enterprise desktop provisioning, you can't tie anything to a computer because the user may log on from any system, not just a roaming desktop but Citrix, VDI, whatever, so all of the desktop setup has to take place at that point as if you were a new user.

The game also has split-screen mode (party mode) so this is technically correct. The online part was removed from the description, however.

The Game Info still has multiplayer, but the game also supports split-screen with multiple controllers. The statement "then prove yourself online" was quickly removed, however.

That figures. It's still on int'l keyboard layouts: AltGr-Shift-Z

Agreed. I will take something that works over anything that is open any odd day of the damn week.
(Hey, sorry it's a badly documented enthusiast implementation of what *we* think is interesting, but at least it's *OPEN*!)

Plz and thx. Next thing you know he'll be handing out free coffee.

Get off my shared bus.

What was your score on the Turing Test? "Human but coward."

Now, there's the problem. Within a few months time, it will get increasingly more difficult to find business desktops and laptop systems that will run XP. The consumer already has no choice. That's what "support" means. PC manufacturers, developers, everyone who's getting along, will no longer develop and test products for XP. This better sinks in: in a year's time, it's virtually impossible to get new (business class) hardware that runs this ancient OS. If you need to replace, update, upgrade or expand, you will be stuck, and you will be forced into migration at the least convenient moment.

"Stick with XP". No, that's really good advice.