This report describes many of the key points from that meeting and it is delivered just internally (at Microsoft) by Marshall Brumer. Added to his circulation are some executives who did not attend the meeting with Intel. These include Bill Gates, Steve Ballmer, and Paul Maritz.

Microsoft set up an internal site, http://msintel — something which it has done for various other issues like “linux”. We saw this here for example.

Here is a gem on security:

- Security – We have been stuck in this area-for a while. We are working to setup a meeting that is basically a go/nogo meeting to identify the areas we can/will work with Intel on and move forward. They goal is to cut through some of challenges in this area in one giant step and move on.

Here is a bit about drivers:

- Driver Signing at Intel – Intel is creating a large focus behind drivers and driver quality. They are creating a completely separate organization to createt/test drivers outside the silicon groups to better align the driver goals with quality rather than silicon schedules. We are supporting their efforts and working on a plan to let Intel self sign their drivers over the long run.

This says nothing about Linux and yet, Gates could not help uttering in response to this:

Is Intel planning to write drivers for Linux? This huge driver group scares me. Its them doing something we should do and they will do it cross OS in a way that could be a real problem for us. Maybe not but we should find out whether this is the case.

Gates said this only to a reduced number of people who are closer to his high circle (Veghte, Allchin, Maritz, among a few more) and it’s marked “confidential”.

Why was Gates so concerned about Linux despite the fact that it was not mentioned in the report? Let’s not forget his attempt to sabotage ACPI for Linux. Also, what’s so wrong with “cross OS”? Can Gates not tolerate competition? Is he interested in making microchips Windows-only?

Going back to the report, here is an interesting bit:

Intel is concerned that ‘we’ are missing the boat in the value platform area down at the ‘lnternet Appliance’ offering. Pat is the one who is very charged up over this. He sees us completely missing the boat with both the IA architecture and Windows being of no value here unless we move the PC down into that space (rather than what is currently happening with other platforms moving up into that space.)

The report also mentions NC, which we covered before and have lots more in store about (how Microsoft turned Intel against NC). There are many exhibits that we need to organise and process in order to show them properly.

The latter mention of NC includes:

Jim’s position is that this is the NC all over again in the consumer space. Most folks in the room agreed with this thinking and that since we had handled this before ala NetPC, that we could do this again. There is more work to be done here and David agreed to drive the thinking at MS and work with the right folks at Intel to explore this area. I will work with Dan Russell at Intel to get the joint parts of this going.

This is a funny:

Intel believes that they are more engaged with the consumer folks than MS (ala 5C) and thus we don’t get the picture.

Then it returns to drivers:

Driver Signing Discussion
Intel wanted to stress to us their committment to better drivers and ultimately being able to test and sign their own drivers. They are building up a huge number of people (~450) to work in this area. These folks include a driver software quality lab, platform driver quality lab and software qualification process team. Overall, the broad goal is to do driver development completely separate from silicon development so the goals of the driver folks are not put second to the goals of the silicon guys, At Intel, this means that the driver guys having a quality goal rather than a ship date only goal. This is good for us and good for Intel.

WHQL is working on a plan with Intel to implement this and things are looking good. The only real sticking point is what happens to Intel if they sign a driver that really should be failing. MS wants to reserve the right to pull the signature and Intel does not want this to ever happen. We will clearly revisit this issue, but still need to make this happen going forward.

We also need to make sure that part of the process at intel is to always be in sync with the development group within MS that is shipping the OS the driver supports. We cannot afford to have Intel doing their work and just sending us a ‘completed’ driver at the end of the process. Intel agrees with this and we will drive to make sure this is part of the process.

Is Intel planning to write drivers for Linux? This huge driver group scares me. Its them doing something we should do and they will do it cross OS in a way that could be a real problem for us. Maybe not but we should find out whether this is the case.

Microsoft/intel Confidential
Executive SummmyWe met with Intel today to continue our executive roadmap disclosures and to discuss current high level issuesbetween the companies. This meeting followed a Win64/IA64 meeting also held at Intel that either OnLee or MikePo
should be sending notes on.

The roadmap details are below and slides should up up on http://msintel as soon as we have them from Intel. Intelroadmap highlights include:- Mainstream/Server/Workstation lines will be >600 MHz by EOY99 and all hit 1GHz in 2000.
- Value line at 500 in 99 and 600 in 00.- Mobile > 600 in 99 on.18micron up to 7xx in 00.- Intel’s process technology now on a 2 year treadmill vs 3+ years in the past.- Biggest hole is lack of Willamette details that we will work to rectify in next 1-2 weeks.

Prior to MS presenting our overall plans for Windows 2000, Windows 98 and Windows CE, Jim briefed the group onoverall, picture of an upcoming MS reorg that includes him taking over the executive role in the Intel relationship.

