Transparent, see through, blurred, GLASS in VISTA BASIC!


Recommended Posts

Well that was a constructive comment :/

Electrik Jesus: How did you get your desktop icons like that?

constructive.. why would i be constructive, when you losers try to get aero by bugs, instead of just buying it or warezing it if thats what you want

@Electrik Jesus- how did you get a completely transparent task bar..yours really looks great. did you use a custom msstyle. please let me know. i GOTTTA mhave this . THX in advance.

I used the Vista MaxClear theme with the longhorn retrophase shellstyle.

I will be soon working on "The Next 3" for Vista now that I can see what the skin will look like with transparency.

constructive.. why would i be constructive, when you losers try to get aero by bugs, instead of just buying it or warezing it if thats what you want

For starters, Most people you come across get a bad vibe from you... I wonder why.

Secondly, not everyone has the money or the system specs for Vista Ultimate. I for instance am running this with 502mb ram and an 8mb shared memory Gfx card.

So why not.

Link me to where I can buy Aero from Microsoft and only Aero... (dont try to be smart and post a link of premium).

This isn't anything different to everything else that's discussed here imo.

Thing is flip3d and the thumbnails aren't bloatware in ANY way and media center's services can be disabled if you want them to be. Price might be able to be considered a valid concern (despite the difference being relatively small). Avoiding features, especially ones that go right along with the one you want, not so much.

For starters, Most people you come across get a bad vibe from you... I wonder why.

Secondly, not everyone has the money or the system specs for Vista Ultimate. I for instance am running this with 502mb ram and an 8mb shared memory Gfx card.

So why not.

You don't need Ultimate for what's being discussed in this thread.

Home Basic come bundled on my laptop so the price difference is pretty big for something which is a small upgrade IMO. Media Center is something I dont even want on my laptop, my HD is packed as it is...

Electrik Jesus: How did you get your desktop icons as tiles??

I'm only interested in this thread because of the hack aspect of it. I run Business N so it's no big deal really to me otherwise. If there's a way to get aero running in Vista Basic then more power to those users that are stuck with it.

cant you just use a Vista theme like one of the millions for xp?

Not without third party apps like WB. Theres no Vista VSs around with a basic shell that looks like Vista Aero that I know of. I can't believe how butt ugly Vista Basic looks though, I hate when it knocks out of Aero for compatibility reasons and I see it. Why they couldn't just make it look like an XP VS Vista clone when in Basic, eugh.

Here is a screen shot for all of you that still doubt Vista Basic Home can't do transparency.

post-165061-1182194805_thumb.jpg

Just to confirm, did you knock this screenshot up using my method for getting Aero on Vista Basic? Also, the windows aren't resizable without loosing the transparency, right? I don't run Basic so can't test this. I didn't actually know if it worked, I just guessed it did after noticing the quirk while using Pitaschio, heh.

first off before I get to the pitaschio thing, I play simcity4 in the windowed mode... guess what happens if I hit the maximized button...(aero without having to do that dual screen stuff, but it's only with the game :(

okay I tried pitaschio and it works. although I don't like how it renders the maximize button on the window moot.

It does transparency and the windows behave exactly like how the windows on the dual screen thing acted, no shadows no resizing,....

By that, you're actually infringing the company's rights and nullifying limitations set by the company to differentiate the different versions of Windows, and that's unethical and wrong isn't it?

PS: Not that I support MS, on the contrary.

It's not unethical or wrong, and it certainly doesn't violate Microsoft's right to artificially cripple a basic version of their OS. There's no law which says we can't customise the OS to imitate/re-enable features which were removed to create obvious differences between different versions of Vista.

It's no different to modifying an engine on a low-end car model which has been artificially crippled to create differences in performance between models.

I'm assuming the vistaglazz patch just adds some things from Aero somewhere else to get the glass effect? If so, I'm thinking this is all you're gonna get if you're a Basic user (Since the code/whatever won't be anywhere else).

This is simply easy, if you want to use Aero in Vista Basic, it is done by modifying just TWO values in the Windows Registry, and restarting the service labeled:

uxsms ( Desktop Window Manager ), in Vista Basic

This will make Windows Vista Home Basic, have Aero, With Glass, and All the cool effects as seen In Home Premium and Ultimate, without any 3rd party applications

Start, and type in "regedit" without the quotes.

In the Registry Editor, navigate to
HKEY_CURRENT_USER/Software/Microsoft/Windows/DWM

Change Composition to 1
Change CompositionPolicy to 2

CLose the registry editor, Start, and type CMD, press enter

Type
net stop uxsms

then type

net start uxsms

If it does not automatically load with Aero, then Right click the Desktop, Personalization, Windows Color and Appearance, and select Windows Aero.

This is simply easy, if you want to use Aero in Vista Basic, it is done by modifying just TWO values in the Windows Registry, and restarting the service labeled:

uxsms ( Desktop Window Manager ), in Vista Basic

This will make Windows Vista Home Basic, have Aero, With Glass, and All the cool effects as seen In Home Premium and Ultimate, without any 3rd party applications

Start, and type in "regedit" without the quotes.

In the Registry Editor, navigate to
HKEY_CURRENT_USER/Software/Microsoft/Windows/DWM

Change Composition to 1
Change CompositionPolicy to 2

CLose the registry editor, Start, and type CMD, press enter

Type
net stop uxsms

then type

net start uxsms

If it does not automatically load with Aero, then Right click the Desktop, Personalization, Windows Color and Appearance, and select Windows Aero.

ummm...it didn't do anything.

and I don't see Aero under Windows Color and Appearance.

I'll just stick with the glazz app for now. That seems to work.

It's not unethical or wrong, and it certainly doesn't violate Microsoft's right to artificially cripple a basic version of their OS. There's no law which says we can't customise the OS to imitate/re-enable features which were removed to create obvious differences between different versions of Vista.

It's no different to modifying an engine on a low-end car model which has been artificially crippled to create differences in performance between models.

I'm not clear on whether it is unethical or not, but it is most certainly a breach of the EULA to modify portions of Windows. Yes, the uxtheme patch is also a violation of the EULA, and so is the Mess.be MessPatch, and so on, and so on...

It's just that Neowin chooses to ignore that the uxtheme patch is a breach of the EULA. From the looks of it, Microsoft is turning a blind eye, too- but I think they'll take a different stance on what you're trying to achieve here.

I'm not clear on whether it is unethical or not, but it is most certainly a breach of the EULA to modify portions of Windows. Yes, the uxtheme patch is also a violation of the EULA, and so is the Mess.be MessPatch, and so on, and so on...

It's just that Neowin chooses to ignore that the uxtheme patch is a breach of the EULA. From the looks of it, Microsoft is turning a blind eye, too- but I think they'll take a different stance on what you're trying to achieve here.

oh please stop with this sanctimonious drivel. if the mods wish to lock or delete this thread they have it within their means to. otherwise, live what you preach and stop trying to argue how selectively breaking the EULA via patching is somehow morally and legally superior than what the OP is trying to do.

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

    • No registered users viewing this page.
  • Posts

    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
  • Recent Achievements

    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
    • 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
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      70
  • Tell a friend

    Love Neowin? Tell a friend!