Recommended Posts

that mini tile idea is crap!...

why do u need to show what the startscreen looks like?

also.

u have it in charms. why do u need it anywhere else? pointless.

it feels similar to the thumbnail you get in DP when cursor is near left edge (where it shows preview of prev/next app)

I don't expect many desktop side UI changes at this point tbh. I think the bigger molding of metro and the "desktop" will happen in Win9 after more people get use to the new UI/start screen.

I really believe that what we think of as the desktop is just going to turn into a part of the UI where you can manage/work with lots of apps together like now of course but even future WinRT apps not just older Win32 apps like we're getting in Win8. I don't expect a split between the two sections come Win9.

I also expect the next thing to go will be the systray in favor of a new notification area in the UI that will slide into view from the side or the bottom etc. Then the last part will be the taskbar itself.

brilliantly written post! :)

do read it. Very informative.

Im thinking that Steven talked alot about new devices coming from AMD and Intel. Im very excited. I want a x86 tablet and if the AMD low power PCs can give me the performance, battery life, slim and light design, they can have my money! :)

brilliantly written post! :)

do read it. Very informative.

Im thinking that Steven talked alot about new devices coming from AMD and Intel. Im very excited. I want a x86 tablet and if the AMD low power PCs can give me the performance, battery life, slim and light design, they can have my money! :)

And it also clears up some misperceptions (even mine) on why the multi-API support on Windows 8 outside of ARM exists.

I have called Immersive on x86/x64 a *superset* UI; apparently, I was severely underestimating the case.

Windows 8 on x86/64 is a *superset OS* - basically WOA-plus.

The blog post (and the video) point out that WinRT is, by design, CPU-neutral (which Win32 isn't). Writing to the WinRT API means that as long as the API support is there, the application will work. However, WinRT, with it being primarily designed for lightweight-power-miserly architectures (such as Ultrabooks and ARM) means that it isn't suitable for the heavier applications (such as Outlook or even Photoshop or Acrobat Professional). With WinRT, the CPU isn't relevant.

However, some heavier-duty productivity applications, existing games, existing applications, are simply unsuitable for WinRT. (Outlook. Acrobat Professional. The full version of Photoshop. MMORPGs - even the F2P sort. Etc.) Therefore, Win32 still has a place. That's where everything from higher-end tablets and slates (such as SAMSUNG's existing SERIES 7) to traditional desktops, notebooks, etc. and the Win32 API come in. There are times that a ball-peen hammer simply won't do.

However, here's where the big change from previous versions of niche-targeted Windows (WinMo and TPC Edition in particular) comes in - the learning curve goes away - completely. You still have the jackhammer - or even the sledgehammer - in your arsenal.

Yes - it's not what we're used to. (It's also not what Apple - or even Google - wants.)

Whoever would have thought that "Think different." (the old Apple slogan) could ever apply to Microsoft?

Everyone of these screenshots over the last couple of pages give me orgasms.

So excited for Gmail and calendar integration.

The Google Calendar integration is nice. The Gmail support isn't surprising in the least (mainly because Outlook has supported Gmail since it began, and added IMAP4 auto-configuration of Gmail accounts across all of Outlook two years back). I'm hoping that I can actually use Google Calendar with Outlook in Windows 8 (either the Consumer Preview or the finished product) without requiring an upgraded version of Office.

Interesting trivia courtesy of Long...

Photo EXIF evidence points to Windows on ARM before iPad release

Turns out Microsoft has been working on Windows on ARM for a while, quite a while in fact.

In Steven Sinofsky?s thesis of Windows on ARM (generically dubbed WOA) published on the Building Windows 8 blog today, two photographs of an early development build of Windows running on prototype ARM hardware dates the effort to as far back as 22 January 2010, almost a week before iPad?s announcement on the 27th.

Although Microsoft waited almost a year later to reveal WOA for the first time in public at a CES 2011 press conference, it?s now clear Microsoft too had future bets on an ARM-based ecosystem even before the iPad began selling and ARM took the spotlight for tablet devices.

As one might gather from Steven?s insight into the ARM development process, it became a lot more complicated to optimize the Windows experience on ARM than just porting all the code from one architecture than another. I think the dated photographs also reaffirm just how big of an investment this has been already with two years of development already in the bag.

Although no one can deny the influence the iPad has had and continues to have on Windows, Windows 8 is looking to level the playing field on ARM hardware with a vengeance. It?s safe to say WOA is not a knee-jerk reaction to the iPad, but a strategic move planned much earlier. But of course like most things Microsoft, with a longer lead time to market.

The NT kernel has been portable since the times of NT 3.x in the early 1990s. NT 3.51 and NT 4.0 ran on four different CPU architectures: x86, MIPS, DEC Alpha, PowerPC.

I'm pretty sure MS had an ARM build of NT running in their labs for years, just like Apple had x86 builds of all versions of Mac OS X running in their labs before the switch.

Long Zheng's findings are nice, but not earth shattering.

The NT kernel has been portable since the times of NT 3.x in the early 1990s. NT 3.51 and NT 4.0 ran on four different CPU architectures: x86, MIPS, DEC Alpha, PowerPC.

I'm pretty sure MS had an ARM build of NT running in their labs for years, just like Apple had x86 builds of all versions of Mac OS X running in their labs before the switch.

Long Zheng's findings are nice, but not earth shattering.

Well, I did say it's just trivia :)

OK, I requested canouna to try to dl Classic Shell and see if it could install and run in the beta build he has on hand, and here's the report:

http://forums.mydigitallife.info/threads/31998-Windows-8-Consumer-Preview-Discussion/page4?p=544698&viewfull=1#post544698

image_186.jpg

:s

This topic is now closed to further replies.
  • Posts

    • 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?
    • 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 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.
    • And with SO much better perf than the laggy mess that is Files.
  • 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
  • Tell a friend

    Love Neowin? Tell a friend!