Key issues discussed inlude:- Server working relationship – how to better engage one another in this space for positive customer ourientedresults. Brian Ball introduced and tasked here with driving for good results with Intel in this space. There is much
we can do here with renewed focus on working together at both companies.- 'Value Platforms’ aka ‘lnternet Appliance’ – Pat is very concerned that we need to create an offering in this space.We had a broad discussion about what this actually meant and did not really bottom out. Jim viewed this area as
the NC all over again in the consumer/intemet space. We agreed to get together with David Cole owning the MSthinking on this.- Security – We have been stuck in this area-for a while. We are working to setup a meeting that is basically a
go/nogo meeting to identify the areas we can/will work with Intel on and move forward. They goal is to cut throughsome of challenges in this area in one giant step and move on.- Driver Signing at Intel – Intel is creating a large focus behind drivers and driver quality. They are creating a
completely separate organization to createt/test drivers outside the silicon groups to better align the driver goalswith quality rather than silicon schedules. We are supporting their efforts and working on a plan to let Intel self
sign their drivers over the long run.

Details, action items and attendees below. Please send me mail if I got any of this wrong. Thanksl

- Mainstream – P3>600MHz in 99, Willamette 1GHz in 00. Willamette announce Q2/3 at 1GHz with new
instructions. We need to get the info on these instructions in house as some of this is new here (especiallytimeline and that this is now mainstream, not just workstation).- Value – Celeron at 50OMHz in 99, Timna at 600MHz in 00.
- Mobile – P3>600Mhz in 99, Mobile-Coppermine at 7xx/600Mhz in 00, Timna at 533 in 2000. .18 micron 2Q99 withP2 then into P3 in 3Q99 – First .18 micron from Intel is in Mobile.- A bit further out in the value line, Intel showed Coppermine128, Timna, then Pinecrest in .13 micron through 01 -
not lots of detail here just faster/smaller.- A bit further out in the desktop/mainstream line – Willamette through late 00, Northwood at .13 in late 01.- Further out on Server – Merced 00, McKinley 01, Madison (Perf)/Deerfield (Cost reduced), Yosemite (beyond
McKinley going up in perf) and then Gallatin following Foster a bit lower down in the map.- Intel is now on a 2 year cycle for process technology. They use to be on a 3+ year cycle. They are also startingtheir Mobile first on the new process when it is first introduced.
- Launches – Merced 3Q00, Foster 3Q00, Willamette 3Q00, McKinely 2Q01. Intel asked for us to be in sync with allthese and to deliver SW for them. There is much work to see where these all fit into our roadmaps.- They touched on wanting complete Geyserville solution going forward.
- Also noted that they now deliver their four products in parallel. They use to do two lines and are up to four.

Windows RoadmapJim started this area off with a description of some upcoming org changes that I will not go into in this mail. Overall,
the message was that Jim is now the executive in charge of the Intel relationship at MS. We then presented theWindows 2000, Windows 98 and Windows CE roadmaps and some slides on key features of each. We gave Intel
NON-public dates of 4/21 for Beta 3 and 10/26 for RTM. David explained the high-level overview of where we seeWin98/Win2000 splitting on consumer and agreed that we will spend more time with lntel on this as we have already
done on Win98 OSR1 work.

Server Strategy DiscussionJohn Miner presented a number of slides on the Server space and how Intel views this space. This was to get us intoa discussion on how to work better in this area. There have been some good and bad experiences here and the goal
was to get us moving forward more broadly. Brian Ball (welcome!) was named as the MS person to work more closelywith Intel on this front.

Their view in this area has changed from 95-98 scaling up and growing the market in the corporate world to 99-xx
focusing on Comm/lSP servers beyond the standard model we have today. They want to scale from top to bottom Inthe standard space and grow into the Comm/ISP world. They have spent a bunch of time with ISPs (8000 surveys
with 5000 ISPs) helping them form this mindset and now are asking us to engage with them in this. We should notethat they have already started much of this and did that with other OS folks and seemingly came to us late, but they
are now seeming to be interested in making this happen MS/Intel wise – we need to engage on that to determine realplans here.

