Misplaced Pages

Atari DOS

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.

Atari DOS is the disk operating system used with the Atari 8-bit computers . Operating system extensions loaded into memory were required in order for an Atari computer to manage files stored on a disk drive . These extensions to the operating system added the disk handler and other file management features.

#317682

78-488: The most important extension is the disk handler. In Atari DOS 2.0, this was the File Management System ( FMS ), an implementation of a file system loaded from a floppy disk . This meant at least an additional 32 KB RAM was needed to run with DOS loaded. There were several versions of Atari DOS available, with the first version released in 1979. Atari was using a cross assembler with Data General AOS . In

156-448: A file system or filesystem (often abbreviated to FS or fs ) governs file organization and access. A local file system is a capability of an operating system that services the applications running on the same computer . A distributed file system is a protocol that provides file access between networked computers. A file system provides a data storage service that allows applications to share mass storage . Without

234-424: A device, device type, directory prefix, file path separator, or file type. File systems typically support organizing files into directories , also called folders , which segregate files into groups. This may be implemented by associating the file name with an index in a table of contents or an inode in a Unix-like file system. Directory structures may be flat (i.e. linear), or allow hierarchies by allowing

312-458: A direct replacement for the 1050 rather than the major upgrade it was intended to be. DOS XE did not ship until 1988/89, by which time the same modes were already supported by a variety of 3rd party solutions like SpartaDOS . Nevertheless, shipping DOS 2.5 with the drives for over a year led to significant confusion in the market. The drive was otherwise very well received. It was "eerily silent during operation", so much so that reviews noted it

390-652: A directory to contain directories, called subdirectories. The first file system to support arbitrary hierarchies of directories was used in the Multics operating system. The native file systems of Unix-like systems also support arbitrary directory hierarchies, as do, Apple 's Hierarchical File System and its successor HFS+ in classic Mac OS , the FAT file system in MS-DOS 2.0 and later versions of MS-DOS and in Microsoft Windows ,

468-405: A disk formatted with DOS 2.0S . DOS 2.0S consisted of DOS.SYS and DUP.SYS . DOS.SYS was loaded into memory, while DUP.SYS contained the disk utilities and was loaded only when the user exited to DOS. In addition to bug fixes, DOS 2.0S featured improved NOTE/POINT support and the ability to automatically run an Atari executable file named AUTORUN.SYS . Since user memory

546-515: A file system can be managed by the user via various utility programs. Atari XF551 The XF551 is a 5 1/4 inch floppy disk drive produced by Atari, Inc. for the Atari 8-bit computers . Introduced in 1987, it matches the gray design language of the XE models. It was the first drive from the company with official support for double-density and double-sided floppy disks—360 kB of storage per disk—and

624-443: A file system creates a file, it allocates space for data. Some file systems permit or require specifying an initial space allocation and subsequent incremental allocations as the file grows. To delete a file, the file system records that the file's space is free; available to use for another file. A local file system manages storage space to provide a level of reliability and efficiency. Generally, it allocates storage device space in

702-422: A file system implementation. The physical file system layer provides relatively low-level access to a storage device (e.g. disk). It reads and writes data blocks , provides buffering and other memory management and controls placement of blocks in specific locations on the storage medium. This layer uses device drivers or channel I/O to drive the storage device. A file name , or filename , identifies

780-529: A file system, applications could access the storage in incompatible ways that lead to resource contention , data corruption and data loss . There are many file system designs and implementations – with various structure and features and various resulting characteristics such as speed, flexibility, security, size and more. Files systems have been developed for many types of storage devices , including hard disk drives (HDDs), solid-state drives (SSDs), magnetic tapes and optical discs . A portion of

858-417: A file to consuming applications and in some cases users. A file name is unique so that an application can refer to exactly one file for a particular name. If the file system supports directories, then generally file name uniqueness is enforced within the context of each directory. In other words, a storage can contain multiple files with the same name, but not in the same directory. Most file systems restrict

SECTION 10

#1732873675318

