MacOS Mojave

macOS Mojave ( ) (version 10.14) is the fifteenth major release of macOS, Apple Inc.'s desktop operating system for Macintosh computers. Mojave was announced at Apple's Worldwide Developers Conference on June 4, 2018, and was released to the public on September 24, 2018. The operating system's name refers to the Mojave Desert and is part of a series of California-themed names that began with OS X Mavericks. It succeeded macOS High Sierra and was followed by macOS Catalina.
macOS Mojave brings several iOS apps to the desktop operating system, including Apple News, Voice Memos, and Home. It also includes a much more comprehensive "dark mode", is the final version of macOS to support 32-bit application software, and is also the last version of macOS to support the iPhoto app, which had already been superseded in OS X Yosemite (10.10) by the newer Photos app.
Mojave was well received and was supplemented by point releases after launch.
Overview.
macOS Mojave was announced on June 4, 2018, at Apple's annual Worldwide Developers Conference in San Jose, California. Apple pitched Mojave, named after the California desert, as adding "pro" features that would benefit all users. The developer preview of the operating system was released for developers the same day, followed by a public beta on June 26. The retail version of 10.14 was released on September 24. It was followed by several point updates and supplemental updates.
System requirements.
Mojave requires a GPU that supports Metal, and the list of compatible systems is more restrictive than the previous version, macOS High Sierra. Compatible models are the following Macintosh computers running OS X Mountain Lion or later:
macOS Mojave requires at least 2GB of RAM as well as 12.5GB of available disk space to upgrade from OS X El Capitan, macOS Sierra, or macOS High Sierra, or 18.5GB of disk space to upgrade from OS X Yosemite and earlier releases. Some features are not available on all compatible models.
Changes.
System updates.
macOS Mojave deprecates support for several legacy features of the OS. The graphics frameworks OpenGL and OpenCL are still supported by the operating system, but will no longer be maintained; developers are encouraged to use Apple's Metal library instead.
OpenGL is a cross-platform graphics framework designed to support a wide range of processors. Apple chose OpenGL in the late 1990s to build support for software graphics rendering into the Mac, after abandoning QuickDraw 3D. At the time, moving to OpenGL allowed Apple to take advantage of existing libraries that enabled hardware acceleration on a variety of different GPUs. As time went on, Apple has shifted its efforts towards building its hardware platforms for mobile and desktop use. Metal makes use of the homogenized hardware by abandoning the abstraction layer and running on the "bare metal". Metal reduces CPU load, shifting more tasks to the GPU. It reduces driver overhead and improves multithreading, allowing every CPU thread to send commands to the GPU.
macOS does not natively support Vulkan, the Khronos group's official successor to OpenGL. The MoltenVK library can be used as a bridge, translating most of the Vulkan 1.0 API into the Metal API.
Continuing the process started in macOS High Sierra (10.13), which issued warnings about compatibility with 32-bit applications, Mojave issues warnings when opening 32-bit apps that they will not be supported in future updates. In macOS Mojave 10.14, this alert appears once every 30 days when launching the app, as macOS 10.15 will not support 32-bit applications.
When Mojave is installed, it will convert solid-state drives (SSDs), hard disk drives (HDDs), and Fusion Drives, from HFS Plus to APFS. On Fusion Drives using APFS, files will be moved to the SSD based on the file's frequency of use and its SSD performance profile. APFS will also store all metadata for a Fusion Drive's file system on the SSD.
New data protections require applications to get permission from the user before using the Mac camera and microphone or accessing system data like user Mail history and Messages database.
Removed features.
Mojave removes integration with Facebook, Twitter, Vimeo, and Flickr, which was added in OS X Mountain Lion.
The only supported Nvidia graphics cards are the Quadro K5000 and GeForce GTX 680 Mac Edition.
Applications.
Mojave features changes to existing applications as well as new ones. Finder now has metadata preview accessed via View > Show Preview, and many other updates, including a Gallery View (replacing Cover Flow) that lets users browse through files visually. After a screenshot is taken, as with iOS, the image appears in the corner of the display. The screenshot software can now record video, choose where to save files, and be opened via + + .
Safari's Tracking Prevention features now prevent social media "Like" or "Share" buttons and comment widgets from tracking users without permission. The browser also sends less information to web servers about the user's system, reducing the chance of being tracked based on system configuration. It can also automatically create, autofill, and store strong passwords when users create new online accounts; it also flags reused passwords so users can change them.
A new Screenshot app was added to macOS Mojave to replace the Grab app. Screenshot can capture a selected area, window or the entire screen as well as screen record a selected area or the entire display. The Screenshot app is located in the codice_1 folder, as was the Grab app. Screenshot can also be accessed by pressing ++.
FaceTime.
macOS 10.14.1, released on October 30, 2018, adds Group FaceTime, which lets users chat with up to 32 people at the same time, using video or audio from an iPhone, iPad or Mac, or audio from Apple Watch. Participants can join in mid-conversation.
App Store.
The Mac App Store was rewritten from the ground up and features a new interface and editorial content, similar to the iOS App Store. A new 'Discover' tab highlights new and updated apps; Create, Work, Play and Develop tabs help users find apps for a specific project or purpose.
iOS apps ported to macOS.
Four new apps (News, Stocks, Voice Memos and Home) are ported to macOS Mojave from iOS, with Apple implementing a subset of UIKit on the desktop OS. Third-party developers would be able to port iOS applications to macOS in 2019.
With Home, Mac users can control their HomeKit-enabled accessories to do things like turn lights off and on or adjust thermostat settings. Voice Memos lets users record audio (e.g., personal notes, lectures, meetings, interviews, or song ideas), and access them from iPhone, iPad or Mac. Stocks delivers curated market news alongside a personalized watchlist, with quotes and charts.
User interface.
Dark mode and accent colors.
Mojave introduces "Dark Mode", a Light-on-dark color scheme that darkens the user interface to make content stand out while the interface recedes. Users can choose dark or light mode when installing Mojave, or any time thereafter from System Preferences.
Apple's built-in apps support Dark Mode. App developers can implement Dark mode in their apps via a public API.
A limited dark mode that affected only the Dock, menu bar, and drop-down menus was previously introduced in OS X Yosemite.
Desktop.
Stacks, a feature introduced in Mac OS X Leopard, now lets users group desktop files into groups based on file attributes such as file kind, date last opened, date modified, date created, name and tags. This is accessed via View > Use Stacks.
macOS Mojave features a new Dynamic Desktop that automatically changes specially made desktop backgrounds (two of which are included) to match the time of day.
Dock.
The Dock has a space for recently used apps that have not previously been added to the Dock.
Preferences.
macOS update functionality has been moved back to System Preferences from the Mac App Store. In OS X Mountain Lion (10.8), system and app updates moved to the App Store from Software Update.
Reception.
Mojave was generally well received by technology journalists and the press. "The Verge"s Jacob Kastrenakes considered Mojave a relatively minor update, but Kastrenakes and Jason Snell thought the release hinted at the future direction of macOS. In contrast, "Ars Technica"s Andrew Cunningham felt that "Mojave feels, if not totally transformative, at least more "consequential" than the last few macOS releases have felt." Cunningham highlighted productivity improvements and continued work on macOS's foundation.
TechCrunch’s Brian Heater dubbed Mojave "arguably the most focused macOS release in recent memory", playing an important role in reassuring professional users that it was still committed to them.
Mojave's new features were generally praised. Critics welcomed the addition of Dark Mode.


IBM 5550

IBM 5550 is a personal computer series that IBM marketed in Japan, Korea, Taiwan and China in the 1980s and 1990s, for business use customers. In Japan, it was introduced in 1983 and promoted as "" because it had three roles in one machine: a PC, a word processing machine which was traditionally marketed as a machine different from a PC in Japan, and an IBM-host attached terminal.
General.
The IBM PC that had been marketed by IBM since 1981, using Intel 8088, was not powerful enough to process the far eastern languages of Japanese, Korean and Chinese. Nor was the resolution of IBM PC's display high enough to show the complex characters of these languages.
The IBM 5550 was first introduced in Japan in March 1983, using Intel 8086 microprocessor and was called "Multistation 5550" because it had three roles in one machine: a PC, a word processing machine which was traditionally marketed in Japan as a machine different from a PC, and an online terminal.
After the Japanese 5550 models, Korean, Traditional Chinese and Simplified Chinese models were also introduced. IBM 5550 initially used its own architecture, but, later since 1987, was changed to use IBM Personal System/2's Micro Channel Architecture, being renamed as Personal System/55.
In Japan, Kiyoshi Atsumi, a film actor, was used to promote the 5550. IBM later introduced IBM JX for home users in Japan, Australia and New Zealand, and DOS/V for both business and home users in Japan.
Features.
The 5550 was originally planned as a terminal with a combination of word processing and personal computing targeted for Japanese computer market. To display 24 dots Mincho kanji typeface which was also used in many Japanese word processing machines, the 5550 had high display resolution such as a 1024×768 pixel graphic screen. The first model of 5550 was designed to read a display font from an external storage for multilingual support, including Chinese and Korean languages.
The 5550 fulfills three roles, via the following components:
The original Bunsho Program and emulators booted from a floppy disk without Nihongo DOS. They used a proprietary disk format which couldn't be read from Nihongo DOS, so users had to replace floppy disks or set the boot partition to switch between two programs. Also, they had to use a conversion program to exchange data. Later, they were ported for Nihongo DOS, and functions were gradually implemented. 3270 Kanji Emulation, 5250 Kanji Emulation and Bunsho Program were superseded by Nihongo 3270 PC in October 1983, Nihongo 5250 PC in September 1984 and DOS Bunsho Program in May 1986.
The first generation of IBM 5550 has up to three 5¼ inch double-density (720 KB) floppy drives because the Bunsho Program uses three floppy disks; program disk, font disk, and user data disk. Later models contain a font ROM card as other 1980's Japanese personal computers did.
Development.
 of IBM Fujisawa Development Laboratory planned the terminal with a combination of word processor and personal computer, called the Multi-functional Workstation, and he proposed it at the headquarter in March 1981. The development team was founded as an Independent Business Unit (IBU).
