Windows Registry: Difference between revisions

Content deleted Content added
Filled in 2 bare reference(s) with reFill () | Cleaned up using AutoEd
Rescuing 4 sources and tagging 0 as dead. #IABot (v1.6.1) (Ost316)
Line 116:
 
; HKEY_DYN_DATA
:This key is used only on Windows 95, [[Windows 98]] and [[Windows ME]].<ref>{{Cite web|url=http://support.microsoft.com/kb/250568|title=Description of the HKEY_DYN_DATA Registry Key in Windows 95, Windows 98, and Windows 98 SE|website=support.microsoft.com}}</ref> It contains information about hardware devices, including Plug and Play and network performance statistics. The information in this hive is also not stored on the hard drive. The Plug and Play information is gathered and configured at startup and is stored in memory.<ref>{{cite web|url=http://docs.rinet.ru/Registratura/htm/apf.htm|title=A Closer Look at HKEY_DYN_DATA|website=rinet.ru|deadurl=yes|archiveurl=https://web.archive.org/web/20080509003336/http://docs.rinet.ru/Registratura/htm/apf.htm|archivedate=2008-05-09|df=}}</ref>
 
=== Hives ===
Line 346:
Windows 2000 kept an alternate copy of the registry hives (.ALT) and attempts to switch to it when corruption is detected.<ref>{{cite web | url = https://technet.microsoft.com/en-us/library/cc750583.aspx | title = Inside the Registry | accessdate = 2007-12-28}}</ref> Windows XP and Windows Server 2003 do not maintain a <tt>System.alt</tt> hive because [[NTLDR]] on those versions of Windows can process the <tt>System.log</tt> file to bring up to date a System hive that has become inconsistent during a shutdown or crash. In addition, the <tt>%SystemRoot%\Repair</tt> folder contains a copy of the system's registry hives that were created after installation and the first successful startup of Windows.
 
Each registry data file has an associated file with a ".log" extension that acts as a [[transaction log]] that is used to ensure that any interrupted updates can be completed upon next startup.<ref name="Norris">{{cite paper|archiveurl=https://web.archive.org/web/20090529202753/http://amnesia.gtisc.gatech.edu/~moyix/suzibandit.ltd.uk/MSc/Registry%20Structure%20-%20Main%20V4.pdf|format=PDF|url=http://amnesia.gtisc.gatech.edu/~moyix/suzibandit.ltd.uk/MSc/| date=February 2009 |title=The Internal Structure of the Windows Registry|publisher=Cranfield University|archivedate=29 May 2009|last=Norris|first=Peter|deadurl=yes|df=}}</ref> Internally, Registry files are split into 4&nbsp;[[Kilobyte|kB]] "bins" that contain collections of "cells".<ref name="Norris" />
 
=== Windows 9x ===
Line 465:
* In [[Mac OS X]], system-wide configuration files are typically stored in the <tt>/Library/</tt> folder, whereas per-user configuration files are stored in the corresponding <tt>~/Library/</tt> folder in the user's home directory, and configuration files set by the system are in <tt>/System/Library/</tt>. Within these respective directories, an application typically stores a [[property list]] file in the <tt>Preferences/</tt> sub-directory.
* [[RISC OS]] (not to be confused with ''[[MIPS RISC/os]]'') uses directories for configuration data, which allows applications to be copied into [[application directory|application directories]], as opposed to the separate installation process that typifies Windows applications; this approach is also used on the [[ROX Desktop]] for Linux.<ref>{{cite web
| url = http://roscidus.com/desktop/AppDirs
| title = Application directories
| accessdate = 17 May 2012
|deadurl = yes
|archiveurl = https://web.archive.org/web/20120527133205/http://roscidus.com/desktop/AppDirs
|archivedate = 27 May 2012
|df =
}}</ref> This directory-based configuration also makes it possible to use different versions of the same application, since the configuration is done "on the fly".<ref name="riscos.com list">{{cite web
| url=http://www.riscos.com/the_archive/rol/annoyance/index.htm
Line 473 ⟶ 477:
| accessdate=3 April 2012
}} Page from the riscos.com website. Mentioned in points 82 and 104.</ref> If one wishes to remove the application, it is possible to simply delete the folder belonging to the application.<ref>{{cite web | url = http://www.riscos.org/tour/index.html | title = RISC OS tour | accessdate = 2007-07-19}}</ref><ref>{{cite web
| url = http://productsdb.riscos.com/admin/riscos.htm
| title = The RISC OS Products Directory
| date = 2 Nov 2006
| accessdate = 1 April 2012
|deadurl = yes
|archiveurl = https://archive.is/20070219161339/http://productsdb.riscos.com/admin/riscos.htm
|archivedate = 19 February 2007
|df =
}}</ref> This will often not remove configuration settings which are stored independently from the application, usually within the computer's [[Application directory#The RISC OS !Boot system directory|!Boot structure]], in !Boot.Choices or potentially anywhere on a network fileserver. It is possible to copy installed programs between computers running RISC OS by copying the application directories belonging to the programs, however some programs may require re-installing, e.g. when shared files are placed outside an application directory.<ref name="riscos.com list" />
* [[IBM AIX]] (a Unix variant) uses a registry component called [[Object Data Manager]] (ODM). The ODM is used to store information about system and device configuration. An extensive set of tools and utilities provides users with means of extending, checking, correcting the ODM database. The ODM stores its information in several files, default location is /etc/objrepos.