Saturday, January 30, 2010

bench3

Installing New Software In Windows Seven | Installation Difference Between Windows XP And Seven

Compared to earlier releases of Windows, the processes of installing, configuring, and maintaining software and game programs work differently in Windows Vista and Windows 7. Primarily, this is because of changes to:
  • The way accounts are used
  • The way User Account Control (UAC) works
  • The removal of the Add/Remove Programs utility
  • The way application access tokens are used
  • The way applications write to the system locations

Unlike earlier releases of Windows (particularly windows XP), Windows Vista and Windows 7 has only standard user accounts and administrator accounts. When you log on to Windows Vista or Windows 7, you use one type of account or the other, removing the gray area between these two types of accounts that was previously available through the Power Users group. From Windows Vista, the Power Users group is included only for backward compatibility, and you should use it only when you need to resolve compatibility issues.

From the introduction of Windows Vista, software installation, configuration, and maintenance are processes that require elevated privileges. Because of this, only administrators can install, configure, and maintain software. Because of UAC, Windows Vista and Windows 7 is able to detect software installation. When Windows Seven or Vista detects a software-installation-related process, it prompts for permission or consent prior to allowing you to install, configure, or maintain software on your computer.

You know that the new Windows Seven and even Vista does not include an Add/Remove Programs utility. Instead, it relies completely on the software and game programs themselves to provide the necessary installation features through a related Setup or Autorun program.

Most programs created for Windows 95, Windows 98, Windows Me, Windows 2000, and Windows XP use setup.exe programs. Programs created for Windows Vista and later versions of Windows can use autorun.exe programs, particularly if those programs use current versions of Windows installers. For simplicity's sake, I'll refer to both Setup and Autorun programs as Setup programs.

Windows Seven and Vista also provides new architecture guidelines for software and game programs that fundamentally change the way software access tokens are used and the way software programs write to system locations. These changes are so far-reaching that software not specifically designed to support the new architecture guidelines is considered legacy software. This means there are two general categories of software that you can use with Windows Vista or Windows Seven:
  • Windows Vista-compliant applications
  • Legacy applications

Any software written specifically for Windows Seven or Vista's new architecture guidelines is considered a compliant application and can be certified as compliant with Microsoft. Applications certified as compliant have the Windows Vista-compliant logo or Windows Seven-compliant logo. Applications written for Windows Seven or Vista have access tokens that describe the privileges required to run and perform tasks. Windows Seven or Vista-compliant applications fall into two general categories:

  • Administrator user applications

  • Standard user applications


Administrator user applications

If an application requires elevated privileges to run and perform tasks, it is considered an administrator user application. Administrator user applications can write to system locations of the registry and filesystem.

Standard user applications
If an application does not require elevated privileges to run and perform tasks, it is considered a standard user application. Standard user applications should write only to non-system locations of the registry and filesystem.

Any application written for an earlier version of Windows is considered a legacy application. Legacy applications run as standard user applications and in a special compatibility mode that provides virtualized views of file and registry locations. When a legacy application attempts to write a system location, Windows Seven / Vista gives the application a private copy of the file or registry value. Any changes are then written to the private copy, and this private copy is in turn stored in the user's profile data. If the application attempts to read or write to this system location again, it is given the private copy from the user's profile.

bench3

About bench3 -

Haja Peer Mohamed H, Software Engineer by profession, Author, Founder and CEO of "bench3" you can connect with me on Twitter , Facebook and also onGoogle+

Subscribe to this Blog via Email :