The team set goals for IBM 5550 that the machine was usable for both word processing and personal computing on the same architecture at least 3-5 years. They tried to build the 5550 from the IBM Displaywriter System 6580, the English word processor developed in Austin office in 1980, and the IBM Personal Computer developed in Boca Raton office, but it was difficult to combine different types of machines.
Considering price–performance ratio and continuity of an architecture, the team examined processors chosen from Intel's and other manufacturers. The IBM PC used an Intel 8088, but the 5550 employed an Intel 8086 because bus speed largely influenced for performance of the machine which had high display resolution.
To gain an advantage over competitors in Japanese word processing, 24 pixel font models render characters in a box of 26×29 pixels, and the total display resolution is 1066×725 pixels calculated with box width by 41×25 text. 16 pixel font models render characters in a box of 18×21 pixels, and the total display resolution is 738×525 pixels. The 5550 had one more column than 40 columns of usual Japanese computers, which enabled line breaking.
For personal computing, Nihongo DOS K2.00 had been developed by Microsoft. It was the second Japanese localization of MS-DOS 2.0 followed to Toshiba's PASOPIA 16. Nihongo DOS bundled the Microsoft BASIC interpreter which designed for the 5550. Programming languages and the Japanese version of Multiplan were also provided.
The team didn't consider the machine was used for online communication, but they realized its importance during the development. They decided to add a role of a terminal in January 1982. This change extended its development term. In May 1982 Business Show (one of computer industry exhibitions in Japan), IBM Japan only displayed the IBM PC as a reference material. They unveiled the development of 5550 in fall 1982.
IBM Japan didn't have a factory for mass production of personal computers, so the production of 5550 was outsourced to some companies. System units, hard disks, and monitors were manufactured by Matsushita Electric Industrial, printers by Oki Electric Industry, and keyboards by Alps Electric.
Competition.
In Japan, Multistation 5550 competed against:
Reception.
"BYTE" in 1983 speculated that "we may soon see a similar machine here in America". Describing the 5550 as "a true workstation", the magazine envisioned the computer as filling the "considerable gulf above the PC", and a rival to the IBM System/36 minicomputer. It praised the 5550's "unprecedented" combination of kanji support with high-end word-processing capability, and reported that in Japan an ecosystem of vendors providing products for the computer was forming. The magazine concluded that "if the American PC is any precedent, the market should soon be filled with 5550 software".
The 5550 was primarily sold for large enterprises who used IBM's mainframe computer. Meiji Life who used the IBM 3081 mainframe decided to purchase about 500 units of the 5550 in 1983. A manager of its System Development section said, "IBM supports us to satisfy our demand for the communication software. We are planning to replace all of our IBM terminals. A new personal computer must respond for the host computer as fast as a terminal, and it must have various communication softwares."
In Japan, the 5550 had annual sales of 70,000 units in 1985, and the Nikkei Personal Computing magazine reported in 1986 that the 5550 had the largest personal computer share of 30% in the corporate sector.


Windows Display Driver Model

Windows Display Driver Model (WDDM) is the graphic driver architecture for video card drivers running Microsoft Windows versions beginning with Windows Vista.
It is a replacement for the previous Windows 2000 and Windows XP display driver model XDDM/XPDM and is aimed at enabling better performance graphics and new graphics functionality and stability. Display drivers in Windows Vista and Windows 7 can choose to either adhere to WDDM or to XDDM. With the removal of XDDM from Windows 8, however, WDDM became the only option.
WDDM provides the functionality required to render the desktop and applications using Desktop Window Manager, a compositing window manager running on top of Direct3D. It also supports new DXGI interfaces required for basic device management and creation. The WDDM specification requires at least Direct3D 9-capable video card and the display driver must implement the device driver interfaces for the Direct3D 9Ex runtime in order to run legacy Direct3D applications; it may optionally implement runtime interfaces for Direct3D 10 and higher.
Features enabled by the WDDM.
WDDM drivers enable new areas of functionality which were not uniformly provided by earlier display driver models. These include:
Virtualized video memory.
In the context of graphics, virtualization means that individual processes (in user mode) cannot see the memory of adjacent processes even by means of insertion of forged commands in the command stream. WDDM drivers allow video memory to be virtualized, and video data to be paged out of video memory into system RAM. In case the video memory available turns out to be insufficient to store all the video data and textures, currently unused data is moved out to system RAM or to the disk. When the swapped out data is needed, it is fetched back. Virtualization could be supported on previous driver models (such as the XP Driver Model) to some extent, but was the responsibility of the driver, instead of being handled at the runtime level.
Scheduling.
The runtime handles scheduling of concurrent graphics contexts. Each list of commands is put in a queue for execution by the GPU, and it can be preempted by the runtime if a more critical task arrives and if it has not begun execution. This differs from native threads on the CPU where one task cannot be interrupted and therefore can take longer than necessary and make the computer appear less responsive. A hybrid scheduling algorithm between native and light threads with cooperation between the threads would achieve seamless parallelism. It is important to note that scheduling is not a new concept but it was previously the responsibility of individual driver developers. WDDM attempts to unify the experience across different vendors by controlling the execution of GPU tasks.
Cross-process sharing of Direct3D surfaces.
A Direct3D graphics surface is the memory area that contains information about the textured meshes used for rendering a 2D or 3D scene. WDDM allows Direct3D surfaces to be shared across processes. Thus, an application can incorporate a mesh created by another application into the scene it is rendering. Sharing textures between processes before WDDM was difficult, as it would have required copying the data from video memory to system memory and then back to video memory for the new device.
Enhanced fault-tolerance.
If a WDDM driver hangs or encounters a fault, the graphics stack will restart the driver. A graphics hardware fault will be intercepted and if necessary the driver will be reset.
Drivers under Windows XP were free to deal with hardware faults as they saw fit either by reporting it to the user or by attempting to recover silently. With a WDDM driver, all hardware faults cause the driver to be reset and the user will be notified by a popup; this unifies the behavior across vendors.
Previous drivers were fully implemented in kernel mode, whereas WDDM is implemented partly in user mode. If the user mode area fails with an unrecoverable error, it will, at the most, cause the application to quit unexpectedly instead of producing a blue screen error as it would in previous driver models.
WDDM also allows the graphics hardware to be reset and users to update drivers without requiring a reboot.
Limitations.
The new driver model requires the graphics hardware to have Shader Model 2.0 support at least, since the fixed function pipeline is now translated to 2.0 shaders. However, according to Microsoft as of 2009, only about 1–2 percent of the hardware running Windows Vista used the XDDM, with the rest already WDDM capable. It also requires some other hardware features; consequently some SM 2.0-supporting hardware such as the Intel GMA 900 fails the WDDM certification.
One of the limitations of WDDM driver model version 1.0 is that it does not support multiple drivers in a multi-adapter, multi-monitor setup. If a multi-monitor system has more than one graphics adapter powering the monitors, both the adaptors must use the same WDDM driver. If more than one driver is used, Windows will disable one of them. WDDM 1.1 does not have this limitation.
WDDM 1.0/1.1 does not allow some modes that were previously handled by the driver such as spanning mode (stretching the desktop across two monitors) although "Dual View" is still available.
Need for a new display driver model.
One of the chief scenarios the Windows Display Driver Model enables is the Desktop Window Manager. Since the desktop and application windows managed by DWM are Direct3D applications, the number of open windows directly affects the amount of video memory required. Because there is no limit on the number of open windows, the video memory available may prove insufficient, necessitating virtualization. As the window contents that DWM composes into the final desktop are generated by different processes, cross-process surface sharing is necessary. Also, because there can be other DirectX applications running alongside DWM on the DWM-managed desktop, they must be able to access the GPU in a shared manner, necessitating scheduling.
Though this is true for Microsoft's implementation of a composited desktop under Windows Vista, on the other hand, a composited desktop need not theoretically require a new display driver model to work as expected. Successful implementations of composited desktops were done before Windows Vista on other platforms such as Quartz, Compiz, WindowFX. The approach Microsoft attempted was to try to make sure WDDM was a unified experience across different GPUs from multiple vendors by standardizing their features and performance. The software features missing from other driver models could be made immaterial by extensions or if a less restrictive or simply different driver model was in place.
History.
WDDM 1.0.
Windows Vista introduced WDDM 1.0 as a new display driver architecture designed to be better performing, more reliable, and support new technologies including HDCP. Hybrid Sleep, which combines hibernation and sleep mode functionality for enhanced stability in the event of power failure, also requires WDDM.
WDDM 1.1.
Windows 7 supports major additions to WDDM known as WDDM 1.1; the details of this new version were unveiled at WinHEC 2008. New features include:
Hardware acceleration of GDI and Direct2D/DirectWrite operations helps reduce memory footprint in Windows 7, because DWM compositing engine no longer needs to keep a system memory copy of all surfaces used by GDI/GDI+, as in Windows Vista.
DXGI 1.1, Direct3D 11, Direct2D, and DirectWrite were made available with Windows Vista Platform Update; however GDI/GDI+ in Vista continues to rely on software rendering and the Desktop Window Manager continues to use Direct3D 9Ex.
WDDM 1.1 drivers are backward compatible with WDDM 1.0 specification; both 1.0 and 1.1 drivers can be used in Windows Vista with or without the Platform Update.
WDDM 1.2.
Windows 8 includes WDDM 1.2 and DXGI 1.2. New features were first previewed at the Build 2011 conference and include performance improvements as well as support for stereoscopic 3D rendering and video playback.
Other major features include preemptive multitasking of the GPU with finer granularity (DMA buffer, primitive, triangle, pixel, or instruction-level), reduced memory footprint, improved resource sharing, and faster timeout detection and recovery. 16-bit color surface formats (565, 5551, 4444) are mandatory in Windows 8, and Direct3D 11 Video supports YUV 4:4:4/4:2:2/4:2:0/4:1:1 video formats with 8, 10, and 16-bit precision, as well as 4 and 8-bit palettized formats.
WDDM 1.2 supports display-only and render-only WDDM drivers, such as "Microsoft Basic Display Driver" and WARP-based "Microsoft Basic Render Driver" which replaced kernel-mode VGA driver.
WDDM 1.0/1.1 only allows rudimentary task scheduling using "batch queue" granularity; improvements to multitasking, as well as fast context switching and support for virtual memory, were initially expected in versions tentatively named WDDM 2.0 and WDDM 2.1, which were announced at WinHEC 2006.
WDDM 1.3.
Windows 8.1 includes WDDM 1.3 and DXGI 1.3. New additions include the ability to trim DXGI adapter memory usage, multi-plane overlays, overlapping swap chains and swap chain scaling, select backbuffer subregion for swap chain and lower-latency swap chain presentation. Driver feature additions include wireless displays (Miracast), YUV format ranges, cross-adapter resources and GPU engine enumeration capabilities. Graphics kernel performance improvements.
WDDM 2.0.
Windows 10 includes WDDM 2.0, which is designed to dramatically reduce workload on the kernel-mode driver for GPUs that support virtual memory addressing, to allow multithreading parallelism in the user-mode driver and result in lower CPU utilization. Windows 10 also includes DXGI 1.4.
Direct3D 12 API, announced at Build 2014, requires WDDM 2.0. The new API will do away with automatic resource-management and pipeline-management tasks and allow developers to take full low-level control of adapter memory and rendering states.
The display driver model from Windows 8.1 and Windows Phone have converged into a unified model for Windows 10.
A new memory model is implemented that gives each GPU a per-process virtual address space. Direct addressing of video memory is still supported by WDDMv2 for graphics hardware that requires it, but that is considered a legacy case. IHVs are expected to develop new hardware that supports virtual addressing. Significant changes have been made to the DDI to enable this new memory model.
WDDM 2.1.
Windows 10 Anniversary Update (version 1607) includes WDDM 2.1, which supports Shader Model 6.0 (mandatory for feature levels 12_0 and 12_1), and DXGI 1.5 which supports HDR10 - a 10-bit high dynamic range, wide gamut format defined by ITU-T Rec. 2100/Rec.2020 - and variable refresh rates.
WDDM 2.2.
Windows 10 Creators Update (version 1703) includes WDDM 2.2, which is tailored for virtual, augmented and mixed reality with stereoscopic rendering for the Windows Mixed Reality platform, and DXGI 1.6.
WDDM 2.3.
Windows 10 Fall Creators Update (version 1709) includes WDDM 2.3.
The following is a list of new features for Windows Display driver development in Windows 10, version 1709:
WDDM 2.4.
Windows 10 April 2018 Update (version 1803) includes WDDM 2.4. Updates to display driver development in Windows 10 version 1803 include the following features.:
WDDM 2.5.
Windows 10 October 2018 Update (Version 1809) Includes WDDM 2.5. Updates to Display driver development in Windows 10, version 1809 include the following features:
WDDM 2.6.
Windows 10 May 2019 Update (Version 1903) includes WDDM 2.6. Updates to display driver development in Windows 10 version 1903 include the following features:
WDDM 2.7.
Windows 10 May 2020 Update (Version 2004) includes WDDM 2.7. Updates to display driver development in Windows 10 version 2004 include the following features:
WDDM 2.8.
Windows 10 Insider Preview Manganese included WDDM 2.8, but no driver was ever publicly demonstrated to support it and it has been skipped for "Iron" and "Cobalt" development releases.
WDDM 2.9.
WDDM 2.9 in Windows 10 Insider Preview "Iron" will bring support for GPU hardware acceleration to the Windows Subsystem for Linux 2 (WSL 2) and support for feature level 12_2 and HLSL Shader Model 6.6.
WDDM 3.0.
WDDM 3.0 appeared on Windows 10 Insider Preview "Cobalt" build 21301. WDDM 3.0 improves graphics architecture in Windows Subsystem for Linux adding:


