June. 1985
1. Log into DSKO:[1,2].
2. Copy all of the files from your AMOS/L 1.3 release medium to your System Disk, DSKO:, using the appropriate copy or restore commands. Make sure that you copy all files to their proper accounts. For example:
or:
or:
or:
.COPY DSKO:[) = HWK1:[]
. VCRRES DSKO:[]
=
ALL:[].STRRES DSKO:[]
=
ALL:[].TAPFIL DSKO:[J
=
ALL:[)3. Integrated systems and bootable media are shipped assuming that the Opera-tor Terminal uses the ALPHA. TDV terminal driver configured for an Alpha Micro AM-SO terminal. If under your previous AMOS/L version you used the COPY command to reconfigure ALPHA.TDV to contain a driver for a non AM-SO terminal, you must remember to use COpy to reconfigure ALPHA.TDV again for your non AM-SO terminal since you have just copied over your old ALPHA. TDV with the AM-60 version supplied with AMOS/L Version 1.3. See Section 5.1 for information on configuring the ALPHA.TDV terminal driver.
AMOS/L 1.3 RELEASE NOTES
Page 23 If you change the contents of ALPHATDV, do not forget to disable the ALPHA translation tables by renaming them to some other name. Do NOT use the name of a terminal driver, since this will confuse the application software prod-uct into thinking that the translation table applies to that terminal.Remember that these translation files apply only to the AM-60 terminal. We suggest renaming all translation files to a name not likely to be used as a terminal driver name. For example:
.RENAMEID TRNS60.VUX
=
ALPHA.VUXThe translation files currently available are: DSKO:ALPHAVUX (AlphaVUE);
DSKO:ALPHAWRX[7,12] (AlphaWRITE; supplied with AlphaWRITE product);
and DSKO:ALPHACAX[7,13] (AlphaCALC; supplied with AlphaCALC product).
Other translation files may be made available with future software products.
DO NOT reboot your system until you have reconfigured ALPHA.TDV and any translation files.
4. Reboot your system by pushing the Reset button.
5. before you do anything else, you should use the AMOS/L 1.3 software to generate a new disk driver for your System Disk and incorporate it into the monitor:
a. Log into DSKO:[1,6] and make new copies of your disk and device driv-ers. For example:
.COPY SMD.DVR
=
SMD410.DVR .COPY HWK.DVR=
HWKSOO.DVR .COPY VCR.DVR=
610DVR.DVR .COPY STR.DVR=
620DVR.DVRUse the FIX210 command to generate new drivers for all floppy disk drives that run under the control of a Floppy Disk Controller.
Use the FIX420 command to generate new drivers for all Winchester disk drives.
OSS·10125-00, Rev. AOO
Page 24
June,1985
AMOS/L 1.3 RELEASE NOTES
b. Log into DSKO:[1,4) and use the MONGEN command to incorporate your DSKO: System Device driver into your new AMOS/L 1.3 monitor.Use the name TEST.MON for the new monitor. For example:
.MONGEN
Input new monitor: AMOSL.MON New disk driver name: PLD.DVR New language Definition Table Name:
New monitor name: TEST.MON Now, save the new monitor to the disk:
.SAVE TEST.MON
6. Log into DSKO:[1,2) and use the MONTST command to boot from the new monitor:
.MONTEST TEST.MON,AMOSL.lNI
7. If the test monitor comes up fine, log into DSKO:[1,4] and rename the file to AMOSL.MON:
.RENAME/D AMOSL.MON
=
TEST.MON8. Push the Reset button to reboot your system. You are
now
up and running with an AMOS/L 1.3 monitor, system initialization command file, and system software.9. Remember to use the AMOS/L 1.3 WRMGEN command to generate new warm boot monitors for your boatable 1/2" magnetic tapes, video cassettes and 1/4" streamer tapes. (And be sure to include CMDLlN.SYS and SYSMSG.USA on your warm boot tape.)
WARM BOOT MONITOR WARNING
Many people who build warm boot tapes routinely include the CRT420 pro-gram so that they can recertify Winchester disks that run under the control of the AM-420 disk controller or t~at are contained in AM-1000 series systems.
Certifying a disk is always a last resort. You should NEVER recertify a disk unless you see repeated error messages indicating: 1) the BADBLK.SYS file for that disk is no longer on the disk; OR, 2) hard device errors make areas of the disk inaccessible.
Winchester disks you receive from Alpha Micro already have been fully tested and certified at the factory using sophisticated testing procedures not feasible for use in the field. If you certify a disk drive, that drive may be marginally less reliable in its handling of media flaws than when it arrived from Alpha Micro because the BADBLK.SYS file created when you certify may be different from the optimum one created at the factory.
AMOS/L 1.3 RELEASE NOTES Page 25
The AMOS/L 1.3 CRT420 has been modified. You MUST include. both CRT420.LlT and XXXCRT.LlT in your AMOS/L 1.3 warm boot monitor when creating a warm boot tape that you think you will need to use in the future to certify an AM-420 or AM-1000 disk drive.Before you create a warm boot tape that will allow you to certify a disk drive, be sure to save a copy of that disk drive's BADBLK.SYS file under another name on removable media so that you can restore that file after certifying the drive. This avoids deleting the optimum, factory-created BADBLK.SYS file. For more information on this procedure, contact your dealer or the Alpha Micro Service Division.