Recommended Posts

Hehe, nice, disabling the hardware check actually made it work for me...

Despite the User Experience SubSystem crash... :laugh:

Blur effects behind the transparent titlebar, never really noticed from the screenshots. And "folding" window openings... Posting an example.

post-21023-1114468714_thumb.jpg

Hehe, nice, disabling the hardware check actually made it work for me...

Despite the User Experience SubSystem crash... :laugh:

Blur effects behind the transparent titlebar, never really noticed from the screenshots. And "folding" window openings... Posting an example.

585829255[/snapback]

What video card do you have and what exact steps did you take to enable it?

It runs awfully slow here, albeit starting up - gets all the effects with no registry keys, just the DWM start command [not UXSS].

I have a Geforce FX 5600. Nothing too hot these days, really.

The "zoom effects" are actually quite smooth at least if it's about small windows. However, I get choppiness due to what seems to be hard drive work. I guess this early build isn't very optimized, and you'd really do better with 1 GB RAM; I only have 512 MB.

Oh and to enable the stuff in that screenshot, I only edited the registry to disable the hardware check and typed "uxss" in the Run dialog. Crash, but it works as long as you keep the crash window open. :rofl:

If I instead did the startup trick with RunDLL, I got similar results, but no zoom effects IIRC.

I'm also not really sure if it's a great idea to use *both* tricks (rundll + uxss) at once?

I have a Geforce FX 5600. Nothing too hot these days, really.

The "zoom effects" are actually quite smooth at least if it's about small windows. However, I get choppiness due to what seems to be hard drive work. I guess this early build isn't very optimized, and you'd really do better with 1 GB RAM; I only have 512 MB.

Oh and to enable the stuff in that screenshot, I only edited the registry to disable the hardware check and typed "uxss" in the Run dialog. Crash, but it works as long as you keep the crash window open.  :rofl:

If I instead did the startup trick with RunDLL, I got similar results, but no zoom effects IIRC.

I'm also not really sure if it's a great idea to use *both* tricks (rundll + uxss) at once?

585829342[/snapback]

You can create that reg key for UXSS, or just enable the service.

Start -> Run -> services.msc -> User Experience Session Management Service -> Automatic/Start

No crashing for me, but it doesn't work smooth at all, here is what I get.

post-37989-1114471147_thumb.jpg

Oh. Well. Yeah. That's great. Visual effects... and quite nice ones. Oh and I am especially very surprised that someone's Internet actually works cuz it sure doesn't here. Nor Wireless nor telephony networks work.