IBM 386SLC

The 386SLC was an Intel-licensed version of the 386SX (32-bit internal, 16-bit external, 24-bit memory addressing), developed and manufactured by IBM in 1991. It included power-management capabilities and an 8KB internal CPU cache, which enabled it to yield comparable performance to 386DX processors of the same clock speed, which were considerably more expensive. Known inside IBM as "Super Little Chip" for its initials, it was used in the IBM PS/2 35, 40 and 56 Series and in the IBM PS/ValuePoint 325T, but never gained much market share. This was mainly due to an agreement with Intel, in which IBM was not allowed to sell their CPUs if they were not part of a system or upgrade board. It was also marketed as an optional upgrade for 8086-equipped IBM PS/2 25 Series computers.
Design and Technology.
Built with complementary metal oxide semiconductor (CMOS) technology, the IBM 386SLC had a 161-square millimeter die. It was available with clock speeds of 16, 20, and 25 MHz. The 25 MHz model produced only 2.5 watts of dissipated power, making it especially well suited for laptops and other portable devices.
Despite the fact that the SLC and DLC chips are bus compatible with i386SX and i386DX respectively, they can not be used as drop-in replacements as they are not pin-compatible.
IBM 486SLC.
Is an improved version of the IBM 386SLC, based on the Intel core. IBM 486SLC featured 16Kb of L1 cache and the i486 instruction set. It had 1.349 million transistors and a 69mm² die. It was manufactured in 1992. It came in a 100-pin BQFP package, with 33 MHz FSB speed. The 486SLC was also available in a clock-doubled version, the 486SLC2 (50 & 66 MHz), and later in a clock tripled-version, the 486SLC3 (60, 75, & 100 MHz). Clock-for-clock, it was substantially faster than the similarly-named Cyrix part, yielding performance broadly comparable to a similarly-clocked 486SX in the 16-bit applications of its day. However, its narrow 16-bit bus, limited memory addressing capability (16 MB) and lack of on-chip FPU would prove to be major disadvantages under the new generation of 32-bit operating systems (such as Windows 95) that would become popular in following years.
It is suspected the clock tripled 486SLC3 part did not in fact actually exist as a stand-alone product. All known instances of 486SLC3 CPUs are reportedly in the 132-pin PQFP packaging with the extra address lines not connected (a 486BL3 running in 16-bit mode).
IBM 486BL (Blue Lightning).
The 486BL is a fully 32-bit version of the 486SLC, with 1.4 million transistors on a 82mm² die, using a 0.8 µm CMOS process. It came in a 132-pin QFP package. In July, 1993 IBM produced clock-doubled and clock-tripled versions of the chip, the 486BL2 and 486BL3. The chips were available from 50 to 100 MHz and were sold by IBM only.
IBM later marketed Socket 3 168-pin PGA Blue Lightning 486 CPUs, but these are technically not related to earlier Blue Lightning models as they are based on the Cyrix Cx486 CPU core. They can be distinguished by the inclusion of a "DX" (or DX2, DX4) legend somewhere on the label, setting them apart from the earlier 386-derived, nominally 486SX-equivalent processors.
IBM's adoption of Cyrix cores for their self-manufactured CPUs, very restricted release of information regarding the earlier generations, and policy of only printing cryptic in-house part numbers on first-generation Blue Lightning chips rather than any easily recognised family name has led to some confusion amongst the retro/low-end PC community as to their actual name. As a result the first-generation BLs are often commonly referred to as "486DLC" (and 486DLC2, DLC3/4) CPUs, a logical and 386-alike progression from the 16-bit SLC models - even though IBM themselves do not appear to have used that name in any official materials, simply calling them "Blue Lightning" or shortening the name to "486BL". The "486DLC" name itself is instead one used by Cyrix for their wholly distinct (from IBM/Intel's product) predecessors to the "4x86" generation (itself the basis of IBM's later 486DX line), as openly and clearly printed on the processor cases. However, in the absence of any better common name for the line, "IBM 486DLC" has stuck, and in practice it would be difficult to confuse any two of the three different model lines for each other due to clearly different packaging and branding.


Microsoft Realtime Compression Interface


WinChip

The WinChip series was a low-power Socket 7-based x86 processor designed by Centaur Technology and marketed by its parent company IDT.
Overview.
Design.
The design of the WinChip was quite different from other processors of the time. Instead of a large gate count and die area, IDT, using its experience from the RISC processor market, created a small and electrically efficient processor similar to the 80486, because of its single pipeline and in-order execution microarchitecture. It was of much simpler design than its Socket 7 competitors, such as AMD K5/K6 and Intel Pentium, which were superscalar and based on "dynamic" translation to buffered micro-operations with advanced instruction reordering (out of order execution).
Use.
WinChip was, in general, designed to perform well with popular applications that didn't do many (if any) floating point calculations. This included operating systems of the time and the majority of software used in businesses. It was also designed to be a drop-in replacement for the more complex, and thus more expensive, processors it was competing with. This allowed IDT/Centaur to take advantage of an established system platform (Intel's Socket 7).
Later developments.
WinChip 2, an update of C6, retained the simple in-order execution pipeline of its predecessor, but added dual MMX/3DNow! processing units that could operate in superscalar execution. This made it the only non-AMD CPU on Socket 7 to support 3DNow! instructions. WinChip 2A added fractional multipliers and adopted a 100 MHz front side bus to improve memory access and L2 cache performance. It also adopted a performance rating nomenclature instead of reporting the real clock speed, similar to contemporary AMD and Cyrix processors.
Another revision, the WinChip 2B, was also planned. This featured a die shrink to 0.25 μm, but was only shipped in limited numbers.
A third model, the WinChip 3, was planned as well. This was meant to receive a doubled L1 cache, but the W3 CPU never made it to market.
Performance.
Although the small die size and low power-usage made the processor notably inexpensive to manufacture, it never gained much market share. WinChip C6 was a competitor to the Intel Pentium and Pentium MMX, Cyrix 6x86, and AMD K5/K6. It performed adequately, but only in applications that used little floating point math. Its floating point performance was simply well below that of the Pentium and K6, being even slower than the Cyrix 6x86.
Decline.
The industry's move away from Socket 7 and the release of the Intel Celeron processor signalled the end of the WinChip. In 1999, the Centaur Technology division of IDT was sold to VIA. Although VIA branded the processors as "Cyrix," the company initially used technology similar to the WinChip in its Cyrix III line.


Radeon X300-X600 series

ATI released the Radeon X300 and X600 boards. These were based on the "RV370" (110 nm process) and "RV380" (130 nm Low-K process) GPU respectively. They were nearly identical to the chips used in Radeon 9550 and 9600, only differing in that they were native PCI Express offerings. These were very popular for Dell and other OEM companies to sell in various configurations; connectors: DVI vs. DMS-59, card height: full-height vs. half-height.
Later the Radeon X550 was launched, using the same chip as Radeon X300 graphics card (RV370).


UltraSPARC IIi


LXLE Linux

