Well it happened.

Today my MacBook Pro blue-screened.

I was in the middle of troubleshooting a WLAN connectivity issue*, and BAM!, IRQ_NOT_EQUAL or something. A nice touch was the magenta square in the the middle of the field of blue.

I've been running XP/Boot camp on my MacBook Pro for several months. I had some hardware issues, weird behavior with games and inconsistent "Sleep" behavior, but XP had never crashed. I'm not sure, but I think my messing around with the wireless connectivity configuration caused a problem in the Bootcamp drivers.

When I installed XP using Bootcamp, I opted to use FAT32 as my filesystem so I could share files between OsX and XP. Unfortunately, sometimes the disk consistency checker would run during boot and find errors on my disk.

I'm going to finally make the plunge and move to using Parallels for my primary XP instance for my "corporate" stuff. Internally, Intel Mac users are very happy about the stability, and functionality of Parallels. (All is not perfect though, I think I'll need to use a h/w security token for VPN)

I'll post my experiences soon

* It seems Intel IT has recently changed/upgraded the way we attach to our internal WLAN. It's still not working, even after a hour of troubleshooting by IT.

Systems

A thick client is usually a full featured PC (hard drive, powerful CPU, local processing, etc.) Generally, a thin client is a "dumb terminal" that effectively acts a display device for applications running on a server (usually within virtual machines/sessions), sort of a remote desktop. This approach can have many benefits: manageability, security and TCO is considered to be better when using Thin Clients. There are some drawbacks: new hardware purchase/deployments, incompatibility with existing applications, limited mobile support, and user acceptance ("I want big a BIG PC just like everyone else has!").

