Recommended Posts

Here is a new video (Avalon Transparencies) straight from Paul showing how Avalon works with the windows (still called explorer?).

Nice alerts! I hope the error dialogues will be alerts now. That would make it sooo much nicer.

Actually it is.. some sort of.. in PDC 4051, if you try to plug a device not working, or with no driver, the error notification appears like this.

But when a soft crashes.. well still like before ^^

any one know what these new fonts are? and where i can get em?

http://msdn.microsoft.com/library/en-us/dn...ic_alerts10.gif

I believe this is Myriad Pro.

Interesting thing is that this is Apple's corporate font and all their products are branded in this. :unsure:

two questions....

where can i download myriad pro for free? i downloaded an apple font pack once i think from aquaxp.com but there download section is closed now.

also i cant beileve no one knows the music!! ive heard it on a car commercial before too. im gonna try to do some research

edit/update: the song is called Horn Dog and its by Overseer

Edited by MikeCoz

Just a note that MY netgear NIC FA311 is receiving Code 10 errors after drivers are installed. This didn't occur on Build 4015. This build is definitely picky on drivers. This could be a glitch as well who knows. Well off to finish my MS recertification.

From the screenshots I see the back button but where is the forward button?

The XAML looks exciting(M$ extending it's reach to the net.)

Wonder what will be the price of Longhorn once it's out in 3 years?

(My next PC will be DIY! no more brands for me)

The forward button is to the right of the Back button, but it is invisible because there is nothing to go foward to. And I think the back button is always there, but disabled if there is nothing to go back to.

Strange. Says it would take 10 minutes to set up hardware and it takes 30 to 40 minutes to do that on my machine. Couldn't believe how much freakin' memory is consumed for just EXPLORER.EXE! In 2000, it's slightly less than 5 MB. In XP, it's between 15 - 20 MB. In Longhorn, it's almost 70 MB! Something tells me that it's going to get even worse unless if one could optimize a version for lower end PC's.

Well it should be said one more time :

Alpha build = new things tested, lot's of time is spent on ideas

Beta build = debug, speed up parts, as well as keeping only best ideas from alpha build. A lot of interim builds are released during that time to tweak, debug, track any problems found before.

RC build = (Release Candidate) then you enter the final phase, the time to tune up the os, not the best part but actually you are near to get the final product.

So where does belong the Pdc build ?... Alpha build, so please people be realist on what you may think/believe/see/say : It's an alpha build, so it's basically a show case of what to come. Not the product you will be playing with and whine in 2 years :) ! It's like you see a cake not even baked and say :"awfull" after tasting it...

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft launches Godot Sample to streamline Xbox PC game development on the engine by Pulasthi Ariyasinghe Microsoft today announced a new endeavor that aims to make it simpler for Godot developers to get their products into the Xbox PC ecosystem. Dubbed the "XBOX Godot Sample," this is a new public reference for developers using the open-source engine. This is set to serve as an example of how Microsoft GDK, Xbox Services, and PlayFab can be integrated into their projects. The sample is available now on GitHub as a working example. This covers key features in gaming projects that developers may need to release their projects on Xbox PC, with everything from matchmaking and game sign-in to gamepad compatibility with Godot being covered. This release is being called the first step in giving Godot developers the tools to bring their games over to Xbox PC, with more changes to come based on feedback and issue reports. However, the company was clear that this is not related to bringing Godot projects to Xbox consoles. The engine's open development model stops it from accessing console SDKs due to the requirement of NDAs and legal contracts. Here's how it explained this Godot sample project's focus: This is a source-only sample, not a product. It's MIT-licensed at the wrapper layer; the GDK and PlayFab dependencies still require their own installs and license acceptance, consistent with our other XBOX samples. There is no set update cadence for support or maintenance. We’ll watch the repo, monitor issues, and iterate where it makes sense, but this isn't a commercial release. That said, we’re excited to hear your feedback and see any community PRs, as we evolve this together. This is the first step in bringing Godot for XBOX on PC. We plan to evolve it over time based on what the community tells us is most valuable. This sample is built specifically for XBOX on PC. It doesn’t include support for XBOX Series X|S or XBOX One. If you’re already building for XBOX Series X|S or XBOX One, please talk with your XBOX representative. If not, you can get started by signing up here. Game developers can find the XBOX Godot Sample by heading to GitHub over here. Documentation on how to get started with Godot for building an Xbox PC project can be seen here.
    • I don't understand the vision. Do people really want to buy a new computer from Dell with 6 browsers installed? We all keep asking for Microsoft to stop having so much junk on their OS, and adding a bunch of browsers seems to go against that. Ideally, we would just be asked what browser we want during OOBE but Google is just going to pay Dell a bunch of money to include Chrome. Additionally, would you want your phones to start including all the browsers too when you get them? The only thing I ever wanted was to be able to uninstall IE or edge and I believe you are now able to. I do agree that microsoft needs to chill with their "are you sure you don't want to try edge before you install chrome" ads when going to download chrome.
    • It is notable that around 70% of web browser users choose Google Chrome. However, it is puzzling why anyone on Windows would opt for Chrome when Microsoft Edge is often superior in many aspects and comes pre-installed. Edge collects less data, uses less RAM, and is more optimized for Windows as a native Microsoft product. While some may point to bloat in Edge, much of it can be removed with simple tools, requiring no more effort than installing Chrome. Meanwhile, Chrome reportedly downloads large amounts of AI data (4 GB) without explicit consent. I'm sure you Chrome users love that, or? Here is one example of a tool that doesn't even need to be installed to be able to use: https://github.com/TheBobPony/MSEdgeTweaker Although Microsoft’s aggressive promotion of Edge may be questionable, the browser’s current advantages make it a preferable choice over Chrome today, even if Chrome may have been better in the past.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      468
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!