TI-DNOS

Distributed Network Operating System (DNOS).
The Distributed Network Operating System (DNOS) is a general purpose,
multitasking operating system designed to operate with the Texas Instruments
990/10, 990/10A and 990/12 minicomputers.
DNOS includes a sophisticated file management package which provides support
for key indexed files, sequential files, and relative record files.
DNOS is a multiterminal system that is capable of making each of several users
appear to have exclusive control of the system.
DNOS supports output spooling and program accessible accounting data.
Job level and task level operations enable more efficient use of system
resources.
In addition to multiterminal applications, DNOS provides support for advanced
program development.
Users communicate with DNOS by entering commands at a terminal or by providing
a file of commands.
The System Command Interpreter (SCI) processes those commands and directs the
operating system to initiate the action specified by a command.
A text editor allows the user to enter source programs or data into the system.
A Macro Assembler is provided for assembly language programs.
Several high level languages, including Fortran, COBOL, BASIC, RPG II, and
Pascal, are supported.
A link editor and extended debugging facilities are also provided.
A variety of utility programs and productivity tools support access to and
management of information contained in a data base, design of specific forms
on the screen of a video display terminal (VDT), and word processing.
The system supports a wide range of user environments.
DNOS can support as few as one or two terminals, thus allowing the user of a
smaller System to perform tasks efficiently and yet inexpensively.
Larger configurations with a wide variety of peripherals are also supported.
The maximum configuration size varies with the user's environment.
Almost every minicomputer system requirement or application need can be met
with DNOS.
DNOS provides the base for a variety of communications products.
Standard protocols for IBM 2780/3780 and for IBM 3270 communications are supported.
Local area network software is supported for network input/output (I/O) and
logon.
In addition, sophisticated networking software is available with the
Distributed Network Communications System (DNCS) and Distributed Network I/O
(DNIO) packages.
DNCS includes networking capabilities for X.25 and IBM's Systems Network Architecture
(SNA) protocols.
DNIO provides users transparent access to other TI 990s running DNOS and can
be used to connect to local or wide-area networks.
DNOS is an international operating system designed to meet the commercial
requirements of the United States, most European countries, and Japan.
DNOS supports a complete range of international data terminals that permit
users to enter, view, and process data in their own languages.
The system includes error text files that can be edited so that error messages
can be easily translated into languages other than English.
DNOS Features.
DNOS supports features that incorporate the computing power of the larger
computers, and it is upwardly compatible with other Texas Instruments operating
systems.
DNOS features include:


Asus ZenUI

ASUS ZenUI is a front-end touch interface developed by ASUS with partners, featuring a full touch user interface.
Current version is ZenUI 7
ZenUI is used by Asus for Android phones and tablet computers, and is not available for licensing by external parties. ZenUI also comes with Asus-made apps preloaded like ZenLink (PC Link, Share Link, Party Link & Remote Link)
The ZenUI made its debut in Asus Zenfone Series, Asus MemoPad 7 (ME176C) and Asus Padfone Mini (2014).
History.
Before ZenUI, Asus made a front-end interface for Android phones and tablets called ASUS WaveShare UI.
WaveShare UI.
ASUS WaveShare UI was a front-end touch interface developed by ASUS & partners. WaveShare UI was used by Asus for android phones and tablet computers, and was not available for licensing by external parties. WaveShare UI was originally released on the Asus PadFone hybrid smartphone/tablet, and was later used on other Asus products. The last gadget to use the WaveShare UI was the ASUS MeMO Pad HD 7.
Versions.
Asus ZenUI can be updated in the Google Play Store
First Release: 1.2.0.140918.
Preloaded Apps:
Recent Release : 2.2.0.14_160307.
Preloaded Apps:


Darius II (video game)

 is a 1989 arcade video game developed by Taito. It is the direct sequel to the 1987 "Darius". It was later released as in Japan in 1991 for the Game Boy as well as non-Japanese ports. A remake was released for the PC Engine Super CD-ROM² as in 1993.
Gameplay.
The game is set in the inner half of the solar system, and has the same branching level structure as "Darius". Similar to the first "Darius" game, "Darius II" was programmed for multiple screens; while a three-screen version like the original exists, "Darius II" is more commonly and generally represented as a two-screen game.
The red/green/blue powerups from the first game return, and have the same function: respectively, upgrades to the "missile" main weapon and "bomb" subweapon, and a shield to absorb some damage. Two new power-ups were added: a yellow powerup that adds a new "laser" main weapon that functions somewhat similarly to the bombs, and a rainbow powerup that grants one upgrade to "all" the players weapons. Acquiring these power-ups and the upgrade path is completely different from "Darius": a formation of a specific enemy must be completely destroyed (and a given formation may not have a powerup), and every single powerup now grants some kind of upgrade. Further, the various weapons upgrade differently, though the shield upgrade the same as before.
Another new feature in "Darius II" is the appearance of minibosses known as "captains"; large enemies that appear somewhere in the level before the main boss. In "Darius II", these are all smaller versions of bosses from the first game, with similar abilities.
Plot.
"Darius II" takes place sometime after the first "Darius" game. The colonized planet Darius is recuperating from its invasion from the alien Belser Army thanks to that game's heroes Proco and Tiat. Darius' inhabitants have since situated themselves on the planet Olga while Darius' societies, architecture and attacked areas were being repaired. The space flight Headquarters established on Olga picks up an SOS signal coming from Earth, where the first colonists originated before colonizing Darius. The signal included the description of alien ships similar to those of the Belser Army. Suspecting that these might be their remaining Earthling ancestors, the people of Darius sends both Proco Jr. and Tiat Young to help them.
Ports.
A Mega Drive conversion was released in Japan in 1990; it was later released for the Genesis in the United States and Brazil in 1991, where it was renamed "Sagaia". Changes include a boss rush mode (via a code) and various modifications to levels and mechanics, such as the boss Steel Spine being moved to another level and the boss Killer Higia being replaced with a similar creation called Nehonojia. This conversion does not support two players, so the ability to choose between Proco Jr. and Tiat Young was added; Proco plays like normal, while Tiat starts every life off with one power level to every weapon.
A Master System conversion, developed by Natsume, was released in Europe and Brazil in 1992, also titled "Sagaia". It is somewhat based on the Mega Drive port, and while Tiat Young and her abilities are still present (though even more limited), many zones (and thus bosses) have been completely removed.
The Super CD-ROM² version features an entirely new set of bosses, major changes to levels, and a fully arranged soundtrack including new songs.
In 1996, a port of the arcade version itself was released in Japan and Europe for the Sega Saturn, complete with two-player mode and stretchable wide screen modes. The arcade version is also available in the Japan-only "Taito Memories" series of emulation-based compilations.
Reception.
In Japan, "Game Machine" listed "Darius II" on their November 15, 1989 issue as being the sixth most-successful upright arcade unit of the year.


MICRODOS.SYS


MX Linux

MX Linux is a midweight Linux operating system based on Debian stable and using core antiX components, with additional software created or packaged by the MX community. It was developed as a cooperative venture between the antiX and former MEPIS communities. The community's stated goal is to produce "a family of operating systems that are designed to combine elegant and efficient desktops with high stability and solid performance". MX Linux uses the Xfce desktop environment as its flagship, to which it adds a freestanding KDE Plasma version and a Fluxbox implementation. Other environments can be added or are available as "spin-off" ISO images.
History.
MX Linux began in a discussion about future options among members of the MEPIS community in December 2013. Developers from antiX then joined them, bringing the ISO build system as well as Live-USB/DVD technology. To be listed on the Linux distribution clearinghouse website DistroWatch, MX Linux was initially presented as a version of antiX. It received its own DistroWatch page with the release of the first public beta of MX-16 on November 2, 2016.
The MX-14 series was based on Debian Stable "Wheezy", using Xfce 4.10 and then, with the 14.4 release, Xfce 4.12. The MX-14 versions were intended to fit onto a CD, which limited the number of applications that could be included. This series saw the gradual evolution of the MX Tools, a collection of utilities to help users with common tasks that are often complicated and obscure.
MX-15 moved to the new Debian Stable "Jessie" using systemd-shim, meaning that systemd is installed but the default init is sysvinit. The size limitation was lifted, enabling the developers to present a full turnkey product. There was substantial expansion of MX Tools.
MX-16 was still based on Debian Stable "Jessie", but with many applications backported and added and from other sources. There were further refinements to MX Tools, import of advanced antiX developments, expanded support, and a completely new icon/theme/wallpaper collection.
MX-16.1 collected all bug fixes and improvements since MX-16, added a new kingfisher theme, upgraded and streamlined MX Tools, revised documentation, and added new translations.
MX-17 changed its base to Debian 9 (Stretch) and brought upgraded artwork, new MX Tools, improved Live operation via antiX and other changes.
MX-18 continued the development of MX Tools, introduced a new kernel, enabled whole disk encryption, and added grub themes, splash functionality through MX Boot options artwork, and improved localization.
MX-19 upgraded its base to Debian 10 (Buster) and its default desktop to Xfce 4.14. It is characterized by new and revised Tools, artwork, documentation, localization and technical features.
A fully integrated overlay called MX-Fluxbox was released December 12, 2019. Two apps, mx-idesktool and mx-dockmaker, were added for a Fluxbox environment in MX 19.2.
A KDE version was released August 16, 2020, an Advanced Hardware Support (AHS) enabled (64-bit only) version of MX featuring the KDE/Plasma desktop.
Features.
MX Linux has basic tools like a graphic installer that handles UEFI computers, a GUI-based method to change a Linux kernel and other core programs.
It includes MX Tools, a suite of user-oriented utilities, many of which were developed specifically for MX, while some were forked from existing antiX applications or are existing antiX applications; a couple were imported with permission from outside sources. A particularly popular one is MX-snapshot, a GUI tool to remaster a live session or installation into a single .ISO file. The "cloned" image is bootable from disk or USB flash drive, maintaining all settings, allowing an installation to be completely backed up, and/or distributed with minimal administrative effort, since an advanced method of copying the file system (developed by antiX-Linux) uses bind-mounts performing the "heavy lifting".