LXLE is a Linux distribution based upon the most recent Ubuntu/Lubuntu LTS release, using the LXDE desktop environment. LXLE is a lightweight distro, with a focus on visual aesthetics, that works well on both old and new hardware.
Reception.
In a January 2014 review in "Full Circle Magazine", Gabriele Tettamanzi noted that LXLE has some minor localization issues but otherwise described it as a nice "light and fast" desktop "rich" with software and "stable".
Jesse Smith reviewed LXLE 12.04.3 for DistroWatch Weekly:
Jesse Smith also reviewed LXDE 14.04.


Dynamic Debugging Tool


GENCMD.CMD


John Quarterman

John S. Quarterman (born April 27, 1954) is an American author and long time Internet participant. He wrote one of the classic books about networking prior to the commercialization of the Internet. He has also written about risk management.
Biography.
Quarterman grew up in the Bemiss community, near Valdosta, Georgia, USA.
He first used the ARPANET in 1974 while attending Harvard, and worked on UNIX ARPANET software at BBN (the original prime contractor on the ARPANET) from 1977 to 1981. He was twice elected to the Board of Directors of the USENIX Association, a professional association related to the UNIX operating system. While on that board, he was instrumental in its vote in 1987 to approve the first funding received by UUNET, which, along with PSINet, became one of the first two commercial Internet Service Providers (ISPs).
He co-founded the first Internet consulting firm in Texas (TIC) in 1986, and co-founded one of the first ISPs in Austin (Zilker Internet Park, since sold to Jump Point). He was a founder of TISPA, the Texas ISP Association.
He was a founder and Chief Technology Officer of Matrix NetSystems Inc., established as Matrix Information and Directory Services (MIDS) in 1990.
Quarterman published the first maps of the whole Internet; conducted the first Internet Demographic Survey and started the first continuing series of performance data about the entire Internet in 1993, on the web since 1995 in the Internet Weather Report, and also visible as Internet Average, plus comparisons of ISPs visible as ISP Ratings.
Inter@ctive Week listed John Quarterman as one of the 25 Unsung Heroes of the Internet in 1998, saying ..."As president of [MIDS], Quarterman, 43, is to Net demographics what The Gallup Organization is to opinion polls." Internet World interviewed Quarterman at length with a full page picture in its June 1996 issue, as Surveyors of Cyberspace."
On September 21, 2006, Quarterman served as a panelist with Hank Hultquist and Michele Chaboudy at a joint meeting of the IEEE Central Texas Section and Communications and Signal Processing Chapters titled "Network Neutrality: Altruism or Capitalism" at St. Edward's University in Austin, Texas. He also organized a November 2, 2006 panel on Net Neutrality for EFF-Austin, featuring Quarterman and Hank Hultquist, Michael Hathaway, and Austin Bay.


Genesis Nomad

The Genesis Nomad, also known as Sega Nomad, is a handheld game console manufactured by Sega and released in North America in October 1995. The Nomad is a portable variation of the Sega Genesis home video game console (known as the Mega Drive outside North America). Based on the Mega Jet, a portable version of the home console designed for use on airline flights in Japan, Nomad was the last handheld console released by Sega. In addition to functioning as a portable device, it was designed to be used with a television set via a video port. Released late in the Genesis era, the Nomad had a short lifespan.
Sold exclusively in North America, the Nomad was never officially released worldwide, and employs a regional lockout. Sega's focus on the Sega Saturn left the Nomad under-supported, and the handheld itself was incompatible with several Genesis peripherals, including the Power Base Converter, the Sega CD, and the 32X. About 1 million units of the Nomad were sold, and it is considered a commercial failure.
History.
The Sega Genesis was Sega's entry into the 16-bit era of video game consoles. In Japan, Sega released the Mega Jet, a portable version of the Mega Drive for use on Japan Airlines flights. The Mega Jet requires a connection to a television screen and a power source, and so outside of airline flights can only be used in cars equipped with a television set and cigarette lighter receptacle. On planes, the Mega Jet was connected into armrest monitors. It had a limited consumer release in Japanese department stores in 1994, but did not see success.
Planning to release a new handheld console to succeed the Game Gear, Sega originally intended to produce a system with a touchscreen interface two years before the Game.com handheld by Tiger Electronics. However, touchscreen technology was expensive at the time, so Sega instead released the Genesis Nomad, a handheld version of the Genesis. The development codename was "Project Venus". Sega hoped to capitalize on the Genesis's popularity in North America. At the time, the Genesis Nomad was the only handheld console that could connect to a television.
The Nomad was released in October 1995 in North America only. The release was five years into the market span of the Genesis, with an existing library of more than 500 Genesis games. While Sega Technical Institute's "The Ooze" was originally planned as a launch game, it was not included. According to former Sega of America research and development head Joe Miller, the Nomad was not intended to replace the Game Gear, and Sega of Japan had few plans for the new handheld. Sega was supporting five different consoles: Saturn, Genesis, Game Gear, Pico, and the Master System, as well as the Sega CD and 32X add-ons. In Japan, the Mega Drive had never been successful and the Saturn was more successful than Sony's PlayStation, so Sega Enterprises CEO Hayao Nakayama decided to focus on the Saturn, resulting in the end of support for the Genesis and Genesis-based products. Additionally, the Game Boy, Nintendo's handheld console that had been dominant in the market, became even more dominant with the release of "Pokémon Red" and "Blue". This meant the Nomad was not successful. By 1999, the Nomad was being sold at less than a third of its original price.
Technical specifications.
Similar to the Genesis and the Mega Jet, the Nomad's main CPU is a Motorola 68000. Possessing similar memory, graphics, and sound capabilities, the Nomad is nearly identical to the full-size console; the only variation is that it is completely self-sufficient. However, due to the smaller screen size it suffers from screen blurring, particularly during fast scrolling. The Nomad has a 3.25 inch diagonal backlit color LC display and an A/V output that allows the Nomad to be played on a television screen. Design elements of the handheld were made similar to the Game Gear, but included six buttons for full compatibility with later Genesis releases. Also included were a red power switch, headphone jack, volume dial, and separate controller input for multiplayer games. The controller port functions as player 2, so single-player games cannot be played with a Genesis controller. The Nomad could be powered by an AC adapter, a battery recharger known as the Genesis Nomad PowerBack, or six AA batteries, which provide a battery life of two to three hours. The Nomad consumed more power (DC 9V, 3.5W) than Sega's earlier portable gaming console, the Game Gear (DC 9V, 3W).
The Nomad is fully compatible with several Genesis peripherals, including the Sega Activator, Team Play Adaptor, Mega Mouse, and the Sega Channel and XBAND network add-ons. However, the Nomad is not compatible with the Power Base Converter, Sega CD, or 32X. This means the Nomad can only play Genesis games, whereas the standard Genesis can also play Master System, Sega CD, and 32X game with the respective add-ons.
Game library.
The Nomad does not have its own game library, but instead plays Genesis games. At the time of its launch, the Nomad had over 500 games available for play. However, no pack-in game was included. The Nomad can boot unlicensed, homebrew, and bootleg games made for the Genesis. Some earlier third-party games have compatibility issues when played on the Nomad, but can be successfully played through the use of a Game Genie. Likewise, due to its lack of compatibility with any of the Genesis' add-ons, it is unable to play any games for the Sega Master System, Sega CD, or Sega 32X. The Nomad employs two different regional lockout methods, physical and software, but methods have been found to bypass these.
Reception and legacy.
Reviewing the Nomad shortly after launch, "Game Players" considered the price "a bit steep", but said it was the best portable system on the market, and recommended it over the stock Genesis since it could play all the same games in a portable format. In a 1997 year-end review, a team of four "Electronic Gaming Monthly" editors gave the Nomad scores of 8.0, 6.5, 7.0, and 7.5. They praised its support for the entire Genesis library, but criticized its hefty battery usage and noted that despite a recent price drop, it was still expensive enough to discourage interested consumers. While they generally complimented the screen display, they remarked that its small size makes it difficult to play certain games. Sushi-X declared the Nomad the best portable gaming system then on the market, while his three co-reviewers had more misgivings, saying it has merits but might not be a worthwhile buy.
Blake Snow of "GamePro" listed the Nomad as fifth on his list of the "10 Worst-Selling Handhelds of All Time", criticizing its poor timing into the market, inadequate advertising, and poor battery life. Scott Alan Marriott of Allgame placed more than simply timing into reasons for the Nomad's lack of sales, stating, "The reason for the Nomad's failure may have very well been a combination of poor timing, company mistrust and the relatively high cost of the machine (without a pack-in). Genesis owners were too skittish to invest in another 16-bit system." Stuart Hunt of "Retro Gamer", however, praised the Nomad, saying in a retrospective that Nomad was "the first true 16-bit handheld" and declared it the best variant of the Genesis. He noted the collectability of the Nomad, due to its low production, and stated, "Had Sega cottoned on to the concept of the Nomad before the Mega Drive 2, and rolled it out as a true successor to the Mega Drive ... then perhaps Sega may have succeeded in its original goal to prolong the life of the Mega Drive in the U.S." In 2017 a mod was developed to allow the Nomad to charge power using USB devices.


Crusader of Centy

Crusader of Centy is an action-adventure game developed by Nextech for the Sega Genesis. The story centers on Corona, a boy who has just turned 14 years of age and must inherit his late father's sword to fight the monsters that threaten the human race's existence. Gameplay uses an overhead perspective and focuses on exploring, battling enemies with a sword, and solving puzzles. As the story progresses, numerous animals join the hero and aid him. They are used in gameplay like weapons or tools, which often grant passage to previously inaccessible areas.
Gameplay.
Early in the game, Corona finds himself losing his ability to speak to fellow humans, and instead gaining the ability to speak to animals. Some of them will join him, lending Corona their abilities while they are "equipped". Each animal has its own special technique. The very first animal the player gets is Corona's pet dog, Mac (US version), or Johnny (UK version). He can hold enemies down for Corona to attack. Later, the player gets a penguin, named Chilly (US version), or Penguy (UK version), which will power up Corona's sword with an ice-attack. Corona can equip two abilities at a time. A total of 16 animals can be obtained.
Plot.
In Soleil Town, a law requires that all 14-year-old boys go to train and prepare for battle. The game's hero, Corona, has just turned fourteen at the beginning of the game. As such, Corona receives the sword and shield of his father, who died in battle and had a great reputation for his bravery in defending the city.
The story is divided into two parts. Corona must first take time to discover his world and unlock the various levels that make it up. He can then access them at his leisure. During this half of the game, Corona will not have the ability to speak to humans, but only to animals and plants. Only after beating Dragon ("Maldra the Dragon" in the US version) will the second half of the game begin: Corona has recovered the ability to talk to humans and he will travel through time to build a better world and understand why the monsters are at war with humanity.
Development and release.
"Crusader of Centy" was developed by Nextech.
Reception.
The four reviewers of "Electronic Gaming Monthly" contended that the game is a worthy "Zelda" clone, with Ed Semrad and Sushi-X going so far as to say it is equally good as the "Zelda" series. They identified the story and Zelda-like play mechanics as the game's strongest points, and gave the game a 7.75 out of 10. Scary Larry of "GamePro" viewed the game as the Genesis's answer to "", and remarked that "While "Zelda" had tons of hidden surprises, weapons, and fearsome bosses (making it one of the best action/RPGs ever), "Crusader of Centy" has a too-familiar story line, minor enemies, and a serious shortage of puzzles." He nonetheless concluded that though "Crusader of Centy" would bore the average RPG gamer, it successfully appeals to its young target audience. "Next Generation" rated it three stars out of five, and stated that ""Centy" is a mirror image of the immensely popular "Zelda", and is a load of fun that Genesis owners have yet to experience." "Jeuxvideo.com" rated the game with a 17 out of 20 score.


