CMOS.COM is a simple program (312 bytes long) to save contents of your CMOS
to a file. It is here for you to test a script called CMOS.SCP.

This utility is not distributed in a COM file, rather it is saved as a
stream of hex bytes and strings in a file called CMOS.PAT. You must process
this file by PBT in order to obtain a COM file. The command to create this
file is as follows:
PBT P ++CMOS.COM @CMOS.PAT

As you see, we use the P command of PBT to create the COM file. In all
versions of PBT prior to 1.64, we used only one plus sign in the file name
and PBT created it only when necessary. But since 1.64, we have the
possibility to force PBT to create the output file. It ensures that your
new copy of CMOS.COM is clean. If you, for example, copied another file like
PBT.EXE into CMOS.COM before, PBT would overwrite first 312 bytes but the
file would be still very large and in some cases, you wouldn't be able to
run it due to its size (COM files must be 64K in size or smaller). I know
this example is rather stupid, but illustrative.

Since version 1.60, PBT has the ability to compile patch streams. You can
test this feature by issuing the following command:
PBT PM CMOS ++CMOS.COM @CMOS.PAT
As of version 1.93 of PBT, you can do the same thing by using the auxiliary
batch file called COMPILE.BAT as follows:
COMPILE /P CMOS ++CMOS.COM

These commands do not patch (or in this case, create) a .COM file. Instead,
they create an executable file called CMOS.EXE, which in turn creates the
CMOS.COM file when run.

You might ask why you must process the CMOS.PAT file. Well, I wanted to make
a little script file for the P command but had no idea for it. Furthermore,
this is the best way to show you that PBT's scripting works in the P
command, too.