List of Intel Itanium microprocessors

The Itanium from Intel is a high-end server and supercomputer microprocessor.
Itanium (2007–2019).
Tukwila (65 nm).
All models support: XD bit (an NX bit implementation), Hyper-threading, Turbo Boost, VT-i2 (Itanium Virtualization technology), Intel VT-d, RAS with Advanced Machine Check Architecture, Cache Safe technology, Enhanced Demand Based Switching, two DDR3 memory controllers and ECC.
Poulson (32 nm).
All models support: Itanium New Instructions, XD bit (an NX bit implementation), Intel VT-x, Intel VT-d, VT-i3 (Itanium Virtualization technology), Hyper-threading (with Dual-Domain Multithreading), Turbo Boost, Enhanced Intel SpeedStep Technology (EIST), Cache-Safe technology, RAS with Advanced Machine Check Architecture, Instruction Replay technology, ECC, two DDR3 memory controllers.
Kittson (32 nm).
The 9700 series is an extension of the 9500 series of Itanium processors.


PlayStation 4 Slim


Lavarand

Lavarand was a hardware random number generator designed by Silicon Graphics that worked by taking pictures of the patterns made by the floating material in lava lamps, extracting random data from the pictures, and using the result to seed a pseudorandom number generator.
Details.
Although the secondary part of the random number generation uses a pseudorandom number generator, the full process essentially qualifies as a "true" random number generator due to the random seed that is used. However, its applicability is limited by its low bandwidth.
It was covered under the now-expired , titled "Method for seeding a pseudo-random number generator with a cryptographic hash of a digitization of a chaotic system."
From 1997 to 2001,
there was a Web site at lavarand.sgi.com demonstrating the technique. Landon Curt Noll, one of the originators, went on to help develop LavaRnd, which does not use lava lamps. Despite the short life of lavarand.sgi.com, it is often cited as an example of an online random number source.
 Cloudflare maintains a similar system of lava lamps for securing Internet traffic.


Atari System

Atari System refers to two arcade system boards introduced in 1984 for use in various arcade games from Atari Games. Two versions of the board were released, Atari System 1 and Atari System 2.
Atari System 1.
The Atari System 1 was Atari Games' first upgradeable arcade game hardware platform. Introduced in 1984, the System 1 platform was used for the following games:
The hardware used a large circuit board with a Motorola 68010 main CPU running at 7.159 MHz, a MOS Technology 6502 sound CPU running at 1.789 MHz, a system ROM, text and graphics display hardware, and control interfaces. Two large edge-card connectors allowed a "cartridge board" to be plugged in; the cartridge board supplied the main program ROMs, sound program ROMs, graphics ROMs, graphics shift registers, a "SLAPSTIC" copy protection chip, a Yamaha YM2151 FM sound generator, a POKEY and (for some games) TI TMS5220 LPC speech synthesis chip. System 1 was capable of generating a max resolution of 336 x 240 with 256 colors from a palette of 1024 colors.
Converting one System 1 game into another generally required replacing the cartridge board, attraction marquee, control panel, and in some cases installing additional controls (e.g., foot pedal for Road Blasters).
Several games (most notably "Gauntlet" and "Gauntlet II") used hardware that was electrically very similar to System 1, but implemented on a single board rather than using a cartridge board.
Early System 1 boards and cartridge boards used large numbers of 7400 series TTL chips. These boards were later replaced by the functionally identical "System 1 LSI Main" and "LSI Cartridge" boards, which used ASICs for reduced manufacturing costs.
Modular or upgradeable video games were not commonly offered by the major video game companies in the 1970s and 1980s, because it was more profitable to sell an entirely new machine. System 1 and the Japanese JAMMA wiring standard were attempts to move to a modular solution, though there were many smaller companies that sold conversion kits for competitors' hardware.
The System 1 and its games are noted for the use of "raw" sounding FM Synthesizers for sound effects and music: that is, the music many times used instruments that had the modulation settings turned too high or too low to emulate realistic sounding instruments, instead creating a warbly or noisy sound.
Atari System 2.
Very soon after the introduction of the Atari System 1, the Atari System 2 was introduced. The System 2 platform was used for the following games:
Probably the most noticeable difference between the System 2 and System 1 games was the fact that the System 2 used higher-resolution graphics. The video resolution was 512x384 and as such a medium-resolution monitor was used (System 1 used low resolution).
The hardware was similar to its predecessor in the fact that it used two main circuit boards. In this case it used a "CPU board" and a "Video Board". The EPROMs were split between both boards.
The main CPU was a Digital Equipment Corporation (DEC) T-11 microprocessor running at 10 MHz.
The sound CPU was a MOS Technology 6502 running at 1.789 MHz, and the sound chips used were a Yamaha YM2151 running at approx. 3.579 MHz, 2 POKEYs at approx. 1.789 MHz and a TMS5220 running at 625 kHz.


COPY (command)


VEX prefix

The VEX prefix (from "vector extensions") and VEX coding scheme are comprising an extension to the x86 and x86-64 instruction set architecture for microprocessors from Intel, AMD and others.
Features.
The VEX coding scheme allows the definition of new instructions and the extension or modification of previously existing instruction codes. This serves the following purposes:
The VEX prefix "replaces" the most commonly used instruction prefix bytes and escape codes. In many cases, the number of prefix bytes and escape bytes that are replaced is the same as the number of bytes in the VEX prefix, so that the total length of the VEX-encoded instruction is the same as the length of the legacy instruction code. In other cases, the VEX-encoded version is longer or shorter than the legacy code. In 32-bit mode VEX encoded instructions can only access the first 8 YMM/XMM registers; the encodings for the other registers would be interpreted as the legacy LDS and LES instructions that are not supported in 64-bit mode.
The two-byte VEX prefix contains the following components:
The three-byte VEX prefix additionally contains:
Technical description.
The VEX coding scheme uses a code prefix consisting of two or three bytes, which is added to existing or new instruction codes.
In x86 architecture, instructions with a memory operand may use the ModR/M byte which specifies the addressing mode. This byte has three bit fields:
The base-plus-index and scale-plus-index forms of 32-bit addressing (encoded with r/m=100 and mod <>11) require another addressing byte, the SIB byte. It has the following fields:
To use 64-bit addressing and additional registers present in the x86-64 architecture, the REX prefix has been introduced which provides additional space for encoding addressing modes. Bit-field W changes the operand size to 64 bits, R expands "reg" to 4 bits, B expands "r/m" (or "opreg" in the few opcodes such as "POP reg" which encode register number in their 3 lowest opcode bits), and X and B expand "index" and "base" in the SIB byte. However REX prefix is encoded quite inefficiently, wasting half of its 8 bits.
The VEX prefix provides a compact representation of the REX prefix, as well as various other prefixes, to expand the addressing mode, register enumeration and operand size and width:
Instructions coded with the VEX prefix can have up to four variable operands (in registers or memory) and one constant operand (immediate value). Instructions that need more than three variable operands use immediate operand bits to specify a 4th register operand (IS4 above). At most one of the operands can be a memory operand; and at most one of the operands can be an immediate constant of 4 or 8 bits. The remaining operands are registers.
The AVX instruction set is the first instruction set extension to use the VEX coding scheme. The AVX instruction set uses VEX prefix only for instructions using the SIMD XMM registers.
However, the VEX coding scheme has been used for other instruction types as well in subsequent expansion of instruction set. For example, BMI introduced VEX coded arithmetic and bit manipulation instructions that operate on general purpose registers. AVX-512 introduced 8 mask registers and added instructions to manipulate them. These instructions use VEX encoding. VEX.R, VEX.B or VEX.v3 is ignored when the field is used to encode a mask register.
The VEX prefix's initial-byte values, C4h and C5h, are the same as the opcodes of the LDS and LES instructions. These instructions are not supported in 64-bit mode. To resolve the ambiguity while in 32-bit mode, VEX's specification exploits the fact that a legal LDS or LES's ModRM byte can not be of the form "11xxxxxx" (which would specify a register operand). Various bit-fields in the VEX prefix's second byte are inverted to ensure that the byte is always of this form in 32-bit mode.
Legacy SIMD instructions with a VEX prefix added are equivalent to the same instructions without VEX prefix with the following differences:
Instructions that use the whole 256-bit YMM register should not be mixed with non-VEX instructions that leave the upper half of the register unchanged, for reasons of efficiency.


List of Intel Ice Lake-based Xeon microprocessors


LOADALL

