Abort, Retry, Fail?

From HandWiki
Short description: Computer error message
MS-DOS prompts "Abort, Retry, Fail?" after being commanded to list a directory with no diskette in the drive using the dir command.

"Abort, Retry, Fail?" (or "Abort, Retry, Ignore?") is an error message found in DOS operating systems, which prompts the end-user for a course of action to follow. Although an improvement over CP/M,[1] the message has been cited as an example of poor usability in computer user interfaces.

Background

In CP/M, attempting to read a floppy disk drive with the door open would hang until a disk was inserted and the disk drive door was closed (very early disk hardware did not send any kind of signal until a disk was spinning, and a timeout to detect the lack of signal required too much code on these tiny systems). Many users of CP/M became accustomed to this as a method of managing multiple disks, by opening the disk drive to stop a program from reading or writing a file until the correct disk could be inserted.

A primary design consideration for PC DOS was that software written for CP/M be portable to DOS without changes. Even the first IBM PC had hardware that told the operating system that the disk drive door was open, but returning an error to software would require the software to be rewritten to handle the error. Still, it was desirable to improve the experience, in particular by giving the user a way to get out of the hang without having to find a disk to insert in the drive.[1] The prompt was invented for this reason.

Similarily, CP/M would repeatedly read or write a disk sector as long as there was an error. Often the only way out of this was to change the disk to another (it would then read something random off the new disk). The prompt was reused to provide a way to stop this as well.

Description

A missing disk (or disk drive door opened) was defined by DOS as a "critical error" and would call the "critical error handler".[2] The default "critical error handler" was part of COMMAND.COM[2] and printed the "Abort, Retry, ..." prompt, then waited for user input. Other problems (in particular, a checksum error while reading data from a disk) were also defined as a "critical error", thus causing the prompt to appear for reasons other than a missing disk or opened disk drive. Users could press a key to indicate what they wanted to happen; available options included:[3]

  • Abort (A): Terminate the operation or program, and return to the command prompt. In hindsight, this was not a good idea as the program would not do any cleanup (such as completing writing of other files).
  • Retry (R): Attempt the operation again. "Retry" was what the user did if they could fix the problem by inserting a disk and closing the disk drive door. On early hardware, retrying a disk read error would sometimes be successful, but as disk drives improved, this became far less likely.
  • Ignore (I): Return success status to the calling program or routine, despite the failure of the operation. This could be used for disk read errors, and DOS would return whatever data was in the read buffer (which might contain some of the correct data). "Ignore" did not appear for open drives or missing disks.
  • Fail (F): Starting with MS-DOS/PC DOS 3.3, "Fail" returned an error code to the program, similar to a "file not found" error. The program could then gracefully recover, perhaps asking the user for a different file name. This removed the biggest problem with the prompt (which earlier was known as "Abort, Retry, Ignore?") by providing an option that did not crash the program or repeat the prompt.

A program could install its own "critical error handler" while running,[2] and many of the more sophisticated programs (in particular full screen programs) did so in order to avoid the messages disturbing the display. Some programs faked the missing "Fail" response in DOS 2.0 by jumping back to the calling program, skipping the return stack in DOS. This was a risky hack as it relied on the stack layout and skipped cleanup operations in the operating system.

Usability

The error message has been described as being an example of poor user interface design. For most users, if the message appeared, the only choice was to hit 'R'—which repeated the message—or hit another letter, which caused the program to crash and all work to be lost. The scholar Mireille Hildebrandt described it this way:[4]

It has become an icon of poor interface design, because it led exactly nowhere ... A veritable Catch 22, since the only viable option appeared to be to keep typing R until one was willing to accept that one's work was lost and there was nothing left to do but shut down the program and start anew.

MS-DOS 6.22 contained a singular case where the only option was "(R) Retry": when flushing the hard disk write-behind cache could not be completed. The user may attempt to repeat the write until successful or power off the system.

Modern systems

Hard disks and larger removable media such as Zip drives made the need to manage multiple disks per drive obsolete, and thus made the prompt useless. It was gradually replaced with code that acted like "Fail" immediately. DOS 3.3 COMMAND.COM provided the startup option /F to force the default critical error handler to return "Fail" on all errors. Starting with version 4.0, the alternative command line processors 4DOS and NDOS supported /F and the corresponding CritFail=Yes directive in 4DOS.INI/NDOS.INI as well. The option was also supported by the COMMAND.COM of PTS-DOS 6.51 and S/DOS 1.0, as well as by DR-DOS 7.02 and higher. In OpenDOS 7.01, COMMAND.COM provides a similar feature with /N (described as "do not install a critical error handler") which is still supported in newer versions. Most other operating systems, such as Linux, always act like "Fail" in all cases.