936-697: A forked file system on the Macintosh, and Microsoft supports streams in NTFS. Some file systems maintain multiple past revisions of a file under a single file name; the file name by itself retrieves the most recent version, while prior saved version can be accessed using a special naming convention such as "filename;4" or "filename(-4)" to access the version four saves ago. See comparison of file systems#Metadata for details on which file systems support which kinds of metadata. A local file system tracks which areas of storage belong to which file and which are not being used. When

1014-472: A granular manner, usually multiple physical units (i.e. bytes ). For example, in Apple DOS of the early 1980s, 256-byte sectors on 140 kilobyte floppy disk used a track/sector map . The granular nature results in unused space, sometimes called slack space , for each file except for those that have the rare size that is a multiple of the granular allocation. For a 512-byte allocation, the average unused space

1092-404: A new "Dual Density" mode. To avoid confusion, Atari users soon began referring to this as Enhanced Density to differentiate it from real double density systems. Initially, this increased density mode was not able to be used as Atari shipped the drives with 2.0, which only supported the original 90 kB mode. This was addressed not long after with the release of DOS 3.0. When formatted with DOS 3.0,

1170-595: A new model was not put into production. At the same time, the success of the Nintendo Entertainment System (NES) prompted Atari to repackage their 65XE as the Atari XEGS video game console , boasting it could be expanded to a complete computer with the addition of a keyboard and disk drive. Nintendo sued, noting that Atari had no disk drives to sell, forcing Atari to rush the drive to market in June 1987 even though

1248-668: A proprietary TOP-DOS format. Published by Eclipse Software. Written by R. K. Bennett. This DOS supports Turbo 1050, Happy, Speedy, XF551 and US Doubler highspeed drives. XL/XE only. Published by Martin Reitershan Computertechnik. Written by Herbert Barth and Frank Bruchhäuser. This DOS adds the ability to use sub-directories, and supports hard-drives. Published by Wordmark Systems, includes complete source code under copyleft license , with an exception on distributing commercially only if it included in software or derivated software made of it would cost less than $ 50. There

1326-472: A relatively fast 8.33 MHz. The controller was paired with the then-standard Western Digital FD1772 floppy disk controller, a late-model version of WD's drive controllers that implemented almost all of the required circuitry in a single 28-pin chip and thereby lowered the total cost of implementation. Previous to the XF551, users would generally use both sides of a floppy disk by formatting one side, flipping

1404-452: A repackaged Atari 65XE and would run existing 8-bit games. As part of the XEGS launch, Atari boasted about its large library of software as well as its ability to be used as a true computer with the supplied keyboard and optional peripherals including a floppy drive. By this point, stocks of the 1050 had already run out. This led to about six months where no official Atari drives were available for

1482-431: A stream of bytes . Typically, to read file data, a program provides a memory buffer and the file system retrieves data from the medium and then writes the data to the buffer. A write involves the program providing a buffer of bytes that the file system reads and then stores to the medium. Some file systems, or layers on top of a file system, allow a program to define a record so that a program can read and write data as

1560-585: A structure; not an unorganized sequence of bytes. If a fixed length record definition is used, then locating the n record can be calculated mathematically, which is relatively fast compared to parsing the data for record separators. An identification for each record, also known as a key, allows a program to read, write and update records without regard to their location in storage. Such storage requires managing blocks of media, usually separating key blocks and data blocks. Efficient algorithms can be developed with pyramid structures for locating records. Typically,

1638-407: A thriving market for 3rd party DOSes which had long supported double-density modes and the higher transfer speeds. Among these was DOS XL , introduced in 1983 by Optimized Systems Software (OSS), authors of the original Atari DOS. Atari contracted OSS to produce a new version, initially known as ADOS, which added double-sided support to its existing double-density and high-speed features. Prior to

SECTION 20

#1732873675318

1716-432: A user's use of storage space. A file system typically ensures that stored data remains consistent in both normal operations as well as exceptional situations like: Recovery from exceptional situations may include updating metadata, directory entries and handling data that was buffered but not written to storage media. A file system might record events to allow analysis of issues such as: Many file systems access data as

1794-405: Is 256 bytes. For 64 KB clusters, the average unused space is 32 KB. Generally, the allocation unit size is set when the storage is configured. Choosing a relatively small size compared to the files stored, results in excessive access overhead. Choosing a relatively large size results in excessive unused space. Choosing an allocation size based on the average size of files expected to be in

