Get your fill of sci-fi, science, and mockery of stupid ideas
http://stardestroyer.dyndns-home.com/
http://stardestroyer.dyndns-home.com/viewtopic.php?f=24&t=74935
Considering the improvement over it with 2k and XP, I'd be surprised if it actually got worse. Well, maybe not surprised..but..sadThe Kernel wrote:My question is whether Windows Rot and registry bloat is still going to be an issue.
Yeah, but it's still a problem. Windows XP is more robust, but you still can't go a year without having to reformat and reinstall. Plus, I've noticed that it's damn easy to kill a Windows XP install doing hardware replacements. These are the things I really want to see changed, there is no good reason why I should have to reinstall my OS on a regular basis.Akaramu Shinja wrote:Considering the improvement over it with 2k and XP, I'd be surprised if it actually got worse. Well, maybe not surprised..but..sadThe Kernel wrote:My question is whether Windows Rot and registry bloat is still going to be an issue.
Yes, I have an idea why, I tend to install a lot of different software on my PC's. But so what? The number of software installs shouldn't have an effect on the stability of the OS. We shouldn't be forced to minimalize.Tiger Ace wrote:Kernel, any idea why? I keep my system in shape, 2 years without a re-install and its rock stable with a pair of small quirks.
Maybe its because I rarely add programs and keep stuff maintained all the time.
That only has relevance if you neglect to install your video card maker's drivers (which have their own real OGL implementation). I don't think anyone who actually cares is going to be forgetting to do that.Akaramu Shinja wrote:Emulated OGL through D3D when using Windowed mode with AeroGlass running. I was really looking forward to Vista too
Um, what? No. AeroGlass keeps Windows in constant D3D drawing mode, which means you can't have OGL calling to the G.Card at the same time without causing flicker. This is why they catch the OGL calls and wrap them into D3D. This is only relevant when AeroGlass is being used (thus not fullscreen OGL or when AeroGlass is disabled).Seggybop wrote:That only has relevance if you neglect to install your video card maker's drivers (which have their own real OGL implementation). I don't think anyone who actually cares is going to be forgetting to do that.Akaramu Shinja wrote:Emulated OGL through D3D when using Windowed mode with AeroGlass running. I was really looking forward to Vista too
Well they are going to include performance monitoring software which watches for software changes which massively impact of system performance. There is also going to be a new prefetch system which loads commonly used applications into memory before the user actually uses them("yay!" cry RAM Manufacturers).The Kernel wrote:My question is whether Windows Rot and registry bloat is still going to be an issue.
Baddly written installers, Windows software with very baddly writter installers is common as dirt. Properly written MSI files are a god-send, they allow the OS to cleanly uninstall something in a safe and reliable way.The Kernel wrote:Yes, I have an idea why, I tend to install a lot of different software on my PC's. But so what? The number of software installs shouldn't have an effect on the stability of the OS. We shouldn't be forced to minimalize.
Interesting. So is GDI being replaced D3D for desktop applications ?Akaramu Shinja wrote:Um, what? No. AeroGlass keeps Windows in constant D3D drawing mode, which means you can't have OGL calling to the G.Card at the same time without causing flicker. This is why they catch the OGL calls and wrap them into D3D. This is only relevant when AeroGlass is being used (thus not fullscreen OGL or when AeroGlass is disabled).Seggybop wrote:That only has relevance if you neglect to install your video card maker's drivers (which have their own real OGL implementation). I don't think anyone who actually cares is going to be forgetting to do that.Akaramu Shinja wrote:Emulated OGL through D3D when using Windowed mode with AeroGlass running. I was really looking forward to Vista too
While the Monad commandline will not be in the client version of Vista (aka Vista Pro & Vista Home) it will be in the server versions and it will also be an optional DL from Microsoft the Vista client-versions once Monad is released.Destructionator XIII wrote:That actually looks pretty decent. It seems that they have strengthened the command line and they new administrative account security looks promising.
It's what you install not how much. My install is 2 years old and running smooth as (would have been 3 but upgradeing is nessecary).Yes, I have an idea why, I tend to install a lot of different software on my PC's. But so what? The number of software installs shouldn't have an effect on the stability of the OS. We shouldn't be forced to minimalize.
Wrong. A miss behaving app will bring down any os. My install of mandrake 9.2 was really screwed by a bad XMMS install.After all, the average Linux distro installs with thousands of applications, yet there is no adverse hit to the stability of the OS.
From hereThis afternoon, Microsoft's Greg Sullivan confirmed the company's official exodus away from the System Registry as a key component, and toward what are now being called "application manifests"--individual, secure files for applications to store their own configuration data, and for other purposes. It turns out that, as Microsoft moves toward gradual adoption of what was dubbed this morning Windows Communication Foundation (formerly and more affectionately known as "Indigo"), a single file for storing the configurations and data attributes of all running components in the system, may eventually no longer be necessary.
"This has been an ongoing design goal of ours," Sullivan told us. "The Registry has served its purpose well for managing the settings and keys required to do configuration--particularly application installation and behavior--but that model has also been fraught with some challenges that we've had to face. So it's been a long-term goal for us to evolve that." However, Sullivan added, there are still over 600 million people using Windows XP and, therefore, using local System Registries. The challenge over the next several years will be to migrate to a Registry-free world without breaking applications.
One approach to implementing this exodus, Sullivan revealed to us for the first time, will be a new system that provides non-administrative users with a "virtual Registry," ostensibly at first for the sake of protecting the main Registry from abuse. This way, said Sullivan, "not every user has to be an administrator to accomplish something. But when we're able to virtualize the Registry, we can actually provide a standard user with a way to have a meaningful interaction, including installing applications that write to the Registry, but in a way that doesn't necessarily permanently harm or affect what the administrator has set up." Conceivably, a virtual Registry could be used by older Windows applications that still require it, within a future system - probably far later than Vista - that no longer provides the Registry as a standard service.
and how many people will declare the OS crap and advise people not to use it, as it "breaks apps".Durandal wrote: Wonder how many poorly-designed apps this is going to break.
Windows 98 -> Windows ME...Akaramu Shinja wrote:Considering the improvement over it with 2k and XP, I'd be surprised if it actually got worse. Well, maybe not surprised..but..sadThe Kernel wrote:My question is whether Windows Rot and registry bloat is still going to be an issue.
I wonder where they got that idea?This afternoon, Microsoft's Greg Sullivan confirmed the company's official exodus away from the System Registry as a key component, and toward what are now being called "application manifests"--individual, secure files for applications to store their own configuration data, and for other purposes. It turns out that, as Microsoft moves toward gradual adoption of what was dubbed this morning Windows Communication Foundation (formerly and more affectionately known as "Indigo"), a single file for storing the configurations and data attributes of all running components in the system, may eventually no longer be necessary.
