Today Amazon announced new Kindles. Three are e-ink devices, like all the Kindles that have come before. Unlike all previous Kindles, none have keyboards. The cheapest is a $79 device with some basic navigation buttons. Then comes the $99 Touch, followed by the $149 Touch 3G, and, finally, the Kindle Fire.

The Fire is the most interesting of the bunch. It is a 7″ color tablet with WiFi and a custom version of Android that will sell for $199. Compare that to the Nook Color, another Android based color tablet from a bookseller which goes for $250.

Of course, before the announcement, lots of people were yammering about it as a challenger to Apple’s iPad. It’s $300 less than the cheapest iPad, but I don’t think its a good comparison. The iPad has a 10″ screen, which is large enough to support some fairly functional applications, like the Numbers spreadsheet. It’s also large enough to provide a highly usable on-screen keyboard in landscape mode. The Kindle Fire isn’t going to support the same breadth of apps.

I think the Kindle Fire is a much closer competitor to the iPod Touch. Like the iPod Touch, the Kindle Fire is strongest as a content consumption device. The larger screen makes it better for reading, for watching video, and for playing games, but it’s also less portable than the Touch, which probably matters most for music and for a lot of games.

I think the Fire is bad for pretty much any other Android tablet.  No one is having much success going up against Apple head-to-head, so Amazon widely targeted the 7″ form factor (though rumors are that a 10″ is coming). I think they’ll do much better here than any other Android tablet since they provide a strong distribution channel and it seems they are willing to sell at or below cost in exchange for all the commerce opportunities that will come once people have the device.

It’s interesting to compare Amazon to Apple’s approaches to this general market.  Both companies sell hardware and have electronic storefronts people can use to buy content and games for the hardware.  Apple sells the content with thin margins to enhance the value of their high-margin hardware.  Amazon sells the hardware with thin or negative margins to enhance the volume of low-margin content they sell.

There have been a lot of complaints about Apple’s desire to get a cut of in-app content sales, but, never the less, iPad users aren’t limited to content distributed through the App store.  For example, even though Apple distributes TV shows, movies, and ebooks, users can get video content from Netflix and Hulu, eBooks from Barnes & Nobel, Amazon, and others. Will Amazon be as open?

One thing is clear, this is a blow to Google’s influence over Android in the tablet market. It weakens other Android-based tablets while the whole Android identity take’s a backseat to Amazon’s Kindle brand.

I still need to explain what I think some of the facts I laid out earlier surrounding Windows 8 could mean, but before I do, I feel like I should share my thoughts on the implications of some of the under-appreciated synergies between OS X Lion, iCloud and iOS 5.

I’ve been chewing on this for a while, but I was finally inspired to post something after commenting on Amit Kumar’s post “The User Experience of Apple’s Upcoming iCloudBook.”  In that post, Amit builds on an earlier blog post where he explains how he thinks certain features of OS X Lion portend a “cloud” notebook from Apple.  Its some nice thinking, but I think its fundamentally flawed.

The reason? By focusing on Lion and the Mac, he’s thinking about Apple too narrowly. That focus might have made sense just a couple of years ago, but these days it’s important to remember that Apple earns substantially more revenue, and profit, from iOS devices than the Mac.

The real story, in my view, is how Lion’s new document model and incremental file versioning and storage, along with iCloud and iOS 5 combine to create the beginning of a seamless, pervasive computing environment.

I’ve linked above to an in depth discussion of Lion’s new document model and the file versioning and storage services that support it, but to put it briefly, apps built specifically for Lion are supposed to continually service changes to disk, while the file versioning and storage services help support compact storage of multiple versions of the same file and provide a standard way for users to access older versions.  The key here though is the fact that the version on disk is never very far out of date, and that the changes are stored in a compact manner.

Now add iCloud, and this means that as long as some Internet connectivity is available, a user can have an up to date version of their documents available from anywhere, including their iPhone, or iPad.

Pull it all together, and you can do something like this:

You stay late at the office to finish a presentation you have to give in Denver tomorrow afternoon.  You put the finishing touches on the presentation with Keynote, close your MacBook Pro, and hurry out the door so you aren’t late for your girlfriend’s birthday dinner.

 

The next morning, in the line for a latte at an Airport Starbucks, you pull out your iPhone, and open Keynote so you can review the presentation.  Your laptop is still closed, on your desk at work, but the latest version of the presentation opens quickly from iCloud. You flip through the presentation until your order is filled.  As you wait to board your flight, you sip your coffee and fix a few typos.

 

