TRS-80 Zaps - DOS - NEWDOS/80 v2.0 (Official, Model III)

CAREFULLY STUDY chapter 11 of NEWDOS/80 documentation for instructions on how to apply zaps.

Some modules have multiple versions with the zaps different in each version. Use the verify to determine which version you have and apply the appropriate zap(s). If you have a version different from any listed (i.e., the verify(s) do not match, contact the program's distributor or Apparat). Apparat is trying to get the program creator/maintainer/distributor to create and distribute the necessary zaps to run with NEWDOS/80, Version 2, but where this does not occur and for widely used programs, Apparat will generate any necessary zaps. If Apparat decides to generate the zaps and does not have your particular version, you will be asked to send the version you have on a diskette to Apparat (as a gift to Apparat, see chapter 11) so that Apparat may determine the appropriate zaps; Apparat will not seek out your version from another source, and will not create a zap from a paper listing.

The zaps for NEWDOS/80 Version 2.0 on the Model I are on the Model I official zap page. Where a zap exists for both machines, a link under the zap leads to its counterpart.

This page is not an exact reproduction of the zaps as Apparat printed them. When the printed zaps were checked against the code they patch and against actual NEWDOS/80 disk images, errors were found in the official zap sheets: wrong bytes, bytes that did not print, and dates out of sequence. This page gives the corrected zaps. Where a printed byte was wrong, a note under that zap gives the printed value and explains from the code why it is wrong.

Mandatory zap to Model III TRSDOS 1.2 Version of SCRIPSIT to run under NEWDOS/80 Version 2. This zap module will not run on other DOSs. If you are running NEWDOS and files appear to load short one sector, be sure these zaps are in. The first two zaps allow for the difference between NEWDOS/80 and the older TRSDOSs in the FCB NEXT and EOF fields. The next 2 zaps move the stack area down so MINI-DOS can be used.

Correction to the printed zap: the official zap sheet prints the third byte of the SCRIPSIT/CMD,11,C9 “to” bytes as FC. Apparat corrected it to F9 in ZAP 043; the bytes above show the corrected value.

Mandatory zap to the old Model I versions of SCRIPSIT/UC and SCRIPSIT/LC to run under NEWDOS/80 Version 2 on the Model III. This zapped module will not run on other DOSs. The first 3 changes are necessary because of the different way the FCB's NEXT and EOF fields are maintained. If you are running NEWDOS and files appear to load short one sector, check to make sure these zaps are in. The 4th zap causes DOS' HIMEM address value in 4411H - 4412H to be used as SCRIPSIT's high memory. The 5th zap re-enables the interrupts so MINI-DOS can be invoked from SCRIPSIT. The 6th through 9th zaps cause parallel printer output to go to port 0F8H. The 10th zap allows for the Model III treating each shift key as an individual code. The 11th through 13th zaps change the stack ptr to allow for MINI-DOS.

Model I: ZAP 003

Optional zap to EDTASM/CMD to disable the lower case to upper case conversion done by EDTASM's keyboard input routine. Most functions within EDTASM will still require upper case, but comments and operands enclosed in single quotes (for DEFM and DEFB) will accept lower case.

Model I: ZAP 006

This is information rather than an actual zap.

1. Where possible, the NEWDOS/80 modules have reserved zap areas. Apparat purposely did not mention them in its documentation as it did not want to draw attention to them. Users are hereby warned that Apparat will preempt these areas without preliminary notice and in its zap verifies will expect these areas to contain zeroes. Users who apply non-Apparat zaps into these areas should carefully maintain logs of what they have done to compare against future NEWDOS/80 zaps for area conflicts.

2. The DOS command ATTRIB (see section 2.3) has an additional optional parameter, LRL=xxx, not specified in that section. LRL=xxx specifies the new logical record length of records in the file where xxx is an integer between 1 and 256. This record length is used now only by DIR, but if user processing assumes a file has a given record length, some users may want the DIR display to reflect it.

3. MINI-DOS (see section 4.2) is illegal under DOS-CALL (see section 4.4). If the DFG keys are depressed while DOS is under DOS-CALL, the triple key depression will be ignored.

4. DOS command ROUTE (see section 2.43) has been altered such that existing routes are displayed only if the ROUTE command has no parameters.

5. DOS command COPY (see section 2.14), format 6 (CBF) has a new optional parameter DFO (Destination Files Only). If DFO is specified, then file contents are copied if and only if the file previously existed on both the destination and source diskettes. DFO is mutually exclusive with FMT.

6. DOS command FORMAT (see section 2.22) has a new optional parameter RWF (RaW Format). If RWF is specified, all errors are ignored and each track is formatted once, whether or not the format actually takes. RWF is used when the user wishes to obliterate the information on a damaged diskette and doesn't have a magnet. RWF is mutually exclusive with KDN, KDD, DDSL, DDGA and PFST.

7. NEWDOS/80 Version 2 does not have the equivalent of Model III TRSDOS's $RAMDIR or $FILPTR functions.

Model I: ZAP 007

Mandatory zap to allow the TRSDOS 1.2 Model III VISICALC to operate with Model III NEWDOS/80 Version 2. The first zap sets the proper BREAK key enable address. The 2nd zap disables VISICALC's directory search feature.

The directory search capability of VISICALC is disabled as NEWDOS/80 does not have the RAMDIR facility that Model III TRSDOS does. However, it is possible to use MINI-DOS to search the directory by (1) typing in the /SL command, (2) pressing DFG to enter MINI-DOS, (3) perform the MINI-DOS functions, (4) clear the display, (5) exit from MINI-DOS, (6) back in VISICALC, press three or more CLEARs to clear the command state, (7) execution one of the /T commands to restore the VISICALC display.

Mandatory zap to allow the old Model I VISICALC to operate with Model III NEWDOS/80. The resulting zapped module will not run with TRSDOS or NEWDOS21; so maintain 2 different versions. The first 3 zaps deal with the different handling by NEWDOS/80 of the user 25ms interrupt routines (see sections 3.8 and 3.9). The 4th zap adjusts for NEWDOS/80's difference from TRSDOS on a returned error code causing VISICALC's directory search to hang if any of the 4 drives are not present or have no diskette mounted. The 5th and 6th zaps adjust for the different HIMEM location in the Model III. The 7th zap disables the 431>H disable of DEBUG (not used on Model III).

Model I: ZAP 011

Optional zap to increase or decrease the sensitivity of double density diskette formatting. One of three byte patterns can be chosen, depending on the reliability of your interface, drive and diskettes. The more sensitive the byte pattern, the greater the probability a marginal diskette will fail format and the lesser the probability that having formatted successfully, the diskette will fail later (under normal careful handling). The less sensitive the byte pattern, the lesser the probability a marginal diskette will fail format and the greater the probability that having formatted successfully, the diskette will fail later. The byte patterns are:

1. E5 E5 = least sensitive during formatting. This was and is the single density standard pattern.

2. 5B 5B = intermediate sensitivity during formatting. This is the TRSDOS Model III pattern.

3. 6D B6 = most sensitive during formatting. This pattern strains the disk formatting and if the interface, drives and diskettes are not in first class condition, 30% or more of the diskettes will fail formatting.

Depending upon the frequency of format failures to diskette failures at other times, the user chooses which of the three 2 byte patterns to use and inserts them in the following locations, first checking that one of the three patterns is already at those locations. Each location receives both bytes, and as a check on each location, the preceding byte is F5.

SYS6/SYS,31,E3
SYS6/SYS,31,FD

Model I: ZAP 012

Optional zap to allow the COPY function to use Model III diskettes in the TRSDOS 1.2 or earlier directory format instead of the TRSDOS 1.3 format the COPY command is prepared to handle. The zap must be backed off when the user wants to re-enable COPY to handle TRSDOS 1.3 format Model III diskettes.

Model I: ZAP 013

Mandatory zap to correct error in format 5 COPY where the BOOT sector was not receiving the correct directory starting lump number if this differed from the PDRIVE specification. The error would manifest itself by directory read error in DIR.

Model I: ZAP 015

Correct error in PDRIVE causing SYSTEM PROGRAM NOT FOUND error when the second drive number is specified wrongly as greater than 9.

Model I: ZAP 016

Mandatory zap to correct error in COPY and FORMAT where DDSL parameter was being erroneously rejected.

Model I: ZAP 017

Mandatory zap to SUPERZAP to correct an error where the DM,P functions was not sending the correct memory contents to the printer.

Model I: ZAP 018

Mandatory zap to correct next-without-for error occuring when CHAINBLD is saving a file in version 1 format and the last line starts with a /./ sequence.

Add to the end of line 126 of CHAINBLD/BAS the following eight characters: :GOTO130

Model I: ZAP 019

This zap is an extension of ZAP 002.

Mandatory zap to DOS to allow ROUTE of the display to cause the BASIC PRINT of a numeric value to not output the value twice.

Model I: ZAP 020

Mandatory zap to BASIC to correct error during marked item and fixed item file processing causing strings greater than 127 characters to be written erroneously and IGEL expressions of the form (len)# and (len)$ to malfunction.

Model I: ZAP 021

Mandatory zap to EDTASM to cause the cursor display to be forced every time the * prompt is displayed, waiting for the next command. This allows the cursor to be turned back on after a return from the DEBUG 123 function, which turns it off.

Model I: ZAP 022

Mandatory zap to DOS to ease some of the problems caused by the fact that NEWDOS/80 Version 1 always used a granule lockout table in the directory GAT sector whereas Version 2 many times does not, leaving that part of the GAT sector for use by the extension for the free/allocated table. Early in the development of Version 2, the rule was that if the PDRIVE specification for GPL was greater than 2, then the lockout table was not used. Later on, the rule was changed to be if the number of lumps is greater than 60H (96 decimal) or if relative byte 60H of the GAT sector = 0FFH, then the lockout table is not used. Some code in SYS6 was not changed to reflect this rule change, causing either a lock out table to not be created or to not be properly extended when the destination diskette has more granules than the source diskette. This change corrects this. However, users are warned that diskettes with GPL greater than 2 (such as 8 inch or double sided, single density 5 inch diskettes coming from Version 1) converted previous to this zap may have trouble with DIRCHECK, on either Version 1 or 2, complaining that one or more granules are locked out but free or locked out but allocated to a file. The diskettes can still be used as it is only DIRCHECK that has the problem, but sooner or later the diskettes should be re-copyed using CBF with FMT so this lockout table conflict will be straightened out and DIRCHECK will stop complaining.

Model I: ZAP 023

Mandatory zap to DOS to:

1. Correct error in format 5 and 6 COPY where destination verify error was causing erroneous END OF FILE ENCOUNTERED or INPUT PAST END error to be triggered for the next sector.

2. Allow FORMAT with BDU option and format 5 COPY with FMT and BDU options to format the destination diskette even though the destination has PDRIVE TI flag M set (TRSDOS model III diskette). The BDU option prevents any NEWDOS/80 system control data from being written on the diskette during format, and thus allows the Model III diskette to copied via format 5. *** Warning, the resulting diskette is no more processable by NEWDOS/80 than was the source diskette; the purpose here is to allow a NEWDOS/80 format to occur as would have happened had TI flag L been set instead of M (which also implies I for Model III TRSDOS diskettes). Remember, this is not a TRSDOS Model III format.

Model I: ZAP 024

Mandatory zap to DOS to eliminate an excessive number of sector write retries due to LOST DATA. Usually the error retry worked, but efficiency suffered as one diskette revolution (200ms) was lost each time.

This mandatory zap is an extension to zap 006 for the old Model I VISICALC being used on the Model III.

Changes to enable use of the right shift key.

Change to enable directory search feature. Note, to work, the directory must start at diskette relative sector 170 and contain only 2 granules (this is the standard when GPL=2, DDSL=17 and DDGA=2 are in effect).

Model I: ZAP 025

Mandatory zap to DISASSEM to correct causing the RTD option to write extraneous data to the diskette and correct a wrong specification in the manual.

On page 6-9, 6th paragraph, change "1st byte = low value, 2nd = high." to be "1st byte = high value, 2nd byte = low.".

Model I: ZAP 027

Mandatory zap to DOS to specify the mutual exclusivity of the FORMAT parameter PFST and to correct the rejection of the combination of the Y and the PFST parameters in FORMAT (see 4th format example on page 2-26).

Append to the end of the PFST=tn3 paragraph on page 2-25 the following: PFST is mutually exclusive with N, DDND, ODN, KDN, KDD, DDSL, DDGA and RWF.

The user will notice that neither KDD or RWF were specified in the FORMAT command; however, KDD is a legal parameter and RWF was defined in zap 004.

Model I: ZAP 028

Information only.

1. Chapter 12 failed to make it clear that though diskettes are content interchangeable under NEWDOS/80 Version 2 between the Model I and Model III, there is a problem dealing with a format control byte for directory sectors of single density diskettes. Carefully read SYSTEM options BK and BN (even though you have only Model III) on page 2-49, WRDIRP command on page 2-52 and the W function of DIRCHECK on page 6-14.

1. For Model III NEWDOS/80 Version 2 users, single density diskettes coming from the model I can be processed on the Model III by setting SYSTEM option BK=Y, setting up the proper single density PDRIVE and then for each such diskette, execute once either the DOS command WRDIRP or the W function of DIRCHECK. After this is done, the diskette can be used as any other diskette under Model III NEWDOS/80 Version 2. Subsequently, this diskette can not be processed by the Model I TRSDOS 2.3, but it can be processed by the Model I NEWDOS/80 Version 1 provided the format of the diskette is not changed to one of the variety of formats available on Version 2 but not available on Version 1). However, once this diskette is used back on the Model I NEWDOS/80 Version 1 and a directory sector is updated, the diskette cannot be reused on the Model III without performing again the WRDIRP or DIRCHECK function on that diskette on the Model III (remember, NEWDOS/80 Version 1 does not have either of these two functions).

