A filename extension, file extension or file type is an identifier specified as a suffix to the name of a computer file. The extension indicates a characteristic of the file contents or its intended use. A filename extension is typically delimited from the filename with a full stop (period), but in some systems[1] it is separated with spaces.
Simple to use, and extremely useful - DMG File Extractor can open any DMG file created on an Apple Mac and extract the files content to Windows compatible file formats. Opens all Apple DMG file. The DMG Extractor can open a wide variety of Disk Image files and encrypted.dmg files as used on OS X, without having to first convert them to ISO or IMG files. Question: Q: DMG files and Windows XP I have an ipod touch and have installed the software. I notice I have some.dmg files in a folder called C: Documents and Settings All Users Application Data Apple Computer iTunes iPod Temporary Files.dmg. DMG Backup Extractor allows Windows users to open Apple Mac.DMG disc image files and extract the files within to their Windows PC. Simple to use, and extremely useful - DMG File Extractor can. Come aprire file DMG su Mac; Come aprire file DMG su Windows. Se utilizzi un PC Windows e vuoi sapere come aprire file DMG, eccoti alcune applicazioni che dovrebbero fare al caso tuo. 7-Zip (gratis) Forse non tutti lo sanno, ma 7-Zip, la famosissima alternativa gratuita a WinRAR, permette di aprire i file DMG in maniera semplicissima.
Some file systems implement filename extensions as a feature of the file system itself and may limit the length and format of the extension, while others treat filename extensions as part of the filename without special distinction.
Usage[edit]
Filename extensions may be considered a type of metadata.[2] They are commonly used to imply information about the way data might be stored in the file. The exact definition, giving the criteria for deciding what part of the file name is its extension, belongs to the rules of the specific filesystem used; usually the extension is the substring which follows the last occurrence, if any, of the dot character (example:txt is the extension of the filename readme.txt, and html the extension of mysite.index.html).On file systems of some mainframe systems such as CMS in VM, VMS, and of PC systems such as CP/M and derivative systems such as MS-DOS, the extension is a separate namespace from the filename. Under Microsoft's DOS and Windows, extensions such as EXE, COM or BAT indicate that a file is a program executable. In OS/360 and successors, the part of the dataset name following the last period is treated as an extension by some software, e.g., TSO EDIT, but it has no special significance to the operating system itself; the same applies to Unix files in MVS.
Filesystems for UNIX-like operating systems do not separate the extension metadata from the rest of the file name. The dot character is just another character in the main filename. A file name can have no extensions, a single extension, or more than one extension. More than one extension usually represents nested transformations, such as files.tar.gz (the .tar indicates that the file is a tar archive of one or more files, and the .gz indicates that the tar archive file is compressed with gzip). Programs transforming or creating files may add the appropriate extension to names inferred from input file names (unless explicitly given an output file name), but programs reading files usually ignore the information; it is mostly intended for the human user. It is more common, especially in binary files, for the file itself to contain internal metadata describing its contents.This model generally requires the full filename to be provided in commands, whereas the metadata approach often allows the extension to be omitted.
The VFAT, NTFS, and ReFS file systems for Windows also do not separate the extension metadata from the rest of the file name, and allow multiple extensions.
With the advent of graphical user interfaces, the issue of file management and interface behavior arose. Microsoft Windows allowed multiple applications to be associated with a given extension, and different actions were available for selecting the required application, such as a context menu offering a choice between viewing, editing or printing the file. The assumption was still that any extension represented a single file type; there was an unambiguous mapping between extension and icon.
The classic Mac OS disposed of filename-based extension metadata entirely; it used, instead, a distinct file type code to identify the file format. Additionally, a creator code was specified to determine which application would be launched when the file's icon was double-clicked. macOS, however, uses filename suffixes, as well as type and creator codes, as a consequence of being derived from the UNIX-like NeXTSTEP operating system.
Improvements[edit]
The filename extension was originally used to determine the file's generic type.[citation needed] The need to condense a file's type into three characters frequently led to abbreviated extensions. Examples include using .GFX for graphics files, .TXT for plain text, and .MUS for music. However, because many different software programs have been made that all handle these data types (and others) in a variety of ways, filename extensions started to become closely associated with certain products—even specific product versions. For example, early WordStar files used .WS or .WSn, where n was the program's version number. Also, conflicting uses of some filename extensions developed. One example is .rpm, used for both RPM Package Manager packages and RealPlayer Media files;.[3] Others are .qif, shared by DESQview fonts, Quicken financial ledgers, and QuickTime pictures;[4].gba, shared by GrabIt scripts and Game Boy Advance ROM images;[5].sb, used for SmallBasic and Scratch; and .dts, being used for Dynamix Three Space and DTS.
Some other operating systems that used filename extensions generally had much more liberal sizes for filenames. Many allowed full filename lengths of 14 or more characters, and maximum name lengths up to 255 were not uncommon. The file systems in operating systems such as Multics and UNIX stored the file name as a single string, not split into base name and extension components, with the '.' is just another character allowed in file names. Such systems generally allow for variable-length filenames, permitting more than one dot, and hence multiple suffixes. Some components of Multics and UNIX, and applications running on them, used suffixes, in some cases, to indicate file types, but they did not use them as much—for example, executables and ordinary text files had no suffixes in their names.
The High Performance File System (HPFS), used in Microsoft and IBM's OS/2 also supported long file names and did not divide the file name into a name and an extension. The convention of using suffixes continued, even though HPFS supported extended attributes for files, allowing a file's type to be stored in the file as an extended attribute.
Microsoft's Windows NT's native file system, NTFS, supported long file names and did not divide the file name into a name and an extension, but again, the convention of using suffixes to simulate extensions continued, for compatibility with existing versions of Windows.
When the Internet age first arrived, those using Windows systems that were still restricted to 8.3 filename formats had to create web pages with names ending in .HTM, while those using Macintosh or UNIX computers could use the recommended .html filename extension. This also became a problem for programmers experimenting with the Java programming language, since it requiressource code files to have the four-letter suffix .java and compilesobject code output files with the five-letter .class suffix.[6]
Eventually, Windows 95 introduced support for long file names, and removed the 8.3 name/extension split in file names from non-NT Windows, in an extended version of the commonly used FATfile system called VFAT. VFAT first appeared in Windows NT 3.5 and Windows 95. The internal implementation of long file names in VFAT is largely considered to be a kludge[by whom?], but it removed the important length restriction and allowed files to have a mix of upper case and lower case letters, on machines that would not run Windows NT well. However, the use of three-character extensions under Microsoft Windows has continued, originally for backward compatibility with older versions of Windows and now by habit, along with the problems it creates.
Command name issues[edit]
The use of a filename extension in a command name appears occasionally, usually as a side effect of the command having been implemented as a script, e.g., for the Bourne shell or for Python, and the interpreter name being suffixed to the command name, a practice common on systems that rely on associations between filename extension and interpreter, but sharply deprecated[7] in UNIX-derived systems like Linux and Apple's macOS, where the interpreter is normally specified as a header in the script ('shebang').
On association-based systems, the filename extension is generally mapped to a single, system-wide selection of interpreter for that extension (such as '.py' meaning to use Python), and the command itself is runnable from the command line even if the extension is omitted (assuming appropriate setup is done). If the implementation language is changed, the command name extension is changed as well, and the OS provides a consistent API by allowing the same extension-less version of the command to be used in both cases. This method suffers somewhat from the essentially global nature of the association mapping, as well as from developers' incomplete avoidance of extensions when calling programs, and that developers can't force that avoidance. Windows is the only remaining widespread employer of this mechanism.
On systems with interpreter directives, including virtually all versions of Unix, command name extensions have no special significance, and are by standard practice not used, since the primary method to set interpreters for scripts is to start them with a single line specifying the interpreter to use (which could be viewed as a degenerate resource fork). In these environments, including the extension in a command name unnecessarily exposes an implementation detail which puts all references to the commands from other programs at future risk if the implementation changes. For example, it would be perfectly normal for a shell script to be reimplemented in Python or Ruby, and later in C or C++, all of which would change the name of the command were extensions used. Without extensions, a program always has the same extension-less name, with only the interpreter directive and/or magic number changing, and references to the program from other programs remain valid.
Security issues[edit]
The default behavior of File Explorer, the file browser provided with Microsoft Windows, is for filename extensions to not be displayed. Malicious users have tried to spread computer viruses and computer worms by using file names formed like LOVE-LETTER-FOR-YOU.TXT.vbs. The hope is that this will appear as LOVE-LETTER-FOR-YOU.TXT, a harmless text file, without alerting the user to the fact that it is a harmful computer program, in this case, written in VBScript. Default behavior for ReactOS is to display filename extensions in ReactOS Explorer.
Later Windows versions (starting with Windows XPService Pack 2 and Windows Server 2003) included customizable lists of filename extensions that should be considered 'dangerous' in certain 'zones' of operation, such as when downloaded from the web or received as an e-mail attachment. Modern antivirus software systems also help to defend users against such attempted attacks where possible.
Some viruses take advantage of the similarity between the '.com' top-level domain and the '.COM' filename extension by emailing malicious, executable command-file attachments under names superficially similar to URLs (e.g., 'myparty.yahoo.com'), with the effect that some naive users click on email-embedded links that they think lead to websites but actually download and execute the malicious attachments.
There have been instances of malware crafted to exploit vulnerabilities in some Windows applications which could cause a stack-based buffer overflow when opening a file with an overly long, unhandled filename extension.
The filename extension is just a marker and the content of the file does not have to match it.[8] This can be used to disguise malicious content. When trying to identify a file for security reasons, it is therefore considered dangerous to rely on the extension alone and a proper analysis of the content of the file is preferred. For example, on UNIX derived systems, it is not uncommon to find files with no extensions at all, as commands such as file (command) are meant to be used instead, and will read the file's header to determine its content.
Alternatives[edit]
In many Internet protocols, such as HTTP and MIME email, the type of a bitstream is stated as the media type, or MIME type, of the stream, rather than a filename extension. This is given in a line of text preceding the stream, such as Content-type: text/plain.
There is no standard mapping between filename extensions and media types, resulting in possible mismatches in interpretation between authors, web servers, and client software when transferring files over the Internet. For instance, a content author may specify the extension svgz for a compressed Scalable Vector Graphics file, but a web server that does not recognize this extension may not send the proper content type application/svg+xml and its required compression header, leaving web browsers unable to correctly interpret and display the image.
BeOS, whose BFS file system supports extended attributes, would tag a file with its media type as an extended attribute. The KDE and GNOMEdesktop environments associate a media type with a file by examining both the filename suffix and the contents of the file, in the fashion of the file command, as a heuristic. They choose the application to launch when a file is opened based on that media type, reducing the dependency on filename extensions. macOS uses both filename extensions and media types, as well as file type codes, to select a Uniform Type Identifier by which to identify the file type internally.
See also[edit]
References[edit]
- ^'What Is a File?'. z/VM Version 7 Release 1 CMS Primer(PDF). IBM. 2018-09-11. p. 7. SC24-6265-00.
One thing you need to know about creating files with z/VM is that each file needs its own three-part identifier. The first part of the identifier is the file name. The second part is the file type. And the third part is the file mode. These three file identifiers are often abbreviated fn ft fm.
- ^Stauffer, Todd; McElhearn, Kirk (2006). Mastering Mac OS X. John Wiley & Sons. pp. 95–96. ISBN9780782151282. Retrieved 2 October 2017.
- ^File Extension .RPM Details from filext.com
- ^File Extension .QIF Details from filext.com
- ^File Extension .GBA Details from filext.com
- ^'javac – Java programming language compiler'. Sun Microsystems, Inc. 2004. Retrieved 2009-05-31.
Source code file names must have .java suffixes, class file names must have .class suffixes, and both source and class files must have root names that identify the class.
- ^Commandname Extensions Considered Harmful
- ^'What Is a File Extension?'.
External links[edit]
- Media related to Filename extensions at Wikimedia Commons
- Data Formats Filename extension at Curlie
People presume binary files to be a chain of bytes. However, they comprise the bytes designed for interpretation into something else contrary to text characters. Computer programs are great examples of these files. Note that bin files imply that the stored information could contain sounds, images and other versions of alternative files.
Related:
File Extension Dmg Windows Xp 10
To open them, you require a Bin File Opener. This application enables you to access CUE files because it interprets the data stored in the files.
MagicISO
This Bin extractor makes possible to open, extract and edit data in your bin files. You will love it because it is comparable to process ISO image files, this tool burns different BIN files into CD-RW/R. Furthermore, depending on your wishes, you can use it to convert your typical BIN files into regular ISO images.
PowerISO
Like many other BIN File openers, Power ISO allows you to access your binary files without hassle. It runs in both 32-bit and 64-bit Windows. You can also download it for Linux or OSX. It is perfect for configuring toolbar buttons and shell context menu. It features “DISM Tool” with enhanced support for DMG and WIM files.
Bandizip
This free and lightweight bin file extractor are worth using for commercial and personal purposes. It is fast in compressing, creating and extracting files. It supports several compression formats among them, ZIP, RAR, and 7Z. As a freeware, it operates in Windows XP, Vista and 7+. Then, it uses Unicode in order to display universal characters.
BIN File Extension
Among the best bin file openers to use, is Bin File Extension for Windows. It is unique than different types of binary files. You will appreciate it for compressing your Microsoft docs, PDFs, images, videos and audio files. You can also customize it to back up your data on a given schedule.
The Unarchiver for Mac
Every organization is interested in an application that will unarchive their multiple types of archive files. The Unarchiver for Mac is among the smallest and easiest to use software programs. It opens standard file formats such as ZIP, RAR, and Gzip. Interestingly, although it favors several encodings, it permits you to select the most appropriate one.
ISO Extractor for Android
Unlike most software products, ISO Extractor for android is compatible with all Android 2+ devices. You can use it to browse and extract files from unique CD image files. It converts selected images to ISO. Above all, it supports several file systems and formats including BIN, ZIP, NRG, MDF and CCD.
Most Popular Software – IZArc
There is no easier way to encrypt, zip and unzip binary files free of cost than using IZArc. Apart from opening CD- image files, this virus free software converts the different files from a given form to another. Interestingly, you can use it to self-archive large files and send them to your associates who lack archiving tools. You can also see DSK to ISO Converter Software
What is Bin File Opener?
You must have come across files that store information in binary form. The files e.g., Disk images are BIN files. You require them to run certain programs on your devices. They differ from text-based files because unlike the latter, BIN files cannot be edited manually. Nonetheless, you can use several programs to create them. It is for this reason that you require a bin file opener.
The opener is a software product that simplifies the ease of accessing binary files. Similarly, it enables you to edit, compress and convert your files to match your needs. Luckily, these applications are available freely and they work on all devices.
File Extension Dmg Free Download
You no longer have to worry about opening binary files. All you need is to download a bin file opener that is compatible with your device. Then, use it to access your stored data. Remember, it is possible to edit, convert and save your bin files in preferred formats after accessing them using this tool.