Some specific areas they are working on- IA64 Developer lmplemetation Guide – This is sort of turning our Server Design Guide around on us. Our guide
(jointly authored with Intel) is a Windows focused guide telling folks how to build HW. They want a guide that isIA64 focused telling folks how to build SW/OSes/Peripherals and probably systems. We need to learn more in
this area and then determine if this is something we want to get involved in as it levels the playing field for the OSside of things whife using our input to do it.- NGIO – Much has transpired on this in the past 1-2 weeks. Intel has made drastic changes to the licensing model
and the openness of NGIO that is positive for MS and for the industry. MS has agreed to join both NGIO andFuture IO groups and we are now in the process of crawling through the NGIO agreements to make sure this is
truly something we can sign up for. We also agreed to put out our IO architecture requirements doc by the end of March.- Note that they have not bottomed out with Future IO folks so there still looks to be two of these. Tom made
clear here that we still have a goal of seeing there only be one architecture here and that we would beinterested in helping make that happen. Miner stated that there are already 4 companies trying to accomplishthis and adding a 5th would not be of any help.
- PAE – We are already pushing this a bunch and surprised by them not being happy about it. We will spend moretime with Intel on this one.- 8-way optimized benchmarks – Again, we need to get more tied into this one. Both sides are spending time here
and just need to be in sync and see what we can leverage by working together.

Intel has created the Intel 64 Fund to accelerate the completion of solutions for Merced. This fund is targeted to be$200M with money from lntel, 3-5 OEMs, and some eedy adopter end users corporations. The fund is targeted at
startups rather than existing companies that would be approached via normal (evangelism style) channels. The focus

MS01 0049155HIGHLY CONFIDENTIAL

is on creating solutions for shrink wrapped OSs (like NT) not for proprietary Unix’s. This is a creative idea that folks atMS are already discussing in other mail.

We bottomed out in this discussion agreeing that there was much we could work on together going forward and that
we would strengthen the relationship here with Brian now driving on our side. We will also stretch this more into themarketing space going forward.Value Platforms aka Internet Appliance discussionIntel is concerned that ‘we’ are missing the boat in the value platform area down at the ‘lnternet Appliance’ offering.
Pat is the one who is very charged up over this. He sees us completely missing the boat with both the IA architectureand Windows being of no value here unless we move the PC down into that space (rather than what is currently
happening with other platforms moving up into that space.)

The product they envision is for mail/browse/commerce. Jim asked Pat what they actually wanted us to do. Pat said‘make significant progress against – Ease of Use, Stability, Price and Simplicity to meet the needs for 2H00′. They
talked about this being a Windows 98 based appliance platform. They could not articulate broadly beyond that it wasOEM only and agressively legacy reduced and had a hard time answering David’s question of what would you take out
of the PC to make this thing work. Jim made clear that if this is truly a fixed function type device then there is not pointin doing the work from Windows as it is not a PC nor will it be.

Jim’s position is that this is the NC all over again in the consumer space. Most folks in the room agreed with this
thinking and that since we had handled this before ala NetPC, that we could do this again. There is more work to bedone here and David agreed to drive the thinking at MS and work with the right folks at Intel to explore this area. I will
work with Dan Russell at Intel to get the joint parts of this going.

Security DiscussionThere was a short discussion of the challenges we have had on working together in Security. Their opening slide was
‘Security – Collaboration or Collision’. This was a useful discussion to educate execs on both sides of what has beenhappening.

Our fundamental sticking points are around how we look at the space. We firmly believe that we need to get
ubiquitious core support to get Content to be authored for the PC rather than closed boxes and Intel does not see itthis way. Based on this fundamental disagreement, we are stuck on how to make the core part ubiquitous.

Intel believes that they are more engaged with the consumer folks than MS (ala 5C) and thus we don’t get the picture.An interesting point in their view is that they are only protecting content as it comes into the PC (via some wire like
1394), they are not worried about the content once there. We stated that there are many ways to get the content and itmust be protected once on the PC. Thus they think they can get good enough security above the CPU/OS rather than
at it’s core and we disagree. This is a good place to start our discussions going forward with lntel to see how toresolve this area.

The timing issue (not just ubiquity, but timing for getting things going) was another issue based on Intel’s waterfall
model. We understand and can agree to the Intel waterfall model, but cannot agree that all this must wait 18-36months to be in all CPUs and shared across to other vendors.

The other sticking point has been that Intel is not comfortable having a discussion with us under our standard CITA
terms or under extended CITA terms that would give them MORE rights to also build what they need in SW. They aresaying that they are not interested in signing away all their IP before even coming to the table here. Note that this is a
fundamental change to how we work together with Intel and is something that we need to address going forward as itwill surely come up again. Our current solution is to have a meeting that is not covered by CITA that will mainly map
out all the areas in this space that we could play together, identify the areas that we will and will not engage and thencover each of the engaging areas under CITA and get to work.

We are working to setup a meeting with lntel with the goal of coming out of the meeting with a map of what we will and
will not engage intel on.Driver Signing DiscussionIntel wanted to stress to us their committment to better drivers and ultimately being able to test and sign their owndrivers. They are building up a huge number of people (~450) to work in this area. These folks include a driver
software quality lab, platform driver quality lab and software qualification process team. Overall, the broad goal is todo driver development completely separate from silicon development so the goals of the driver folks are not put
second to the goals of the silicon guys, At Intel, this means that the driver guys having a quality goal rather than a shipdate only goal. This is good for us and good for Intel.