A little later, you fasten your seatbelt and pull out your iPad. While you wait for the flight to depart, you open Keynote, and make further changes to your presentation.

As you move from device to device, the latest version of your document is available to you without a second thought.  It just works.

I haven’t spent a lot of time looking at demos of Windows 8, but I have been reading and listening to thoughtful commentary by Horace Dediu and John Gruber, which has, in turn, got me thinking.

This post is an attempt to work through some of those thoughts, but, where to start?

I guess I’ll start by noting some basic facts, as I understand them:

• Windows 8 won’t ship for a year or so.
• Microsoft demoed Windows 8 on an Intel i5 based tablet that is so beefy that it needs a cooling fan, and which, by implication, must have some combination of poor battery life and added weight and bulk to support the larger battery.
• They also demoed Windows 8 on ARM based tablets running the soon to be released NVidia Tegra3. This platform, or it’s successor, will likely not perform as well as the i5 based tablets, but should offer better battery life for a given level of performance. In theory, the power/performance will be in the range of whatever Apple puts in the iPad3, but hardware is only part of the story.  The iPad’s apps and OS are built for the power and performance constraints of a mobile device.
• Windows 8 is schizoid.  On Intel, it will run traditional Windows apps within the context of a slight evolution on the traditional windows API and new Metro apps.
• On ARM, it will only run Metro apps, unless, of course, it doesn’t.  There will be no x86 emulation on ARM, but Microsoft may or may not allow developers to recomplile traditional Windows apps for ARM
• Metro apps will be distributed through a Windows App Marketplace, and microsoft will take a 30% cut of revenue.
• A corrolary of Moore’s law, dubbed Koomey’s Law, states that power efficiency of computation doubles approximately every 18 months.
• Battery technology improves much more slowly. Capacity of lithium ion batteries is improving at a rate of less than 10% per year.
• iPad 2 Power consumption: Display: 2.7W, Also a 25Wh battery
• IPad WiFi+3G Idle, with display, 2.97W.  Average power consumption 2.5W (25Wh battery, 10 hour run time)
• These numbers don’t quite square up, but they support something I read when the first iPad was released, that the large display was the biggest contributor to the devices power consumption.
• Microsoft’s biggest customers are businesses, particularly “enterprises”
• Micrsoft’s enterprise customers are slow to upgrade.  Many were on Windows 2000 or XP (and IE6) and only just recently upgraded to Windows 7, which helps explain why Windows 7 has sold so well, but also suggests that they will not be in a hurry to upgrade to Windows 8, indeed, they may not upgrade again until Windows 10.
• Apple has been winning new enterprise customers with the iPad.

Well, that took longer than I thought.  What I actually think it all might mean is going to have to wait for a follow-up post.

I’ve been having trouble with a Windows 7 client connecting to a PPTP VPN endpoint on Mac OS X 10.6 (Snow Leopard) Server.  The client authenticates just fine, and can access resources on the LAN, but connections time out when connecting to remote servers.

The simple solution was to configure the VPN client to only tunnel LAN traffic through the VPN, but that undermined one or our reasons for having a VPN: Securing connections from public WiFi hotspots.

For a long time, I assumed the problem had something to do with the routing, but after an hour or two with a packet sniffer hooked to the server, I discovered that TCP sockets to the problematic servers were being established, and, often, significant amounts of traffic were being passed back and forth.  I also noticed that the conversations were interspersed with packet fragmentation errors.

Ah Hah!  Something must be screwy with negotiation of the MTU.  With a little digging, I found some instructions for adjusting the MTU, which I’ll summarize here:

1. Click the start menu, search for “cmd.exe,” right-click the search result, and choose to run as administrator.  Answer yes to the security warning prompt.
2. Connect to the VPN in question.
3. Run “netsh interface ipv4 show subinterfaces“
4. Make note of the name of the listed connection name (it should be the same name as the VPN connection entry you used to connect to the network)
5. Run “netsh interface ipv4 set subinterface “[CONNECTION NAME]” mtu=1100” Substituting the name of your connection for [CONNECTION NAME], you can try different values for the MTU, in my case, it defaulted to 1200.
6. Check that the change was made “netsh interface ipv4 show subinterfaces“
7. Restart your computer.