Well... for someone who waited one year just to see this, I am not surprised at all. Still full of bugs, has a messy interface (still a placeholder after 2 - 3 years of development? What's going on?), it's notreally usable, is not user-friendly at all unlike everything they said (it even makes things harder to do and more complicated to understand).

Now that's pretty much confirmed. May 24th, I am buying a Mac G5 dual. The whole thing. Windows Longhorn will be nothing but what I described up there. If they didn't manage to do much progress in one year, I don't see why I should give them another year or another year and a half (cuz first it's still not enough and second it's too far away)

did this (someone here can take the time to create the batch file as I can't be arsed to do it atm):

Open DOS and navigate to:

c:\windows\system32\

Type this:

rundll32.exe udwm.dll DwmClientStartup

That'll get your glass going. The buttons will be square still but the buttons will have the colors when you hover over them.

To start the effects, use the same registry hacks as you did for 4074:

Start > Run > Regedit

Navigate to:

HKLM>Software>Microsoft>Windows>CurrentVersion>Explorer

Create 2 new keys: MILDesktop and MILExplorer and give them both a value of 1.

Restart.

That's all I did to get where we got for the screenshots. Perhaps on the appropriate PC, the effects will be much greater. Enjoy. happy.gif

-Ref'X

It also looks like cpu killer has some Radeon LDDM drivers (on the DVD?).

:D

585828791[/snapback]

LDDM drivers are available for the 9500, 9600, 9700 and 9800 (and XT) series. If your exact card isn't in the list, choose the closest family, and if its lower than a 9800, use the EnableMachineCheck hack to allow DWM.

Oh. Well. Yeah. That's great. Visual effects... and quite nice ones. Oh and I am especially very surprised that someone's Internet actually works cuz it sure doesn't here. Nor Wireless nor telephony networks work.

Well... for someone who waited one year just to see this, I am not surprised at all. Still full of bugs, has a messy interface (still a placeholder after 2 - 3 years of development? What's going on?), it's notreally usable, is not user-friendly at all unlike everything they said (it even makes things harder to do and more complicated to understand).

Now that's pretty much confirmed. May 24th, I am buying a Mac G5 dual. The whole thing. Windows Longhorn will be nothing but what I described up there. If they didn't manage to do much progress in one year, I don't see why I should give them another year or another year and a half (cuz first it's still not enough and second it's too far away)

585829701[/snapback]

Judging by what we saw today I totally agree with you. Longhorn in it's current state really is a pile of dung. It feels like a dirty and buggy WinXP with bits and pieces sticking out all over the place. That being said, it isn't even in beta so why should we even get all dissapointed about it? I guess it's just hard to understand what they are doing over there with all that money, all those resources, and this is all they are able to produce after three years. We'll just have to wait some more (atleast 6 months) till the betas and RC's are out for a final verdict.

To enable it for other cards create a regkey

HKLM\Software\Microsoft\DWM\EnableMachineCheck (Dword) and set it to 0

after that uxss.exe enables the effects and crashes.. but if you just drag the error window to someplace where it doesn't bother you it seems to keep running.

This is the best way to enable it and it's really quite smooth on my 5600. But this isn't all the effects that are possible I would imagine.

It's still an alpha people, we are not in Beta yet, don't judge it until it is final.

Now that's pretty much confirmed. May 24th, I am buying a Mac G5 dual. The whole thing. Windows Longhorn will be nothing but what I described up there. If they didn't manage to do much progress in one year, I don't see why I should give them another year or another year and a half (cuz first it's still not enough and second it's too far away)

585829701[/snapback]

You're going to buy a Mac because you're not impressed, as an end-user, with an Alpha build of an operating system 2 years from release that was designed exclusively for hardware engineers and includes only the bits having to do with driver development on the only part of the OS that is basically complete (the driver framework, LDDM, and Metro).

That's about the most absurd thing I've ever heard.

Several people I know have seen Aero Glass. And that ain't it. Believe me, they've done a lot of User Experience work for Longhorn. But unless you're good buddies with Jim Allchin, you're not going to see it until next year when they want you to.

Oh. Well. Yeah. That's great. Visual effects... and quite nice ones. Oh and I am especially very surprised that someone's Internet actually works cuz it sure doesn't here. Nor Wireless nor telephony networks work.

Well... for someone who waited one year just to see this, I am not surprised at all. Still full of bugs, has a messy interface (still a placeholder after 2 - 3 years of development? What's going on?), it's notreally usable, is not user-friendly at all unlike everything they said (it even makes things harder to do and more complicated to understand).

Now that's pretty much confirmed. May 24th, I am buying a Mac G5 dual. The whole thing. Windows Longhorn will be nothing but what I described up there. If they didn't manage to do much progress in one year, I don't see why I should give them another year or another year and a half (cuz first it's still not enough and second it's too far away)

585829701[/snapback]

And it's for that exact reason that Microsoft isn't showing Longhorn's current state to the general public yet. You can't see what's changed under the hood, nor can you see the other builds - Microsoft have already shown off some of build 5060 so what's the point in judging an older (albeit the most recent we've seen) alpha build?

Oh I give up. Buy a Mac if you want, they're great machines, but I still think making such a comment on an OS that isn't even beta yet is quite pathetic. Being as the build was distributed for WinHEC attendees, it stands to reason that the fancy stuff isn't there yet. Sigh.

To enable it for other cards create a regkey

HKLM\Software\Microsoft\DWM\EnableMachineCheck (Dword) and set it to 0

after that uxss.exe enables the effects and crashes.. but if you just drag the error window to someplace where it doesn't bother you it seems to keep running.

This is the best way to enable it and it's really quite smooth on my 5600. But this isn't all the effects that are possible I would imagine.

It's still an alpha people, we are not in Beta yet, don't judge it until it is final.

585829885[/snapback]

this way works great!!! FYI

Maybe none of you were around back then... but development of Windows 2000 was much the same way. Pre-beta 1 was entirely unuseable. Beta 1 (still called Windows NT 5.0) wasn't even worth running. It was unstable, ugly, and had broken pieces everywhere. The beta 1 refreshes showed very little noticeable improvement. A lot of people thought it would never see the light of day. Then one day they posted beta 2 and announced the name change to Windows 2000 (one of the beta tester's jobs was to make sure all the branding got changed over properly). It still had a ways to go, but the progress from beta 1 was massive, and seemed to happen over night. It was an entirely different beast.

A beta 2 refresh came not much later and suddenly we realized what a massive overhaul this OS had undergone. By this time it was useable for most day-to-day tasks, and was quite exciting to test.

With beta 3 came the polish. Everything came together and finally made many of us go "wow, this is amazing. How did I ever live without this?" And the RCs just cleaned up one or two loose ends.

I expect Longhorn to be much the same way (even though there may not be a beta 3 since they seem to have stopped with those).

Some say it would be better for Microsoft not to show anything until it's ready for public view. And that's the problem... if you let anyone see this stuff, enthusiasts like us are going to eat up every ounce of it that we can get.

On the other hand, letting developers and hardware engineers get their hands on this early improves the user experience for the final product massively. No one wants to install Longhorn the day it comes out only to find that half of their hardware isn't supported. We all want Longhorn to ship with huge hardware support and some awesome new applications to show off the new platform.

If you want to critique Longhorn right now, critique the stuff that they're showing you... not the placeholder items like the UI. Critique the LDDM, since that's one of the largest focuses for this release. Critique the implementation of Metro, and the Windows Driver Kit that they handed out. That's what they want to hear about.

Beta 1 will probably be a more developer-oriented release (this one, for the most part, is not). Although nowadays Avalon and Indigo are being made available to developers without Longhorn, so that's not as important as before. So the real thing to watch will be beta 2. I doubt beta 2 will have the final look and feel of the OS... but it will be a much better indicator than this engineering technology sample.

Maybe none of you were around back then... but development of Windows 2000 was much the same way.  Pre-beta 1 was entirely unuseable. Beta 1 (still called Windows NT 5.0) wasn't even worth running.  It was unstable, ugly, and had broken pieces everywhere.  The beta 1 refreshes showed very little noticeable improvement.  A lot of people thought it would never see the light of day.  Then one day they posted beta 2 and announced the name change to Windows 2000 (one of the beta tester's jobs was to make sure all the branding got changed over properly).  It still had a ways to go, but the progress from beta 1 was massive, and seemed to happen over night.  It was an entirely different beast.

A beta 2 refresh came not much later and suddenly we realized what a massive overhaul this OS had undergone.  By this time it was useable for most day-to-day tasks, and was quite exciting to test.

With beta 3 came the polish.  Everything came together and finally made many of us go "wow, this is amazing.  How did I ever live without this?"  And the RCs just cleaned up one or two loose ends.

I expect Longhorn to be much the same way (even though there may not be a beta 3 since they seem to have stopped with those).

Some say it would be better for Microsoft not to show anything until it's ready for public view.  And that's the problem... if you let anyone see this stuff, enthusiasts like us are going to eat up every ounce of it that we can get.

On the other hand, letting developers and hardware engineers get their hands on this early improves the user experience for the final product massively.  No one wants to install Longhorn the day it comes out only to find that half of their hardware isn't supported.  We all want Longhorn to ship with huge hardware support and some awesome new applications to show off the new platform.

If you want to critique Longhorn right now, critique the stuff that they're showing you... not the placeholder items like the UI.  Critique the LDDM, since that's one of the largest focuses for this release.  Critique the implementation of Metro, and the Windows Driver Kit that they handed out.  That's what they want to hear about.

Beta 1 will probably be a more developer-oriented release (this one, for the most part, is not).  Although nowadays Avalon and Indigo are being made available to developers without Longhorn, so that's not as important as before.  So the real thing to watch will be beta 2.  I doubt beta 2 will have the final look and feel of the OS... but it will be a much better indicator than this engineering technology sample.

585830014[/snapback]

same with xp, hell these guys should have seen win95's beta releases.

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

    • No registered users viewing this page.
  • Posts

    • Segra 1.6.2 by Razvan Serea Segra is a free, open-source OBS-powered game recorder offering fast gameplay capture, instant clips, AI highlights, deep game integration, and seamless uploads—perfect for gamers, streamers, and content creators. Lightweight, fast, zero bloat. Segra key features: Automatic Game Recording: Begin capturing gameplay the moment your game launches, with zero manual setup. Instant Clipping: Save important moments instantly using a customizable hotkey—perfect for highlights, montages, or quick shares. Segra AI Highlights: Let Segra automatically detect kills, assists, deaths, and key events to generate polished highlight reels without manual editing. Gameplay Uploads: Upload recordings and clips directly to Segra.tv for fast sharing and cloud access. Deep Game Integration: Enjoy advanced game-data tracking across hundreds of supported titles, enabling smart highlight generation and stat-informed clipping. High-Performance Capture: Record up to 4K at 144 FPS using OBS-powered technology with minimal performance impact, supporting NVENC, AMD VCE, and custom quality controls. Segra Editor: Edit recordings easily with timeline controls, segment management, and event-based navigation to build the perfect clip. Customization Options: Adjust hotkeys, output formats, storage paths, codecs, capture quality, and performance settings for a tailored recording experience. Segra 1.6.2 changelog: UI: Improved the transition from the loading skeleton to the real content card. Security: Added Segra.dll code signing and automatic VirusTotal upload. Settings: Fixed the settings header to highlight Account when scrolled to the top. Recording: Updated OBSKit.NET to 1.4.1. Download: Segra 1.6.2 | 74.5 MB (Open Source) View: Segra Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Hey Google, these are the Gemini features I want in 2026 by Aditya Tiwari Google Gemini has been around for over three years. The AI chatbot started its journey back in 2023 (as Bard) when ChatGPT was already a talk of the town. However, it quickly attracted criticism after misrepresenting facts about the James Webb Space Telescope. The search giant spent a year fine-tuning Bard before rebranding the chatbot and its underlying generative AI model to Gemini, drawing inspiration from NASA's first human spaceflight program. Note that Bard was initially powered by LaMDA and PaLM 2; Google has since added several new features and integrations to Gemini. That said, there is scope for improvement and a gap for new features. I have been using Gemini for a while now and have realized that the chatbot lacks several features, making it harder for me to research across topics. These are mostly function-over-form updates that can improve the overall experience. Delete individual messages from a conversation Image via DepositPhotos.com One good thing about Gemini is that it can maintain context throughout the conversation. But things might get chaotic when you want to ask a related question, but don't want it to be part of your conversation in the long run. You can't ask that related question in a fresh chat because Gemini will lose the active conversation context of what you're trying to research. If Google allowed you to delete individual question/answer pairs, you could simply ask about a sub-topic and remove it from the conversation to create a smooth flow of important stuff. Offline mode Image via DepositPhotos.com A big pain of using Gemini daily is that everything loads from the cloud. It takes time for your chats to appear, and you can't view your conversation history while offline. To get a better idea, you can open the Gemini app and see how it looks without an internet connection. While Gemini models run in the cloud, it wouldn't hurt if Google could store chats (at least the text part) on the device so we can refer to them when offline. Google can also offer a lightweight version of its AI model to help with basic drafting, summarization, and other tasks. It has the Gemini Nano model, which can perform on-device processing on Google Pixel, Samsung, and some other Android brands, but it's a system feature and not related to the cloud-based Gemini app. Make temporary chats permanent I can't thank Google enough for taking the time and effort to add incognito mode or temporary chat mode to the Gemini app. It lets you have conversations without worrying that the topics will end up in your chat history or used for model training (at least on paper). Google claims that it doesn't use your temporary chats to "personalize your Gemini experience or train Google’s AI models." However, the data is stored "up to 72 hours to respond to you and to process any feedback you choose to provide." That said, I often start researching something in a temporary chat, only to realize the chatbot's answer is good enough to refer to later. Sadly, Gemini doesn't have an option to make such temporary chats permanent. In other words, I won't be able to follow up on it if I close the temporary chat. I'm left with alternatives like copying the answers into notes or another app. My digital life will get a lot better if Gemini gets a button to make temporary chats permanent. Collapse answers for a cleaner view You're heavily invested in your research game and suddenly feel the need to go up in the chat to recall something. This is when the conversation thread starts to feel like an overwhelming, unending wall of questions and answers. What if Google added a way to collapse Q&A pairs in the Gemini chat thread? It would look quite clean and easy to navigate. You'll quickly get an overview of everything you have discussed with the chatbot. Add buttons to jump between messages Suggested mockup of the feature. This reminds me of a small but useful Gemini feature that Google could add to its chatbot: the ability to hop between prompts in a conversation. Just add simple up- and down-arrow buttons, similar to YouTube Shorts, so people can quickly scroll through the messages. A table of contents or Chat Overview It's hard to get a bird's-eye view of everything you have discussed with the chatbot during a lengthy conversation. This is where a table of contents, or Chat Overview, displayed at the top of the screen, possibly in a drop-down button, might come in handy. You'll be able to get an overview of the chat and jump between messages, serving as an alternative to the up/down arrow buttons. Temporary mode for Gemini Live Image: Google You can use Gemini Live to have real-time conversations with the chatbot, which feels like you're talking to someone in the same room. However, a downside is that Gemini Live doesn't work in Temporary Chat mode, so all your conversations end up in the chat history. Google should consider expanding the temporary chat mode to include Gemini Live. Default to a specific chat One thing that feels somewhat annoying to me is that Gemini always opens in a new chat, whether on web or mobile. Sometimes, you want to return to your last chat. Google can take cues from web browsers, which let you choose whether you want to go to a new tab or a specific web page(s). Gemini can also have options to default to a specific chat when reopened. That said, generative AI chatbots have endless possibilities given the vagueness of their work. You can mold them the way you want by attaching different connectors, adding custom instructions, and including source files. It remains to be seen what Google has in store for future updates and whether anything from this wishlist gets the green light. The search giant released a stream of new Gemini updates in recent months, including Gemini 3.5 Flash and Gemini Omni Spark, adding that it now has 13 products with more than a billion users each. What do you want to see in the Gemini app? Tell us in the comments.
    • Thank you for the post. Just a FYI that links to an outside site or promoting specific software is considered spamming here. Asking general questions is fine.
    • I have been thinking about AI detector tools as a software workflow rather than a single "AI score" widget. When someone pastes text or uploads a document, the UI can return a report with a probability-style score, sentence highlights, reliability notes, and limitations. The useful part is that it can point a reviewer toward passages worth reading again. The risky part is that a polished score can look more certain than it really is. For people who build or review web apps, what should happen before the user copies or exports that kind of report? The minimum I would expect is: A clear input boundary for pasted text versus document files. Limits shown near the workflow, including minimum text length and maximum file size. A report label that says the result is a signal, not proof of who wrote the text. Sentence highlights and evidence notes alongside the global score. Reliability notes when the sample is too short or lacks enough sentence variety. False-positive and false-negative caveats that remain visible in copied/exported summaries. I am trying to avoid the pattern where a clean report card becomes the whole product story. For AI detection, "review this evidence in context" seems more honest than "trust this score." Would you keep the warning text visible on every report, or make it collapsible so the main result stays easier to scan? Disclosure: I work on a small AI detector/reporting workflow, but I am intentionally not linking it here. I am asking about software and report design, not promoting a site.
  • Recent Achievements

    • Conversation Starter
      sumytbe earned a badge
      Conversation Starter
    • One Year In
      B4dM1k3 earned a badge
      One Year In
    • One Year In
      DarkWun earned a badge
      One Year In
    • Dedicated
      Almohandis earned a badge
      Dedicated
    • Dedicated
      JuvenileDelinquent earned a badge
      Dedicated
  • Popular Contributors

    1. 1
      +primortal
      507
    2. 2
      +Edouard
      181
    3. 3
      PsYcHoKiLLa
      86
    4. 4
      Michael Scrip
      78
    5. 5
      Steven P.
      76
  • Tell a friend

    Love Neowin? Tell a friend!