System information

11. Upon completion of step 10, CP/M has prompted the console for a command input. To
test the disk write operation, type
SAVE 1 X.COM
All commands must be followed by a carriage return. CP/M responds with another
prompt after several disk accesses:
A>
If it does not, debug the disk write functions and retry.
12. Test the directory command by typing
DIR
CP/M responds with
A:X COM
13. Test the erase command by typing
ERA X.COM
CP/M responds with the A prompt. This is now an operational system that only requires a
bootstrap loader to function completely.
14. Write a bootstrap loader that is similar to GETSYS and place it on track 0, sector 1, using
PUTSYS (again using the test disk, not the distribution disk). See Sections 6.5 and 6.8 for
more information on the bootstrap operation.
15. Retest the new test disk with the bootstrap loader installed by executing steps 11, 12, and
13. Upon completion of these tests, type a CTRL-C. The system executes a warm start,
which reboots the system, and types the A prompt.
16. At this point, there is probably a good version of the customized CP/M system on the test
disk. Use GETSYS to load CP/M from the test disk. Remove the test disk, place the
distribution disk, or a legal copy, into the drive, and use PUTSYS to replace the
distribution version with the customized version. Do not make this replacement if you are
unsure of the patch because this step destroys the system that was obtained from
Digital Research.
17. Load the modified CP/M system and test it by typing
DIR
CP/M responds with a list of files that are provided on the initialized disk. The file
DDT.COM is the memory image for the debugger. Note that from now on, you
must always reboot the CP/M system (CTRL-C is sufficient) when the disk is removed
and replaced by another disk, unless the new disk is to be Read-Only.
6.2 First-level Regeneration CP/M Operating System Manual
6-5