|
UUTool
UUTool was a freeware application written for the Apple Macintosh by Bernie Wieser. The purpose of UUTool was to uuencode and uudecode files, however, the application functionality grew to translate uLaw encoded files to AIFF format, segment large uuencoded files, and recombine multiple uuencoded files for decode. Technical details UUTool uuencoded files and attached the extension. However, UUTool was the first Macintosh program that encoded the data fork, resource fork, and finder information into one uuencoded file with the extension. The format for this was to catenate the three pieces of file information and uniquely name the resource fork and finder info as files. This allowed for some interoperability on non-Macintosh platforms. ''Example'' begin 0700 myfile ... end begin 0700 .rsrc ... end begin 0700 .finfo ... end Version history See also *uuencoding uuencoding is a form of binary-to-text encoding that originated in the Unix programs uuencode and uudecode writte ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Uuencoding
uuencoding is a form of binary-to-text encoding that originated in the Unix programs uuencode and uudecode written by Mary Ann Horton at UC Berkeley in 1980, for encoding binary data for transmission in email systems. The name "uuencoding" is derived from Unix-to-Unix Copy, i.e. "Unix-to-Unix encoding" is a safe encoding for the transfer of arbitrary files from one Unix system to another Unix system but without guarantee that the intervening links would all be Unix systems. Since an email message might be forwarded through or to computers with different character sets or through transports which are not 8-bit clean, or handled by programs that are not 8-bit clean, forwarding a binary file via email might cause it to be corrupted. By encoding such data into a character subset common to most character sets, the encoded form of such data files was unlikely to be "translated" or corrupted, and would thus arrive intact and unchanged at the destination. The program uudecode reverses the ef ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Μ-law Algorithm
The μ-law algorithm (sometimes written mu-law, often approximated as u-law) is a companding algorithm, primarily used in 8-bit PCM digital telecommunication systems in North America and Japan. It is one of two versions of the G.711 standard from ITU-T, the other version being the similar A-law. A-law is used in regions where digital telecommunication signals are carried on E-1 circuits, e.g. Europe. Companding algorithms reduce the dynamic range of an audio signal. In analog systems, this can increase the signal-to-noise ratio (SNR) achieved during transmission; in the digital domain, it can reduce the quantization error (hence increasing the signal-to-quantization-noise ratio). These SNR increases can be traded instead for reduced bandwidth for equivalent SNR. Algorithm types The μ-law algorithm may be described in an analog form and in a quantized digital form. Continuous For a given input , the equation for μ-law encoding is: : F(x) = \sgn(x) \dfrac, \quad -1 \ ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
AIFF
Audio Interchange File Format (AIFF) is an audio file format standard used for storing sound data for personal computers and other electronic audio devices. The format was developed by Apple Inc. in 1988 based on Electronic Arts' Interchange File Format (IFF, widely used on Amiga systems) and is most commonly used on Apple Macintosh computer systems. The audio data in most AIFF files is uncompressed pulse-code modulation (PCM). This type of AIFF file uses much more disk space than lossy formats like MP3—about 10 MB for one minute of stereo audio at a sample rate of 44.1 kHz and a bit depth of 16 bits. There is also a compressed variant of AIFF known as AIFF-C or AIFC, with various defined compression codecs. In addition to audio data, AIFF can include loop point data and the musical note of a sample, for use by hardware samplers and musical applications. The file extension for the standard AIFF format is .aiff or .aif. For the compressed variants it is supposed to be .aif ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Resource Fork
The resource fork is a fork (file system), fork or section of a computer file, file on Apple Inc., Apple's classic Mac OS operating system, which was also carried over to the modern macOS for compatibility, used to store structured data along with the unstructured data stored within the data fork. A resource fork stores information in a specific form, containing details such as icon bitmaps, the shapes of windows, definitions of menus and their contents, and application code (machine code). For example, a word processing file might store its text in the data fork, while storing any embedded images in the same file's resource fork. The resource fork is used mostly by executables, but every file is able to have a resource fork. The Macintosh file system Originally conceived and implemented by programmer Bruce Horn, the resource fork was used for three purposes with Hierarchical File System, Macintosh file system: * It was used to store all graphical data on disk until it was neede ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Fat Binary
A fat binary (or multiarchitecture binary) is a computer executable program or library which has been expanded (or "fattened") with code native to multiple instruction sets which can consequently be run on multiple processor types. This results in a file larger than a normal one-architecture binary file, thus the name. The usual method of implementation is to include a version of the machine code for each instruction set, preceded by a single entry point with code compatible with all operating systems, which executes a jump to the appropriate section. Alternative implementations store different executables in different forks, each with its own entry point that is directly used by the operating system. The use of fat binaries is not common in operating system software; there are several alternatives to solve the same problem, such as the use of an installer program to choose an architecture-specific binary at install time (such as with Android multiple APKs), selecting an archi ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
PowerPC
PowerPC (with the backronym Performance Optimization With Enhanced RISC – Performance Computing, sometimes abbreviated as PPC) is a reduced instruction set computer (RISC) instruction set architecture (ISA) created by the 1991 Apple Inc., Apple–IBM–Motorola alliance, known as AIM alliance, AIM. PowerPC, as an evolving instruction set, has been named Power ISA since 2006, while the old name lives on as a trademark for some implementations of Power Architecture–based processors. PowerPC was the cornerstone of AIM's PReP and Common Hardware Reference Platform (CHRP) initiatives in the 1990s. Originally intended for personal computers, the architecture is well known for being used by Apple's Power Macintosh, PowerBook, iMac, iBook, eMac, Mac Mini, and Xserve lines from 1994 until 2005, when Mac transition to Intel processors, Apple migrated to Intel's x86. It has since become a niche in personal computers, but remains popular for embedded system, embedded and high-performanc ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
BinHex
BinHex, originally short for "binary-to-hexadecimal", is a binary-to-text encoding system that was used on the classic Mac OS for sending binary files through e-mail. Originally a hexadecimal encoding, subsequent versions of BinHex are more similar to uuencode, but combined both "forks" of the Mac file system together along with extended file information. BinHexed files take up more space than the original files, but will not be corrupted by non-"8-bit clean" software. History TRS-80 BinHex (.hex) BinHex was originally written in 1981 by Tim Mann for the TRS-80, as a stand-alone version of an encoding scheme originally built into a popular terminal emulator, ST80-III by Lance Micklus. BinHex was used for sending files via major online services such as CompuServe, which were not "8-bit clean" and required ASCII armoring to survive. Not everyone used ST-80, however, so Mann wrote BinHex to allow users of other emulators to use the format. The original ST-80 system worked by con ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
