Atlas - README.DOC
Home / ext / JunkDrawer / DOS / BuildTools / v2.0 Lines: 1 | Size: 8832 bytes [Download] [Show on GitHub] [Search similar files] [Raw] [Raw (proxy)][FILE BEGIN]1 MSDOS 2.0 RELEASE 2 3 4The 2.0 Release of MSDOS includes five 5 1/4 double density single sided 5diskettes or three 8 iinch CP/M 80 format diskettes. 6 7The software/documentation on the five inch diskettes is arranged 8as follows: 9 101. DOS distribution diskette. This diskette contains files which 11 should be distriibuted to all users. This allows the DOS distri- 12 bution diskette to meet the requirements of users of high level 13 language compilers as well as users running only applications. 14 Many compilers marketed independently through the retail channel 15 (including those of Microsoft) assume LINK comes with the DOS, as 16 in the case of IBM. How you choose to distrubute BASIC (contracted 17 for separately) is up to you. 18 192. Assembly Language Development System diskette. This diskette 20 contains files of interest to assembly language programmers. 21 High level language programmers do not need these programs unless 22 they are writing assembly language subroutines. IBM chose to 23 unbundle this package from the DOS distribution diskette (except 24 for DEBUG), but you do not have to do so. 25 263. PRINT and FORMAT diskette. This diskette contains .ASM source 27 files which are necessary to assemble the print spooler, which you 28 may wish to customize for greater performance. .OBJ files are also 29 included for the FORMAT utility. 30 314. Skeltal BIOS and documentation diskette. This diskette contains 32 the skeltal BIOS source code and the SYSINIT and SYSIMES object 33 modules which must be linked with your BIOS module. The proper 34 sequence for linking is BIOS - SYSINIT - SYSIMES. 35 A profiler utiliity is also included on the diskette, but this 36 is not intended for end-users. This is distributed for use by 37 your development staff only and is not supported by Microsoft 38 If you do decide to distribute it, it is at your own risk! 39 40 415. Documentation. Features of 2.0 are documented on this disk. 42 43The user manual contains some significant errors. Most of these are 44due to last minute changes to achieve a greater degree of compatibility 45with IBM's implementation of MS-DOS (PC DOS). This includes the use 46of "\" instead of "/" as the path separator, and "/" instead of "-" 47as the switch character. For transporting of batch files across 48machines, Microsoft encourages the use of "\" and "/" respectively 49in the U.S. market. (See DOSPATCH.TXT for how you can overide this. 50The user guide explains how the end-user can override this in CONFIG.SYS). 51Both the printer echo keys and insert mode keys have now been made to 52toggle. The default prompt (this may also be changed by the user 53with the PROMPT command) has been changed from "A:" to "A>". 54We apologize for any inconveniences these changes may have caused 55your technical publications staff. 56 57 58Here is what you need to do to MSDOS 2.0 to create a shipable product: 59(see "Making a Bootable Diskette" below) 60 611. BIOS. If you have developed a BIOS for the Beta Test 2.0 version 62 You should link your BIOS module to SYSINIT.OBJ and SYSIMES.OBJ. 63 You must modify your BIOS to accomodate the call back to the BIOS 64 at the end of SYSINIT. If you have no need for this call, simply 65 find a far RET and label it RE_INIT and declare it public. 66 An example of this can be found in the skeletal BIOS. In addition 67 please add support for the new fast console output routine as 68 described in the device drivers document. We strongly recommend 69 that you adapt the standard boot sector format also described in 70 device drivers. Once again, please refer to the skeletal BIOS. 71 If you have not yet implemented version 2.0 please read the device 72 drivers document. Microsoft strongly recommends that machines 73 incorporating integrated display devices with memory mapped video 74 RAM implement some sort of terminal emulations through the use of 75 escape sequences. The skeletal BIOS includes a sample ANSI 76 terminal driver. 77 782. Please refer to DOSPATCH.TXT for possible changes you might wish 79 to make. We strongly recommend that you not patch the switch 80 characters for the U.S. market. Your one byte serial number 81 will be issued upon signing the license agreement. Please patch 82 the DOS accordingly. If you wish to serialize the DOS, this is 83 described in DOSPATCH.TXT. Please patch the editing template 84 definitions. Please note the addition of the Control-Z entry 85 at the beginning of the table. Also note that the insert switches 86 have now both been made to toggle. 87 883. Utilities. FORMAT must be configured for each specific system. 89 GENFOR is a generic example of a system independent format module, 90 but it is not recommended that this be distributed to your customers. 91 Link in the following order: FORMAT, FORMES, (your format module). 92 The print spooler is distributed as an executable file, which only 93 prints during wait for keyboard input. If you wish with your 94 implementation to steal some compute time when printing as well, 95 you will need to customize it and reassemble. Please note that 96 you can use a printer-ready or timer interrupt. The former is more 97 efficient, but ties the user to a specific device. Sample code 98 is conditionaled out for the IBM PC timer interrupt. 99 100The following problems are known to exist: 101 1021. Macro assembler does not support the initialization of 10-byte 103 floating point constants in 8087 emulation mode - the last two bytes 104 are zero filled. 105 1062. LIB has not been provided. The version which incorporates support 107 for 2.0 path names will be completed in a couple of weeks. The 108 1.x version should work fine if you cannot wait. Because the library 109 manager acts as a counterpart to the linker, we recommend that it 110 be distributed with the DOS distribution diskette as opposed to the 111 assembly language development system. 112 1133. International (French, German, Japanese, and U.K.) versions will be 114 available in several months. 115 1164. COMMAND.ASM is currently too large to assemble on a micro. It is 117 being broken down into separate modules so it can be asembled on 118 a machine. Source licensees should realize that the resultant 119 binaries from the new version will not correspond exactly to the 120 old version. 121 1225. If you have any further questions regarding the MSDOS 2.0 distribution 123 please contact Don Immerwahr (OEM technical support (206) 828-8086). 124 125 126 Sincerely yours, 127 128 129 Chris Larson 130 MS-DOS Product Marketing Manager 131 (206) 828-8080 132 133 134 135 BUILDING A BOOTABLE (MSDOS FORMAT) DISKETTE 136 137 1381. In implementing MSDOS on a new machine, it is highly recommended 139 that an MSDOS machine be available for the development. 140 Please note that utilities shipped with MSDOS 2.0 use MSDOS 2.0 141 system calls and WILL NOT not run under MSDOS 1.25. 142 1432. Use your MSDOS development machine and EDLIN or a word processor 144 package to write BOOT.ASM, your bootstrap loader BIOS.ASM and 145 your Format module. 146 1473. Use MASM, the Microsoft Macro-86 Assembler, to assemble these 148 modules. LINK is then used to link together the .OBJ modules in 149 the order specified. 150 1514. Link creates .EXE format files which are not memory image files 152 and contain relocation information in their headers. Since your 153 BIOS and BOOT routines will not be loaded by the EXE loader in 154 MSDOS, they must first be turned into memory image files by 155 using the EXE2BIN utility. 156 1575. The easiest thing to do is to (using your development machine) 158 FORMAT a single sided diskette without the system. Use DEBUG 159 to load and write your BOOT.COM bootstrap loader to the BOOT 160 sector of that diskette. You may decide to have your bootstrap 161 load BIOS and let the BIOS load MSDOS or it may load both. Note that 162 the Bootstrap loader will have to know physically where to go on 163 the disk to get the BIOS and the DOS. COMMAND.COM is loaded 164 by the SYSINIT module. 165 1666. Use the COPY command to copy your IO.SYS file (what the 167 BIOS-SYSINIT-SYSIMES module is usually called) onto the disk 168 followed by MSDOS.SYS and COMMAND.COM. You may use DEBUG 169 to change the directory attribute bytes to make these files hidden. 170 171CAUTION: 172 173At all times, the BIOS writer should be careful to preserve the state 174of the DOS - including the flags. You should be also be cautioned that 175the MSDOS stack is not deep. You should not count on more than one or 176two pushes of the registers. 177[FILE END](C) 2025 0x4248 (C) 2025 4248 Media and 4248 Systems, All part of 0x4248 See LICENCE files for more information. Not all files are by 0x4248 always check Licencing.