Recommended Posts

So why does it slows down?

You keep claiming that the registry slows down without providing any evidence for it. I have no idea what answer you are looking for.

As I said, there are still programs that don't support it. One of this is also Visual Studio which doesn't support installing DLLs without administration rights.

What? Obviously you can't install shared system-wide components without administrator rights.

Obviously there are some, otherwise older programs wouldn't run.

I have no idea what this is supposed to mean. New and old programs mostly use the same APIs. There have been some minor additions and changes here and there, but not in a way that let's you remove anything without breaking modern software.

I don't know about anyone else but I never had any problems running applications when I used XP.The only time I ever had a problems was when I switched from XP to Vista.

I had all kinds of issues with XP back when it was still in beta. The early days of XP was ify as well. There were driver issues, stability issues... though neither was really Microsoft's fault. It was more issues with application developers believing they should have free reign of the system. It got significantly better even before SP2. With SP2 came a list of modifications to make XP more secure. A number of reasonable issues were addressed in XP sp3 as well.

As for Vista, I really never had any issues. It was rather resource intensive on light hardware, and there were minor issues (network copying), but again, it was mostly third party vendor issues with poor drivers and application design. I think it took a while for them to catch up. They have with Win7. Microsoft also did its part by improving the overall look and feel Vista with Win7. Less services, incremental start ups (elect).

You keep claiming that the registry slows down without providing any evidence for it. I have no idea what answer you are looking for.

People say that the registry causes system to slow down. So if you say that registry is not the cause, then what is?

What? Obviously you can't install shared system-wide components without administrator rights.

Visual Studio is used for application developing, why would I need to install system-wide components? I need them to be installed in user space which is obviously not supported with Windows.

I had all kinds of issues with XP back when it was still in beta. The early days of XP was ify as well. There were driver issues, stability issues... though neither was really Microsoft's fault. It was more issues with application developers believing they should have free reign of the system. It got significantly better even before SP2. With SP2 came a list of modifications to make XP more secure. A number of reasonable issues were addressed in XP sp3 as well.

As for Vista, I really never had any issues. It was rather resource intensive on light hardware, and there were minor issues (network copying), but again, it was mostly third party vendor issues with poor drivers and application design. I think it took a while for them to catch up. They have with Win7. Microsoft also did its part by improving the overall look and feel Vista with Win7. Less services, incremental start ups (elect).

it was beta what do you expect?When i switched from 98 to XP it was flawless for me.And i was running a P2 2.33mghz processor :p it was slow but did the job.

So? I'm sure some people preferred the look of system 7 on the early Macintoshes, does this mean that apple should have made it so people can switch MACOSX Snow Leopard to look like System 7?

The difference is that OS X and System 7 are completely different operating systems. Windows is the same from the first release of NT (and further back) to today. They simply added the themeing service in XP, and added the DWM in Vista. These are all layers sitting on top of each other. To get Classic, you simply remove two of the layers. It's the ultimate fallback, not just another theme. If they were to redesign Windows today with no focus on compatibility, this would all go, but that's asking for a lot more than just "replacing the Classic appearance with Basic." It would be a major breaking architectural change.

There's a time where certain outdated and ugly things must be laid to rest, to remove unnecessary outdated foundation to allow a more efficient (and better looking) foundation to take its place.

I think you're getting a little carried away here. What you are talking about is making changes that are purely visual and have no other impact on the OS at all.

People say that the registry causes system to slow down. So if you say that registry is not the cause, then what is?

It's not my job to tell you what you are talking about, you should know that yourself. You want to claim the registry slows down, you have to provide evidence of this.

Visual Studio is used for application developing, why would I need to install system-wide components? I need them to be installed in user space which is obviously not supported with Windows.

It could have been designed to install all shared components locally, and disable the various functionality that requires administrative rights, but what's the point. It accomplishes nothing of value.

People say that the registry causes system to slow down. So if you say that registry is not the cause, then what is?