2. For users that have NEWDOS/80 Version 2 for both the Model I and III and wish to use single density 5 inch diskettes interchangeably between the model I and model III, set SYSTEM options BK=Y and BN=Y on the Model I and BK=Y on the Model III. Then, for each such single density diskette, execute once either WRDIRP or the W function of DIRCHECK. This can be done on either the Model I or III and all such diskettes do not have to be done at the same session. Each such diskette can now be used interchangeably between the Model I and Model III under NEWDOS/80 Version 2 (don't forget the proper PDRIVE specifications), but the diskette cannot be processed by TRSDOS 2.3

2. For BASIC function RENUM (see section 7.9 on page 7-5) the 4th and 5th formats listed (RENUM X and RENUM U,X) are not valid and should be deleted from the middle of page 7-5. If the X parameter is to be used, it must be done via the 1st format listed as X is meaningless unless specific values for ppppp and/or qqqqq are also specified.

3. Some users have asked for more distinctions between full diskette COPY (format 5) or Copy By File COPY (format 6), both specified in section 2.14.

1. Format 5 copies a full diskette sector by sector and is generally faster than format 6, which copies files individually. However, if the source diskette is relatively empty, format 6 may be faster.

2. In format 5 the source directory becomes the destination directory, including the same size and relative sector position on the diskette, while in format 6, the two directories are considered separate just as in a format 1 through format 4 COPY.

3. Generally, if format 5 is used, both the source and destination PDRIVE specifications for GPL, DDSL and DDGA must be the same (though only the restriction on GPL is enforced, but not if BDU is specified); the other PDRIVE parameters may be different provided the destination diskette is to have at least as many sectors as the source diskette (though the format 5 specifications say that sectors per track must be the same; this is not so in Version 2 where it was in Version 1).

4. Format 5 with the BDU option allows some alien diskettes to be copied that otherwise could not be copied.

5. Format 6 allows a diskette's contents to be copied between diskettes having a different number of granules per lump (GPL), the directories positioned differently on the diskettes, the directories of different sizes, or the destination diskette having less sectors than the source.

6. Format 6 copies all of a source diskette's files or a selected subset of those files.

7. Both format 5 and 6 allow the option of formatting the destination diskette (FMT) or not (NFMT). Formatting a diskette magnetically initializes the entire diskette including the inter-sector control bytes used only by the drives and the controller. Many users prefer to do this every time a back up is done. Of course, formatting a diskette destroys the previous contents.

8. If format 6 is being used to copy a NEWDOS/80 Version 2 system diskette, the FMT option must be specified. This assures the correct BOOT, SYSTEM and PDRIVE control informat is stored on the destination diskette, and the correct positioning of SYSTEM files which, excepting for BOOT/SYS and SYS0/SYS, are all positioned on the destination diskette in same position relative to the directory that they are on the source diskette.

9. In format 6 where NFMT is specified, system files are NOT copied to the destination diskette if they are not already existing in the destination directory. This is because system files usually use specific FDEs in the directory, and only FMT can assure that these FDEs are available.

10. Format 5 without BDU and format 6 with FMT both assume the possibility of the destination diskette being used later as the system diskette and the destination drive or one like it being used later as drive 0; therefore both initialize the BOOT/SYS file to contain the proper BOOT code and drive 0 PDRIVE specifications.

Model I: ZAP 030

Mandatory zap to DOS to allow files to be copied from and to diskettes used by Model I TRSDOS 2.3B and higher as well as from and to diskettes used by Model III TRSDOS 1.3 or higher. After applying the documentation changes given below, see section 12.5.1 on page 12-7, the 'flag M' paragraph on page 2-35 and the bottom half of page 2-15.

This enhancement expands the definition of PDRIVE TI flag M (see page 2-35). When the M flag is specified and the TD field specifies double density (i.e., TD=E), the PDRIVE specification is assumed for a Model III TRSDOS diskette and TI flag I is implied (see example 3 on page 2-38). When the M flag is specified and the TD field specifies single density (i.e., TD=A), the PDRIVE specification is assumed for Model I TRSDOS 2.3B or higher diskette, and TI flag I is not implied and must not be specified (see example 1 on page 2-38 with TI=AM).

Radio Shack has started distributing certain new programs (i.e., COBOL) with or on Model I TRSDOS 2.3B or higher diskettes with that system being somewhat different than Model I TRSDOS 2.3, including the use of RBAs as discussed in section 12.1 for the Model III. These diskettes are NOT compatible with NEWDOS/80 diskettes, and, as with Model III TRSDOS diskettes, COPY is the only function of NEWDOS/80 that can be used with the Model I TRSDOS 2.3B diskettes (though FREE and DIR (except EOF and special flags) appear to work).

Files on either Model III TRSDOS or Model I TRSDOS 2.3B diskettes that are to be used either by NEWDOS/80 or user programs executing with NEWDOS/80 must be copied to NEWDOS/80 diskettes. FORMAT or COPY with FMT option cannot be used to format a diskette in either the Model III TRSDOS or the Model I TRSDOS 2.3B format; however, format 5 COPY with the BDU option can be used to make copies of those diskettes.

*** ZAP 008 must NOT be installed in a NEWDOS/80 that is used to copy Model I TRSDOS 2.3B files. ZAP 008 must be used for Model III TRSDOS 1.1 or 1.2 diskettes.

Insert the following notes in the outside margin of the specified paragraph:

1. Page 2-9, next to last paragraph: "For Model III TRSDOS and Model I TRSDOS 2.3B diskettes, see ZAP 025."

2. Page 2-15, "The COPY command" paragraph: "This section applies also to standard 35 track, single sided, single density diskettes for Model I TRSDOS 2.3B or higher."

3. Page 2-15, "The user must" paragraph: "See examples 1 and 3, section 2.37".

4. Page 2-35, "Flag M" paragraph: "Expanded to include Model I TRSDOS 2.3B or higher diskettes. See ZAP 025

5. Page 2-38, example 1: "For Model I TRSDOS 2.3B diskettes, use TI=AM (see ZAP 025)." Also in this paragraph, change the last two words to read "option BN" instead of AN.

6. Page 12-7, paragraph 12.5.1: "See ZAP 025."

Model I: ZAP 031

Mandatory zap to DOS to:

1. prevent COPY from setting file update flag on in Model I TRSDOS 2.3B and Model III TRSDOS diskettes when that bit is used differently in those systems.

2. enable /ext type CBF file selection when the source is a Model I TRSdos 2.3B or Model III TRSDOS diskette.

Model I: ZAP 032

Mandatory zap to correct error in SUPERZAP during the DM function and during the F, find function.

Model I: ZAP 033

Mandatory zap to the Ryan-McFarland Corp's COBOL version 1.3B distributed by Radio Shack to allow it to run with NEWDOS/80 Version 2 for the Model I and Model III. This zapped version will not run under TRSDOS. Users must copy the COBOL multiple files onto NEWDOS/80 diskettes (see zap 025).

Model I: ZAP 034

Mandatory zap to DOS to correct a directory clobbering error that occurs when either CLOSE or KILL frees up a FPDE or FXDE that occupies the first FDE slot in a directory sector. This error was missed during BETA testing as it was caused by a late adjustment to handle the TRSDOS Model III diskettes. A few persons were complaining about directories being clobbered, but only on September 12th was an error report made that lead to the discovery. Though the problem would appear to affect many users, apparently to date it has not.

Model I: ZAP 035

Information zap.

1. Documentation correction for EDTASM. Tape I/O is NOT available for the Model III. If it is attempted, BAD PARAMETER(S) error will be given.

1. Place in the outside margin of the "2. L T=nnnnnn" paragraph of page 6-15 the following restriction: "Model I only"

2. Place in the outside margin of the 2nd line of page 6-16 of page 6-16 the following restriction: "Model I only"

2. Correct the "A list of all" paragraph on page 1-3 to read "NWD80V2/ILF and NWD80V2/XLF" instead of "NWD82V2/ILF and NWD82V2/XLF".

3. Delete the words "sectors per track, " from the "Format 5 is a full" paragraph of page 2-11.

4. The MM=addrl function of ROUTE requires the main memory location addrl to be greater than 51FFH. In the "Any of the devices" paragraph of page 2-43, insert the words "greater than 51FFH" after the word "location" in the phrase "memory location of a user".

Model I: ZAP 036

Mandatory zap to DOS to correct rare occurring error that could, if the same HIT code is used more than 31 times in a directory, cause file open to not find a file and to put two files with the same name/ext on the diskette.

Model I: ZAP 040

Information and manual corrections.

1. A number of users have had trouble with tape I/O under NEWDOS/80 Version 2. Some of the early copies of NEWDOS/80 Version 2 had errors due to undetected RAM errors during duplication and in maybe as many as 20 cases this affected the EDTASM or LMOFFSET module. However, if these modules were bad, they usually also had problems with disk I/O as well as cassette I/O and so if disk I/O works fine, we assume it is not a bad copy of NEWDOS/80. Tape I/O has long history of trouble, varying from computer to computer and especially from tape unit to tape unit such that any particular tape will fail on somebody's cassette unit. This has always been an exasperating problem and the main reason why cassettes are not used at Apparat (though we do act as a retailer/distributor for products distributed on cassettes produced by others). Because cassettes are not used at Apparat, NEWDOS receives very little testing with cassettes, and in the future we are considering withdrawing all support (i.e., LMOFFSET and EDTASM) from cassettes. Cassette support for EDTASM for the Model III has already been withdrawn and will probably soon be withdrawn for the Model I (since the purpose of our EDTASM was to give disk support, not cassette). For now though, we will restrict our error study to those problems presented to us on a diskette containing the actual NEWDOS system used. If the user presents us with a cassette along with the diskette we will test that as well; otherwise we will test with simple programs from disk in-house. Neither the diskette nor the cassette will be returned to the user. Lastly, if you can avoid use of cassettes, DO!!!!!

2. The specifications for ROUTE using the MM=addrl operand are in error in the manual.

1. Page 2-43, 3rd paragraph, 3rd line, change "12" to "16".

2. Same paragraph, 5th line, change "13th" to "17th".

3. Page 2-44, top line, change "0FE8CH" to "0FE90H".

3. A number of users has asked why Automatic Density Recognition (ADR) was not used in NEWDOS/80 Version 2. We wanted to include ADR but found it impractical unless we limited or expanded other capabilities made available by PDRIVE. Since we were already two months late in releasing Version 2, we decided to release without it. Part of the problem is in providing a second SPT parameter and an extra indicator for track 0 usage (remember, Version 2 operates with double density diskettes that may or may not have track 0 reserved for single density). We also felt that if we included ADR, we should also include ASR (automatic side recognition). For now, we will remain without ADR and ASR, but will not rule it out for a subsequent NEWDOS/80 version.

4. For BASIC CMD "O" and multi-dimensional arrays, a few users have asked for clarification of term REN used in the documentation for on pages 7-14 through 7-17. CMD"O" does not care whether an array is single or multi-dimensional as CMD"O" only concerns itself with the relative positioning in main memory between array elements and not with the actual subscripts for a given element, except for determining the main memory position of the first element participating in the sort as specified in the CMD "O" statement. As an aide to the programmer to understand the sort order, a formula was given for two and three dimensional arrays to determine the REN of any array element given its subscripts. The following working BASIC program demonstrates the relationship between REN and subscripts for a three dimensional array, using R1, R2, R3, X1, X2 and X3 to correspond with the usage at the bottom of page 7-14 and top of page 7-15.

10 R1=3: R2=4: R3=2: DIM A(R1,R2,R3)
20 REN=0: FOR X3=0TOR3: FOR X2=0TOR2: FOR X1=0TOR1 'CREATE ARRAY IN REN ORDER
30 IF REN <> X1+X2*(R1+1)+X3*(R1+1)*(R2+1) THEN PRINT"ERROR": STOP
35 ' THE ABOVE ASSURES THE FORMULA COMPUTES TO THE CURRENT REN NUMBER
40 A(X1,X2,X3)=REN: REN=REN+1: NEXT X1,X2,X3 'STORE THE REN NUMBER IN THAT ELEMENT
50 CMD"O",0,A(0,0,0) 'SORT ARRAY IN ASCENDING NUMERIC ORDER
60 ' THE ARRAY ORDER SHOULD NOT HAVE BEEN CHANGED.
70 FOR X3=0TOR3: FOR X2=0TOR2: FOR X1=0TOR1 'LIST ARRAY IN SAME ORDER STORED
80 PRINT A(X1,X2,X3);: NEXT X1,X2,X3 'AND THIS SHOULD BE ALSO THE SORTED ORDER

Elements with one or more zero subscripts do participate in the sort if that element is within the main memory range of elements sorted, i.e., has a REN greater than or equal to the REN of the 1st sort element and less than or equal to the REN of the last sort element.

5. Correct the last paragraph of page 2-27 by deleting the 3rd sentence and changing the 4th sentence to read "Hex codes less than 20H or greater than the SYSTEM option AX value will be displayed as periods.".

6. ZAP 025 has in its 7th, 10th, 11th and 12 paragraphs, references to ZAP 031 which must be changed to refer to ZAP 025.

Model I: ZAP 041

Mandatory zap to correct error in BASIC's RENUM function giving SEQ # OVERFLOW when large programs, say over 26,000 bytes of text, are renumbered. Though a number of users called on this problem, it wasn't until a user sent us a written error report with the problem program on a system diskette that we finally had enough to go on.

Model I: ZAP 042

Mandatory zap to DOS to correct omission from ZAP 015 (ROUTE) which caused SYSTEM option BA to cause hang on reset.

Model I: ZAP 043

Mandatory zap to DOS to disable SYSTEM option BM. SYSTEM option BM=N caused the full diskette verify to be bypassed when the user felt the track verify that occurred immediately after a track was formatted was sufficient. However, if the user is formatting more tracks that the drive can physically handle, FORMAT with SYSTEM option BM=N will not detect the error whereas it will with SYSTEM option BM=Y. Therefore, SYSTEM option BM is dropped, and the full diskette verify will always be done.

On the outside margin of the BM=yn paragraph of page 2-49, write the following: "eliminated by ZAP 035".

Model I: ZAP 044

Mandatory zap to correct BASIC function REF$ to (1) avoid occasional misses of printer line advance and (2) disable printer operations after the function.

Model I: ZAP 045

Optional zap to DOS to allow 'JKL' to print graphics on the EPSOM printers that use graphic codes 0A0H - 0DFH. This is done by converting hex codes 80H through 0BFH to CA0H through 0DFH.

Use next zap if 0BFH rather than SYSTEM option AX is to govern as high ASCII for JKL.

Model I: ZAP 046

Mandatory zap to remove a part of a unreleased zap that inadvertently was placed on some master diskettes. If the 'before' contents do not exist on your master diskette, ignore this zap. If the 'before' contents do exist, then this zap must be done before zap 039 as 039 uses some of the affected area. Please note that 4 bytes of loader control information remain unchanged by this zap.

Mandatory zap to DOS to correct an error where disk write precompensation was not being done for high numbered tracks if the PDRIVE TC parameter was an odd, vice even, number (i.e., TC=35)

Mandatory zap to correct DOS handling of 8 inch, double density, single or double sided, single volume drives (PDRIVE TD=H) where the computer hardware is modified to handle double CPU speed and 8 inch, double density, single or double sided, single volume operations. The PDRIVE SPT maximum values are 30 for single sided and 60 for double sided. The PDRIVE GPL must be at least 3 for single sided and at least 5 for double sided; however 8 is recommended in both cases. This zap does NOT mean that your particular computer can handle this type of drive; for now we know of no Model III's that can, but 8 inch double density support was included in anticapation that eventually some would.

Model I: ZAP 047

Mandatory zap to EDTASM to correct error occurring when shift-left-arrow is used to erase a filespec response.

Model I: ZAP 048

Mandatory zap to Version 3.1 of SCRIPSIT for TRSDOS 1.1 or 1.2 to run with NEWDOS/80.

Correction to the printed zap: the official zap sheet prints the third “to” byte of SCRIPSIT/CMD,11,43 as 45 and the third “to” byte of SCRIPSIT/CMD,11,CE as E2. Apparat corrected them to 4F and DF in ZAP 043 (the 45 was a fatal error that kept SCRIPSIT from running); the bytes above show the corrected values.

Correction to ZAP 001, in the SCRIPSIT/CMD,11,C9 zap, change the 3rd byte of the 'to' part from FC to F9 if it not already F9. This was not a fatal error.

Correction to ZAP 042, the 3rd byte of the 'to' part of the SCRIPSIT/CMD,11,43 zap is to be changed from 45 to 4F if not already 4F. This was a fatal error not allowing SCRIPSIT to run.

Correction to ZAP 042, the 3rd byte of the 'to' part of the SCRIPSIT/CMD,11,CE zap is to be changed from E2 to DF if not already DF. This was not a fatal error.

Mandatory zap to DOS to correct error in DIR $ or DIR $0 command where DOS hangs if any response other than ENTER is given to the diskette mount requests.

Model I: ZAP 049

Optional zap to DOS to allow the DOS PRINT and LIST commands to accept all control characters in the hexadecimal range 00 to 1F instead of just 0D (end of line). If this zap is used, users must assure that files used with PRINT and LIST do not contain control characters the display or printer cannot handle. Remember, the high bit of all characters is zeroed, thus display graphic characters 80 - 9F will be transmitted as 00 - 1F.

Model I: ZAP 050

Mandatory zap for PROFILE Version 3.0 being issued to run with TRSDOS 1.3. This zap disables some of the error checking being done to determine if a drive is available.

Note, during some testing, PROFILE did not have enough space on drive 0 to initialize the files. You may find that some files must be deleted from drive 0 to have enough room.

Information zap.

1. Users must remember that the Model I TRSDOS 2.3B or higher and Model III TRSDOS 1.3 or higher, amongst other things, both went to using RBAs in the NEXT and EOF fields of the FCB, thus intentionally or unintentionally restablishing compatibility with NEWDOS21 and NEWDOS/80 in the use of those two fields (which many user programs use), even though the EOF fields in the directories (which most user programs don't use) are now incompatible. Though files from those systems must be copied to NEWDOS diskettes, assembly language programs upgraded to run with those TRSDOS systems are more like to run with NEWDOS without change then they were before. For example, on the Model III, SCRIPSIT Version 3.2 has been found to work as-is. So, before calling Apparat to see if zaps exist for a given program, try it out, giving special attention to the file I/O.

2. The manual failed to explain that when SYSTEM option AJ=N or when the up-arrow key is held down during reset/power-on, DOS loses the ability use the lower case driver (Model I only) or to actually input keyboard characters from the chain file during chaining as these functions depend upon DOS's keyboard intercept routine being enabled. SYSTEM options AU=N and BF=N (Model I only) and are also forced. DOS will think it is activating chaining, but actually the input characters will continue to come from the keyboard; the DOS READY prompts will not be seen as DOS thinks it is chaining. For LCDVR (Model I only), the command will execute but the key input functions for lower case drive will not be done. Insert the note "see ZAP 047, part 2" in the outside margin at the following places in the manual.

1. Page 2-7, the "CHAINING is discussed" paragraph.

2. Page 2-29, the "In NEWDOS/80" paragraph.

3. Page 2-47, the "AJ=yn" paragraph.

4. Page 4-9, the "If a DOS recognized" paragraph.

3. Chain files must always have a name-extension. When creating a CHAIN file, you must always specify a name-extension in the filespec, excepting that CHAINBLD/BAS will assume name extension /JCL if you don't give one. If the filespec given in a DO or CHAIN command does not specify a name-extension, then /JCL is assumed; therefore it is recommended that the name-extension /JCL be used on chain files when created. Place the note "See ZAP 047, part 3" in the outside margin in the following places in the manual.

1. Page 2-7, the "When the system" paragraph.

2. Page 4-8, the "Chain file creators" paragraph.

Model I: ZAP 051

Mandatory zap to BASIC to correct CLOSE without explicit fan(s) where filearea 2 and up was not being closed if filearea 1 was not open and the V parameter was specified in the BASIC invocation sequence.

Model I: ZAP 052

Mandatory zap to DOS to extend ZAP 039. After that zap, we found that precompensation was going on all of the time during diskette format. Some users were complaining about this, but our test routines were just not seeing it.

Part mandatory and part optional zap to MICROSOFT's BASIC compiler Version 5.23 for the Model I (the release Version for a long time)(the first line a /LST file created by the compiler gives the compiler version number) to allow it to run with NEWDOS/80 Version 2 on the Model III. This zap has been provided to Apparat by MICROSOFT and if there are questions with this zap, please contact MICROSOFT. Once these zaps are applied, this compiler and the compiled programs cannot be used with TRSDOS!!! Future enhancements to the compiler may require the optional changes below to be backed off; therefore users should maintain copies of the compiler (1) as it existed before the mandatory changes below were applied, (2) after the mandatory changes but before the optional changes below are applied and (3) the final result. Also, remember, the BASIC compiler's L80/CMD is not for use with FORTRAN, assembler, etc., but only with BASIC. Lastly, remember it is the model I compiler that is being zapped.

The production of this zap required a large amount of research and testing by MICROSOFT, and APPARAT sincerely thanks MICROSOFT for this extensive effort to make the BASIC compiler operate with NEWDOS/80, Version 2.

Note, in the above zap both the before and after portions contain a CD 39 44 sequence, which is a sector-write-without-verify-read. If the sequence is CD 3C 44, then it is really a sector-write-with-verify-read (which uses an extra disk revolution (200 ms) per sector write). Thus the old contents may have the 3C and you may optionally use the 3C in the new sequence if you want the verify read.

*** Optional section

The following optional zaps are for:

1. The LOF function is changed to work like NEWDOS/80, rounding up the returned value if EOF is not integer divisible by the logical record length used in the OPEN statement. Further, if the result exceeds 32767, BAD RECORD NUMBER error results.

2. PUT and GET without explicit record number works correctly.

3. LOC functions correctly for the logical record length in the OPEN statement.

DIR/SYS,xx,yy Search the directory for BRUN/CMD's directory entry, the associated line on the SUPERZAP display should look something like this: 1020 0062 0042 52 55 4E20 2020 2043 4D44 ...b.BRUN...CMD change the 62 (the 4th) byte to F6.

Note, the above zap to L80/CMD changes the default data address for compiled BASIC programs from 8A00H to 8B00H to allow an extra 256 bytes for BASIC system use. If the -R switch is issued during the linking process, the -D switch must be reset to 8B00 instead of 8A00 as mentioned in the compiler manual.

Model I: ZAP 053

Mandatory zap to DOS to allow COPY with CBF option to allocate space on Model III TRSDOS diskettes beyond track 23.

Model I: ZAP 056

Mandatory zap to DOS to correct directory errors created during format 5 COPY when copying to a destination diskette that is to contain more granules than the source diskette and when the source diskette has less than 61H (97 decimal) lumps and the destination diskette is to have more than 60H (96 decimal) lumps. In NEWDOS/80 Version 2, in order to allow a maximum of C0H (192 decimal) lumps in the granule allocation table, that table (normally in 00-5F of the GAT sector) expands into and supercedes the granule lockout table (normally in 60-BF of the GAT sector. This error was leaving the GAT granule lockout table in existence in the destination directory (remember, it is transferred over from the source diskette in format 5 COPY) when it should have been done away with to make room for the expanded granule allocation table. The error is immediately detectable by DIRCHECK after the format 5 COPY by the presence of one or more BAD "GAT" SECTOR BYTE errors. Otherwise, the error is not seen until TRACK # TOO HIGH error occurs when writing to the diskette and a granule beyond those allowed for the diskette is erroneously allocated; the file getting the error will NOT have had its EOF increased to include the erroneous sector. DIRCHECK will, in addition to the GAD "GAT" SECTOR BYTE errors, then display EXTENT SPACE OVERFLOWS DISKETTE for that file, but since EOF does not include that bad granule, single file COPY or format 6 COPY will still be able to copy the file. Therefore, any bad diskettes should be recoverable by using a format 6 COPY with FMT option to copy the contents of the bad diskette onto another diskette. You can then use either format 5 or 6 COPY with FMT option to copy it back.

This zap is large as part of SYS6/SYS is being moved to SYS17/SYS to make more patch area available in SYS6/SYS.

Model I: ZAP 057

Mandatory zap to LMOFFSET to correct error occurring when a object code block's load point is in the range 3F00 to 3FFFH.

Model I: ZAP 058

Mandatory zap to DOS to correct I/O timing loop found to be too long to support 8 inch disk operations on the Model III.

Optional zap to DOS to cause DIR to actually read ENTER and BREAK from the keyboard rather than just look at the keyboard matrix. This zap allows BREAK to work for that function only if the BREAK key is enabled. This zap allows remote terminal operators of NEWDOS/80 to perform the DIR function when more than one display page will be involved. NEWDOS/80 was not designed to be run from remote terminals and at many places in its code looks directly at the keyboard matrix rather than actually accepting an input key when looking for BREAK, ENTER, UP or RIGHT ARROW. This zap changes only one of these situations, but a number of users have said they would be happy with that.

Model I: ZAP 061

Mandatory zap to DOS force the 4445H call to DOS (back up one record) to set bit 6 of the FCB 2nd byte (disables EOF truncation).

Model I: ZAP 062

Information zap.

1. NEWDOS/80 V2 BASIC functions LOAD, RUN and MERGE implicitly require that the text file being read be already in ascending sorted line number order whereas NEWDOS/80 Version 1, NEWDOS/21, TRSDOS, VTOS, LDOS, DOSPLUS and the other DOS's do not. Normally, the BASIC program files are in sorted line number order; so this difference was not noticed for some time into Version 2's release. Some users prefer to create text files in random line number order, relying on the implicit sort (not in NEWDOS/80 V2) done during LOAD, MERGE or RUN to sort the lines. These users must find some way or pre-sorting the text files, and since leading zeroes are suppressed from line numbers (causing line 5000 to sort before line 51), normal sorts won't work. The following sort program (known as CODESORT/BAS) will perform the sort, sorting the input text file into a different output text file.

10 CLEAR 2000: DEFINT A-Z: NR=0
20 PRINT"FILESPEC OF BASIC PROGRAM TO BE SORTED?": LINEINPUT FS$
30 OPEN"I",1,FS$: BC!=LOC(1)%
40 IF EOF(1)=0 THEN NR=NR+1: LINEINPUT #1,A$: GOTO 40
50 A$="": CLOSE
60 DIM CD$(NR), IX(NR), SN(NR): CMD"F=SASZ",BC!=NR+200
70 OPEN"I",1,FS$: X=1: K=1
80 IF X>NR THEN 170
90 LINEINPUT #1,CD$(X): Y=LEN(CD$(X)): Z=1: W=0: SN!=0: K=K+1
100 IFY=0 THEN 160
110 IF Z>Y THEN 130 ELSE J=ASC(MID$(CD$(X),Z,1)): Z=Z+1: IF J=32 THEN 110
120 IF J>=48 AND J<58 THEN W=W+1: SN!=10*SN!+J-48: GOTO 110
130 IF W>0 AND SN!<65530 THEN SN(X)=SN!-32768: X=X+1: GOTO 80
140 PRINT K;"TH LINE HAS BAD OR MISSING LINE NUMBER. BYPASS IT? (Y/N) ";
145 INPUT A$
150 IF A$="N" THEN END ELSE IF A$<>"Y" THEN INPUT"BAD REPLY";A$: GOTO 150
160 NR=NR-1: GOTO 80
170 CLOSE: IF NR=0 THEN PRINT"NO RECORDS TO SORT": END
180 CMD"O",NR,*IX(1),SN(1)
190 PRINT"SORTED OUTPUT FILESPEC? "; LINEINPUT FS$
200 OPEN"O",1,FS$
210 FOR X=1 TO NR: PRINT #1,CD$(IX(X)): NEXT
220 CLOSE: PRINT"DONE":END

2. In BASIC, RENUM does not renumber the CMD"F",DELETE statement properly. No zap will be issued to correct this.

3. The manual failed to inform programmers building programs to be executed that the command keyword or program name (filespec) is the first parameter of each DOS command and that, on entry to that program or DOS command function, register HL points to the parameters following the program name (filespec) in the DOS command statement that invoked the program. Examples:

1. XXXXXX This DOS command causes user program XXXXXX/CMD to be loaded from whichever drive it is found on into memory and program execution commenced at its entry location. At that time, register HL points to the EOL character (0DH) since there are no parameters following the program's filespec. Note, in absence of a name-extension for the filespec XXXXX, /CMD was substituted. Also, since no drive number was given, the drives were searched, starting with the drive 0, looking for the first occurrence of XXXXX/CMD.

2. YYYY/OBJ:1,5,JJJ:1 This DOS command causes user program YYYY/OBJ:1 to be loaded into main memory from drive 1 and program execution commences at its entry location. At this time, register HL points the character 5 in the above command, as this is the first character of the first parameter following the program filespec. The user program may interrogate the parameter(s) with the EOL character (0DH) indicating the end of parameters.

3. ZZZ,Y,N,MYFILE This DOS command causes user program ZZZ/CMD to be loaded into main memory and execution started at its entry location with HL pointing to the character Y

3. A number of users have asked why NEWDOS/80 Version 2 lacks features that other DOS's have. For the most part and for obscure reasons, we just elected to exclude them, but in many cases the main problem is that sufficient resident main memory space or overlay main memory space or both is not available.

1. In the DOS main memory region, 4000H thru 51FFH, NEWDOS/80 has 256 bytes less resident (always in memory) code/data than other DOS's have as it uses this 256 bytes to make the DOS overlay programs (i.e., SYS1/SYS) bigger.

2. Some DOS's have taken part of their resident code/data into high memory in order to gain more resident memory for DOS. For NEWDOS/80 Version 2, it was decided to remain out of high main memory, with the exception of the spooler, which was already there.

3. NEWDOS/80 has MINI-DOS which most other DOS's do not. This means that most of the DOS commands (DIR, FREE, LOAD, etc.) that execute in the 5200H thru 6FFFH region of main memory (and may call overlay routines that execute in the 4E00H thru 51FFH region) in other DOS's must execute in NEWDOS/80 entirely within the 4D00-51FFH DOS overlay region. This complicates the effort to extend the capabilities of any given DOS command.

4. A number of users have asked why DIRECTORY READ ERROR or DIRECTORY WRITE ERROR appear as the DOS error message when an error occurs with a directory sector. Why not display the regular error code? We did this in order that normal file processing, the user would know that the directory, rather than his/her file, was the source of the error. At the time the error code substitution takes place, the system does not know whether or not the directory I/O was subsidiary to file I/O. We do apologize for the confusion created when the directory I/O was the main I/O (i.e., in DIR, FREE, etc.). The user can go to SUPERZAP and step through the directory (via DD, DTS or DFS (on DIR/SYS) to determine which sector is bad and what is the actual complaint. VDS mode can also be used.

Model I: ZAP 063

Mandatory zap to DOS if and only if the following two verifies exist.

SYS18/SYS,02,A9 59 00 0F 30 06
SYS18/SYS,02,FC 54 5B 5B 5B

If these two conditions do not exist, then ignore this entire ZAP. During production of the NEWDOS/80 Version 2 diskettes for the Model III, the master diskettes, dated 01/12/82, were found to be bad on 01/21/82, after some 100 to 300 NEWDOS/80 diskettes had been created and shipped with the bad sector. We don't understand how this alteration of the master diskette appeared, but it did, must be corrected, and we apologize.

Mandatory zap to DOS to cause the /./5Y function of chaining (see page 4-11) to properly exit the current DOS-CALL level, if any, under certain circumstances where it was not. This problem can also be avoided by using CHNON,Y instead of /./5Y if DOS is awaiting its next command at that DOS level.

Model I: ZAP 064

Information zap.

1. When COPY format 6 (CBF) is used to copy a system diskette and the system files are to be copied, the FMT parameter MUST be specified!!! On page 2-14, last paragraph, is stated "If NFMT is specified, ... system files are not copied unless already existent in the destination file directory." This is not true; if NFMT is specified or implied, the files are copied, but (1) SYS0/SYS will usually be in the wrong position causing BOOT to fail and (2) other system files may be in the wrong directory slots, eventually causing even worse trouble.

2. Some users have had GAT OVERFLOW error occur when using CBF with FMT to copy a system diskette. The system files SYS1/SYS through SYS21/SYS on a system diskette are positioned near the directory, some file above and some below, to enhance system efficiency. During the CBF COPY, the each system file is assigned space on the destination diskette in the same position relative to the directory as on the source diskette, and if that position is beyond either end of the diskette, GAT OVERFLOW error occurs. The solution to the problem is to cause the directory to be positioned nearer the center of the diskette. Two of the destination diskette's PDRIVE parameters are involved in the directory positioning: GPL and DDSL. Compute the number of lumps on the diskette and compare against DDSL to determine which end of the diskette the directory is too close to. You can take one of three actions to cause the directory to move closer to the diskette center: (1) change the DDSL value, (2) decrease the GPL value if the directory was too near the end of the diskette, or (3) increase the GPL value if the directory was too near track 0.

3. A number of users have complained that the LIST and PRINT commands do not allow for graphic characters. This was done so purposely as the intent with both LIST and PRINT was to provide a rudimentary, emergency method of listing or printing regular text files (files whose printable characters are between 20H and 7FH ASCII or that modulate to those values). These two commands were seldom used in NEWDOS+ or NEWDOS/80 Version 1, and we have been surprised by the increased usage in Version 2. For a subsequent release of NEWDOS80, we will try to add more capabilities to allow for graphics, but for now we simply apologize that the capability is not there.

4. ZAP 054 causes Model III's with AM disk controllers to malfunction with LOST DATA DURING WRITE. This is because the AM controller CPU-hold-for-DRQ interval is too short compared with the standard Radio Shack interval, which is specified at 1000 microseconds. If you have this type of disk controller, back off ZAP 054.

Model I: ZAP 065

No zap with this number appears in the Model III zap list or index.

Mandatory zap to BASIC to correct error in dynamic MERGE occurring when the old text has lines within the range of the merging text (though not matching line numbers, which is not allowed). This is an unusual condition but nevertheless legal. This error was causing string variables whose strings are in the text area to not be properly repointed into the resulting text.

Model I: ZAP 066

Mandatory zap to allow the TRSDOS 1.2 Model III VISICALC Version VC-150Y0-T83 to operate with Model III NEWDOS/80 Version 2. This zap disables VISICALC's directory search feature.

The directory search capability of VISICALC is disabled as NEWDOS/80 does not have the RAMDIR facility that Model III TRSDOS does. However, it is possible to use MINI-DOS to search the directory by (1) typing in the /SL command, (2) pressing DFG to enter MINI-DOS, (3) perform the MINI-DOS functions, (4) clear the display, (5) exit from MINI-DOS, (6) back in VISICALC, press three or more CLEARs to clear the command state, (7) execution one of the /T commands to restore the VISICALC display.

Model I: ZAP 067

Mandatory zap to DOS to correct an error in CREATE whereby the old file's (not the new) EOF was not being set = 0 when REC=0 parameter spec'ed or defaulted to.

Model I: ZAP 068

Mandatory zap to DOS to correct error in the DMDB function of SUPERZAP where the F, function was not displaying the correct dump location.

Correction to the printed zap: the official zap sheet prints the verify bytes for SUPERZAP/CMD,05,12 as 03 3A B2 54 CD. That is a misprint: the bytes in the file are 03 2A B2 54 CD, which are shown above, and SUPERZAP will not verify 3A. The code shows why:

• 05,12 is memory 585CH. The 03 is the offset of JR Z,5860H at 585BH, which skips the three bytes at 585DH-585FH unless the command is DMDB (bit 3 of Register B). Those three bytes are the instruction the zap replaces with CALL 5214H.
• 2A B2 54 is LD HL,(54B2H): Register Pair HL gets the dump's base address, the first two bytes of the DMDB file (stored at 54B2H by 5609H). The routine called next, 5E37H, saves and restores Register Pair HL, so that value reaches the search as its start position.
• 3A B2 54 would be LD A,(54B2H): only the low byte of the address, into Register A. 5E37H returns the key typed in Register A straight afterwards, so the byte would be lost and the DMDB branch would do nothing.
• The zap's own routine at 5214H (00,18) shows what was meant: it builds Register Pair HL from the base address's high byte at 54B3H (Register L stays 00H) and stores it at 54C3H, the page address the search displays. The original code loaded Register Pair HL but never set 54C3H, which 520DH had left at 0000H, so the F function showed the wrong dump location.

Model I: ZAP 069

Mandatory zap to BASIC to correct an error in CMD"O" sort of floating point values and, to a much lesser degree, of characters strings. It is astonishing that this error was finally reported 8 months after Version 2 release; we simply refused to believe it as this meant virtually no one is using the floating point sort feature. The reporting user was persistent, however, sending in a very detailed problem report even so far as providing the zap! Well done!!! We thank this user and all others that persist in proving their point.

Model I: ZAP 070

Mandatory zap to VISICALC Version VC-160Y0-T83 for Model III TRSDOS 1.3 to operate with Model III NEWDOS/80 Version 2. Refer to ZAP 063 as this zap performs the same functions as that zap did for the TRSDOS 1.2 version.

Model I: ZAP 071

Information zap on Model III TRSDOS diskettes.

Despite explicit and implicit statements in the manual and the zaps, users continue to think that Model III TRSDOS type diskette are directly useable with NEWDOS/80 Version 2. NEWDOS/80 Version 2, with two exceptions, CANNOT, repeat, CANNOT operate with TRSDOS Model III system or data diskettes. Please believe us; this is so!!! DO NOT ATTEMPT to use Model III type diskettes (data or system) with NEWDOS/80 except for the special conditions of COPY and SUPERZAP wherein PDRIVE TI flag M is used!!!!! If you must use the DIR command to determine what is on a Model III TRSDOS type diskette, do so under TRSDOS, not NEWDOS.

The directory for Model III TRSDOS system and data diskettes is markedly different from the directory used on Model I TRSDOS 2.3 and all NEWDOS diskettes. For NEWDOS/80 Version 2 on the Model III, Apparat elected to remain with the old style directory so that data diskettes (once the address mark had been adjusted; see WRDIRP command and SYSTEM option BN) could be used interchangeably between the Model I and Model III under NEWDOS/80 Version 2 on both computers.

Most programs generated for Model III TRSDOS will operate under NEWDOS/80 Version 2. Try each program out using replacable data before using valued data. If in doubt, ask your program vendor.

Realizing that data files and program files must be transferable between TRSDOS Model III type diskettes and NEWDOS/80 Version 2 type diskettes, NEWDOS/80's COPY command, formats 1 - 4 and 6, allow, via special PDRIVE conditions, files to be copied from a Model III TRSDOS type diskette to a NEWDOS/80 Version 2 type diskette and from a NEWDOS/80 Version 2 type diskette to a Model III type diskette (note, COPY formats 1 and 2 filespecs for Model III TRSDOS files must have an explicit drive number). The special PDRIVE state is given in PDRIVE, example 3, page 2-38, and provides only for Model III TRSDOS type diskettes that are single sided, double density, 40 track. On your master Model III NEWDOS/80 system diskette, PDRIVE display slot # 4 was initialized to the correct value to use with these Model III TRSDOS 1.3 type diskettes (see zap 008 for TRSDOS 1.2 or 1.1 diskettes; see zap 025 for Model I TRSDOS 2.3B diskettes). For the remainder of this discussion, we will assume PDRIVE specification 4 contains the following values:

TI=AM,TD=E,TC=40,SPT=18,TSR=3,GPL=6,DDSL=17,DDGA=2

There are many variations available for copying to/from Model III TRSDOS diskettes which the more experienced NEWDOS user will adapt for his/her own uses. The following examples are to get the novice through the first anxious moments.

1. To copy file XXX/DAT from a Model III TRSDOS type diskette to a preformatted NEWDOS/80 Version 2 diskette, the following command will work: COPY,XXX/DAT:0,XXX/DAT:1,SPDN=4 NEWDOS/80 will ask for the mount of the source diskette (the Model III TRSDOS type diskette) and the system diskette (the NEWDOS/80 system diskette) on drive 0 as necessary.

2. To copy multiple files from a Model III TRSDOS type diskette to a previously formatted NEWDOS/80 type diskette, the following command will work: COPY,0,1,,NFMT,CBF,CFWO,SPDN=4 NEWDOS/80 will ask for the mount of the source diskette (the Model III TRSDOS type diskette) and the system diskette (the NEWDOS/80 system diskette) on drive 0 as necessary. The user will be asked, one file at a time, which files are to be copied, except that files marked as system files are excluded automatically from the copy. To copy a system file, use the single file copy example above.

3. To copy file XXX/DAT from a NEWDOS/80 Version 2 diskette to Model III TRSDOS diskette, the following command will work: COPY,XXX/DAT:1,XXX/DAT:0,DPDN=4 NEWDOS/80 will ask for the mount of the destination diskette (the Model III TRSDOS type diskette) and the system diskette (the NEWDOS/80 system diskette) on drive 0 as necessary.

4. To copy multiple files from a NEWDOS/80 type diskette to a previously formatted (under TRSDOS) Model III TRSDOS type diskette, the following command will work:

COPY,1,0,,NFMT,CBF,CFWO,DPDN=4

NEWDOS/80 will ask for the mount of the destination diskette (the Model III TRSDOS type diskette) and the system diskette (the NEWDOS/80 system diskette) on drive 0 as necessary. The operator will be asked, one file at a time, to select which files are to be copied, excepting that any files marked as system files are automatically excluded from the copy. To copy a system file, use the single file copy example given above.

NEWDOS/80 Version 2 does not provide a method of copying to/from DOS's other than itself and TRSDOS. It is our intention that the TRSDOS diskette remain the common media for moving data between non-TRSDOS DOS's which is why we took the extra trouble to be able to copy TO a Model III TRSDOS diskette.

For the experienced user, SUPERZAP modes DD and DTS can be used to inspect Model III TRSDOS type diskettes provided the PDRIVE specifications are set correctly. The command

PDRIVE,0,1=4,A

will activate the drive #4 specifications as drive #1's specifications, thus allowing SUPERZAP to inspect a Model III TRSDOS type diskette on drive 1. When done, don't forget to change the PDRIVE specifications for drive 1 back. The Model III TRSDOS directory is 18 sectors long, starting at relative sector 306; remember, the directory format is different than that for NEWDOS/80.

Model I: ZAP 072

Information zap on Model I TRSDOS 2.3B and higher diskettes. Refer also to ZAP 025.

Some time ago Radio Shack announced a double density modification to the Model I TRSDOS. To date, this modification is not available and Apparat does not know what zaps will have to be issued to operate with the new Model I TRSDOS 2.3B or higher double density diskettes. We assume that the new Model I TRSDOS will continue with the implementation of RBA format in the FCBs and the directories (which make the new TRSDOS diskettes incompatible with the old TRSDOS and with NEWDOS diskettes), and that like Model III TRSDOS diskettes, the new Model I TRSDOS diskettes will useable with NEWDOS/80 Version 2 only with COPY and SUPERZAP (see above zap) when the PDRIVE setting includes TI flag M. However, for now, use of flag M does not allow access to Model I TRSDOS double density diskettes as a TD code for double density implies Model III.

Model I: ZAP 073

Mandatory zap to CHAINBLD/BAS to eliminate an unintended and non-displayed CLEAR character that causes trouble during PRINT of an ASCII copy of the program. This character is non-displayed but is the character in text immediately following the GOSUB36 of line 92. Load the program under BASIC, delete the character, and SAVE the CHAINBLD/BAS file back. Line 92 should display exactly the same after the character delete as before.

Model I: ZAP 074

Mandatory zap to BASIC to correct memory-wipe-out error caused in certain circumstances by a REF= statement containing a ' character. The actual error is at 1A8B - 90 in the ROM and can be triggered in non-disk BASIC by keying in twice the direct command sss' where sss is three spaces. By making a change to NEWDOS/80's BASIC, the problem with REF is avoided.

Model I: ZAP 075

Mandatory zap to Microsoft's FORTRAN sold by Radio Shack as Catalog # 26-2200 (EDIT/CMD version 2.02, L80/CMD version 3.43, F80/CMD version not specified) to run with NEWDOS/80 Version 2 on the Model III (and no longer with TRSDOS 1.3). This change deals with the insert-default-extension vector being 4473 in NEWDOS as opposed to being 444B in TRSDOS. User having other versions can search the EDIT/CMD, F80/CMD and L80/CMD modules using the SUPERZAP display mode command L,CD,4B,44 to find the occurrences of this call.

Optional zap to allow COPY formats 1, 2, 3, 4 and 6 to copy files from or to Model I TRSDOS 2.7DD double density diskettes when the PDRIVE for that diskette is: TI=xM,TD=E,TC=tc,SPT=18,TSR=3,GPL=6,DDSL=dt,DDGA=2 where:

TI=xM,TD=E,TC=tc,SPT=18,TSR=3,GPL=6,DDSL=dt,DDGA=2

x = A for the standard Radio Shack disk controller, and D for Apparat's disk controller.

tc = diskette track count, 35, 40 or whatever. This track count includes the single density track 0.

dt = the directory track number (the standard is 17). NEWDOS/80 must be given the correct value as it does not obtain the value from the diskette's boot sector in the single density track 0.

See example 3, page 2-38. If ZAP 008 is applied to the diskette receiving this zap, ZAP 008 must be taken out before this zap is applied. Once this zap has been applied, the zapped diskette cannot be used to copy to/from Model III TRSDOS diskettes or to/from Model I TRSDOS 2.3B diskettes; this zap should only be applied to a special NEWDOS/80 system diskette whose sole function is to be used when copying files to/from Model I TRSDOS 2.7DD double density diskettes.

A Model I TRSDOS 2.7DD double density diskette cannot be formatted by NEWDOS/80, and it cannot be format 5 copied by NEWDOS/80, not even via the BDU option. Further, remember, format 6 (CBF) COPY does not copy system files to/from TRSDOS diskettes; formats 1 through 4 do, however.

Users must be aware that Model I TRSDOS 2.7DD double density diskettes are written with track 0 in single density and all other tracks in double density; the directory information assumes track 0 is in double density and counts its information from track 0's 1st sector. Note, that track 0 is allocated on all diskettes to BOOT, a file that contains 10 sectors, not 18.

Model I: ZAP 078

Mandatory zap to DOS to correct error occurring when a file with EOF = 0 is copied (via single file COPY) to a NEWDOS/80 diskette from TRSDOS diskette other than the old TRSDOS 2.3 (or as now being called TRSDOS 2.3A) diskettes.

Model I: ZAP 079

Mandatory zap to NEWDOS/80's ASPOOL program to correct error in the *ASP,S function where the computer is forced to DOS READY after the remaining spooled print completes printing. Instead, the delayed completion of the function should simply continue the interrupted program. To make room for this correction, the SPOOL PURGED message is no longer displayed. To determine that the spooler is gone, simply execute the *ASP command asking for spooler status. If the response is FILE NOT IN DIRECTORY, the spooler is gone.

Model I: ZAP 080

Mandatory zap to LMOFFSET to correct error where the first program is stored with a disable-DOS appendage and the second program is stored with an appendage that does not disable DOS. This error causes the 2nd stored program to have a bad appendage.

Model I: ZAP 081

Mandatory zap to Radio Shack's Model III SuperSCRIPSIT to enable it to work with the Model III NEWDOS/80 Version 2:

1. Allow the Main Menu Directory function to work with NEWDOS/80. An actual NEWDOS/80 directory is executed via DOS-CALL; so the display will look different from that for TRSDOS.

2. Allow the program to determine the number of 1024 byte page units of diskette space are available on the target drive. To do this, the DOS command DIR x,/Q9Q (where x is the drive #) is executed via DOS-CALL as NEWDOS/80 does not have the RAMDIR function. This causes an extra directory display to appear for during Main Memory function 0 that opens a document (appears after you have adjusted the document control data). This extra directory display may also appear at other times.

This zapped SuperSCRIPSIT must only be used with NEWDOS/80 Version 2 for the Model III.

With SuperSCRIPSIT, users may use DOS functions DFG (MINI-DOS) and 123 (DEBUG), but they must be very careful when pressing the three keys as SuperSCRIPSIT is likely to receive one or more of them. When a page of text is displayed, using the control-H command (HELP) puts the users where DFG or 123 may be pressed. Upon executing DOS command MDRET (to exit Mini-DOS back to SuperSCRIPT) or DEBUG command G (to exit DEBUG back to SuperSCRIPT), press BREAK to return to the page. If HELP was not available, you will additionally have to press control-T followed by BREAK to get back the full display. From the main menu, use option D to display a directory; then while the program is awaiting BREAK, you can press DFG or 123. WARNING!!!! Do not exit directly to DOS from Mini-DOS or DEBUG without giving SuperSCRIPSIT its chance to write data from memory and close its files; this can be disastrous to your document file.

Model I: ZAP 083

Mandatory zap to Model III SCRIPSIT Version 3.2 to enable it to run with NEWDOS/80 Version 2.

Information zap.

1. Most users are still puzzled about using multi-dimension arrays with BASIC's CMD"O". Please refer to section 7.21 in the manual and ZAP 32.4. CMD"O" was intended for single dimension arrays only, but it was found that a multi-dimension array could also be sorted if the user understands that the arrays items sorted (directly or indirectly) actually occupy consecutive memory locations (as assigned by BASIC during execution of the associated DIM statement) starting with the element specified in the CMD "O" statement. For single dimension arrays, this is the same order as ascending order of subscript, but for multi-dimension arrays, the order of elements used in the sort is COMPLEX and is given by the REN formulas. If you are going to sort a multi-dimension array, it is highly recommend that the sort start with the array's first element (i.e., the array's item specified in the CMD"O" statement should have all zero subscripts (i.e., A(0,0,0) for a 3 dimension array)). If you use anything other than zero subscripts for the sort of a multi-dimension array, you must be very clever to figure out which elements actually participate in the sort.

The REN formulas given on pages 7-14 and 7-15 show how to compute the REN for a given element in the array. Following are the formulas for computing the element subscripts corresponding to a given REN value (remember, the first REN value is zero).

1. For a single dimension array whose DIM statement is DIM A(R1) and for array element A(X1):

X1 = REN

2. For a two dimension array whose DIM statement is DIM A(R1,R2) and for array element A(X1,X2):

REN/(R1+1) gives a quotient that is X2 and a remainder that is X1.

3. For a three dimension array whose DIM statement is DIM A(R1,R2,R3) and for array element A(X1,X2,X3):

REN/((R1+1)*(R2+1)) gives a quotient that is X3 and remainder M2

such that M2/(R1+1) gives a quotient that is X2 and a remainder that is X1.

For an n dimension array (where n is not 1) the calculation involves REN being divided by product of all the ranges (a range is 1 greater than the value given in the DIM statement) except the nth, giving a quotient that is the nth subscript and a remainder that can be used as the REN value for calculating n-1th subscript as if the array had only n-1 dimensions. Continue this loop until n is reduced to 1.

2. Manual correction for ATTRIB, section 2-3, page 2-4. Place a note there to indicate that parameter LRL=lenl exists, allowing the user to alter the Logical Record Length of the file to the value lenl (1 to 256). This value, kept in the file's FPDE in the directory, is hardly ever used except by DIR, but some people want DIR to show the correct value. Remember, in NEWDOS/80 OPENs of a file, the LRL value is taken from register B rather than from the directory (in BASIC, it comes explicitly or implicitly from the OPEN statement).

Model I: ZAP 084

Mandatory zap to DOS to correct error that was allowing a format 5 COPY to occur when both diskettes had the same number of sectors but different GPL values.

Model I: ZAP 085

Mandatory zap to EDTASM to correct error where an error flag was not being reset after failure of a file open, thus causing the next file operation to fail to CLOSE a file properly.

Model I: ZAP 086

Mandatory zap to BASIC to correct error in CMD"O" direct sort where an array is specified twice in the command sequence (i.e., two parts of a string supply independent sorting criteria.

Model I: ZAP 087

Mandatory zap to EDTASM to disable a faulty attempt to keep the drives rotating which was actually causing the drive motors to stop. A number of users had complained of this, and finally a user from Australia showed us a disassembly of exactly what was wrong.

Model I: ZAP 088

Mandatory zap to Radio Shack's Model III SuperScripsit Version 1.1 to enable it to work with the Model III NEWDOS/80 Version 2. This zap is identical in function to ZAP 077 for SuperScripsit 1.0.

Following is an optional zap which will correct the SuperScripsit display to read NEWDOS instead of TRSDOS.

Mandatory zap to BASIC to (1) correct error where an RBA exceeds 8,388,607 (uses the 24th bit) and (2) to extend the allowable range for record numbers from 1 - 32767 to 1 - 16777215 (even though the file itself is limited to 16 million bytes). The extension of the record number range was needed as FF and MF processing using RBAs was generating bad record number errors when BASIC converts the RBA to record number to assure that the RBA was on a record boundary and the resulting record number was greater than 32767. This zap is especially important to NEWDOS/80 2.5 users.

Model I: ZAP 089

Information zap. For those users with the Hard Disk Operating System NEWDOS/80 Version 2.5, be sure to apply zaps separately to each of NEWDOS/80 Version 2.0 and to NEWDOS/80 Version 2.5. Do NOT just apply the patch to one of the two systems and copy the module over to the other as you may eliminate some 2.5 zaps or end up applying some 2.5 zaps to 2.0, which can be disastrous. If a zap applies only to Version 2.0 or only to Version 2.5, we will state such; otherwise, the zap applies to both systems.

Model I: ZAP 090