Microsoft "Athens" PC White Paper

By Ian W
in Microsoft (Windows)

 Share

Recommended Posts

Grand Master

Ian W

Posted
Posted

In my pursuit for information related to Windows "Longhorn" and Windows Vista I discovered that Microsoft had published a white paper for its "Athens" PC concept from 2003. I believe the white paper originates from the Microsoft Windows Hardware Hardware Engineering Conference web site. The "Athens" was a collaborative effort between Microsoft and Hewlett-Packard.

vzBjtpY.png

According to Microsoft the significance of "Athens" was not the device itself, but that it consolidated various hardware and software features previously included separately in a single device.

Some of you may believe that the PC isn't relevant anymore, and while technically true, the information is historically significant and may be of use to those looking for information about the subject. It is also fascinating to read about the technology and scenarios discussed in the white paper?such as appliance-like availability, audio communications, and Bluetooth connectivity?which are now commonplace.

https://web.archive.org/web/20031002214315/http://www.microsoft.com/presspass/events/winhec/docs/AthensPCWP.doc

Link to comment
https://www.neowin.net/forum/topic/1233441-microsoft-athens-pc-white-paper/
Share on other sites
Grand Master

goretsky Supervisor

Posted
  • Supervisor
Posted

Hello,

 

Interesting photo; it looks a little like an Apple iMac with an Apple Mac Mini behind it and an Apple iPad in front of it.

 

Downloading the white paper now.

 

Regards,

 

Aryeh Goretsky

Grand Master

Ian W

Posted
  • Author
Posted

Hello,

 

Interesting photo; it looks a little like an Apple iMac with an Apple Mac Mini behind it and an Apple iPad in front of it.

 

Downloading the white paper now.

 

Regards,

 

Aryeh Goretsky

It is somewhat interesting that you mention Apple. According to reports, when "Athens" was first unveiled, Microsoft and Hewlett-Packard were accused of imitating design elements popularized by the aforementioned company.

http://www.nytimes.com/2003/05/12/technology/12SOFT.html

Grand Master

bandit_liberty_rumble

Posted
Posted

 

"The one thing Apple's providing now is leadership in colors," Mr. Gates, the head of Microsoft , said at a conference for financial analysts at the time, News.com said. "It won't take long for us to catch up with that, I don't think." (2003)

 

:rofl:

 

Grand Master

MikeChipshop Member

Posted
  • Member
Posted

Go to 2:08  -- did this "hardware" guy really just commit the ul;ultimate geek faux pa ?  Calling the tower a CPU ?  Really ?  Just lost all credibility.

 

He was clearly referring to the main function of the white box. In that it's doing the brute work for the rest of the external systems. 

Grand Master

Ian W

Posted
  • Author
Posted

How is the PC not relevant anymore at all?

I guess it depends on how one looks at it. To some the PC may not be relevant anymore because technology has progressed, yet others will look at its historical significance and use that as a basis for their reasoning . . . The "Athens" is unlike other "Longhorn" innovations because most of the technology and features are here for Windows users to enjoy. It's not like the situation with, for example, the NGSCB. It has been over ten years and I am still not able to seal data to 'environments' of my choosing; barring Measured Boot in Windows 8 I am not able to send information about my software and/or hardware configuration to external requestors; other applications have access to the information in my graphics buffer, and et cetera.

Perhaps 'important' would have been a better word to use other than 'relevant.' If I could, I would update my previous statement.

  • 2 months later...
Grand Master

+Warwagon MVC

Posted
  • MVC
Posted

true, but calling it a CPU is exactly what non-techies do. 

It was shocking

 

They call it the CPU or The Modem. They call it the computer sometimes too, but half the time they are actually referring to their monitor.

This topic is now closed to further replies.
 Share
Go to topic listing

  • Posts

    • Waymo recalls self-driving software after cars enter closed freeway work zones

      By zikalify · Posted

      Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • Microsoft confirms Recycle Bin bug across all versions of Windows

      By snowy owl · Posted

      I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs

      By hellowalkman · Posted

      Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • My favorite file manager for Windows 11 finally gets a long-requested feature

      By Malisk · Posted

      And with SO much better perf than the laggy mess that is Files.
    • The official Funny Pictures thread

      By Steven P. · Posted

  • Recent Achievements

    • First Post
      BizSAR earned a badge
      First Post
    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done

  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      80
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      69
    Show More

  • Tell a friend

    Love Neowin? Tell a friend!