Topic: computing (Page 36)
You are looking at all articles with the topic "computing". We found 493 matches.
Hint:
To view all topics, click here. Too see the most popular topics, click here instead.
π Windows 3.1 beta crashed on 3rd-party DOS
The AARD code was a segment of code in a beta release of Microsoft Windows 3.1 that would determine whether Windows was running on MS-DOS or PCΒ DOS, rather than a competing workalike such as DR-DOS, and would result in a cryptic error message in the latter case. This XOR-encrypted, self-modifying, and deliberately obfuscated machine code used a variety of undocumented DOS structures and functions to perform its work, and appeared in the installer, WIN.COM, and several other executables in the OS.
The AARD code was originally discovered by Geoff Chappell on 17 April 1992 and then further analyzed and documented in a joint effort with Andrew Schulman. The name was derived from Microsoft programmer Aaron R. Reynolds (1955β2008), who used "AARD" to sign his work; "AARD" was found in the machine code of the installer. Microsoft disabled the AARD code for the final release of Windows 3.1, but did not remove it, so that it could have become reactivated later by the change of a single byte in an installed system, thereby constituting a "smoking gun".
DR-DOS publisher Digital Research released a patch named "business update" in 1992 to enable the AARD tests to pass on its operating system.
The rationale for the AARD code came to light when internal memos were released during the United States v. Microsoft Corp. antitrust case in 1999. Internal memos released by Microsoft revealed that the specific focus of these tests was DR-DOS. At one point, Microsoft CEO Bill Gates sent a memo to a number of employees, reading "You never sent me a response on the question of what things an app would do that would make it run with MS-DOS and not run with DR-DOS. Is there [sic] feature they have that might get in our way?" Microsoft Senior Vice President Brad Silverberg later sent another memo, stating: "What the [user] is supposed to do is feel uncomfortable, and when he has bugs, suspect that the problem is DR-DOS and then go out to buy MS-DOS."
Following the purchase of DR-DOS by Novell and its renaming to "Novell DOS", Microsoft Co-President Jim Allchin stated in a memo, "If you're going to kill someone there isn't much reason to get all worked up about it and angry. Any discussions beforehand are a waste of time. We need to smile at Novell while we pull the trigger."
What had been DR-DOS changed hands again. The new owner, Caldera, Inc., began a lawsuit against Microsoft over the AARD code, Caldera v. Microsoft, which was later settled. It was believed that the settlement ran in the order of $150 million, but was revealed in November 2009 with the release of the Settlement Agreement to be $280 million.
Discussed on
- "AARD Code" | 2020-09-27 | 13 Upvotes 2 Comments
- "Windows 3.1 beta crashed on 3rd-party DOS" | 2015-09-17 | 11 Upvotes 4 Comments
π Blinking Twelve Problem
The blinking twelve problem is a term used in software design. It usually refers to features in software or computer systems which are rendered unusable to most users by the complexity of the interface to them.
The usage emanates from the 'clock' feature provided on many VCRs manufactured in the late 1980s or early 1990s. The clock could be set by using a combination of buttons provided on the VCR in a specific sequence that was found complicated by most users. As a result, VCR users were known to seldom set the time on the VCR clock. This resulted in the default time of '12:00' blinking on the VCR display at all times of the day, which is the origin of this term.
"In most surveys, the majority of people have never time-shifted just because they don't know how to program their machines," said Tom Adams, a television analyst for Paul Kagan Associates, a media research firm, in 1990.
In software, 'the blinking twelve problem' thus refers to any situation in which features or functions of a program go unused for reasons that the designers never anticipated, largely because developers were unable to anticipate the level of understanding the users would have of the technology. The term may also refer to the challenge faced by developers of addressing the real causes of users' difficulties, as well as the challenge of providing helpful documentation or technical support without knowing beforehand how well the user understands their own problem.
In other instances, it can be used to reference the lack of basic user-friendly features in complex systems; stemming from the lack of a backup battery to keep the clock setting in a $300 VCR during even the briefest power interruption, when a $10 clock would have one.
The terms is usually used mostly by geeks, often in discussion forums. The term appears in the 1999 essay In the Beginning... Was the Command Line by Neal Stephenson.
Discussed on
- "Blinking Twelve Problem" | 2021-06-01 | 28 Upvotes 2 Comments
π Deep Crack
In cryptography, the EFF DES cracker (nicknamed "Deep Crack") is a machine built by the Electronic Frontier Foundation (EFF) in 1998, to perform a brute force search of the Data Encryption Standard (DES) cipher's key space β that is, to decrypt an encrypted message by trying every possible key. The aim in doing this was to prove that the key size of DES was not sufficient to be secure.
Discussed on
- "Deep Crack" | 2009-04-24 | 23 Upvotes 6 Comments
π Non-blocking synchronization
In computer science, an algorithm is called non-blocking if failure or suspension of any thread cannot cause failure or suspension of another thread; for some operations, these algorithms provide a useful alternative to traditional blocking implementations. A non-blocking algorithm is lock-free if there is guaranteed system-wide progress, and wait-free if there is also guaranteed per-thread progress.
The word "non-blocking" was traditionally used to describe telecommunications networks that could route a connection through a set of relays "without having to re-arrange existing calls", see Clos network. Also, if the telephone exchange "is not defective, it can always make the connection", see nonblocking minimal spanning switch.
Discussed on
- "Non-blocking synchronization" | 2010-02-03 | 21 Upvotes 8 Comments
π Compute Express Link
Compute Express Link (CXL) is an open standard for high-speed central processing unit (CPU)-to-device and CPU-to-memory connections, designed for high performance data center computers. CXL is built on the PCI Express (PCIe) physical and electrical interface and includes PCIe-based block input/output protocol (CXL.io) and new cache-coherent protocols for accessing system memory (CXL.cache) and device memory (CXL.mem).
Discussed on
- "Compute Express Link" | 2022-07-20 | 25 Upvotes 4 Comments
π Fifth-Generation Warfare
Fifth-generation warfare (5GW) is warfare that is conducted primarily through non-kinetic military action, such as social engineering, misinformation, cyberattacks, along with emerging technologies such as artificial intelligence and fully autonomous systems. Fifth generation warfare has been described by Daniel Abbot as a war of "information and perception". There is no widely agreed upon definition of fifth-generation warfare, and it has been rejected by some scholars, including William S. Lind, who was one of the original theorists of fourth-generation warfare.
Discussed on
- "Fifth-Generation Warfare" | 2023-11-08 | 26 Upvotes 3 Comments
π Indentation Style: Notable Styles
In computer programming, indentation style is a convention, a.k.a. style, governing the indentation of blocks of source code. An indentation style generally involves consistent width of whitespace (indentation size) before each line of a block, so that the lines of code appear to be related, and dictates whether to use space or tab characters for the indentation whitespace.
Discussed on
- "Indentation Style: Notable Styles" | 2025-02-24 | 11 Upvotes 18 Comments
π Cyrix 6x86
The Cyrix 6x86 is a line of sixth-generation, 32-bit x86 microprocessors designed and released by Cyrix in 1995. Cyrix, being a fabless company, had the chips manufactured by IBM and SGS-Thomson. The 6x86 was made as a direct competitor to Intel's Pentium microprocessor line, and was pin compatible. During the 6x86's development, the majority of applications (office software as well as games) performed almost entirely integer operations. The designers foresaw that future applications would most likely maintain this instruction focus. So, to optimize the chip's performance for what they believed to be the most likely application of the CPU, the integer execution resources received most of the transistor budget. This would later prove to be a strategic mistake, as the popularity of the P5 Pentium caused many software developers to hand-optimize code in assembly language, to take advantage of the P5 Pentium's tightly pipelined and lower latency FPU. For example, the highly anticipated first-person shooter Quake used highly optimized assembly code designed almost entirely around the P5 Pentium's FPU. As a result, the P5 Pentium significantly outperformed other CPUs in the game.
Discussed on
- "Cyrix 6x86" | 2024-10-30 | 24 Upvotes 5 Comments
π Dancing Links (A very useful hack by Knuth)
In computer science, dancing links is a technique for reverting the operation of deleting a node from a circular doubly linked list. It is particularly useful for efficiently implementing backtracking algorithms, such as Donald Knuth's Algorithm X for the exact cover problem. Algorithm X is a recursive, nondeterministic, depth-first, backtracking algorithm that finds all solutions to the exact cover problem. Some of the better-known exact cover problems include tiling, the n queens problem, and Sudoku.
The name dancing links, which was suggested by Donald Knuth, stems from the way the algorithm works, as iterations of the algorithm cause the links to "dance" with partner links so as to resemble an "exquisitely choreographed dance." Knuth credits Hiroshi Hitotsumatsu and KΕhei Noshita with having invented the idea in 1979, but it is his paper which has popularized it.
Discussed on
- "Dancing Links (A very useful hack by Knuth)" | 2010-06-01 | 21 Upvotes 7 Comments
π Unreal Mode
In x86 computing, unreal mode, also big real mode, huge real mode, flat real mode, or voodoo mode is a variant of real mode, in which one or more segment descriptors has been loaded with non-standard values, like 32-bit limits allowing access to the entire memory. Contrary to its name, it is not a separate addressing mode that the x86 processors can operate in. It is used in the 80286 and later x86 processors.
Discussed on
- "Unreal Mode" | 2019-03-18 | 27 Upvotes 1 Comments