Yellowstone (supercomputer)

Yellowstone was the inaugural supercomputer at the NCAR-Wyoming Supercomputing Center (NWSC) in Cheyenne, Wyoming. It was installed, tested, and readied for production in the summer of 2012. The Yellowstone supercomputing cluster was decommissioned on December 31, 2017, being replaced by its successor Cheyenne.
Yellowstone was a highly capable petascale system designed for conducting breakthrough scientific research in the interdisciplinary field of Earth system science. Scientists used the computer and its associated resources to model and analyze complex processes in the atmosphere, oceans, ice caps, and throughout the Earth system, accelerating scientific research in climate change, severe weather, geomagnetic storms, carbon sequestration, aviation safety, wildfires, and many other topics. Funded by the National Science Foundation and the State and University of Wyoming, and operated by the National Center for Atmospheric Research, Yellowstone's purpose was to improve the predictive power of Earth system science simulation to benefit decision-making and planning for society.
System description.
Yellowstone was a 1.5-petaflops IBM iDataPlex cluster computer with 4,536 dual-socket compute nodes that contained 9,072, 2.6-GHz Intel Xeon E5-2670 8-core processors (72,576 cores), and its aggregate memory size was 145 terabytes. The nodes interconnected in a full fat tree network via a Mellanox FDR InfiniBand switching fabric. System software includes the Red Hat Enterprise Linux operating system for Scientific Computing, LSF Batch Subsystem and Resource Manager, and IBM General Parallel File System (GPFS).
Yellowstone was integrated with many other high-performance computing resources in the NWSC. The central feature of this supercomputing architecture was its shared file system that streamlined science workflows by providing computation, analysis, and visualization work spaces common to all resources. This common data storage pool, called the GLobally Accessible Data Environment (GLADE), provides 36.4 petabytes of online disk capacity shared by the supercomputer, two data analysis and visualization (DAV) cluster computers (Geyser and Caldera), data servers for both local and remote users, and a data archive with the capacity to store 320 petabytes of research data. High-speed networks connect this Yellowstone environment to science gateways, data transfer services, remote visualization resources, Extreme Science and Engineering Discovery Environment (XSEDE) sites, and partner sites around the world.
This integration of computing resources, file systems, data storage, and broadband networks allowed scientists to simulate future geophysical scenarios at high resolution, then analyze and visualize them on one computing complex. This improves scientific productivity by avoiding the delays associated with moving large quantities of data between separate systems. Further, this reduces the volume of data that needs to be transferred to researchers at their home institutions. The Yellowstone environment at NWSC makes more than 600 million processor-hours available each year to researchers in the Earth system sciences.


List of PlayStation 4 free-to-play games


VIEWMAX.INI


Kernfs (BSD)

In the Berkeley Software Distribution (BSD) and its descendants, kernfs is a pseudo file system that provides access to information on the currently running kernel. The file system itself and its content are dynamically generated when the operating system is booted, and the kernfs is often mounted at the directory. As a result of its nature, kernfs does not consist of actual files on a storage device, allowing instead processes to retrieve system information by accessing virtual files.
kernfs first appeared in 4.4BSD, and NetBSD 6.0 continues to use kernfs by default while mounting it at the canonical mount point.


IBM Aptiva

The IBM Aptiva personal computer was introduced in September 1994 as the replacement for the IBM PS/1. The first Aptiva models were based on the Intel 80486 CPU with later models using the Pentium and AMD CPUs. All systems were developed in-house except for the later E series which was developed by Acer. The last system was withdrawn in May 2001 without direct replacement when IBM decided to exit the home market. Customers were directed to the IBM NetVista, which was more targeted to business desktops. Most Aptiva models included a modem and a standby/hibernation feature called "Rapid Resume".
Aptiva computers were typically sold as a bundle which included monitor, speakers, keyboard and mouse. First generation models came with IBM PC DOS 6.3 and Windows 3.1. Pentium generation Aptivas came with Windows 95 and OS/2 'select-a-system' (PC DOS 7/Windows 3.1 and OS/2 Warp) on selected models.
Sound and modem functionality was provided on M, A, C and S models by an IBM Mwave adapter. The Mwave adaptor had multiple compatibility and performance issues and was eventually replaced by standard modems and sound cards. IBM settled a lawsuit for Mwave owners by refunding Aptiva Mwave owners a small monetary fee so that those owners could purchase industry standard devices.
Market history.
Among other things, IBM's development and marketing of Lotus SmartSuite and OS/2 placed it in direct competition with Microsoft Office and Microsoft Windows, respectively. As a result, Microsoft "punished the IBM PC Company with higher prices, a late license for Windows 95, and the withholding of technical and marketing support."
IBM was not granted OEM rights for Windows 95 until 15 minutes prior to the release of Windows 95, August 24, 1995. Because of this uncertainty, IBM machines were sold without Windows 95, while Compaq, HP, and other companies sold machines with Windows 95 from day one.
The Aptiva never managed to recapture IBM's early 1980s PC dominance from Compaq, Dell, or HP. IBM's PC Group had higher costs than its competitors which made it impossible to match them on prices. Throughout the 1990s, IBM lost the most market share in PCs during that decade compared to its rivals, and only the ThinkPad laptop remained a stronghold. Most desktop and laptop sales were with longstanding corporate customers that already used IBM mainframe computers. Despite IBM's continued decline in hardware, that was more than offset by the company shifting focus to the more lucrative e-business (integrated e-commerce and Internet technology solutions). By 2005, IBM had sold the Personal Computing Division to Lenovo.
Aptiva models.
To understand which 'series' a Pentium-based Aptiva belongs to look at the first letter of the 3 character model number (so a 2168-M40 is an M Series). The word in quotes relates to the internal development name for the computer.
Aptiva machine types
The first generation of Aptivas used the 2144 desktop and 2168 tower unit form factors.
The 2159 "stealth" series was a unique all black design that had the monitor resting on a metal stand with a 'console' located underneath which contained the floppy and CD drive. The console connected to the main unit via a 6-foot cable. Later in the production life, all Aptivas used tower unit form factors. Originally the 2144 and 2168 machine types referred to the amount of open slots and drive bays. Later machine type numbers did not have the same nomenclature.
User groups.
Various Aptiva user and fan groups emerged. One of the most notable and tenured was run by Don Schneider, "DON5408's Unofficial Aptiva Support Site"., now available on aptivasupport.com. The site had much information on topics such as how to open the computer case, drivers and upgrade tips. The site included a user chat group on Friday nights for users to help each other with PC issues. The site was removed when AOL discontinued its web hosting services, but some pages still remain on ptd.net. The site ran from 4/4/1997 to 10/31/2008, bringing in just under a million views on the home page.


AMD Turbo Core

AMD Turbo Core a.k.a. AMD Core Performance Boost (CPB) is a technology implemented by AMD that allows the processor to dynamically adjust and control the processor operating frequency in certain versions of its processors which allows for increased performance when needed while maintaining lower power and thermal parameters during normal operation. AMD Turbo Core technology has been implemented beginning with the Phenom II X6 microprocessors based on the AMD K10 microarchitecture. AMD Turbo Core is available with some AMD A-Series accelerated processing units.
AMD Turbo Core is similar to Intel Turbo Boost, which is another dynamic processor frequency adjustment technology used to increase performance, as well as AMD PowerNow!, which is used to dynamically adjust laptop processor's operating frequencies in order to decrease power consumption (saving battery life), reduce heat, and lower noise. AMD PowerNow! is used to "decrease" processor frequency, whereas AMD Turbo Core is used to "increase" processor frequency.
Background.
To decide a processor's clock speed, the processor is stress tested to determine the maximum speed that the processor can run at before the maximum amount of power allowed is reached, which is called thermal design power or TDP. It has been reported that customers would complain that the processors rarely consumed the rated TDP, which meant that most consumers do not come close to the power consumed during maximum stress testing. A parameter called average CPU power (ACP) is used to address this issue. ACP defines the average power expected to be consumed with regular use, whereas TDP gives the maximum power consumed. Power consumed is an important factor when considering thermal limits and determining CPU power dissipation.
AMD Turbo Core and similar dynamic processor frequency adjustment technologies take advantage of average power consumed being less than the maximum design limits, allowing frequency (and the accompanying power and heat) to be increased for short periods of time without exceeding design limits.
Features.
Advantages of AMD Turbo Core include:
With the Ryzen processors, AMD has introduced extra auto-overclocking features:


Sony Toshiba IBM Center of Competence for the Cell Processor

The Sony Toshiba IBM Center of Competence for the Cell Processor is the first Center of Competence dedicated to the promotion and development of Sony Toshiba IBM's Cell microprocessor, an eight-core multiprocessor designed using principles of parallelism and memory latency. The center is part of the Georgia Institute of Technology's College of Computing and is headed by David A. Bader.
According to IBM, the center is intended "to build a community of
programmers and broaden industry support for the Cell BE processor." So far, the program has resulted in two workshops that involved detailed lectures on and training with various basic cell programming concepts, and has deployed a cluster of 28 IBM BladeCenter QS20 Servers (14 blades) for student and faculty use.


EA DATA. SF


List of mobile phones with WVGA display

