L}  a l0C)HCCH Vhhݩh `CmDiCD`   RP   * 1H@R! YH`CR  i   m G  GGpI0S S0  iIM֠  DDԙ`DOS SYS  J}  K)&IC )! J)L rK} I L(x  G )ޞޟL* }L$ ( LQ(  GLLC )`( VL 0΍ F Cd?   C}       3 nCD .CF V  LA! )?ݕ$ .}Rߐ) a$F@ЬL )Lݕ a )煮LFȘݕL  }  r LLQ )0>3  HCy  hy   )  L> LNn"JJ8`$F%G)( , }0 )8F$G%L\FCȱFDȱFE .CFȥDFȥEFF}FGiG8(() I rh   gI   }C H h nCd?    z  r V  g  z LL  GC ] )` ,E  r }C )E  z창0AMݙLݘ ML VNݕLLNLML  }B"'8 HH`/kn GF eK0%! F z F1FL    JK) }")1JJJ(>!   ]ޙޘG  F   H D D    } gLvuF rK LuF0MFɛֽA  z    v}FɛL FREE SECTORS C ) *Fȩ FȽ F FC  EHH HdHCD0I8HDCHIIIEE}FIhեH 0EFȩF`$0\:Ȣȱ$*?ȝd ?. ? [_{ 0: dй d }`L 4C 0)d?  08` I}IFFI F }0U `8FG eLl`(0   L   N  }0<I FJJݐ, QFȱFȱFHh0})Hh`LB!8`L F ` F8  eDii}( ɃжL !    `   8  eh  I  !` CJfCJfCJfCDFC`}    )8jHiPiJIjFIjFIjhFI  `  `  I I L8j Y  }8j Y  &I &I &IHeHIi   `!M"  ȹ L} FoG` e Ȍ 8 rI0 !M` cٵ`DOS SYSC ) 멧}C`0ؠX k  , /0 !LPp $  `DE` BHILV8hh}J ȱHȱIȱBȱDȱEeeHHLV n I * \*` 9`hh }HH` $ K   L}FԽ٩Յ׆ K ` SUލTp Z J0"` K0N}%$H Ph`֠XY / V0l֤׍TU؅֥مשؠΩл8֍X׍YXY1  $}` V0,0 Laв P,0 ބ,p&$ ޤ` S I0 K* H Sh`- I0' K *0} BLV F L50L#   P,p I0 0,  L7llԭ $ $lD}:AUTORUN.SYSD:MEM.SAVE:1D1:Dup.SYS:AUTORUN.SYSD:MEM.SAVE:1D1:Dup.SYS:AUTORUN.SYSD:MEM.SAVE:1D1:Dup.SYS:AUTORUN}1D2:DOS.SYS 1Need MEM.SAV!8آR'S ҩ0* (0M0,  (0 /(0(0ڭ) 1Error  }loading MEM.SAV!   MJS D  0 * ʈ }MYDOS 3.07 -- copyright 1983,˛DISKS: *1!}S A. Disk Directory I. Initialize DiskB. Run Cartridge J. Duplicate DiskC. Copy File(s) K"}. Save MemoryD. Delete File(s) L. Load MemoryE. Rename File(s) M. Run at AddressF. Lock File(s) N. Create MEM.SAVG. #}Unlock File(s) O. Change Config.H. Write DOS Files P. Drive Control P0 H Select Item ( for me$}nu):@  ,ɛLQ@  LNo such item!LN .!!"!"+"A"$$|%*+0,+)( @#(PMJH)0*0%}MJ!0j"0* 0hJJJ 0)HJ 0 0h i0L/Files to list, Destination? . 0 / S0۩کݩ΅ܢ0&}0 .de  A-LN Loading MEM.SAVII 1NO CARTRIDGE! LDelete what file? .'}Ni!RWFile to rename, new name? . R2Lock which file?#Unlock which file?$R . 0 .LN 0 TYPE 'Y'(} TO DELETE:! 30 - Delete   ? ,Y .L"L. I0L!File source, destination? 4 .1)}ڭ8ܭ1 00 .ߍeލdDЏ /X / S0ލ2ȱލ3ȱ4? :A*}0H* .@ ȱ.* #,ɛȝ  / - LN u2t3?5 .5Ƚ+}?5  .456  -->2 _o J 1 J0=0430`5,}u2tz0 A-L#LN L.Disk to FORMAT: k/ 0UTލ$ Type 'Y' to FORMAT drive 2: ,IYNj[-}R VL.LN Drive to write DOS files to? k/ލH1 /Z X0 Shp +UލT.}1٩ةLQ+Source, Destination (Sectors)? k/)(  e/)OO,0(/} Insert both disks, type ,L & / 0 0MM/(0 /MM 1Drives not compatible!Jj0}Hih(ɛy 1Invalid options! C.- C.)׍۩ک8* "'1} "'8*8ܭݥ1, 1Not enough memory! ک`;h   ,L.2}i N   ,  թԥԍՍ  1ՠ3}ԍ,0"  ,mm  "LN   /L',, Insert DESTINA4}TION disk, press ,N  1b 0 .ԭխ  L'Drive, (new density): 5}k/ɛލL 1Drive unchanged.ު)(0SDѩM)7 L Verify WRITEs? ,WnNPy Numb6}er of File Buffers? - C.  Allow fast WRITEs? ,ɛɠnNꎒ L7,R(0LN Drive number or 7}: ,ɛL")/ Ӎ(0 Remove drive? ,Y Is drive configurable? ,YЉ Is drive double sided? ,Y8} * Tracks/side? - C.#0M P( * Step rate? ,4/ * LN (0`SAVE:filename,start,end(,init9}(,run)) .TUH E.1p` + E.؆8֍ 1Invalid START-END range! E.  E.:} hԄՠAȌZ X00 K 0L L.֍׎`Load from what file? .TUIN;}Z X0- 4OL. 1Bad load file!Type 'Y' to create MEM.SAV file: ,Y  0 L.LN Run from w<}hat address? -ɛ E.$ 1Address must be 1-4 hex digits!L ,0Hɛ 9 9h` 9LN %H$H`=}( r (L.(`E(  , /@A J X00gHHIIDDEE B .CɈ=/>}  , /Bڤ 1ܝHݝI VL,L. H0 I! I 00LH /R XY . 9?}  .   .ʩ`ލDߍEBIʎH V0`ԩ ؠ>.ȱ?.ȱ)@}@. 1Error -- 128$8f E/ԄձG/ $;58i/Ԧ`H&եԦ&&eԅheԅԊe(iLO.&&&&A}ԅLO.0 - E/?*ɛ"./ލȱ.ɛލި0#:$Ȱ : ފ :B}ȱ:: U/ U/D U/ޥ`eޅީe߅`` .Ln/ .TUȪ: 1File name not allowed! InsC}ert SOURCE disk, press ,A(0OEJ!0j"0* 0 '0 Y0'S SL. iM`(D}@1O0 bdeD:ލJDEDȱ) 00 O JqOL.TUD 1Not aE} disk file!ȱ)  i ,0$L/ȱޙ:*șȩ`D:`OS.SYS,DOS.SYShh LN  1Error s _M_Y_D_O_S _3._0 User Guide G} Revision 3.07 Charles W. Marslett H} WORDMARK Systems 2705 Pinewood Dr. I} Garland, TX 75042 August 16, 1983 This information is disclJ}osed for the personal, private use of customers of WORDMARK Systems and their employees. WORDMARK K} Systems reserves the right to make changes to this document and to the product described at any time withouL}t further notice. The information in this document is believed to be accurate and reliable. HoweM}ver, no responsibility is assumed by WORDMARK Systems for its use; nor any infringements to copyrights, patenN}ts or rights of any third parties resulting from its use. O} _M_Y_D_O_S _3._0 User Guide Revision 3.07 P} Charles W. Marslett WORDMARK Systems 2705Q} Pinewood Dr. Garland, TX 75042 111111...... IIIIIINNNR}NNNTTTTTTRRRRRROOOOOODDDDDDUUUUUUCCCCCCTTTTTTIIIIIIOOOOOONNNNNN S} The two disk operating systems described in this manual are identical in usage and share common cT}ode for nearly all functions. The only significant difference a user of the MYDOS and ROMDOS opU}erating systems will notice is that the ROMDOS version will occupy significantly less memory (larger files mV}ay be edited, larger BASIC programs may be run, and some assembly language programs might run that wW}ould not otherwise). Both are modeled after the ATARI (trademark of Warner Communications, Inc.)X} disk operating systems (DOS and DOS II) and may be considered an extension of the very "user friendY}ly" concepts introduced with those two operating systems. For this reason the two DOSs documented heZ}re are identified as MYDOS 3.0 and ROMDOS 3.0. This version is the first to be released, but not the last. [} The ATARI 810 disk drive is well supported by the DOS II operating system, but it had limited pro\}vision for a double density disk system (the ATARI 815 dual drive system), and no provision at ]} all for a system that could change density dynamically (a "dual" density system). Since dual dens^}ity systems have now been manufactured for some time for the ATARI, and there does not appear to _}be an easy to use system to take full advantage of such a drive, WORDMARK Systems has developed a disk`} operating system to allow for dynamic density changes and larger capacity diskettes even in a single drive cona}figuration. 222222...... SSSSSSYYYYYYSSSSSSTTTTTTEEEEEEMMMMMM RRRRRb}REEEEEEQQQQQQUUUUUUIIIIIIRRRRRREEEEEEMMMMMMEEEEEENNNNNNTTTTTTSSSSSSc} The ROMDOS 3.0 operating system requires 8K of RAM and either the Newell Industries RAMRd}OD board for the ATARI 800 or the CDY adapter board for the ATARI 800 or ATARI 400 computers. MYDOS e}3.0 requires 16K of RAM (provided by most 400, and all 800 or 1200XL computers). Both require one ATARI 810 compaf}tible disk drive or disk controller. In addition, if the dynamic density control functions are useg}d, the controller must support the extended 810 interface described in Section 10. This extendedh} _M_Y_D_O_S _3_._0 User Guide Revision 3.07 i} - 2 - interface is supported by both the PERCOM dual density disk suj}bsystems and the ATR8000 disk/printer/RS232 controller manufactured by Software Publishers, Inc. k} Up to eight disk drives may be accessed, but only one is required. The resident part of the operal}ting systems (even the RAM resident MYDOS 3.0) takes less space than any other ATARI disk operatinm}g system and supports all documented functions of the DOS II operating system, so MYDOS 3.0 and ROMDOS 3.0 suppn}ort most available software for the ATARI home computers. The BASIC and Assembler/Editor Cartridges bo}oth take advantage of the added memory available, and APX Pascal, OSS BASIC A+, MEDIT and the AMACp} macro assembler all run from double density disks with no alterations or limitations. ATARI BASIC has overq} 32,000 bytes left in a 40K system, even with eight double density disk drives configured. The memoryr} occupied by the permanently resident part of MYDOS is $0700 to $1C00 and that part occupied by the utility s} program exchanged with the MEM.SAV file extends to $3100. A program loaded into the area $1C00 to t} $3100 must have its initialization or execution entry points included or the MEM.SAV file must be u}used. Otherwise, after loading the program the utility program will be loaded back in on top of the desv}ired program before it can be run. The memory available is only affected by the number of filesw} to be open concurrently: each disk file that may be open at the same time requires 256 bytes of buffex}r space. Memory requirements are independent of number of disk drives or the sector size (densityy}). 333333...... MMMMMMEEEEEENNNNNNUUUUUU FFFFFFUUUUUUNNNNNNCCCCz}CCTTTTTTIIIIIIOOOOOONNNNNNSSSSSS The menu provided by MYDOS 3.0 identifies 16 {}common tasks that might need to be done. Rather than having to write a utility program (only a few lin|}es of BASIC would perform most of the menu functions) or even remember the name and format of a DOS command, }} these tasks can be handled by entering the item identifier. MYDOS 3.0 responds with a question asking ~}for the details of the operation (which file, what density, are you sure or whatever else it mig}ht need to know). After you enter the remaining information, the function is performed and another prompt} is displayed. You should notice two interesting things about the menu, too: the second line on t}he screen identifies the disk drives present on the system and what they appear to MYDOS 3.0 to be }(single or double density). One of them (usually drive 1) will be marked with an '*' to indicated it is the _d}_e_f_a_u_l_t drive, or the drive that files are expected to be on if no disk drive is specifie}d in a command. The second thing to notice is that after commands fill the screen, the menu 'rolls' off the top: }some DOS programs keep the menu, MYDOS 3.0 does not in order to permit _M_Y_D_O_S _3}_._0 User Guide Revision 3.07 - 3 -} more information to retained on the screen when a long sequence of commands is needed to perfo}rm a function or when a directory is being listed or several files are being copied. To restore the} menu to the screen, just type _R_E_T_U_R_N and the initial screen is restored. Some co}mmands require further information to prevent accidental damage to your disk files: the 'I' command and the} 'J' command both require confirmation (through an additional key entry) before distroying the }destination disk. To abort either operation without damaging any existing disk files, simply press _R}_E_S_E_T or _B_R_E_A_K. The 'D', 'E', 'F' and 'G' commands (delete, rename, lock and unlock) al}l require an explicit file specification. All other commands will assume the drive marked in} the menu with '*' or all the files on that drive (depending on whether the command affects an entire drive or a f}ile set). Disk drive specifications and file specifications are made using the same rules: if} only a drive is specified and file data is required, all files on that drive (or in the case of the 'K' } and 'L' commands to save and load programs, the first file on that drive) will be the assumed choice. A } drive is specified with a ':' (meaning the default drive), a number (with or without a trailing ':')} or the letter 'D' followed by an optional number and a _r_e_q_u_i_r_e_d ':'. If you wish to specify }the file or set of files to be referenced, the drive format must include a ':' or it must be omitted } entirely -- D1:Test.obj, 1:TEST.ASM, or D2TEST (really D1:D2TEST) are valid file names, but d1:Test.obj or} 1TEST.ASM are not. The file name itself is either fully specified (refering to exact}ly one file on the disk) or includes _w_i_l_d _c_a_r_d_s (specifying a set of zero or more files). A} fully specified file name consists of one to eight characters followed by a period ('.') and ze}ro to three additional characters. The first character in the file name must be an upper or lower case } letter, an underscore ('_') or the characters '@' or '`'. The '`' is the ATARI diamond graphic. } The remaining character may be in that set or one of the digits 0-9. The 'wild card' characters are the } characters '*' and '?': the character '*' or the sequence '*.' end either the 8 character or the 3 characte}r field in the file name and match all possible characters. The character '?' matches any sin}gle file name character. If a disk directory includes the files TEST.ASM, TEST.OBJ, TEST.C, TEST.AL}M, TEASET.DOC, TRACE.FIL, and BETS.LST, the specification "t*.*" will not match any file name (sin}ce "t" and "T" are not the same letter to MYDOS 3.0). The specification "T**" will match all but "BETS}.LST" (since the others all begin with the letter "T"). The specification "?E??.*" will match the first four fil}es and the last one (since the 8 character part of the file name must have 4 _M_Y_D_O_S }_3_._0 User Guide Revision 3.07 - }4 - characters in it and the second must be an "E"). The specification "*?" will mat}ch only the file TEST.C (since it is the only file name with a single character in the 3 character }field). The specification "????E**" will match the files TEASET.DOC and TRACE.FIL and none of the other}s (since the 8 character part of the file name must have at least 5 characters and the fifth must }be an "E"). Where more than one file name is asked for, the first may be omitted by starting t}he response with a space or comma, and the last may be omitted by ending the line with a comma (the space } cannot be used here since trailing spaces are ignored). If both file names are entered, they may be separa}ted with either a space or a comma. Some commands may be _m_o_d_i_f_i_e_d using a letter } following the character '/' after the file name (for example, 1/A or D1:TEST/A). The letter used (the _m_}o_d_i_f_i_e_r) generally means the same thing if it is allowed. Invalid modifiers are always }ignored with no error indication at all. The modifier '/A' causes the results to be _a_p_p_e_n_d_e_}d to the end of an existing file. This is applicable to 'C' (copy) and 'A' (directory) commands. The} modifier '/N' causes the destination disk formatting to be skipped (saving about a minute) when used in the 'I}' (initialize) and 'J' (duplicate disk) commands. It prevents the questions asked before deleting} each file if it is used in the 'D' command (bending the rule only so recently mentioned). In both cases, } part of the function is skipped (see?). The '/X' command causes MYDOS 3.0 to pause at the end of each rea}d or write pass when copying data to allow you to change disks (permitting you to copy from one dis}k to another with a single drive, even if that drive appears to MYDOS 3.0 to be two drives). This option sup}ports disk drive that support increased capacity by making a single diskette appear to be on more} than one drive at a time, as well as disk drives that select density through the drive number (0-3 ar}e single density, 4-7 are double, for example, and drives 0 and 4 are the same physically). This also allows the } writing of a directory of one disk onto another as a file (use the command 'A' followed by the entry} "1,1:DRV01.dir/X") even with only a single drive on the system. The '/X' is assumed if only one file name } is entered in the copy command. This emulates the operation of the ATARI DOS II 'O' command which is} not implemented in MYDOS 3.0. 444444...... TTTTTTHHHHHHEEEEEE MMMMMME}EEEEENNNNNNUUUUUU CCCCCCOOOOOOMMMMMMMMMMMMAAAAAANNNNNNDDDDDDSSSSSS} 444444......111111 AAAAAA...... LLLLLLiiiiiisssssstttttt aaaaaa }DDDDDDiiiiiirrrrrreeeeeeccccccttttttoooooorrrrrryyyyyy oooooorrrrrr a}aaaaa SSSSSSeeeeeetttttt ooooooffffff FFFFFFiiiiiilllllleeeeeessssss} The 'A' command will list the files on a disk with their sizes, followed by a line specifyin}g the number of free sectors on the disk. If the line starts with an '*', the file has been _l_o_}c_k_e_d and may not be modified or deleted without first being _M_Y_D_O_S _3_._0 User Guide} Revision 3.07 - 5 - _}u_n_l_o_c_k_e_d. No indication is made of the type of file (ATARI DOS, ATARI DOS II, or MYDOS 3.0 are th}e three supported file formats). See Section 6 for further information if you need more info}rmation about the files than the 'A' command provides. This command will list the directory information to the s}creen if only one file specification is entered. If two are entered, the second is taken as a destinat}ion file and will be overwritten (or appended to) with the directory data: the entry "1,P:" will write } the directory of the disk on drive 1 to the printer, for example. 444444......222222 BBB}BBB...... RRRRRRuuuuuunnnnnn tttttthhhhhheeeeee CCCCCCaaaaaarrrrrrttt}tttrrrrrriiiiiiddddddggggggeeeeee The 'B' command returns control to the cart}ridge in the first cartridge slot. If no cartridge is present, an error is displayed, and nothing} happens. No additional information is required, so if a cartridge is present it is entered immediately. } 444444......333333 CCCCCC...... CCCCCCooooooppppppyyyyyy aaaaaa F}FFFFFiiiiiilllllleeeeee oooooorrrrrr aaaaaa SSSSSSeeeeeetttttt oooooof}fffff FFFFFFiiiiiilllllleeeeeessssss The 'C' command is used to make another }copy of one or more files of data. The two file specifications asked for after entering the 'C'} identify the source and the destination of the information being copied. Either may be fully specified dis}k file or a device specification (such as E:, P: or one of the RS232 ports R1: to R4:). The de}stination may be a set of disk files (specified with wild cards) only if the source specifies a file }name for the destination to use. Copies from a file set to a device will implicitly write consecutive files to }the device (generating a set of listings or a collection of cassette files for example). The source} may be a set and the destination a single disk file, but unless the '/A' modifier is specified to } append each copied file to the end of the previously copied files, only the last source file will rema}in on the destination disk. Note that the 'C' command always uses the full memory space } for a copy operation (unlike ATARI DOS II) and as a result, will always invalidate MEM.SAV if it is used. }Any pending program cannot be restarted after a 'C' or 'J' command. 444444......44444}4 DDDDDD...... DDDDDDeeeeeelllllleeeeeetttttteeeeee aaaaaa FFFFFFiiii}iilllllleeeeee oooooorrrrrr SSSSSSeeeeeetttttt ooooooffffff FFFFFFiiii}iilllllleeeeeessssss The 'D' command will remove all files that match the file } specification entered asking for confirmation before each one is removed. This verification that the file is r}eally the one to be removed can be disabled for the duration of this single 'D' command by adding} the file modifier '/N' to the end of the file specification. In this case, all the matching files will be} removed 'quietly' and the only further indication you will see is the prompt for the next command.} _M_Y_D_O_S _3_._0 User Guide Revision 3.07 } - 6 - 444444......555555 EEEEEE...... RRRRRReee}eeennnnnnaaaaaammmmmmeeeeee aaaaaa FFFFFFiiiiiilllllleeeeee oooooorrr}rrr SSSSSSeeeeeetttttt ooooooffffff FFFFFFiiiiiilllllleeeeeessssss } The 'E' command changes the name of the source file or files to match the specification in the destin}ation. Unlike the other commands, _t_h_e _d_e_s_t_i_n_a_t_i_o_n _s_p_e_c_i_f_i_c_a_t_i_}o_n _m_u_s_t _n_o_t _c_o_n_t_a_i_n _a _d_r_i_v_e _n_u_m_b_e_r, only a file name. } 444444......666666 FFFFFF...... LLLLLLoooooocccccckkkkkk aaaaaa F}FFFFFiiiiiilllllleeeeee oooooorrrrrr SSSSSSeeeeeetttttt ooooooffffff F}FFFFFiiiiiilllllleeeeeessssss The 'F' command limits access to the files identifie}d. The files may not be deleted, renamed, added to or replaced without being first unlocked with the} 'G' command. When a directory is listed, the files that have been locked using either the 'F' }command or the 'lock' or 'open locked' functions provided through CIO will be marked with an '*' in the first c}olumn. The files that are locked may be read or loaded and executed normally, only modification or rem}oval are prohibited. 444444......777777 GGGGGG...... UUUUUUnnnnnnllllll}oooooocccccckkkkkk aaaaaa FFFFFFiiiiiilllllleeeeee oooooorrrrrr SSSSSS}eeeeeetttttt ooooooffffff FFFFFFiiiiiilllllleeeeeessssss The '}G' command removes the limitations imposed on a file when it is 'locked' using the 'F' command. It does not al}ter the file or otherwise change the way the file is accessed or used. The same function may be pe}rformed in a program through the CIO function to 'unlock' a file. 444444......888888 }HHHHHH...... WWWWWWrrrrrriiiiiitttttteeeeee MMMMMMYYYYYYDDDDDDOOOOOOS}SSSSS 333333......000000 ttttttoooooo aaaaaa DDDDDDiiiiiisssssskkkkkk} The 'H' command is used to make a rebootable copy of the current MYDOS 3.0 files in memo}ry. The two files created or rewritten are 'DOS.SYS' and 'Dup.SYS'. 'DOS.SYS' is an image of the per}manently resident file management routine accessed through CIO and the small interface package that loads and save}s MEM.SAV (an image of the part of memory used to hold the nonresident part of MYDOS 3.0) and the } second part of MYDOS 3.0 itself ('Dup.SYS'). The file 'Dup.SYS' is a standard load file } containing the part of MYDOS 3.0 that is overwritten when a program is loaded into memory. Neither } of these files is compatible with any other disk operating system either for the ATARI or any }other home computer. Both should be treated as a single object. Never copy only DOS.SYS or only Dup.SYS to a dis }k without copying the other. The files written to the disk by the 'H' command will reflect the config }uration parameters currently in memory, which may be different from the ones active if the _R_E }_S_E_T key has not been pressed since modifying them. (See Section 9 for the definition of the con }figuration parameters provided in the system and how to specify a modified configuration.) } _M_Y_D_O_S _3_._0 User Guide Revision 3.07 } - 7 - 444444......999999 IIIIII...... IIII }IInnnnnniiiiiittttttiiiiiiaaaaaalllllliiiiiizzzzzzeeeeee aaaaaa DDDDD }Diiiiiisssssskkkkkkeeeeeetttttttttttteeeeee The 'I' command is used to p }repare a new disk for use with the MYDOS 3.0 operating system or to remove all the files on an old }disk. The result of the 'I' command is a completely empty disk. The only data on the diskette is that sy }stem provided information defining the space available and the empty directory entries. If the drive }number is followed by a '/N' modifier, the diskette will not be reformatted, but just 'erased'. This is the } recommended way to remove all the files on a diskette, rather than to use the 'D' command. }444444......111111000000 JJJJJJ...... DDDDDDuuuuuupppppplllllliiiiiic }cccccaaaaaatttttteeeeee aaaaaa DDDDDDiiiiiisssssskkkkkkeeeeeetttttttt }tttteeeeee The 'J' command copies all the information from one diskette to another. Th }e information on the diskette is identified by the MYDOS 3.0 bit map (on the VTOC sectors) if no sector range }is specified. If a range is specified, the data to be copied are the sectors in that range and } the VTOC is not examined. Specifying a sector range is done by adding two numbers seperated by a }dash and enclosed in parentheses to the end of the drive specification(s). For example, to copy sectors 1 }9 through 54 (tracks 1 through 3) from drive 1 to drive 3 the command line could be "1,3(19-54)". } If the destination disk is already a properly formatted MYDOS 3.0 diskette, the '/N' modifie }r may be entered after either drive number to skip the formatting of the destination drive. Otherwi }se, the destination diskette will be formatted before the data from the source is copied to it. That is, either }"1/N,2" or "1,2/N" will copy from drive 1 to drive 2 without first formatting the diskette in } drive 2. Note that the 'J' command, like that in ATARI DOS II, will use all of available memo }ry to duplicate the diskette: this means that if memory has been saved using the MEM.SAV file, it will no } longer be valid. Any pending program cannot be restarted after a 'C' or 'J' command. 444444 }......111111111111 KKKKKK...... SSSSSSaaaaaavvvvvveeeeee MMMMMMeeeeee }mmmmmmoooooorrrrrryyyyyy ttttttoooooo DDDDDDiiiiiisssssskkkkkk !} The 'K' command builds a binary load file containing the data from the memory area specified, as well as "} an initialization and a run vector address if specified. If the file is not to execute an ini #}tialization routine on being loaded, the initialization vector should be omitted. If it is not to run on $} being loaded, the run vector should also be omitted (and trailing commas need not be typed in either). %} If either vector is entered as zero, that vector will not be invoked when the program is loaded. &} Note that the starting and ending addresses of the _M_Y_D_O_S _3_._0 User Guide '} Revision 3.07 - 8 - program and (} the initialization and run entry points of the program are all specified as hex numbers. 444 )}444......111111222222 LLLLLL...... LLLLLLooooooaaaaaadddddd MMMMMMeee *}eeemmmmmmoooooorrrrrryyyyyy ffffffrrrrrroooooommmmmm DDDDDDiiiiiissss +}sskkkkkk The 'L' command takes a binary load file from the disk and loads it into memo ,}ry. The load file's initialization routine(s) will be executed and the program started at its run address -} unless the '/N' modifier is appended to the file name. 444444......111111333333 M .}MMMMM...... RRRRRRuuuuuunnnnnn aaaaaatttttt AAAAAAddddddddddddrrrrrree /}eeeessssssssssss The 'M' command is used to enter a program loaded without a run 0} address, or to jump into any program without the need for a return address. It may be used to restart the compu 1}ter (loading the AUTORUN.SYS file, if any) by specifying $E477 as the jump address. 4 2}44444......111111444444 NNNNNN...... CCCCCCrrrrrreeeeeeaaaaaatttttte 3}eeeee MMMMMMEEEEEEMMMMMM......SSSSSSAAAAAAVVVVVV The 'N' command is 4}used to put a file called 'MEM.SAV' onto the diskette in drive 1. This file will contain an image of the 5} part of memory occupied by the nonresident part of MYDOS 3.0 when it is loaded, and memory will be rest 6}ored from MEM.SAV when another program is given control of the system through the 'B' or 'L' commands 7} or by means of the _R_E_S_E_T key. Note that MEM.SAV does not contain an image of the part of memory u 8}sed to copy disks or files when the 'C' or 'J' commands are used. These commands invalidate the 9} MEM.SAV file. 444444......111111555555 OOOOOO...... SSSSSSyyyyyysss :}ssstttttteeeeeemmmmmm aaaaaannnnnndddddd DDDDDDrrrrrriiiiiivvvvvveeee ;}ee CCCCCCoooooonnnnnnffffffiiiiiigggggguuuuuurrrrrraaaaaattttttiiiiii <}oooooonnnnnn The 'O' command is used to specify the type (at least logically) =} of the disk drives on the ATARI computer. Additionally, it is used to specify the number of file bu >}ffers provided and to control writing to the disks (with or without verification). For owners of ?} early production 800 and 400 computers with the ATARI A revision OS ROMs this command is used to @} disable the 'fast write' algorithms that do not reliably work with those computers. The last three functions A}, which are not specified for individual drives, are selected by entering a _R_E_T_U_R_N w B}hen the prompt asking for a drive number is displayed. Three questions will then be asked: "Verify WRITEs" expec C}ts a 'Y' to be entered if all data written to the disk is to be read back to verify that it was not on D}ly written correctly, but that the data is in fact readable from the disk. The second question: E} "Number of File Buffers" expects a number, followed by a _R_E_T_U_R_N to specify the number of file buffe F}rs to be allocated. _T_h_i_s _d_o_e_s _n_o_t _a_f_f_e_c_t _t_h_e _c_u_r_r_e_n_t_l_y G}_u_s_e_d _b_u_f_f_e_r_s -- _i_f _t_h_i_s _c_o_u_n_t _i_s _c_h_a_n_g_e_d _t_h_e H}_c_h_a_n_g_e_d _D_O_S_3 _m_u_s_t _b_e _w_r_i_t_t_e_n _t_o _a _d_i_s_k _a_n_d _t_h_a_t I}_d_i_s_k _b_o_o_t_e_d _M_Y_D_O_S _3_._0 User Guide Revisi J}on 3.07 - 9 - _b_e_f_o_r_e _i_t _w_i_l_l _h_a_v_e K} _a_n_y _e_f_f_e_c_t! The third question, 'Fast WRITEs allowed?', should be answered 'Y' if the computer L}is an XL series computer or a 400 or 800 computer with the B-revision OS ROMs. If the computer is M}an early 400 or 800 computer with the A- revision ROMs the answer should be 'N' to disable the fast write N} algorithm because the A-revision ROMs do not allow the sector buffer to be located anywhere in memory. O}A _R_E_T_U_R_N does not retain the current value -- the result is NO as the answer to the 'Verif P}y WRITEs' question, and 3 buffers as the answer to the number of buffers question. Anything but a 'Y' will e Q}nable fast writes in response to the third question. If instead of a _R_E_T_U_R_N, a drive nu R}mber had been specified (one digit without a following _R_E_T_U_R_N) then that drive would be S}reconfigured. The first question identifies whether the drive is to be included in system initialization (and t T}hus be available for later use). If a non-existent disk is included it does not cause any problems wit U}h the system: it simply causes that disk to be examined each time the system is booted (adding perhaps a V} second to the time it takes to boot up DOS3). If drive is excluded from the system, no further q W}uestions are asked. Otherwise, the second question asks if the drive is configurable: that is, is it li X}ke the ATARI 810 or 815 drives (with a fixed configuration) or is it like the PERCOM or ATR8000 drives. If the Y} disk is not configurable it is assumed to be a 720 sector, single or double density ATARI 81x disk drive. Z} If the first two answers are 'N' (do not exclude the drive) and 'Y' (it is configurable), the co [}nfiguration is asked for: Is the drive double sided, how many tracks are there on the each side of \}the disk, and at what speed can it move the read/write head across the disk (what is its step rate). The first qu ]}estion is answered with 'Y' or 'N' ('Y' meaning 'yes' it is a double sided drive and diskettes format ^}ted on it will be double sided). The second question is answered with 35, 40, or 80 followed by a _R_ _}E_T_U_R_N if the disk drive is a 35 track, 40 track, or 80 track 5 1/4 inch floppy drive and with 77 if the `} drive is a standard 77 track 8 inch drive. No other number is accepted. The answer to this question a} specifies both the type of drive (8 inch or 5 1/4 inch) as well as the number of tracks per inch and total capacit b}y of the drive. This answer is _v_e_r_y _i_m_p_o_r_t_a_n_t to the operation of the drive. c} The last answer is entered as a code: use the following table and the drive specifications to determin d}e the proper value. _M_Y_D_O_S _3_._0 User Guide Revisio e}n 3.07 - 10 - Code value 8 inch rate 5 1/4 f} inch rate 0 3 ms/track 6 ms/track 1 6 ms/t g}rack 12 ms/track 2 10 ms/track 20 ms/track 3 q}?BDOS SYSB'Dup SYSbFMANUAL TXT 15 ms/track 30 ms/track 444444......111111666666 PPPPPP..... r}. DDDDDDeeeeeennnnnnssssssiiiiiittttttyyyyyy aaaaaannnnnndddddd DDDDDD s}eeeeeeffffffaaaaaauuuuuulllllltttttt DDDDDDrrrrrriiiiiivvvvvveeeeee S t}SSSSSeeeeeelllllleeeeeeccccccttttttiiiiiioooooonnnnnn The 'P' com u}mand is used to specify which disk drive is to be used when a menu command's file specification omits the drive v} information (the part of the file name before the ':'). Initially MYDOS 3.0 assumes this refers to d w}rive 1: the only one always present. To specify another, simply respond to the question 'Drive, (ne x}w density)?' with the desired 'default' disk drive. In addition, since the initialize command ('I') may be u y}sed to change the format of a diskette and does not provide for entering the density of the diskett z}e being formatted, the 'P' command may be used to set the sector size (and density) assumed for a di {}sk drive. Note that a copy to or from the disk drive set up with the 'P' command will override (and obliterate) th |}e effect of this command, as will a directory list or almost any command that accesses that disk driv }}e. If the density of a diskette is being changed, it is to be recommended that the density be set wit ~}h the 'P' command _i_m_m_e_d_i_a_t_e_l_y before the 'I' command is issued. 555555 }...... FFFFFFIIIIIILLLLLLEEEEEE MMMMMMAAAAAANNNNNNAAAAAAGGGGGGEEEEEER }RRRRR FFFFFFUUUUUUNNNNNNCCCCCCTTTTTTIIIIIIOOOOOONNNNNNSSSSSS PPPPPPRR }RRRROOOOOOVVVVVVIIIIIIDDDDDDEEEEEEDDDDDD TTTTTTHHHHHHRRRRRROOOOOOUUU }UUUGGGGGGHHHHHH CCCCCCIIIIIIOOOOOO MYDOS 3.0 supports all CIO calls supported by A }TARI DOS II, with the following modifications to the OPEN (function code 3) and the FORMAT (function }code 254) functions. The OPEN function in ATARI DOS II does not use the data provided in the } AUX2 byte, but in MYDOS 3.0 the AUX2 byte contains three flags that control the file format and whether it } will be created _l_o_c_k_e_d or not when the AUX1 byte is 8 or 9 (the file is opened for output o }r appending). If AUX2 bit 1 is set, the file will be written in the ATARI DOS (original) format }(unless the disk is double density: the original format is not viable for 256 byte sectors, when using doubl }e density disks, this bit is ignored). If AUX2 bit 2 is set, the file will be written in MYDOS 3. }0 format, and may contain sectors beyond absolute sector 1023. Such a file may not (easily) be read using } any ATARI or OSS DOS. If AUX2 bit 5 is set, the file will be written with the 'LOCKED' bit in the direc }tory set initially. This is provided for use by multi-tasking functions (such as a print spooler, se }quential file pre-reading function or other _M_Y_D_O_S _3_._0 User Guide } Revision 3.07 - 11 - enhancements one might want to make } to the standard OS or DOS provided functions). The FORMAT function in ATARI DOS II does not provid }e for any variations to the standard disk usage: in MYDOS 3.0, the contents of the AUX1 and AUX2 bytes ar }e used to specify the number of sectors on the disk being formatted and whether the disk needs to be } formatted by the controller as well as needing directory initialization. Bit 7 of AUX1 is set to ski }p the physical formatting of the entire disk surface when it is not required, and bits 6-0 of AUX1 } and all of AUX2 are used to specify the number of sectors on the disk being created (if all 15 bits are } zero, the disk is assumed to be a standard 720 sector disk with 719 usable sectors).. 666666. }..... DDDDDDIIIIIISSSSSSKKKKKK SSSSSSTTTTTTRRRRRRUUUUUUCCCCCCTTTTTTUU }UUUURRRRRREEEEEESSSSSS SSSSSSUUUUUUPPPPPPPPPPPPOOOOOORRRRRRTTTTTTIII }IIINNNNNNGGGGGG MMMMMMYYYYYYDDDDDDOOOOOOSSSSSS 333333......000000 } MYDOS 3.0 uses the first three sectors of a disk to hold some disk information and the initial boot }program if the drive contains DOS.SYS and Dup.SYS. Sector $168 (and sector $167 if the disk is forma }tted as a high capacity disk) is used to hold a bit map of available sectors and several flag byte identifying } the default format of files on the disk. Sectors $169 through $170 contain disk directory data, identi }fying the files on the disk, their sizes and their starting sector number. Note that this usage, } when the disk is declared to be DOS II compatible, is in fact exactly the same as ATARI DOS II would } make of the disk. The only significant change made when the high capacity format is chosen are that sector $167 } is also reserved for use by the system. The high capacity disk directory may be read by ATARI DOS } II, but the data in the files can only be accessed if it falls in the first 1023 sectors of the disk and } then only if the file number checking code in DOS II is disabled. This format and MYDOS 3.0 support accessing } disks of up to 4015 sectors of 256 bytes each. 777777...... MMMMMMYYYYYYDDDD }DDOOOOOOSSSSSS 333333......000000 MMMMMMEEEEEEMMMMMMOOOOOORRRRRRYYYYY }Y MMMMMMAAAAAAPPPPPP The MYDOS 3.0 disk operating system occupies the area from $0 }700 to $1B00 at all times, and when the menu is active, it also occupies the area from $1B00 to $2E00. In addition, } the first 13 bytes of the floating point workspace ($D4 - $E0) are used by MYDOS 3.0 at that time. }Unlike ATARI DOS II, MYDOS 3.0 also calls the floating point ROM entry points. _M_Y_D_O_S _ }3_._0 User Guide Revision 3.07 - 12 - } 888888...... RRRRRROOOOOOMMMMMMDDDDDDOOOOOOSSSSSS 333333......000 }000 MMMMMMEEEEEEMMMMMMOOOOOORRRRRRYYYYYY MMMMMMAAAAAAPPPPPP Th }e ROMDOS 3.0 disk operating system occupies the area from $0700 to $0AE0 at all times, and when the menu is activ }e it also occupies the area from $0AE0 to $1DE0. As does MYDOS 3.0, it uses the floating point ROM entry } points and 13 bytes of the floating point ROM workspace from $D4 to $E0. It also resides in a ROM oc }cupying the address range $C000-$CFFF. 999999...... CCCCCCUUUUUUSSSSSSTTTTTTOOOO }OOMMMMMMIIIIIIZZZZZZIIIIIINNNNNNGGGGGG AAAAAA SSSSSSYYYYYYSSSSSSTTTTT }TEEEEEEMMMMMM DDDDDDIIIIIISSSSSSKKKKKK 999999......111111 NNNN }NNuuuuuummmmmmbbbbbbeeeeeerrrrrr ooooooffffff FFFFFFiiiiiilllllleeeee }essssss OOOOOOppppppeeeeeennnnnn aaaaaatttttt OOOOOOnnnnnncccccceeeeee } The number of files that may be simultaneously open is set with the same byte as in ATARI DOS } II: location $0709 (decimal 1801). This byte contains a number from 0 to 16 setting the number of } disk files that may be open at the same time. Normally it is set to 3, the smallest number that supports al }l the functions in the MYDOS 3.0 menu. Specifically, a copy from one disk file to another requires th }ree open disk files. The value in the distributed version of MYDOS 3.0 is three, to permit more or fe }wer files, "poke" the value desired into location $0709 and press the _R_E_S_E_T key. This will then use the }new value to redefine the system. To permanently change the maximum number of files, use the 'H' co }mmand to write a modified MYDOS 3.0 system to a disk. 999999......222222 CCCCCCoo }oooonnnnnnttttttrrrrrroooooolllllllllllliiiiiinnnnnngggggg tttttthhh }hhheeeeee DDDDDDiiiiiisssssskkkkkk DDDDDDrrrrrriiiiiivvvvvveeeeeessss }ss AAAAAAcccccccccccceeeeeesssssssssssseeeeeedddddd bbbbbbyyyyyy MMMMM }MYYYYYYDDDDDDOOOOOOSSSSSS 333333......000000 Like ATARI DOS II, MYDOS 3.0 } automatically identifies the disk drives that are present when booted up initially and any time i }t is reinitialized (some programs do this on exiting to the DOS and it is always done if the _R_E_S_E_T key is } pressed. MYDOS 3.0 is distributed with drives 1 and 2 configured, all others are omitted in order }to speed up the booting process. To modify the maximum configuration MYDOS 3.0 will use, invoke the 'O' command } for each drive to be added to (or removed from) the system. Pressing the _R_E_S_E_T key will th }en use this value to redefine the system. To permanently change the maximum drive configuration, use } the 'H' command, writing a new copy of MYDOS 3.0 back to the system disk. 999999......333 }333 SSSSSSeeeeeelllllleeeeeeccccccttttttiiiiiinnnnnngggggg oooooorrrr }rr DDDDDDiiiiiissssssaaaaaabbbbbblllllliiiiiinnnnnngggggg WWWWWWrrrrr }riiiiiitttttteeeeee------wwwwwwiiiiiitttttthhhhhh------VVVVVVeeeeeer }rrrrriiiiiiffffffyyyyyy MYDOS 3.0 is distributed with all data written to the disk } read back to verify that it was not only written to the diskette correctly, but that there was not a problem }(dust, a scratch in the oxide coating, or some other problem that may have arisen since the diskett }e was formatted) that prevented the data from _M_Y_D_O_S _3_._0 User Guide } Revision 3.07 - 13 - being read back from the diskette. } If the programs being run have no long term value (games for example, often write daily high scores } to the disk, and loss of such data might result in a few screams or moans, but so does waiting for a slow update } of the scores after each game!). The byte at location $0779 (1913 decimal) controls all write } operations to the disk. If the value 'poked' into it is $57 (87 decimal), than all writes will be read bac }k to verify the action was successful. If the value 'poked' into $0779 is $50 (80 decimal) then } writes will be assumed successful, and will normally be performed in about one third the normal amount o }f time. This byte is defined, along with the count of the number of buffers to be allocated when the }file manager is initialized, whenever the 'O' command is invoked with no drive specified (only a _R_E_ }T_U_R_N is entered in response to the drive number query). 111111000000...... DDDDDDIII }IIISSSSSSKKKKKK DDDDDDRRRRRRIIIIIIVVVVVVEEEEEE IIIIIINNNNNNTTTTTTEEEE }EERRRRRRFFFFFFAAAAAACCCCCCEEEEEE ((((((vvvvvviiiiiiaaaaaa SSSSSSIIIII }IOOOOOO)))))) The physical disk drives and diskettes are external to the ATARI home c }omputers and the ones supported by MYDOS 3.0 are normally attached to the "serial interface connector" on t }he right side of the computer. The software in the operating system (OS ROMs) to access the devices atta }ched to that connector is call the "serial I/O driver" or SIO for short. The MYDOS 3.0 disk oper }ating system uses this lower level driver to pass all commands and information to and from the physical disk } drive. Several commands were defined by ATARI to communicate with the 810 disk drive and both PER }COM and Software Publishers, Inc., have adopted a slightly extended version of this set of commands. MYDO }S 3.0 will operate in a limited fashion with any disk system that supports the entire 810 set, but the full set of } commands is required to support all the functions. The minimum set of disk drive functions to supp }ort MYDOS 3.0 (or ATARI DOS II for that matter) are: Device Unit Command Direction Byte Ct. Aux. }Bytes Function $31 Drive# $21 From Drive 128/256 1 to 720 FORMAT DISK $31 Drive# $50 } To Drive 128/256 1 to 720 WRITE(no vfy) $31 Drive# $52 From Drive 128/256 1 to 720 READ } $31 Drive# $53 From Drive 4 1 to 720 READ STATUS $31 Drive# $57 To Drive 128/25 }6 1 to 720 WRITE(verify) The byte count is always 128 for a small sector drive, and is 128 for the } first three sectors (1, 2, and 3) of a large sector drive. All other sectors on a large sector drive are 256 } bytes long. _M_Y_D_O_S _3_._0 User Guide Revision 3.07 } - 14 - The FORMAT function is never called with a sector number not }in the range of 4 to 720. It expects 128 bytes from a small sector drive and 256 bytes from a large sec }tor drive. The first byte returned by the READ STATUS command is expected to indicate the sector size } -- if bit 5 is a 1 (bit 7 is the sign bit) then the sectors are large (256 bytes), otherwise, they are }small (128 bytes). The auxiliary bytes are treated as an address to a sector on the diskette, and ran }ge from 1 to 720 (when in DOS II compatible mode) or from 1 to 4015 (when accessing large capacity disk } drives). The additional functions used to configure disk drives dynamically are: Devi }ce Unit Command Direction Byte Ct. Aux. Bytes Function $31 Drive# $4E From Drive 12 1 to 7 }20 READ CFG. $31 Drive# $4F To Drive 12 1 to 720 WRITE CFG. These commands sup }port the 'P' command, permitting reconfiguration of a disk drive on demand: to format a diskette, } for example. These commands support identification of a disk drive as an 8 inch or double si }ded drive as well. The individual bytes are defined as follows: byte 0: Tracks per side (40 for a st }andard disk drive) byte 1: Disk Drive Step Rate (as defined by Western Digital) byte 2: Zero (high }byte of sectors/track) byte 3: Sectors/Track (18 for standard diskettes) byte 4: Side Code (0=singl }e sided, 1=double sided) byte 5: Disk Type Code -- bit 2: 0=single density, 1=double density } bit 1: 0=5 1/4 inch diskette, 1=8 inch diskette drive byte 6: High byte of Bytes/Sector (0 fo }r ATARI 810 compatible) byte 7: Low byte of Bytes/Sector (128 for ATARI 810) byte 8: Translation co }ntrol bit 7: 1=40 trk. disk I/O on an 80 trk. drive bit 6: Always 1 (to indicate drive }present) bit 1: 1=Handle sectors 1, 2, and 3 as full size sectors bit 0: 1=Sectors numb }er 0-17 (for example) not 1-18 bytes 9-11 are not used (and should be zero) An additional requirement }is that the disk drive automatically switch density if required to read sector 1. This is necessary if } one is to 'boot' either single or double density disks and is used by the MYDOS 3.0 system to automatica }lly set the drive _M_Y_D_O_S _3_._0 User Guide Revision 3.07 } - 15 - density from the menu handler. } _M_Y_D_O_S _3_._0 User Guide Revision 3.07 } - 16 - _I_N_D_E_X A-ROM (OS) support ......... 8 Dup.SYS }.................... 6 AMAC ....................... 2 duplicate a disk }ette ....... 7 assembly language .......... 2 erase all files ........ }.... 7 ATARI 810 .................. 1 ATARI 815 .................. 1 fast write ................ 12 } ATR8000 .................... 2 file buffers ............... 8 file }specification ......... 3 BASIC ...................... 2 file specification, default 3 } file specification, modifiers 4 buffer size ................ 2 file specification, omitt }ing 4 file specification, samples3-4 cartridge (running from MYDOS) 5 } files, locked ............ 5-6 changing MYDOS 3.0 permanently (SeefSielcetsi,onnu4m.b8e)r of .......... } 12 cold start, simulated ...... 8 files, system .............. 6 copy a boot file/diskette .. 7 }format a diskette .......... 7 copy a diskette ............ 7 copying files to same drive 5 high cap }acity disks ........ 1 copying files, single drive 5 copying files, two drive ... 5 initialize a dis }kette ...... 7 deleting files ............. 5 joining files .............. 5 directory list ........ }..... 4 directory list, to printer . 5 load memory ................ 8 disk drive, default ....... 10 } locking files .............. 6 disk drives, number of ... 1-2 disk status line ........... 2 MEDI }T ...................... 2 disk, default drive ........ 2 MEM.SAV .................. 5-8 DOS differe }nces ............ 1 memory required .......... 1-2 DOS II ..................... 1 menu, scrolling ......... }... 3 DOS, original ATARI ........ 1 menu, why use one? ......... 2 DOS.SYS .................... 6 } MYDOS 3.0 .................. 1 double density ............. 1 }drive access control ...... 12 naming files ............... 3 drive configurations, unusual 12 drive } specification ........ 3 OS ROM requirements ........ 8 drive specification, default 3 drives, ATARI } 810 .......... 9 Pascal ..................... 2 drives, ATR8000 ............ 9 PERCOM .................... }. 2 drives, configuring ..... 9-10 drives, ignoring ........... 9 prepare a diskette ......... 7 } drives, missing ............ 9 drives, PERCOM ............. 9 read a program from disk ... 8 du }al density ............... 1 remove all files ........... 7 _M_Y_D_O_S _3_._0 User Guide } Revision 3.07 - 17 - removing files ......... }.... 5 renaming files ............. 6 ROMDOS 3.0 ................. 1 run a program .......... }.... 8 run vector ................. 7 save memory ................ 7 save MYDOS to disk ...... }... 6 set density ............... 10 set sector size ........... 10 single drive copying ...... }. 4 single drive systems ....... 1 Software Publishers, Inc. .. 2 software supported ........ !}. 2 start a program (GOTO) ..... 8 start address .............. 7 system configuration ....... "}8 system files ............... 6 system files, format ....... 6 unlock files ............... 6 #} verify (write) ............. 8 wild cards in file names ... 3 wild cards ................. 5 $} write program to disk ...... 7 write system files ......... 6 write with verify ......... 12 %} _M_Y_D_O_S _3_._0 User Guide Revision 3.07 &} _C_O_N_T_E_N_T_S 1. INTRODUCTION ................................... '}.......... 1 2. SYSTEM REQUIREMENTS ...................................... 1 3. MENU FUNCTIONS .... (}....................................... 2 4. THE MENU COMMANDS ........................................ 4 )} 4.1 A. List a Directory or a Set of Files ............... 4 4.2 B. Run the Cartridge .............. *}.................. 5 4.3 C. Copy a File or a Set of Files .................... 5 4.4 D. Delet +}e a File or Set of Files .................... 5 4.5 E. Rename a File or Set of Files .................... 6 ,} 4.6 F. Lock a File or Set of Files ...................... 6 4.7 G. Unlock a File or Set of Fil -}es .................... 6 4.8 H. Write MYDOS 3.0 to a Disk ........................ 6 4.9 I. .}Initialize a Diskette ............................ 7 4.10 J. Duplicate a Diskette ........................... /}. 7 4.11 K. Save Memory to Disk ............................. 7 4.12 L. Load Memory from Disk 0} ........................... 8 4.13 M. Run at Address .................................. 8 4.1 1}4 N. Create MEM.SAV .................................. 8 4.15 O. System and Drive Configuration ............ 2}...... 8 4.16 P. Density and Default Drive Selection ............. 10 5. FILE MANAGER FUNCTIONS P 3}ROVIDED THROUGH CIO .............. 10 6. DISK STRUCTURES SUPPORTING MYDOS 3.0 ..................... 11 4} 7. MYDOS 3.0 MEMORY MAP ..................................... 11 8. ROMDOS 3.0 MEMORY MAP ..................... 5}............... 12 9. CUSTOMIZING A SYSTEM DISK ................................ 12 9.1 Number of 6}Files Open at Once ........................ 12 9.2 Controlling the Disk Drives Accessed by MYDOS 7} 3.0 ................................................. 12 9.3 Selecting or Disabling Write-with-Verify .. 8}.......... 12 10. DISK DRIVE INTERFACE (via SIO) .......................... 13 INDEX ................. 9}....................................... 16 - i -$ the drive. j