Re: windows fix all solution that Microsoft should deploy in longhorn

From: Admiral Q (Star_Fleet_Admiral_Q(NOSPAM)_at_(SPAMNOT)hotmail.com)
Date: 02/08/05


Date: Tue, 8 Feb 2005 15:32:56 -0500

Your English is so broken and unstructured it is hard to distinguish exactly
what is going on - do you have a question? ranting and/or raving? offering
advice? I just can't understand it.

-- 
Star Fleet Admiral Q @ your service!
"Google is your Friend!"
www.google.com
***********************************************
"Dogin" <Dogin@discussions.microsoft.com> wrote in message
news:AD5F5911-2DF9-4FA1-81A5-23DC214A9CDD@microsoft.com...
> windows as most people will tell you can become broken* to the point of
> having to reinstall the whole operating system again >> windows dose have
> >>System restore >> which workers [most, to some] of the time depending on
> your restore points that you may or may not have set, and again depending
on
> the amount of Disk space you designate it to use in the {{System
> properties/System restore/Drive settings}} . other than the windows
braking,
> it has other problems to like the User Accounts having to share some
system
> wide settings like screen resolution or sound mute >> moving on to my fix
all
> solution >>
> if you know the registry you know
> >>HKEY_CURRENT_USER And  HKEY_LOCAL_MACHINE<<
> HKEY_CURRENT_USER being the User Account, and
> HKEY_LOCAL_MACHINE  being the system wide settings
>
> HKEY_CURRENT_USER keeps each users custom seatings >>but if
> >>HKEY_CURRENT_USER And  HKEY_LOCAL_MACHINE<< were merged into something
like
> HKEY_USER it could keep all the settings of the whole system for each user
> then all that would be required is that windows keeps a back up or a
default
> HKEY_USER; and say a user account becomes compromised or broken* it
replaces
> your whole  HKEY_USER that you backed up before your account became
> compromised or >> my favorite instead of reinstalling the whole operating
> system like you currently have to do when one of your system wide seatings
or
>  HKEY_LOCAL_MACHINE get corrupted; you could gust revert all the way to
the
> default HKEY_USER
>
> this is not the only part of a fix all solution >> because its only the
> settings or registry side of the equation theres also the file part of my
fix
> all solution and it would be to >> seperate the windows default programs
like
> notepad and paint from the required things like shell32.dll and
kernel32.dll
> then putting all the required things in a folder like "System Volume
> Information" which is some what protected from petty bugs and my favorite
> spy-ware and add-ware which are another major cause of having to reinstall
> the whole operating system again   not only because they slip themselves
into
> your registry  because they slip themselves into the system32 folder also


Relevant Pages

  • Re: Cant change home page, read others post
    ... I would do a clean install of Windows Xp and before ... "nass" wrote: ... I don't like the sound of *Reset web settings* not allowed, ... The entry in the registry did change to the new ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
  • Re: Found HWS.EXE & INSTALL.DAT Pls Advise
    ... Reg fixes plus learning of a way of to get into the Registry when all the ... MUI file in it's bliue border, prior to booting into Windows. ... works through the hang then my Personal Settings loaded. ... tight security settings on both your Anti-Virus and your Browser security ...
    (microsoft.public.windowsxp.general)
  • Re: How to repair corrupted files w/o Windows XP disk?
    ... Registry settings. ... I just made the registry changes, ... Changing the SourcePath setting to the Recovery partition doesn't work ... a WINDOWS disk, ...
    (microsoft.public.windows.mediacenter)
  • Re: The Beginning Of The End For Micro$oft Reign Of Terror
    ... >>found in the registry. ... cryptic keynames and settings in the registry, someone has a lot to hide. ... > is just as easy to implement in Windows; ... > You're just defending the primitive text-based config files of Linux. ...
    (comp.security.firewalls)
  • (no subject)
    ... >>found in the registry. ... cryptic keynames and settings in the registry, someone has a lot to hide. ... > is just as easy to implement in Windows; ... > You're just defending the primitive text-based config files of Linux. ...
    (comp.security.firewalls)