1872-534: Is invisible to the end user and the system still works correctly. However this can degrade performance on some storage hardware that work better with contiguous blocks such as hard disk drives . Other hardware such as solid-state drives are not affected by fragmentation. A file system often supports access control of data that it manages. The intent of access control is often to prevent certain users from reading or modifying certain files. Access control can also restrict access by program in order to ensure that data

1950-510: Is modified in a controlled way. Examples include passwords stored in the metadata of the file or elsewhere and file permissions in the form of permission bits, access control lists , or capabilities . The need for file system utilities to be able to access the data at the media level to reorganize the structures and provide efficient backup usually means that these are only effective for polite users but are not effective against intruders. Methods for encrypting file data are sometimes included in

2028-500: Is number of free addons and extensions for MyDOS created by users. This is a fork of MyDOS, intended to be used as game laucher. This DOS used a command-line interface. Was not compatible with DOS 2.0, but could read DOS 2.0 disks. Supports subdirectories and hard drives being capable of handling filesystems sized up to 16 MB . Included the capability to create primitive batch files. A more sophisticated version of SpartaDOS , which strongly resembles MS-DOS in its look and feel. It

2106-550: Is stored inside the allocation group itself. Additional attributes can be associated on file systems, such as NTFS , XFS , ext2 , ext3 , some versions of UFS , and HFS+ , using extended file attributes . Some file systems provide for user defined attributes such as the author of the document, the character encoding of a document or the size of an image. Some file systems allow for different data collections to be associated with one file name. These separate collections may be referred to as streams or forks . Apple has long used

2184-404: The 815 Dual Disk Drive, which was both expensive and incompatible with the standard 810, and thus sold only a small number; making DOS version 2.0D rare and unusual. The 1050 was the first drive from Atari to offer higher recording density. For reasons unknown, they did not take advantage of the 180 kB "double density" mode the hardware in the 1050 was capable of using, and instead introduced

2262-625: The Atari XF551 drive, as well as its burst I/O. DOS XE used a new disk format which was incompatible with DOS 2.0S and DOS 2.5, requiring a separate utility for reading older 2.0 files. It also required bank-switched RAM, so it did not run on the 400/800 machines. It supported date-stamping of files and sub-directories. DOS XE was the last DOS made by Atari for the Atari 8-bit computers. Many of these DOSes were released by manufacturers of third-party drives, anyone who made drive modifications, or anyone who

2340-623: The Intel 8048 microcontroller . The 8048 included internal RAM and ROM and thus greatly simplified the overall design of the interface. The Tramiels took the CR and repackaged it to match the silver-grey styling of the XE and ST line. While introducing the XE's at the January 1985 Consumer Electronics Show , the company previewed the design as the XF521. It was rumored it would also support true double-density mode. When

2418-656: The NTFS file system in the Windows NT family of operating systems, and the ODS-2 (On-Disk Structure-2) and higher levels of the Files-11 file system in OpenVMS . In addition to data, the file content, a file system also manages associated metadata which may include but is not limited to: A file system stores associated metadata separate from the content of the file. Most file systems store

Atari DOS - Misplaced Pages Continue

2496-447: The 1050 it replaced, but overall similar. It connected to the computer or XEGS using the SIO port, with two ports on the back, in and out, to allow it to be daisy chained to other peripherals. The back also had the jack for the power supply , the power switch, and a DIP switch that allowed the drive to be numbered 1 through 4. When operating in legacy modes to read or write to disks from

2574-428: The 810 or 1050, the system transferred data at the original standard speed of 19,040 bps. This speed was much lower than the SIO was capable of, and had been selected simply because that was the limit of the logic analyzer available to the engineers designing the original 810s. The XF551, when operating in double-density mode, doubled this to 38,908 bps. SIO is a serial bus that sends commands and data over

2652-413: The 815 began shipping in June 1980, but mass production never started. Nevertheless, this brief introduction set the standard for double-density drives that other companies would later support. During the introduction of the Atari 1200XL in 1982, the company introduced a new line of peripherals matching the styling of the new machine. This included the Atari 1050 , a new disk drive that was built around

