Recommended Posts

The error window honestly has to be the best part. I mean I hate to keep starting flame but I just don't understand though. I mean I believe this is cool and everything, but the orginal OS X release had effects that equaled this and it doesn't make sense why we have to wait a whole year before it's not buggy. Why a whole year before the search is up to spotlight. Apple's been consistent with releases every year lately. I'm gonna use it (LH) when it comes out but god you have to wonder what MS is doing with all of the dough.

The error window honestly has to be the best part. I mean I hate to keep starting flame but I just don't understand though. I mean I believe this is cool and everything, but the orginal OS X release had effects that equaled this and it doesn't make sense why we have to wait a whole year before it's not buggy. Why a whole year before the search is up to spotlight. Apple's been consistent with releases every year lately. I'm gonna use it (LH) when it comes out but god you have to wonder what MS is doing with all of the dough.

585830442[/snapback]

Im sure MS isnt going for effects right now. Besides that error doesnt happen on the hardware it is meant for right now. There is no point for MS to bundle every freaking driver for it. They probaly only had it for for cetain hardware at WinHEC and maybe the majority of developers. Besides apple is so closed about their betas. ******s

How is that exactly?

585830444[/snapback]

didnt goolge patent that index technology? At least in search engines or w/e.

:EDIT:

Alt+Tab looks the same 2 me as it does in XP

How is that exactly?

585830444[/snapback]

You might remember the original big search engine: Yahoo (powered by Inktomi (sp?))

That said, thanks for the video Gelob. I think it's enough motivation to get and install this. Let's see if my GeForce 5700 is up to the task...

The error window honestly has to be the best part. I mean I hate to keep starting flame but I just don't understand though. I mean I believe this is cool and everything, but the orginal OS X release had effects that equaled this and it doesn't make sense why we have to wait a whole year before it's not buggy. Why a whole year before the search is up to spotlight. Apple's been consistent with releases every year lately. I'm gonna use it (LH) when it comes out but god you have to wonder what MS is doing with all of the dough.

585830442[/snapback]

Cocaine is a hell of a drug.
didnt goolge patent that index technology? At least in search engines or w/e.

585830452[/snapback]

The desktop search technology? LOL

The desktop search technology used in Longhorn (and MSN Desktop Search) is the same index technology used in the Windows 2000/XP Indexing Service, SharePoint Portal Server, SQL Server's full-text index, and other places. It's obviously enhanced to a degree, but mostly the work has been done on the interface and usefulness of the indexed information.

When Google released their beta of the Google Desktop Search tool last fall, the MSN guys nearly had a collective heart attack. They'd been working for months and months on the MSN Desktop Search tool and were only a couple weeks away from their first release. Several of them recently told me that they still don't know how Google timed their release so perfectly.

The desktop search technology?  LOL

The desktop search technology used in Longhorn (and MSN Desktop Search) is the same index technology used in the Windows 2000/XP Indexing Service, SharePoint Portal Server, SQL Server's full-text index, and other places.  It's obviously enhanced to a degree, but mostly the work has been done on the interface and usefulness of the indexed information.

When Google released their beta of the Google Desktop Search tool last fall, the MSN guys nearly had a collective heart attack.  They'd been working for months and months on the MSN Desktop Search tool and were only a couple weeks away from their first release.  I talked to several of them last week and they said they still don't know how Google timed their release so perfectly.

585830590[/snapback]

Ah!!!

Google must ahve sources then

Google, of course, uses their own indexing engine. But they certainly don't have any patents that affect Microsoft/MSN or Apple's offerings.

Besides that, before GDS, there were plenty of great tools like Copernic and X1.

Most of these effects (transparency, shadows, etc) are possible on Windows 2000/XP with GDI+. The problem is, driver support for per-pixel alpha blending and accelerated 2D stretchblts (among other features) are inconsistent and largely unpredictable. That's why the effects in WindowFX sometimes work great and sometimes don't work at all.

LDDM will change that. But more than this, it will move UI acceleration from using the hardware's 2D capabilities to using its (much more robust) 3D capabilities and its vertex/pixel shading capabilities.

Furthermore, replacing GDI+ with the DWM will yield a more consistent and clean user interface. When Longhorn is finished, gone will be the drawing artifacts you see when Windows XP is rendering a window. In XP, windows will often draw certain controls that aren't "ready" to be painted. In Longhorn, this won't happen.

There are a lot of other subtle changes that the DWM will bring. Overall the result will be a much cleaner, more sophisticated interface. Yes, OS X has a lot of this (but not all) already. But that doesn't mean it isn't welcome on Windows.

Did you ever think they do all that to test what it can handle and what happens in the final version. Besides who says there is a final version...

http://img191.echo.cx/img191/1981/dsc006139vm.jpg

585830149[/snapback]

Correction: Who says there is a COMMERCIAL version.

Pretty funny and interesting thing you found there. :)

And yes, this release looks like several "little pieces scattered around". But don't forget that it's the intentions with it too... It's supposed to be demo'ed at WinHEC, not used as a desktop OS. Don't forget that. ;) They've probably picked some features to demo that was fairly stable on the hardware they used, and there's probably some quite evolved hardware abstraction layer in this build too for driver developers, one of those under the hood things. Some evidence for this is that my card among others was detected and set up for LDDM, so there has apparently been some effort at driver development for Longhorn in this build.

The thing many of you who complain miss is that you aren't the auidence with this release. There's obviously very large Longhorn stuff not in this release because it's not the point of it... msh being one of those things...

But if you want a Mac, go ahead, please do!

Edited by Jugalator
Several people I know have seen Aero Glass. 

585829910[/snapback]

I get your point but its hilarious that you said that because no one except 12 people at microsoft and those 12 are the microsoft UX team have ever seen aero glass. what they likely saw is a demo of the glass theme which is nothing compaired to what aero glass and diamond user experiences will be when longhorn is rtm or anything similar to what those 12 guys are working on right now. :laugh:

The error window honestly has to be the best part. I mean I hate to keep starting flame but I just don't understand though. I mean I believe this is cool and everything, but the orginal OS X release had effects that equaled this and it doesn't make sense why we have to wait a whole year before it's not buggy. Why a whole year before the search is up to spotlight. Apple's been consistent with releases every year lately. I'm gonna use it (LH) when it comes out but god you have to wonder what MS is doing with all of the dough.

585830442[/snapback]

In the builds the released it had effects enabled, however they started the early work on it with Rhapsody in 1997, and even when 10.0 came out nothing in it worked except for the pretty animations and the dock, hell cd burning and dvd viewing were broken. So its not like apple pulled it out of their ass and everything worked from the first release.

I have a 6800. Can the LDDM driver be installed through manually updating the driver in device manager? Is there an option for the 5900 LDDM to choose from???

585831072[/snapback]

I have the 6600GT, and I tried the FX5950, no go. But there are many other drivers to choose from, unfortunitely, it lookis like we are out of luck though :(

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!