You mean those very same people who go and download registry cleaners that do nothing? Yup I really trust their evidence.

As I said, there are still programs that don't support it.

I would assume that this has to do with shoddy code. Before Vista every application developer thought they could code their applications with admin rights, since pretty much 99% of XP accounts were admins. When Vista came about and started making prompts, most applications started acting funny.

So? I'm sure some people preferred the look of system 7 on the early Macintoshes, does this mean that apple should have made it so people can switch MACOSX Snow Leopard to look like System 7? There's a time where certain outdated and ugly things must be laid to rest, to remove unnecessary outdated foundation to allow a more efficient (and better looking) foundation to take its place.

Apple has an easy way with Mac. It's usershare isn't anywhere near as big as Windows. Sure MS can re-design windows to make it look different but think about the problems that would cause. You had the media and even people on this forum (and others) up in arms about vista because a few shortcuts were moved around.

If they finally got rid of the classic theme, it means they rewrote the foundation and a much better look, without requiring a service, has taken its place. Imagine that, a nice looking theme that does not require a service to run!

And replace the service with what exactly?

The difference is that OS X and System 7 are completely different operating systems. Windows is the same from the first release of NT (and further back) to today. They simply added the themeing service in XP, and added the DWM in Vista. These are all layers sitting on top of each other. To get Classic, you simply remove two of the layers. It's the ultimate fallback, not just another theme. If they were to redesign Windows today with no focus on compatibility, this would all go, but that's asking for a lot more than just "replacing the Classic appearance with Basic." It would be a major breaking architectural change.

I think you're getting a little carried away here. What you are talking about is making changes that are purely visual and have no other impact on the OS at all.

Yes and no. Aqua is a theme (like Luna and the default Win7 theme). It runs atop the Quartz Compositor (like the Desktop Windows Manager), which is the windowing system for OS X. I believe you could simply remove the ability for the end user to select the Classic UI theme. It would still be there, but unavailable. The issue, however, would become more complex if there were driver issues.

Yes and no. Aqua is a theme (like Luna and the default Win7 theme). It runs atop the Quartz Compositor (like the Desktop Windows Manager), which is the windowing system for OS X. I believe you could simply remove the ability for the end user to select the Classic UI theme. It would still be there, but unavailable. The issue, however, would become more complex if there were driver issues.

Yeah, why don't they just make it so only safe mode and servers can use this theme? Have the ability to use it disabled in normal Windows client. Then they can totally break how things look in it further without a big worry.

That way I won't have to see that ugliness used in a modern OS nearly as much in people's screenshots/videos.

Yeah, why don't they just make it so only safe mode and servers can use this theme? Have the ability to use it disabled in normal Windows client. Then they can totally break how things look in it further without a big worry.

That way I won't have to see that ugliness used in a modern OS nearly as much in people's screenshots/videos.

I don't know what screenshots / videos you're looking at but I haven't seen any that show Windows 7 classic theme. And why disable it?

If people want to use it, it's THEIR choice. Not yours. And its not like someone won't use a UXTHEME patch and put it right back anyways.

I don't know what screenshots / videos you're looking at but I haven't seen any that show Windows 7 classic theme. And why disable it?

If people want to use it, it's THEIR choice. Not yours. And its not like someone won't use a UXTHEME patch and put it right back anyways.

I've seen it on various IRC locales, on Youtube, and even on the desktop threads here on Neowin occassionally. Windows 7 and classic theme do not mix, and honestly 15 years is a very long time in the world of technology, to keep the SAME EXACT LOOK around for so long.

I've seen it on various IRC locales, on Youtube, and even on the desktop threads here on Neowin occassionally. Windows 7 and classic theme do not mix, and honestly 15 years is a very long time in the world of technology, to keep the SAME EXACT LOOK around for so long.

Yet again, why the hell do you care if someone else likes that theme and wants to use it? Did you make Windows? Did you pay for their computer and their software?