2730-509: The Atari HELP key and/or the inverse key. Help files needed to be present on the system DOS disk to function properly. DOS 3 also used special XIO commands to control disc operations within BASIC programs. Version 2.5 is an upgrade to 3.0. After listening to complaints by their customers, Atari released an improved version of their previous DOS. This allowed the use of Enhanced Density disks, and there

2808-461: The Nintendo lawsuit, Atari claimed the only holdup on the new drive was that the documentation for the new DOS was not ready. When the lawsuit was launched, Atari put the drive on the market immediately in June 1987, shipping it with the existing Atari DOS 2.5. This was a success, as it did result in the lawsuit being dropped. However, DOS 2.5 lacked support for the new modes, which essentially made it

2886-525: The Tramiels took over the company they found huge stocks of unsold 1050s, and repeatedly delayed the XF521 while selling these off. By the time the stocks of these drives finally dwindled in 1986, the ST was selling strongly and the company had lost interest in the 8-bit line. Any mention of the XF521 disappeared. In October 1985, Nintendo introduced the Nintendo Entertainment System to North America. By late 1986 it

2964-588: The XF551 Enhancer appeared, a modification that allowed the drive to ignore the timing hole and write to either side of the disk. Most of the drives sold used a Mitsumi Electric mechanism, although a small number of later models replaced this with one from Chinon Industries . They can be distinguished as the Mitsumi version has a rectangular LED on the front while the Chinon version is round. The Chinon versions also used

3042-429: The XF551 ran at the industry standard 300 RPM. This caused problems for a small number of programs whose copy protection relied on accurately timing the drive. One design feature of DOS XE was that it always wrote files to side one of the floppy until it ran out of room. This meant the disks could be inserted in older drives also being run with DOS XE, or compatible double-density 3rd party DOSes, and at least read

3120-469: The birth of the 130XE". By the late 1980s, sales of the XE series were primarily to low-cost markets like eastern Europe and South America. These markets were so cost-sensitive that even the low price of the XF551 was too much for most users, and the most common storage mechanism was the XC12 cassette tape system. The entire 8-bit series was eventually discontinued in 1992. The XF551 was slightly smaller than

3198-543: The board , Irving Gould , and left the company. After spending some time looking for ways to re-enter the field, in July he arranged a deal to buy Atari from its owners, Warner Communications , for no cash and several million in promissory notes . Attempting to bring the company back to some semblance of profitability, the new management laid off whole divisions while working to bring their new Atari ST , to market as soon as possible. During this period many advanced projects within

Atari DOS - Misplaced Pages Continue

3276-447: The company were cancelled. This included Atari's own 32-bit efforts and several advanced game consoles . Warehouses filled with stocks of the 8-bit line were sold off at fire-sale prices pending the introduction of cost-reduced models, the XE series. Atari had already been working on several upgrades to the 1050 series, including the 1050CR, for cost-reduced. This replaced the original custom MOS 6507 -based interface card with one using

3354-421: The computer main memory can be set up as a RAM disk that serves as a storage device for a file system. File systems such as tmpfs can store files in virtual memory . A virtual file system provides access to files that are either computed on request, called virtual files (see procfs and sysfs ), or are mapping into another, backing storage. From c.  1900 and before the advent of computers

3432-519: The concepts. The logical file system layer provides relatively high-level access via an application programming interface (API) for file operations including open, close, read and write – delegating operations to lower layers. This layer manages open file table entries and per-process file descriptors. It provides file access, directory operations, security and protection. The virtual file system , an optional layer, supports multiple concurrent instances of physical file systems, each of which called

3510-405: The disk held 40 tracks of 27 sectors, up from 18 on DOS 2.0. Each sector holds 128 bytes, for a total of 133,120 bytes of storage, up from DOS 2.0's 92,160. In DOS 2.0, a 10-bit number was used to store sector numbers in the directory. This limited disks to a maximum of 1024 sectors. The new format had 1080 sectors, so 2.0 would not be able to use all of its capability. To address this, and to offer

3588-495: The disk over, and formatting the second, the so-called " flippy disk ". This presented a potential problem with the new drive; if a user flipped the disk and formatted using the default double-sided format, any data on the other side would be erased. To prevent this, the system only allowed formatting if the disk's timing hole was in the correct "up" position, otherwise it would only format in the older single-sided formats. For those that needed to make flippys for use with other drives,