LOADALL is the common name for two different, undocumented machine instructions of Intel 80286 and Intel 80386 processors, which allow access to areas of the internal processor state that are normally outside of the IA-32 API scope, like "descriptor cache registers". The LOADALL for 286 processors is encoded 0Fh 05h, while the LOADALL for 386 processors is 0Fh 07h.
Both variants – as the name implies – load all CPU internal registers in one operation. LOADALL had the unique ability to set up the visible part of the segment registers (selector) independently of their corresponding cached part, allowing the programmer to bring the CPU into states not otherwise allowed by the official programming model.
Usage.
As an example of the usefulness of these techniques, LOADALL can set up the CPU to allow access to all memory from real mode, without having to switch it into unreal mode (which requires switching into protected mode, accessing memory and finally switching back to real mode). Programs such as the pre-XMS versions of RAMDRIVE.SYS (1985), SMARTDRV.SYS (1986) as well as HIMEM.SYS (2.03, 1988-08-04; 2.04, 1988-08-17) drivers in MS-DOS, Uniform Software Systems' The Extender (1985) and The Connector (1985) for Lotus 1-2-3, Above Disk (1986) (a LIMulator by Above Software (formerly Tele-Ware West aka Los Angeles Securities Group) that converted hard disk space or extended memory into expanded memory), and OS/2 1.0 and 1.1 used the 286 LOADALL instruction. DOS 3.3 and 4.0 reserved a 102-byte buffer at 0070:0100h (which was normally occupied by DOS BIOS data) so that there was no need to save & restore it for LOADALL. Microsoft's EMM386.EXE special-cases both the 286 and 386 LOADALL instructions in its invalid opcode handler. Examination of the virtual-machine monitor code in Windows/386 2.10 shows that it uses both the 286 and the even less known 386 variant. Microsoft's HIMEM.SYS version 2.06 also used LOADALL to quickly copy to and from extended memory on 286 systems.
Another interesting usage of LOADALL, laid out in the book "The Design of OS/2", would have been to allow running former real-mode programs in 16-bit protected mode, as utilized by Digital Research's Concurrent DOS 286 since 1985, as well as FlexOS 286 and IBM 4680 OS since 1986. Marking all the descriptor caches in the GDT and LDTs "not present" would allow the operating system to trap segment-register reloads, as well as attempts at performing real-mode–specific "segment arithmetic" and emulate the desired behavior by updating the segment descriptors (LOADALL again). This "virtual 8086 mode" for the 80286 was, however, too slow to be practical. The idea had to be mostly discarded, furthermore, due to errata in some early Intel 80286 processors before the E-2 stepping. As a result, OS/2 1.x – and Windows in "standard" mode as well – had to run DOS programs in real mode. Nevertheless, the idea was not lost; it led Intel to introduce the virtual 8086 mode of the 80386, allowing the implementation of "DOS boxes" at last in a relatively efficient and documented way.
Because LOADALL did not perform any checks on the validity of the data loaded into processor registers, it was possible to load a processor state that could not be normally entered, such as using real mode (PE=0) together with paging (PG=1) on 386-class CPUs.
An in-circuit emulator (ICE) is a tool used for low-level debugging. On Intel 80386, asserting the undocumented pin at location B6 causes the microprocessor to halt execution and enter ICE mode. The microprocessor saves its entire state to an area of memory isolated from normal system memory. The layout of this area is suitable for LOADALL instruction, and this instruction is used by ICE code to return to normal execution.
In later processors, this evolved into System Management Mode (SMM). In SMM, the RSM instruction is used to load a full CPU state from a memory area. The layout of this memory area is similar to one used by the LOADALL instruction. 386-style LOADALL instruction can be executed on 486 too, but only in SMM mode. In later processors, RSM instruction, with a different encoding, took its role.
Microsoft's Codeview 3.0 and Borland's Turbo Debugger 2.0 correctly decode 286 and 386 LOADALL instructions.
As the two LOADALL instructions were never documented and do not exist on later processors, the opcodes were reused in the AMD64 architecture. The opcode for the 286 LOADALL instruction, 0F05, became the AMD64 instruction SYSCALL; the 386 LOADALL instruction, 0F07, became the SYSRET instruction. These definitions were implemented even on Intel CPUs with the introduction of the Intel 64 implementation of AMD64.
80286.
Opcode 0F05. The instruction reads data from addresses 00800–00866, whatever the content of the segment registers.
The 80286 LOADALL instruction can not be used to switch from protected back to real mode (it can't clear the PE bit in the MSW). However, use of the LOADALL instruction can avoid the need to switch to protected mode altogether.
80386.
Opcode 0F07. The instruction loads data from address ES:EDI. It actually uses ES, not the ES descriptor.


Beyond Oasis

Beyond Oasis, known in Japan and Europe as The Story of Thor: A Successor of the Light, is an action-adventure game developed by Ancient and published by Sega for the Sega Genesis. The game has also been re-released in various emulated collections, such as the Virtual Console, "Sonic's Ultimate Genesis Collection", and "Sega Forever". A prequel to the game, "The Legend of Oasis", was released for the Sega Saturn in 1996.
Plot.
The player takes the role of Prince Ali, who has discovered a buried gold "armlet" which once belonged to a wizard who waged a long war against the evil wielder of a silver armlet. The silver armlet was used to create chaos and destruction, while the gold armlet had the power to summon four spirits: the water spirit, "Dytto"; the fire spirit, "Efreet"; the shadow spirit, "Shade"; and the plant spirit, "Bow". Ali travels the land of Oasis, gradually acquiring the ability to summon all these spirits, in an attempt to stop the person who has discovered the ancient silver armlet and is once again using it for evil.
Gameplay.
The game has action adventure elements similar to The Legend of Zelda series. The player controls Prince Ali and takes him across the maps to fulfill his quest. Along the way the player picks up special items to restore health and magic, special weapons to help defeat enemies, and four magic spirits found in shrines to aid Prince Ali's mission.
Prince Ali's default weapon is his knife, which can perform special attacks and has unlimited usage. Also during the course of the game the player can equip Prince Ali with special weapons such as swords, crossbows, and bombs. Some crossbows (and a sword) can ignite their targets on fire. However, unlike the knife, these weapons do not have unlimited usage and will break after a set number of uses.
Reception.
"Game Informer" gave the game a "very good" score of 8.75/10. "Electronic Gaming Monthly" gave it a 38/50 (7.6/10 average), praising the vast game world and strong plot twists. A reviewer for "Next Generation" contended that the combination of RPG and action elements results in a game which is average on both fronts. He added that, "The use of magic, whether it be the fireball or meteor storm; a user-friendly interface; and an ever-ready map put "Beyond Oasis" beyond others of its type. But ultimately, poor fighting and an uninspired storyline leave this title looking more like a mirage." "GamePro" commented that the game "is definitely not for hardcore RPGers" due to its small game world, limited challenge, and greater emphasis on hack-n-slash combat and puzzle solving than on RPG elements, but would be a good game for players new to the RPG genre. They praised the "intriguing" gameplay and the 3D feel of the graphics.
"IGN" gave the Virtual Console re-release an 8/10, calling it "very stylish," and expressing "surprise" that despite a lack of polish in certain areas, its "unique" mechanics "deserve to be mentioned alongside such classics as Secret of Mana."


BattleTanx

BattleTanx is a 1998 action game released for the Nintendo 64, produced by The 3DO Company. The game was followed by a 1999 sequel, titled "".
Plot.
In 2001, a virus has killed 99% of the female population of Earth. Various countries fight over each other's quarantine zones, and end up engaging in nuclear war, destroying much of civilization. The few remaining women (called Queenlords) are held by gangs who have taken over small pieces of the world. The main character, Griffin Spade, had his fiancée Madison taken away from Queens, New York by the U.S. government. Griffin ends up separated from his fiancée, and New York City is destroyed. He claims a tank for his own and sets out to cross the United States to find her, battling gangs as he reaches his goal. After surviving the ruins of New York City, Griffin heads westward gaining recruits in the countryside, Chicago, Las Vegas, and San Francisco.
Gameplay.
There are three tanks in the game for the player to choose from. The player can choose between a Moto Tank, M1A1 Abrams MBT, or the Goliath. There are 17 levels to complete in order to finish the single player game, all of which are filled with enemy tanks. Each level is located in a specific place in the United States, such as New York City, Chicago, Las Vegas, and San Francisco. The game features destructible environments, and in some cases, interactive environments.
In the game's multiplayer mode, players can battle with up to 4 players simultaneously. There are four different multiplayer configurations; Battlelord mode (equivalent to capture the flag), Deathmatch, Family Mode, and Annihilation.
Levels.
The first three levels all take place in New York City and involve the suburb of Queens, Queens Midtown Tunnel, and Times Square. The Chicago stage takes place in Lake Shore Drive and State Street. The Las Vegas stage takes place on the world-famous Fremont Street. The San Francisco stages take place on the Golden Gate Bridge, The Wharf, and the fictional Q-Zone.
Reception.
The Nintendo 64 version received favorable reviews, while the Game Boy Color version received unfavorable reviews, according to the review aggregation website GameRankings. "Next Generation" said that the former console version was "fast [and] controls well, and it's got tanks blowing up everything in sight – sounds good to us."


Take Command Console

Take Command Console (TCC), formerly known as "4DOS for Windows NT" ("4NT"), is a command-line interpreter by JP Software, designed as a substitute for the default command interpreter in Microsoft Windows, CMD.EXE.
Take Command was the name that JP Software used for their GUI command-line interpreters for Windows 3.1 (TC16), Windows 32-bit (TC32) and later OS/2 Presentation Manager (TCOS2). These were released concurrently with version 4DOS 5.5, 4NT 2.5 and 4OS2 2.52. The OS/2 and Windows 16-bit survived until version 2.02, they are still available for download from the FTP site on JP Software.
History.
TCC is based on the earlier 4DOS command shell for DOS, and 4OS2 for OS/2.
Beginning with version 12 of 4NT, support for Windows 95, 98, ME, NT and 2000 were removed. Beginning with version 16 of TCC, support for Windows XP was removed, although it might still run in XP. 4NT was renamed to Take Command Console as part of JP Software's Take Command version 9. Beginning with version 9, the name Take Command was applied to an entirely different assembly of products: TCI (Tabbed Command Interface) and 4NT. The original Take Command is no longer being developed. TCI was expanded to include a file manager and various other windows, while 4NT was renamed TCC, and issued in "light" form.
Features.
TCC provides a rich set of command line and batch programming capabilities. It can work in conjunction with other scripting languages, such as REXX, Ruby and Perl, or Windows Scripting languages, in the form of Active Scripting engines such as VBScript and JScript as well as PerlScript (via ActivePerl), TclScript (via ActiveTcl), PythonScript (via ActivePython), and the scripting engine version of Object REXX to provide greater access to the operating system.
TCC features a number of enhancements when compared to
Take Command.
Take Command is a command-line interpreter for the Microsoft Windows line of operating systems. Its advantages over the regular command shell are analogous to those of 4DOS over the codice_1 supplied with MS-DOS.
Beginning with version 9, Tabbed Console Interface and 4NT have been merged into the Take Command product line. 4NT was renamed to Take Command Console, with a Lite Edition (TCC/LE) released as freeware. Take Command includes a tabbed interface, configurable toolbars, and an integrated graphical file explorer. Take Command adds a built-in batch file editor and debugger, FTP and HTTP file access in commands, network file system access, Active Scripting integration, system monitoring commands, and Windows service controls.
Features of note include:


Cyrix Cx486DLC

The Cyrix Cx486DLC was an early 486 CPU from Cyrix, intended to compete
with the Intel 486SX and DX. Texas Instruments, who manufactured the 486DLC for Cyrix, later released its own version of the chip, the TI486SXL, with 8 kB internal cache vs 1 kB of the original Cyrix design. The similarly named IBM 486DLC, 486DLC2, 486DLC3 (aka Blue Lightning) are often confused with the Cyrix chips, but are not related and are instead based on Intel's i486 design.
Introduced in June 1992, like the later and more famous Cyrix Cx5x86 it was a hybrid CPU, incorporating features of a new CPU (in this case the Intel 80486) while plugging into its predecessor's (386DX) socket. It ran at speeds of 25, 33, and 40 MHz.
The 486DLC can be described as a 386DX with the 486 instruction set and 1 KB of on-board L1 cache added. Because it used the 386DX bus (unlike its 16-bit cousin, the 486SLC) it was a fully 32-bit chip. Like the 386 and 486SX, it had no on-board math coprocessor, but unlike the 486SX, it could make use of an Intel 387DX or compatible numeric coprocessor. A few 486SX motherboards also provided i387 sockets, but this feature was a very much a rarity. Due to the smaller L1 cache, the 486DLC could not compete on a clock-for-clock basis with the 486SX, but a 33 MHz 486DLC could keep pace with a 25 MHz 486SX, cost less, and offered the ability to upgrade further with the addition of an inexpensive math coprocessor.
While some advertisements in PC magazines from smaller manufacturers touted the superiority of their 486DLC over name-brand computers sporting a 486SX, in reality the only advantage the 486DLC offered feature-wise over the 486SX was the ability to add an inexpensive math coprocessor. The Intel 487 "math coprocessor" for 486SX users was in reality a CPU replacement—a 486DX with a different pinout—and originally cost several hundred dollars more than a 387.
As prices on Intel's 486 line fell, Cyrix found it more and more difficult for its 486SLC and DLC CPUs to compete and released a fully pin-compatible version of the 486SX and DX in 1993.
The 486DLC did not see widespread use among large OEMs, but it was widely known among the hardware enthusiast community that an AMD 386DX-40 or Cyrix 486DLC-33 could keep up with a 486SX-25 at a lower cost, so it gained a small following among budget-minded enthusiasts. It was also sometimes used as a replacement for a 386 CPU to give a small speed boost. However, the 486DLC was not designed to be a direct CPU replacement and could lead to stability problems in older boards it was not intended for. "Cyrix" aware motherboards usually had a few extra cache control lines to maintain cache coherency, as well as CPU register control in the BIOS to enable/disable the on-board cache. Cyrix later released a clock-doubled "direct replacement" upgrade package for 386DX systems called the Cx486DRu2. This kit included a standard 486DLC with an extra "dingus" that sat between the CPU and socket and provided the control lines for cache coherency. These kits were quickly superseded by the Cx486DRx2 CPU, which integrated the cache coherency circuitry into the CPU itself. The Cx486DRx2 appeared on the market in 1994, by which time the 486 was already being displaced by the Pentium. Sales were poor due to the high price and the underwhelming performance compared to a true Intel 486DX2. It was often cheaper to purchase a new 486 motherboard than to invest in an upgrade CPU.


AMD XGP

AMD XGP (eXternal Graphics Platform) is brand for an external graphics solution for laptops and notebooks by AMD. The technology was announced on June 4, 2008 on Computex 08 trade show, following the announcement of the codenamed "Puma" notebook platform.
Development.
Originally reported by Hexus.net as a side project to the R600 series graphics cards. Codenamed "Lasso", the project is an external graphics solution using desktop video cards, and data is sent via two cables as defined in PCI-E external cabling specification (version 1.0). The project would later fall into development hell with unknown development status. In June 2008, near Computex 2008, rumours surfaced over the Internet about AMD is preparing an external graphics solution for notebook computers, but using a proprietary connectivity solution instead. The ATI XGP was officially announced on June 4, 2008 during the course of the Computex 2008 exhibition.
Technology.
The XGP platform consists of several parts, that includes a mobility Radeon HD graphics card, an external case and a proprietary connectivity solution.


DRDOS.COM


Patrick Volkerding

Patrick Volkerding (born October 20, 1966) is the founder and maintainer of the Slackware Linux distribution. Volkerding is Slackware's "Benevolent Dictator for Life" (BDFL), and is also known informally as "The Man".
Personal life.
Volkerding earned a Bachelor of Science in computer science from Minnesota State University Moorhead in 1993. Volkerding is a Deadhead, and by April 1994 had already attended 75 concerts.
Volkerding is a Church of the SubGenius affiliate/member. The use of the word "slack" in "Slackware" is an homage to J. R. "Bob" Dobbs. About the SubGenius influence on Slackware, Volkerding has stated: "I'll admit that it was SubGenius inspired. In fact, back in the 2.0 through 3.0 days we used to print a dobbshead on each CD."
Volkerding is an avid homebrewer and beer lover. Early versions of Slackware would entreat users to send him a bottle of local beer in appreciation for his work.
Volkerding was married in 2001 to Andrea and has a daughter Briah Cecilia Volkerding (b. 2005).
Illness.
In 2004, Volkerding announced via mailing list post that he was suffering from Actinomycosis, a serious illness requiring multiple rounds of antibiotics and with an uncertain prognosis. This announcement caused a number of tech news outlets to wonder about the future of the Slackware project. As of 2012, both Volkerding and the Slackware project were reported to be in a healthy state again.
Slackware Linux.
For a short while, Chris Lumens and others assisted with his work on Slackware. Due to the lack of a continuing revenue stream following the sale of his publisher, Walnut Creek CDROM, to BSDi (which was ultimately sold to Wind River Systems), these people had to be let go.
For the last several years Volkerding has managed Slackware with the help of many volunteers and testers.
Awards.
In 2014, Volkerding received the O'Reilly Open Source Award.


Indus OS

Indus OS is an Indian app and content discovery platform based on Android that brings the users, app developers and smartphone brands on a single platform and truly creates an Indian smartphone ecosystem.
The platform is addressing the low smartphone adoption, content consumption and linguistic challenges of Indian markets. The contextual integration provides India's service & content providers a platform to seamlessly distribute their content & services and engage with India's ever-growing smartphone users.
The company is catering to 10 crore+ users and has partnered with top OEMs like Samsung, Karbonn, Micromax and 9 other Indian OEMS.
The company's app marketplace, Indus App Bazaar is the largest Indian app store. It is powering Samsung's default app store, Galaxy Store Since 2019.
About.
Indus OS was founded in 2013 by Rakesh Deshmukh, Akash Dongre and Sudhir B; all three are alumni of the Indian Institute of Technology, Bombay.
Hari Padmanabhan, an IIT Kanpur alumni, industry veteran and serial entrepreneur, is a seed investor in the company. The company is funded by various investors such as "Omidyar Network, JSW Ventures, VenturEast, Samsung Ventures & Affle".
Indus OS has offices in Mumbai, Delhi and Singapore and currently has an 84-member team.
Firstouch OS.
Indus OS was initially known as "First Touch OS". In May 2015, Micromax Informatics started shipping the latest version (Unite 3) of its Unite series smartphones with Firstouch OS. The operating system was available in English and 10 Indian languages. A key feature of the operating system was the Swipe-to-translate or Indus Swipe which helped users to translate or transliterate English text in regional languages. The operating system also had its own app marketplace' App Bazaar with over 5,000 applications in regional languages.
In December 2015, Firstouch announced a collaboration with the Government of India's Ministry of Electronics and Information Technology previously known as the Department of Electronics and IT (DeitY) to introduce text-to-speech technology in regional languages.
Indus App Bazaar.
The Indus App Bazaar is India's largest Indian app store. It is available 12 Indian languages namely Hindi, Gujarati, Marathi, Tamil, Telugu, Urdu, Odia, Punjabi, Malayalam, Bengali, Assamese and Kannada & English . It has over 4 lakh applications in regional languages. Top publishers on the platform include Truecaller, Amazon, Winzo Games, Blacklight Studio, Sharechat, Junglee Games, Ola, Meesho, MSN, Times Group, Editorji, Inshorts, Rebel Group, Opera News, mpokket, etc.
The product provides various tools to app developers for distribution and promotions along with data insights for targeting and performance analysis. The app store focuses on providing the users with a personalised and localised experience with rich user interface for smooth discovery of apps and content.
Investors.
The major investors include Omidyar Network, JSW Ventures, VenturEast, Samsung Ventures and Affle.


Batch file

A batch file is a script file in DOS, OS/2 and Microsoft Windows. It consists of a series of commands to be executed by the command-line interpreter, stored in a plain text file. A batch file may contain any command the interpreter accepts interactively and use constructs that enable conditional branching and looping within the batch file, such as codice_1, codice_2, and codice_3 labels. The term "batch" is from batch processing, meaning "non-interactive execution", though a batch file may not process a "batch" of multiple data.
Similar to Job Control Language (JCL), DCL and other systems on mainframe and minicomputer systems, batch files were added to ease the work required for certain regular tasks by allowing the user to set up a script to automate them. When a batch file is run, the shell program (usually COMMAND.COM or cmd.exe) reads the file and executes its commands, normally line-by-line. Unix-like operating systems, such as Linux, have a similar, but more flexible, type of file called a shell script.
The filename extension .bat is used in DOS and Windows. Windows NT and OS/2 also added .cmd. Batch files for other environments may have different extensions, e.g., .btm in 4DOS, 4OS2 and 4NT related shells.
The detailed handling of batch files has changed significantly between versions. Some of the detail in this article applies to all batch files, while other details apply only to certain versions.
Variants.
DOS.
In DOS, a batch file can be started from the command-line interface by typing its name, followed by any required parameters and pressing the key. When DOS loads, the file AUTOEXEC.BAT, when present, is automatically executed, so any commands that need to be run to set up the DOS environment may be placed in this file. Computer users would have the AUTOEXEC.BAT file set up the system date and time, initialize the DOS environment, load any resident programs or device drivers, or initialize network connections and assignments.
A .bat file name extension identifies a file containing commands that are executed by the command interpreter COMMAND.COM line by line, as if it were a list of commands entered manually, with some extra batch-file-specific commands for basic programming functionality, including a codice_3 command for changing flow of line execution.
Early Windows.
Microsoft Windows was introduced in 1985 as a graphical user interface-based (GUI) overlay on text-based operating systems and was designed to run on DOS. In order to start it, the codice_5 command was used, which could be added to the end of the AUTOEXEC.BAT file to allow automatic loading of Windows. In the earlier versions, one could run a .bat type file from Windows in the MS-DOS Prompt. Windows 3.1x and earlier, as well as Windows 9x invoked COMMAND.COM to run batch files.
OS/2.
The IBM OS/2 operating system supported DOS-style batch files. It also included a version of REXX, a more advanced batch-file scripting language. IBM and Microsoft started developing this system, but during the construction of it broke up after a dispute; as a result of this, IBM referred to their DOS-like console shell without mention of Microsoft, naming it just DOS, although this seemingly made no difference with regard to the way batch files worked from COMMAND.COM.
OS/2's batch file interpreter also supports an EXTPROC command. This passes the batch file to the program named on the EXTPROC file as a data file. The named program can be a script file; this is similar to the #! mechanism.
Windows NT.
Unlike Windows 98 and earlier, the Windows NT family of operating systems does not depend on MS-DOS. Windows NT introduced an enhanced 32-bit command interpreter (cmd.exe) that could execute scripts with either the .CMD or .BAT extension. Cmd.exe added additional commands, and implemented existing ones in a slightly different way, so that the same batch file (with different extension) might work differently with cmd.exe and COMMAND.COM. In most cases, operation is identical if the few unsupported commands are not used. Cmd.exe's extensions to COMMAND.COM can be disabled for compatibility.
Microsoft released a version of cmd.exe for Windows 9x and ME called WIN95CMD to allow users of older versions of Windows to use certain cmd.exe-style batch files.
, cmd.exe is the normal command interpreter for batch files; the older COMMAND.COM can be run as well in 32-bit versions of Windows able to run 16-bit programs.
Batch file parameters.
COMMAND.COM and cmd.exe support that a number of special variables (codice_14, codice_15 through codice_16) in order to refer to the path and name of the batch job and the first nine calling parameters from within the batch job, see also SHIFT. Non-existent parameters are replaced by a zero-length string. They can be used similar to environment variables, but are not stored in the environment. Microsoft and IBM refer to these variables as "replacement parameters" or "replaceable parameters", whereas Digital Research, Novell and Caldera established the term "replacement variables" for them. JP Software calls them "batch file parameters".
Examples.
This example batch file displays codice_17, prompts and waits for the user to press a key, and then terminates. (Note: It does not matter if commands are lowercase or uppercase unless working with variables)
@ECHO OFF
ECHO Hello World!
PAUSE
To execute the file, it must be saved with the filename extension suffix .bat (or .cmd for Windows NT-type operating systems) in plain text format, typically created by using a text editor such as Microsoft Notepad or a word processor working in plain text mode.
When executed, the following is displayed:
Explanation.
The interpreter executes each line in turn, starting with the first. The codice_18 symbol at the start of any line prevents the prompt from displaying that command as it is executed. The command codice_19 turns off the prompt permanently, or until it is turned on again. The combined codice_20 is often as here the first line of a batch file, preventing any commands from displaying, itself included. Then the next line is executed and the codice_21 command outputs codice_17. The next line is executed and the codice_23 command displays codice_24 and pauses the script's execution. After a key is pressed, the script terminates, as there are no more commands. In Windows, if the script is executed from an already running command prompt window, the window remains open at the prompt as in MS-DOS; otherwise, the window closes on termination.
Limitations and exceptions.
Null values in variables.
Variable expansions are substituted textually into the command, and thus variables which contain nothing simply disappear from the syntax, and variables which contain spaces turn into multiple tokens. This can lead to syntax errors or bugs.
For example, if %foo% is empty, this statement:
IF %foo%==bar ECHO Equal
parses as the erroneous construct:
IF ==bar ECHO Equal
Similarly, if codice_25 contains codice_26, then a different syntax error results:
IF abc def==bar ECHO Equal
The usual way to prevent this problem is to surround variable expansions in quotes so that an empty variable expands into the valid expression codice_27 instead of the invalid codice_28. The text that is being compared to the variable must also be enclosed in quotes, because the quotes are not special delimiting syntax; these characters represent themselves.
IF "%foo%"=="bar" ECHO Equal
The delayed !VARIABLE! expansion available in Windows 2000 and later may be used to avoid these syntactical errors. In this case, null or multi-word variables do not fail syntactically because the value is expanded after the IF command is parsed:
IF !foo!==bar ECHO Equal
Another difference in Windows 2000 or higher is that an empty variable (undefined) is not substituted. As described in previous examples, previous batch interpreter behaviour would have resulted in an empty string. Example:
C:\>set MyVar=
C:\>echo %MyVar%
%MyVar%
C:\>if "%MyVar%"=="" (echo MyVar is not defined) else (echo MyVar is %MyVar%)
MyVar is %MyVar%
Batch interpreters prior to Windows 2000 would have displayed result codice_29.
Quotation marks and spaces in passed strings.
Unlike Unix/POSIX processes, which receive their command-line arguments already split up by the shell into an array of strings, a Windows process receives the entire command-line as a single string, via the GetCommandLine API function. As a result, each Windows application can implement its own parser to split the entire command line into arguments. Many applications and command-line tools have evolved their own syntax for doing that, and so there is no single convention for quoting or escaping metacharacters on Windows command lines.
Where a string contains quotation marks, and is to be inserted into another line of text that must also be enclosed in quotation marks, particular attention to the quoting mechanism is required:
C:\>set foo="this string is enclosed in quotation marks"
C:\>echo "test 1 %foo%"
"test 1 "this string is enclosed in quotation marks""
C:\>eventcreate /T Warning /ID 1 /L System /SO "Source" /D "Example: %foo%"
ERROR: Invalid Argument/Option - 'string'.
Type "EVENTCREATE /?" for usage.
On Windows 2000 and later, the solution is to replace each occurrence of a quote character within a value by a series of three quote characters:
C:\>set foo="this string is enclosed in quotes"
C:\>set foo=%foo:"="""%
C:\>echo "test 1 %foo%"
"test 1 """this string is enclosed in quotes""""
C:\>eventcreate /T Warning /ID 1 /L System /SO "Source" /D "Example: %foo%"
SUCCESS: A 'Warning' type event is created in the 'Source' log/source.
Escaped characters in strings.
Some characters, such as pipe (codice_30) characters, have special meaning to the command line. They cannot be printed as text using the command unless escaped using the caret ^ symbol:
C:\>Echo foo | bar
'bar' is not recognized as an internal or external command,
operable program or batch file.
C:\>Echo foo ^| bar
foo | bar
However, escaping does not work as expected when inserting the escaped character into an environment variable. The variable ends up containing a live pipe command when merely echoed. It is necessary to escape both the caret itself and the escaped character for the character display as text in the variable:
C:\>set foo=bar | baz
'baz' is not recognized as an internal or external command,
operable program or batch file.
C:\>set foo=bar ^| baz
C:\>echo %foo%
'baz' is not recognized as an internal or external command,
operable program or batch file.
C:\>set foo=bar ^^^| baz
C:\>echo %foo%
bar | baz
The delayed expansion available with or with in Windows 2000 and later may be used to show special characters stored in environment variables because the variable value is expanded after the command was parsed:
C:\>cmd /V:ON
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\>set foo=bar ^| baz
C:\>echo !foo!
bar | baz
Sleep or scripted delay.
Until the TIMEOUT command was introduced with Windows Vista, there was no easy way to implement a timed pause, as the PAUSE command halts script activity indefinitely until any key is pressed.
Many workarounds were possible, but generally only worked in some environments: The codice_31 command was not available in older DOS versions, codice_32 was only available if TCP/IP was installed, and so on. No solution was available from Microsoft, but a number of small utility programs, could be installed from other sources. A commercial example would be the 1988 Norton Utilities Batch Enhancer (BE) command, where codice_33 would wait for 1 second, or the free 94-byte WAIT.COM where codice_34 would wait for 5 seconds, then return control to the script. Most such programs are 16-bit .COM files, so are incompatible with 64-bit Windows.
Text output with stripped CR/LF.
Normally, all printed text automatically has the control characters for carriage return (CR) and line feed (LF) appended to the end of each line.
@echo foo
@echo bar
C:\>batchtest.bat
foo
bar
It does not matter if the two echo commands share the same command line; the CR/LF codes are inserted to break the output onto separate lines:
C:\>@echo Message 1&@echo Message 2
Message 1
Message 2
A trick discovered with Windows 2000 and later is to use the special prompt for input to output text without CR/LF trailing the text. In this example, the CR/LF does not follow Message 1, but does follow Line 2 and Line 3:
@echo off
set /p ="Message 1"<nul
echo Message 2
echo Message 3
C:\>batchtest2.bat
Message 1Message 2
Message 3
This can be used to output data to a text file without CR/LF appended to the end:
C:\>set /p ="Message 1"<nul >data.txt
C:\>set /p ="Message 2"<nul »data.txt
C:\>set /p ="Message 3"<nul »data.txt
C:\>type data.txt
Message 1Message 2Message 3
However, there is no way to inject this stripped CR/LF prompt output directly into an environment variable.
Setting a Uniform Naming Convention (UNC) working directory from a shortcut.
It is not possible to have a command prompt that uses a UNC path as the current working directory; e.g. codice_35
The command prompt requires the use of drive letters to assign a working directory, which makes running complex batch files stored on a server UNC share more difficult. While a batch file can be run from a UNC file path, the working directory default is codice_36.
In Windows 2000 and later, a workaround is to use the ' and ' command with command extensions.
If not enabled by default, command extensions can be temporarily enabled using the switch for the command interpreter.
So to run a batch file on a UNC share, assign a temporary drive letter to the UNC share, and use the UNC share as the working directory of the batch file, a Windows shortcut can be constructed that looks like this:
The working directory attribute of this shortcut is ignored.
This also solves a problem related to User Account Control (UAC) on Windows Vista and newer. When an administrator is logged on and UAC is enabled, and they try to run a batch file as administrator from a network drive letter, using the right-click file context menu, the operation will unexpectedly fail. This is because the elevated UAC privileged account context does not have network drive letter assignments, and it is not possible to assign drive letters for the elevated context via the Explorer shell or logon scripts. However, by creating a shortcut to the batch file using the above / construct, and using the shortcut to run the batch file as administrator, the temporary drive letter will be created and removed in the elevated account context, and the batch file will function correctly.
The following syntax does correctly expand to the path of the current batch script.
 %~dp0
UNC default paths are turned off by default as they used to crash older programs.
The Dword registry value codice_37 at codice_38 allows the default directory to be UNC. codice_39 command will refuse to change but placing a UNC path in Default Directory in a shortcut to Cmd or by using the Start command. ( share is for administrators).
Character set.
Batch files use an OEM character set, as defined by the computer, e.g. Code page 437. The non-ASCII parts of these are incompatible with the Unicode or Windows character sets otherwise used in Windows so care needs to be taken. Non-English file names work only if entered through a DOS character set compatible editor. File names with characters outside this set do not work in batch files.
To get output in Unicode into file pipes from an internal command such as codice_40, one can use the codice_41 command. For example, codice_42 creates a file containing a directory listing with correct Windows characters, in the UTF-16LE encoding.
Batch viruses and malware.
As with any other programming language, batch files can be used maliciously. Simple trojans and fork bombs are easily created, and batch files can do a form of DNS poisoning by modifying the hosts file. Batch viruses are possible, and can also spread themselves via USB flash drives by using Windows' Autorun capability.
The following command in a batch file will delete all the data in the current directory (folder) - without first asking for confirmation:
del /Q *.*
These three commands are a simple fork bomb that will continually replicate itself to deplete available system resources, slowing down or crashing the system:
 start "" %0
 goto TOP
Other Windows scripting languages.
The cmd.exe command processor that interprets .cmd files is supported in all 32- and 64-bit versions of Windows . COMMAND.EXE, which interprets .BAT files, was supported in all 16- and 32-bit versions up to at least Windows 10.
There are other, later and more powerful, scripting languages available for Windows. However, these require the scripting language interpreter to be installed before they can be used:
Script files run if the filename without extension is entered. There are rules of precedence governing interpretation of, say, codice_43 if codice_44, codice_45, codice_46, codice_47, etc. exist; by default codice_44 has highest priority. This default order may be modified in newer operating systems by the user-settable PATHEXT environment variable.


List of VIA Nano microprocessors

The Nano microprocessor from VIA Technologies is an eighth-generation CPU targeted at the consumer and embedded market.


DOSSTART.BAT


DOSSHELL.EXE


IPhone OS 2

iPhone OS 2 is the second major release of the iOS mobile operating system developed by Apple Inc., being the successor to iPhone OS 1. It was the first release of iOS to support third-party applications via the App Store. iPhone OS 2.2.1 was the final version of iPhone OS 2. It was succeeded by iPhone OS 3 on June 17, 2009.
iPhone OS 2.0 became available on July 11, 2008 with the release of the iPhone 3G. Devices running iPhone OS 1 are upgradable to this version. This version of iOS introduces the App Store, making third-party applications available to the iPhone and iPod Touch. Prior to the public release of iPhone OS 2.0, Apple held a keynote event to announce the iPhone OS Software Development Kit ("SDK") to developers. Originally it was called 1.2.
History.
iPhone OS 2 was introduced at the Apple Worldwide Developers Conference keynote address on June 9, 2008.<br>
iPhone OS 2.0 was released on July 11, 2008. It was released along with the iPhone 3G, and ran on the first-generation iPhone as well.
Features.
App Store.
The most notable feature of iPhone OS 2 was the App Store. Before this feature was introduced, the only way to install custom applications on the device was via jailbreaking, which is strongly discouraged and unsupported by Apple. There were 500 applications available for download at the launch of the App Store, though this amount has grown dramatically since then. Now, the App Store has more than 2 million apps as of 2016.
Mail.
The Mail app had a makeover, having push-emails that provide an always-on capability. It also supports Microsoft Office attachments, as well as iWork attachments. Other new features including support for BCC, multiple email delete, and the ability to select an outgoing email.
Contacts.
The Contacts app now has a new home screen icon that is only available on iPod Touch. Along with the release is the ability to search contacts without being searched one-by-one, as well as SIM contacts import ability.
Maps.
New features were added to the Maps app in the iPhone OS 2.2 software update. Among the features added are the inclusion of Google Street View, directions to public transit and while walking, and the ability to display the address of a dropped pin.
Calculator.
When the device is in landscape mode, the calculator app displays a scientific calculator. Also, the app icon is updated.
Settings.
Settings now had an ability to turn Wifi back on while in Airplane mode, as well as the ability to turn on/off the Location Services within the app.
Reception.
Rene Ritchie at "iMore" said, "Overall, iPhone Firmware 2.0 is a stunning achievement that really puts the iPhone on par with the Apple II and Mac as one of the great revolutions in modern technology. It takes it beyond simple Phone + iPod, or even smartphone, and makes it the leading contender for the next great shift in computing." However, they criticized it for having stability issues and overall sluggishness. "Macworld" said, "The iPhone 2.0 software is full of the kind of refinements that you'd expect from a second-generation Apple product. The iPhone OS still isn't perfect, and we wish Apple has addressed some lingering shortcomings, but it's a welcome step-up for what was already arguably the best mobile platform on the market."
iPod Touch price.
iPhone OS 2 cost $9.95 for iPod Touch users; it was free for iPhone users.


Loadable kernel module

In computing, a loadable kernel module (LKM) is an object file that contains code to extend the running kernel, or so-called "base kernel", of an operating system. LKMs are typically used to add support for new hardware (as device drivers) and/or filesystems, or for adding system calls. When the functionality provided by an LKM is no longer required, it can be unloaded in order to free memory and other resources.
Most current Unix-like systems and Microsoft Windows support loadable kernel modules under different names, such as kernel loadable module (kld) in FreeBSD, kernel extension (kext) in macOS (now deprecated), kernel extension module in AIX, kernel-mode driver in Windows NT and downloadable kernel module (DKM) in VxWorks. They are also known as kernel loadable modules (or KLM), and simply as kernel modules (KMOD).
Advantages.
Without loadable kernel modules, an operating system would have to include all possible anticipated functionality compiled directly into the base kernel. Much of that functionality would reside in memory without being used, wasting memory, and would require that users rebuild and reboot the base kernel every time they require new functionality.
Disadvantages.
One minor criticism of preferring a modular kernel over a static kernel is the so-called "fragmentation penalty". The base kernel is always unpacked into real contiguous memory by its setup routines; thus, the base kernel code is never fragmented. Once the system is in a state in which modules may be inserted, for example once the filesystems have been mounted that contain the modules, it is likely that any new kernel code insertion will cause the kernel to become fragmented, thereby introducing a minor performance penalty by using more TLB entries, causing more TLB misses.
Implementations in different operating systems.
Linux.
Loadable kernel modules in Linux are loaded (and unloaded) by the modprobe command. They are located in /lib/modules and have had the extension .ko ("kernel object") since version 2.6 (previous versions used the .o extension). The lsmod command lists the loaded kernel modules. In emergency cases, when the system fails to boot due to e.g. broken modules, specific modules can be enabled or disabled by modifying the kernel boot parameters list (for example, if using GRUB, by pressing 'e' in the GRUB start menu, then editing the kernel parameter line).
License issues.
In the opinion of Linux maintainers, LKM are derived works of the kernel. The Linux maintainers tolerate the distribution of proprietary modules, but allow symbols to be marked as only available to GNU General Public License (GPL) modules.
Loading a proprietary or non-GPL-compatible module will set a 'taint' flag in the running kernel—meaning that any problems or bugs experienced will be less likely to be investigated by the maintainers. LKMs effectively become part of the running kernel, so can corrupt kernel data structures and produce bugs that may not be able to be investigated if the module is indeed proprietary.
Linuxant controversy.
In 2004, Linuxant, a consulting company that releases proprietary device drivers as loadable kernel modules, attempted to abuse a null terminator in their codice_1, as visible in the following code excerpt:
MODULE_LICENSE("GPL\0for files in the \"GPL\" directory; for others, only LICENSE file applies");
The string comparison code used by the kernel at the time tried to determine whether the module was GPLed stopped when it reached a null character (\0), so it was fooled into thinking that the module was declaring its license to be just "GPL".
FreeBSD.
Kernel modules for FreeBSD are stored within /boot/kernel/ for modules distributed with the operating system, or usually /boot/modules/ for modules installed from FreeBSD ports or FreeBSD packages, or for proprietary or otherwise binary-only modules. FreeBSD kernel modules usually have the extension .ko. Once the machine has booted, they may be loaded with the kldload command, unloaded with kldunload, and listed with kldstat. Modules can also be loaded from the loader before the kernel starts, either automatically (through /boot/loader.conf) or by hand.
macOS.
Some loadable kernel modules in macOS can be loaded automatically. Loadable kernel modules can also be loaded by the kextload command. They can be listed by the kextstat command. Loadable kernel modules are located in bundles with the extension .kext. Modules supplied with the operating system are stored in the /System/Library/Extensions directory; modules supplied by third parties are in various other directories.
NetWare.
A NetWare kernel module is referred to as a NetWare Loadable Module (NLM). NLMs are inserted into the NetWare kernel by means of the LOAD command, and removed by means of the UNLOAD command; the modules command lists currently loaded kernel modules. NLMs may reside in any valid search path assigned on the NetWare server, and they have .NLM as the file name extension.
VxWorks.
A downloadable kernel module (DKM) type project can be created to generate a ".out" file which can then be loaded to kernel space using "ld" command. This downloadable kernel module can be unloaded using "unld" command.
Solaris.
Solaris has a configurable kernel module load path, it defaults to /platform/platform-name/kernel /kernel /usr/kernel. Most kernel modules live in subdirectories under /kernel; those not considered necessary to boot the system to the point that init can start are often (but not always) found in /usr/kernel. When running a DEBUG kernel build the system actively attempts to unload modules.
Binary compatibility.
Linux does not provide a stable API or ABI for kernel modules. This means that there are differences in internal structure and function between different kernel versions, which can cause compatibility problems. In an attempt to combat those problems, symbol versioning data is placed within the .modinfo section of loadable ELF modules. This versioning information can be compared with that of the running kernel before loading a module; if the versions are incompatible, the module will not be loaded.
Other operating systems, such as Solaris, FreeBSD, macOS, and Windows keep the kernel API and ABI relatively stable, thus avoiding this problem. For example, FreeBSD kernel modules compiled against kernel version 6.0 will work without recompilation on any other FreeBSD 6.x version, e.g. 6.4. However, they are not compatible with other major versions and must be recompiled for use with FreeBSD 7.x, as API and ABI compatibility is maintained only within a branch.
Security.
While loadable kernel modules are a convenient method of modifying the running kernel, this can be abused by attackers on a compromised system to prevent detection of their processes or files, allowing them to maintain control over the system. Many rootkits make use of LKMs in this way. Note that on most operating systems modules do not help privilege elevation in any way, as elevated privilege is required to load a LKM; they merely make it easier for the attacker to hide the break-in.
Linux.
Linux allows disabling module loading via sysctl option codice_2. An initramfs system may load specific modules needed for a machine at boot and then disable module loading. This makes the security very similar to a monolithic kernel. If an attacker can change the initramfs, they can change the kernel binary.
macOS.
In OS X Yosemite and later releases, a kernel extension has to be code-signed with a developer certificate that holds a particular "entitlement" for this. Such a developer certificate is only provided by Apple on request and not automatically given to Apple Developer members. This feature, called "kext signing", is enabled by default and it instructs the kernel to stop booting if unsigned kernel extensions are present. In El Capitan and later releases, it is part of System Integrity Protection.
In older versions of macOS, or if kext signing is disabled, a loadable kernel module in a kernel extension bundle can be loaded by non-root users if the OSBundleAllowUserLoad property is set to True in the bundle's property list. However, if any of the files in the bundle, including the executable code file, are not owned by root and group wheel, or are writable by the group or "other", the attempt to load the kernel loadable module will fail.
Solaris.
Kernel modules can optionally have a cryptographic signature ELF section which is verified on load depending on the Verified Boot policy settings. The kernel can enforce that modules are cryptographically signed by a set of trusted certificates; the list of trusted certificates is held outside of the OS in the ILOM on some SPARC based platforms. Userspace initiated kernel module loading is only possible from the Trusted Path when the system is running with the Immutable Global Zone feature enabled.


Sega Zone (console)

The Sega Zone, also known as Sega Reactor is a dedicated video game console released under license from Sega (through AtGames) in summer 2010. It has 20 built-in classic games from the Mega Drive/Genesis library. Of these 20 games, 16 of them have motion-control enabled. When released, it cost £49 in the UK.


Nokia E6

The Nokia E6-00 is a smartphone running the Symbian^3 operating system. It supersedes the Nokia E72 as the new Symbian business mobility solution from Nokia following its announcement on 12 April 2011 (same day as Nokia X7-00). It shipped with the new "Symbian Anna" version of Symbian^3, and originally retailed for 340 euros before taxes.
The smartphone is notable for its backlit 4-rows QWERTY keyboard and touch screen input methods, for its long battery life (Talktime : 7.5 to 14.8 h and Standby : 28 to 31 days), the out-of-the-box access to Microsoft Exchange ActiveSync, Microsoft Communicator Mobile and Microsoft SharePoint and the high pixel density of its VGA display (326ppi).
Like its predecessors (Nokia E71/E72), the Nokia E6-00 integrates a stainless steel and glass design. The back removable cover, the raised panel for the back camera, dual LED flash and loud speaker and the contour of the front are made of stainless steel. The front of the phone (except for the QWERTY keyboard, short cut buttons and Navikey) is covered with Corning Gorilla Glass. Its casing has three color options (black, silver and white).
The E6 would also be the last Symbian-based device with a QWERTY keyboard, as the later QWERTY devices would be Series 40 from the Asha line. The Nokia Asha 302 from 2012 bears strong design similarities to the E6.
In October 2012, Vertu released the Constellation Quest Blue, based on the E6.
History and availability.
The predecessor of the E6-00 in the Eseries, consisting of business-oriented smartphones, was the Nokia E72 which shipped in November 2009. As with the E71, the E72 received mostly praises from the press. It is worth noting that Nokia released the E7, a landscape QWERTY slider smartphone in the Eseries based on Symbian^3, that shipped in February 2011.
The first hints that the Nokia E6-00 was being developed came, in early January 2011, from a Nokia XML and pictures from a Picasa album with pictures taken with the device. Various information could be retrieved from the XML such as the 8 MP camera, VGA display and QWERTY keyboard. The device was not officially announced at the Mobile World Congress held in Barcelona (14–17 February 2011). Various pictures and videos of the Nokia E6-00 leaked during the months of February and March.
It was officially announced at a special event, named Discover Symbian, on 12 April 2011 along with the Nokia X7 and the latest update of Symbian software. It was expected to be released in Q2 2011 in Europe at a price of €340 (before taxes and subsidies) and in Q3 2011 in North America.
In May 2011, the Nokia E6 became available at the Nokia Deutschland online shop for preorder at the price of €429.
Hardware.
Processors.
The Nokia E6-00 is powered by the same processor found in other contemporary Symbian devices such as the Nokia N8 , E7 and C7 , Nokia e series which is an ARM11 clocked at 680 MHz with a Broadcom BCM2727 GPU which supports OpenVG1.1 and OpenGL ES 2.0 support.
Screen and input.
The Nokia E6-00 has a 62.5 mm (diagonally) capacitive touchscreen with a resolution of 640 × 480 pixel (VGA, 326 ppi). According to Nokia, it is capable of displaying up to 16.7M colours. This pixel density was the highest among the smartphones launched at the time until the launch of Nokia Lumia 920. The screen brightness of the E6-00 is "more than double the brightness of the E72" when measured in candelas. There is a proximity sensor which deactivates the display and touchscreen when the device is brought near the face during a call. The Nokia E6 also understands PictBridge protocol so it's possible to directly print from the phone to a printer without using a computer to handle the data transfer in between.
The optical Navi key of the E72 has been replaced by a Navi key on the E6-00. It has also an ambient light sensor that adjusts the display brightness and activates the backlit of the 4-row keyboard. A 3-axis accelerometer is present but will not switch the display to portrait mode when the device is turned sideways. It will, however, take pictures in portrait and show them the right way in the photo gallery.
The device has an autonomous GPS with optional A-GPS functionality, Wi-Fi network positioning and Cell-ID and comes pre-loaded with the Ovi Maps application. Ovi Maps for Symbian^3 provides: free lifetime, turn by turn, voice guided car and pedestrian navigation. If the map is already downloaded to the device, Ovi Maps does not require an active data connection and can work as a stand-alone GPS navigator. For other services, for example Google Maps, a data connection is required.
The 8-megapixel (3264 × 2448 px) back camera has an extended depth of field feature (no autofocus), dual LED flash, 2X digital zoom (3X in video mode) and offers high definition (720p, 16:9 aspect ratio) video recording at 25 frame/s or 4:3 aspect ratio. The 0.3-megapixel front camera is capable of video recording (176 × 144 px at 15 frame/s) for video calling.
The Nokia E6 has a loudspeaker and two microphones. The microphone at the front of the device collects voices of the user, another microphone at the back of the device collects environmental noise for active noise cancellation, which makes user's voice in noisy environment sound clearer to the person at the other end of the line. Noise cancellation is not available when using the loudspeaker or a headset.
Buttons.
On the front of the device, there is a QWERTY keyboard, call creation and call termination keys, home (menu), calendar, contact and email shortcut keys with short and long press features and a 5-way Scrolling (Navi key). On the top there is the power/lock button, on the right hand side there is the lock/unlock slider, which also turn on the torch (dual LED flash of the camera). Above that button, there are three keys: (1) volume down, (2) volume up and (3) a middle key for activating the voice commands (long press) and the voice recorder (short press). When the device is locked, pressing the Navi will also bring up a menu which allow to unlock the Nokia E6-00 from the touch screen.
The QWERTY keyboard comes in a variety (24) language versions, including Arabic, Thai, Russian and Chinese.
Audio and output.
The E6-00 has a microphone and a loudspeaker located on the back of the device. There is a 3.5 mm four-contact audio jack which simultaneously provides stereo audio output and either microphone input or video output. PAL and NTSC TV out is possible using a Nokia Video Connectivity Cable (not included upon purchase) or a standard 3.5 mm audio jack to RCA cable.
There is a High-Speed USB 2.0 USB Micro-B connector provided for data synchronization, mass storage mode (client) and battery charging. The Nokia E6-00 supports for USB On-The-Go 1.3 (the ability to act as a USB host) using a Nokia Adapter Cable for USB OTG CA-157 (not included upon purchase).
The built-in Bluetooth v3 supports wireless earpieces and headphones through the HSP profile. The Nokia E6-00 is also capable of stereo audio output with the A2DP profile. Built-in car hands-free kits are also supported with the HFP profile. File transfer is supported (FTP) along with the OPP profile for sending/receiving objects. It is possible to remote control the device with the AVRCP profile. The DUN profile which permits access to the Internet from a laptop by dialing up on a mobile phone wirelessly (tethering). Other profiles are also supported (BIP, GAP, GAVDP, GOEP, HSP, PBAP, SAP, SDP and SPP). The device has an 87.5-108 MHz (76-90 MHz in Japan) FM receiver with RDS support. It has Wi-Fi b/g/n connectivity (single band) with support for WEP, WPA and WPA2 (AES/TKIP) security protocols.
Battery and SIM.
The BP-4L 1500 mAh Li-Ion battery performance, as provided by Nokia, are up to 14.8h of talk time, 681h standby, 9h of video playback, 4.7h of video recording and up to 75h of music play back.
Storage.
The Nokia E6-00 has 8 GB of internal storage, which can be expanded with a microSDHC card up to 32 GB in size There is 1 GB of ROM, of which 350 MB is available to the user to install applications.
Criticism and issues.
Notification LED visibility.
Some new users of the Nokia E6 have experienced problems with the notification LED which has been placed under the D-pad navigation key, as in previous models (E71, E72). However, it is apparent that Nokia has not allowed sufficient space between the D-pad key and the front face for the light to be visible. Nokia have acknowledged the problem but have not indicated whether a fix is possible in software by adjusting the brightness of the component.
There is one solution that was done by Aniket Patil (aniketroxx), it was to redirect the notification light to Red Mute key, which was used by many people as alternative to D-Pad Fix. That solution also helped user to see light without opening E6 from cover.
A revised Nokia E6 which has a hardware change to resolve the notification light issue started shipping on 22 October 2011.
Vibration alert not strong enough.
Many users of the Nokia E6 reported that the vibration alert is not strong enough.
Software.
Symbian^3 "Anna".
Along with the Nokia X7, the E6-00 shipped with the updated Symbian^3 software user experience. This update, nicknamed "Anna", offers, amongst others:
Preinstalled applications on the Nokia E6-00 include JoikuSpot Premium (mobile WiFi hotspot), World Traveler, F-secure Mobile Security and QuickOffice.
Nokia Belle.
The stock OS version Symbian Anna was specially adapted to E6. The February 2012 Nokia Belle update was heavily criticised for its failure to meet special demands of E6 which had been met by the original stock firmware. In August 2012, Nokia Belle Refresh was made available.
Compatibility.
Due to its VGA (640 × 480) resolution, compared to the nHD (640 × 360) of the other Symbian^3 devices, some application may be incompatible with the E6-00 if they are designed for nHD display. For example, Nokia guidelines stipulate that the user interface elements of the touch screen (accept button, virtual numpad, etc. ...) should be at least 7mm × 7mm. The high pixel density of the Nokia E6-00 means that the elements will need to be proportionately larger in pixels.
Compared to other recent Symbian^3 devices, the Nokia E6-00 has two extra homescreens bringing the total to 5 homescreens. This is to give users the same opportunity for customization as other devices with smaller displays accommodating 3 widgets per homescreen.
The Nokia E6 has WiFi coverage of the full spectrum of channels 1–13 in the crowded 2.4 GHz waveband (compared to just channels 1–11 on the E63 for example). It does not support the newer 5 GHz WiFi frequencies.
See also.
Charging LED workaround for notifications


Extent File System

Extent File System (EFS) is an older extent-based file system used in IRIX releases prior to version 5.3. It has been superseded by XFS.


Coates (supercomputer)

Coates is a supercomputer installed at Purdue University on July 21, 2009. The high-performance computing cluster is operated by Information Technology at Purdue (ITaP), the university's central information technology organization. ITaP also operates clusters named Steele built in 2008, Rossmann built in 2010, and Hansen and Carter built in 2011. Coates was the largest campus supercomputer in the Big Ten outside a national center when built. It was the first native 10 Gigabit Ethernet (10GigE) cluster to be ranked in the TOP500 and placed 102nd on the June 2010 list.
Hardware.
The Coates cluster consists of 982 64-bit, 8-core HP Proliant DL165 G5p and 11 64-bit, 16-core HP Proliant DL585 G5 systems using AMD 2380 and AMD 8380 processors with various combinations of 16-128 gigabytes of RAM, 500 GB to 2 terabytes of disk and 10 Gigabit Ethernet (10GigE) local to each node. Coates uses Cisco and Chelsio network equipment. The cluster's nodes are arrayed in five logical sub-clusters each with different memory and storage configurations designed to meet the varying needs of the researchers using Coates.
Software.
Coates nodes run Red Hat Enterprise Linux 5.6 (RHEL5.6) and use Portable Batch System Professional 10.4.6 (PBSPro 10.4.6) for resource and job management. The cluster also has compilers and scientific programming libraries installed.
Cooling system.
Coates has a heat-exchanging cooling system that recycles the hot water for use on the Purdue campus.
Construction.
Coates was largely built in less than four hours on July 21, 2009, by a team of more than 200 Purdue computer technicians and volunteers, including volunteers from Indiana University, the University of Iowa, the University of Michigan and Michigan State University. It was the second such "high-tech barn raising" hosted by Purdue to assemble a cluster in a single morning. The process was first used for the Steele cluster in 2008.
Funding.
The Coates supercomputer and Purdue's other clusters are part of the Purdue Community Cluster Program, a partnership between ITaP and Purdue faculty. In Purdue's program, a "community" cluster is funded by hardware money from grants, faculty startup packages, institutional funds and other sources. ITaP's Rosen Center for Advanced Computing administers the community clusters and provides user support. Each faculty partner always has ready access to the capacity he or she purchases and potentially to more computing power when the nodes of other investors are idle.
Users.
The Purdue departments and schools by which Coates is used vary broadly, including Aeronautics and Astronautics, Agronomy, Biology, Chemical Engineering, Chemistry, Civil Engineering, Communications, Computer Science, Earth and Atmospheric Sciences, Electrical and Computer Engineering, Electrical and Computer Engineering Technology, Industrial Engineering, Mechanical Engineering, Medicinal Chemistry and Molecular Pharmacology, Physics, the Purdue Terrestrial Observatory and Statistics.
DiaGrid.
Unused, or opportunistic, cycles from Coates are made available to the TeraGrid and the Open Science Grid using Condor software. Coates is part of Purdue's distributed computing Condor flock, which is the largest publicly disclosed distributed computing system in the world and the center of DiaGrid, a nearly 43,000-processor Condor-powered distributed computing network for research involving Purdue and partners at nine other campuses.
Naming.
The Coates cluster is named for Clarence L. "Ben" Coates, who came to Purdue in 1973 to head the School of Electrical Engineering (now Electrical and Computer Engineering) where, for the next decade, he emphasized computer education and the development of computing facilities. He was a driving force behind the high-performance computing and networking plan that led to the creation of the Engineering Computer Network (ECN) serving all of Purdue’s engineering schools. He also initiated a degree program in computer engineering at Purdue. As a research scientist at the General Electric Research Laboratory in New York, Coates developed five patents involving waveform recognition devices, circuit gates and accumulators on computer chips. The Coates cluster continues Purdue's practice of naming new supercomputers after notable figures in the university's computing history.


List of DOS system files

MS-DOS / PC DOS and some related disk operating systems use the files mentioned here.
System Files:
Command-line interpreter (Shell):
User configuration files:
Standard DOS utility programs:
Standard DOS device drivers:


Asterix and the Great Rescue

Asterix and the Great Rescue is a video game released by Sega for the Genesis/Mega Drive in 1993 and for the Game Gear and Master System in 1994.
Plot.
This game is based on the long-running, French comic book series "Asterix the Gaul". The characters Asterix and Obelix must rescue Getafix (Panoramix) and Dogmatix (Idéfix) from the Romans, who are in the process of taking over Gaul.
Gameplay.
It is a side-scrolling platform game. The startup screen offers a choice of difficulty level, as well as the ability to turn off the music and/or sound effects. The Master System and Game Gear versions allows changing characters during a level, whereas the Mega Drive/Genesis version removes this feature in favor of allowing choosing characters at the start of a level.
Reception.
Reviewing the Genesis version, "GamePro" criticized the steep difficulty slope and poor controls, elaborating that "it's annoyingly easy to mix up the button for "swapping" special weapons with the button for "using" the special weapons. Even worse, the hard-to-control jumps become ... a big frustration when you need to jump precisely, but can't."[emphases in original] They nonetheless recommended the game to players who like tough puzzles.
Mean Machines gave a positive review of the Master System version which was described as "particularly entertaining" and "compulsive". The graphics were praised including the characters' resemblance to the original comic versions. The game was found to be lacking originality as it was so similar to previous titles featuring Disney characters, and sometimes frustrating but was judged to be "a great game".
The four reviewers of "Electronic Gaming Monthly" gave the Game Gear version a 5 out of 10, remarking that the graphics are well done the sounds are "a nuisance", and that the controls make the game excessively frustrating. "GamePro" similarly wrote that the Game Gear version's graphics and animation are good but that controlling the character is extremely difficult.


RDOFF