Yeh they could completely re-write it and design an entire new classic theme. But why? It wouldn't be able to use many "special effects," if any, since that is all done by DWM, it may cause compatibility issues etc. You have a perfectly good working shell working on top of it, so might as well leave something as trivial as a classic look that less than 1% of the world uses and focus on other more important things.

---

Here's an example. I hate the font you use, but I'm not telling you which one to use since its your account and I don't own Neowin.

I agree with others, who cares if the classic theme is still in there.Its not mandatory that you have to use it,it doesn't ship with the classic theme being the first thing you see when you turn on your new machine.The more options the better.Maybe i'll want to use it just for old times sake,I've tried it out in 7 and it doesn't look quite like the actual classic theme but its close enough.I don't like the classic theme myself and I wouldn't use it unless I had to but I don't want it gone just because I don't use it. The more options the better.

But Microsoft will need to do it in the future. What is the point of keep up with the NTFS since 1993 and updated framework. Where is the research work that they have been doing with

?

Why would they need to start from scratch in the future. They could rewrite certain parts of the OS (And I would expect them to do this), but I see no *Need* to start from scratch...

Well, if it was gone, then colleges and workplaces could no longer FORCE their users to use classic theme against their will like they have been with XP... and I sure don't wanna be stuck on a machine for the majority of the day forced to the classic look because the admin was a total jerk who wants to make everyone deal with his plain ideology. No classic theme in Windows = no more forcing users to have to use it.. which means I won't have to deal with it if I end up in a place like that!

People say that the registry causes system to slow down. So if you say that registry is not the cause, then what is?

These same people are usually trying to sell you, or have been lured by a company trying to sell you, a registry optimization product.

Which is completely useless and can actually wreck your registry on some occasions.

The registry is NOT slow. It's only weakness is that it's centralized. But that's also its strength.

Well, if it was gone, then colleges and workplaces could no longer FORCE their users to use classic theme against their will like they have been with XP... and I sure don't wanna be stuck on a machine for the majority of the day forced to the classic look because the admin was a total jerk who wants to make everyone deal with his plain ideology. No classic theme in Windows = no more forcing users to have to use it.. which means I won't have to deal with it if I end up in a place like that!

Are you aware of a situation where this is actually occuring with Windows 7? I ask because I've never heard of this, nor can I imagine an IT person doing this when the standard UI is much easier for them to just set up...

But Microsoft will need to do it in the future.

I agree that such a thing would be exciting, but i cannot genuinely think when it would become feasible or at least economically viable for Microsoft. That said, it isn't difficult to envisage a scenario where they will need to develop an Operating System that is designed to harness the power of the Internet as opposed to the colossal amount if ram your Computer has.

Are you aware of a situation where this is actually occuring with Windows 7? I ask because I've never heard of this, nor can I imagine an IT person doing this when the standard UI is much easier for them to just set up...

In my experience, when dealing with NT, 2000 & XP workstations it became necessary in some situations to force the Classic theme for certain Groups of users alone with the Classic Start Menu to avoid compatibility issues. The gap has only become more apparent between older Operating Systems and Windows 7 as time progresses.

If windows 7 is such a huge hit and takes the place of everyones xp machine, then windows 8 could be marketed as a power user OS.