Mobile phones with WVGA native display resolution have become common. This is a list of phones that have such displays.
Wide VGA or WVGA an abbreviation for Wide Video Graphics Array is any display resolution with the same 480 pixel height as VGA but wider than 640 pixels, such as 800x480, 848x480, or 854x480.
The following mobile phones have WVGA displays:


Univel

Univel, Inc. was a joint venture of Novell and AT&T's Unix System Laboratories (USL) that was formed in October 1991 to develop and market the "Destiny" desktop Unix operating system, which was released in 1992 as UnixWare 1.0. Univel existed only briefly in the period between AT&T initially divesting parts of USL in 1991, and its eventual outright purchase by Novell, which completed in 1993, thereby acquiring rights to the Unix operating system. Novell merged USL and Univel into their new Unix Systems Group (USG).


Serial port

In computing, a serial port is a serial communication interface through which information transfers in or out sequentially one bit at a time. This is in contrast to a parallel port, which communicates multiple bits simultaneously in parallel. Throughout most of the history of personal computers, data has been transferred through serial ports to devices such as modems, terminals, various peripherals, and directly between computers.
While interfaces such as Ethernet, FireWire, and USB also send data as a serial stream, the term "serial port" usually denotes hardware compliant with RS-232 or a related standard, such as RS-485 or RS-422.
Modern consumer PCs have largely replaced serial ports with higher-speed standards, primarily USB. However, serial ports are still frequently used in applications demanding simple, low-speed interfaces, such as industrial automation systems, scientific instruments, point of sale systems and some industrial and consumer products.
Server computers may use a serial port as a control console for diagnostics, while networking hardware (such as routers and switches) commonly use serial console ports for configuration, diagnostics, and emergency maintenance access. To interface with these and other devices, USB-to-serial converters can quickly and easily add a serial port to a modern PC.
Hardware.
In the present day, many devices use an integrated circuit called a UART to implement a serial port. This IC converts characters to and from asynchronous serial form, implementing the timing and framing of data specified by the serial protocol in hardware. The IBM PC implements its serial ports, when present, with one or more UARTs.
Very low-cost systems, such as some early home computers, would instead use the CPU to send the data through an output pin, using the bit banging technique. These early home computers often had proprietary serial ports with pinouts and voltage levels incompatible with RS-232.
Before large-scale integration (LSI) made UARTs common, serial ports were commonly used in mainframes and minicomputers, which would have multiple small-scale integrated circuits to implement shift registers, logic gates, counters, and all the other logic needed. As PCs evolved serial ports were included in the Super I/O chip and then in the chipset.
DTE and DCE.
The individual signals on a serial port are unidirectional and when connecting two devices, the outputs of one device must be connected to the inputs of the other. Devices are divided into two categories: "data terminal equipment" (DTE) and "data circuit-terminating equipment" (DCE). A line that is an output on a DTE device is an input on a DCE device and vice versa, so a DCE device can be connected to a DTE device with a straight wired cable, in which each pin on one end goes to the same numbered pin on the far end.
Conventionally, computers and terminals are DTE, while peripherals such as modems are DCE. If it is necessary to connect two DTE (or DCE) devices together, a cable with reversed TX and RX lines, known as a cross-over, roll-over or null modem cable must be used.
Gender.
Generally, serial port connectors are gendered, only allowing connectors to mate with a connector of the opposite gender. With D-subminiature connectors, the male connectors have protruding pins, and female connectors have corresponding round sockets. Either type of connector can be mounted on equipment or a panel; or terminate a cable.
Connectors mounted on DTE are likely to be male, and those mounted on DCE are likely to be female (with the cable connectors being the opposite). However, this is far from universal; for instance, most serial printers have a female DB25 connector, but they are DTEs. In this circumstance, the appropriately gendered connectors on the cable or a gender changer can be used to correct the mismatch.
Connectors.
The only connector specified in the original RS-232 standard was the 25-pin D-subminiature, however, many other connectors have been used to save money or save on physical space, among other reasons. In particular, since many devices do not use all of the 20 signals that are defined by the standard, connectors with fewer pins are often used. While specific examples follow, countless other connectors have been used for RS-232 connections.
The 9-pin DE-9 connector has been used by most IBM-compatible PCs since the Serial/Parallel Adapter option for the PC-AT, where the 9-pin connector allowed a serial and parallel port to fit on the same card. This connector has been standardized for RS-232 as TIA-574.
Some miniaturized electronics, particularly graphing calculators and hand-held amateur and two-way radio equipment, have serial ports using a phone connector, usually the smaller 2.5 or 3.5 mm connectors and the most basic 3-wire interface—transmit, receive and ground.
8P8C connectors are also used in many devices. The EIA/TIA-561 standard defines a pinout using this connector, while the rollover cable (or Yost standard) is commonly used on Unix computers and network devices, such as equipment from Cisco Systems.
Many models of Macintosh favor the related RS-422 standard, mostly using circular mini-DIN connectors. The Macintosh included a standard set of two ports for connection to a printer and a modem, but some PowerBook laptops had only one combined port to save space.
10P10C connectors can be found on some devices. Digital Equipment Corporation defined their own DECconnect connection system which is based on the Modified Modular Jack (MMJ) connector. This is a 6-pin modular jack where the key is offset from the center position. As with the Yost standard, DECconnect uses a symmetrical pin layout which enables the direct connection between two DTEs.
Another common connector is the DH10 header connector common on motherboards and add-in cards which is usually converted via a cable to the more standard 9-pin DE-9 connector (and frequently mounted on a free slot plate or other part of the housing).
Pinouts.
The following table lists commonly used RS-232 signals and pin assignments.
The signal ground is a common return for the other connections; it appears on two pins in the Yost standard but is the same signal. The DB-25 connector includes a second "protective ground" on pin 1, which is intended to be connected by each device to its own frame ground or similar. Connecting this to pin 7 (signal reference ground) is a common practice but not recommended.
Note that EIA/TIA 561 combines DSR and RI, and the Yost standard combines DSR and DCD.
Powered ports.
Some serial ports on motherboards or add-in cards provided jumpers that select whether pin 1 of the DE-9 connector connects to DCD or a power-supply voltage, and whether pin 9 of the DE-9 connector connects to RI or a power-supply voltage. Supply voltage could be set to +5 V, +9 V, +12 V, or ground depending on the manufacturer. The power was required for some mice and point-of-sale equipment.
Hardware abstraction.
Operating systems usually create symbolic names for the serial ports of a computer, rather than requiring programs to refer to them by hardware address.
Unix-like operating systems usually label the serial port devices /dev/tty*. "TTY" is a common trademark-free abbreviation for "teletype", a device commonly attached to early computers' serial ports, and * represents a string identifying the specific port; the syntax of that string depends on the operating system and the device. On Linux, 8250/16550 UART hardware serial ports are named /dev/ttyS*, USB adapters appear as /dev/ttyUSB* and various types of virtual serial ports do not necessarily have names starting with tty.
The DOS and Windows environments refer to serial ports as COM ports: COM1, COM2..etc.
Common applications for serial ports.
The RS-232 standard is used by many specialized and custom-built devices. This list includes some of the more common devices that are connected to the serial port on a PC. Some of these such as modems and serial mice are falling into disuse while others are readily available.
Serial ports are very common on most types of microcontroller, where they can be used to communicate with a PC or other serial devices.
Since the control signals for a serial port can be easily turned on and off by a switch, some applications used the control lines of a serial port to monitor external devices, without exchanging serial data. A common commercial application of this principle was for some models of uninterruptible power supply which used the control lines to signal loss of power, low battery, and other status information. At least some Morse code training software used a code key connected to the serial port, to simulate actual code use. The status bits of the serial port could be sampled very rapidly and at predictable times, making it possible for the software to decipher Morse code.
Settings.
Serial standards provide for many different operating speeds as well as adjustments to the protocol to account for different operating conditions. The most well known options are speed, number of data bits per character, parity, and number of stop bits per character.
In modern serial ports using a UART integrated circuit, all these settings can be software-controlled. Hardware from the 1980s and earlier may require setting switches or jumpers on a circuit board.
The configuration for serial ports designed to be connected to a PC has become a de facto standard, usually stated as 9600/8-N-1.
Speed.
Serial ports use two-level (binary) signaling, so the data rate in bits per second is equal to the symbol rate in baud. A standard series of rates is based on multiples of the rates for electromechanical teleprinters; some serial ports allow many arbitrary rates to be selected, but the speeds on both sides of the connection must match, or data will be received as gibberish.
The capability to set a bit rate does not imply that a working connection will result. Not all bit rates are possible with all serial ports. Some special-purpose protocols such as MIDI for musical instrument control, use serial data rates other than the teleprinter standards. Some serial port implementations can automatically choose a bit rate by observing what a connected device is sending and synchronizing to it.
The total speed includes bits for framing (stop bits, parity, etc.) and so the effective data rate is lower than the bit transmission rate. For example, with 8-N-1 character framing, only 80% of the bits are available for data; for every eight bits of data, two more framing bits are sent.
Bit rates commonly supported include 75, 110, 300, 1200, 2400, 4800, 9600, 19200, 38400, 57600 and 115200 bit/s.
Crystal oscillators with a frequency of 1.843200 MHz are sold specifically for this purpose. This is 16 times the fastest bit rate, and the serial port circuit can easily divide this down to lower frequencies as required.
Data bits.
The number of data bits in each character can be 5 (for Baudot code), 6 (rarely used), 7 (for true ASCII), 8 (for most kinds of data, as this size matches the size of a byte), or 9 (rarely used). 8 data bits are almost universally used in newer applications. 5 or 7 bits generally only make sense with older equipment such as teleprinters.
Most serial communications designs send the data bits within each byte LSB (least significant bit) first. This standard is also referred to as "little endian."
Also possible, but rarely used, is "big endian" or MSB (most significant bit) first; this was used, for example, by the IBM 2741 printing terminal.
The order of bits is not usually configurable within the serial port interface, but is defined by the host system. To communicate with systems that require a different bit ordering than the local default, local software can re-order the bits within each byte just before sending and just after receiving.
Parity.
Parity is a method of detecting errors in transmission. When parity is used with a serial port, an extra data bit is sent with each data character, arranged so that the number of 1 bits in each character, including the parity bit, is always odd or always even. If a byte is received with the wrong number of 1s, then it must have been corrupted. However, an even number of errors can pass the parity check.
Electromechanical teleprinters were arranged to print a special character when received data contained a parity error, to allow detection of messages damaged by line noise. A single parity bit does not allow implementation of error correction on each character, and communication protocols working over serial data links will have higher-level mechanisms to ensure data validity and request retransmission of data that has been incorrectly received.
The parity bit in each character can be set to one of the following:
Aside from uncommon applications that use the last bit (usually the 9th) for some form of addressing or special signaling, mark or space parity is uncommon, as it adds no error detection information.
Odd parity is more useful than even parity since it ensures that at least one state transition occurs in each character, which makes it more reliable at detecting errors like those that could be caused by serial port speed mismatches. The most common parity setting, however, is "none", with error detection handled by a communication protocol.
Stop bits.
Stop bits sent at the end of every character allow the receiving signal hardware to detect the end of a character and to resynchronise with the character stream. Electronic devices usually use one stop bit. If slow electromechanical teleprinters are used, one-and-one half or two stop bits are required.
Conventional notation.
The data/parity/stop (D/P/S) conventional notation specifies the framing of a serial connection. The most common usage on microcomputers is 8/N/1 (8N1). This specifies 8 data bits, no parity, 1 stop bit. In this notation, the parity bit is not included in the data bits. 7/E/1 (7E1) means that an even parity bit is added to the 7 data bits for a total of 8 bits between the start and stop bits. If a receiver of a 7/E/1 stream is expecting an 8/N/1 stream, half the possible bytes will be interpreted as having the high bit set.
Flow control.
Flow control is used in circumstances where a transmitter might be able to send data faster than the receiver is able to process it. To cope with this, serial lines often incorporate a handshaking method, usually distinguished between "hardware" and "software" handshaking.
Hardware handshaking is done with extra signals, often the RS-232 RTS/CTS or DTR/DSR signal circuits. Generally, the RTS and CTS are turned off and on from alternate ends to control data flow, for instance when a buffer is almost full. DTR and DSR are usually on all the time and, per the RS-232 standard and its successors, are used to signal from each end that the other equipment is actually present and powered-up. However, manufacturers have over the years built many devices that implemented non-standard variations on the standard, for example, printers that use DTR as flow control.
Software handshaking is done for example with ASCII control characters XON/XOFF to control the flow of data. The XON and XOFF characters are sent by the receiver to the sender to control when the sender will send data, that is, these characters go in the opposite direction to the data being sent. The circuit starts in the "sending allowed" state. When the receiver's buffers approach capacity, the receiver sends the XOFF character to tell the sender to stop sending data. Later, after the receiver has emptied its buffers, it sends an XON character to tell the sender to resume transmission. It is an example of in-band signaling, where control information is sent over the same channel as its data.
The advantage of hardware handshaking is that it can be extremely fast; it doesn't impose any particular meaning such as ASCII on the transferred data; and it is stateless. Its disadvantage is that it requires more hardware and cabling, and these must be compatible at both ends.
The advantage of software handshaking is that it can be done with absent or incompatible hardware handshaking circuits and cabling. The disadvantage, common to all in-band control signaling, is that it introduces complexities in ensuring that a) control messages get through even when data messages are blocked, and b) data can never be mistaken for control signals. The former is normally dealt with by the operating system or device driver; the latter normally by ensuring that control codes are "escaped" (such as in the Kermit protocol) or omitted by design (such as in ANSI terminal control).
If no handshaking is employed, an overrun receiver might simply fail to receive data from the transmitter. Approaches for preventing this include reducing the speed of the connection so that the receiver can always keep up; increasing the size of buffers so it can keep up averaged over a longer time; using delays after time-consuming operations (e.g. in termcap) or employing a mechanism to resend data which has been corrupted (e.g. TCP).
Virtual serial port.
A virtual serial port is an emulation of physical serial port. There are several use cases.
Serial port redirection.
Serial port redirection software creates extra virtual serial ports in an operating system without additional hardware installation (such as expansion cards, etc.) in order to split or redirect the data to and from a serial port for a variety of applications.
One option is to share data between several applications. A serial port typically can only be monitored by one device at a time under the constraints of most operating systems, but a serial port redirector can create two virtual ports, for two separate applications to monitor the same data, for instance, a GPS device outputting location data.
Another option is to communicate with another serial device via internet or LAN as if they were locally connected, using serial over LAN.
Virtual serial ports ideally emulate all hardware serial port functionality, including baud rate, data bits, parity bits, stop bits, etc. Additionally, they allow controlling the data flow, emulating all signal lines (DTR, DSR, CTS, RTS, DCD, and RI) and customizing pinout.
It is possible to create a large number of virtual serial ports in a PC. The only limitation is the resources, such as RAM and CPU time. Serial port emulators are available for many operating systems including MacOS, Linux, NetBSD and other Unix-like operating systems, and various mobile and desktop versions of Microsoft Windows.
Bluetooth.
Bluetooth implements virtual serial ports over the Serial Port Profile. This is the standard way of receiving data from Bluetooth-equipped GPS modules, for instance.
Softmodems.
The drivers for a software-implemented modem create a virtual serial port for communication with the host operating system, since the modem is implemented entirely in the device driver and therefore there is no point where the serial data would be sent to the physical card.


