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

    • Anthropic introduces Claude Tag, a new AI teammate for Slack by Fiza Ali Anthropic has announced Claude Tag, a new feature that lets teams work with Claude directly inside Slack. The idea is simple: once Claude is added to a Slack workspace and given access to selected channels, users can tag @Claude in conversations and assign tasks. Claude can then work through those requests using connected tools and data sources before posting its results back into a Slack thread. What makes Claude Tag different from a typical chatbot is that it's designed to operate as a shared assistant for an entire team rather than a single user. Everyone in a channel interacts with the same Claude instance. This allows the team members to see ongoing work and continue tasks started by others. Furthermore, Anthropic says the AI can build context over time by following conversations in channels where it has permission to operate. This means users don't have to repeatedly provide the same background information for every request. The system is also designed for asynchronous work. Instead of waiting for responses in a chat window, users can assign a task to Claude and return later once the work is complete. Anthropic says Claude can break larger requests into multiple steps and use connected tools to complete them. Moreover, the system can also schedule follow-up tasks and continue working on projects over extended periods. Another feature allows Claude to keep the users updated and follow up on unresolved tasks when its optional "ambient" mode is enabled. The company says the tool is already being used internally for software development, data analysis, support workflows, and debugging. According to Anthropic, around 65% of its product team's code is now generated through its internal version of Claude Tag. For organisations concerned about security, administrators can control which channels, tools, and data sources Claude can access. Separate Claude instances can also be configured for different departments, helping keep information isolated between teams. Administrators can also monitor activity logs, review completed tasks, and set spending limits at both the organisation and channel level. Claude Tag is now available in beta for Claude Enterprise and Claude Team customers and runs on Claude Opus 4.8 that was announced this May. The feature will also replace Anthropic's existing Claude in Slack application, with current users able to migrate within a 30-day migration window. Lastly, eligible customers will receive introductory credits to help teams evaluate the new experience.
    • Beats Studio Pro wireless over-ear ANC headphones drop to their lowest price yet by Fiza Ali Amazon is currently offering the Beats Studio Pro headphones at their all-time low price. The Studio Pro use 40mm active drivers which are designed to improve clarity and reduce distortion compared to previous models, with up to an 80% improvement over the Beats Studio3 Wireless. A built-in digital processor adjusts frequency response to keep the sound balanced rather than overly boosted in any one area. They also include Active Noise Cancelling that adapts to your surroundings to reduce background noise along with a Transparency mode that lets outside sound in when you need awareness of what’s going on around you. Furthermore, the headphones support personalised Spatial Audio with dynamic head tracking as well as Dolby Atmos playback on supported content. Moreover, built-in voice-targeting microphones improve call quality. You can also switch between three sound profiles including Beats Signature for balanced music playback, Entertainment for films and gaming, and Conversation for clearer voice in calls and podcasts. Physically, they are designed to be worn for long periods without feeling heavy or awkward. The ear cushions use UltraPlush engineered leather while metal sliders allow you to adjust the fit. On the connectivity side, the Studio Pro use Class 1 Bluetooth for a stable, long-range wireless connection. There is also a 3.5mm input if you want to plug in directly, including use with in-flight entertainment systems. Controls are located on the headphones and include a "b" button for music and call control, a volume rocker, and a multifunction button used for switching listening modes, EQ settings, power, and pairing. In addition, the headphones offer integration with both Apple and Android devices. On Apple devices, they support one-touch pairing with iCloud-linked devices, hands-free Siri access, Find My tracking based on last connected location, and automatic software updates. On Android devices, they support Google Fast Pair, Audio Switch between compatible devices, and Google Find My Device tracking, with additional features available through the Beats app. When it comes to the battery performance, it is rated at up to 40 hours of listening time with ANC turned off, and up to 24 hours with ANC or Transparency mode enabled. A 10-minute Fast Fuel charge should provide up to 4 hours of playback. Finally, the headphones use a rechargeable lithium-ion battery and charge via USB-C. Beats Studio Pro Wireless Over-Ear ANC Headphones: $149.95 (Amazon US) Good to know This Amazon deal is U.S. specific, and not available in other regions unless specified. We only use first-party seller links (at the time of article publishing); ensure that you purchase from a first-party seller link only. Check out Today's Deals on Amazon | or our recent tech deals. Become a Prime member (for Students or SNAP) via Neowin Get Prime Access - Prime for half price (for qualifying Medicaid, EBT, SNAP) Subscribe to Prime Video, Audible Plus, Music Unlimited or Kindle Unlimited via Neowin As an Amazon Associate, we earn from qualifying purchases.
    • "lets you pause updates by choosing an end date, for up to 35 days" Wasn't it "indefinitely"?
    • Those extra reboots are related to the UEFI Secure Boot certificate update thing.
    • Hands on with the ProtoArc EM25: Affordable ergonomic mouse that focuses on the right things by Taras Buria ProtoArc is known for making all sorts of office products with a big focus on ergonomics and comfort. Its latest product, the EM25, promises a comfortable-to-use, affordable, and customizable mouse. We took one for a spin; here are our impressions. The ProtoArc EM25 is a $49.99 mouse, but right now, during Prime Day 2026, you can get it for just $37.99. Right off the bat, you can see that the EM25 is inspired by Logitech's MX Master lineup and the legendary MX Master 3/3S. Its shape and proportions are very similar, so for a person with large hands (right-handed person, mind you), the EM25 is very comfortable to use. The mouse fills the palm, and the thumb rests on a small extension, giving your wrist a small tilt to reduce strain. The mouse is made of black plastic without any coating, eliminating long-term wear concerns. However, I can see the main buttons and other areas you touch the most getting polished over time. Despite its size and bulk, the mouse is not too heavy. It weighs about 100 grams, which is significantly less than the MX Master 3S and its successor. It is no lightweight gaming mouse by any means, but it is not excessively heavy like the MX Master 4. The EM25 has a built-in storage for its USB dongle. It is a cleverly made magnetic flap that you open by simply pressing on it. Next to the flap, you will find the on/off switch, the 1,000 Hz sensor, and a DPI button (up to 8,000 DPI). I find the DPI button location a bit odd, and I would prefer it somewhere below the main scroll wheel. Still, given that I never change DPI on my mice, I will let it pass. What is more important is that, unlike MX Master 3/3S/4, the device switch button is located below the left-click button, which allows you to switch devices without lifting and flipping the mouse. For a multi-device setup, this is a perfect solution: the button does not require too much effort to use, it does not get in your way, but it is also easily reachable with your thumb. The main scroll wheel has two modes: ratcheted and free-flow. You can only change between them with a bright orange button (I like this little touch of color), which is sprung and requires some effort to press. The wheel is dead-silent in free-flow mode, but ratched is quite loud and stiff, perhaps even too much to my liking. I can hardly call it deal-breaking, but it will certainly take some time to get used to. The side scroll wheel, it is notched, silent, and pleasant to use. Next to it, you can find a piece of glossed plastic with connection indicators: Dongle, Bluetooth 1, Bluetooth 2, and the low battery indicator. By the way, the built-in battery is rechargeable via a USB Type-C cable, which is included. It is sleeved and has an orange velcro strap to keep it tidy. After using the EM25 for a few weeks, I can say that its main buttons are my absolute favorite. They have very pronounced clicks, which feel great with just the right amount of force required to register a press. I would say they feel like something in between regular mouse clicks and silent ones. You can hear and feel the springy switch, but it is not sharp or loud to the point of annoying you. As for back/forward and device switch buttons, they are very clicky and quite noisy. Unfortunately, there are no extra buttons that you can map to specific things like in the MX Master lineup. Besides great primary clicks, another thing I like about the EM25 is its 1,000 Hz sensor. In the world, where Logitech still uses 125 Hz sensors in $100+ mice, seeing a much faster sensor in a mouse that costs three times less is very refreshing. Also, all the settings and customization you make are stored on-device, and you do not need to install any software. Just open the web-based app and change all that you need. Speaking of customization, you can remap what buttons do, adjust the DPI, and the sensor speed. Sadly, gestures are not supported, but you can still map pretty much anything to each button, including shortcuts, media buttons, and more. I also recommend using software like XMouseControl, as it will let you remap the side scroll wheel. At the end of the day, the ProtoArc EM25 is a great mouse. Clearly inspired by the MX Master lineup, it takes the best of it and complements it with a much more wallet-friendly price tag, significantly better sensor, on-device memory, a built-in storage for the dongle, and more (it fixes everything that I complained about the MX Master 4 recently). And for only $37.99 during Prime Day, the EM25 is an easy recommendation. Buy ProtoArc EM25 mouse - $37.99 | 24% off with Prime As an Amazon Associate, we earn from qualifying purchases.
  • Recent Achievements

    • Rookie
      DaviKar went up a rank
      Rookie
    • Dedicated
      HidekoYamamoto94 earned a badge
      Dedicated
    • One Month Later
      timbobit earned a badge
      One Month Later
    • One Month Later
      nates earned a badge
      One Month Later
    • Week One Done
      Almohandis earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      460
    2. 2
      +Edouard
      161
    3. 3
      PsYcHoKiLLa
      110
    4. 4
      Michael Scrip
      81
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!