Well, Windows 7 is being labeled as a "Minor" release. Windows 8 will be "Major", as Microsoft has stated they plan on alternating Major / Minor releases... I would love to know what's planned for Windows 8... *drools*

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

    • No registered users viewing this page.
  • Posts

    • Rufus 4.15.2393 Beta 2 by Razvan Serea Rufus is a small utility that helps format and create bootable USB flash drives, such as USB keys/pendrives, memory sticks, etc. Despite its small size, Rufus provides everything you need! Oh, and Rufus is fast. For instance it's about twice as fast as UNetbootin, Universal USB Installer or Windows 7 USB download tool, on the creation of a Windows 7 USB installation drive from an ISO (with honorable mention to WiNToBootic for managing to keep up). It is also marginally faster on the creation of Linux bootable USBs from ISOs. A non-exhaustive list of Rufus supported ISOs is available here. It can be especially useful for cases where: you need to create USB installation media from bootable ISOs (Windows, Linux, UEFI, etc.) you need to work on a system that doesn't have an OS installed you need to flash a BIOS or other firmware from DOS you want to run a low-level utility Rufus 4.15.2393 Beta 2 changelog: Add RISC-V 64 support to UEFI:NTFS Improve the guards for using the "silent" option Improve the ability to cancel during write retries Improve progress reporting for compressed image extraction Fix unrestricted XML entity expansion and integer overflow in ezxml parser (courtesy of @esadowski4) [GHSA-55r2-34wg-8mv9] Fix "silent" Windows installation failing at 75% in most cases [#2960] Fix a crash during boot when using UEFI:NTFS on Snapdragon X based ARM64 platforms [#2934] Fix the first WUE option always being checked by default [#2965] Fix an infinite loop when using Windows ISOs that contain multiple WIMs Fix "Enable runtime UEFI media validation" checkbox not always being properly enabled Other WUE improvements/fixes for OneDrive removal and username validation (with thanks to @christian8641) [#2984, #2991] Download: Rufus 4.15 Beta 2 | 1.9 MB (Open Source) Links: Rufus Home Page | Project Page @GitHub | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Tixati 3.43 by Razvan Serea Tixati is a free and easy to use BitTorrent client featuring detailed views of all seed, peer, and file transfer properties. Also included are powerful bandwidth charting and throttling capabilities, and a full DHT implementation. Tixati is one of the most advanced and flexible BitTorrent clients available. And unlike many other clients, Tixati contains NO SPYWARE, NO ADS, and NO GIMMICKS. Tixati portable version is meant to run on a USB flash drive or other portable media. It stores all its configuration files in the same folder as the executable binary files, and all file paths are stored in a format relative to the program executable folder. It is important you do not delete the "tixati_portable_mode.txt" file within the executables folder. This file is what triggers Tixati to run in portable mode. (The executable binaries are actually the same as the standard edition binaries.) When running the portable edition from a USB flash drive, especially one that is formatted in FAT16/FAT32, you may experience some lag when initially loading a new transfer. This is because initializing and allocating large files on flash-based media consumes a greater amount of time and resources compared to a conventional hard-drive. Tixati has the following features: detailed views of all aspects of the swarm, including peers, pieces, files, and trackers support for magnet links, so no need to download .torrent files if a simple magnet-link is available super-efficient peer choking/unchoking algorithms ensure the fastest downloads peer connection encryption for added security full DHT (Distributed Hash Table) implementation for trackerless torrents, including detailed message traffic graphs and customizable event logging advanced bandwidth charting of overall traffic and per-transfer traffic, with separate classification of protocol and file bytes, and with separate classification of outbound traffic for trading and seeding highly flexible bandwidth throttling, including trading/seeding proportion adjustment and adjustable priority for individual transfers and peers bitfield graphs that show the completeness of all downloaded files, what pieces other peers have available, and the health of the overall swarm customizable event logging for each download, and individual event logs for all peers within the swarm expert local file management functions which allow you to move files to a different partition even while downloading is still in progress 100% compatible with the BitTorrent protocol Windows and Linux-GTK native versions available Tixati 3.43 changelog: Several major DHT improvements Added several screening heuristics to filter malicious DHT nodes, prevent Sybil floods Rewrote DHT search algorithms to add support for multi-path lookups Improved DHT logging, more details in several error messages Extended timeout lengths for outgoing queries over I2P Added incoming query / response per second to DHT table status display Updated Regex engine to PCRE2 Faster Search function, scans channel user profiles in much less time Fixed problems with file name parsing and date handling in RSS Faster and more accurate RSS filtering and episode number detection Several optimizations to global text processing functions, such as UTF-8 cleaning, line splitting, and token parsing Complete update of port-mapping UPNP/NAT-PMP engine, added PCP support, mapping over VPN support, and more Several refinements to default gateway detection on Windows / Android, which is used for port-mapping Support for IPv6 interface-scoped addresses, which is sometimes needed for IPv6 gateway detection and port mapping Full support for PCP port remapping, added backup zero-port query in case requested port is rejected New UPNP/NAT-PMP Monitor in Help > Diagnostics New reflected local port/location tracker that analyzes DHT replies to detect true port/location and NAT mapping type New TCP/UDP Ports monitor in Help > Diagnostics, with several statistic and information tabs, and a detailed event log Calculated/reflected local port is now used for port parameter in tracker queries and peer handshake Fixed several problems with Linux Wayland compatibility Completely replaced tray icon functions in Linux, new SNI implementation is now the default with GSI backup Implemented full DBus-Menu server to be used by new SNI tray icon implementation Replaced Linux tray balloon notification DBus client Rewrote auto-shutdown DBus interface for Linux Rewrote sleep inhibit DBus interface for Linux Dropped deprecated Linux dbus-glib dependencies Completely new Windows asynchronous file handling, now using IOCP model with several block-alignment optimizations Better handling of system network resets and interface down/up cycles Added option to fully clear configuration in Settings > Import/Export Remember last option checkboxes when using Import/Export Fixed minor I2P incoming connection routing problems Much faster I2P vanity host name finder Much faster channel user vanity key finder Raised length limit for torrent tracker remote failure messages to 120 from 64 Fixed problems setting download location on a torrent before the meta info is resolved Added location/MOC paths to category pane tooltips Several minor Web Interface fixes Refinements to static and scrolling ellipsizing layout routines Several fixes and improvements to single and multi-line text edit controls Many other minor fixes throughout the user interface A major overhaul of the Android framework has also been done: API target raised to 35, page alignment set to 16K Rewrote all inset processing routines Full rewrite of foreground service, application, and main activity objects New permission request routines Added multi-cast lock request before UPNP/LPDP discovery operations Fixed file permission and locking problems when loading .torrent from web browsers Fixed problems with Z-ordering of modal / non-modal and popup windows Fixed handling of back gesture on newer OS Added status bar icon adjustment based on status bar background color Added option in Settings > UI > Behavior to continue running in tray when task removed from recents App can be closed by swiping away notification Rewrote IME interface, fixed several problems with auto-correct, on-screen keyboard visibility, and cursor positioning Added full support for Android hardware mouse and keyboard function Added full tooltip implementation for Android hovering via mouse or other cursor device Full rewrite of popup menu widgets to better support hardware pointers and keyboard Added mouse cursor updating framework for Android hovering Added Settings > Import/Export to Android builds Added language file support to Android builds Download: Tixati 64-bit | Tixati 32-bit ~20.0 MB (Freeware) Download: Portable Tixati 3.43 | 114.0 MB Download: Tixati 3.43 for Linux | Android View: Tixati Website | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Firefox 152.0.1 by Razvan Serea Firefox is a fast, full-featured Web browser. It offers great security, privacy, and protection against viruses, spyware, malware, and it can also easily block pop-up windows. The key features that have made Firefox so popular are the simple and effective UI, browser speed and strong security capabilities. Firefox has complete features for browsing the Internet. It is very reliable and flexible due to its implemented security features, along with customization options. Firefox includes pop-up blocking, tab-browsing, integrated Google search, simplified privacy controls, a streamlined browser window that shows you more of the page than any other browser and a number of additional features that work with you to help you get the most out of your time online. Firefox key features Enhanced Tracking Protection (ETP) – Blocks trackers, cookies, cryptominers, and fingerprinters by default. Private Browsing Mode – Deletes history, cookies, and temporary files when closed. Lightweight & Fast Performance – Optimized memory usage with efficient page loading. Cross-Platform Sync – Sync bookmarks, passwords, history, and open tabs across devices. Customizable Interface – Toolbars, themes, and extensions can be tailored to user needs. Strong Privacy Controls – Options to manage cookies, permissions, and site data easily. Reader Mode – Strips away clutter for distraction-free reading. Pocket Integration – Save and read articles offline with Pocket built into Firefox. Picture-in-Picture (PiP) – Watch videos in a floating window while multitasking. Extensions & Add-ons – Vast library for productivity, security, and personalization. Built-in PDF Viewer – No need for external software to view PDFs. Firefox Monitor – Alerts users if their email is part of a known data breach. Multi-Account Containers – Isolate browsing sessions (e.g., work, personal, shopping). Performance & Resource Efficiency – Uses fewer system resources than some competitors. Open Source & Community-Driven – Transparent development with global contributions. Firefox 152.0.1 fixes: Fixed frequent crashes affecting users with Intel Raptor Lake processors. (Bug 2039575) Fixed an issue on macOS where choosing a PDF option, such as "Save as PDF", from the system print dialog would send the job to your printer instead of saving a file. (Bug 2047850) Download: Firefox 64-bit | Firefox 32-bit | ARM64 | ~70.0 MB (Freeware) Download: Firefox for MacOS | 146.0 MB View: Firefox Home Page | Release Notes Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Zed 1.7.2 has landed with updated OpenCode models, bug fixes and other improvements by David Uzondu Zed 1.7.2 recently landed on the stable release channel, bringing a host of AI-related features including automatic context compaction and settings-based skill management, along with other things like better Markdown preview rendering and custom git commands in the graph view. Starting with the AI stuff, the developers introduced "/compact", a command that basically summarizes your conversation history on demand. This tool prevents your active chat window from hitting token limits by compressing older parts of the dialogue into a brief overview. In addition to that, the team relocated skill management to the settings UI, improving how the application communicates errors regarding those skills, and updated the OpenCode model roster to support DeepSeek V4 Flash, MiniMax M3, Qwen 3.7 Plus, and Nemotron 3 Ultra Free. External agent users can also monitor context window cost metrics and delete individual sessions directly from their history. Right-clicking ref labels in the git graph now opens a context menu that runs different actions against selected targets, kind of how VS Code does it. Here are some of the bug fixes this new release brings: The active agent fails to auto-select when creating a new git worktree. A scrollbar unexpectedly appears on wrapped code blocks in the agent chat. Collapse indicators for project headers appear when performing sidebar searches. Bracketed ellipsis title prefixes fail to show the ellipsis icon properly. Project icons render incorrectly in the recent projects picker. Diff hunk controls appear inside non-editable commit view multibuffers. The software update button hangs indefinitely on the downloading stage. Restoring an agent terminal in a remote project triggers a sudden crash. Splitting a pane that contains an active commit view causes a crash. Linux Wayland freezes when trying to read the clipboard from laggy external apps. Zed is a "newish" code editor trying to break the massive stronghold VS Code has on the developer community. Funny enough, the editor was created by former GitHub employees who worked on the Atom text editor (which Microsoft killed in 2022, several years after it bought GitHub). The project officially hit version 1.0 back in April, introducing platform parity for Windows and Linux alongside deep support for DeepSeek-V4-Pro.
    • 26H2 absolutely will support ARM Windows just not on devices that came with 26H1. This is evident by the fact I am running 26H2, which on my MacBook Neo and Surface Pro 12 (inch), within a VM.
  • Recent Achievements

    • One Year In
      hhgygy earned a badge
      One Year In
    • One Month Later
      AMV earned a badge
      One Month Later
    • Week One Done
      AMV earned a badge
      Week One Done
    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      523
    2. 2
      +Edouard
      172
    3. 3
      PsYcHoKiLLa
      78
    4. 4
      Steven P.
      72
    5. 5
      Michael Scrip
      71
  • Tell a friend

    Love Neowin? Tell a friend!