3666-409: The disks unreadable on DOS 2.0. The DOS 3.0 Master Diskette included a small utility program to copy a 2.0 disk to 3.0, but not one to copy it back. A separate utility allowed disks to be formatted in 2.0 format if compatibility was needed. As a result of this decision, DOS 3 was extremely unpopular and did not gain widespread acceptance amongst the Atari user community. DOS 3 provided built-in help via

3744-484: The double-density MFM encoding standard that provided up to 180 kB of storage. For reasons unknown, Atari's DOS for the machine did not support the double-density format, instead it used a new format known alternately as "enhanced density" or "dual density" with 130 kB. Several 3rd party DOS products emerged that fully supported double-density, as well as new drives like the Indus GT that offered double-density from

3822-413: The entire 8-bit computer line, in 1992. When the Atari 8-bit computers began shipping in 1979, Atari showed two floppy disk drive systems, the 810 and the 815. The 810 used the then-standard single-density FM encoding format that stored about 90 kB of data, while the 815 packaged two drives in a single case, both supporting a double-density MFM encoding format of 180 kB. Small numbers of

3900-416: The file system. This is very effective since there is no need for file system utilities to know the encryption seed to effectively manage the data. The risks of relying on encryption include the fact that an attacker can copy the data and use brute force to decrypt the data. Additionally, losing the seed means losing the data. Some operating systems allow a system administrator to enable disk quotas to limit

3978-472: The first version of DOS from Atari , all commands were only accessible from the menu. It was bundled with the Atari 810 disk drives. This version was entirely memory resident, which made it fast but occupied memory space. The second, more popular version of DOS from Atari was bundled with the 810 disk drives and some early Atari 1050 disk drives. It is considered to be the lowest common denominator for Atari DOSes, as any Atari-compatible disk drive can read

SECTION 50

#1732873675318

4056-473: The format of a disk automatically, and the user had to select the format of the disks from the DOS menu. The 1450XLD was never released, and the rights for DOS 4 were returned to the author, Michael Barall, who placed it in the public domain . It was published by Antic Software in 1984, and is sometimes referred to as "Antic DOS" for this reason. DOS XE supported the double-density and double-sided capabilities of

4134-455: The introduction of the IBM PC , drives using the standard 34-bit ribbon cable had proliferated. This allowed internal mechanisms to be easily swapped. Earlier Atari drives used a customized controller that communicated with the host computer's Atari SIO bus using a MOS 6507 running at 500 kHz. For historical reasons, these drives used a 19.2 kbps speed to transfer data, although this

4212-446: The last 3 bytes for housekeeping data (bytes used, file number, next sector), leaving 125 bytes for data. This meant each disk held 707 × 125 = 88,375 bytes of user data. The single-density disk holding a mere 88 KB per side remained the most popular Atari 8-bit disk format throughout the series' lifetime, and almost all commercial software continued to be sold in that format (or variants of it modified for copy protection ), since it

4290-495: The length of a file name. Some file systems match file names as case sensitive and others as case insensitive. For example, the names MYFILE and myfile match the same file for case insensitive, but different files for case sensitive. Most modern file systems allow a file name to contain a wide range of characters from the Unicode character set. Some restrict characters such as those used to indicate special attributes such as

4368-493: The line, and it appeared the company was in no hurry to introduce the XF521. Nintendo sued Atari for false advertising , noting that Atari claimed the system supported a floppy but did not actually have drives for sale. At some point during this period, Atari decided to completely redesign the drive. The computer market was already well into the conversion from 5.25 to 3.5-inch disks, and 5.25 double-density double-sided drives were now commonplace and inexpensive. Moreover, after

4446-595: The names of all the files in one directory in one place—the directory table for that directory—which is often stored like any other file. Many file systems put only some of the metadata for a file in the directory table, and the rest of the metadata for that file in a completely separate structure, such as the inode . Most file systems also store metadata not associated with any one particular file. Such metadata includes information about unused regions— free space bitmap , block availability map —and information about bad sectors . Often such information about an allocation group

