For keyboard interface on I/O Multi board. Default is disabled. Requires interrupt #2 jumper set on I/O Multiboard, which is pin 11-12 in P5. Has limitations around port settings. Do not have a video card on my Duo so have been forcing a video driver to load and testing with PIP CON:=UR2: . Let me know what you think.
During testing of the NVRAM Switch changes (#451), I found some pre-existing stuff I didn't like, so I have tried to clean things up.
- BOOT_DEFAULT has been replaced by AUTO_CMD
- There is no longer a "default" boot loader command when pressing <enter>.
- An additional SD Module has been developed by Stephen Cousins. Since this module will be distributed as a kit, I think it makes sense to enable support by default. It will do nothing on systems without an SD Module.
- Per Mark Pruden, corrected NZCOM user area specification for CP/M 2.2 files.
- Added some DRI files to CP/M 3 that are documented in the CP/M 3 documentation (LIB, LINK, MAC, RMAC, XREF). They are duplicated in CP/M 2.2 image, so this should be reviewed at some point.
- Added XREF to CP/M 2 disk image for consistency with CP/M 3.
- Updated Catalog.md per Mark Pruden to eliminate obsolete column from table.
- WRERR was putting the CAN character in register C to send. However, it needs to be in register A. Fixed here. Credit and thanks to HubertH for finding this and providing the fix.
- Added "Character Device Mapping" sub-section to each of the Operating System sections of the User Guide. This attempts to clarify how character devices will appear within the different operating system environments.
- Generate a disk image "catalog" file for each disk image generated during build. This simply helps confirm what files wound up on each disk image and the space used/free.
- Make the CP/M 2.2 files added to NZCOM and ZSDOS consistent.
- Restore copying PIP application to ZSDOS and NZCOM disks.
- The floppy version of some supplemental disks were not being generated due to a typo.
- The ReadMe.txt file for some supplemental disks was not being added to the disk.
- The file sort order being forced in the disk image generation process was causing a problem with achieving binary exact build results. Not sure why it was the way it was, but corrected now.
- Move SALIAS and related files to Common/Z3
- Move ALIAS and related files to Common/Z3
- Remove Source/ZSDOS/Distribution folder because the files were duplicated in the ZSDOS disk image