DOSSHELL.COM


List of AMD K5 microprocessors

The AMD K5 microprocessor is a Pentium-class 32-bit CPU manufactured by American company Advanced Micro Devices (AMD), and targeted at the consumer market. It was the first x86 processor designed by AMD from the ground up, and not licensed or reverse-engineered as previous generations of x86 processors produced by AMD.


Motorola 68008

The Motorola 68008 is an 8/16/32-bit microprocessor made by Motorola. It is a version of the Motorola 68000 with an 8-bit external data bus, as well as a smaller address bus.
The original 68000 (introduced in 1979) has a 24-bit address bus and a 16-bit data bus. These relatively large buses made it hard to design a low-cost system based on the 68000; they were difficult to lay out on a circuit board and needed a lot of supporting circuitry. A 16-bit data bus also required twice as many memory chips as an 8-bit one.
The 68008, introduced in 1982, was designed to work with low-cost 8-bit memory systems. Because of its smaller data bus, it was only about half as fast as a 68000 of the same clock speed. However, it was still faster than competing 8-bit microprocessors, because the 68008 internally was based on 32-bit data registers and a 16-bit data bus.
Except for its smaller data and address buses, the 68008 behaved identically to the 68000 and had the same internal organization and microarchitecture.
The 68008 was an HMOS chip with about it came with a speed grade of . There were two distinct versions of the chip. The original version came in a 48-pin dual in-line package and had a 20-bit address bus, allowing it to use up to 1 megabyte of memory. A later version came in a 52-pin plastic leaded chip carrier; this version provided a 22-bit address bus and could support of RAM.
Very few computer systems used the 68008 as the main processor; the Sinclair QL microcomputer is the best known of these. However, the 68008 was popular in embedded systems.
Motorola ended production of the 68008 in 1996.


Aaron R. Reynolds


Henry Poole (technologist)

Henry Poole is a technologist and social entrepreneur, CEO of CivicActions and Board Member of the Free Software Foundation.
He co-founded one of the first digital agencies, Vivid Studios, in 1993. That year, he served as technical editor for the book, "Demystifying Multimedia". In 1994, he led a project to study the social interactions and use of technology for the WELL community. In 1995, his firm managed the online launch of Microsoft Windows 95 (the largest online technology product introduction of this time).
In 2000, Poole joined as CEO of French Linux publisher MandrakeSoft. In 2001, Poole founded the first openSAAS enterprise, Affero, Inc. and in 2002, published the Affero General Public License, version 1. Poole joined the board of the Free Software Foundation in December 2002. In 2003, Poole managed the digital team for Kucinich for US President and in 2004, founded government digital services firm CivicActions. In May 2006, Poole and the Free Software Foundation launched the anti-DRM campaign, Defective by Design.
A software freedom activist, Poole has organized fundraisers for Dmitry Sklyarov and the Free Software Foundation.
He is a signatory to the 9/11 Truth Statement.


CVF (Microsoft)


VIA Nano

The VIA Nano (formerly code-named VIA Isaiah) is a 64-bit CPU for personal computers. The VIA Nano was released by VIA Technologies in 2008 after five years of development by its CPU division, Centaur Technology. This new Isaiah 64-bit architecture was designed from scratch, unveiled on 24 January 2008, and launched on May 29, including low-voltage variants and the Nano brand name. The processor supports a number of VIA-specific x86 extensions designed to boost efficiency in low-power appliances.
History.
Unlike Intel and AMD, VIA uses two distinct development code names for each of its CPU cores. In this case, the codename 'CN' was used in the United States by Centaur Technology. Biblical names are used as codes by VIA in Taiwan, and Isaiah was the choice for this particular processor and architecture. It is expected that the VIA Isaiah will be twice as fast in integer performance and four times as fast in floating-point performance as the previous-generation VIA Esther at an equivalent clock speed. Power consumption is also expected to be on par with the previous-generation VIA CPUs, with thermal design power ranging from 5 W to 25 W. Being a completely new design, the Isaiah architecture was built with support for features like the x86-64 instruction set and x86 virtualization which were unavailable on its predecessors, the VIA C7 line, while retaining their encryption extensions. Several independent tests showed that the VIA Nano performs better than the single-core Intel Atom across a variety of workloads. In a 2008 Ars Technica test, a VIA Nano gained significant performance in memory subsystem after its CPUID changed to Intel, hinting at the possibility that the benchmark software only checks the CPUID instead of the actual features supported by the CPU to choose a code path. The benchmark software used had been released before the release of VIA Nano.
On November 3, 2009, VIA launched the Nano 3000 series. VIA claims that these models can offer a 20% performance boost and 20% more energy efficiency than the Nano 1000 and 2000 series. Benchmarks run by VIA claim that a 1.6 GHz 3000-series Nano can outperform the ageing Intel Atom N270 by about 40–54%. The 3000 series adds the SSE4 SIMD instruction set extensions, which were first introduced with 45 nm revisions of the Intel Core 2 architecture.
On November 11, 2011, VIA released the VIA Nano X2 Dual-Core Processor with their first ever dual core pico-itx mainboard. The VIA Nano X2 is built on a 40 nm process and supports the SSE4 SIMD instruction set extensions, critical to modern floating point dependent applications. Via claims 30% higher performance in comparison to Intel's Atom with a 50% higher clock.
The Zhaoxin joint venture processors, released from 2014, are based on the VIA Nano series.
Architecture overview.
Around 2014/8/31 rumors appeared about a potential Isaiah II refresh.