A screenshot of Wrong Volume dialog box on Windows 10.

(As of 2001) Windows can still generate a similar prompt, although in a dialog box and with a more comprehensive error message. The choices are similar but renamed: "Cancel" (to the user this is similar to "Abort" but technically it is a "Fail" with a different error code), "Try Again" (instead of "Retry") and "Continue" (instead of "Fail"). This may be supported by the drivers for some removable media when a file is opened with a full volume name or the disk is removed while the file is open. However for mundane actions similar to what triggered the prompt in DOS, such as attempting to read "E:" when there is no disk in the CD drive, Windows produces an immediate "Fail".

In popular culture

Humorous variations of Edgar Allen Poe's The Raven using "Abort, Retry, Ignore?" in place of "nevermore" were written in the 1980s and 1990s and were quite popular, distributed by bulletin board and email.[5] The original and best known version has been credited to Cleveland poet Marcus Bales.[6][7]

In 1993, Neil Howe published 13th Gen: Abort, Retry, Ignore, Fail?, a sympathetic book about the culture of Generation X.[8]

In 1996, White Town released an EP entitled >Abort, Retry, Fail?.[9]

PC Magazine has used the term as the title of its column highlighting humorous computer-related errors.[10]

In the 1999 video game Sid Meier's Alpha Centauri "Abort, Retry, Fail?" was graffiti next to the door of the "Edit Universe project," implied to be a research and development undertaking with an ominous potential. The phrase is introduced as an audio quote when the player achieves the technological advance of "Nanomatter Editation," and ends with the warning, "...if you see this message, always choose 'Retry'."[11]

See also

References

  1. ↑ 1.0 1.1 "CP/M-86 And MS-DOS: A Comparative Analysis". PC Magazine. Operating Systems (Software Communications, Inc.) 1 (7): 181–182, 187–190 [189]. November 1982. https://books.google.com/books?id=vy3cBZkjbZgC&pg=PA189. Retrieved 10 February 2020. "[…] Error handling is one of MS-DOS's most mature features. The operating system traps disk errors and displays an error message in understandable English, giving the options RETRY, IGNORE, or ABORT. Applications programs running under MS-DOS can also trap these errors and handle them in whatever way is most consistent with the application, ensuring the applications program is always in control of the system. […]". 
  2. ↑ 2.0 2.1 2.2 "Chapter 19.1.3: Exception Handling in DOS: The Critical Error Handler". The Art of Assembly Language Programming. 29 September 1996. http://webster.cs.ucr.edu/AoA/DOS/ch19/CH19-2.html. 
  3. ↑ "Action Taken on Abort, Retry, Ignore, Fail". Microsoft Knowledge Base. Microsoft. 16 November 2006. http://support.microsoft.com/kb/67586. 
  4. ↑ Human Law and Computer Law: Comparative Perspectives. Springer Science & Business Media. 23 May 2013. pp. 47–48. ISBN 978-9-40076314-2. https://books.google.com/books?id=SbREAAAAQBAJ&pg=PA82. 
  5. ↑ "Midnight Dreary - GNU Project". https://www.gnu.org/fun/jokes/midnight.dreary.html. 
  6. ↑ "Abort, Retry, Ignore – Poe Puree". http://www.stokely.com/lighter.side/abort.retry.ignore.html. 
  7. ↑ "Three Parodies of The Raven". http://www.silverberch.com/poe3.html. 
  8. ↑ 13th Gen: Abort, Retry, Ignore, Fail? (1 ed.). New York, USA: Vintage Books. 1993. ISBN 978-0-67974365-1. https://archive.org/details/13thgenabortretr00howe. 
  9. ↑ "Abort, Retry, Fail?_ Your Woman". discogs. 1997. http://www.discogs.com/White-Town-Abort-Retry-Fail_-Your-Woman/release/119353. 
  10. ↑ "PC Magazine's Extreme Makeover". 3 May 2006. https://www.pcmag.com/article2/0,2817,1953607,00.asp. 
  11. ↑ "Quotes / Sid Meier's Alpha Centauri". https://tvtropes.org/pmwiki/pmwiki.php/Quotes/SidMeiersAlphaCentauri. 



Retrieved from "https://handwiki.org/wiki/index.php?title=Abort,_Retry,_Fail%3F&oldid=3386902"