4524-463: The new drive, which operated at higher speeds and had more features, the 6507 was replaced by the Intel 8040 , microcontrollers that included ROM and RAM on the same chip and thus allowed a great simplification of the controller. The 8040 versions did not have enough ROM for the entire driver, so later models moved to the 8050 with 4 kB for a further simplification. These chips, originally introduced in 1976, were now available for pennies and ran at

4602-457: The older Atari 400 / 800 models. BW-DOS is freeware by Jiří Bernasek. XDOS is freeware by Stefan Dorndorf. Minimalistic DOS for Atari, supporting files formats of various other DOS software, such as files of Atari DOS and MyDOS. A number of different formats existed for Atari disks. Atari DOS 2.0S, single-sided, single-density disk had 720 sectors divided into 40 tracks . After formatting , 707 sectors were free. Each 128-byte sector used

4680-535: The older single and enhanced density formats from DOS 2 and 2.5. To support the newer modes, it returned to the blocks concept used in DOS 3.0 when used to format enhanced or double density disks, but this time using slightly smaller 6-sector format, which held 768 bytes in enhanced density and 1536 bytes in double density. Like DOS 3, disks formatted in the new higher-density formats were not compatible with older drives and DOSes. It could read and write to those disks to retain compatibility. However, it could not determine

4758-420: The possibility of working with even larger formats in the future, DOS 3.0 grouped sectors together in groups of eight, known as a block , each holding 1,204 bytes. The number in the directory was reduced to 8-bits, meaning it could address up 256 kB on a single disk. The boot information and directory used three blocks, leaving 130 kB free for user storage on the 1050. Unfortunately, the new directory format made

SECTION 60

#1732873675318

4836-550: The rapidly falling market prices. Atari eventually introduced lower-cost models, the 600XL and 800XL, but these were repeatedly delayed and did not reach market until late in 1983, too late to have an impact. Combined with the effects of the video game crash of 1983 , the company was soon losing over a million dollars a day. The success of the C64 did not save Commodore from problems of its own. In January 1984, Commodore president Jack Tramiel got into some sort of argument with chairman of

4914-626: The same in and out pins. This requires the devices on the SIO to be "smart", listening for commands being sent to their device number, decoding the instructions, and responding in kind. In previous Atari drives, this had been accomplished with the 6507, a cut-down version of the MOS 6502 that was being used in the Atari VCS console. The console ran at 1.1 MHz, but some 6507s supplied by Synertek failed to run at this speed reliably and were passed off to be used as SIO controllers running at lower speeds. For

4992-405: The software was not ready. The XF551 is generally considered the best of Atari's drive offerings; not only does it store three times as much data as the 1050, it is twice as fast and almost silent in operation. Its release was marred by packaging it with an old version of Atari DOS which does not support the new features. This was addressed with DOS XE a year later. Support was dropped, along with

5070-454: The start, along with additional features and improved performance. In 1983, Commodore International sparked off a price war in the home computer market by repeatedly lowering the price of its VIC-20 and Commodore 64 (C64) lines in order to undercut the TI-99/4A . Atari had recently introduced the Atari 1200XL at a higher price point, and its lineup could not be produced profitably at

5148-429: The storage tends to minimize unusable space. As a file system creates, modifies and deletes files, the underlying storage representation may become fragmented . Files and the unused space between files will occupy allocation blocks that are not contiguous. A file becomes fragmented if space needed to store its content cannot be allocated in contiguous blocks. Free space becomes fragmented when files are deleted. This

5226-442: The terms file system , filing system and system for filing were used to describe methods of organizing, storing and retrieving paper documents. By 1961, the term file system was being applied to computerized filing alongside the original meaning. By 1964, it was in general use. A local file system's architecture can be described as layers of abstraction even though a particular file system design may not actually separate

5304-462: The timing hole for both formatting and reading, and thus could not work with flippy disks at all. This limitation could be removed with the Enhancer. Because the drive mechanism was connected to the board using a standard connector, it was possible to replace it with a 3.5-inch mechanism, and this became quite popular. In contrast to the 810 and 1050, which ran at the non-standard speed of 288 RPM,

