Abuse filter log

'{{Infobox 86-DOS version | name = 86-DOS 0.11 | version = 0.11 | image = 86-DOS 0.11 First Boot.png | arch = x86 | releasedate = 1980-08 | replaces = [[86-DOS 0.10]] | replaced-by = [[86-DOS 0.2]] }} '''86-DOS 0.11''' is the first public release of [[86-DOS]].<ref name="email">Paterson, Tim (5 February 2024). [[Document:Tim_Paterson_05-Feb-2024_Email]]</ref> It fixed an unspecified bug found in [[86-DOS 0.10]]<ref name="email" /><ref name="softalk">Hunter, David (March 1983). ''[https://web.archive.org/web/20190906120449/http://www.patersontech.com/dos/softalk.aspx The Roots of DOS: Tim Paterson]''. Softalk for the IBM Personal Computer. p. 12-15.</ref>, compiled shortly after version [[86-DOS 0.10|0.10]] was finished, and shipped in August 1980.<ref name="softalk" /> The [[w:Cromemco 4FDC|Cromemco 4FDC]] variant of this version of [[86-DOS]] was uploaded to the [[w:Internet Archive|Internet Archive]] by Gene Buckle ([https://archive.org/details/@f15sim f15sim]) on 29 December 2023.<ref>https://archive.org/details/86-dos-version-0.1-c-serial-11-original-disk</ref> Due to its earliness, several important features seen in later versions of [[86-DOS]] are missing. The [[COMMAND.COM|Command Interpreter]] does not support displaying file sizes, there is no tool for reporting available memory and disk space and it lacks the ability to format disks. ==<code>CREATE</code>== This version of 86-DOS supports an undocumented internal command named <code>CREATE</code>. It takes one argument, the name of the file to create, and creates an empty file with the specified name.<ref name="create">PorkyPiggy (January 2024). [https://forum.vcfed.org/index.php?threads/earliest-known-copies-of-86-dos.1246146/post-1360552 Earliest known copies of 86-DOS... (post #61)]</ref> [[86-DOS]] 0.11 is the only known version of [[86-DOS]] with this command. ==CHESS== [[File:86-DOS 0.11 Chess.png|thumb|CHESS running under 86-DOS 0.11.]] A modified<ref>PorkyPiggy (February 2024). [https://forum.vcfed.org/index.php?threads/86-dos-0-11-source-code-reconstruction.1246592/post-1365579 86-DOS 0.11 Source Code Reconstruction (post #11)]</ref> 8086 translation of the Z80 version of the chess game [[w:Sargon_(chess)|Sargon]] was shipped with 86-DOS 0.11.<ref name="email"></ref> The game prompts you for your color and ply depth at the beginning. Then, a user enters their moves in the coordinate notation format (referred to by [[w:Tim Paterson|Tim Paterson]] as the "algebraic chess notation") <code>FF-TT</code>, with <code>FF</code> being the "from" location and <code>TT</code> being the "to" location, both in uppercase. The computer makes moves in the exact same way, except in lowercase, to differentiate from your moves. Just like [[w:Sargon_(chess)|Sargon]], you can also restart or resign from the game by entering a capital case <code>R</code>. [[86-DOS]] 0.11 is the only known version of [[86-DOS]] with this game. ==EDLIN== EDLIN{{efn|Capitalizations vary between "EDLIN" and "Edlin". For example, the [https://web.archive.org/web/20210613012709/http://www.os2museum.com/wp/wp-content/uploads/2011/12/1987-Oct-OS2-1.0-Users_Reference.pdf OS/2 1.0 user manual] (published in 1987) uses "Edlin", while the [https://web.archive.org/web/20210519201510/http://bitsavers.org/pdf/hp/9000_hpux/softpc/98870-90050_MSDOS_3.3_Reference_Sep89.pdf MS-DOS 3.3 user manual] (published in 1988 and revised in 1989) uses "EDLIN". However, most references to 86-DOS' line editor between 1980 and 1982, including in the [https://computerhistory.org/blogs/microsoft-research-license-agreement-msdos-v1-1-v2-0/ MS-DOS 2.00 source code], use an all-capital case.}} is a line editor introduced in 86-DOS 0.11. It was meant to last only 6 months,<ref name="byte">Paterson, Tim (June 1983). ''[https://archive.org/stream/byte-magazine-1983-06/1983_06_BYTE_08-06_16-Bit_Designs#page/n245/mode/2up A Short History of MS-DOS]''. BYTE Magazine. p. 246.</ref> but ended up being the only text editor until [[MS-DOS]] 5.0 and is supported in all [[Windows NT]] versions up to [[Windows 10]].{{efn|EDLIN is supported only in [[Windows 10]] 32-bit with [[w:NTVDM|NTVDM]] installed, as well as [[Windows 7]] 32-bit and below by default. [[Windows 11]] [https://web.archive.org/web/20210811165354/https://www.microsoft.com/en-us/windows/windows-11-specifications does not have IA-32 support].}} The creator, [[w:Tim Paterson|Tim Paterson]], has called it the "quickest line editor I could imagine"<ref name="softalk" /> and an "absurdity".<ref name="byte" /> Software critic Bill Machrone called a later version of 86-DOS' EDLIN "just as bad as any other line editor I have attempted to use".<ref>Machrone, Bill (Late 1981). ''Seattle Computer Products' 8086 System''. Microsystems Magazine. p. 24.</ref> ===History=== EDLIN, being a line editor, was not a new concept. Its look, feel, and syntax have been compared to CP/M's ''ed'',<ref>United States District Court for the Western District of Washington (25 July 2007). ''[https://web.archive.org/web/20181003165746/http://seattletimes.nwsource.com/ABPub/2007/07/26/2003806592.pdf Paterson v. Little, Brown, and Co., et al. - Order]''. Seattle Times. Case 2:05-cv-01719-TSZ Document 29.</ref> which itself is loosely similar to Unix's ''ed'' and its predecessor ''qed''.<ref>Darwin, Ian (1984). ''[https://web.archive.org/web/20210713123804/http://doc.cat-v.org/unix/unix-before-berkeley/ A History of UNIX before Berkeley]''. /sys/doc/ Documentation Archive.</ref> EDLIN was created out of need for a text editor, a key part of office work and assembly-language development.<ref name="byte" /> It was written in either one<ref name="byte" /><ref>Paterson, Tim (4 August 2018). ''[https://www.youtube.com/watch?v=R2Qh0O3Dt10 VCF West XIII -- Tim Paterson -- Original DOS and the old days]''. Vintage Computer Federation.</ref> or two weeks.<ref name="softalk" /> ===Usage=== EDLIN was a line editor, reading a text file line-by-line.{{efn|EDLIN defines lines as text ending in a carriage return, or a line shorter than 255 characters if a carriage return is not found in the first 255.}} Line numbers were printed along with each line.<ref name="manual">Paterson, Tim (October 1980). ''[https://web.archive.org/web/20191105041038/http://patersontech.com/dos/docs/86_Dos_inst.pdf 86-DOS Preliminary Instruction Manual]''. PatersonTech.</ref> To call EDLIN, use the command <code>EDLIN <file></code>. If the file already exists, it will be opened - otherwise, it will be created and the message "New file" will be shown.<ref name="manual" /> The editor contained commands for users to control the document. They are denoted by the asterisk symbol (<code>*</code>) and appear after every line.<ref name="manual" /> {| class="wikitable" style="text-align: center;" !Command !Description !Notes !Extra controls |- |<number> |Jump to and edit a specific line number. |If no line number is entered, the line after the current line is selected. |When editing, the DEC VT-52 function key escape sequences (or custom escape sequences defined by the user) are available to use. ESC + S (F1) - Copy one character from the old line to the new line. ESC + T (F2) - After pressing, the user must press one character. All text in the old line up to the first occurrence of that character is copied to the new line. ESC + U (F3) - Copy all remaining characters from the old line to the new line. ESC + V (F4) - Skip over one character in the old line. ESC + W (F5) - After pressing, the user must press one character. All text in the old line including and after the first occurrence of that character is copied to the new line. ESC + P (BLUE) - Enter insert mode. As characters are typed, the position in the old line will not advance. ESC + Q (RED) - Exit insert mode. The position in the old line is advanced for each character typed. ESC + R (GRAY) - Make the new line the old line. |- |<numbers> L | List content of lines. | One or multiple numbers can be selected, in the format <code>line1,line2</code>. If none are specified, then the last 21 are selected. | |- |<number> I |Insert a new line at a specific line number. |If no line number is selected, the last line plus 1 is the selected. |To finish editing, press control and Z together. Then, press enter. |- |<numbers> D |Delete lines by number. |One or multiple numbers can be selected, in the format <code>line1,line2</code>. | |- |E |End editing and save the current file. |After saving, a backup of the previous version is saved as <code><filename>.BAK</code>. | |} ==File Search API== The file search APIs (search first and search next) are different and incompatible with later versions of [[86-DOS]]. This version's file search APIs return the 16-byte directory entry of the file found in the disk transfer address, instead of an unopened [[w:File Control Block|FCB]] containing the filename. Since the directory entry and [[w:File Control Block|FCB]] structures are different, applications such as <code>[[COMMAND.COM]]</code> do not work correctly under later versions of [[86-DOS]], and vice versa. ==Bugs and Quirks== {{multiple image | align = right | direction = vertical | width = 270 | image1 = 86-DOS 0.11 Filename Issue.png | caption1 = Creating multiple <code>TEST.DOC</code>s and erasing them all. | image2 = 86-DOS 0.11 Asterisk In Filename.png | caption2 = Filenames containing <code>*</code>. }} *Multiple files are allowed to have the same name, and <code>ERASE</code> erases all files with the specified name.<ref name="create" /> Existing files are not overwritten when new files with the same names are created (via the <code>CREATE</code> command or the file creation API). *The wildcard character <code>*</code> is not supported. This makes it very inconvenient to copy multiple files at once, and as a side effect, <code>*</code> can be used in filenames. Erasing files with names containing <code>*</code>, such as <code>*.*</code>, using a later version of 86-DOS may cause undesired data loss. *Various system utilities (such as the assembler) make use of high bit terminated strings, and characters with the 7th bit set may be outputted to the console. The high bits will be automatically stripped when characters are displayed through dumb terminals, but they may cause problems when video card/CRT is used. *By design, the filesystem supports files of any size; however, in this version, file sizes are assumed to be divisible by 128. If not, they will be rounded (up or down) to the nearest 128 bytes (instead of always rounding up) when accessed. This may cause files created by later versions of [[86-DOS]] to appear truncated. ==Notes== {{notelist}} ==References== {{reflist}} [[Category:86-DOS versions]]'