WHQL is working on a plan with Intel to implement this and things are looking good. The only real sticking point is

MS01 0049156HIGHLY CONFIDENTIAL

what happens to Intel if they sign a driver that really should be failing. MS wants to reserve the right to pull the
signature and Intel does not want this to ever happen. We will clearly revisit this issue, but still need to make thishappen going forward.

We also need to make sure that part of the process at intel is to always be in sync with the development group within
MS that is shipping the OS the driver supports. We cannot afford to have Intel doing their work and just sending us a‘completed’ driver at the end of the process. Intel agrees with this and we will drive to make sure this is part of the
process.

IDF and WinHEC AlignmentWe did not bottom out in this area. More work in a smaller group to happen here.

The more I read the more convinced I am of intentional sabotage in cases like the Foxcomm ACPI bios fiasco. Every level of the PC Industry has been sabotaged to break competitors – awful standards than will only work for Windows – OEM, Vendor, Analyst and Customer manipulation. Nothing goes untouched. The sooner M$ goes bankrupt, the better. My ACPI Sabotage Page has been updated with the much better Boycott Novell write up of the Foxcomm incident.

>> The more I read the more convinced I am of intentional sabotage in cases like the Foxcomm ACPI bios fiasco.

ACPI is a standard where, in industry today, half is implemented by closed source hardware that, in order for the hardware manufacturer to be able to survive in the market, must work with closed source Microsoft OS.

Now do two random groups doing closed source and using what appear to be proprietary MS extensions manage to sync up well without some sharing of source code knowledge (or at least without a good description of the extensions)? I don’t think so, and, additionally, the same likely is required for the base ACPI spec if it’s as flawed a spec as many have said. So, for both the base ACPI spec and for the MS extensions to it, hardware manufacturers require access to MS secrets in order to achieve interop with the monopoly MS OS.

If ACPI is a standard required by MS for hardware to be competitive in the MS OS market, then what we have is anticompetitive behavior by Microsoft and collusion by the hardware vendors in sharing certain secrets not available to other OS vendors and which other OS vendors would require in order to interop with the full feature set of the hardware. At least this is the case if the hardware vendor is giving Microsoft any extra value (quality or features). Clearly this extra value is being given to Microsoft at least in various circumstances and is also happening for other hardware besides over ACPI.

This is anticompetitive (leveraging monopoly to protect monopoly). And the only way this would not be “intentional sabotage” is if Microsoft was not aware of the consequences of creating secrets that would then be shared with hardware partners but not with other OS vendors. To believe Microsoft is not aware of these consequences makes about as much sense as to believe Microsoft is not aware of the difficulty of achieving interop with closed source and with bad specs. It’s a ridiculous notion to think that Microsoft is not extremely aware of this. You’d have to believe that Microsoft thinks they produce software without bugs, Microsoft always abides by the standard perfectly, the standards are perfect and complete. ..People, there is a reason vendors either share code with customers (eg, this always happens in the FOSS world) or else offer support for the bugs. No one that ever does either of these two fails to appreciate the imperfectness of software creation and the need for this help in order to help smooth out interop.

What really pisses me off, is even when you show people the documentation, most of them:

A) Don’t believe the documents are real
B) Think Gates was misquoted
C) Think that we are all delusional
D) Think that this is perfectly acceptable behavior by a CEO
E) Think that we are paranoid
F) All of the above

Pardon if what I wrote isn’t 100% logical, I should have gone to bed a couple of hours ago.

The lunacy of the EPO with its patent maximalism will likely go unchecked (and uncorrected) if Battistelli gets his way and turns the EPO into another SIPO (Croatian in the human rights sense and Chinese in the quality sense)

Another long installment in a multi-part series about UPC at times of post-truth Battistelli-led EPO, which pays the media to repeat the lies and pretend that the UPC is inevitable so as to compel politicians to welcome it regardless of desirability and practicability

Implementing yet more of his terrible ideas and so-called 'reforms', Battistelli seems to be racing to the bottom of everything (patent quality, staff experience, labour rights, working conditions, access to justice etc.)

"Good for trolls" is a good way to sum up the Unitary Patent, which would give litigators plenty of business (defendants and plaintiffs, plus commissions on high claims of damages) if it ever became a reality

Microsoft's continued fascination with and participation in the effort to undermine Alice so as to make software patents, which the company uses to blackmail GNU/Linux vendors, widely acceptable and applicable again