> they can pressure FreeBSD to stay away from GPL3

Yes; Apple can pressure the FreeBSD project to stay away from GPLv3, through their evil Apple magic. In fact, they are presumably pressuring the whole world to stay away from GPLv3, as it has seen almost no adoption outside the FSF! Naughty, naughty Apple. If not for mean ol' Apple, the FreeBSD project would no doubt rush to embrace GPLv3, discarding their horrible old BSD license!

In a word - no. FreeBSD has been around a lot longer than Apple's switch to Darwin. FreeBSD has a long history of preferring BSD licensed code to GPL licensed code. Apple has just financed clang/llvm. Apple has their reasons for using clang, and FreeBSD has theirs. FreeBSD didn't need any pressure from Apple to make the switch.

Uh, no. We aren't subsidized by the NSA or any part of any government or any organization or person for that matter. We bootstrapped Private Internet Access with 500$ and a lot of caffeine and have been profitable since our second month in operation.

We believe what the NSA is referring to when talking about "VPN startups" is the initial stages of PPTP sessions. PPTP has been crackable for a while, check out moxie's cloudcracker.com. We believe it highly unlikely that they have broken OpenVPN (which is what our application uses) or SSL.

Please see our stance on PRISM: https://www.privateinternetaccess.com/blog/2013/06/prism/

It is interesting on slide 17 that the NSA can decrypt all VPN traffic.

Does this indicate that they have broken HTTPS, or simply that they own VPN companies like Private Internet Access?

Seems like it is the NSA who has been lying

Dropbox used Python for client portability?

The Geoff Chappell article is great. Seems like he examined it in detail:

"The 32-bit editions of Windows Vista and Windows 7 all contain code for using physical memory above 4GB. Microsoft just doesn’t license you to use that code."

A huge pity he no longer blogs.

MS gave users no upgrade path from 32bit to 64bit Windows.

You need a clean install, something many are hesitant to do, or can't do.

Seems like it to me. Maybe they thought the whole drop quantam tunneled to the bottom

I guess you could have asked that if you find a tree that's fallen in a forrest, did it actually fall over if no one saw it?

You will make Microsoft angry if you do this. They have various versions of Windows 8, and some are more crippled than others.

It enables PAE which is 36bit addressing Microsoft brought in for their server product line. You still only have 4GB per process, though.

I've been using this one for Windows 7. Gives me 64GB http://www.adminsehow.com/2011/03/windows-7-32-bit-pae-patch...

Don't the 32bit and 64bit versions cost the same amount? I'm not sure why this would make MS angry.

Yea, I think the licensing mechanism was used for this limit just because it was convenient to do so.

I'm pretty sure that not all the drivers(especially graphic ones) fully support PAE. Server versions of PAE would be much easier to support than making sure drivers for win32 would be compatible in a PAE environment.

See http://msdn.microsoft.com/en-us/library/windows/hardware/gg4...

Typically, device drivers must be modified in a number of small ways. Although the actual code changes may be small, they can be difficult. This is because when not using PAE memory addressing, it is possible for a device driver to assume that physical addresses and 32-bit virtual address limits are identical. PAE memory makes this assumption untrue.

How safe is it to use? Have you heard of people having issues with the patch? If things don't work, would it be as simple as removing the patch or would a fresh Windows install be required?

ReactOS is great, but the project seems to have died in the last few years.

dead? the last trunk build is today!

Yeah it is not dead. He probably got that impression from the stall they got when they had to do a massive code audit