You are looking at all articles with the topic "Computing". We found 526 matches.

Hint: To view all topics, click here. Too see the most popular topics, click here instead.

🔗 Computing 🔗 Internet culture 🔗 Law 🔗 Software 🔗 Software/Computing

The Warez scene, often referred to as The Scene, is an underground network of piracy groups specialized in obtaining and illegally releasing digital media before their official release date. The Scene distributes all forms of digital media, including computer games, movies, TV shows, music, and pornography. This network is meant to be hidden from the public, with the files shared only with members of the community. However, as files became commonly leaked outside the community and their popularity grew, some individuals from The Scene began leaking files and uploading them to file-hosts, torrents and EDonkey Networks.

The Scene has no central leadership, location, or other organizational culture. The groups themselves create a rule set for each Scene category (for example, MP3 or TV) that then becomes the active rules for encoding material. These rule sets include a rigid set of requirements that warez groups (shortened as "grps") must follow in releasing and managing material. The groups must follow these rules when uploading material and, if the release has a technical error or breaks a rule, other groups may "nuke" (flag as bad content) the release. Groups are in constant competition to get releases up as fast as possible. First appearing around the time of Bulletin Board Systems (BBSes), The Scene is composed primarily of people dealing with and distributing media content, for which special skills and advanced software are required.

🔗 Computing 🔗 Systems 🔗 Computing/Software 🔗 Systems/Software engineering

From its beginnings in the 1960s, writing software has evolved into a profession concerned with how best to maximize the quality of software and of how to create it. Quality can refer to how maintainable software is, to its stability, speed, usability, testability, readability, size, cost, security, and number of flaws or "bugs", as well as to less measurable qualities like elegance, conciseness, and customer satisfaction, among many other attributes. How best to create high quality software is a separate and controversial problem covering software design principles, so-called "best practices" for writing code, as well as broader management issues such as optimal team size, process, how best to deliver software on time and as quickly as possible, work-place "culture", hiring practices, and so forth. All this falls under the broad rubric of software engineering.

🔗 Computing 🔗 Computing/Computer hardware

In the x86 architecture, the CPUID instruction (identified by a CPUID opcode) is a processor supplementary instruction (its name derived from CPU IDentification) allowing software to discover details of the processor. It was introduced by Intel in 1993 with the launch of the Pentium and SL-enhanced 486 processors.

A program can use the CPUID to determine processor type and whether features such as MMX/SSE are implemented.

🔗 Computing

Project Denver is the codename of a microarchitecture designed by Nvidia that implements the ARMv8-A 64/32-bit instruction sets using a combination of simple hardware decoder and software-based binary translation (dynamic recompilation) where "Denver's binary translation layer runs in software, at a lower level than the operating system, and stores commonly accessed, already optimized code sequences in a 128 MB cache stored in main memory". Denver is a very wide in-order superscalar pipeline. Its design makes it suitable for integration with other SIPs cores (e.g. GPU, display controller, DSP, image processor, etc.) into one die constituting a system on a chip (SoC).

Project Denver is targeted at mobile computers, personal computers, servers, as well as supercomputers. Respective cores have found integration in the Tegra SoC series from Nvidia. Initially Denver cores was designed for the 28nm process node (Tegra model T132 aka "Tegra K1"). Denver 2 was an improved design that built for the smaller, more efficient 16nm node. (Tegra model T186 aka "Tegra X2").

In 2018, Nvidia released an improved design (codename: "Carmel", based on ARMv8 (64-bit; variant: ARM-v8.2 with 10-way superscalar, functional safety, dual execution, parity & ECC) got integrated into the Tegra Xavier SoC offering a total of 8 cores (or 4 dual-core pairs). The Carmel CPU core supports full Advanced SIMD (ARM NEON), VFP (Vector Floating Point), and ARMv8.2-FP16. First published testings of Carmel cores integrated in the Jetson AGX development kit by third party experts took place in September 2018 and indicated a noticeably increased performance as should expected for this real world physical manifestation compared to predecessors systems, despite all doubts the used quickness of such a test setup in general an in particular implies. The Carmel design can be found in the Tegra model T194 ("Tegra Xavier") that is designed with a 12 nm structure size.

🔗 Computing

Proxmox Virtual Environment (Proxmox VE or PVE) is an open-source software server for virtualization management. It is a hosted hypervisor that can run operating systems including Linux and Windows on x64 hardware. It is a Debian-based Linux distribution with a modified Ubuntu LTS kernel and allows deployment and management of virtual machines and containers. Proxmox VE includes a web console and command-line tools, and provides a REST API for third-party tools. Two types of virtualization are supported: container-based with LXC (starting from version 4.0 replacing OpenVZ used in version up to 3.4, included), and full virtualization with KVM. It includes a web-based management interface.

Proxmox VE is licensed under the GNU Affero General Public License, version 3.

🔗 Technology 🔗 Computing 🔗 Computing/Software 🔗 Software 🔗 Software/Computing 🔗 C/C++ 🔗 Java

ArcaOS is a proprietary operating system based on OS/2, developed and marketed by Arca Noae, LLC under license from IBM. It was first released in 2017 and builds on OS/2 Warp 4.52 by adding support for new hardware, fixing defects and limitations in the operating system, and by including new applications and tools, and includes some Linux/Unix tool compatibility. It is targeted at professional users who need to run their OS/2 applications on new hardware, as well as personal users of OS/2.

Like OS/2 Warp, ArcaOS is a 32-bit single user, multiprocessing, preemptive multitasking operating system for the x86 architecture. It is supported on both physical hardware and virtual machine hypervisors.

🔗 Computing 🔗 Microsoft Windows 🔗 Microsoft Windows/Computing

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.

🔗 Computing

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.

🔗 Computing 🔗 Electronics

1-Wire is a wired half-duplex serial bus designed by Dallas Semiconductor that provides low-speed (standard 16.3 kbit/s; "overdrive" at 10×) data communication and supply voltage over a single conductor.

1-Wire is similar in concept to I²C, but with lower data rates and longer range. It is typically used to communicate with small inexpensive devices such as digital thermometers and weather instruments. A network of 1-Wire devices with an associated master device is called a MicroLAN. The protocol is also used in small, 16 mm electronic keys known as a Dallas key or iButton.

One distinctive feature of the bus is the possibility of using only two conductors — data and ground. To accomplish this, 1-Wire devices integrate a small capacitor (~800 pF) to store charge, which powers the device during periods when the data line is active.

🔗 United States/U.S. Government 🔗 United States 🔗 History 🔗 Computing 🔗 Cryptography 🔗 Cryptography/Computer science

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.