Craig McClanahan

Craig R. McClanahan is a programmer and original author of the Apache Struts framework for building web applications. He was part of the expert group that defined the servlet 2.2, 2.3 and JSP 1.1, 1.2 specifications. He is also the architect of Tomcat's servlet container Catalina.


Capcom Classics Collection

 is a compilation of arcade games released by Capcom for the PlayStation 2 and Xbox on September 27, 2005 in North America and in 2006 in Japan. It was developed by Digital Eclipse Software (then Backbone Entertainment), Sensory Sweep, and its Japanese developer Klein Computer Entertainment. A second volume, "Capcom Classics Collection Vol. 2", was released on November 14, 2006 in North America, for PlayStation 2 and Xbox. The second volume as well as the Xbox version of the first volume were not released in Japan.
Two handheld compilations, "Capcom Classics Collection Remixed" (not released in Japan) and "Capcom Classics Collection Reloaded" ("Capcom Classics Collection" in Japan) were released on March 22 and October 24, 2006 respectively on the PlayStation Portable. Reloaded can also be played on the PlayStation Vita by downloading it on a PS3 and copying it via the USB transfer function to the Vita. A Game Boy Advance compilation, "Capcom Classics Mini-Mix" (North America only), was released on September 19, 2006. "Reloaded" and "Mini-Mix" were not developed by Digital Eclipse, but rather by Klein Computer Entertainment and Sensory Sweep, respectively.
Many of the games included in this compilation were re-released as part of "Capcom Arcade Cabinet" for PlayStation 3 and Xbox 360 from February 19, 2013 to April 17, 2013.
Overview.
In 1998, Capcom produced a series of five video game compilations titled "Capcom Generations" for the PlayStation and Sega Saturn, released in Japan and the PAL region. The series as a whole compiled over 15 arcade games and the Super NES game "Super Ghouls'n Ghosts". Each volume was accompanied by extra features such as a historical overview of each title, artwork gallery, hints and even cast profiles. All games in these compilations also contained enhanced gameplay options such as rapid fire, a bigger screen, and remixed soundtrack.
"Volume 1" of "Capcom Classics Collection" contains all sixteen games from "Capcom Generations" and "Street Fighter Collection 2" respectively (converted from these ports rather than the arcade originals) and six added emulated titles, while "Volume 2" features only titles not included in the "Capcom Generations" series. As with the "Capcom Generations" titles, all games contain extra features, which consist of gameplay tips, artwork, listenable music and cast profiles, although the contents are not identical. All the extra features are typically unlocked by getting high scores or achieving unusual gameplay objectives, such as collecting the Yashichi item in several games or picking up Edi. E's gum in "Final Fight". High scores can be saved for all the games for three different difficulty settings: Normal, Hardcore (in which only the minimum number of lives and continues are available and the AI is at its best), or Custom (if the player changes the options from the Normal or Hardcore settings).
The home console volumes feature one bonus game each. The first volume features a "Deluxe Versus Mode" for the "Street Fighter II" games which allows two players to compete against each other by offering the players a selection of characters from all three installments of the "Street Fighter II" series included in the compilation. This game mode was originally from the "Street Fighter Collection 2" compilation for the PlayStation and Saturn, which are the versions emulated in "Capcom Classics Collection" and "Reloaded". "Remixed" and "Volume 2" contain a version of "Quiz and Dragons" that is exclusively composed of Capcom-related questions.
Portable versions.
"Remixed" and "Reloaded", both for the PSP contain mostly the same lineup of games from the two home console volumes. "Reloaded" contains the 16 games respectively from the "Capcom Generations" and "Street Fighter Collection 2" lineup plus "Knights of the Round", "Eco Fighters" and "The King of Dragons" while "Remixed", which came out before "Reloaded", contains the majority of remaining games from the home console versions of "Vol. 1" and "2". "Super Street Fighter II Turbo", "Tiger Road", and "Trojan" do not appear in the portable versions.
"Capcom Classics Mini-Mix".
"Capcom Classics Mini-Mix" is a compilation for the Game Boy Advance that was developed by "Sensory Sweep" and released around the same time as the home console and PSP versions.
This GBA compilation includes three games originally released for the Nintendo Entertainment System:


Relative identifier

In the context of the Microsoft Windows NT line of computer operating systems, the relative identifier (RID) is a variable length number that is assigned to objects at creation and becomes part of the object's Security Identifier (SID) that uniquely identifies an account or group within a domain. The Relative ID Master allocates security RIDs to Domain Controllers to assign to new Active Directory security principals (users, groups or computer objects). It also manages objects moving between domains.
The "Relative ID Master" is one role of the Flexible single master operation for assigning RID.


Procfs

The proc filesystem (procfs) is a special filesystem in Unix-like operating systems that presents information about processes and other system information in a hierarchical file-like structure, providing a more convenient and standardized method for dynamically accessing process data held in the kernel than traditional tracing methods or direct access to kernel memory. Typically, it is mapped to a mount point named "/proc" at boot time. The proc file system acts as an interface to internal data structures in the
kernel. It can be used to obtain information about the system and to change
certain kernel parameters at runtime (sysctl).
Many Unix-like operating systems support the proc filesystem, including Solaris, IRIX, Tru64 UNIX, BSD, Linux, IBM AIX, QNX, and Plan 9 from Bell Labs. OpenBSD dropped support in version 5.7, released in May 2015.
The Linux kernel extends it to non–process-related data.
The proc filesystem provides a method of communication between kernel space and user space. For example, the GNU version of the process reporting utility ps uses the proc file system to obtain its data, without using any specialized system calls.
History.
UNIX 8th Edition.
Tom J. Killian implemented the UNIX 8th Edition (V8) version of "/proc": he presented a paper titled "Processes as Files" at USENIX in June 1984. The design of procfs aimed to replace the "ptrace" system call used for process tracing. Detailed documentation can be found in the proc(4) manual page.
SVR4.
Roger Faulkner and Ron Gomes ported V8 "/proc" to SVR4, and published a paper called "The Process File System and Process Model in UNIX System V" at USENIX in January 1991. This kind of procfs supported the creation of "ps", but the files could only be accessed with functions "read()", "write()", and "ioctl()". Between 1995 and 1996, Roger Faulkner created the procfs-2 interface for Solaris-2.6 that offers a structured /proc filesystem with sub-directories.
Plan 9.
Plan 9 implemented a process file system, but went further than V8. V8's process file system implemented a single file per process. Plan 9 created a hierarchy of separate files to provide those functions, and made /proc a real part of the file system.
4.4BSD.
4.4BSD cloned its implementation of from Plan 9. , procfs is gradually becoming phased out in FreeBSD. It was removed from OpenBSD in version 5.7, which was released in May 2015, because it "always suffered from race conditions and is now unused".
Solaris.
/proc in Solaris was available from the beginning. Solaris 2.6 in 1996 introduced procfs2 from Roger Faulkner.
Linux.
Linux first added a /proc filesystem in v0.97.3, September 1992, and first began expanding it to non-process related data in v0.98.6, December 1992.
As of 2020, the Linux implementation includes a directory for each running process, including kernel processes, in directories named , where is the process number. Each directory contains information about one process, including:
(Users may obtain the PID with a utility such as pgrep, pidof or ps:
$ ls -l /proc/$(pgrep -n python3)/fd # List all file descriptors of the most recently started `python3' process
total 0
lrwx------ 1 baldur baldur 64 2020-03-18 12:31 0 -> /dev/pts/3
lrwx------ 1 baldur baldur 64 2020-03-18 12:31 1 -> /dev/pts/3
lrwx------ 1 baldur baldur 64 2020-03-18 12:31 2 -> /dev/pts/3
$ readlink /proc/$(pgrep -n python3)/exe # List executable used to launch the most recently started `python3' process
/usr/bin/python3.8
 also includes non-process-related system information, although in the 2.6 kernel much of that information moved to a separate pseudo-file system, sysfs, mounted under :
On multi-core CPUs, /proc/cpuinfo contains the fields for "siblings" and "cpu cores" which represent the following calculation is applied:
A CPU package means physical CPU which can have multiple cores ("single core" for one, "dual core" for two, "quad core" for four).
This allows a distinction between hyper-threading and dual-core, i.e. the number of hyper-threads per CPU package can be calculated by "siblings / CPU cores". If both values for a CPU package are the same, then hyper-threading is not supported. For instance, a CPU package with siblings=2 and "cpu cores"=2 is a dual-core CPU but does not support hyper-threading.
The basic utilities that use /proc under Linux come in the procps ( processes) package, and only function in conjunction with a mounted .
Proprietary Expansions.
Several companies and projects added additional functions to "/proc" for their systems, e.g. "/proc/lcd", might be a file containing the contents of the front-panel LCD screen. Text written to this file would be displayed on the screen.


DISKCOPY


VER (command)


Helix HeadRoom

HeadRoom is a DOS context switching and multitasking memory manager produced by Helix Software Company in the late 1980s and early 1990s. HeadRoom managed multiple Terminate and Stay Resident programs and was the first TSR manager to allow sharing of address space and interrupts among TSRs in DOS. HeadRoom v1.0 was released in September 1988.
In April 1989, Helix Software released HeadRoom v1.1 together with the "HeadRoom Network Extensions." This version added support for network communications processes. The HeadRoom Network Extensions intercepted and buffered NETBIOS and TCP/IP communications requests, allowing HeadRoom to manage network communications software such as mainframe Terminal Emulators and e-mail programs. The background communications of these programs would continue while the programs were swapped out. HeadRoom would reactivate the swapped-out programs when activity occurred on the NETBIOS or TCP/IP sockets.
In October 1989, Helix Software released HeadRoom v2.0 which included support for Microsoft Windows and LIM EMS v4.0. Starting in March 1990, this version of HeadRoom was bundled with AST Research RAMpage, RAMpage Plus and SixPack memory expansion boards.
In June 1990, Helix Software licensed technology from Headroom to Digital Communications Associates for use with their IRMA boards and IRMALan software.
In January 1991, Helix released the final version of Headroom, v2.03 and thereafter incorporated HeadRoom's features into its Netroom LAN memory manager, a decision which caused market confusion.