IMD 1.17: 23/10/2016 22:06:01 File generated by the HxC Floppy Emulator software v2.8.9.4  X- ؋FFFv3Pvv^FFFF= rߌȎ.OCopyright 1980, 1981, 1982, 1983, 1984 Intel Corporation program_version_number=V6.0program_name=iAPX 86, 88 Bootstrap LoaderX P.XYu P. vǹ4^&t&W&g&G>_u &S&/SYSTEM/RMX86UFfs1PP^&7Y:147750iRMX 86F03 VOL1 N 2 05 1   u.^GFF ^GFFf뺀>fs ^&?t F24]U>u.SP8.BDB&gOBDa6]UNN]UJ&FJF~t[FJJ&FJ t~t7NJ&w>F^YJ&FJ@JN럋]U_~L7t@~htA"^s~?t@~ytA"_FF&F$F "`FPR t&t t u ,PR^&?/u GPR$.06&W1P.SS^$1 t.0FY.&G&GT&G $1(&w&wQ*,6TP.SP/V1V;r܋.&8tLPS.@P5s62PRV.&TP&?/uGPRvVuw6TPa8X>XuX3hq6>hudXv>hpuL>6vh $iFj>iu`4:.8р>i@u><@봀>hu@t`:8X>hu+HF>6v~F&GFH>huaH`FbJL>6vGJ&GJLJZ\bJLJ;6\u;Zsh>6tj>at"P S6^`s8P^ S$P S6^]UQQ u~u!#P S6^>|u{u FFF F^6&6p6n^SSVnpu|tvx6x6v6(vx6&6x6v^SSvxvx(;~uezCz%e +e +e Cf44h%1e 8e 8e /0%=e Be Be + ,%Ge Ie Ie t @ )FV.Sv$+FVs.6$Pv.v0VFlnp6p6n6(npr|z~]UFf؋ʋFf‹]UFf‹]UF3vFv،]UFVv] 0123456789A%pe re re {%ye ze ze _%e e e %e e e e e e P= e e e %e e e >%e e e zz@6t抄;uJt@tzvx6x6vQKvxt;$u|(;~u r~~l;ru=l@lr|np6p6n6(np$;u;r)]U~u6&6,6*PS2Pvv6FVl$&(P`FV;Vu;Fs )FVlvv$&(P_rlnp6p6n6(np6r6(np6r$&(PN~+N~$9Vu9Fv.Sv$%Oe Qe Qe aP %We [e [e Y` %be de de p%ie ke ke  e e e g44he e e P;e e e <e e e %e e e  %e e e %e e e  %e e e YU++V%Se Ue Ue H %]e _e _e X%fe ie ie  %ne oe oe %e e e  %e e e %e e e 8 %e e e H%e e e NU %e e e ]%e e e _ek %e e e  lt %-e /e /e  %7e 9e 9e %@e Be Be  %Ie Ke Ke  8 %e e e 0 %e e e @%e e e P %e e e  `"%te ve ve  %|e ~e ~e 1  %e e e 6= %e e e  ?FJ%e e e X % e e e h%e e e x %e (e (e C"D%e e e v}  representing problem fixes replace the existing version of an object module in the library with the new fixed version. The update package contains an accumulation of all ZAPs issued against the current version of the iRMX~ 86 Operating System. Thus, when you install this update, you are assured that all current ZAPs have been applied to your system. (Previously applied ZAPs are re-applied when the new update is installed.) The iRMX~ 86 R6.0 UP3 Installation Guide describes the contents ofR?SPACEMAPR?FNODEMAPR?BADBLOCKMAPR?VOLUMELABELinstal.docread.me notes ed ptch86 zaps.cfg r6path.cfgs3path.cfgs4path.cfgr6gen.csds3gen.csds4gen.csdZBRA00.A86ZBRA00.CSDZBRA01.A86ZBRA01.CSDZBRA02.R86ZBRA02.CSDZBRA06.RMDZBRA06.CSDZBRA09.INCZBRA09.CSDZBRA11.RMDZBRA11.CSDZBRA14.RMD ZBRA14.CSD!ZBRA15.RMD"ZBRA15.CSD code on any of three types of development systems: an iRMX~ 86 R6.0 development system (System 300 Series microcomputer or a custom built system), an Intellec Series III development system, or a Series IV development system. The update package contains a generation submit file designed for each type of development system, plus two configuration files. One configuration file contains the pathnames for the iRMX~ 86 system files and the other contains the list of ZAPs being applied. Se Introduction The iRMX~ 86 Update Package is the mechanism Intel uses to distribute (1) fixes to reported software problems and (2) newly added iRMX~ 86 features. Intel refers to problem fixes and to newly added features as ZAPs. ZAPs reside on the update diskette as object modules. These object modules are automatically applied to your system when you install the update. ZAPs representing new features are simply added to the system library. ZAPs the iRMX~ 86 Update Package and explains how to install the update. The installation guide contains two sections. Section One describes the procedure for installing the update on each of the three types of Intel development systems. Section Two provides a brief overview of all of the ZAPs contained in the current update. Section One Installation Procedures The update package is designed to update your iRMX~ 86 R6.0 object#ZBRA16.R86$ZBRA16.CSD%ZBRA18.RMD&ZBRA18.CSD'ZBRA21.RMD(ZBRA21.CSD)ZBRA22.RMD*ZBRA22.CSD+ZBRA24.RMD,ZBRA24.CSD-ZBRA25.LIT.ZBRA25.CSD/ZBRA27.RMD0ZBRA27.CSD1ZBRA28.RMD2ZBRA28.CSD3ZBRA29.RMD4ZBRA29.CSDction 1.1 General Installation Notes Following is a list of the utilities used by the update package and their corresponding version numbers. UTILITY iRMX~ 86 Series III Series IV RUN ----- V2.0 ---- ASM86(.86) V2.0 V2.0 V2.0 LINK86(.86) V2.0 V2.0 V2.0 LIB86(.86) V2.1 V2.1 V2en.csd" is the generation submit file. This submit file will use the two configuration files: "r6path.cfg" and "zaps.cfg" to generate the application submit file "upr6.csd". The contents of "r6gen.csd" MUST NOT BE CHANGED. "r6path.cfg" is the pathname configuration file. This file contains the pathnames for the directories on your development system used by the update process. The pathnames in this file are a subset of those created by the installation process for Release 6. The pathnamities to determine whether both have been linked to the right version. (Use the Human Interface DIR command with the S option set.) A properly linked ASM86 V2.0 has a file size of 137,286 bytes; LINK86 V2.0 has a file size of 83,752 bytes. If any other file size is indicated, contact your local Intel representative. NOTE For Series III development system users, "PTCH86" and "ED" will have to be RENAMED to "PTCH86.86" and "ED.86" in o Basic I/O System and Device Drivers /rmx86/ios/ Extended I/O System /rmx86/eios/ Loaders /rmx86/loader/ System Debugger (SDB) /rmx86/sdb/ Human Interface /rmx86/hi/ Universal Development Interface (UDI) /rmx86/udi/ Crash Analyzer /rmx86/crash/ Filrface system commands using less memory, by manually copying the ZAP from the update package diskette to your "/system" directory. You will need to rename the ZAP file to the proper system command name. The minimum amount of memory for this is 1) 384K Bytes of memory in the system, and 2) a user's memory partition size (/config/terminals file) of at least 135K. There are three files on the update package diskette that you need to use: r6gen.csd, r6path.cfg, and zaps.cfg. "r6g.1 *PTCH86 V2.3 V2.3 V2.3 *ED V1.1 V1.1 V1.1 * The PATCH Utility (PTCH86) and ED editor (ED) are supplied on the Update diskette. NOTE To execute properly under iRMX~ 86 Release 6.0, the assembler (ASM86) and the linker (LINK86) must have been linked to Version 2.0 of the UDI interface libraries. You must check the size of these utiles can be changed (as described in Step 4) to reflect the names used in your system. The directory pathnames specified in "r6path.cfg" are: System files for Directory pathname Language Utilities /lang/ Human Interface system commands /system/ Nucleus /rmx86/nucleus/ Terminal Handler/Dynamic Debugger /rmx86/th/ rder to "RUN" properly. Refer to Step 2 in the instructions for Series III development system users. Section 1.2 Installing the Update on an iRMX~ 86 Development System The memory requirements for applying the entire update package are similar to the requirements for running the ICU. These requirements are: 1) a minimum of 512K Bytes of memory in the system, and 2) a user's memory partition size (/config/terminals file) of at least 235K. You can apply replacement Human Intees Utility /rmx86/files/ Interactive Configuration Utility (ICU) /rmx86/icu/ Include Files /rmx86/inc/ Interface Libraries /rmx86/lib/ "zaps.cfg" is the ZAP configuration file. This file contains the list of ZAPs to be applied. STEPS: 1) If your system files (e.g., "/rmx86/*") do not allow read, write or delete access to users other than uffects. 4) If your system uses the same iRMX~ 86 directory names as those listed above, then go on to Step 5. If your pathnames are not the same then you MUST edit the file "r6path.cfg". When editing this file, simply find the pathname that you need to change and modify it. THERE ARE THREE IMPORTANT RULES TO FOLLOW WHILE EDITING THE "r6path.cfg" FILE: (1) DO NOT change the order of the pathnames in this file. The  controls which ZAPs will be applied during the update process. At the beginning of the file is a block of comments. At the end of the file is a list of control lines. Each control line corresponds to one ZAP. For example, ZAP number 33 has a corresponding control line that reads "ZBRA33(PZZ03) *". The asterisk causes the ZAP to not be applied. Each of the ZAPs is described at the end of these instructions. The description will indis, you will not need the slash "/". 5) Invoke the submit file "r6gen.csd". There is one parameter. This parameter is the pathname for the directory that you created in Step 2. This directory MUST contain the contents of the update package diskette (be sure to include a slash "/" as the last character). This submit file will create the application submit file "upr6.csd". Example: "submit /rmx86/update/r6gen(/rmx86/updatemove the asterisk from the control line for that ZAP. IMPORTANT NOTE Some of the ZAPs supplied with this update default so that they are not applied during the update process. This is done when a ZAP has side effects. These ZAPs should only be installed if you need the feature or fix and have read the documentation concerning that ZAP. This documentation will explain the side eser O, then become the "super user" by executing the SUPER command and entering the correct password. The ZAP submit files need to access your iRMX~ 86 system files. 2) Copy the contents of the update package diskette onto your system. Intel recommends that you create a directory in your "/rmx86" directory called "update" and copy the contents there. 3) The ZAP installation procedure includes a file called "zaps.cfg". This file order is essential for the "r6gen.csd" generation submit file to work properly. (2) DO NOT remove any of the pathnames from this list. The number of pathnames in this file is essential for the "r6gen.csd" generation submit file to work properly. (3) When changing a directory name, you MUST put a slash "/" as the last character in the pathname. If you change the directory pathnames to logical namecate if the ZAP is defaulted to not be applied. You should read these descriptions so that you can decide which ZAPs you want to apply. If your decision matches the default, you can proceed to Step 4. If you decide to modify which ZAPs are applied, you MUST edit the file "zaps.cfg". To remove a ZAP that is to be applied, add an asterisk to the control line for that ZAP. Conversely, to apply a ZAP that is NOT to be applied, re/)" 6) Now invoke the application submit file "upr6.csd" created in Step 5. There are no parameters. Example: "submit /rmx86/update/upr6" NOTE: The warnings of "UNRESOLVED SYMBOLS" from the LINK86 utility are expected and should be ignored. 7) Now that the system files are updated, you will need to re-generate your iRMX~ 86 bootable system using ICU86. The system that you re-generate will then incorporate al Analyzer :F1: Files Utility :F1: Interactive Configuration Utility (ICU) :F1: Include Files :F1: Interface Libraries :F1: "zaps.cfg" is the ZAP configuration file. This file contains the list of ZAPs to be applied. STEPS: 1) The first step is to make a copy of the update package diskette. You caRLD has read only access. Section 1.3 Installing the Update on an ISIS Series III Development System There are three files on the update package diskette that you need to use: s3gen.csd, s3path.cfg, and zaps.cfg. "s3gen.csd" is the generation submit file. This submit file will use the two configuration files: "s3path.cfg" and "zaps.cfg" to generate and execute the application submit file "ups3.csd". The contents of "s3gen.csd" MUST NOT BE CHANGED.  copied the update package diskette to (Step 1), RENAME the file "PTCH86" to "PTCH86.86" and the file "ED" to "ED.86". 3) The ZAP installation procedure includes a file called "zaps.cfg". This file controls which ZAPs will be applied during the update process. At the beginning of the file is a block of comments. At the end of the file is a list of control lines. Each control line corresponds to one ZAP. For example, ZAP number 33 has a us :F1: Terminal Handler/Dynamic Debugger :F1: Basic I/O System and Device Drivers :F1: Extended I/O System :F1: Loaders :F1: System Debugger (SDB) :F1: Human Interface :F1: Universal Development Interface (UDI) :F1: Crashl of the ZAPs from this update package. Refer to Chapter 18 of the Release 6.0, iRMX~ 86 Configuration Guide for information on generating an iRMX~ 86 system. NOTE ON ACCESS RIGHTS: When the update process is complete, all iRMX~ 86 system files and libraries accessed by the update process will have the same access rights as set by the installation process for iRMX~ 86 Release 6.0. User 0 has all access rights, and user WOn copy it to a hard disk or make another floppy diskette. The device that you copy the contents to will be used by the update package (e.g., assembling, patching, linking). Therefore, be sure that the device is NOT write protected. 2) The two files "PTCH86" and "ED" on the update package diskette are used in the update process. These files need to be RENAMED in order to "RUN" properly on a Series III development system. On the device you "s3path.cfg" is the pathname configuration file. This file contains the devicenames for your development system. The devicenames can be changed (as described in Step 4) to reflect the devices used for your development work. The devicenames assumed for your Series III system: System files for Devicename Language Utilities (for Series III) :F0: ISIS II System Commands :F0: Nucle corresponding control line that reads "ZBRA33(PZZ03) *". The asterisk causes the ZAP to not be applied. Each of the ZAPs is described at the end of these instructions. The description will indicate if the ZAP is defaulted to not be applied. You should read these descriptions so that you can decide which ZAPs you want to apply. If your decision matches the default, you can proceed to Step 4. If you decide to modify which ZAPs ll need to re-generate your iRMX~ 86 bootable system using ICU86. The system that you re-generate will then incorporate all of the ZAPs you selected from this update package. Refer to chapter 18 of the Release 6.0, iRMX~ 86 Configuration Guide for information on generating an iRMX~ 86 system. NOTE The list of devicenames above does not contain a devicename for the Human Interface syst ZAP has side effects. These ZAPs should only be installed if you need the feature or fix and have read the documentation concerning that ZAP. This documentation will explain the side effects. 4) If your system uses the devicenames listed above, go on to Step 5. If your devicenames are not the same, you MUST edit the file "s3path.cfg". When editing this file, simply find the pathname that you need to change and modify it. nstalling the Update on a Series IV Development System There are three files on the Update Package Diskette that you need to use: s4gen.csd, s4path.cfg, and zaps.cfg. "s4gen.csd" is the generation submit file. This submit file will use the two configuration files: "s4path.cfg" and "zaps.cfg" to generate and execute the application submit file "ups4.csd". The contents of "s4gen.csd" MUST NOT BE CHANGED. "s4path.cfg" is the pathname configuration file. This file contains 5) Now invoke the submit file "s3gen.csd". There is one parameter. This parameter is the devicename where the contents of the update package diskette were copied to in Step 1. This device MUST contain the contents of the update package diskette. Example: "submit :F1:s3gen(:F1:)" NOTE: The warnings of "UNRESOLVED SYMBOLS" from LINK86 are expected and should be ignored. 6) Now that the system files are updated, you wiare applied, you MUST edit the file "zaps.cfg". To remove a ZAP that is to be applied, add an asterisk to the control line for that ZAP. Conversely, to apply a ZAP that is NOT to be applied, remove the asterisk from the control line for that ZAP. IMPORTANT NOTE Some of the ZAPs supplied with this update default so that they are not applied during the update process. This is done when aem commands. The Update Package submit files will not copy ZAPs that are Human Interface system commands onto your Series III development system. Depending on your application you will need to copy all ZAPs that are replacement system commands to your iRMX 86 System. Refer to the ZAP descriptions at the end of these instructions to see which ZAPs are replacement system commands. Section 1.4 I THERE ARE TWO IMPORTANT RULES TO FOLLOW WHILE EDITING THE "s3path.cfg" FILE: (1) DO NOT change the order of the devicenames in this file. The order is essential for the "s3gen.csd" generation submit file to work properly. (2) DO NOT remove any of the devicenames from this list. The number of devicenames in this file is essential for the "s3gen.csd" generation submit file to work properly. the pathnames for the directories on your development system used by the update process. These pathnames can be changed (as described in Step 4 below) to reflect the names used on your development system. The directory pathnames specified in "s4path.cfg" are: System files for Directory pathname Nucleus rmx86/nucleus/ Terminal Handler/Dynamic Debugger rmx86/th/ Basi Example: "createdir :RMX86:update" Then copy the contents of the update package diskette to this directory. 4) The ZAP installation procedure includes a file called "zaps.cfg". This file controls which ZAPs will be applied during the update process. At the beginning of the file is a block of comments. At the end of the file is a list of control lines. Each control line corresponds to one ZAP. For example, ZAP number 33 has a  rmx86/files/ Interactive Configuration Utility (ICU) rmx86/icu/ Include Files rmx86/inc/ Interface Libraries rmx86/lib/ "zaps.cfg" is the ZAP configuration file. This file contains the list of ZAPs to be applied. STEPS: Series IV development systems can be different, depending on the hardware configuration. Therefore, logical names are used by the  applied, you MUST edit the file "zaps.cfg". To remove a ZAP that is to be applied, add an asterisk to the control line for that ZAP. Conversely, to apply a ZAP that is NOT to be applied, remove the asterisk from the control line for that ZAP. IMPORTANT NOTE Some of the ZAPs supplied with this update default so that they are not applied during the update process. This is done when ctory that contains your system commands. (e.g., copy, delete, rename) :RMX86: = The directory ("rmx86") that contains the 13 directories in "s4path.cfg". Here is an example of how to define the logical name for the rmx86 directory, assuming your system device is "wini0": Example: "lname define :RMX86: for /wini0/rmx86" 3) Create a directory in the "rmx86" directory called "update". c I/O System and Device Drivers rmx86/ios/ Extended I/O System rmx86/eios/ Loaders rmx86/loader/ System Debugger (SDB) rmx86/sdb/ Human Interface rmx86/hi/ Universal Development Interface (UDI) rmx86/udi/ Crash Analyzer rmx86/crash/ Files Utility  corresponding control line that reads "ZBRA33(PZZ03) *". The asterisk causes the ZAP to not be applied. Each of the ZAPs is described at the end of these instructions. The description will indicate if the ZAP is defaulted to not be applied. You should read these descriptions so that you can decide which ZAPs you want to apply. If your decision matches the default, you can proceed to Step 5. If you decide to modify which ZAPs are update package. 1) If your iRMX~ 86 system files (e.g., "rmx86/*") are only accessible by superuser, then you will need to logon as superuser. The ZAP command files need to access your iRMX~ 86 system files. 2) Assign the following logical names using the "LNAME" system command: :LANG: = The directory that contains your language utilities. (e.g., ASM86, LINK86, LIB86) :SYSTEM: = The direa ZAP has side effects. These ZAPs should only be installed if you need the feature or fix and have read the documentation concerning that ZAP. The documentation will explain the side effects. 5) If your system uses the same iRMX~ 86 directory names as described above and you used the logical names described in Step 2, go on to Step 6. If your pathnames are not the same, you MUST edit the file "s4path.cfg". When editing es will not copy ZAPs that are Human Interface system commands onto your Series IV development system. Depending on your application you will need to copy all ZAPs that are replacement system commands to your iRMX~ 86 System. Read the ZAP descriptions at the end of these instructions to see which ZAPs are replacement system commands. Section 2 The iRMX~or the "s4gen.csd" generation submit file to work properly. (3) When changing a directory name, you MUST put a slash "/" as the last character in the pathname. If you change the directory pathnames to logical names, you will not need the slash "/". 6) Now invoke the submit file "s4gen.csd". There is one parameter. This parameter is the pathname for the directory that you created in Step 3. This direct upper right hand corner. Description: This document introduces the iRMX~ 86 Release 6 Update 3 product. It also serves as an entry point into the documentation, indicating where to find vital information concerning Update 3. Re-Ordering: Not available for re-ordering The iRMX 86 R6.0 UP3 Installation Guide (Order #147731-001) Appearance: A double-sided, five-hole punched document stapled in ll then incorporate all of the ZAPs from this update package. Refer to Chapter 18 of the Release 6.0, iRMX~ 86 Configuration Guide for information on generating an iRMX~ 86 system. NOTE The list of directory names in the instructions for Series IV development system users does not contain a directory name for the Human Interface system commands. The update package submit filthis file, simply find the pathname that you need to change and modify it. THERE ARE THREE IMPORTANT RULES TO FOLLOW WHILE EDITING THE "s4path.cfg" FILE: (1) DO NOT change the order of the pathnames in this file. The order is essential for the "s4gen.csd" generation submit file to work properly. (2) DO NOT remove any of the pathnames from this list. The number of pathnames in this file is essential f 86 Update 3 Documentation The iRMX~ 86 Update 3 is supported by two types of documentation--printed documents that accompany the Update 3 diskettes and files that reside on Update 3 Diskette No.1. 2.1 Printed Documentation Each iRMX~ 86 Update 3 package includes a shrinkwrapped package containing the following five items of printed documentation: The iRMX 86 Release 6 Update 3 Customer Letter Appearance: A three-page single-sided document stapled in the ory must contain the contents of the update package diskette (be sure to include a slash "/" as the last character). Example: "submit :RMX86:update/s4gen(:RMX86:update/)" NOTE: The warnings of "UNRESOLVED SYMBOLS" from LINK86 are expected and should be ignored. 7) Now that the system files are updated, you will need to re-generate your iRMX~ 86 bootable system using ICU86. The system that you re-generate wi the upper right hand corner. The front and back covers are white. Description: This document contains instructions for installing the update on an iRMX~ 86 Development System, an ISIS Series III Development System, and a Series IV Development System. In addition, it describes all of the ZAPs contained in Update 3. The contents of this document are duplicated in  Available through Intel's Literature Department (address below). iRMX 86 Release 6 Documentation Change Package: Update 3 (Order #147540-001) Appearance: A shrinkwrapped package containing double-sided five-hole punched change pages. The front and back cover are blue. Description: This package contains change pages to be installed in the existing iRMX~ 86 Release 6 Operating System  FORMAT command and the Disk Verification Utility. These enhancements offer two new iRMX~ 86 capabilities--the capability of backing up and restoring volume fnodes, and the capability of adding the second stage of the Bootstrap Loader to a volume without re-formatting the volume. This document (along with the associated software) was first distributed in Bowers Avenue Santa Clara, CA 95051 2.2 Documentation Residing in Update 3 Files The Update 3 Diskette No. 1 contains the following three documentation files: READ.ME The READ.ME file (1) describes workarounds for problems discovered in the iRMX~ 86 Release 6.0 Operating System software (2) provides vital information that is missing from the iRMX~ 86 Release 6.0 Operating System documentation. All items in this file are temporary. An item remDescription: This package contains change pages to be installed in the existing iRMX~ 86 Release 6 Operating System documentation. These change pages provide documentation to support the device drivers currently distributed through the iRMX~ 86 Updates. Instructions for installing the change pages are printed on a blue sheet at the front of the package. Re-Ordering:a file named INSTAL.DOC on Update diskette No. 1. Re-Ordering: Not available for re-ordering FORMAT Command and Disk Verification Utility Enhancements (Order #147155-001) Appearance: A double-sided, five-hole punched document stapled in the upper right hand corner. The front and back covers are white. Description: This document provides information about enhancements made to the documentation. These change pages correct technical errors identified in the documentation. Instructions for installing the change pages are printed on a blue sheet at the front of the package. Re-Ordering: Available through Intel's Literature Department (address below). Items may be re-ordered by contacting: Intel Corporation Literature Department 3065 Update 1 (June, 1984). If you have received Update 1 or Update 2, you already have a copy. Re-Ordering: Available through Intel's Literature Department (address below). iRMX 86 Device Driver Change Package: Update 3 (Order # 147721-001) Appearance: A shrinkwrapped package containing double-sided five-hole punched change pages. The front and back cover are blue. ains in the file only as long as the associated problem is unfixed. Once a fix is available through the update service (either as a ZAP or as change pages to the documentation), the item is removed from the READ.ME file. NOTES The NOTES file contains (1) general background information about the iRMX~ 86 Release 6.0 Operating System, and (2) an outline of some of the major differences between iRMX~ 86 Release 6.0 and iRMX~ 86 Release 5.0. Items in the NOT problem. Installing this ZAP will cause Utilities which use UDI calls to always reserve 12K Bytes of RAM for work files. This ZAP will become obsolete as soon as the next version of the assembler is released. ZBRA02.R86 DATE: 20 APRIL 1984 PRODUCT: iRMX 86 R6.0, Human Interface V3.0 REPLACEMENT SYSTEM COMMAND: hrest.r86 (RESTORE) DESCRIPTION: This ZAP is for the RESTORE system command. This ZAP fixes the problem in RESTORE that returned anrinted document titled "The iRMX~ 86 R6.0 UP3 Installation Guide". Section Three ZAP Descriptions The next section of this document is the list of ZAPs and their descriptions. Read this section to determine which ZAPs you want to have applied to your system. Pay special attention to "SPECIAL NOTES" and "SIDE EFFECTS". Unless stated otherwise, the default condition for a ZAP is that it will be installed during the upda DATE: 20 APRIL 1984 PRODUCT: iRMX 86 R6.0, SDB V3.0 REPLACEMENT MODULE: sdbint in sdb.lib DESCRIPTION: This replacement module corrects the SDB's help screen sign-on message to reflect V3.0. ZBRA09.INC DATE: SEPTEMBER 1984 PRODUCT: iRMX 86 R6.0, BOOTSTRAP LOADER V6.0 REPLACEMENT INCLUDE FILE: BS1DEV.INC DESCRIPTION: This replacement include file fixes a problem which occured when using only %AUTO without %CONSOLE or %MANUAL. This  PRODUCT(S): iRMX 86 R6.0, UDI V3.0 REPAIR LIBRARY(MODULE): udi.lib(uxclsv) DESCRIPTION: If the assembler (ASM86 V2.0) runs out of memory and has to create a work (spill) file, it will abort with an E$MEM exception. This ZAP adds code to UDI to call DQ$RESERVE$IO$MEMORY before the assembly starts. This will allow the assembler to create work (spill) files if it needs to. SIDE EFFECTS: This ZAP should only be applied if you are experiencing the aboveES file accumulate from update to update. Thus, in addition to the notes added in Update 3, the NOTES file also contains the notes from all previous updates. INSTAL.DOC The INSTAL.DOC file contains instructions for installing the update on an iRMX~ 86 System, an ISIS Series III Development System, and a Series IV Development System. In addition, it describes all of the ZAPs contained in Update 3. The contents of this file are duplicated in an Update 3 p E$MEM when restoring multiple volumes. SPECIAL NOTES: This copy of the RESTORE system command is V3.1 (the sign-on message reflects this). If you are using a Series III or Series IV development system, you will have to copy this replacement system command to your target system manually. The application submit files ups3.csd and ups4.csd will not copy replacement system command ZAPs to your Series III or Series IV development system. ZBRA06.RMD te process. ZBRA00.A86 DATE: 11 April 1984 PRODUCT(S): iRMX 86 R6.0, UDI V3.0 REPAIR LIBRARY(MODULE): udi.lib(udures) DESCRIPTION: This ZAP solves the problem of the FORTRAN compiler not being able to run on iRMX~ 86 R6.0. SPECIAL NOTES: This ZAP only applies to Fortran V2.2 that is linked with UDI V2.0. This ZAP will become obsolete as soon as the next version of the compiler is released. ZBRA01.A86 DATE: 12 APRIL 1984 produced errors during the assembly of the module BS1.A86. ZBRA11.RMD DATE: SEPTEMBER 1984 PRODUCT: iRMX 86 R6.0, UDI V3.0 REPLACEMENT MODULE: udufil in udi.lib DESCRIPTION: This replacement module fixes a problem where DQ$FILE$INFO returns erroneous information about a file's owner id and file type. ZBRA14.RMD DATE: SEPTEMBER 1984 PRODUCT: iRMX 86 R6.0, IOS V4.1 REPLACEMENT MODULE: ilnmat in ios.lib DESCRIPTION: This rDUCT: iRMX 86 R6.0, HI V3.0 REPLACEMENT SYSTEM COMMAND: hdvfy.r86 (DISKVERIFY) DESCRIPTION: This ZAP is the DISKVERIFY system command. Features were added to DISKVERIFY to manipulate the "R?SAVE" file created by the new FORMAT system command. DISKVERIFY contains a command to copy fnodes to the R?SAVE file. Also the volume label and fnodes can be restored by copying them from R?SAVE over the original fnodes and volume label. See the enclosed manual "FORMAT must be used in conjunction with ZBRA14.RMD to fix the problem. ZBRA16.R86 DATE: SEPTEMBER 1984 PRODUCT: iRMX 86 R6.0, HI V3.0 REPLACEMENT SYSTEM COMMAND: hform.r86 (FORMAT) DESCRIPTION: This ZAP is the FORMAT system command. It has two new features: 1) FORMAT can now copy the 2nd stage of the Bootstrap Loader onto track 0, without formatting the volume. This enables a user to put the capabilities of the Release 6.0 Bootstraelopment system. ZBRA18.RMD DATE: SEPTEMBER 1984 PRODUCT: iRMX 86 R6.0, HI V3.0 REPLACEMENT MODULE: hgtchr in hi.lib DESCRIPTION: This replacement module corrects a problem where DQ$GET$ARGUMENT does not handle buffers ending with double delimiters correctly. It also corrects a problem which prevents TX from accepting one character filenames. SPECIAL NOTES: This ZAP must be used in conjunction with ZBRA68.RMD to fix the problem.  SPECIAL NOTES: This copy of the FORMAT system command is V3.1 (this can be displayed using the VERSION system command). If you are using a Series III or Series IV development system, you will have to copy this replacement system command to your target system manually. The application submit files ups3.csd and ups4.csd will not copy replacement system command ZAPs to your Series III or Series IV development system. ZBRA17.R86 DATE: SEPTEMBER 1984 PROeplacement module fixes a problem where a file cannot be deleted if its fnode has been corrupted. SPECIAL NOTES: This ZAP must be used in conjunction with ZBRA15.RMD to fix the problem. ZBRA15.RMD DATE: SEPTEMBER 1984 PRODUCT: iRMX 86 R6.0, IOS V4.1 REPLACEMENT MODULE: ispath in ios.lib DESCRIPTION: This replacement module corrects a problem where a file cannot be deleted if its fnode has been corrupted. SPECIAL NOTES: This ZAP Command and Disk Verification Utility Enhancements" for a full description. SPECIAL NOTES: This copy of the DISKVERIFY system command is V3.1 (the sign-on message reflects this). If you are using a Series III or Series IV development system, you will have to copy this replacement system command to your target system manually. The application submit files ups3.csd and ups4.csd will not copy replacement system command ZAPs to your Series III or Series IV devp Loader (specifically the debug switch) onto a volume without having to re-format it. 2) FORMAT can now (while formatting the disk) create a file named R?SAVE. The volume label and the fnodes are then copied to this file. This feature works in conjunction with the enhanced DISKVERIFY system command (see next ZAP description). See the enclosed manual "FORMAT Command and Disk Verification Utility Enhancements" for a full description.   ZBRA19.RMD DATE: SEPTEMBER 1984 PRODUCT: iRMX 86 R6.0, UDI V3.0 REPLACEMENT MODULE: uduarg in udi.lib This ZAP has been replaced by ZBRA68.RMD. ZBRA21.RMD DATE: DECEMBER 1984 PRODUCT: iRMX 86 R6.0, DEVICE DRIVERS V2.0 (iSBC 544) REPLACEMENT MODULE: x544 in xcmdrv.lib DESCRIPTION: This ZAP fixes the iSBC 544 driver problem where a series of successive interrupts could result in a stack overflow that caused the system to crash. RMD and ZBRA29.RMD. These ZAPs MUST be included or excluded from the update process as a group. ZBRA28.RMD DATE: DECEMBER 1984 PRODUCT: iRMX 86 R6.0, DEVICE DRIVERS V2.0 (TERMINAL SUPPORT CODE) REPLACEMENT MODULE: xtsmod in xcmdrv.lib DESCRIPTION: See ZBRA27.RMD. SPECIAL NOTES: This ZAP is intended to be used in conjunction with ZBRA27.RMD and ZBRA29.RMD. These ZAPs MUST be included or excluded from the update process as a group. ZBRrs a problem where the UDI DQ$SPECIAL call would corrupt the status of the output control character when the call was made with mode equal to 1 or 3. This would result in flow control being defeated and screen oriented applications garbaging the display on the screen. ZBRA24.RMD DATE: DECEMBER 1984 PRODUCT: iRMX 86 R6.0, EIOS V3.0 REPLACEMENT MODULE: hybriddetachdevice in eios.lib DESCRIPTION: This ZAP fixes a problem where RQ$HYBRID$DETACH$DEVICE  DESCRIPTION: This replacement system command fixes a problem with supplying user jobs to the ICU. If the user supplied a user job, the ICU would add it to the boot image library last. If the job was written as a main module, the boot loader would pick up it's start address, overriding the root job's starting address. The result was that the bootloader would give control to the user job instead of the root job. The most likely consequence was that the system would lib DESCRIPTION: This ZAP fixes a problem where the hardware would always be reset when an RQ$A$SPECIAL, an RQ$S$SPECIAL, or a DQ$SPECIAL call was made. If output was pending, it would result in garbage characters being output. With this ZAP and ZAPs ZBRA28.RMD and ZBRA29.RMD the hardware is only reset if the input or output baud rate or the read or write parity are being modified. SPECIAL NOTES: This ZAP is intended to be used in conjunction with ZBRA28. SPECIAL NOTES: The iSBC 544 driver can still lose characters and experience communication errors. This can happen when large quantities of data are input to the iSBC 544 at high data rates or over multiple channels. If you need specific information about performance data, please contact your local Intel representative. ZBRA22.RMD DATE: DECEMBER 1984 PRODUCT: iRMX 86 R6.0, UDI V3.0 REPLACEMENT MODULE: uduspl in udi.lib DESCRIPTION: This ZAP repaiA29.RMD DATE: DECEMBER 1984 PRODUCT: iRMX 86 R6.0, DEVICE DRIVERS V2.0 (TERMINAL SUPPORT CODE) REPLACEMENT MODULE: xtsosc in xcmdrv.lib DESCRIPTION: See ZBRA27.RMD. SPECIAL NOTES: This ZAP is intended to be used in conjunction with ZBRA27.RMD and ZBRA28.RMD. These ZAPs MUST be included or excluded from the update process as a group. ZBRA30.R86 DATE: DECEMBER 1984 PRODUCT: iRMX 86 R6.0, ICU V2.1 REPLACEMENT COMMAND: icu86.r86  fails when called by user 0. The exception E$TYPE would be returned erroneously. ZBRA25.LIT DATE: DECEMBER 1984 PRODUCT: iRMX 86 R6.0, IOS V4.1 REPLACEMENT LITERAL FILE: iexcep.lit DESCRIPTION: This ZAP corrects the spelling of E$IDDR in the literal file IEXCEP.LIT. It was incorrectly spelled as E$IDD. ZBRA27.RMD DATE: DECEMBER 1984 PRODUCT: iRMX 86 R6.0, DEVICE DRIVERS V2.0 (TERMINAL SUPPORT CODE) REPLACEMENT MODULE: xtsio in xcmdrv.  not boot. This version of the ICU puts the user jobs first in the boot image library. An additional feature of this version of the ICU is support for the iSBC 188/48 driver (see ZBRA42.LIB). SPECIAL NOTES: This version of the ICU is version 2.1. The version number of the ICU can be displayed with the VERSION command. This ZAP is intended to be used in conjunction with ZBRA31.HLP, ZBRA40.R86 and ZBRA41.LIT. These ZAPs MUST be included or excluded from the  system manually. This update includes change pages for the Operator's Reference manual that describe how to use this command. ZBRA40.R86 DATE: DECEMBER 1984 PRODUCT: iRMX 86 R6.0, ICU V2.1 REPLACEMENT COMMAND: icu862.r86 DESCRIPTION: This ZAP replaces the second stage of the ICU with version 2.1. See ZBRA30.R86 for more information. SPECIAL NOTES: This version of the ICU second stage is version 2.1. The version number of the ICU second stageTE: DECEMBER 1984 PRODUCT: iRMX 86 R6.0, DEVICE DRIVERS V2.0 (iSBC 215/218) REPLACEMENT MODULE: xtflop in xcmdrv.lib DESCRIPTION: This ZAP alters the iSBC 215/218 driver to allow reading and writing of 9 sectors per track on a 5 1/4" uniform diskette that is attached "physical". The ZAP will not supply formatting capabilities, only read and write. SPECIAL NOTES: The default for this ZAP is to not be installed. SIDE EFFECTS: A system generated with this ch is V2.1. For more information see ZBRA30.R86. SPECIAL NOTES: This ZAP is intended to be used in conjunction with ZBRA30.R86, ZBRA31.HLP and ZBRA40.R86. These ZAPs MUST be included or excluded from the update process as a group. ZBRA42.LIB DATE: DECEMBER 1984 PRODUCT: iRMX 86 R6.0, DEVICE DRIVERS V2.1 (iSBC 188/48) NEW LIBRARY: x18848.lib DESCRIPTION: This ZAP provides support for the iSBC 188/48. SPECIAL NOTES: ZAPs ZBRA30.R86, ZBRA31.HLP, ZBRAnot apply this ZAP, the system that you generate can only access 8 sectors per track for this type of diskette. ZBRA34.R86 DATE: DECEMBER 1984 PRODUCT: iRMX 86 R6.0, ZSCAN V3.0 NEW SYSTEM COMMAND: zscan.r86 DESCRIPTION: This new command displays a list of all ZAPs applied to a system image (library) or object module. If you are using a Series III or a Series IV development (or target) system, you will have to copy this command to yourupdate process as a group. ZBRA31.HLP DATE: DECEMBER 1984 PRODUCT: iRMX 86 R6.0, ICU V2.1 REPLACEMENT HELP FILE: icu86.hlp DESCRIPTION: This ZAP is the new help messages for the new version (2.1) of the ICU. See ZBRA30.R86 for more information. SPECIAL NOTES: This ZAP is intended to be used in conjunction with ZBRA30.R86, ZBRA40.R86 and ZBRA41.LIT. These ZAPs MUST be included or excluded from the update process as a group. ZBRA33.RMD DA can be displayed with the VERSION command. This ZAP is intended to be used in conjunction with ZBRA30.R86, ZBRA31.HLP and ZBRA41.LIT. These ZAPs MUST be included or excluded from the update process as a group. ZBRA41.LIT DATE: DECEMBER 1984 PRODUCT: iRMX 86 R6.0, ICU V2.1 REPLACEMENT LITERAL FILE: icu86.021 DESCRIPTION: This ZAP replaces the file ICU86.020 with the file ICU86.021. This literal file contains the new version number of the ICU whiZAP installed will allow ONLY nine sectors per track on 5 1/4", uniform, double density diskettes with 512 byte granularity that have been attached physical. Other diskette formats are unaffected. For a diskette with these attributes, the only thing that determines whether you access 8 or 9 sectors per track is the application of this ZAP. If you apply the ZAP, the system that you generate can only access 9 sectors per track for this type of diskette. If you do  40.R86 and ZBRA41.LIT (ICU version 2.1) supply configuration support for the iSBC 188/48 driver. If you intend to use the iSBC 188/48 driver you should use version 2.1 of the ICU. Installing the four ZAPs just mentioned will ensure that version 2.1 of the ICU will be used. The new iSBC 188/48 device driver cannot be used in the same iRMX 86 system as the iSBC 544 device driver. Therefore, you should not attempt to configure an iRMX 86 system with both a iSBC 544 aODUCT: iRMX 86 R6.0 APPLICATION LOADER V3.1 REPLACEMENT MODULE: ltask in loadrl.lib DESCRIPTION: This ZAP fixes a problem in the loader where the specified or default stack size allocated to the loaded job's initial task is too small. This can result in a stack overflow. This ZAP fixes loadrl.lib which is used if you specify LTL for Code Type in the application loader configuration screen of the ICU. SPECIAL NOTES: If your loaded job currently has a stack san 272 decimal. Specifying a stacksize from 0 to 271 inclusive may result in (1) a system crash, or (2) CORRUPTION OF DATA ON ANY ACTIVE DISK OR DISKETTE VOLUME. (including the Winchester volume). If you install ZAPS 44-47, attempting to load a job with a specified stacksize from 1 to 271 will result in an E$PARAM exception being returned. ZBRA44.RMD DATE: DECEMBER 1984 PRODUCT: iRMX84 PRODUCT: iRMX 86 R6.0 APPLICATION LOADER V3.1 REPLACEMENT MODULE: ltask in loadro.lib DESCRIPTION: This ZAP fixes a problem in the loader where the specified or default stack size allocated to the loaded job's initial task is too small. This can result in a stack overflow. This ZAP fixes loadro.lib which is used if you specify OVR for Code Type in the application loader configuration screen of the ICU. SPECIAL NOTES: If your loaded job currently ha zero, it will work without changes when this ZAP is applied to your system. If you do not specify a stack size of zero, you should specify a stack size of at least 272 decimal. SIDE EFFECTS: If you currently have a job with a specified stack size between 1 and 271 inclusive, this job will not work correctly when this ZAP is applied to your system. An attempt to load such a job will result in an E$PARAM exception. ZBRA45.RMD DATE: DECEMBER 1984 PRnd an iSBC 188/48. Installing this ZAP will not cause a conflict between the iSBC 544 driver and the iSBC 188/48 driver, but do not ask the ICU to include both the iSBC 188/48 and the iSBC 544 in the same configuration. CAUTION If you choose not to install ZAPS 44-47, be aware of the following: When you use the Application Loader to load a job, you must specify a stacksize greater thize of zero, it will work without changes when this ZAP is applied to your system. If you do not specify a stack size of zero, you should specify a stack size of at least 272 decimal. SIDE EFFECTS: If you currently have a job with a specified stack size between 1 and 271 inclusive, this job will not work correctly when this ZAP is applied to your system. An attempt to load such a job will result in an E$PARAM exception. ZBRA46.RMD DATE: DECEMBER 19 86 R6.0 APPLICATION LOADER V3.1 REPLACEMENT MODULE: ltask in loadrp.lib DESCRIPTION: This ZAP fixes a problem in the loader where the specified or default stack size allocated to the loaded job's initial task is too small. This can result in a stack overflow. This ZAP fixes loadrp.lib which is used if you specify PIC for Code Type in the application loader configuration screen of the ICU. SPECIAL NOTES: If your loaded job currently has a stack size of  s a stack size of zero, it will work without changes when this ZAP is applied to your system. If you do not specify a stack size of zero, you should specify a stack size of at least 272 decimal. SIDE EFFECTS: If you currently have a job with a specified stack size between 1 and 271 inclusive, this job will not work correctly when this ZAP is applied to your system. An attempt to load such a job will result in an E$PARAM exception. ZBRA47.RMD DATE: DE memory needed to load some object modules. ZBRA50.RMD DATE: MARCH 1985 PRODUCT: iRMX 86 R6.0 APPLICATION LOADER V3.1 REPLACEMENT MODULE: laldj in loadro.lib DESCRIPTION: In some cases, RQ$A$LOAD$IO$JOB and RQ$S$LOAD$IO$JOB calls return an E$NO$MEM exception due to incorrect calculations in the Application Loader. This ZAP corrects the error in the Loader to calculate the memory requirements correctly. SIDE EFFECTS: The application of this Zurrently has a stack size of zero, it will work without changes when this ZAP is applied to your system. If you do not specify a stack size of zero, you should specify a stack size of at least 272 decimal. SIDE EFFECTS: If you currently have a job with a specified stack size between 1 and 271 inclusive, this job will not work correctly when this ZAP is applied to your system. An attempt to load such a job will result in an E$PARAM exception. ZBRA48.RMD ECTS: The application of this ZAP will slightly increase the memory needed to load some object modules. ZBRA52.RMD DATE: MARCH 1985 PRODUCT: iRMX 86 R6.0 DEVICE DRIVERS V2.0 REPLACEMENT MODULE: xrad2 in xcmdrv.lib DESCRIPTION: This replacement module corrects a coding error in the random access support code so that concurrent seeking is supported on all Intel-supported random access devices. ZBRA53.RMD DATE: MARCH 1985 PRODUCT: iRMX 8bject modules. ZBRA49.RMD DATE: MARCH 1985 PRODUCT: iRMX 86 R6.0 APPLICATION LOADER V3.1 REPLACEMENT MODULE: laldj in loadrl.lib DESCRIPTION: In some cases, RQ$A$LOAD$IO$JOB and RQ$S$LOAD$IO$JOB calls return an E$NO$MEM exception due to incorrect calculations in the Application Loader. This ZAP corrects the error in the Loader to calculate the memory requirements correctly. SIDE EFFECTS: The application of this ZAP will slightly increase the CEMBER 1984 PRODUCT: iRMX 86 R6.0 APPLICATION LOADER V3.1 REPLACEMENT MODULE: ltask in loadra.lib DESCRIPTION: This ZAP fixes a problem in the loader where the specified or default stack size allocated to the loaded job's initial task is too small. This can result in a stack overflow. This ZAP fixes loadra.lib which is used if you specify ABS for Code Type in the application loader configuration screen of the ICU. SPECIAL NOTES: If your loaded job cAP will slightly increase the memory needed to load some object modules. ZBRA51.RMD DATE: MARCH 1985 PRODUCT: iRMX 86 R6.0 APPLICATION LOADER V3.1 REPLACEMENT MODULE: laldj in loadra.lib DESCRIPTION: In some cases, RQ$A$LOAD$IO$JOB and RQ$S$LOAD$IO$JOB calls return an E$NO$MEM exception due to incorrect calculations in the Application Loader. This ZAP corrects the error in the Loader to calculate the memory requirements correctly. SIDE EFF DATE: MARCH 1985 PRODUCT: iRMX 86 R6.0 APPLICATION LOADER V3.1 REPLACEMENT MODULE: laldj in loadrp.lib DESCRIPTION: In some cases, RQ$A$LOAD$IO$JOB and RQ$S$LOAD$IO$JOB calls return an E$NO$MEM exception due to incorrect calculations in the Application Loader. This ZAP corrects the error in the Loader to calculate the memory requirements correctly. SIDE EFFECTS: The application of this ZAP will slightly increase the memory needed to load some o 6 R6.0 NUCLEUS V6.0 REPLACEMENT MODULE: ncrtsk in nuc4.lib DESCRIPTION: This replacement module corrects an error in one of the Nucleus routines that was causing iRMX 86 to write into ROM code during system initialization. Note that the problem was only relevant when the root job was in ROM. ZBRA54.RMD DATE: MARCH 1985 PRODUCT: iRMX 86 R6.0 DEVICE DRIVERS V2.0 REPLACEMENT MODULE: xprntr in xcmdrv.lib DESCRIPTION: This replacement module resrror when you attempt to attach the device.) d. Use the iSBX 217C board only in conjunction with a model number 5945L-2 Archive streamer tape drive. e. The 8742 microcomputer on the iSBX 217C board must have part number 146855-001. f. Jumper the iSBX 217C board as follows: -Remove 87-88, 95-96, and 37-38. -Connect jumpers 88, 95, and 96 by running a wire wrap from  several of its source lines. The CRs have been added in the replacement file. ZBRA58.LIT DATE: MARCH 1985 PRODUCT: iRMX 86 R6.0 LITERAL DECLARATION FILES REPLACEMENT LITERAL DECLARATION: uexcep.lit in /rmx86/inc The original file is missing carriage returns (CR) at the end of several of its source lines. The CRs have been added in the replacement file. ZBRA60.RMD DATE: JANUARY 1984 PRODUCT: iRMX 86 R6.0, DEVICE DRIVERS V2.1 (iSBX 217C)  DESCRIPTION: See ZBRA60.RMD. ZBRA63.RMD DATE: JANUARY 1984 PRODUCT: iRMX 86 R6.0, DEVICE DRIVERS V2.1 (iSBX 217) REPLACEMENT MODULE: x215it in xcmdrv.lib DESCRIPTION: See ZBRA60.RMD. ZBRA64.RMD DATE: JANUARY 1984 PRODUCT: iRMX 86 R6.0, DEVICE DRIVERS V2.1 (iSBX 217) REPLACEMENT MODULE: x215st in xcmdrv.lib DESCRIPTION: See ZBRA60.RMD. ZBRA65.RMD DATE: JANUARY 1984 PRODUCT: iRMX 86 R6.0, DEVICE DRIVERS V2.1 (iSBX 217) STRICTIONS COULD RESULT IN LOSS OF DATA. a. Install these ZAPs only in a System 310-XX. b. The iSBC 215G board in the 310 system must be of revision level -012. c. The iSBC 215G board in the 310 system must contain firmware EPROMs with the following part numbers: 174581-001 and 174581-002. (If your iSBC 215G board does not contain this version of the firmware, the driver generates an E$SUPPORT etores the line printer driver to the way it was in Release 5. It was found that additions made to the driver in Release 6 (so that it meets Centronics specifications) are unnecessary and they slowed down the performance of the driver on 86-based systems. ZBRA57.EXT DATE: MARCH 1985 PRODUCT: iRMX 86 R6.0 EXTERNAL DECLARATION FILES REPLACEMENT DECLARATION FILE: hgtcmd.ext in /rmx86/inc The original file is missing carriage returns (CR) at the end of 88 through 95 to 96. g. Jumper the iSBC 215G board as follows: -Remove W3(1-2). -Remove W24(1-2). ZBRA61.RMD DATE: JANUARY 1984 PRODUCT: iRMX 86 R6.0, DEVICE DRIVERS V2.1 (iSBX 217) REPLACEMENT MODULE: x215in in xcmdrv.lib DESCRIPTION: See ZBRA60.RMD. ZBRA62.RMD DATE: JANUARY 1984 PRODUCT: iRMX 86 R6.0, DEVICE DRIVERS V2.1 (iSBX 217) REPLACEMENT MODULE: x215cs in xcmdrv.lib  REPLACEMENT MODULE: xrad3 in xcmdrv.lib DESCRIPTION: This ZAP provides support for the iSBX 217C tape cartridge controller. SPECIAL NOTES: ZAPs ZBRA60.RMD through ZBRA67.RMD were designed to be used together. These ZAPs MUST be included or excluded from the update process as a group. The default for these ZAPs is to not be installed. Install ZAPs ZBRA60.RMD through ZBRA67.RMD only under the following conditions. FAILURE TO COMPLY WITH THESE RE  REPLACEMENT MODULE: x217dm in xcmdrv.lib DESCRIPTION: See ZBRA60.RMD. ZBRA66.RMD DATE: JANUARY 1984 PRODUCT: iRMX 86 R6.0, DEVICE DRIVERS V2.1 (iSBX 217) REPLACEMENT MODULE: x217it in xcmdrv.lib DESCRIPTION: See ZBRA60.RMD. ZBRA67.RMD DATE: JANUARY 1984 PRODUCT: iRMX 86 R6.0, DEVICE DRIVERS V2.1 (iSBX 217) REPLACEMENT MODULE: x217st in xcmdrv.lib DESCRIPTION: See ZBRA60.RMD. ZBRA68.RMD DATE: MARCH 1985 PROD number of files that may reside on a single volume to 32,768. Furthermore, no single file may be larger than 67MB. ZBRA74.OBJ DATE: JANUARY 1984 PRODUCT: iSBC 544 FIRMWARE NEW FIRMWARE: xf544 DESCRIPTION: This ZAP is the new iSBC 544 firmware (V2.3). Installation of the update will only copy this file to your disk. To use the new firmware you must burn PROMs and install them on your iSBC 544 board. 9 need not worry because applying this ZAP nullifies the effects of ZBRA19. ZBRA73.LIB DATE: JANUARY 1984 PRODUCT: iRMX 86 R6.0, DEVICE DRIVERS V2.1 (iSBC 226) NEW LIBRARY: 226DD.LIB DESCRIPTION: This ZAP provides support for the iSBC 226 SMD controller. In addition to 226DD.LIB, this ZAP uses two other files supplied with Update 3--226IT.A86 and 226DB.A86. The documentation change page package (title "iRMX 86 Device Driver Change Package: Update the ZAP. An example for ; Series III, Series IV and iRMX86 is included. ; ; ; APPLICATION: submit ZBRA22.CSD( %0, %1, %2, %3, %4, %5, %6 ) ; ; %0 = Pathname for the directory that contains your ; system commands (i.e., submit, copy, rename, delete). ; (ex: Series III = ":f0:", Series IV = ":system:", and ; iRMX 86 = "/system/") ; ; %1 = Pathname for the directory that contains your language ; utilities (i.e., ASM86, L COMMAND BEFORE CHANGING DISK PACKS MAY RESULT IN CORRUPTION OF DATA ON THE NEWLY INSERTED PACK. b. The iSBC 226 driver does not support drive partitioning. c. Attempting to invoke DISKVERIFY on a very large capacity drive used in conjunction with the iSBC 226 will cause the system to hang. NOTE: When using very large capacity drives, keep in mind the following iRMX 86 Operating System constraints. iRMX 86 limits theUCT: iRMX 86 R6.0 UDI V3.0 REPLACEMENT MODULE: dq$get$argument in udi.lib DESCRIPTION: This replacement module corrects a problem where DQ$GET$ARGUMENT does not handle buffers ending with double delimiters correctly. It also corrects a problem which prevents TX from accepting one character filenames. SPECIAL NOTES: This ZAP must be used in conjunction with ZBRA18.RMD to fix the problem. This ZAP replaces ZBRA19. Users who have already applied ZBRA1;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; ; ; NAME: ZBRA22.CSD ; DATE: 10 OCT 84 ; ; ; NOTE: This submit file applies the above ZAP to the iRMX 86 ; Operating System object code. This submit file can be ; executed on an Intellec Series III, a Series IV or an ; iRMX 86 development system. ; ; The following parameter list (in order) must be used for ; the correct application of 3") provides instructions on how to install and configure the 226 driver into your system. SPECIAL NOTES: The following limitations apply to the use of the iSBC 226 Driver: a. On SMD drives with removable disk packs, you must always execute a DETACHDEVICE command before changing disk packs. After inserting the new disk pack, reattach the drive using the ATTACHDEVICE command. FAILURE TO EXECUTE THE DETACHDEVICE  INK86, LIB86). ; (ex: Series III = ":f0:", Series IV = ":lang:", and ; iRMX 86 = "/LANG/") ; ; %2 = Pathname for the directory that contains the contents ; of the iRMX 86 Update Package. ; (ex; Series III = ":f4:", Series IV = ":rmx86:update/", ; and iRMX 86 = "/rmx86/update/") ; ; %3 = Pathname for the directory that contains the iRMX 86 ; object code (e.g., nuc3.lib, xcmdrv.lib, eios.lib). ; (ex:ile (1) describes workarounds for problems discovered * * in the iRMX 86 Release 6 Operating System software, and (2) provides * * vital information that is missing from the iRMX 86 Operating * * System documentation. All items in this file are temporary. An * * item remains in the READ.ME file only as long as the associated * * problem is unfixed. Once a fix is available through the update * * service (either as a ZAP or as change p;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; %4 %1lib86 delete %3udi.lib(uduspl) add %2zbra22.rmd to %3udi.lib exit %5 ; This line is only applicable to iRMX 86 R6.0 development system users. %6permit %3udi.lib r u=world  * * following this section is a listing of the items that have been * * deleted since the last update. The remainder of the file contains * * items entered during previous updates. * * * ******************************************************************************* ===============================================================================  ******************************************************************************* * * * READ.ME * * * ******************************************************************************* * * * The READ.ME f Series III = ":f1:", Series IV = ":rmx86:ios/", ; and iRMX 86 = "/rmx86/ios/") ; ; %4 = 'RUN'. This parameter is only needed for ISIS Series ; III development systems. ; ; %5 = 'EXIT'. This parameter is only needed for ISIS Series ; III development systems. ; ; %6 = ';'. This parameter is only needed for Series III and ; Series IV development systems. ; ; ; ASSUMPTIONS: None. ; ; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;ages to the documentation) the * * description of the workaround is removed. A designated section of the * * READ.ME file lists the items that have been deleted since the last * * update. * * * * Items that have been added to the READ.ME file during the current * * update appear in a section at the front of the file. ImmediatelyHYBRIDDETACHDEVICE=2STACKMEMORYCODEDATADGROUPCGROUPZAPS??SEGPHH T>ƘDh X  ROOTJOBTOKEN RQGETTYPERQCREATEMAILBOX RQSENDMESSAGE OBJECTLOOKUP DELETEMAILBOXVALIDATEMESSAGE GETOWNERIDCOMPOSITEINSPECTION\\HYBRIDDETACHDEVICE'HYBRIDDETACHDEVICE?PLM86 V2.309/27/84 14:43:0ϠU&^&FF t&?u ^&@G6^SP^SF^&?uCv^SF^&?u~t ^&AF PvF  ITEMS ADDED IN UPDATE 3 =============================================================================== 15. Preconditions for Using the iSBX 217C Driver Install the iSBX 217C Driver only under the following conditions. FAILURE TO COMPLY WITH THESE RESTRICTIONS COULD RESULT IN LOSS OF DATA. a. Install the iSBX 217C only in a System 310-XX. b. The iSBC 215G board in the 310 system must be of revision level -012. c. The iSBC 215G board in the 310 systeves, keep in mind the following iRMX 86 Operating System constraints. iRMX 86 limits the number of files that may reside on a single volume to 32,768. Furthermore, no single file may be larger than 67MB. *** 13. Activating flow control with an the iSBC 188/48 Terminal Controller To activate flow control using the A$SPECIAL system call, assign the following values to the A$SPECIAL system call parameters: flow$c f. Jumper the iSBX 217C board as follows: -Remove 87-88, 95-96, and 37-38 -Connect jumpers 88, 95, and 96 by running a wire wrap from 88 through 95 to 96. With the above modifications, the iSBX 217C board should conform to the following jumper configuration: 84-91 33-48 40-41 10-11 71-72 26-27 13-34 39-54 81-82 31-32 66-73 77-78  ESC]T:J=xESC\ where x is a decimal number such that 1 <= x <= 242 (see NOTE at the end of this item) ESC]T:K=yESC\ where y is a decimal number such that 0 <= y <= 242 (see NOTE at the end of this item) ESC]T:P=aESC\ where a is the Hex value of the ASCII character used as "XON" ESC]T:Q=bESC\ where b is the Hex value of the ASCII character used as "XOFF" NOTE: The size of each channel's input buffer inserting the new disk pack, reattach the drive using the ATTACHDEVICE command. FAILURE TO EXECUTE THE DETACHDEVICE COMMAND BEFORE CHANGING DISK PACKS MAY RESULT IN CORRUPTION OF DATA ON THE NEWLY INSERTED PACK. b. The iSBC 226 driver does not support drive partitioning. c. Attempting to invoke DISKVERIFY on a very large capacity drive used in conjunction with the iSBC 226 will cause the system to hang. NOTE: When using very large capacity drim must contain firmware EPROMs with the following part numbers: 174581-001 and 174581-002. (If your iSBC 215G board does not contain this version of the firmware, the driver generates an E$SUPPORT error when you attempt to attach the device.) d. Use the iSBX 217C board only in conjunction with an Archive model number 5945L-2 streamer tape drive. e. The 8742 microcomputer on the iSBX 217C board must have part number 146855-001. ontrol = 1 high$water$mark = a decimal number x such that 1 <= x <= 242 (see NOTE at the end of this item) low$water$mark = a decimal number y such that 0 <= y <= 242 (see NOTE at the end of this item) fc$on$char = the Hex value of the ASCII character used as "XON" fc$off$char = the Hex value of the ASCII character used as "XOFF" To activate flow control using an OSC sequence: ESC]T:G=1ESC\  16-17 46-61 8-29 52-67 57-58 88-96 35-50 45-60 95-96 g. Jumper the iSBC 215G board as follows: -Remove W3(1-2) -Remove W24 (1-2) *** 14. The following limitations apply to the use of the iSBC 226 Driver: a. On SMD drives with removable disk packs, you must always execute a DETACHDEVICE command before changing disk packs. After  on the iSBC 188/48 is fixed by the firmware at 1940 bytes. When setting the high and low threshholds used for flow control, the 188/48 firmware multiplies the supplied high and low water mark values by eight to yield the true threshhold values. Intel recommends using 241 (decimal) as the high$water$mark value and 120 (decimal) as the low$water$mark value. *** =========================================================ders - Number of Alternate Cylinders) * (Number of Heads) * (Sectors per Track) * (Device Granularity) g) calculate and enter the Device Size (DSZ) on smdt0's DUIB screen using the following formula: DSZ = (Number of Cylinders) * (Number of Heads) * (Sectors per Track) * (Device Granularity) 2) Place the system created in step 1 onto the boot disk/diskette. 3) Boot the system from the disk/diskette specified in step 2.ormatted SMD disk drive into an iRMX 86 system using an iSBC 220 Controller, the system will 'hang' unless the following steps are taken: 1) When generating the iRMX 86 system, include as a minimum 2 Device Unit Information Blocks (DUIBs) and 2 Unit Information Tables for the SMD drive. Assuming that the DUIB names are 'smd0' and 'smdt0', and the Unit Information Table names are 'uinfo_220' and 'uinfo_220t': a) in uinfo_220t, specify No for Bad Track Informatio)} - {i * (sectors per track)} where i = 4 for Device Granularity of 1024 bytes per sector, i = 3 for Device Granularity of 512 bytes per sector, i = 2 for Device Granularity of 256 bytes per sector, i = 1 for Device Granularity of 128 bytes per sector; c) Read the Block Number calculated in step 6b; d) Write the manufacturer-supplied Bad Track Information into the block using the following format: er Track (NS) for both uinfo 220 and uinfo_220t; d) associate uinfo_220 with smd0 by specifying uinfo_220 for Unit Info Name (UN) on smd0's Device Unit Information screen; e) associate uinfo_220t with smdt0 by specifying uinfo_220t for Unit Info Name (UN) on smdt0's Device Unit Information screen; f) calculate and enter the Device Size (DSZ) on smd0's DUIB screen using the following formula: DSZ = (Number of Cylin====================== ITEMS DELETED IN UPDATE 3 =============================================================================== None =============================================================================== ACTIVE ITEMS FROM PREVIOUS UPDATES =============================================================================== 12. Installing an Unformatted SMD Disk Drive with an iSBC 220 Controller When installing a completely unf 4) Attach physically to smdt0 (ATTACHDEVICE smdt0 as s0 phys). 5) FORMAT :s0: 6) Using DISKVERIFY, write the Bad Track Information provided by the SMD Drive manufacturer onto the SMD disk as follows: a) DISKVERIFY :s0: ; b) Calculate the Block (sector) Number on which to write the Bad Track Information using the following formula: Block # = {(number of cylinders - 1) * (number of heads) * (sectors per trackn (BTI) and a value equal to approximately 2% of the total cylinders for Number of Alternate Cylinders (NAC); b) in uinfo-220, specify YES for Bad Track Information (BTI) and a value equal to approximately 2% of the total cylinders for Number of Alternate Cylinders (NAC); c) specify the correct Number of Cylinders (NC), Number of Heads/ Fixed Disk (NFH), Number of Heads/Removable Disk (NRH), and Number of Sectors p  *SW xxxx:yyyy- (ABCD) xxxx:yyyy- (number of Bad Tracks) xxxx:yyyy- (Cylinder Number of 1st Bad Track) xxxx:yyyy- (Head Number of 1st Bad Track) xxxx:yyyy- (Cylinder Number of 2nd Bad Track) xxxx:yyyy- (Head Number of 2nd Bad Track) : : : xxxx:yyyy- (Cylinder Number of Last Bad Track) xxxx:yyyy- (Head Number of Last Bad Track) xxxx:yyyy- (0) that Serial Channel 2 in configured properly, make sure the following jumpers are connected on the IEU Board in your Series IV: E11 - E13 Selects Timer 0, port F0. E16 - E17 Usart clock. E22 - E23 Transmit clock. E25 - E26 Receive clock. E28 - E29 Ties CLEAR_TO_SEND to REQUEST_TO_SEND. E31 - E33 Selects DATA and COMAND STATUS ports F4 and F5. E40 - E42 Crosses TRANSMIT and RECEIVE data lines (pins 2 and 3 E41 - E43 on cable) for boards with numbers 12 6d and 6e if necessary; g) Exit. 7) DETACHDEVICE :s0: 8) ATTACHDEVICE smd0 as :s0: a) The System will respond with a 'Volume Is Not a Named Volume' message. 9) FORMAT :s0: Files = ( ) where ( ) is the user-specified maximum number of files that can reside on the drive. *** 11. Notes on Running iRMX 86 on a Series IV The following utilities can be used when developing iRMXher development systems. If you use any of the default definition files for the ICU (such as FS86.DEF to configure the Files Utility), you must make several modifications. Using the CHANGE option of the ICU, the INCLUDES AND LIBRARIES screen should be changed to reflect the directory structure on the Series IV. The GENERATE FILE screen should also be changed to reflect valid Series IV pathnames. Since the Series-IV supports a hierarchical directory structure, the pathnames in the ICU must not exdes for serial transfer. When using the iSDM 86 serial connection, be sure to use the RS232C cable supplied with the iSDM 86 package. Note that the iSDM-86 loader (SDM86) is an 8-bit loader. Thus you must enter ISIS mode on the Series IV before running SDM86. The iSDM-86 Monitor comunicates with the iRMX-86 system through Serial Channel 2 of the Series IV development system. The IEU board in your Series IV system comes shipped from the factory with Serial Channel 2 configured. To verify  xxxx:yyyy- (0) xxxx:yyyy- (0) xxxx:yyyy- (0) xxxx:yyyy- . where xxxx is the WORD location in the block to be changed, yyyy is the current value of the WORD, ( ) is the new value the operator places into the WORD. e) Write the new Block Information onto the disk; f) Read and Display the Block Number again to be sure all the information has been added in the proper format; Repeat steps4744-002 and below. OR E40 - E43 Crosses TRANSMIT and RECEIVE data lines (pins 2 and 3 E41 - E42 on cable) for boards with number 124744-003. E44 - E45 Usart RECEIVE READY Interrupt 2. E48 - E49 Usart TRANSMIT READY Interrupt 3. Files Utility The Files Utility operates the same on the Series-IV as on other development systems. Interactive Configuration Utility (ICU) Using the ICU from the Series-IV is virtually the same as using it from one of the ot 86 applications on any standard Series IV: iSDM-86 Files Utility Interactive Configuration Utility (ICU) Crash Analyzer When developing iRMX 86 Release 6.0 applications on a Series-IV please note the following: iSDM-86 Monitor The iSDM-86 Monitor provides a means of communication between the Series-IV and the iRMX-86 target system. iSDM-86 allows either a parallel or a serial connection. However, without including any additional hardware, the Series-IV only proviceed 256 characters. In the naming of directories and in the placement of ICU files, avoid long pathnames by using logical assignments. Crash Analyzer The Crash Analyzer operates the same on the Series-IV as on the other development systems. Notice that there is a bug in the Dumper portion of the Crash Analyzer. After the dumper writes the dump file to the Series-IV, it is supposed to display a message indicating that the dump completed. It is then supposed to return to the iSDM-86 monitor. Heads/Fixed Disk [0-0FFH] 0008H (NRH) Number of Heads/Removable Disk [00-0FFH] 0000H (NS) Number of Sectors/Track [0-0FFFFH] 0009H (NAC) Number of Alternate Cylinders [0-0FFH] 000AH (SSN) Starting Sector Number [0-0FFFFFFFFH] 00000000H (BTI) Bad Track Information [Yes/No] Yes (HLT) Head Load Time [0-0FFH] 0000H (SR) Step Rate [0-0FFH] nit Information screen and the Unit Information screen when configuring a 40 Megabyte Disk Drive with an iSBX 215 driver. iSBC 215/iSBX 218 Device-Unit Information (NAM) Device-Unit Information [1-13 Chars] qma0 (PFD) Physical File Driver Required [Yes/No] Yes (NFD) Named File Driver Required [Yes/No] Yes (SDD) Single or Double Density Disks [Single/Double] Single (SDS) Single or Double Sided Disks [Single/Double] Single (EF (SDS) Single or Double Sided Disks [Single/Double] Single (EFI) 8 or 5 Inch Disks [8/5] 8 (SUF) Standard or Uniform Format [Standard/Uniform] Standard (GRA) Granularity [0-0FFFFH] 0400H (DSZ) Device Size [0-0FFFFFFFFH] 03C69000H (UN) Unit Number on this Device [0-0FFH] 0000H (UIN) Unit Info Name [1-17 Chars] uinfo_215iwb (RUT) Request Updaterandom = 0/rand = 1-0FFFFH] 0008H (CUP) Common Update [True/False] True (MB) Max Buffers [0-0FFH] 00FFH iSBC 215/iSBX 218 Unit Information (NAM) Unit Info Name [1-17 Chars] uinfo_215qma (MR) Maximum Retries [0-0FFFFH] 0009H (CS) Cylinder Size [0-0FFFFH] 0048H (NC) Number of Cylinders [0-0FFFFH] 0200H (NFH) Number of  In reality, the first letter of the message ("D") is displayed after which the system hangs. However, since at this point the dump file has already been created, you can work around this bug by interrupting the target system and continuing to use the Crash Analyzer on the Series-IV. *** 10. Device Unit Information Screen and Unit Information Screen for 40 Megabyte and 70 Megabyte Disk Drives The following data should be supplied in the Device U 0000H The following data should be supplied in the Device Unit Information screen and the Unit Information screen when configuring a 70 Megabyte Disk Drive with an iSBX 215 driver. iSBC 215/iSBX 218 Device-Unit Information (NAM) Device-Unit Information [1-13 Chars] iwb0 (PFD) Physical File Driver Required [Yes/No] Yes (NFD) Named File Driver Required [Yes/No] Yes (SDD) Single or Double Density Disks [Single/Double] SingleI) 8 or 5 Inch Disks [8/5] 5 (SUF) Standard or Uniform Format [Standard/Uniform] Standard (GRA) Granularity [0-0FFFFH] 0400H (DSZ) Device Size [0-0FFFFFFFFH] 0234C000H (UN) Unit Number on this Device [0-0FFH] 0000H (UIN) Unit Info Name [1-17 Chars] uinfo_215qma (RUT) Request Update Timeout [0-0FFFFH] 0064H (NB) Number of Buffers [non Timeout [0-0FFFFH] 0064H (NB) Number of Buffers [nonrandom = 0/rand = 1-0FFFFH] 0008H (CUP) Common Update [True/False] True (MB) Max Buffers [0-0FFH] 00FFH iSBC 215/iSBX 218 Unit Information (NAM) Unit Info Name [1-17 Chars] uinfo_215iwb (MR) Maximum Retries [0-0FFFFH] 0009H (CS) Cylinder Size [0-0FFFFH] 003CH (NC) Nuinto the system, regardless of the number of channels actually used. Four separate Device Unit Information screens must be defined, with one screen representing each channel. (In other words, in the ICU you must invoke the iSBC 544 Unit Information screen four times. In doing so, make sure that the specified unit numbers are in the range from 0 to 3) Failure to configure all four channels in this fashion may cause the system to fail when a device connecte 0000H (SR) Step Rate [0-0FFH] 0000H *** 9. Release 6.0 ICU using Release 5.0 Definition Files If you are running the Release 6.0 ICU but using a Release 5.0 definition file, please note the following: Unless you specify otherwise, the ICU will use the Release 5.0 definition file as the output file. The ICU modifies this file to conform to the Release 6.0 formber. In the Intel supplied definition file for the iSBC 186/03 (r18603.def), three DUIB's-identified by the device unit names ATSO, XESO, and SHSO--have the same device size and unit number. Therefore, if your system requires any of these DUIB's, be sure to make the necessary modifications so that each DUIB has either a unique device size or a unique unit number. *** 5. Bootstrap Loader Debug Switch and the Cont Human Interface DIR command with the S option set.) A properly linked ASM86 has a file size of 137,286 bytes; LINK86 has a file size of 83,752 bytes. If any other file size is indicated, contact your local Intel representative. *** 7. Configuring in All Four Channels of an iSBC 544 If you are using an iSBC 544 Intelligent Communications controller in an iRMX 86 Release 6.0 system, you must configure all four channels mber of Cylinders [0-0FFFFH] 0419H (NFH) Number of Heads/Fixed Disk [0-0FFH] 0005H (NRH) Number of Heads/Removable Disk [00-0FFH] 0000H (NS) Number of Sectors/Track [0-0FFFFH] 000CH (NAC) Number of Alternate Cylinders [0-0FFH] 0012H (SSN) Starting Sector Number [0-0FFFFFFFFH] 00000000H (BTI) Bad Track Information [Yes/No] Yes (HLT) Head Load Time [0-0FFH] d to the iSBC 544 board is attached. *** 6. Automatic Boot Device Recognition with SASI/SCSI as System Device Observe the following precaution when loading an iRMX 86 Release 6.0 system that uses a SASI/SCSI driver as the system device. If you wish to use the Automatic Boot Device Recognition feature, all device specific DUIB's in the system device definition file must specify a unique device size or a unique unit numat. Thus, the file can no longer be used by the Release 5.0 ICU. *** 8. Assuring that the Proper Version of UDI is Linked to ASM86 and LINK86 To execute properly under iRMX 86 Release 6.0, the assembler (ASM86) and the linker (LINK86) must have been linked to Version 2.0 of the UDI interface libraries. You must check the size of these utilities to determine whether both have been linked to the right version. (Use the ents of CPU Registers If you use the Bootstrap Loader Debug Switch, you should be aware of two items related to the CPU register contents. First, notice that the initial contents of the CPU registers depend on the type of CPU being used. Therefore, when identical copies of a system are run on different types of CPU's, do not be alarmed if the initial contents of the CPU registers vary. Second, on iAPX 286 based systems, the monitor may initially dinitor. *** 1. iSBC 286/10 with one-wait state LBX and the 8274 Terminal Driver If your system contains an iSBC 286/10 board that utilizes one wait-state LBX memory and uses the 8274 Terminal Driver, please note the following: A baud rate scan of a terminal set to 9600 baud will cause the system to fail. As a workaround you can 1) use two or more wait-states in the LBX memory; 2) set the terminais is the version supplied by Intel in BS1.A86.) The other version supports booting from an 8 inch diskette only. The version that supports booting only from an 8 inch diskette requires less memory. You may select this version by modifying the %device macro in BS1.A86 for the iSBC 215. (Simply change deviceinit215gen to deviceinit215 and deviceread215gen to deviceread215.) Notice that, with the %device macro modified in this way, you will not be a***************************************************************** sm for properly initializing the front panel interrupt vector on these systems. When a system crash occurs, the front panel interrupt must be used to break to the monitor so that the Crash Analyzer can be invoked. *** 2. Resetting CPU after Crash Dumper Creates a Memory Image of the System After using the iRMX 86 Crash Dumper to create a memory image of your system, you must reset the system CPU before you invoke the mosplay an incorrect value for the Instruction Pointer (IP) register; however, the actual value in the IP register will be correct. *** 4. Two Versions of iSBC 215/218 Loader Code When configuring the Bootstrap Loader, be aware that iRMX 86 Release 6.0 contains two versions of the iSBC 215/218 loader code. One version supports booting the system from either a 5.25-inch mini-floppy diskette or from an 8 inch diskette. (Thl baud rate to something other that 9600 baud when doing a baud rate scan; or, 3) configure the 8274 Terminal Driver to use a fixed baud rate. ******************************************************************************* * * * END READ.ME * * * **************ble to boot from a 5.25-inch mini-floppy diskette. *** 3. Using the Crash Analyzer with System 86/300 Microcomputers On System 86/300 Series microcomputers, when the Crash Analyzer is used, the System Debugger (SDB) must also be configured into the system. This must be done in spite of the fact that once the Crash Analyzer is initialized, the SDB is rendered inoperative. Nonetheless, the SDB provides the only mechaniP^S^&?uc^SF t^&?uN;t t&F8P^SF^&?uvvPSv^SFv]')E,D=T ņ݆!HYBRIDDETACH_REPLACEMENT_ZBRA24RASM86.86 V2.0wZBRA24F30>Њtthe ZAP. An example for ; Series III, Series IV and iRMX86 is included. ; ; ; APPLICATION: submit ZBRA09.CSD( %0, %1, %2, %3, %4, %5, %6 ) ; ; %0 = Pathname for the directory that contains your ; system commands (i.e., submit, copy, rename, delete). ; (ex: Series III = ":f0:", Series IV = ":system:", and ; iRMX 86 = "/system/") ; ; %1 = Pathname for the directory that contains your language ; utilities (i.e., ASM86, Lthe ZAP. An example for ; Series III, Series IV and iRMX86 is included. ; ; ; APPLICATION: submit zbra24.CSD( %0, %1, %2, %3, %4, %5, %6 ) ; ; %0 = Pathname for the directory that contains your ; system commands (i.e., submit, copy, rename, delete). ; (ex: Series III = ":f0:", Series IV = ":system:", and ; iRMX 86 = "/system/") ; ; %1 = Pathname for the directory that contains your language ; utilities (i.e., ASM86, L Series III = ":f1:", Series IV = ":rmx86:ios/", ; and iRMX 86 = "/rmx86/ios/") ; ; %4 = 'RUN'. This parameter is only needed for ISIS Series ; III development systems. ; ; %5 = 'EXIT'. This parameter is only needed for ISIS Series ; III development systems. ; ; %6 = ';'. This parameter is only needed for Series III and ; Series IV development systems. ; ; ; ASSUMPTIONS: None. ; ; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; ; ; NAME: ZBRA09.CSD ; DATE: 20 APR 84 ; ; ; NOTE: This submit file applies the above ZAP to the iRMX 86 ; Operating System object code. This submit file can be ; executed on an Intellec Series III, a Series IV or an ; iRMX 86 development system. ; ; The following parameter list (in order) must be used for ; the correct application of ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; ; ; NAME: zbra24.CSD ; DATE: 10 OCT 84 ; ; ; NOTE: This submit file applies the above ZAP to the iRMX 86 ; Operating System object code. This submit file can be ; executed on an Intellec Series III, a Series IV or an ; iRMX 86 development system. ; ; The following parameter list (in order) must be used for ; the correct application of INK86, LIB86). ; (ex: Series III = ":f0:", Series IV = ":lang:", and ; iRMX 86 = "/LANG/") ; ; %2 = Pathname for the directory that contains the contents ; of the iRMX 86 Update Package. ; (ex; Series III = ":f4:", Series IV = ":rmx86:update/", ; and iRMX 86 = "/rmx86/update/") ; ; %3 = Pathname for the directory that contains the iRMX 86 ; object code (e.g., nuc3.lib, xcmdrv.lib, eios.lib). ; (ex:INK86, LIB86). ; (ex: Series III = ":f0:", Series IV = ":lang:", and ; iRMX 86 = "/LANG/") ; ; %2 = Pathname for the directory that contains the contents ; of the iRMX 86 Update Package. ; (ex; Series III = ":f4:", Series IV = ":rmx86:update/", ; and iRMX 86 = "/rmx86/update/") ; ; %3 = Pathname for the directory that contains the iRMX 86 ; object code (e.g., nuc3.lib, xcmdrv.lib, eios.lib). ; (ex:;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; %0delete %3bs1dev.inc %0copy %2zbra09.inc to %3bs1dev.inc ; This line is only applicable to iRMX 86 R6.0 development system users. %6permit %3bs1dev.inc r u=world c iRMX 86 operation. (The READ.ME file on the * * Update diskette contains all new information about iRMX 86 operations.) * * Items in the NOTES file accumulate from update to update. Thus, the * * current update, in addition to any new notes, contains all of the notes * * from previous updates. New items are indicated by an asterisk and * * the word "NEW" (e.g. *NEW) on the item's first line. * * ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; %4 %1lib86 delete %3eios.lib(hybriddetachdevice) add %2ZBRA24.rmd to %3eios.lib exit %5 ; This line is only applicable to iRMX 86 R6.0 development system users. %6permit %3eios.lib r u=world  NOTES SECTION ONE iRMX 86 General Notes iRMX 86 Release 6.0 supports use of the iSBC 186/03 parallel port with a SASI/SCSI hard disk only. To control a line printer, install an iSBX 350 multimodule onto the iSBC 186/03 board. Then reconfigure the system to include the lineprinter driver (ICU device driver option #10). Specify the port address of the multimodule connector on which the iSBX 350 is ****************************************************************************** * * * NOTES * * * * The NOTES file presents general background information about the * * iRMX 86 Release 6.0 Operating System. Items in the NOTES file do not * * describe any specifi Series III = ":f1:", Series IV = ":rmx86:ios/", ; and iRMX 86 = "/rmx86/ios/") ; ; %4 = 'RUN'. This parameter is only needed for ISIS Series ; III development systems. ; ; %5 = 'EXIT'. This parameter is only needed for ISIS Series ; III development systems. ; ; %6 = ';'. This parameter is only needed for Series III and ; Series IV development systems. ; ; ; ASSUMPTIONS: None. ; ; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; * * The NOTES file is divided into two sections. The first section provides * * general items of information about the iRMX 86 Release 6.0 Operating * * System. The second section outlines some of the major differences * * between iRMX 86 Release 6.0 and iRMX 86 Release 5.0 * * * ****************************************************************************** $save nolist /* BIOS EXCEPTION CODE LITERALS */ /* This literal file was supplied as ZBRA25.LIT with the iRMX 86 UPDATE 2, 12/28/84. It corrects the spelling of "E$IDD" to "E$IDDR". */ /* Environmental Exceptions */ DECLARE E$FEXIST LITERALLY '0020h', E$FNEXIST LITERALLY '0021h', E$DEVFD LITERALLY '0022h', E$SUPPORT LITERALLY '0023h', E$EMPTY$ENTRY LITERALLY '002 installed. *** The terminal support code is only guaranteed to work with keyboard-input terminals. *** The standard configuration of the Release 6.0 Files Utility system does not support the Intel iSBC 204 or the iSBC 206 I/O controllers. However, the Files Utility may be reconfigured to include them. *** Only iAPX 86/88 based systemn is now the middle of the disk.) o Control C now aborts the rest of a SUBMIT file. Control C now also works in SUPER. o The DIR command now allows you to use the FOR parameter to select specific files within a directory. (FOR can be used in conjunction with wildcard file designators to select specific files within a directory.) o The Release 6.0 version of the SUBMIT command allows you to use the ECHO parameter. When the TO parameter is usedhe iSDM 86 monitor. *** END SECTION ONE *** ______________________________________________________________________________ NOTES SECTION TWO Difference Between iRMX 86 Release 5.0 and iRMX 86 Release 6.0 o The SUPER command now needs "exit" to exit from the SUPER utility. Simply typing "e" will no longer work. o The Release 5.0 startup system on the installation diskette came configured with a:I = 'BAUD RATE' ESC\, the terminal locks until another "ESC\" is entered. But the same OSC sequence copied to a terminal through a SUBMIT file works without the second "ESC\" Also, turning ECHO off will have no affect until a query is issued. o The RAM Driver allows the I/O system to designate an area of RAM to be used as a physical volume or as a named volume. If the area is designated as a named volume, it can now be used in conjunction with the LOC before installing Release 6.0.) o An additional fnode has been added to the fnode file created when the volume is formatted. Fnode 5, which referenced the root directory in Release 5.0, is now the volume label fnode. (Fnode 6 is now the root directory fnode.) o The FORMAT utility contains a new function called "MAPSTART". MAPSTART allows the user to specify the location of the fnode file, bit map files, and the root directory. (The default locatios support the Dynamic Debugger. *** iRMX 86 Release 6.0 will run on systems which contain the iSBC 957B monitor. Existing configurations of the iSBC 957B monitor that include the Release 5.0 Bootstrap Loader can be used to boot load Release 6.0 systems. However, the Release 6.0 Bootstrap Loader cannot be configured into the iSBC 957B monitor. If you wish to upgrade to the Release 6.0 Bootstrap Loader, you must have t to redirect output, the ECHO parameter causes a copy of the data read from the first level of the SUBMIT file to be sent to the CRT. o The System Debugger (SDB) has a new command "vu" which unwinds the stack for iRMX 86 system calls. o The Release 6.0 UDI now returns an E$PARAM error when more the 2 buffers are specified in a call to the DQ$OPEN system call. o When you change the baud rate on the terminal by entering the OSC sequence " ESC]T  resident Human Interface user. The Release 6.0 startup system is configured for a non-resident user (T0) whose configuration information is contained in the /config/terminals file. o If you install Release 6.0 using the installation procedure outlined in the iRMX 86 Installation Guide, your Winchester Disk is formatted automatically and all files that were on the disk are removed. (If there are files on the disk that you wish to save, use the BACKUP Utility DATA command to load Human Interface commands into ROM. (See the iRMX 86 Introduction and Operator's Reference Manual) o In Release 5.0, the iRMX 86 Operating System accessed floppy diskettes as named volumes only if track 0 was single density with a sector size of 128 bytes. This is called iRMX 86 Standard format. In addition to Standard format, Release 6.0 also supports a new format called Uniform format. On diskettes that conform to Uniform format, track 0 or position) sequences to communicate with a terminal. Specifically, you must reverse the order in which the vertical and horizontal coordinates are specified in CUP and CPR (i.e., for Release 6.0 applications, the vertical coordinate must be specified first and the horizontal coordinate second). Also because of this discrepancy, the Release 5.0 version of the iRMX 86 System Analysis Test (RSAT) in not compatible with iRMX 86 Release 6.0. o transfer can occur from any other floppy. o The Terminal Support Code can handle Xon, Xoff, highwater, and lowwater marks for buffered communications device drivers (such as the iSBC 544 board.) o You can now set Head Load Time and Step Rate for floppy diskettes during ICU configuration. o The EIOS contains a call--RQ$HYBRID$DETACH$DEVICE. This call is similar to LOGICAL$DETACH$DEVICE except that it leaves the logical name in the root job object" rather than ":W0:/SYSTEM/RMX86". o There are some minor differences between the Release 5.0 version and Release 6.0 version of the RQ$A$SPECIAL call. In the Release 6.0 version, the query function of an OSC sequence returns more characters than it did in Release 5.0. Also, there are now more elements in the data structures used by the "get attribute" and the "set attribute" functions of the spec$func parameter. For a complete explanation of thesethe Release 6.0 ICU screen for the 8251A terminal driver displays the inrate frequency value as if it had not been divided. Thus if you specified an inrate frequency value of 12C00H, the value displayed by the ICU will be 12C000H, (rather than 12C00H). o In order to operate properly under Release 6.0 of iRMX 86, minor modifications must be made to any application task that uses the ANSI CUP (set absolute cursor position) and CPR (report absolute curshas the same granularity as the rest of the diskette. To access Uniform format diskettes, you must use the ICU to create a Device Unit Information Block for Uniform format. Notice that Automatic Boot Device Recognition does not work on Uniform diskettes unless the device granularity is 128 bytes/sector. o Overlapped and Automatic seeks now work for the iSBC 208 and the iSBC 215/218A drivers. However, while one of the floppies are seeking, no data Previous versions of the Bootstrap Loader automatically added the prefix "/SYSTEM/" to any file name that did not start with a "/". For example, the file ":W0:RMX86" would be treated as ":W0:/SYSTEM/RMX86". By contrast, the Release 6.0 Bootstrap Loader supplies a "/" to any file name that does not already begin with one; however, it does not supply the full prefix "/SYSTEM/". Therefore, the Release 6.0 Bootstrap Loader would treat ":W0:RMX86" as ":W0:/RMX86 directory. o For the 8251A terminal driver, earlier versions of the ICU required that the user divide the Inrate Frequency Parameter (IFP) value by 10H before entering it in the ICU. The Inrate Frequency Parameter (IFP) for all types of terminal drivers is now processed according to a single algorithm. The Release 6.0 version of the ICU automatically divides the value by 10H, regardless of the type of terminal driver being configured. Notice that  new features, see the description of the RQ$A$SPECIAL call in the Basic I/O System section or the Extended I/O System section of the iRMX 86 Programmer's Reference Manual, Part I (Order Number: 146195-001). o Intel has adopted a new file naming convention for Human Interface commands. On the Release 6.0 Human Interface Commands diskette, the suffix ".r86" is now attached to the end of all Human Interface commands. On the same diskette, a SUBMIT filРUP^SF^&?uvv^S^&?t vFP[vPFP^SFvFP^&?uF& t ^&F& rFP^&/~ uaF&(F^&N u&09F t" 10^v&NF1F׋F t^& NF&6&8^&G&WF&&^&G<u&G^&GF&(FF~vFF&>Jt&M;Fu &LFF&>Jv&P;Fu &OFF&>Jv&S;Fu &RFF%FF #;uNF#;uNF~u F^D*ttes. A version file is provided with each layer of the operating system. It resides on the same installation diskette as the layer associated with it. (For example, on the diskette that contains the iRMX 86 Nucleus, there is a version file called "NUCLEUS.060".) You can access this information by using the Human Interface COPY command. ******************************************************************************* * 4h', E$DIR$END LITERALLY '0025h', E$FACCESS LITERALLY '0026h', E$FTYPE LITERALLY '0027h', E$SHARE LITERALLY '0028h', E$SPACE LITERALLY '0029h', E$IDDR LITERALLY '002Ah', E$IO LITERALLY '002Bh', E$FLUSHING LITERALLY '002Ch', E$ILLVOL LITERALLY '002Dh', E$DEV$OFF$LINE LITERALLY '002Eh', UDUFIL2STACKMEMORYCODEDATADGROUPCGROUPZAPS??SEGPHCǘH T0ԘDh X b {\{|euqz{ Hunڎ tsur  E ts Ў   ts  Ԏ ts͎{|muc   tsnjXRQCREATEMAILBOX RQAGETFILESTATUS RQRECEIVEMESSAGERQDELETESEGMENTRQDELETEMAILBOX\\ U_FILE_INFOހUDUFILPLM86 V2.305/16/84 19:50:2e named "instal.csd" copies these commands into the "/system" directory on the iRMX 86 hard disk. In the process, each command is appropriately renamed. For example, the file name "hdir.r86" on the installation diskette will be copied onto the hard disk as "/system/dir". o The iRMX 86 Installation Guide lists the version number for each part of the iRMX 86 Operating System. However, version information is now also provided on the installation diske>TbZ&G F^&GFtIF&*&,^&G&WF&2&4&G&WvFP] 5NUDUFIL_REPLACEMENT_ZBRA11ASM86.86 V2.0wZBRA11K30?Ίt * * END NOTES FILE * * * ******************************************************************************* E$IFDR LITERALLY '002Fh', E$FRAGMENTATION LITERALLY '0030h', E$DIR$NOT$EMPTY LITERALLY '0031h', E$NOT$FILE$CONN LITERALLY '0032h', E$NOT$DEVICE$CONN LITERALLY '0033h', E$CONN$NOT$OPEN LITERALLY '0034h', E$CONN$OPEN LITERALLY '0035h', E$BUFFERED$CONN LITERALLY '0036h', E$OUTSTANDING$CONNS LITERALLY '0037h', E$ALREADY$ATTACHED LITERALLY '0038h', E$DEV$DETfile.Read error on temp file.Write error on temp file.Not enough memory for disk buffers.Maximum file size exceeded.: lines, bytes. : new file. *abcdefghijkm nolpqr@stuvwx=   +-^?/$.'\. *$[r rcD LITERALLY '0052h', E$IO$OPRINT LITERALLY '0053h', E$IO$WRPROT LITERALLY '0054h'; /* Programming Exceptions */ DECLARE E$NOUSER LITERALLY '8021h', E$NOPREFIX LITERALLY '8022h'; $restore 7PBtPFP,$1UQF^tF 0FFF]UVFPFP#FFBF< u<-uoFPFP#FFBvPP.뱍FPYF uF 뛍FPCb돸PT냠s 6PAFPFPO#FFBNPFP 딋]U^^tFF]UFvFnED=%PDY3STACKMEMORYCODEDATACONSTDGROUPCGROUP??SEG %%Ș ` ߘ "r"> k  %%p@"PLM86 V2.11/01/78 00:00:00jr(C) 1981 INTEL CORPe?elmILLEGAL INVOCATION OPTION.MULTIPLE FILE NAMES IN INVOCATION. LINE EDITOR, V1.1ed.mac0123456789ABCDEF:ci::co: Cant't create temp file.Can't open temp file.Seek error on temp ACHING LITERALLY '0039h', E$NOT$SAME$DEVICE LITERALLY '003Ah', E$ILLOGICAL$RENAME LITERALLY '003Bh', E$STREAM$SPECIAL LITERALLY '003Ch', E$INVALID$FNODE LITERALLY '003Dh', E$PATHNAME$SYNTAX LITERALLY '003Eh', E$FNODE$LIMIT LITERALLY '003Fh'; /* E$IO expanded with unitstatus codes */ DECLARE E$IO$UNCLASS LITERALLY '0050h', E$IO$SOFT LITERALLY '0051h', E$IO$HAR:work:rq$r&7PP%7Ƈ88P YP$ 3~lPP$>uQPQ6 s P! : UQs6HFP$~tmJ]U ]UQ+b%dF+ȉsPPPD]UQ9;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; ; ; NAME: ZBRA25.CSD ; DATE: 10 OCT 84 ; ; ; NOTE: This submit file applies the above ZAP to the iRMX 86 ; Operating System object code. This submit file can be ; executed on an Intellec Series III, a Series IV or an ; iRMX 86 development system. ; ; The following parameter list (in order) must be used for ; the correct application of ]U~ u P P<0~ u P<<;1 u <v]U9r::~u -Pj r~tvPPFPI!~tFF;w؂uFFu݋^GrXG;u s ,^wFPFP F+^GwFPD ^G~uPPPFP~uP6F Pv Fs~!uPP]UQjFPuv3PPD.=y~V[s|"*EIv >P6,e P^k P _F< t MPi OPbf$ *;;yt^]UQQMFtzM)Om3$FuFG;uhF `GFG؊$FuHF?w拄GFG؊$Fu.!GFF]UQQLF?u Os F&~\u"+F<#tu1^ヿu^>tFMva]UQPFP,]UFvPFFf^^t&FFNuFFPPYFF̸]UFJFPP-FFf^vtC^<  ]U FĴFF%F~r SP+FFFF;wF^G;Fu)~uG^;t v F^mFF؋FFuFF؊Os wwPF^GGrvwP^G~t@^GFG]UF@P*pP#vsP|P ]UQ P FF;w4$s9FLsv^7PFá9]UQ P PFP~u PPPFP~t7 e P+@P&]UQQve b PFP$@؍FGFGFG]UQ>u?uwFPH؍?ufGs_G;us 2wPPFPwPPwFPGG;u]UQ>t6M FF< t YPPF|w[P7Fu -|L7,+7{9{xP+sM PPFPSF~tPvPSs\K)>u@P DP<7PO/i*d"!+P P]BU]UQPPFPq]U]Uy]UQdfFFwLJFu]U >t` PFPP7PPrF< tF-7@Ff+db+ 10RH]U tP+P06]U^t PF]U:v P]U:F+Pm:P><sP P]U%P]U]UQQrDPFPwH~t Pu6HPPFP~t PT6HPFPF PFP~t P!~u 6HvPFPqF~t'6HvPFP~t P]UQ- ;v>t>r ;s /PFHN;r5؍ LJ F  Ƈ Ƈ Fuu&JFF-%JF]FNuFFPPFFUQF^< t< u,^? uF;F1N+ʉNFFNjF;1]U Fjs6>hu/FF;v 7F؂?t PmhnFF;hw HƇ FuhFs-Ls P>FF;hw PFuAFF8Fu~tM^]F$F< u^#~tF^C^raF뭰^huh< t< uh~.uhu^h.u₿u thUvs F;Fwڰ]UFs 6sP7PFF;tz^7 FF6sFPvO^?u&GF^t6:Fu vvrFvvs F ^?u]FUFFF;wcrssPvtFFjFs?tPPtI^'PSiFFF딊Fr]UQFF؋N9Fs^vFF֋]UQ;ps^p7Fp^]UCF uFFFs!Pl+QFP~t]U>u ;v]U t]U>u;u]U>tt]U;r;s;s;rB]UQPF< t#FN+ȡ+;r]U F< tNu踀PN~ ttF< t~ tFF< t^FF^G<:tNu-OFF^t <:uC^FvvL鿁2w؋ ^a;t FߊFs{FM~u$FFF;sN9FvFF]U>t~F< ukvFF< t?u^UF7~r^$F^Ft< tFu끋FHFذF^]U hFFFPV~t F];rsFFFFNF;FvF+FF+F؋^ڋF^|UQnHnPBs+67Pl+QFPv~t{nl7uFll]Unl7FF;w37FF^FFu Pa P[vS67pFWPFFFFFVF;s.^+ډщV;tJvvvvvv(NF;r#FvPvvvvd]UFFF<0re<9waFF0:r%<9w!F FVµ+FFҊFM~uFvs^FFFF~u~tFvP>.C Y ^ ^ o o 0!FN~uFvF~/uFF;vFF;sFPvmrlF;u6s묡FGPzFNtFs NPP]UQ6FP ~t]UFFFF#F<\u FF< t^u>u FFvMPOu^P6^]UF;Fs؊^C^F7r݋F]UFF7FF;s_؊^FFvs-F$F1:r<6wv*2<rFF$^C^7r^]UQQ r;rݰPcFP7P ^F]UFFFFF:Fu ^?u@6~^u F6~*usFM~2sXF8Fu ^ FW~*tFFvP޴.##l$%%%t$$$$F<(u&~s,F^F^C^FF~)u%F;Fr^ C^FHF؈K^F~ tpF$^^܋^<t< uu܋^M:Fuf^ o^GFFF<^u F^GF<]t#< t@F$^C^F2s)F֊F^G덋^the ZAP. An example for ; Series III, Series IV and iRMX86 is included. ; ; ; APPLICATION: submit ZBRA11.CSD( %0, %1, %2, %3, %4, %5, %6 ) ; ; %0 = Pathname for the directory that contains your ; system commands (i.e., submit, copy, rename, delete). ; (ex: Series III = ":f0:", Series IV = ":system:", and ; iRMX 86 = "/system/") ; ; %1 = Pathname for the directory that contains your language ; utilities (i.e., ASM86, Lthe ZAP. An example for ; Series III, Series IV and iRMX86 is included. ; ; ; APPLICATION: submit ZBRA25.CSD( %0, %1, %2, %3, %4, %5, %6 ) ; ; %0 = Pathname for the directory that contains your ; system commands (i.e., submit, copy, rename, delete). ; (ex: Series III = ":f0:", Series IV = ":system:", and ; iRMX 86 = "/system/") ; ; %1 = Pathname for the directory that contains your language ; utilities (i.e., ASM86, L Series III = ":f1:", Series IV = ":rmx86:ios/", ; and iRMX 86 = "/rmx86/ios/") ; ; %4 = 'RUN'. This parameter is only needed for ISIS Series ; III development systems. ; ; %5 = 'EXIT'. This parameter is only needed for ISIS Series ; III development systems. ; ; %6 = ';'. This parameter is only needed for Series III and ; Series IV development systems. ; ; ; ASSUMPTIONS: None. ; ; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; ; ; NAME: ZBRA11.CSD ; DATE: 20 APR 84 ; ; ; NOTE: This submit file applies the above ZAP to the iRMX 86 ; Operating System object code. This submit file can be ; executed on an Intellec Series III, a Series IV or an ; iRMX 86 development system. ; ; The following parameter list (in order) must be used for ; the correct application of C^F$Fۋ]_^[SVW _^VW_^[SVW _^VW_W_^[SVW _^[SVW _^VW_^[SVW _^VW _^Y[SQVW_^VW_^[SVW _^Y[SQVWȊINK86, LIB86). ; (ex: Series III = ":f0:", Series IV = ":lang:", and ; iRMX 86 = "/LANG/") ; ; %2 = Pathname for the directory that contains the contents ; of the iRMX 86 Update Package. ; (ex; Series III = ":f4:", Series IV = ":rmx86:update/", ; and iRMX 86 = "/rmx86/update/") ; ; %3 = Pathname for the directory that contains the iRMX 86 ; object code (e.g., nuc3.lib, xcmdrv.lib, eios.lib). ; (ex:INK86, LIB86). ; (ex: Series III = ":f0:", Series IV = ":lang:", and ; iRMX 86 = "/LANG/") ; ; %2 = Pathname for the directory that contains the contents ; of the iRMX 86 Update Package. ; (ex; Series III = ":f4:", Series IV = ":rmx86:update/", ; and iRMX 86 = "/rmx86/update/") ; ; %3 = Pathname for the directory that contains the iRMX 86 ; object code (e.g., nuc3.lib, xcmdrv.lib, eios.lib). ; (ex:;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; %4 %1lib86 delete %3udi.lib(udufil) add %2zbra11.rmd to %3udi.lib exit %5 ; This line is only applicable to iRMX 86 R6.0 development system users. %6permit %3udi.lib r u=world NOT FOUND SEGMENT NOT FOUND ATTRIBUTE MODIFIED P PPPP P> uLP P> u86PP P> uw6PP P> uv6P)P P6P&P P6PP Ps6PP P^> us P P  > uyP P > ub>u 6lƇP PPPP P> uY6 PsP P > ub>u>  u6P`6PP Pm> uezu6PP PO;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; %0delete %3iexcep.lit %0copy %2zbra25.lit to %3iexcep.lit ; This line is only applicable to iRMX 86 R6.0 development system users. %6permit %3iexcep.lit r u=world PP P=> u hȴ;r u 6SPQ P> uՠȈ$ (6PP P> u6SPQ Pe> u6PP PT> u6PP P86PP P> utPPPsb6P6 P> uC6(PP P6PP P6,PP P댼 t:PP PB6PP Px6.PP Pcn#PTCH86(3STACKMEMORYCODEDATACONSTDGROUPCGROUP??SEG d d 4 ee> b   f d d  ffp0@pPLM86 V2.301/01/78 00:00:0hri Copyright 1981, 1982 Intel Corporationprogram_version_number=V2.3program_name=iAPX 86, 88 Object Patch UtilityINVALID RECORD TYPE :CO: iAPX 86, 88 Object Patch Utility, V2.3 INVALID SYNTAX INVALID SYNTAX INVALID MODULE TYPE SEGMENT  Series III = ":f1:", Series IV = ":rmx86:ios/", ; and iRMX 86 = "/rmx86/ios/") ; ; %4 = 'RUN'. This parameter is only needed for ISIS Series ; III development systems. ; ; %5 = 'EXIT'. This parameter is only needed for ISIS Series ; III development systems. ; ; %6 = ';'. This parameter is only needed for Series III and ; Series IV development systems. ; ; ; ASSUMPTIONS: None. ; ; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;> u9 uehsPPPr6P H; v{6cPP P> u6dPcP P> u^c @ cPPshih{6SPQ P4> u9"s6PPPr6PP PS6PP Pt:u6PP<u6PQ P> u6PP Po> uߠ I;vP6XTSIOۖ2STACKMEMORYCODEDATADGROUPCGROUPZAPS??SEGPH H T8̘Dh X RQRECEIVECONTROL RXSENDCONTROL RQSENDMESSAGE RQSENDUNITS IORS_ENQUEUE IORS_DEQUEUETSINPUTREQUESTTSOUTPUTREQUEST TSGETCONN TSSETCONNTSCFGDECODEOSCTSCFGTRANSLATERXUNITSAVAILABLEI544UNITSAVAILABLE\\ TSCANCELIO TSQUEUEIO!XTSIO݈PLM86 V2.310/05/84 13:29:3ՠ% /!U"^&G$FF^&G(F6 PPUF1 uF t=6PP P> t>t16v_r6pPP P^&]COMMONPUBLICINVALID SYNTAX U^&^&:t@^&8v*s"S^&H_[&:Htˠ]UcP P >tLdbcr=.:bv3dQPScbd&d뼠csb˷.]6PP Pr]_W F&&N && &"F &&:&><&&>&6vPPF &FF &*;F rrF PS&"QF(Rv QF &&&(RPPvvPF&>u5F&(#;u;&(@tv v vvF&=v] !#V DSmJZ!eUQF &6vPF t3&t F&!IF&F &F&-v vPvv9FF&>t F &F];ILNMAT_REPLACEMENT_ZBRA14ASM86.86 V2.0wZBRA14D41=ъtFF0^FF & ^^F&FPF & .f^&v ^&&u^&v ^&&tF &*F &&^FF &> t^&?sv ^&G&HF&G vFF;v@+FN^^^Y^F&Gv&s ^&OF t-^w^^Y^F&G ^&GF &> t^&GF&GF&GF^&r&G tGFu.>uNv FDRcegikmo v^ē İ І {&!F &&(&6&PFP^&u&v ^&F &&(&6&PFPF &,^&;u&LJ^&t4&u & ^ PF^&;FuS^&tS^&]!"<e ̆׆ZU^&G$FFF0^Fv&D^^F&&FP^&F u&FFFF^&N;tD&*;V u3QP^&F&,&&(&6&PFPILNMATWSTACKMEMORYCODEDATA BIOS_CODE BIOS_DATA BIOS_DGROUP BIOS_CGROUPZAPS??SEGCGROUPԘH H T6 ̘D h ܘH X  o MARKFNODE ALLOCFNODE DEALLOCFNODE BUFFEREDIOENTERDLL LOOKUPDLLDSSMUL DELETESEGMENTRQCREATESEGMENTߚZZ Q  CREATEIFN LOWNUMATTACHeILNMATPLM86 V2.307/12/84 08:03:0ؠiUQQF &")FPFPFF&>t+FNFrv vvF F&>tvP_W_W _W _W_W _W _W _W_W_W%&uQ~& ˜  ܆ &F@Nߵ&@cNF^&O r@w ^& *F^&!FuF & F &*F^&Z&Wt~}^Y.>u^&!G^c!^^&&&LJ&Ƈ &&&&v&D@^&&F&^&G F^SVF&>u2^&Gt&uv&DF^SVF &F&F &&RF &(&6&w^&sU&Ƈv&D F^SV;v u^&F.>uNvqs vF%t^&&8t &&^&GHF vFF;v]+FN^&s6vt~^Y^&g^&G F^SV^~t+FFHN;r^&@ t^&@Fu.>u^&!GFF^&3Gu-^&G;Fu!&G;FuF^&3Gt &sFFsU^&G F^SVAF &> t^&GF߱ :r<@w(N߀~uF ~ v F &^Fߴ&HcN t wI&&Hc^&?tFF we^F뜎F&*;F u:^&^&F&,&&(&6&PFP^&u&F&*;N uw&,^&&^&&t4&u & ^ PF^&;FuSF&(&6&PFP^&F u&FFFF^&N;tD&*;V u3QP^)L܆ f t!E&F&,&&(&6&PFPF뜎F&*;F u:^&^&F&,&&(&6&PFP^&u&F&*;N t&nd it in the list below, then * (2) add an asterisk to that line. * * NOTE: ZAPs with an asterisk next to them are not installed by the * update process. Some ZAPs are supplied this way because they * provide a feature or fix which has side effects. These ZAPs * should only be installed if you need the feature or fix and * have read the documentation concerning that ZAP. This * documentation will explain the side effects. If you need to * install one of these;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; ; ; NAME: zbra27.CSD ; DATE: 10 OCT 84 ; ; ; NOTE: This submit file applies the above ZAP to the iRMX 86 ; Operating System object code. This submit file can be ; executed on an Intellec Series III, a Series IV or an ; iRMX 86 development system. ; ; The following parameter list (in order) must be used for ; the correct application of Z00) ZBRA18(PZZ07) ZBRA21(PZZ03) ZBRA22(PZZ08) ZBRA24(PZZ04) ZBRA25(PZZ12) ZBRA27(PZZ03) ZBRA28(PZZ03) ZBRA29(PZZ03) ZBRA30(PZZ11) ZBRA31(PZZ11) ZBRA33(PZZ03) * ZBRA34(PZZ00) ZBRA40(PZZ11) ZBRA41(PZZ11) ZBRA42(PZZ03) ZBRA44(PZZ05) ZBRA45(PZZ05) ZBRA46(PZZ05) ZBRA47(PZZ05) ZBRA48(PZZ05) ZBRA49(PZZ05) ZBRA50(PZZ05) ZBRA51(PZZ05) ZBRA52(PZZ03) ZBRA53(PZZ01) ZBRA54(PZZ03) ZBRA57(PZZ12) ZBRA58(PZZ12) ZBRA60(PZZ03) * ZBRA61(PZZ03) * ZBRA62(PZZ03) * ZBRA63(PZZ03) * ZBRA64(PZZ03) * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * NAME: zaps.cfg * DATE: 08 Feb 85 * * DESCRIPTION: This file contains the list of ZAPs. * Refer to the Update Installation Guide or the file * on the Update Package diskette named "instal.doc" * for more information on each zap. * * After reviewing each ZAP description, you may decide * NOT to apply one or more of them. * * For each ZAP that you choose NOT to apply, simply: * (1) fi,^&&&(&6&PPFP^&^&&*ȵN&&F&Ƈ t&u&PFP ^&LJ^S^&])FtȆ.9XTSIO_REPLACEMENT_ZBRA271ASM86.86 V2.0wZBRA27E20?Ίt ZAPs, remove the asterisk from the line * containing the ZAP. * * * SPECIAL NOTE: The letters and numbers (e.g., PZZ00) inside the * parenthesis are used by the generation submit files * (s3gen.csd, s4gen.csd, and r6gen.csd) and MUST NOT be * changed or deleted. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * ZBRA00(PZZ08) ZBRA01(PZZ08) ZBRA02(PZZ00) ZBRA06(PZZ06) ZBRA09(PZZ05) ZBRA11(PZZ08) ZBRA14(PZZ03) ZBRA15(PZZ03) ZBRA16(PZZ00) ZBRA17(PZthe ZAP. An example for ; Series III, Series IV and iRMX86 is included. ; ; ; APPLICATION: submit zbra27.CSD( %0, %1, %2, %3, %4, %5, %6 ) ; ; %0 = Pathname for the directory that contains your ; system commands (i.e., submit, copy, rename, delete). ; (ex: Series III = ":f0:", Series IV = ":system:", and ; iRMX 86 = "/system/") ; ; %1 = Pathname for the directory that contains your language ; utilities (i.e., ASM86, L ZBRA65(PZZ03) * ZBRA66(PZZ03) * ZBRA67(PZZ03) * ZBRA68(PZZ08) ZBRA73(PZZ03) ZBRA74(PZZ03) the ZAP. An example for ; Series III, Series IV and iRMX86 is included. ; ; ; APPLICATION: submit ZBRA14.CSD( %0, %1, %2, %3, %4, %5, %6 ) ; ; %0 = Pathname for the directory that contains your ; system commands (i.e., submit, copy, rename, delete). ; (ex: Series III = ":f0:", Series IV = ":system:", and ; iRMX 86 = "/system/") ; ; %1 = Pathname for the directory that contains your language ; utilities (i.e., ASM86, L Series III = ":f1:", Series IV = ":rmx86:ios/", ; and iRMX 86 = "/rmx86/ios/") ; ; %4 = 'RUN'. This parameter is only needed for ISIS Series ; III development systems. ; ; %5 = 'EXIT'. This parameter is only needed for ISIS Series ; III development systems. ; ; %6 = ';'. This parameter is only needed for Series III and ; Series IV development systems. ; ; ; ASSUMPTIONS: None. ; ; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; Series III = ":f1:", Series IV = ":rmx86:ios/", ; and iRMX 86 = "/rmx86/ios/") ; ; %4 = 'RUN'. This parameter is only needed for ISIS Series ; III development systems. ; ; %5 = 'EXIT'. This parameter is only needed for ISIS Series ; III development systems. ; ; %6 = ';'. This parameter is only needed for Series III and ; Series IV development systems. ; ; ; ASSUMPTIONS: None. ; ; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; ; ; NAME: ZBRA14.CSD ; DATE: 16 JUL 84 ; ; ; NOTE: This submit file applies the above ZAP to the iRMX 86 ; Operating System object code. This submit file can be ; executed on an Intellec Series III, a Series IV or an ; iRMX 86 development system. ; ; The following parameter list (in order) must be used for ; the correct application of INK86, LIB86). ; (ex: Series III = ":f0:", Series IV = ":lang:", and ; iRMX 86 = "/LANG/") ; ; %2 = Pathname for the directory that contains the contents ; of the iRMX 86 Update Package. ; (ex; Series III = ":f4:", Series IV = ":rmx86:update/", ; and iRMX 86 = "/rmx86/update/") ; ; %3 = Pathname for the directory that contains the iRMX 86 ; object code (e.g., nuc3.lib, xcmdrv.lib, eios.lib). ; (ex:INK86, LIB86). ; (ex: Series III = ":f0:", Series IV = ":lang:", and ; iRMX 86 = "/LANG/") ; ; %2 = Pathname for the directory that contains the contents ; of the iRMX 86 Update Package. ; (ex; Series III = ":f4:", Series IV = ":rmx86:update/", ; and iRMX 86 = "/rmx86/update/") ; ; %3 = Pathname for the directory that contains the iRMX 86 ; object code (e.g., nuc3.lib, xcmdrv.lib, eios.lib). ; (ex:;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; %4 %1lib86 delete %3xcmdrv.lib(xtsio) add %2zbra27.rmd to %3xcmdrv.lib exit %5 ; This line is only applicable to iRMX 86 R6.0 development system users. %6permit %3xcmdrv.lib r u=world ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; %4 %1lib86 delete %3ios.lib(ilnmat) add %2ZBRA14.rmd to %3ios.lib exit %5 ; This line is only applicable to iRMX 86 R6.0 development system users. %6permit %3ios.lib r u=world an change any of these pathnames to logical names or to * any VALID iRMX 86 pathname. * * * SPECIAL NOTES: Three VERY IMPORTANT rules to remember: * * (1) Do NOT change the order of the pathnames in this file. * The order is essential for the r6gen.csd submit file to * work properly. * * (2) Do NOT remove any of the pathnames from this list. The * number of pathnames in this file is essential for the * r6gen.csd submit fil/] eU^&GtJ&!F&^F&GF^SV^&t&!S]XTSMOD_REPLACEMENT_ZBRA28ASM86.86 V2.0wZBRA28E20@̊tctory contains your language utilities (e.g., ASM86, LIB86, * LINK86). The second path is for the system commands. This * directory contains your System Commands (e.g., copy, delete, * rename, submit). The rest of the pathnames are for the iRMX 86 * layers (starting with ":rmx86:nucleus/". * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * /lang/ /system/ /rmx86/NUCLEUS/ /rmx86/TH/ /rmx86/IOS/ /rmx86/EIOS/ /rmx86/LOADER/ /rmx86/SDB/ /rmx8* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * NAME: r6path.cfg * DATE: 9 MAY 84 * * DESCRIPTION: This file contains the list of the pathnames * used by the Update Package for iRMX 86 development systems. * All of these pathnames are standard iRMX 86 directory * names. Read the Update Package "Customer Letter" or the "read.me" * file on the Update Package diskette for more information about * these pathnames. * * You cXTSMOD2STACKMEMORYCODEDATADGROUPCGROUPZAPS??SEGPH8ӘH TDh X  TSSTUFFINPUT\\1 TSCARRIERLOSS TSQUERYMODEM TSRINGINGlXTSMODPLM86 V2.310/05/84 13:32:5٠pUP^S_P^SMP^S:P^S^&u&GuAHP^SP^S\P^S]D "-P[f0olU^&GtT&F&^F&GF^SV^&G F^SV^&t&!Se to work properly. * * (3) If you decide to change any of the directory pathnames * below, you MUST put a slash "/" as the last character in * the pathname. If you change a pathname to a logical name * you will not need the slash "/" at the end. * * If you already have these standard directory names in your system, * you will not have to change anything in this file. * * * PATHS: The first path is for the language utilities. This * dire;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; ; ; NAME: zbra28.CSD ; DATE: 10 OCT 84 ; ; ; NOTE: This submit file applies the above ZAP to the iRMX 86 ; Operating System object code. This submit file can be ; executed on an Intellec Series III, a Series IV or an ; iRMX 86 development system. ; ; The following parameter list (in order) must be used for ; the correct application of 6/HI/ /rmx86/UDI/ /rmx86/CRASH/ /rmx86/FILES/ /rmx86/ICU/ /rmx86/INC/ /rmx86/LIB/ /t7^t2^v&8tA^v&^&@Fu^v&*t F&'Rv^ SPvvF&>u3^ &u,FrF FuF&FF&!v^ &wvvF؎F&>=u^FsW^ &&WFމVЉFVF&&&NQvvvPF&>u&=F&>u vvvF&>uF؉F|vvvINK86, LIB86). ; (ex: Series III = ":f0:", Series IV = ":lang:", and ; iRMX 86 = "/LANG/") ; ; %2 = Pathname for the directory that contains the contents ; of the iRMX 86 Update Package. ; (ex; Series III = ":f4:", Series IV = ":rmx86:update/", ; and iRMX 86 = "/rmx86/update/") ; ; %3 = Pathname for the directory that contains the iRMX 86 ; object code (e.g., nuc3.lib, xcmdrv.lib, eios.lib). ; (ex:;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; %4 %1lib86 delete %3xcmdrv.lib(xtsmod) add %2zbra28.rmd to %3xcmdrv.lib exit %5 ; This line is only applicable to iRMX 86 R6.0 development system users. %6permit %3xcmdrv.lib r u=world ISPATHWSTACKMEMORYCODEDATA BIOS_CODE BIOS_DATA BIOS_DGROUP BIOS_CGROUPZAPS??SEGCGROUPԘH> ǘH Tp D h ܘH X  D LOWNUMATTACH LOWNUMDETACHLOWNUMDETACHSAVEFINDNAME WRITEFILE)ZZ QSCANPATH\ISPATHPLM86 V2.307/12/84 08:04:3ԠYAUQF FtF^v&8u^v&8/t]Fՠ?UQ^&G^S^F tU^&?^u^&G^&G^Gg^FF w3^&the ZAP. An example for ; Series III, Series IV and iRMX86 is included. ; ; ; APPLICATION: submit zbra28.CSD( %0, %1, %2, %3, %4, %5, %6 ) ; ; %0 = Pathname for the directory that contains your ; system commands (i.e., submit, copy, rename, delete). ; (ex: Series III = ":f0:", Series IV = ":system:", and ; iRMX 86 = "/system/") ; ; %1 = Pathname for the directory that contains your language ; utilities (i.e., ASM86, L]D"Dl$KtUQQF&F&F&sF&9a^&?$uGP^F^&?/uF&F&FF&F&v^Sv^ Svvv]ISPATH_REPLACEMENT_ZBRA15ASM86.86 V2.0wZBRA15D41>ϊt Series III = ":f1:", Series IV = ":rmx86:ios/", ; and iRMX 86 = "/rmx86/ios/") ; ; %4 = 'RUN'. This parameter is only needed for ISIS Series ; III development systems. ; ; %5 = 'EXIT'. This parameter is only needed for ISIS Series ; III development systems. ; ; %6 = ';'. This parameter is only needed for Series III and ; Series IV development systems. ; ; ; ASSUMPTIONS: None. ; ; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;XTSOSC2STACKMEMORYCODEDATADGROUPCGROUPZAPS??SEGPHH T.֘Dh X ] TSSTUFFINPUT TSGETCONN TSSETCONN TSRINGING TSCARRIERLOSS TSQUERYMODEMTSCFGTRANSLATE\\" TSDECODEOSC TSSTUFFVALUEgXTSOSCPLM86 V2.310/05/84 13:33:5ؠLgc * Series III devicename. * * * SPECIAL NOTES: Two VERY IMPORTANT rules to remember: * * (1) Do NOT change the order of the devicenames in this file. * The order is essential for the s3gen.csd submit file to * work properly. * * (2) Do NOT remove any of the devicenames from this list. The * number of devicenames in this file is essential for the * s3gen.csd submit file to work properly. * * If you already use these +F $_F @BDFHJLNPRT( * contain the object code for iRMX 86 R6.0. All of * these devicenames are assumed to be :F1:. * * NUCLEUS :F1: * * TERMINAL HANDLER/DYNAMIC DEBUGGER :F1: * * BASIC I/O SYSTEM :F1: * * EXTENDED I/O SYSTEM :F1: * * LOADER :F1: * * SDB (SYSTEM DEBUG MONITOR) :F1: * * HUMAN INTERFACE :F1: * * UDI :F1: * * CRASH ANALYZER :F1: * * FILES UTILITY :F1: * * ICU (INTERACTIVE CONFIGURATION UTILITY) :F1: * * INCLUDE FILES :F1: * * INTERFACE LIBRARIES :F1: * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * NAME: s3path.cfg * DATE: 9 MAY 84 * * DESCRIPTION: This file contains the list of the devicenames * used by the Update Package for Intellec Series III Development * systems. Read the Update Package "Customer Letter" or the * "read.me" file on the Update Package diskette for more information * about these pathnames. * * You can change any of these devicenames to any VALID Intelle        8 /TERWOCQ 5 ;ALHMRWTFIOSXYUVGJKPQ*/T *&gUQF tP^S=P^SF'F9F s 1FFv0ȋF 10P^SF N1V 1FȋF 0P^SFs ,P^S] DS}CU F $F ^& ^ .L؋..4T]?Ph^&devicenames in your development work, * you will not have to change anything in this file. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * The devicename for the language utilities. This device contains * your Language Utilities. (e.g., ASM86.86, LIB86.86, LINK86.86) :F0: * * The devicename for the system commands. This device contains * your System Commands. (e.g., copy, delete, rename, submit) :F0: * * The devicenames for iRMX 86 R6.0. These devices3>Hafpſƈֈ߈uP^S\P^S^&^&@tu&F&^F&G F^SVO^&&SuAF $_^&G&&Gf^&G N 0&G&M^&D^&G N 0(^&MuGF u<^&G1^&G$tPPP$P8>$uY66)6 66666 6+6K6L66P6NP66.666/$Pl 6&PM8>$u&$>$u/s 6P"PP}%6 P6&P8>&u6&P6"$ tz+uw>(tp%P$P}PRPP<1P P%6'>(ufPP$66~PP$66 PM''6$}PRPP06&PM76$RP&P(7ErKUFVN tFVNFVN] Tn' VERSION3P0NN' ?STACKMEMORYCODEDATADGROUPCGROUP??SEGLQ_PLM86_LIB_CODEq @@ TTY    ee  @@՚ TTp@*PLM86 V2.307/09/84 09:05:4KrCopyright 1981, 1982, 1984 Intel Corporationprogram_version_number=V3.1program_name=iRMX 86 FORMAT:R?DISK:invalid number GRANULARITYGUG INTERLEAVEILIFNODES EXTENsiONSIZEESEFILESMAPSTARTMSM NAMEDPHYSICALPIPQUERYFwmap files do not fit#map files do not fit with save area volume formatted Bootstrap Loader written can't attach device while formatting track while writing block Unit status :co::co: , format? P$P;PP$Pl9$ tPPRPPN36PP+*BPP}P6-$P5>$t?>+u+P$P:$ tPRPRPP2PP6$P!:>$u6$P7 $ tP}PRPP2P6 cP$P9>$u;/r},P}PP/r'T@TxreUFN1 t F1@F1v]UQQ^SFPz,FF tP^ SlPP0F9Fr9FvP^ SlPP/F] UQ^ .hP^SR^S^SPPR^S^SPP8){^S^SPP2^S^SPP*J^S^SPP -^SFP* F tP^SlPP.] U>+) * -/.,PFP@-F tPRPRPP.FPPNQPRPRPFPld have done before starting this submit file!). Read * one of these before starting this submit file. * * PARAMETERS: There is one parameter for this submit file. * * %0 = The pathname of the directory where you copied the * contents of the Update Package. A logical name can * be used instead of a pathname. * * SPECIAL NOTES: This submit file builds the submit file "upr6.csd" * and then executes it. When this submit file is finished your *PFP#FPP&. 6    ( ( / / / ++,-./ӸPFPR]UFK$<uF3PPP ;PP>+uKTPP"oPPLRPP!l"PPi)RPP!GcP PJ>"PP;RPP!jPP!66 P!"PP)RPPl!Fs(PPKu12PQ!PP RPP(!Fs$>PPKuPPy!PPv*RPP F g/PZZ/#a g;(;.-1s;.*;&submit %0; g/(/#b g/(/#c g/(/#d g/(/#c g/(/#d g;(;s;$;&%0,; g/(/#c 1,$#e w %0upr6.csd q %0ed * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * NAME: r6gen.csd * DATE: 09 Oct 84 * * DESCRIPTION: This Submit file builds "upr6.csd" * using the two configuration files "r6path.cfg" and * "zaps.cfg". Both the "Customer Letter" and "read.me file" * from the Update Package describe in detail the contents * of the Update Package. They also explain the steps involved * in applying the Update Package (including the steps you * shou4FF tPRPRPP^.FrPPRPP@.~tPFPRPP#.~vPRP PP.FPPFPFP&~:t@PFPRPP-Nɵ~İ:u+JV;u@WNQRQP-FFNµNF¸}PPRPPFPFP*FF‹F tPFPRPPE-PPvBPF´+PFP$~tPFPPP-FPPNQPRPRPFP2rFtE~u1NQPQFP#FP{P&PFPFP뛸PFP 넀~u{FPNQ system will be Updated. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * Ua;s/(PZZ.*/(/; Ub;.-1,.j; Uc;.,.+1j; Ud;s/$/&,/; Ue;s/$/&)/; r %0r6path.cfg $r %0zaps.cfg g/\*/d g/PZZ/1t. 1d g/PZZ/1t.-1 g/PZZ/1t. g/PZZ00/1t.+2 1d g/PZZ01/1t.+2 1d g/PZZ02/1t.+2 1d g/PZZ03/1t.+2 1d g/PZZ04/1t.+2 1d g/PZZ05/1t.+2 1d g/PZZ06/1t.+2 1d g/PZZ07/1t.+2 1d g/PZZ08/1t.+2 1d g/PZZ09/1t.+2 1d g/PZZ10/1t.+2 1d g/PZZ11/1t.+2 1d g/PZZ12/1t.+2 1d g/PZZ13/1t.+2 1d s)TPPSKu P P P6*!PP'.s#PP!PPNPr]8 FVuPsWPPJ FVWPP) PP ]ݜ T5Tr UcP0PFP(0F tP}PRPP)>LuL66LL;s*W P;u;vPPPQ)>Ku>Lv( 666.>+t >ut;u;s NPFDBLOCKMAPR?VOLUMELABELR?SAVE?iRMX 86F02 TYQUr>&s]ø.024&?uBS.@.0&?uֹd1 u6PPS@,&)t*u&>u]]áx&?t]às$>PRP&?t]66&?t]àsQ6666666666 &?t]6*] ȎTrmU6PPPS])&?t]ø PPS&?t]ð5&w5F@ACEGȡ>ךPRP6fPIKMO?QSUWY 6PePRPSJ(6PPPS,(&?t]ø5PPS&?t]àsV6PPPS'-&?t]ø5PPS&?t]ð 5V PFVRP6FV6 PRP6FVPRvvWRP6_Y׃FV.svN~P+FVurFV FVFVFV+FV+FVJtTȀTT0TɨTr~;u;wPPPP'FV+FV;u;wPPPPz'>u> u$FV+FVRPP FV ;Vu;FrPPPP'.s/FV ;u;rPPPP&]R?SPACEMAPR?FNODEMAPR?BA6RPRPPO6666666666 &?t]66RPRPPPRPk 66RPRPRPRPL b ] ȫTTrUF 10¢5F1065]U(6P.P6^S)+^&?uP6PP^S+^&?u/&^&&.P+]7rU(6^ Sv6^S*^&?uz6P P^SN+ ^&?uY &^& &&+u6  P5V ȭTTr[6O7L81?N":u|2|1616PPPS5'&?t]ø5PPS6PPPS&&?t]PPS]r U 6PvvS&FV&?u6S'&?tLS&&?t H;sjv&&&&U&J& & &&&&d have done before starting this * submit file!). Read one of these before starting this submit file. * * PARAMETERS: There is one parameter for this submit file. * * %0 = The devicename for the device that you copied the * contents of the Update Package to. * * SPECIAL NOTES: This submit file builds the submit file "ups3.csd" * and then executes it. When this submit file is finished your * system will be Updated. * * * * * * * * * * * * * * * * * 66P]&&RP6G&&PRP&B&D_X& &O&W& &G&& &&RP6&&PRP&B&D_X6TȿTVTTrh&&G&Gv&&G&&&&&&>&B&D& &G&W> s&&G&&>+׎&&֋QWP&&&B&D_X&g/(/#c g/(/#d g;(;s;$;&%0,; g/(/#c 1,$#e 1,$s/)/,;)/ w %0ups3.csd q submit %0ups3.csd RUN %0ed * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * NAME: s3gen.csd * DATE: 09 Oct 84 * * DESCRIPTION: This Submit file builds "ups3.csd" using the * two configuration files "s3path.cfg" and "zaps.cfg". Both * the "Customer Letter" and "read.me file" from the Update Package * describe in detail the contents of the Update Package. They * also explain the steps involved in applying the Update Package * (including the steps you shoul.CSk&&O&&P&&RP6&&PRP&B&D_X& &&G&&66M TiTɚTrP}&&RP6g&&PRP&B&D_X& &&O&&6P=&&RP6&&PRP&B&D_X& &&&G&&* * * * * * * * * * * * * * * * * * Ua;s/(PZZ.*/(/; Ub;.-1,.j; Uc;.,.+1j; Ud;s/$/&,/; Ue;s/$/&,RUN,EXIT)/; r %0s3path.cfg $r %0zaps.cfg g/\*/d g/PZZ00/d g/PZZ/1t. 1d g/PZZ/1t.-1 g/PZZ/1t. 1d g/PZZ01/1t.+2 1d g/PZZ02/1t.+2 1d g/PZZ03/1t.+2 1d g/PZZ04/1t.+2 1d g/PZZ05/1t.+2 1d g/PZZ06/1t.+2 1d g/PZZ07/1t.+2 1d g/PZZ08/1t.+2 1d g/PZZ09/1t.+2 1d g/PZZ10/1t.+2 1d g/PZZ11/1t.+2 1d g/PZZ12/1t.+2 1d g/PZZ13/1t.+2 1d g/PZZ/#a g;(;.-1s;.*;&submit %0; g/(/#b g/(/#c g/(/#d &G&WP6S&?ut 6P"]TTraU6PN~PRPS[!N~P&?tvvPRP6P"$У&(5F FuFV+&(;u;r*5PQS5&(믋FV+&(*~.ы5+I6F F uF V+&(;u;r*5PQS5&(믋F V1,;rRwI8r8.ft8؍f 8؍vPQS,u]ǜ T=Tr 8 U6PPPS&?t]ø PPSH&?t]6PPPS@&?t]PPS]X- ؋FFFv3Pvv^FFFF= rߌȎ.OCopyright 1980, 1981, 1982, 1983, 1984 Intel Corporation program_version_number=V6.0program_name=iAPX 86, 88 Bootstrap LoaderX P.XYuF&F$F "`FPR t&t t u ,PR^&?/u GPR$.06&W1P.SS^$1 t.0FY.&G&GT&G $1(&w&wQ*,6TP.SP/V1V;r܋.&8tLPS.@P5s62PRV.&TP&?/uGPRvVuw6TPa8X>XuX3hq6>hudXv>hpuL>6vh $iFj>iu`4:.8р>i@+&(*~ . 5+I6F FuFV +&(ٜ T5TkT8r0O;u;r*5PQS]5&(믋FV +&(*~.ы5+I6F FuFV+&(;u;r*5PQS5&(믋FV+&(*~. 5+I65PPSP]UrzU6PךPRPS>ךP&?t], P. vǹ4^&t&W&g&G>_u &S&/SYSTEM/RMX86UFfs1PP^&7Y:u.^GFF ^GFFf뺀>fs ^&?t F24]U>u.SP8.BDB&gOBDa6]UNN]UJ&FJF~t[FJJ&FJ t~t7NJ&w>F^YJ&FJ@JN럋]U_~L7t@~htA"^s~?t@~ytA"_Fu><@봀>hu@t`:8X>hu+HF>6v~F&GFH>huaH`FbJL>6vGJ&GJLJZ\bJLJ;6\u;Zsh>6tj>at"P S6^`s8P^ S$P S6^]UQQ u~u!#P S6^>|u{u FFF F^6&6p6n^SSVnpu|tvx6x6v6(vx6&6x6v^SSvxld have done before starting this submit file!). Read * one of these before starting this submit file. * * PARAMETERS: There is one parameter for this submit file. * * %0 = The pathname of the directory where you copied the * contents of the Update Package. A logical name can * be used instead of a pathname. * * SPECIAL NOTES: This submit file builds the submit file "ups4.csd" * and then executes it. When this submit file is finished your *9Vu9Fv.Sv$)FV.Sv$+FVs.6$Pv.v0VFlnp6p6n6(npr|z~]UFf؋ʋFf‹]UFf‹]UF3vFv،]UFVv] 0123456789ABCDEF U6:@S6>?>]UQDFNw :sFDF]UF Ftr<+>;Fs6:^SvR@6>8vNFYF>D.++++~ Nu+Jt?]U>Du6:FPP.*;submit %0&; g/(/#c g/(/#d g/(/#c g/(/#d g;(;s;$;&%0,; g/(/#c 1,$#e 1,$s/)/,,,";")/ w %0ups4.csd q submit %0ups4.csd %0ed * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * NAME: s4gen.csd * DATE: 09 Oct 84 * * DESCRIPTION: This Submit file builds "ups4.csd" * using the two configuration files "s4path.cfg" and * "zaps.cfg". Both the "Customer Letter" and "read.me file" * from the Update Package describe in detail the contents * of the Update Package. They also explain the steps involved * in applying the Update Package (including the steps you * shouvx(;~uezCz6t抄;uJt@tzvx6x6vQKvxt;$u|(;~u r~~l;ru=l@lr|np6p6n6(np$;u;r)]U~u6&6,6*PS2Pvv6FVl$&(P`FV;Vu;Fs )FVlvv$&(P_rlnp6p6n6(np6r6(np6r$&(PN~+N~$ system will be Updated. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * Ua;s/(PZZ.*/(/; Ub;.-1,.j; Uc;.,.+1j; Ud;s/$/&,/; Ue;s/$/&)/; r %0s4path.cfg $r %0zaps.cfg g/\*/d g/PZZ00/d g/PZZ/1t. 1d g/PZZ/1t. 1d g/PZZ01/1t.+2 1d g/PZZ02/1t.+2 1d g/PZZ03/1t.+2 1d g/PZZ04/1t.+2 1d g/PZZ05/1t.+2 1d g/PZZ06/1t.+2 1d g/PZZ07/1t.+2 1d g/PZZ08/1t.+2 1d g/PZZ09/1t.+2 1d g/PZZ10/1t.+2 1d g/PZZ11/1t.+2 1d g/PZZ12/1t.+2 1d g/PZZ13/1t.+2 1d g/PZZ/#a g;(;s;t,<;>wF@6>&>< u >Du]UQFF:Fr PFu]UF t؍OQ^&P]r[<,UQQFV FV t vvFV ǃ0EFE] T8Tr,UQQFF;FV9Vu9Fsuv FVҋFV uFVN~0EFEFV;utu@Bt uuEƇF,EFVN~~vFV FVf]ќ3TYTȵTTrQo-UEFRPFtEUF Ft~ s ^&2^&F t!^Sv ^GP^&P^S]UF Ft~ s ^&1^&F t!^Sv ^GP^&P^S]UF Ft~s ^&]^&F tL&:F vBNF ^ &;s*ЈV^SvF ^ @PFP^S3]UQ^&P^&P. ^w^^t+JVYu^&^&^v&@^&H+]UF FtFt^&8s3^GFFFF:Fv^&@FFF^]UF Fu]\ȤTr} 3UQQ^S^SFV^&?u t&FV]query message error query errorU^ &rPP^SFPPP^SFPjF tP^S3PP P PPFPF tP^S3PPFF<]UFtAEP^SF^& tPRPRPP,F tF&$t;t F^&^SvFP^S^& u]F&>u%FPPRPP^ S^S$^& tPFP"FPFP^S^& tP^ SR4~v:FsP^ Sf9QP](^&P^ S9PPAP^S$F^&?ubF&6"P^SV^&?uvPFPSF^& t)P^ S9PP^&7^ JBE end_patch MOV [bp-9H], dl end_patch: JMP patch_return code ENDS END ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; ; ; NAME: zbra00.a86 ; DATE: 11 April 1984 ; ; PRODUCT(S): iRMX 86 R6.0, UDI V3.0 ; ; REPAIR LIBRARY: UDI.LIB ; REPAIR MODULE : UDURES ; ; DESCRIPTION: This zap solves the problem of the FORTRAN ; compiler not being able to run on iRMX 86 R6.0. This patch ; changes UDI so that a request to DQ$RESERVE$IO$MEMORY of ; more than twelve buffers will not return an E$RESERVE$PARAM F Ft<vtvPP=7PFPЉFV~u6}~'u)6r~u;6f~uM6Z~!ua6O~Euu6D~Au68~Fu6-~@u6"~u6~Bu7 ~u 7FNF t&^&Fv+ȊF;sRPPvPFPƆvF FuvPPvPFPvPP^SFPF t=&?t5vtvPP@7PFPvPP^SFPvt0vPPC7PFPoRPPvPFP ~uFFFsvRPFP[] 3outstanding cde zaps SEGMENT WORD COMMON 'CODE' ASSUME cs:cgroup DB 'ZBRA00K30' ;Zap ID string DB 03DH ;Checksum zaps ENDS code SEGMENT WORD COMMON 'CODE' ASSUME cs:cgroup ORG 1CH JMP patch_code NOP ORG 2BH patch_return: ORG 15EH patch_code: CMP cx, dx  SRPPv^SF&]UQQvPFP^SFP^S=uFF&^&vFPc]Uv^SF&N^&?u PFP*F]error in PUT outputUQF t/v ^SPRPFR tPRP&<PP]UQF Ft"^&Fu+JVuF@]UQF Ft"^&Fu+JVu]UF;FrF]UQQvPFP^S5F&^& tvFP ]J ( " t2"ut&] BXQR3PPP͸ZYU͸t^&]U͸t^&]U͸t^&] Qrj u;v 33ˋ33U3 ҃+@sH]؋&6t&  t26t&  t26t& n F $ r 4J`vT t26t&  t2v6t&  t2Z6t&  t2>6t&  t2"6t& $rPJ(r t26|&  t26|&  t26|&  t2PX6|&  t2j6|& pjd^Uv ͸t1~& ~Ãthe ZAP. An example for ; Series III, Series IV and iRMX86 is included. ; ; ; APPLICATION: submit ZBRA00.CSD( %0, %1, %2, %3, %4, %5, %6 ) ; ; %0 = Pathname for the directory that contains your ; system commands (i.e., submit, copy, rename, delete). ; (ex: Series III = ":f0:", Series IV = ":system:", and ; iRMX 86 = "/system/") ; ; %1 = Pathname for the directory that contains your language ; utilities (i.e., ASM86, L Series III = ":f1:", Series IV = ":rmx86:ios/", ; and iRMX 86 = "/rmx86/ios/") ; ; %4 = 'RUN'. This parameter is only needed for ISIS Series ; III development systems. ; ; %5 = 'EXIT'. This parameter is only needed for ISIS Series ; III development systems. ; ; %6 = ';'. This parameter is only needed for Series III and ; Series IV development systems. ; ; ; ASSUMPTIONS: None. ; ; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; ; ; NAME: ZBRA00.CSD ; DATE: 20 APR 84 ; ; ; NOTE: This submit file applies the above ZAP to the iRMX 86 ; Operating System object code. This submit file can be ; executed on an Intellec Series III, a Series IV or an ; iRMX 86 development system. ; ; The following parameter list (in order) must be used for ; the correct application of INK86, LIB86). ; (ex: Series III = ":f0:", Series IV = ":lang:", and ; iRMX 86 = "/LANG/") ; ; %2 = Pathname for the directory that contains the contents ; of the iRMX 86 Update Package. ; (ex; Series III = ":f4:", Series IV = ":rmx86:update/", ; and iRMX 86 = "/rmx86/update/") ; ; %3 = Pathname for the directory that contains the iRMX 86 ; object code (e.g., nuc3.lib, xcmdrv.lib, eios.lib). ; (ex:;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; %4 %1ASM86 %2zbra00.a86 %2PTCH86 %2udures.mod CODE COMMON %1LINK86 %2udures.mod, %2zbra00.obj to %2udures.tmp %2PTCH86 %2udures.tmp CODE PUBLIC %2PTCH86 %2udures.mod CODE PUBLIC %1LIB86 delete %3udi.lib(udures) add %2udures.tmp to %3udi.lib exit %5 ; This line is only applicable to iRMX 86 R6.0 development system users. %6permit %3udi.lib r u=world delete %2udures.tmp,%2udures.mp1,%2zbra00.obj,%2zbra00.lst the ZAP. An example for ; Series III, Series IV and iRMX86 is included. ; ; ; APPLICATION: submit ZBRA16.CSD( %0, %1, %2, %3, %4, %5, %6 ) ; ; %0 = Pathname for the directory that contains your ; system commands (i.e., submit, copy, rename, delete). ; (ex: Series III = ":f0:", Series IV = ":system:", and ; iRMX 86 = "/system/") ; ; %1 = Pathname for the directory that contains your language ; utilities (i.e., ASM86, L Series III = ":f1:", Series IV = ":rmx86:ios/", ; and iRMX 86 = "/rmx86/ios/") ; ; %4 = 'RUN'. This parameter is only needed for ISIS Series ; III development systems. ; ; %5 = 'EXIT'. This parameter is only needed for ISIS Series ; III development systems. ; ; %6 = ';'. This parameter is only needed for Series III and ; Series IV development systems. ; ; ; ASSUMPTIONS: None. ; ; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; ; ; NAME: ZBRA16.CSD ; DATE: 20 APR 84 ; ; ; NOTE: This submit file applies the above ZAP to the iRMX 86 ; Operating System object code. This submit file can be ; executed on an Intellec Series III, a Series IV or an ; iRMX 86 development system. ; ; The following parameter list (in order) must be used for ; the correct application of INK86, LIB86). ; (ex: Series III = ":f0:", Series IV = ":lang:", and ; iRMX 86 = "/LANG/") ; ; %2 = Pathname for the directory that contains the contents ; of the iRMX 86 Update Package. ; (ex; Series III = ":f4:", Series IV = ":rmx86:update/", ; and iRMX 86 = "/rmx86/update/") ; ; %3 = Pathname for the directory that contains the iRMX 86 ; object code (e.g., nuc3.lib, xcmdrv.lib, eios.lib). ; (ex:;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; %0delete %3format %0copy %2zbra16.r86 to %3format ; This line is only applicable to iRMX 86 R6.0 development system users. %6permit %3format r u=world  you are ; exeriencing the above problem. This problem will be fixed in ; the next version ASM86. ; ; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; NAME uxclsv_repair_zbra01 cgroup GROUP code zaps SEGMENT WORD COMMON 'CODE' ASSUME cs:cgroup DB 'ZBRA01K30' ;Zap ID string DB 03EH ;Checksum zaps ENDS code SEGMENT WORD COMMON 'CODE'  MOV es, [bp - 08H] PUSH es CALL u_reserve_io_memory LES bx, DWORD PTR [bp + 04H] CMP es:WORD PTR [bx], 0 JZ no_errors JMP error no_errors: MOV es, [bp - 08H] JMP patch_return code ENDS END ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; ; ; NAME: zbra01.A86 ; DATE: 12 APRIL 1984 ; ; PRODUCT(S): iRMX 86 R6.0, UDI V2.0 ; ; REPAIR LIBRARY: UDI.LIB ; REPAIR MODULE : UXCLSV ; ; DESCRIPTION: This ZAP solves the problem of the ASM86 assembler ; not being able to assemble LARGE files if running on iRMX 86 R6.0 ; The assembler would abort with an E$MEM exception. ; ; SPECIAL NOTES: This ZAP should only be applied if ASSUME cs:cgroup EXTRN u_reserve_io_memory : near ORG 195H JMP patch_code ORG 198H patch_return: ORG 1AAH error: ORG 2AFH patch_code: MOV ax, 6H PUSH ax MOV ax, 0CH PUSH ax LES bx, DWORD PTR [bp +04H] PUSH es PUSH bx \\d CBACKUPCHAR%CGETCHAR CREATEJIDSCSETPARSEBUFFERYDETERMINEDESCRIPTOR LOOKUPJIDS2׀HGTCHRPLM86 V2.307/12/84 00:35:0۠6UQ(P^SF^&?u (F]~Dl2UQPQP^SF^&?t@^&?u4SF^&?u#WPPS^&?uF v] BI]BUQ^SF^&?tF&&  t F]ϠQU^&^&O&;OrF#^&FFv&|^&F^&GF] HGTCHR2STACKMEMORYCODEDATADGROUPCGROUPZAPS??SEGPHtH T$Dh X b {\urg tsَ{|mwos{|eu kz{ Bu h Ύ ts  tsʎ  ts ] ts t sَ  9 tsڎ tsĎ   C t sԌNLOCALDELETESEGMENTRJIDSRQCREATESEGMENTRQCATALOGOBJECTRQLOOKUPOBJECTj8%U^&G&;Gw ^&t&O^&^&] BYUQF&F^ &OF& Z&^ &&&] HGTCHR_REPLACEMENT_ZBRA18ASM86.86 V2.0wZBRA18J30EŠtthe ZAP. An example for ; Series III, Series IV and iRMX86 is included. ; ; ; APPLICATION: submit ZBRA01.CSD( %0, %1, %2, %3, %4, %5, %6 ) ; ; %0 = Pathname for the directory that contains your ; system commands (i.e., submit, copy, rename, delete). ; (ex: Series III = ":f0:", Series IV = ":system:", and ; iRMX 86 = "/system/") ; ; %1 = Pathname for the directory that contains your language ; utilities (i.e., ASM86, L Series III = ":f1:", Series IV = ":rmx86:ios/", ; and iRMX 86 = "/rmx86/ios/") ; ; %4 = 'RUN'. This parameter is only needed for ISIS Series ; III development systems. ; ; %5 = 'EXIT'. This parameter is only needed for ISIS Series ; III development systems. ; ; %6 = ';'. This parameter is only needed for Series III and ; Series IV development systems. ; ; ; ASSUMPTIONS: None. ; ; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; ; ; NAME: ZBRA01.CSD ; DATE: 20 APR 84 ; ; ; NOTE: This submit file applies the above ZAP to the iRMX 86 ; Operating System object code. This submit file can be ; executed on an Intellec Series III, a Series IV or an ; iRMX 86 development system. ; ; The following parameter list (in order) must be used for ; the correct application of INK86, LIB86). ; (ex: Series III = ":f0:", Series IV = ":lang:", and ; iRMX 86 = "/LANG/") ; ; %2 = Pathname for the directory that contains the contents ; of the iRMX 86 Update Package. ; (ex; Series III = ":f4:", Series IV = ":rmx86:update/", ; and iRMX 86 = "/rmx86/update/") ; ; %3 = Pathname for the directory that contains the iRMX 86 ; object code (e.g., nuc3.lib, xcmdrv.lib, eios.lib). ; (ex:;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; %4 %1ASM86 %2zbra01.a86 %2PTCH86 %2uxclsv.mod CODE COMMON %1LINK86 %2uxclsv.mod, %2zbra01.obj to %2uxclsv.tmp %2PTCH86 %2uxclsv.tmp CODE PUBLIC %2PTCH86 %2uxclsv.mod CODE PUBLIC %1LIB86 delete %3udi.lib(uxclsv) add %2uxclsv.tmp to %3udi.lib exit %5 ; This line is only applicable to iRMX 86 R6.0 development system users. %6permit %3udi.lib r u=world delete %2uxclsv.tmp,%2uxclsv.mp1,%2zbra01.obj,%2zbra01.lst  ZAP. An example for ; Series III, Series IV and iRMX86 is included. ; ; ; APPLICATION: submit zbra18.CSD( %0, %1, %2, %3, %4, %5, %6 ) ; ; %0 = Pathname for the directory that contains your ; system commands (i.e., submit, copy, rename, delete). ; (ex: Series III = ":f0:", Series IV = ":system:", and ; iRMX 86 = "/system/") ; ; %1 = Pathname for the directory that contains your language ; utilities (i.e., ASM86, LINKries III = ":f1:", Series IV = ":rmx86:ios/", ; and iRMX 86 = "/rmx86/ios/") ; ; %4 = 'RUN'. This parameter is only needed for ISIS Series ; III development systems. ; ; %5 = 'EXIT'. This parameter is only needed for ISIS Series ; III development systems. ; ; %6 = ';'. This parameter is only needed for Series III and ; Series IV development systems. ; ; ; ASSUMPTIONS: None. ; ; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; ; ; NAME: zbra18.CSD ; DATE: SEP 84 ; ; ; NOTE: This submit file applies the above ZAP to the iRMX 86 ; Operating System object code. This submit file can be ; executed on an Intellec Series III, a Series IV or an ; iRMX 86 development system. ; ; The following parameter list (in order) must be used for ; the correct application of the86, LIB86). ; (ex: Series III = ":f0:", Series IV = ":lang:", and ; iRMX 86 = "/LANG/") ; ; %2 = Pathname for the directory that contains the contents ; of the iRMX 86 Update Package. ; (ex; Series III = ":f4:", Series IV = ":rmx86:update/", ; and iRMX 86 = "/rmx86/update/") ; ; %3 = Pathname for the directory that contains the iRMX 86 ; object code (e.g., nuc3.lib, xcmdrv.lib, eios.lib). ; (ex: Se ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; %4 %1lib86 delete %3hi.lib(hgtchr) add %2zbra18.rmd to %3hi.lib exit %5 ; This line is only applicable to iRMX 86 R6.0 development system users. %6permit %3hi.lib r u=world d Volume Not Found)Volume Must Be Restored By System Managerprogram_version_number=V3.1program_name=iRMX 86 RESTOREiRMX 86 Restore Utility, V3.1 Copyright 1982, 1984 Intel Corporation QUERYVERIFYNAME(Only 9 Characters Allowed In Volume NameInvalid Input SpecificationInvalid Output SpecificationWhile Creating I/O MailboxesAFTERNo Memory For ID Table  ies\PGP5nLPRPO2>RuPRPO.R tPRPPPEPeP/PRPYNTVPVPRPCF tPuPRPPC>uuP9PRPPjC4PPFPJF tP4PRPP>C>4tP4PPP"C4PP:PFPzJF=t =t=uPP;PPBF tP4PRPPB>uP<PRPPBP)PPPRPRPFPIrF tPPRPPaBuTuBPWPFP5PP8.jpwklhPtuP)WPFP5PP8.PPR0mn' VERSION3P0 N Ԗ?STACKMEMORYCODEDATADGROUPCGROUP??SEGLQ_PLM86_LIB_CODEq 3S3S && @B@B   ee  3S3SO &&pf@@BψPLM86 V2.304/23/84 14:24:2Wr:Copyright 1981, 1982, 1984 Intel CorporationiRMX 86BACKUP30Restore CompleteVerify CompleteSummary For Logical Volume (Skipping Logical Volume (Physical Volume ( , Complete Data File Director Restored Verified)RequesteP6NXPRPsO*R tPRPCPPuEX*&6TPRPM*&>ussP3PuPPRPG>RtPZP[PP EZo8l8`P[6PS6PK6Q8N8\P=66<6:P7P'6><u>:tsP5lsP58_P56@6>Po7P5>@u>>uyP[5bP5lsP577lsP?P577U46RRPPPKU,klmrq\uP3PFPCK~uP6P7PPC~uPP8P P PPFP6~uPPBPPwAF uP]/Invalid Backup Record Found, Restore Terminated, Restore Directory? , Verify Directory? , Restore Data File? , Verify Data File? Read Access RequiredCannot Close ConnectionCannot Delete ConnectionCannot Delete File NOT Verified NOT RestoredRestoredVerified5NAME Option Not Allowed With Old Format Backup Disks.!Not Enough Memory for I/O Buffers&Error During BACKUP, File Not Restored'I/O Buffer Overflow, RESTORE Terminated^&?uLvPPS?^&?u$vS64vG+PFsvPFP@$^&?&uPP4P^S\ Pt;^&7P4P^SRPU^&?)uP P PP6]UF&_.TTTTTT#TM&@vPP PP6F@F&9Gu\\t+JtP&GFPB6lsWvVvFP>>F~u;Fu6vP4P4P PA~)uP P PP5!p&G tPP4P4P>:<lsʉDLFHJN6(FPkGB6D6 ~uXr uP"]U0v-msPuPPP)=F tPuPRPP=P6P PP<]UQQns86PFB6&|u&DB&u7&G0PVFB66P>FB6FN&G< wuP&ub\PPGPFPm1&uPGPG+P|'&wB6B6N6]& unsuPPP4PRPPlrPP4PRP ls PP|P PPfPPFP'kPP4PRP PSis'lr#PP4PRP"P]UQQ4FFuȈF؊5F PSr6466^SPv v vP62^Sb@^&?u 62S,lFFPFPGB~t4F@FPFPGBF;FsݸPwP PP=ƋF- ,+F1N+WP4P4P8PP4P4P/P&wF$ns3&wP4P4PP]ns P&wFAUQG+PrAsr:PP4P4PP0lrPPP4P4PM ls PPP PPPPFP(kPP4P4P PSrlr*4P&G P&w&wFP8 u~tE68@ls68FP&<~#uFF tPP4P4PP068FP;F tPP4P4PP68FP;8F t4PP_. Q c z F@F&9Gu\\t+JtP&wF&wF]&wFnsnsPUQQPe%F&_.   &t&w^F]ðPRPRP"'&w=FP$;FsҠns P&&wFUmr&G<t<td&G!+F&GF&GF&GrQB6 tFt+Ju< t &x tm~u/v N+Q\F!]U64664PP62FP7:~u62FP5Fsso~uiPvRQPP62FP:~u62FP6FPvRPPP62FP9~u62FP5F~u%r vShPP@PP0~ u64664P62FPV9~u62FP4F~uv62FPb9~u62FP5F~uF& s F&>&tF'sr~uMFLFFFFFF&;Jw^&xu&FF֊F"VtQRPRPbP4PFJP!PP-PPPvRQ^&&u&Vu&Ou&Lu&Bt>qt F u+JVuF F&&nt+J;u qn &qnr;&;,u&s#ts&:ttPQQ&:quBFt+Ju&&;u;u~ ~ u+JVuF FFuPFP&&&P0q<vuQQP66PnsP6P$4846q:<>@oB PRPRPPgms"nsPAP PP:-& u &w F&&t&GF&G!+FnrU&GrQ B6 t F u+JVuF FvN+Q; F&G<t<t<u&w&tnsF&G!+F&GrQ B6 t F u+JVuF Fv F& u &wns5GP2PRPRP6PG-F~u &FF&%&~+u PFF t1)t,Ut'PuPEPPY#vuPRPPC#F t!UtmsPuPPP#F&FFP,~uF~t ~tF~vF)FHHJ+ȉNos?BvF&| u'&W+ʉN)HЋBFYoFUt)u nroFLN)FN]UQF;LvFFNF)L]U^GFFF*&;FrHF^F&9r3vNH*&T^&;PuFH&t FuFu]U v v At Volume #1.Required0RESTORE, BACKUP Device Attachments Do Not Match.Not A Backup Volume.Error Reading Backup Volume), #, Backup Volume (Cannot Set AccessCannot Set Extension DataExtension Data Not Restored, Bytes Required, , 01^U^S ePP^SaPPF RPPePFFP Pv vFP%FPPFFP Pv vFPb&FP P^Sw}]UFFwM60PQ6.FP0~u6.FP,F~u~tvqFuwP62FP[8~u62FPo4F~uPvRQPP62FP"8~u62FP64FvFP&9~u6 t PPFP7F6vP4PRP"PF]U$P FBvF&HP F^&HFQi FBvF&GFN&INF~tNFF:FsP" FBvF~uVv4F~ ^&GFFP FB~NP4PFPVlrRFtdF:Ft+P FBvF&DPm F4F]U&&- FF tq,;vNFF60Sv6.FP0.~u6.FP2*FF t!PuPEPP/%vuPRyF)F60PP6.FP-~u6.PFPFP.&~u &&F6&FP.F t*uvuP0PP$]Uos"uP msP(qqPH+NB6NB^YH+NJHD+ȎBFFD,+ȋH;s3~t*60BVP62FP,F t'PuPEPP#vuPRPP#62PFPFPPG+PPB&_.t'tttNmtm4PPGPFPx ss|&G FFFFF4 t PFP3F tPP4PRP"P=FPFPz34F tPP4PRP"P&u&uC0&wP4PGPP&u~y]&G t'PP4PGPPPRPRP4 /&wP4PGPPgns P&wF oDirectory RestoredDirectory VerifiedMountedRESTORE Of Old Format Volumes Must Start!RP*&6P62FPO*~u62FPc&Fssk~uePvRQPP62FP*~u62FP%&FPvRQWP62FP)~u62FP%FF ug^GFFF^F&9rhv vRQH^&pFH&062FPv)~u62FP%FF tPP4P4PvPFu]UTv^S62FPA)~u62FP1%F~u~udFPPPPFPIFPPP^&PPFP1FPPPPPFP PP4P4PFvP4P4PP]UlsFFu~t'F t&?t~:t+P^ S^S^SPRP^S]U^&rPP^ SPI PP^SP tP^ SRPPP PPPS tP^ SRPPV @ls PP PPPPFPPP4PRP PPRPRP7 lr6 t PPFPG'F6]U6466^S62^S'^&?u 62S"F^&?uYv62S$'^&?u 62S"F^&?uF&>&u^&'vFP'vPFP&^&?!u&]Cannot Create Device MailboxInvalid Stack TypeSP Is UndN]U~vP*PRPPv^.&3,31363]U~vP*PRPP3^.i3o3t3y3vo tN  9r?H&T t Hº u]UQ~ vP*PRPP^ .44%404 ;vPRPc+PP4F t=DPP^SFP F tP^S+PPF t#|v FY+P^SPr:^SPvFPn$~uvFP~uwP6RPvFP#~uvFP~uC6PPvFP#~uvFPF~uvFP*%]v^ S+PPv^ SRPP6PFPi#6PPFP#GUPFPj$FF tPRP*PPr6vFP1#~uvFP:F6vFP"~uvFPF6PvFP #~uvFPFF t&P^S+PPv^SRPPvFP#]U^ &?t S"&D] U~vP*PRPP~^.7$7/7:7 F;vPRPc+PP*~uPRP*PP FHF&D]UQ~vP*PRPP^.7777 >uPRP*PPH& NA& F]U FFPFPk,PPFPF~uPFPFF tPRPFPvFPQPs^Sv`T]0123456789ABCDEF U6 S6]UQF&P&]UFFPv Ft7:Fr2FF*F:Fr#^Sv z@P^Se^&?uFu^Sv FP^SB];Zx0Nnmmm JANUARYFEBRUARYMARCHAPRILMAYJUNEJULYAUGUST SEPTEMBEROCTOBERNOVEMBERDECEMBER U^&^&8v&x u^&]9rAUFF^S^S^&^&H0N&8w@ vB"s;^&FV PN׉FV;u;v^S^SGF]!^TrdvBU F^&^&8vO&x uFV;utu@Bt uuƇ,FVN~~vFV FVf]3TYTȵTTrI;UFRPFt:r*PaPz]UvvFt:r*P/PH]UF$.8F$.8]Uvv]Uv]U츿8PP]UF FF]UFu6 FPP&,;wF6&< u >u]UQFF:Fr PFu]UF t؍OQ^&P]Dr[:UQQFV FV t vvFV ǃ0] T8Trl:UQQFF;FV9Vu9Fsuv FVҋFV uFVN~0FPNAP6F t)^&^&pnNBF^&룸]UF^&/P^ S> sE^ SFPF^ v&x/uF^ SFPF^ v&x/tUF ^ SFPF^ SFP FF;rq wl9Nrg^ SFPNF^ &;FwJ~Ns)FF1Vn~u* u&~v/~dsFlρ~r~3v^.A;Fr^&^&?tݸFFF^SFPF^&N;vT&x:u^F^SFPF^&N;v)&x:u3F^SFPbF^&;Fw~s <9Fs]UQF Ft/~r)^&F F t!PvF^&;r ^&iF tb^&F9Fw(=v ^&^&^&N+IN^&xv NFY^F&]UF Ft~ s ^&2^&F t!^Sv ^GP^&P^S]UF Ft~ s ^&1^&F t!^Sv ^GP^&P^S]UF Ft~s ^&]^&F tL&:F vBNF ^ &;s*ЈV^SvF ^ @PFP^S3]UQ^&P^&P^w^^"^F^Sv ^GPP^S^Sv AP^S^Sv vP^Sp]NT(rFUQFV Q~v ^Sv ǹ֋P:P^S*FV ~^Sv ǹ<1P:P^S^Sv F<1RP^S]~ T2TOT]r ^Gunrecognized controlinvalid file typeinvalid path nameparameters requiredfile does not existlogical name does not existis not a device connectiondevice does not belong to youinvalid logical name(program version incompatible with s6t&  t2\6t& hF$  l .DT t2 6t&  t26t&  t26t&  t26t& f|B b $ rlD> t2.6|&  t26|&  t26|&  t26|&  t26|&  t26|&  t26|& vt0vPPHPFPRPPvPFP~uFFFsvRPFP] 3outstanding connections to device have been deleteddevice is in usecan't detach deviceUf^ S^SxF^& u\F&>tAEP^ShF^& tPRPRPP,F tF&$t;t F^&^SvFP^S^& u]F&>u%FPPRPP^ S^S^& tPFP"FPFP^S^& tP^ SR4~v:FsP^ SJQP](^&P^ SJPP"^&Fu+JVu]UF;FrF]U^&^&:u}^&ȴ&x:us&?wmF tPv^S^S^&?uQF FtI^&ȴ;F ww^&Sv ^GP^&,P^S^&? v ^&@uF tPv ^S^Si^&?uQF FtI^&;Fv ^&0^&&G:Sv^S^S^&&@:&]Uv^SoF^&?uFPFPSG^&?uF]*$:J ( " t26t&  t2xystemnot a file connectioninvalid wildcard specification, ,  UƆvF F u-vPP^ SFPF Ft<vtvPPHPFPЉFV~u^G}~'usGr~uGf~uGZ~!uGO~EuGD~AuG8~FuG-~@uH"~u)H~BuRH ~u hHFNF t&^&Fv+ȊF;sRPPvPFPOƆvF FuvPPvPFP0vPP^SFPcF t=&?t5vtvPPHPFP4vPP^SFP t2PiX6|& pjd^Uv ͸t1~& ~Ãut&] BXQR3PPP͸ZYU͸t^&]U͸t^&]U͸t^&] rj u;v 33ˋ33U3 ҃+@sH]؋&AP^S F^&?ubF&6"P^S<^&?uvPFPSF^& t)P^ SJPP^&7^ SRPPv^SF&]UQQvPFP^SFP^Sq=uFF&^&vFPI]UQQvPFP^S3F&^& tvFP]Uv^SF&N^&?u PFPF]error in PUT outputUQF t/v ^SP$PF$ tPRPMPP]UQF Ft"^&Fu+JVuF@]UQF Ft#the ZAP. An example for ; Series III, Series IV and iRMX86 is included. ; ; ; APPLICATION: submit ZBRA02.CSD( %0, %1, %2, %3, %4, %5, %6 ) ; ; %0 = Pathname for the directory that contains your ; system commands (i.e., submit, copy, rename, delete). ; (ex: Series III = ":f0:", Series IV = ":system:", and ; iRMX 86 = "/system/") ; ; %1 = Pathname for the directory that contains your language ; utilities (i.e., ASM86, L Series III = ":f1:", Series IV = ":rmx86:ios/", ; and iRMX 86 = "/rmx86/ios/") ; ; %4 = 'RUN'. This parameter is only needed for ISIS Series ; III development systems. ; ; %5 = 'EXIT'. This parameter is only needed for ISIS Series ; III development systems. ; ; %6 = ';'. This parameter is only needed for Series III and ; Series IV development systems. ; ; ; ASSUMPTIONS: None. ; ; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; ; ; NAME: ZBRA02.CSD ; DATE: 20 APR 84 ; ; ; NOTE: This submit file applies the above ZAP to the iRMX 86 ; Operating System object code. This submit file can be ; executed on an Intellec Series III, a Series IV or an ; iRMX 86 development system. ; ; The following parameter list (in order) must be used for ; the correct application of INK86, LIB86). ; (ex: Series III = ":f0:", Series IV = ":lang:", and ; iRMX 86 = "/LANG/") ; ; %2 = Pathname for the directory that contains the contents ; of the iRMX 86 Update Package. ; (ex; Series III = ":f4:", Series IV = ":rmx86:update/", ; and iRMX 86 = "/rmx86/update/") ; ; %3 = Pathname for the directory that contains the iRMX 86 ; object code (e.g., nuc3.lib, xcmdrv.lib, eios.lib). ; (ex:#;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; %0delete %3restore %0copy %2zbra02.r86 to %3restore ; This line is only applicable to iRMX 86 R6.0 development system users. %6permit %3restore r u=world &GFF^G0FFF^&Gȴ;Fs^&u&t ^&G+^&G&G &GF&G F&G F&G F^vFFF^&G ȊN:rfF^& & FF& Z& &ON&ON؋F&&FP^&LJFFFFuFFFt^&G]̜ Dm U]^UQFu FFHN;r9^& Fu)F%@uFFHN;r^&Fu]1UF&FF^&ć FFF^&ć FF^&r!&u & &Ƈ ^&^&GF&G&GF&GFnF^&GF&G&GF&GF&GF&GFF+FF^&GF&GFFFFNNV;sQ tM^8vFY^vPv^&wNF+ȉN^FFFFF t0^v8vFY^vPv^&wP^&& ^&G&&^&@u ^&^&'^& u ^&^&'^&s ^&^&'FF^&GuF ^&tF^&G%=uN^&G%=uN^&u N&Ƈ^F&8Gt&GF^&GFX5442STACKMEMORYCODEDATADGROUPCGROUPZAPS??SEGPHH T>ƘDh X RQSLEEPRQDELETESEMAPHORE'\\i I544ANSWER I544CHECK I544FINISH I544HANGUPI544INIT I544SETUP1I544UNITSAVAILABLE+X544PLM86 V2.309/14/84 13:41:4ҠU^&_^F&GF&GFFF^&Gȴ;Fr^&G &&GFFFuF~wQ PFP^&GFFF^&Gȴ;Fr#^&u&u FFFuFu^^&tPFP^&t:&^&G&G^&?u^&& ^&G&9^&t0^&?u^&% && ^&G& ^&u &u`^&tzF&NF^&tF^&uFN;r+^8 u+JVuF뾋FF@F^&^&F&&ďNF^&tgF^&tBFN;s8+^8 uݜxܠ!+JVuFċFF@F^&볋NF;s +^&N^v^&Z&F u(FF$&GF^&G;FtFF^&GF&GFFs^&& ^&G&]LU^&_^F&GF&GF^&GF&GFF9FvFF]U^&_^F&GF&GFFFF^&Gȴ;Fr^&u!^&G FFFFuѰ^&G=F^&GF^O0NF F^&ć FFF^&G^&GȈF&G<s=.^&^&&:u &^&GF&G F&G F&G Fvv^&F^&G&G^&?u^&& ^&G.=tPPQPPPP]JD E $ (5 < ANT Y\ch݀SDBINT_REPLACEMENT_ZBRA06ASM86.86 V2.0wZBRA06I30AʊtSDBINT2STACKMEMORYCODEDATADGROUPCGROUPZAPS??SEGPHTHTDh X  SETCOMMANDDQCFG SWITCH_STACK RQDELETEJOBRQSETINTERRUPT RQENDINITTASK FRONT_PANELLEVEL MONITOR_957MONITOR_SDM286RQSDBINITERROR\\ SDB_RMX_INITLSIGN_ONSDBINTPLM86 V2.310/05/84 11:33:1ޠPiRMX 86 System Debugger, V3.0 Copyright 1982, 1983, 1984 Intel Corporation1pLUPPu#;u&^&G FC^&G7^&G -^&G #^&GF&GFF^&G^&G]+ňLjɈˈ͈ψшӈxUQQ^SZ]UQQ^SG]X544_REPLACEMENT_ZBRA21ۈASM86.86 V2.0wZBRA21E209ڊt$the ZAP. An example for ; Series III, Series IV and iRMX86 is included. ; ; ; APPLICATION: submit zbra21.CSD( %0, %1, %2, %3, %4, %5, %6 ) ; ; %0 = Pathname for the directory that contains your ; system commands (i.e., submit, copy, rename, delete). ; (ex: Series III = ":f0:", Series IV = ":system:", and ; iRMX 86 = "/system/") ; ; %1 = Pathname for the directory that contains your language ; utilities (i.e., ASM86, L Series III = ":f1:", Series IV = ":rmx86:ios/", ; and iRMX 86 = "/rmx86/ios/") ; ; %4 = 'RUN'. This parameter is only needed for ISIS Series ; III development systems. ; ; %5 = 'EXIT'. This parameter is only needed for ISIS Series ; III development systems. ; ; %6 = ';'. This parameter is only needed for Series III and ; Series IV development systems. ; ; ; ASSUMPTIONS: None. ; ; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; ; ; NAME: zbra21.CSD ; DATE: 10 OCT 84 ; ; ; NOTE: This submit file applies the above ZAP to the iRMX 86 ; Operating System object code. This submit file can be ; executed on an Intellec Series III, a Series IV or an ; iRMX 86 development system. ; ; The following parameter list (in order) must be used for ; the correct application of INK86, LIB86). ; (ex: Series III = ":f0:", Series IV = ":lang:", and ; iRMX 86 = "/LANG/") ; ; %2 = Pathname for the directory that contains the contents ; of the iRMX 86 Update Package. ; (ex; Series III = ":f4:", Series IV = ":rmx86:update/", ; and iRMX 86 = "/rmx86/update/") ; ; %3 = Pathname for the directory that contains the iRMX 86 ; object code (e.g., nuc3.lib, xcmdrv.lib, eios.lib). ; (ex:%;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; %4 %1lib86 delete %3xcmdrv.lib(x544) add %2zbra21.rmd to %3xcmdrv.lib exit %5 ; This line is only applicable to iRMX 86 R6.0 development system users. %6permit %3xcmdrv.lib r u=world the ZAP. An example for ; Series III, Series IV and iRMX86 is included. ; ; ; APPLICATION: submit zbra06.csd( %0, %1, %2, %3, %4, %5, %6 ) ; ; %0 = Pathname for the directory that contains your ; system commands (i.e., submit, copy, rename, delete). ; (ex: Series III = ":f0:", Series IV = ":system:", and ; iRMX 86 = "/system/") ; ; %1 = Pathname for the directory that contains your language ; utilities (i.e., ASM86, L Series III = ":f1:", Series IV = ":rmx86:ios/", ; and iRMX 86 = "/rmx86/ios/") ; ; %4 = 'RUN'. This parameter is only needed for ISIS Series ; III development systems. ; ; %5 = 'EXIT'. This parameter is only needed for ISIS Series ; III development systems. ; ; %6 = ';'. This parameter is only needed for Series III and ; Series IV development systems. ; ; ; ASSUMPTIONS: None. ; ; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; ; ; NAME: ZBRA06.CSD ; DATE: 20 APR 84 ; ; ; NOTE: This submit file applies the above ZAP to the iRMX 86 ; Operating System object code. This submit file can be ; executed on an Intellec Series III, a Series IV or an ; iRMX 86 development system. ; ; The following parameter list (in order) must be used for ; the correct application of INK86, LIB86). ; (ex: Series III = ":f0:", Series IV = ":lang:", and ; iRMX 86 = "/LANG/") ; ; %2 = Pathname for the directory that contains the contents ; of the iRMX 86 Update Package. ; (ex; Series III = ":f4:", Series IV = ":rmx86:update/", ; and iRMX 86 = "/rmx86/update/") ; ; %3 = Pathname for the directory that contains the iRMX 86 ; object code (e.g., nuc3.lib, xcmdrv.lib, eios.lib). ; (ex:%;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; %4 %1lib86 delete %3sdb.lib(sdbint) add %2zbra06.rmd to %3sdb.lib exit %5 ; This line is only applicable to iRMX 86 R6.0 development system users. %6permit %3sdb.lib r u=world S^&t4u8^&7PP^S^&7PFPRP^SFF^&?u=F%N FtNF^&7PFPRP^SFs^&7FP] XDNrUDUSPL_REPLACEMENT_ZBRA22ASM86.86 V2.0wZBRA22K30AʊtUDUSPL2STACKMEMORYCODEDATADGROUPCGROUPZAPS??SEGPHH T.֘Dh X b {\ur{|eupz{ Gum6 ts Ў{|mu i   ts ͎ڎ ts͎  D tsʌ RQSSPECIAL RQSOPENRQSCLOSE\\ U_SPECIALUDUSPLPLM86 V2.309/18/84 10:25:3РU^&F t<v^&#^&?tFv&4PFPRP^&s in BS1.A86. $LIST %IF (%first_device) THEN ( code ends ; ; ; Declare the cico routines if needed ; %IF (%is_console OR %is_loadfile) THEN ( extrn co: far ; will need co in either case ) FI %IF (%is_console) THEN ( extrn ci: far ; need ci here also )FI %IF(%is_cico) THEN ( extrn cinit: far ; must initialize the USART )FI ; extrn bserror: far ; bootstrap error routine DEVICE_NOT_READY equ 11h ; stage one error extrn %device_init: faextrn get_file_name: near ; startup: %IF (%is_cico) THEN ( call cinit )FI call get_file_name ; call console procedure got_name: ; mov debug, FALSE ; default to no debug cmp es:byte ptr [bx], 'D' ; Debug switch? jz check_debug ; might be, check cmp es:byte ptr [bx], 'd' ; check lower case too jnz got_line ; no debug switch ; check_debug: cmp es:byte ptr [bx+1], BLANK ; next char blank? jnz check_end ; no, check for mov debug, TRUE ; yes, there is $NOLIST ; ; INTEL CORPORATION PROPRIETARY INFORMATION ; ; This software is supplied under the terms of a ; license agreement or nondisclosure agreement with ; Intel Corporation and may not be copied or disclosed ; except in accordance with the terms of that agreement. ; ; This include file was supplied as ZBRA09.INC with the ; iRMX 86 UPDATE 2, 12/28/84. It fixes a problem where using ; only AUTO without CONSOLE or MANUAL would produce assembly ; errorr ; extrn %device_read: far ; data segment public polltimes ; Declare the number of times to poll devices polltimes dw ? data ends code segment ; %IF (%is_console) THEN ( code ends ; data segment ; public line_buffer ; Declare line buffer public debug ; line_buffer db 80 DUP (?) ; debug db ? data ends ; ; code segment ; TRUE equ 0FFh ; FALSE equ 000h ; BLANK equ 020H ; CR equ 00DH ; Carriage Return LF equ 00AH ; Line Feed &a debug switch ; parse_blanks: inc bx ; cmp es:byte ptr [bx+1], BLANK ; jz parse_blanks ; get past blanks ; check_end: cmp es:byte ptr [bx+1], CR ; if next char is a CR, jz debug_default ; then debug the default file cmp es:byte ptr [bx+1], LF ; ditto for LF jz debug_default ; ; cmp debug, TRUE ; debug switch? jnz got_line ; no, boot the file inc bx ; yes, point to start of name jmp got_line ; and debug the file ; debug_default: mov debug,les bx, cs: dev_name_ptr ; get pointer to device name push es ; push it push bx ; les bx, cs: dev_read ; get pointer to device$read mov cx, %unit ; get unit ) FI push es ; push pointer to device$read push bx ; push cx ; push unit push ax ; push dev$gran mov bp, sp ; get pointer into stack push cx ; push unit xor ax, ax ; push zero for dev$loc push ax ; push ax ; mov dx, boot ; push pointer to second stage push dx ; push ax ; %x, 14156 ; push the first check word push ax ; mov ax, 26778 ; push the second check word push ax ; mov ax, seg bserror ; push the pointer to the error routine push ax ; mov ax, offset bserror ; push ax ; push es ; push file name pointer push bx ; ) ELSE ( ; (no console) startup: ; got_name: ; mov ax, cs:maxtimes ; set polltimes properly mov polltimes, ax ; ; no_debug: mov ax,0 ; push ax ; push ax ; mov ; no debug message mov ax, cs ; mov ds, ax ; print debug message lea bx, debug_msg ; call print ; ) FI ; no_print: mov ax, cs ; mov ds, ax ; print loading message lea bx, crlflf ; call print ; pop ds ; get the stack back to normal ) FI call dword ptr [bp+4] ; call device$read call second_stage ; call second stage %IF (%is_loadfile) THEN ( ; ; This routine prints the string pointed to by BX. ; print proc near mov al, byte ptr [bx] ; get a by it will call auto if needed ) ELSE ( %IF (%is_auto) THEN ( push ax ; reserve dev name space push ax ; extrn auto_device_select: near; call auto_device_select ; call auto procedure ) FI ) FI %IF (NOT %device_select) THEN ( mov ax, %unit ; push unit push ax ; call %device_init ; call device$init procedure or ax, ax ; make sure device is there jnz boot_ok ; mov cx, DEVICE_NOT_READY ; call the error routine push cx ; call bserror boot_ok:  TRUE ; lea bx, default_file ; load up default file name mov ax, cs ; mov es, ax ; ; got_line: mov ax, cs:maxtimes ; set polltimes properly mov polltimes, ax ; ; cmp debug, FALSE ; debug = FALSE? jz no_debug ; debug switch off mov ax, 37695 ; first debug check word push ax ; mov ax, 49273 ; second debug word push ax ; jmp push_check ; ; no_debug: mov ax,0 ; check words are zero push ax ; push ax ; ; push_check: mov aIF (%is_loadfile) THEN ( push ds ; save ds for awhile mov ax, cs mov ds, ax ; print loading message lea bx, load call print mov ds, word ptr [bp+10] ; get base to device name mov bx, word ptr [bp+8] ; get offset to device name call cprint mov ds, word ptr [bp+14] ; get base to file name mov bx, word ptr [bp+12] ; get the file name pointer call print ; print the file name %IF (%is_console) THEN ( pop ds ; cmp debug, TRUE ; push ds ; jnz no_print ax, 14156 ; push the first check word push ax ; mov ax, 26778 ; push the second check word push ax ; mov ax, seg bserror ; push the pointer to the error routine push ax ; mov ax, offset bserror ; push ax ; lea ax, default_file ; push default file name pointer push cs ; push ax ; ) FI %IF (%is_manual) THEN ( push ax ; reserve dev name space push ax ; extrn manual_device_select: near call manual_device_select ; call manual procedure ;'te from the message cmp al, ' ' ; if a null then done jae continue ret Continue: and al, 7fh ; remove high bit push ax ; put the character where co wants it call co ; print it inc bx ; next character jmp print print endp ; ; This routine prints the counted string pointed to by bx ; cprint proc near mov cl, byte ptr [bx] ; get the name length in cl inc bx ; first true character mov ch, 0 or cx, cx ; check for null name jnz cloop ret h,8ah,8ah,0 ; fool the print routine ) FI %IF (%device_select) THEN ( device_table label byte ; table of devices public device_table ; ) ELSE ( dev_name_ptr dd dev_name ; pointer to device name dev_name db %LEN(%name)+2 ; fill in device name db ':%name:' ; dev_read dd %device_read ; pointer to device$read ) FI %SET(first_device, 0) ;(end of first device macro) ) ELSE ( ;(not first device macro) code ends ; %IF (%NES(%old_dev_init,%device_init)ead procedure ) FI  cloop: mov al, byte ptr [bx] ; load character from device name inc bx push ax ; al has the character in it call co ; print it loop cloop ret cprint endp ) FI ; stackseg dw stack ; stack segment dataseg dw data ; data segment maxtimes dw %times ; max times to poll - used to reset poll times %IF(%is_loadfile) THEN ( load db 8dh,8ah,8ah,'Loading ',0 ; the high bits are set on the cr,lfs debug_msg db ' ',0 ; printed if debug switch on crlflf db 8d) THEN ( extrn %device_init:far ; ) FI %IF (%NES(%old_dev_read,%device_read)) THEN ( extrn %device_read:far ; ) FI code segment ; %IF (NOT %device_select) THEN ( %error ; MORE THAN ONE DEVICE MACRO ILLEGAL ) FI ) FI %DEFINE(old_dev_init)(%device_init) %DEFINE(old_dev_read)(%device_read) %IF (%device_select) THEN ( db %LEN(%name)+2 ; Fill in name db ':%name:' ; dw %unit ; unit dd %device_init ; device$init procedure dd %device_read ; device$r'