Q118335 states that Windows NT 3.51 supports 4GB FAT16 partitions. Q310561: Maximum size of FAT16 in Windows XP is 4GB arising from the use of 64KB clusters, citing that Windows 2K and NT 4.0 support this as well.
Windows 2000: Maximum Volume Sizes refers to compatibility issues with FAT16 partitions over 2GB. (This is actually referring to Microsoft Software, as noted in Q290705.)
Q314463 states that files that are 4GB or later won't work on a FAT32 partition.
Overview of cluster sizes with various operating systems (also covering FAT16 and NTFS).
Copy2GB has some operating system fixes for buggy handling of files over 2GB. MDGX ME Unofficial patches (search for "2-4 GB Files Errors KERNEL32.DLL") MDGX 98 Unofficial Patches (hyperlink goes elsewhere on same page, and same search string to be used), 2GB in Win2K
This has separate sub-sections for CD-based file systems and DVD-based file systems. There may be some overlap: For exampel the CD-based file system ISO 9660 may fairly commonly be used with DVD media, so check out multiple sections as appropriate.
This section is about software related to acting as a driver for CD-based file systems. For some related topics, such as lossless compression specific to ISO 9660 images, see archive-handling software: CD images area/archive-handling software: Optical disk images area for information about creating and otherwise manipulating such files. For working with DVDs in a method other than just using ISO 9660, see DVD file systems. For reading audio data from an optical disc, see the multimedia software page: section.
Common file system types:
These file system drivers need to know which CD Drive driver for DOS has been loaded. The way to determine the drive is to specify a name which is set by the CD Drive driver.
shsucd15.zip contains the SHSUCDX 1.4b executable as well as other programs (apparently designed to create and work with CD images).
This does not have a newer version of SHSUCDX than version 1.4b, but does contain a newer version of SHSUCDHD. SHSUCD14.ZIP contained an older SHSUCDHD 2.0 (as can be seen in the SHSUCDHD.ASM, SHSUCDHD.EXE, and README.CDH files, even though README.CD errorneously indicated the SHSUCDHD version was 4.0.)
Mounting an actual optical disc from a drive is rather straightforward and easy once one is familiar with how to mount other file system volumes, such as the ones storing information on a hard drive, and once the CD device is known. To check the name of the optical drive, try using:
ls -l /dev/*cd*
If that turns up only one result, that is
probably it. If it turns up many results, consider narrowing it down to:
ls -l /dev/cd*
If there are multiple /dev/cd* with different numbers (such as an OpenBSD default install continaing /dev/cd0a and /dev/cd0c and /dev/cd1a and /dev/cd1c) and only one optical drive, the desirable block device to use is probably one with the lowest number, a /dev/cd0? in the example given.
(In the above example, dev/cd0c is the desired device. Using the entry that ends with c is similar to how OpenBSD handles partitions on a hard drive, something one generally learns when installing OpenBSD and learning how to make a proper disklabel which other operating systems may refer to as a bsdlabel.)
If a /media or /mnt subdirectory exists and a *cd* subdirectory exists under one of those things, that is probably meant to be the mount point of a CD.
The mount command will need a -t parameter which is not consistant. If the optical disc uses UDF, try -t udf. If the optical disc uses ISO 9660 CDs, the parameter may be -t cd9660 or -t iso9660.
Specifying “-o ro” is generally unnecessary. Specifying “-o ro,unhide” is generally unnecesarry. One exception is the WoW:WotLK UDF DVD when used under Debian. However, using -o ro,unhide in other operating systems my not work (citing “unhide” as an unsupported, invalid option).
So, an example of all this may be:
mount -t udf /dev/*cd* /media/*cdrom*
echo Note that the above may need customizing.
Additionally, support is generally included in the operating system to be able to mount *.iso images. However, most operating systems which support this functionality will require an additional procedure, not just mounting a *.iso image directly. (I believe this might not have been true with some older versions of Linux.) The secondary procedure may involve creating a vnode device with a separate command (and then, to cleanly free up resources, un-creating that device after unmounting the drive), or an altered mount command. See: Mounting disk/disc images in Linux, Mounting disk/disc images in OpenBSD, and Mounting disk/disc images in FreeBSD.
Support for mounting images is built into standard Linux distributions. The syntax may be mkdir /mntpoint;mount -o loop -t iso9660 filename.iso /mntpoint
Note that some older operating systems and/or implementations of file systems may not be able to store files that are over 4GB. Archivers (and archive formats) may have limits, such as noted by the Info-ZIP documentation of zip 2.x zipfile specification's archive limits do reference 2GB and 4GB limits. Of course, numerous other file size limits may go into effect (like the 504/540MB barrier that some BIOS codebases inflict upon hard drives), but this is courteously mentioned since working with full-sized DVDs will exceed some of these limits that often don't affect other tasks.
DVDs most often store data in one of the following methods:
UDF is used by some removable media, included DVDs. Wikipedia's article on UDF says "Almost directly after the first version of UDF was released, it was adopted by the DVD Consortium as the official file system for DVD Video and DVD Audio. Nowadays, a UDF file system may be found on most authored optical discs in the market, and on almost all recordable DVD media that are used for video recording." UDF may be supported on more devices than ISO 9660. For any further details available here, see #udf section.
Many commercially made DVDs include some form of copy protection, preventing unauthorized accessing of the data. This prevents playback unless the data is decrypted, and so naturally they are meant to be decrypted in some fashion. That method is to use DVD Playback software. Some such software may mount the DVD file system in a way that provides access to the files in an unecrypted manner. Another possibility may be disk writing software, since such software may provide some sort of method of using such encryption. For any such details, check out the software area on writing CDs/DVDs. (Until a more specific hyperlink is available here, search the general CD software area.)
For software that provides access to unencrypted data without performing one of the above functions, the most appropriate part of the site for such a thing is the DVD encryption section below.
Unlike ISO 9660, UDF supports packet writing.
This is meant to be the area where specific files are located, in order to keep the overview areas small, so that they may be used as a quick overview.
For a quick overview, see UDF overview. (Not a lot of further details are currently available here.) There are various versions of UDF: See Wikipedia: Revisions of UDF and Wikpedia: Flavors of UDF. Q321640
Wikipedia: Mount Rainier (packet writing) says "The physical format of MRW disks is an extension of the UDF format"
A technology which has become fairly common and often using UDF is a DVD. Consequently, UDF may be supported similar to ISO 9660 by the same sort of software that handles CDs. For example, in Unix the mount command may simply need a different option (using -t udf). To write to a DVD, software that handles CDs may also have support for using DVDs storing data in ISO 9660 or UDF format. (However, in Unix-like operating systems, CDs are generally written with cdrecord whereas DVDs are often made with growisofs.) Consequently, information on handling DVDs may be in this site's section of handling CD-based file systems, possibly with a quick note of UDF-specific information.