5382-624: The use of Double Density floppies. Unlike most ATARI DOSses, this used a command line instead of a menu. DOS XL provided a menu program in addition to the command line. This DOS could read SS/SD, SS/ED, SS/DD and DS/DD disks, and made use of all known methods of speeding up disk-reads supported by the various third-party drive manufacturers. Published by Technical Support. Written by Paul Nicholls. Menu driven DOS with enhanced features. Sorts disk directory listings and can set display options. File directory can be compressed . Can display deleted files and undelete them. Some advanced features required

5460-403: Was a runaway success, prompting the Tramiels to reexamine the games console market. At the time, Atari had warehouses of the Atari 5200 and Atari 7800 which were put back on the market, but neither had been in production for some time and were built on pre-XE systems with no capability to produce more. This led to the decision to introduce a new console, the Atari XEGS , which was essentially

5538-472: Was a utility to read DOS 3 disks. An additional option was added to the menu ( P. FORMAT SINGLE ) to format single-density disks. DOS 2.5 was shipped with 1050 disk drives and some early XF551 disk-drives. Included utilities were DISKFIX.COM , COPY32.COM , SETUP.COM and RAMDISK.COM . DOS 4.0 was designed for the 1450XLD . It was designed to operate with larger disk formats, adding double density and double sided support while also supporting

5616-408: Was also the final floppy disk drive Atari produced for the 8-bit computers. The XF551 allows faster transfer speed when used in double-density mode, doubling performance. Although an XE-styled drive was shown several times during 1985 and 1986, production waited while leftover inventories of the Atari 1050 were sold off. By the time these ran out late in 1986, interest in the 8-bit line had waned and

5694-494: Was compatible with all Atari-made disk drives. In 1978, Percom established a double-density layout standard which all other manufacturers of Atari-compatible disk drives such as Indus , Amdek , and Rana —except Atari itself— followed. A configuration block of 12 bytes defines the disk layout. It is ramdisk for Atari XL, compatible with many DOS software. It is an utility to work with Atari disks and diskettes, based on MyDOS and SpartaDOS. File system In computing ,

5772-692: Was dissatisfied with the available DOSes. Often, these DOSes could read disks in higher densities, and could set the drive to read disks faster (using Warp Speed or Ultra-Speed techniques). Most of these DOSes (except SpartaDOS) were DOS 2.0 compatible. Menu driven DOS that was compatible with DOS 2.0. Among the first third-party DOS programs to support double-density drives. Many enhancements including sector copying and verifying, speed checking, turning on/off file verifying and drive reconfiguration. Published by Rana Systems. Written by John Chenoweth and Ron Bieber, last version 8.2D. DOS produced by Optimized Systems Software . Compatible with DOS 2.0 - Allowed

5850-464: Was erased when DUP.SYS was loaded, an option to create a MEM.SAV file was added. This stored user memory in a temporary file ( MEM.SAV ) and restored it after DUP.SYS was unloaded. The previous menu option from DOS 1.0 , N. DEFINE DEVICE , was replaced with N. CREATE MEM.SAV in DOS 2.0S . Version 2.0S was for single-density disks, 2.0D was for double-density disks. 2.0D shipped with

5928-422: Was impossible to tell if it was being used without looking at the access LED. The only real complaints were the rear position of the power button, which made it difficult to access in some computer desks, and that it was very "fussy" about the diskettes, rejecting as many as 20% of low-cost floppies. In the end, it was "heartily recommend"ed, and "the best thing that's happened to Atari's 8-bit computer line since

6006-481: Was not a limitation of the bus itself. Third party drives normally used higher speeds, when run with suitable third-party DOSes, with some operating as high as the 52 kbps "Warp Speed" of the Happy 810 . For the new drive, Atari decided to double the rate to 38 kbps, although only when used with double-density disks. Atari DOS 2.5, introduced for the 1050 in 1983, did not support either capability. This had led to

6084-581: Was shipped on a 64 KB ROM cartridge . A SpartaDOS compatible DOS (in fact, a renamed version of SpartaDOS 3.x, for legal reasons). RealDOS is shareware by Stephen J. Carden and Ken Ames. A SpartaDOS compatible DOS, the last version 1.30 was released in December 1995. It has a much lower memory footprint compared to the original SpartaDOS and does not use the RAM under the ROM of XL/XE machines, allowing it to be used on

#317682