This HTML5 document contains 60 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

PrefixIRI
dcthttp://purl.org/dc/terms/
yago-reshttp://yago-knowledge.org/resource/
n10http://dbpedia.org/resource/Speedy_Gonzales:
dbohttp://dbpedia.org/ontology/
foafhttp://xmlns.com/foaf/0.1/
n15http://dbpedia.org/resource/OS/
n11http://dbpedia.org/resource/IBM_Personal_Computer/
dbthttp://dbpedia.org/resource/Template:
rdfshttp://www.w3.org/2000/01/rdf-schema#
freebasehttp://rdf.freebase.com/ns/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
owlhttp://www.w3.org/2002/07/owl#
n13http://en.wikipedia.org/wiki/
dbphttp://dbpedia.org/property/
dbchttp://dbpedia.org/resource/Category:
provhttp://www.w3.org/ns/prov#
xsdhhttp://www.w3.org/2001/XMLSchema#
dbrhttp://dbpedia.org/resource/

Statements

Subject Item
dbr:Bug_compatibility
rdfs:label
Bug compatibility
rdfs:comment
Computer hardware or software is said to be bug compatible if it exactly replicates even an undesirable feature of a previous version. The phrase is found in the Jargon File. An aspect of maintaining backward compatibility with an older system is that such systems' client programs often do not only depend on their specified interfaces but also bugs and unintended behaviour. That must also be preserved by the newer replacement. Besides the significantly higher complexity that needs to be maintained during the natural evolution of the code or interface, it can sometimes cause performance or security issues, and the inconsistencies in the behaviour of interfaces can sometimes lead to new bugs in the software using it, creating difficult to resolve multi-directional cross dependencies between
owl:sameAs
freebase:m.026xbtb yago-res:Bug_compatibility
dbp:wikiPageUsesTemplate
dbt:Portal dbt:Reflist dbt:Use_dmy_dates dbt:Use_list-defined_references dbt:Short_description
dct:subject
dbc:Backward_compatibility dbc:Software_bugs
prov:wasDerivedFrom
n13:Bug_compatibility?oldid=1072997845&ns=0
dbo:wikiPageID
8238278
dbo:wikiPageLength
17905
dbo:wikiPageRevisionID
1072997845
dbo:wikiPageWikiLink
dbr:Microsoft_Flight_Simulator dbr:Off-by-one_error dbr:MS-DOS dbr:A20_line dbr:Sublogic dbr:Design_of_the_FAT_file_system dbr:Intel dbc:Backward_compatibility dbr:Software_bug dbr:Path_(computing) n10:_Los_Gatos_Bandidos n11:AT dbr:Microsoft_Windows dbr:Tenberry_Software dbr:Loader_(computing) dbr:Higan_(emulator) dbr:WINA20.386 dbr:Jargon_File dbr:Backward_compatibility dbr:Wine_(software) dbr:IBM_PC_DOS dbr:IBMBIO.COM dbr:Executable_compression dbr:BIOS_parameter_block dbr:Leap_year_problem dbr:Virtual_DOS_machine dbr:Compaq dbr:Super_Nintendo_Entertainment_System dbr:IBM_PC_compatible dbr:Microsoft_Excel dbr:IBMDOS.COM n15:2 dbr:Bruce_Artwick dbr:Working_directory dbr:COUNTRY.SYS dbr:IBM dbr:AARD_code dbr:Microsoft dbr:Windows_9x dbr:Plug_compatible dbr:DR-DOS dbr:Lotus_1-2-3 dbc:Software_bugs
dbo:abstract
Computer hardware or software is said to be bug compatible if it exactly replicates even an undesirable feature of a previous version. The phrase is found in the Jargon File. An aspect of maintaining backward compatibility with an older system is that such systems' client programs often do not only depend on their specified interfaces but also bugs and unintended behaviour. That must also be preserved by the newer replacement. Besides the significantly higher complexity that needs to be maintained during the natural evolution of the code or interface, it can sometimes cause performance or security issues, and the inconsistencies in the behaviour of interfaces can sometimes lead to new bugs in the software using it, creating difficult to resolve multi-directional cross dependencies between various pieces of code. Examples can be found in MS-DOS/PC DOS:When MS-DOS/PC DOS 3.1 and higher (including Windows 9x) and OS/2 detect certain FAT OEM labels, they don't trust some BIOS Parameter Block (BPB) values and recalculate them from other disk geometry parameters in order to work around several off-by-one calculation errors caused by some of their formatter software under earlier issues of these systems. While this undocumented behaviour allows them to cope with these incorrectly formatted volumes specifically, it limits the flexibility of disk geometries they can work with in general and can cause them to trash validly formatted volumes created by third-parties if they deviate from the defaults used by Microsoft and IBM.When MS-DOS/PC DOS 5.0 and higher are running on 286 or higher processors, the resident executable loader contains code specially designed to detect and fix certain widespread applications and stub loaders (such as programs linked with older versions of Microsoft's EXEPACK or Rational Systems' 386 DOS extenders) by patching the loaded program image before executing it. Under certain conditions an underlying DOS also patches Windows. Over the course of development, DR-DOS also had to be modified to not only emulate many undocumented peculiarities and undesirable properties of MS-DOS and PC DOS (like having to use certain misleading filenames such as IBMBIO.COM, IBMDOS.COM or for files which do not follow the specs for executables under DOS, or having to introduce a directory path length-limited Current Directory Structure (CDS) internally), but also actual bugs in the kernel and several drivers, in order to make certain other drivers and applications run on DR-DOS, when they were tested on specific versions of MS-DOS only. Windows, which has traditionally emulated many old system bugs to allow older low-level programs to run, is another example. As a result, Wine, which makes it possible to run many Windows applications on other platforms, also needs to maintain bug compatibility with Windows. When Microsoft phased out support for 16-bit code in Windows by no longer including NTVDM in 64-bit editions of the operating system, the executable loader was modified to recognize some specific 16-bit stub launchers and installers and replace them on-the-fly with equivalent code stubs that run on 64-bit processors. During development of its IBM PC compatible, Compaq engineers found that Microsoft Flight Simulator would not run because of what subLOGIC's Bruce Artwick described as "a bug in one of Intel's chips", forcing them to make their computer bug-compatible with the IBM PC. Another hardware example is found in the design of the IBM Personal Computer/AT A20 address line to emulate the behaviour in older processors. Microsoft Excel has always had a deliberate leap year bug, which falsely treats February 29, 1900 as an actual date, to ensure backward compatibility with Lotus 1-2-3. Emulators such as Near's higan for the Super Nintendo Entertainment System were made with such accuracy in mind that even bugs present in certain games such as the platformer Speedy Gonzales: Los Gatos Bandidos had to be handled in exactly the same manner as it does in real hardware, allowing the game to be played correctly.
foaf:isPrimaryTopicOf
n13:Bug_compatibility