Recommended Posts

looks great could we have one with a system task bar at the top instead of the side as in the original longhorn 4074...what colour was it? sorta transition to mauve or red in the my documents folder :)

sorta like this

http://www.only4gurus.com/v2/longhorn/page...051_072_jpg.asp

or this

http://www.winsupersite.com/images/showcase/4074_ui_05.gif

thanks keep up the good work by the way!

I don't think double panel at the same side will look good. I make top panel because Aero Slate use gradient style.

Hey I've seen a theme very like that, though it looks like you've really borked it up, did you mod someone elses theme?

I ported this theme myself from WinHEC screenshots for long time ago (About 7 days after shot leaked) but not as this one due to my skinning experiences and old resources. If you mean KoL's work, he ported from the same sources but look different from me if you check it carefully. Each resource is totally different.

post-34-1091391922.jpg

I don't think it will look similar to stefanka's work too. If you mean toolbarbackground, he recaptured it from screenshots too as I but my curve looks different with more accurate for Longhorn work and different patterns. If you notice, KoL and stefanka uses the same captionbar button style but they ported from the same source anyway.

post-34-1091392558.jpg

Yeh but the reason why they've changed it is because it doesn't look very good having a large lighter blue colour over two toolbars. Having it too accurate, when it's hard to port the other features, doesn't always work. But that's JUST a difference of opinion...

I would choose none, sorry, but please stop those bad Longhorn Imitations...you think they are cool? NO! You think you can make Longhorn look good by adding your own graphics? NO! why do you always make the titlebar thicker than it already is? And why are you always using wrong captionbuttons or making them look like they are split up?!? If you are going for the Longhorn look, then please do it right! And after KoL's port there is really no need more for more Longhorn themes! We have every style from Longhorn in so many variations, you just can't think your work looks good compared to the ones we have now!! Also, just because you think you were born to make Longhorn themes doesn't mean you have to show us "concepts" of new ideas every day...please stop it!!!!!

I too, wonder why you still try to make Longhorn themes. I mean is it that hard to wait till what Aero actually looks like rather than making ports of a alpha release purely just to act as a placeholder for the new graphics. I mean each leaked build, you seem to make a port of it, and honestly, its hardly anything like what it looks like. So why don't you just wait until Microsoft employees actually come up with the REAL aero.

Also one thing I don't understand is why you keep naming your work after Microsoft's work. Longhorn, Aero, Jade, etc etc. I mean you didn't actually make them, you just copied their graphics and style and then put it in a Windows XP theme and released it and claimed it as your own.

I would choose none, sorry, but please stop those bad Longhorn Imitations...you think they are cool? NO! You think you can make Longhorn look good by adding your own graphics? NO! why do you always make the titlebar thicker than it already is? And why are you always using wrong captionbuttons or making them look like they are split up?!? If you are going for the Longhorn look, then please do it right! And after KoL's port there is really no need more for more Longhorn themes! We have every style from Longhorn in so many variations, you just can't think your work looks good compared to the ones we have now!! Also, just because you think you were born to make Longhorn themes doesn't mean you have to show us "concepts" of new ideas every day...please stop it!!!!!

I did it before KoL and that's my variation. I use big captionbar text because Aero did from screenshots. I use another captionbar because I don't want to make my themes look crippled with fake background trick. I wonder why everyone who make their own work and post it here ged positive feedback and everything I posted will turn to moron war. For name, you must blame ike too because he named it as Microsoft's name too. Grow up, dude. I can make exactly port easily but I just don't want to make in its way you like as Longhorn nuts being.

Yet all graphics I've used are what from Longhorn without remaking or modification at all. Perhaps you just wanna get me down with reasonless post.

I would choose none, sorry, but please stop those bad Longhorn Imitations...you think they are cool? NO! You think you can make Longhorn look good by adding your own graphics? NO! why do you always make the titlebar thicker than it already is? And why are you always using wrong captionbuttons or making them look like they are split up?!? If you are going for the Longhorn look, then please do it right! And after KoL's port there is really no need more for more Longhorn themes! We have every style from Longhorn in so many variations, you just can't think your work looks good compared to the ones we have now!! Also, just because you think you were born to make Longhorn themes doesn't mean you have to show us "concepts" of new ideas every day...please stop it!!!!!

Although Im not Longhorn crazy, I dont think that your comments serve any purpose whatsoever apart from annoying everyone else.

Everyone's entitled to do their own mods.

So if you dont like it, get out and stop trolling.

@Windows X

Its looking good so far, Id like to see you do some more with the captionbuttons and scrollarrows.

You say you are making these right now? That's great, but they have already been done. Just have a look. Now if you could make a theme that looked like that Photoshop-only project, that would be freakin' sweet!

you should have like three different cariations of the theme for specific wallpapers and overlay them on the taskbar in the theme (if that would even work) giving theillusion of a transparent taskbar.

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

    • No registered users viewing this page.
  • 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

    • One Month Later
      Sharbel earned a badge
      One Month Later
    • 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
  • 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!