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

    • When will the Photos app be updated to remember the window size and position when reopened? They addressed this issue in a 2024 version of the app (though I can't recall the build number). Unfortunately, after that specific version, the problem persists! Please prioritise this fix in your K2 schedule. Additionally, the Snipping Tool has lost the ability to capture the Windows Taskbar starting from the 2024 version!
    • Same, never saw it on Android or iOS. Guess only some people got it *shrugs*
    • Anthropic pulls Fable 5 and Mythos 5 after US export control order by Pradeep Viswanathan In April this year, Anthropic launched the Claude Mythos Preview frontier model with state-of-the-art cyber and coding capabilities for a select set of companies around the world. After preparing appropriate guardrails, early this week, Anthropic launched Claude Fable 5 and Mythos 5, its most capable AI models. Claude Fable 5 is for general users and comes with strict safeguards, while Mythos 5 is designed with fewer safeguards for cybersecurity and biology use cases. Today, Anthropic abruptly suspended access to its Fable 5 and Mythos 5 AI models for all customers after receiving an export control directive from the US government. The company received the directive from the government today at 5:21 p.m. ET, and the received letter did not provide any details regarding the national security concern. Anthropic understands that the government became aware of a method to bypass, or “jailbreak,” Fable 5, which might be the reason behind the directive. The order was issued under national security authorities and requires the company to suspend all access to Fable 5 and Mythos 5 by any foreign national, whether they are inside or outside the United States. The restriction also applies to foreign national employees working at Anthropic. As a result, the company has disabled both models for all customers to ensure compliance. Access to previous Anthropic models like Opus and Sonnet is not affected by this government order. The company highlighted that it had developed strong safeguards to reduce the possibility that Fable is misused for tasks related to cybersecurity. In fact, many developers are complaining that the safeguards are going overboard. Additionally, the company worked with the US government, the UK AISI, multiple private third-party organizations, and internal teams to red-team Fable’s safeguards for thousands of hours. Finally, Anthropic noted that no testers have yet been able to find a universal jailbreak on Fable 5. As expected, Anthropic disagrees that a narrow potential jailbreak should lead to the recall of a commercial model used by hundreds of millions of people. It warned that applying this standard across the AI industry could effectively halt new frontier model deployments. Anthropic concluded by mentioning that it is working to restore access to Fable 5 and Mythos 5 as soon as possible and plans to share more details within the next 24 hours.
    • Brave Browser 1.91.172 is out.
  • Recent Achievements

    • Contributor
      MarkHughes4096 went up a rank
      Contributor
    • Dedicated
      jordanspringer earned a badge
      Dedicated
    • Rookie
      Rimplesnort went up a rank
      Rookie
    • One Year In
      Markus94287 earned a badge
      One Year In
    • One Month Later
      Markus94287 earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      503
    2. 2
      +Edouard
      176
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      ATLien_0
      92
    5. 5
      Steven P.
      79
  • Tell a friend

    Love Neowin? Tell a friend!