There is a hybrid model: the "chubby" client. With this approach, bare metal PCs are provisioned by streaming the operating system (check out http://www.ardence.com ) and applications (checkout http://www.appstream.com) to a full featured PC like the one sitting on your desk or lap right now. Although you would think this would be a performance hit, I've seen streamed Windows XP OS and Word startup faster than the traditional method. Moreover, applications can be virtualized (check out http://www.altiris.com ) to provide a "zero foot print" install -- the application and its data is removed after the user is finished and application isolation -- each application's registry, disk storages, etc are isolated from each other (no more DLL conflicts). Most, if not all, of the advantages of a thin client can be realized by the use of these technologies (one or all depending on needs). Another major benefit is this can work while the user is offline or out of the office. I've talked with several end-users who are running major parts of their enterprise on these technologies with great success " reduced TCO, better manageability, and happy users.

Software

Locally installed native applications such Microsoft Word are considered to be "Thick Clients". They have a persistent footprint on the system and utilized the native capabilities and services of the platform for computation, storage and interaction. However, the distribution of new applications, updates, patches, etc. can be a big headache when you're talking about tens of thousands PCs in an enterprise. Thin clients, e.g. applications which use web browsers, Flex2 as execution containers, may avoid these problems because the application is streamed to the "container" and does not persistent on the system. ("zero-install"). The application is always fresh and easily distributed because it is hosted/generated on the server. Additionally, AJAX and AJAX-like technologies enables the creation of web applications that are as expressive and capable as thick clients (almost). HOWEVER, thin client containers are a product of the Internet. Rarely do they interact with the underlying platform or utilize platform services such as databases/queuing, etc, and are oblivious to the platform/environment they are running on/in (Context). I believe that in order to extend the "Web 2.0" use models (offline operation, high frame rates, adaptive behavior, etc) applications need to be aware of and leverage the capabilities and services of the underlying platform.

In the Web 2.0 space, my group has been developing a Platform and Context Awareness extension for Firefox and IE. It provides a JavaScript interface to various attributes and characteristics a system. Examples include remaining power, power source (AC or DC), loss of network connectivity/reconnection, bandwidth info, and details about the hardware, e.g. number of CPU cores, network interface abstractions (WiFi, BT or GPRS), etc. (see [video] for a demo - click on download first).

We believe this library will enable developers to create more capable and user friendly AJAX applications, e.g. deal with intermittent connectivity and low power situations, and leverage the available CPU power of the system. We have other ideas to expand its functionality, e.g. location, offline queuing, and platform support, so we're looking for input and requirements. The goal is ensure the "thicken" the client application container (the browser) can understand and use the capabilities of the system " a chubby client. I think this technology will enable mobilized/offline AJAX use models/applications, a major gap in today's AJAX applications.

Our plan is release the source code to the Web 2.0 community. Any ideas how/where we should do this? In the mean time, we will be release the API specification for review and comments in the next couple of weeks. We would like a few brave souls to give it a look before we release it publicly. Specifically I'm looking for JavaScript experts help with the current practices and approaches with regard to the JavaScript idiom. If you are interested let me know.

Stay tuned for more details.

As the problem got worse it was nearly impossible to keep the system running for more than 15min, and I had several GB of data that I needed to copy off to another system.

I obviously needed to get some airflow through the system using an external fan. Looking around my home office I came up with very effective and elegant solution.

By attaching the vacuum cleaner to the back of the MacBook I was able to keep the temperature down and copy my data to a file share. Although, it's probably not feasible to take my vacuum cleaner with me to the office or on business trips, I am considering purchasing a DustBuster or one of those keyboard vacuums.

I got a replacement MacBook, reinstalled BootCamp Beta 1.1.1, WinXp, etc. and things have be running smoothly so far. BTW, the melting point of aluminum is 933 K.

In general, there are three ways to get your MacBook Pro on the Intel's corporate network: Windows XP using Boot Camp, Mac OsX, and Parallel's virtual machine. All three methods have been used at Intel, but I won't be discussing Parallel since I've not tried it myself. Before I get into the details, here's my Top Ten List of reasons I like my Mac Book Pro.

10. I can visit the Apple store and buy an iPod with a clear conscience (I got one a few weeks after the announcement)

9. My neighbor and I finally have something in common (he works for Apple)

8. The looks from my co-workers and customers (One ISV told me: "If you told me I'd ever see an Intel employee bring a Mac to a meeting, I'd say you're crazy"

7. Doubles as a space heater during the winter.

6. I can now help out at my son's school computer lab.

5. OsX is a beautiful operating system and has some neat apps (check out ComicLife)

4. Shell and u*ix utilities

3. Integrated video camera, BlueTooth, 802.11b, 5.1 sound/optical. No more silly devices hanging off my computer

2. Magnetic power supply connector. Why didn't someone think of this before?

And the Number One reason I like my MacBook Pro...

1. DUAL CORE!!! Blinding speed - video conferencing, image manipulation and DVD movies are snappy and smooth. OK, the last two aren't really work related but you get the picture. Even simple things like spell check and program loading seem faster. There are some performance limitations when using WinXP (no DMA disk, and video drivers), but I hear that these will be soon addressed in a new version of BootCamp.

Using Boot Camp is probably the easiest way. Use the new v1.1 beta - it adds support for several devices, most notably the iSight camera.

A couple of things:

There is no Delete key on the Mac keyboard. (It's actually a Backspace). This became obvious after I added my Mac to a NT Domain. After reboot, I was prompted to press "ctrl-alt-delete" to log in. Before you add the computer to the domain, remap a key (I used the F12 key) to a delete. There are several good utilities (I used KeyTweek) that do this. Be absolutely sure which WinXP filesystem you want to use (FAT32 or NTFS). I tried to convert my FAT32 to NTFS after the install and ended up learning how to stop a Windows XP disk conversion at startup - <ugly>command line registry edit</ugly>

Some brave individuals have successfully place OsX machines on the Intel network. Firstly, you need to get Mac OsX up to Intel's minimum security rules. This includes the installation of a specific anti-virus program, browser and OsX settings, and bug fixes. Second, Airport needs to be setup to support Intel's WiFi connection/authentication security. This can be done without the use of additional software. Since our software authentication token is not supported by OsX, a hardware token is needed.

To access internal file shares, simply to mount Windows-based shares using Samba. One annoying thing: by default, OS X places hidden .ds_store files in every network share folder it touches. To disable this behavior for all users on your Mac, execute the following from a Terminal window

$ defaults write com.apple.desktopservices DSDontWriteNetworkStores true

$ cp Library/Prefrences/com.apple.desktopservices.plist /Library/Prefrences/.

$ sudo chmod 777 /Library/Prefrences/com.apple.desktopservices.plist

Microsoft Office can be used for office productivity. All is not perfect though " Intel's IM, video conferencing and a lot of internal web sites don't work, so some employees use a backup WinXp system

We've got an internal Wiki page where a growing community of Intel Mac users contribute BKMs and help troubleshoot issues.

I can't wait to get my hands on a Core 2 Duo MacBook!

The unconference format was very interesting and I believe it was the best model for a conference of this type. It ensured that the conference covered the topics of interest to the attendees and increase developer to developer interactions. Look here for an San Jose Mercury News article on the conference.

I propose/hosted a session, "Mobile Mashups: Online/Offline/No Line" which was very well attended (>20).

We had a wide ranging discussion, but in the end most of the discussion was on platform/context awareness, e.g. the ability for Web 2.0 apps to get information about the device and its environment and state.

Key Learnings

The most pressing issue was how applications can adapt/dynamically generate UIs for platforms with different display, input, and output capabilities. For example, a smart phone with a 2.5" display and T9 input, a PDA with a 4" landscape display and pen input, and laptop with a 14" display and keyboard. We also identified othe important contexts: Connectivity, e.g. network state (online/offline), type, e.g. WiFi or GPRS; Power, e.g. charging/discharging, time remaining; and bandwidth, e.g. amount, quality.

We explore several use models including: determining connectivity state BEFORE trying to go to a web site. asking the user if they really wanted download a large file if they were on a low bandwidth network or low on power, etc. We demonstrated a JavaScript interface to retrieve device/context information with a web browser during the Speed Geeking session. Although just a prototype I believe it shows a lot promise in solving the problem for all the contexts. We may release it to the community so if you have ideas, inputs, or interest post to the blog or send me an e-mail.

Intel does have a platform/context SDK (Intel Mobile Platform SDK) for native applications (C++, .NET and Java). This SDK was use to "mobilize" the Elephant Drive client which we demonstrated (along with Amazon) at the Mashup University held a day before the Mashup Camp).

Review: Vendor Swag

As we all know, half the fun of attending a conference is the free swag. Here are my top three:

3. AOL - AOL gave out good looking t-shirts (good colors) that had single words such as "Geek" (very popular), "Open", and "Unwalled".

2. Intel - we gave out "Transformer" pens. Closed they looked like small (3") space ships. Push a button on the side and it unfurls into to a full size pen.

1. Google - Google gave out notepads with one of those prismatic covers (as you tilt it shows different images). Using images from Google Earth, the first image shows the Earth. As you tilt it zooms down to a picture of the Goggle HQ. Very cool

My NEXT post will talk about the MacBook Pro - my real life has been a bit hectic, and I wanted to get my impression of the Mashup Camp out early.

<cvv/>

My name is is C.V. Vick (don't ask... there was an unfortunate naming accident at my birth) and I'm a software architect in the software side of the Intel house. I must it admit it's a bit challenging (strange, surreal, Pythonesque?) to "do" software in a hardware company, but I believe it's important to influence our hardware groups to build the best platforms for software and ensure that software takes advantage of the platform. I'm sure we all can think of tragic examples where this was ignored.

I want the Mobile Community to be a place for open and frank discussions about all aspects of mobility: software, technologies, architectures, use models, problems, solutions, etc. Oh yeah, and hardware too. I'm going to share my experiences (good and bad) and thoughts on developing and using mobile software and devices, and the interesting and exciting software work being done inside and outside Intel. With the advent of "Web 2.0" and the explosive growth in mobile device users, I see some excellent opportunities to expand and extend the reach of web applications. In a couple of weeks at Mashup Camp, Shawn Casey (blog) and I are going to show some mash-ups we developed which explore some of these ideas. Stay tuned for more details.

Years ago I was interviewing for a product development job in a startup, and I had an interview with the founder. Before I had even sat down he asked me : "Are you a pig or a chicken?" With a blank face, I racked my brain searching for some tendril/handhold of context to say something intelligent or at least intelligible. After a minute or two, he let me off the hook, "In a breakfast meal, chickens are involved, but pigs are committed". In a way, projects, communities, etc. are comprised of pigs and chickens - it is the pigs that are the motive force behind ideas and innovation, while chickens provide the means to execute. A good pig converts chickens into pigs.

So, are you a pig or a chicken?

Next time: The Good, the Bad and the Ugly of running Windows XP on a dual-core MacBook Pro on a corporate network.