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

    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • 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
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!