1-Sep-86 13:09:55-MDT,2017;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 1 Sep 86 13:09:44-MDT Received: from uci-icsc.arpa by AMSAA.ARPA id a009720; 1 Sep 86 14:43 EDT Received: from localhost by ICSC.UCI.EDU id a020179; 1 Sep 86 11:43 PDT To: Dave cc: info-cpm@AMSAA.ARPA cc: young@uci-icsc.ARPA Subject: Re: kaypro 10 schematics In-reply-to: Your message of 29 Aug 86 20:49:58 GMT. <268@killer.UUCP> Date: Mon, 01 Sep 86 11:42:45 -0800 From: Michal Young Micro Cornucopia sells three varieties of Kaypro schematics, for $20 each, with a theory-of-operation keyed to schematic. - Kaypro II & 4 (pre-84) - Kaypro 10 (without modem) - Kaypro 2, 4, 10 (84 series) Schematics are on a single 24" by 36" sheet. They include serial and parallel port details and programming examples, and other nitty-gritty details that is hard to find elsewhere (e.g., how the Kaypro II bios switches between video and main ram banks). I have both the Micro-C schematic for Kaypro II, and a bootleg copy of the dealer's manual and schematic. The Micro-C version is a lot better than what Kaypro provides dealers. Address: Micro Cornucopia P.O. Box 223 Bend, Oregon 97709 Phone: (503) 382-5060 (9am to 5pm, PST) They take Visa and Mastercard, and prices include postage. I've ordered from them by phone, and got good fast service. They also have a technical help hot-line, the number of which I don't want to broadcast to the net, but you'll find out about it if you decide to buy a schematic from them. I've called the technical hotline and gotten good help on tracking down a hardware problem. In summary, this organization is a good resource to people with Kaypros (also Big Board homebrew systems, and Xerox 820 series.) I have no connection with Micro C, other than as a satisfied subscriber and customer. --Michal Young University of California, Irvine young@ics.uci.edu 1-Sep-86 14:37:20-MDT,46496;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 1 Sep 86 14:35:48-MDT Received: from simtel20.arpa by AMSAA.ARPA id a009931; 1 Sep 86 15:15 EDT Date: Mon, 1 Sep 1986 13:16 MDT Message-ID: Sender: KPETERSEN@SIMTEL20.ARPA From: Keith Petersen To: Info-Cpm@AMSAA.ARPA Subject: List of best public domain CP/M programs Norm Gregory, SysOp of Seattle's "Downspout" Z-Node, provides this list of best public domain software for the CP/M user. This list is updated monthly. It is presented here for your information and does NOT in any way indicate that ALL these files are available from SIMTEL20, my RCP/M, or GEnie's CP/M RoundTable. However, many are available from these sources. PD:CPM.CRCLST on SIMTEL20 (the file listing all the filenames, sizes and CRCs of the PD: directories) has been updated as of today. --Keith --cut here--SEPBEST2.LST--cut here-- SEPBEST2.LST is a revised version of SEPTBEST.LST to correct for duplicate entries, bad alphabetical sort, and incorrect end-of-file. No entries have been altered. -- Keith Petersen, W8SDZ -- 9/1/86 0938 edt. -[ Seattle's `downspout' ]- 206-325-1325 300/1200/2400 baud DATE: 09/01/86 TO: All CP/M users FROM: Norm Gregory (SYSOP) This is an alphabetized list of public domain files and programs considered "best" by the users of Seattle's `downspout.' ---- ACMDU11.LBR - ZCPR3 Allows you to add, delete and view aliases in an ALIAS.CMD file without a word processor. ACMDUTIL was written for those of us who write aliases on the fly. V1.1 now searches BASE: rather than ROOT: for the ALIAS.CMD file and takes an optional DU: on the command line to find any copy of ALIAS.CMD. ----- ACREATE3.LBR ACREATE now searches A0: and A15: and DCREATE extracts the command line from an alias file and puts it in a text file for editing. That's right, ACREATE3.COM creates a ZCPR3 ALIAS file from a standard text file. And DCREATE.COM will create a text file from an ALIAS file. The system works well and is fast. (01:52:31 AM Jul 14, 1985) ---- ADIS.LBR - CP/M Matt Wing's Z80 and 8080 disasembler. ---- ALIAS#1.LBR - Z3 The Echelon ZCPR3 newsletters frequently contain sample Alias scripts.... this library contains almost all those which have been published to date, plus a few to come in future newsletters. ---- ARCDIR.LBR - CP/M A utlity to allow CP/M80 users to do a directory of PC/DOS ARC files. A must for BBS systems. [ 06:45:01 AM Nov 21, 1985 ] ---- ARUNZ09.LBR - ZCPR3 ARUNZ now has MENU/VMENU-style user prompts (but better!) and parameters that read Z3 registers and memory locations. If you run a Z3 system and do not use ARUNZ you are missing what is perhaps the best of all Z3 utilities. Store all your alias scripts in one little ASCII text file. ---- ASCII.LBR - CP/M ASCII.COM is for folks with poor memories. Just type in ASCII and press any key. The key and it's HEX code is displayed. ^C to end the program and warm boot the system. [ 12:21:13 AM Dec 07, 1985 ] ---- AUTOZINS.CCP Notes on modifing your copy of ZCPR3 ccp to "autoinstall" all ZCPR3 utilities. Erase ZINS - you won't need it any more. No more hassles with downloading ZCPR3 programs and forgetting to install them. ---- B-COMPIL.LBR - CP/M This is BCBC, CP/M VERSION 1.1, written by Bruce Tonkin. It's a BASIC compiler written using the pbasic pre-processor for Microsoft BASIC 5.2 or higher. BCBC generates assembler source code for ASM or MAC. Intel 8080 opcodes are used. ---- B5C8-2.IQS - RCPM/BBS Finally a BYE5 insert for the Commodore C128 to be used with BYE510 or newer. Thanks to George Peace. ---- BBCAT10.LBR BBCAT is a catalog program integrated with the archive/dater/backup utility BBACK (v6.0) to provide a convenient way of keeping track of backed-up files and of eliminating duplicates. Unlike NCAT, UCAT et al, which are meant chiefly for the floppy-disk user, BBCAT is de- signed primarily for those with hard disks who only use floppies for back-up and storage. ---- BD03.LBR - CP/M Irv Hoff's update to his fine bad sector lockout program. This one reports the file names that have bad sectors, which is what you really want to know. ---- BISHOW32.LBR - CP/M BISHOW32 reads just about any text file, whether or not it is squeezed or enclosed in a library. It allows you to move forward and back in the file by a page or a line at a time. You can scroll horizontally in a file wider than the screen. You can jump back to the top of the file. It uses Wordstar cursor keys, as well as alternates. Fits in 2k ---- BRADFORD.LBR - CP/M Aaron Contorer's Near Letter Quality printer program for Epson and Gemini printers. A commercial package that Aaron is now distributing as Freeware. If you use it, send Aaron $15 and he will send you his manual, which tells you about advanced features. ---- BU14.LBR - CP/M Hard disk back-up, special printer versions in .LBR ---- BWFMT.LBR - CP/M This is for BONDWELL computers, 12 and 12A for sure (maybe 14 &16). These allow formatting disks for Osborne and Kaypro computers. ---- BYE510.LBR - RCPM/BBS BYE5 is the program most RCP/M systems use (for CP/M 2 and CP/M 3) to interface their computer and modem to their local BBS system. This version adds the SYSLOG option which captures all input from the remote user. Other improvements...read BYE5.HQS in the .LBR. ---- CHEFREC.5Q - CP/M More recipes for Chef.com. ---- CHOP.LBR - CP/M CHOP is a little CP/M program written in Turbo Pascal to copy a large text file into a number of consecutive smaller ones which are easier to handle and edit. The new files have numbered extensions (file types). The file will be divided into pieces, each having 128 lines. These can be edited and then re-combined with PIP. Program is very slow and files are quite small, typically 5-8k each (depends on the average line length). ---- CRUNCH12.LBR - CP/M File compression utilities for "squeezing" files using the same algorithms as the MSDOS ARC program. Source code included. ---- DASM16.LBR - CP/M This is Rick Conn's DASM15 now including an include file for Hitachi HD64180 mnemonics. [ 03:10:00 PM Oct 26, 1985 ] ---- DBL4.LBR - CP/M Update of the DBL program for printing two pages on one page with an Epson printer in compressed mode. [ 04:20:52 AM Nov 19, 1985 ] ---- DBUG10.LBR - CP/M An internal debugger for Turbo Pascal programs; sort of a DDT tool. It adds about 600 lines of code in an include file. [ 02:55:24 AM Dec 28, 1985 ] ---- DEARC2.LBR - CP/M Allows a CP/M user to access those 16 bit .ARC files that you see everywhere. The program uses two different decompression algorithyms, the Greenlaw and LZW, depending on the method used to compress initially. ---- DEBUGRCP.AQM - ZCPR3 ZCPR3 Debug facility (same as MU31) in a Resident Command Package. ---- DEMOHLP.LBR - ZCPR3 A demonstration and tutorial on ZCPR3 *.HLP files. ---- DDTZ.LBR - CP/M Replacement for Digital Research DDT.COM, adds search features, etc. ---- DIR1ST31.LBR - CP/M DIRFIRST: Z-80 sorted directory showing first line(s) of files. Latest in the DIRFIRST series (v 3.1). ---- DIRR7.LBR - CP/M Directory file, alphabetizes vertically in an unique manner generally considered to be superior to that of "SD". Type '?' for a help guide to see the various options available. In extended mode, shows system files, R/O and archived files with special characters, making use of reverse video, lower case, etc. superfluous. Can also make hard-copy or a disk file including those attributes. Has several unusual fea- tures you will immediately like. Fixed the 'A' option this version. [ 11:36:24 PM Dec 11, 1985 ] ---- DIRSIZE.LBR - CP/M Utility program for disk directory file count. [ 02:33:31 AM Apr 24, 1986 ] ---- DU312.LBR - Z3 Newest version of DiskUtility from Z-NODE Central. ---- DZ-APR86.LBR - CP/M John Washington's latest update to his DazzleStar. It does NOT replace DZ-FEB86.LBR. It is a supplement, principally advising of a few fixes. ---- DZ-FEB86.LBR - CP/M This is latest version of DAZLSTAR, an interactive Z80 disassembler New version has comprehensive install program, "side-line" comments, active cursor indicator in both ascii and hex fields, and greatly improved menus. Extremely flexible. If you do any disassembly, you need this one. [ 04:54:14 AM Apr 06, 1986 ] ---- EPRO.LBR - CP/M E-Prolog is a public domain prolog interpreter for Z-80 computers. The .LBR file contains the interpreter, a library of logical predi- cates (AND, OR, etc.), some sample databases, assembly language source modules, documentation, and some other things. E-Prolog is a minimal prolog, but it works for constructing databases and inference rules within them. Its main lack is that it won't do even integer arithmetic. It will do disk I/O. ---- EXPRESS1.LBR - CP/M A very fast full screen text editor. EXPRESS v1.0: 1) includes a built in macro key translator and editor; 2) can be installed on any CP/M 2.2 system with at least 48k of memory and a terminal with direct cursor addressing; 3) is not a word processor; 4) is a preliminary and limited implementation, distributed without charge, to introduce users to the potential of the EXPRESS full screen editor from Cecil and Laine Stump of Woodinville, Washington. [ 02:51:25 AM Sep 28, 1985 ] ---- FANFOLD5.LBR - CP/M "Universal" version of Ron Rock's (Chicago) FANFOLD. For those with Turbo- Pascal a small RUN.PAS file chains to FANFOLD.CHN with printer codes supplied by user. START address 2100; END address CB10. ---- FASTMX80.MOD - CP/M Speedup for Epson MX-80 Printers!! [ 06:16:51 AM May 29, 1986 ] ---- FATCAT24.CHG - FATCAT Locations in FATCAT24 to change the "|" delimiter to something your printer can print i.e. a ":". ---- FATCAT24.LBR - CP/M Steve Cohen's (Chicago) update of his marvelous catalog program stamps out bugs in version 2.3 and adds some goodies such as a print to file routine. If you came to the party late FATCAT is the super-duper-disk cataloguer featuring rapid-fire disk insertion, with tedious catalog updating taking place after all disks entered; also library file support and a screen-oriented "Cleanup" mode in which files can be erased or renamed before being catalogued, and also disk-name files can be added in this mode. ---- FBAD60.LBR - CP/M Finds and locks out bad sectors on a CP/M-80 disk. Finally it will now run under CP/M Plus as well using included RSX. Instructions on how to implement version for CPM Plus are included. ---- FILT7A.LBR - CP/M A multi-purpose filter program for text files, WordStar files or as- sembly level source code files. Menu-selection. Removes all tabs or optionally puts tabs at all optimum locations. This version checks for space breaks and soft-hyphens before looking for unwanted control characters. Very fast, when done shows a summary of what it found. 7k, 54 records. ---- FINREP22.LBR - CP/M Eric Gans' (French Department, UCLA, Los Angeles, CA) FINd and REPlace V2.2 which adds "V" flag to allow user verification ("Replace (y/n)?") before replacement in text files. FINREP is a search/replace program that remedies most of the deficiencies of Wordstar's ^QA and other similar commands. Aside from being faster, it has important additional features: - allows wildcards in search string (v2.0) - allows wildcard filename (find/replace in groups of files) - command-line entry allows batch processing by SUBMIT, etc. - allows entry of control or hex characters (0-FF) - can be used with object files (e.g., COM files) - sets capitalization (first letter or whole word) and high bit of the last character according to the old string This last feature means that, for example, if you are writing a scenario where the characters' names appear sometimes in CAPS and sometimes just Capitalized, you don't need two search/replaces to replace one name with another: JOE will be replaced by HARRY, Joe by Harry, and even joe by harry. ---- FRONT50.LBR - CP/M Latest update of FRONT, a program that replaces the usual CPM A> prompt with a menu. ---- FT.LBR - CP/M A quick, dirty, and tiny text file creator. Type FT FILENAME.EXT and start typing. Two 's closes and saves file. [ 03:50:10 AM Oct 25, 1985 ] ---- FU-12.LBR - CP/M File Utility is a full screen binary file editor. Cursor functions pretty much follow WS commands. Also includes a windowed full function calculator for binary, hex, and decimal interger. And takes up less memory than PATCH, which is great for use small TPAers. Great hacking tool!!! ---- FUNKY12.LBR - CP/M Allows you to program your terminal's function keys, either interactively or from a disk file. This version includes the ability to embed control characters and escape sequences. ---- GKEY2.LBR - CP/M Gans' key enhancer generalized for all CP/M machines (2.2 at least). Smaller than SMARTKEY, allows redefinition of ESCAPE sequences. use a little beta-testing on machines other than the Kaypro. ---- GTXT11.LBR Makes a text file into a .COM file. V1.1 update: - exit via ^C. - zeroes high bit to read (say) WS doc mode files - allows printing of control characters using "^" (thus ^Z entered in the text will blank the screen when the COM file is run.) - page breaks can be forced with "~" However, a "[More]" is issued every 23 lines without you having to add "~" to the text; when you type a character the [More] is blanked out and doesn't waste a line on the screen. (12:40:38 AM Jun 25, 1985) ---- HELP53.OBJ HELP is version 5.3 of HELP for ZCPR3. The version adds automatic unsqueeze, so when you issue a command like "HELP topic", HELP will search for topic.HLP or topic.HQP along the path and in the HELP: directory, and, when found, will load and unsqueeze as necessary. The tradeoff is space vs speed - squeezed files take less space but more time to unsqueeze during the load. Once loaded, there is no difference in processing HLP/HQP until next load. ---- HIPPO11C.LBR - CP/M Vastly improved release of Happy Investor's (tm) Personal Portfolio Organizer. Bugs fixed, more convenience, and capacity expanded to 5 securities and 10 purchases in this free version of HIPPO (tm). ---- HSH15.LBR - ZCPR3 History SHell. Allows recall and editing of previous command lines. Version 1.5 corrects a serious bug in handling entry of long command lines and allows installation of the prompt string. ---- IMP244.LBR - CP/M Modem program that has 1k protocol, automatic step-down for 2400 bps modems and KMD-batch mode as well as MODEM7 batch. This version changes the batch header block to work with KMD - stores the file length as two hex bytes at the end of the block. Can now handle files up to 8.2 megabytes, while showing additional information. Also supports the Anchor Mark XII for autodial and is easier to use in terminal mode with Osborne OS-1 computers. Other changes. ---- IMP-OVL.LBR - CP/M Overlays for the IMP modem program, dated 27 Oct 85. See IMP-OVL.LST for a list of those avaiable in this library. [ 02:49:05 AM Oct 30, 1985 ] ---- IMPATCH.LBR - CP/M IMPATCH is a menu-driven program for patching of IMP244 default parameters. Options include either directly patching your version of IMP or writing a new version of IMP containing the changes. The LBR file contains a DOC file with patch points explained. ---- INDEX85.LBR INDEX85 reworking by David Cortesi (Dr. Dobbs, "Inside CP/M," etc.) of his earlier indexing program. This version (no new features, but also no bugs) is now in Turbo-pascal, and is quite elegant. Also very useful for indexing any sort of published or just printed document. It's provided in compiled form for CP/M 80 systems (including a 48k version for us Z-system users), but may be recompiled for MS/DOS, probably without code changes. ---- INDOTCOM.ZQX - ZCPR3 This .zex file will install your default RCP, FCP, NDR, PATH, and WHEEL specifications right into Z3DOTCOM so you don't have to load them each time you boot up unless you change them on the fly. ---- K83ZCPR3.LBR Full implementation of ZCPR3 for older Kaypro II's and IV's (pre-1984 machines without video/graphics enhancements). Fully compatible with the "standard" John Smith implementations for the Kaypro 10 and 484. Gives the user full utility interchangeability without reinstallation with ZCPR3 files (except SYS.ENV) used on Kaypro 10's and 484's. Uses all the Smith implementation addresses. ---- K83Z3UPD.LBR This is a library file which updates the K83ZCPR3.LBR. It contains an updated bios image, the ASM file used to modify bios images, both of which focus on fixing the LISTST bug in the KAYPRO rom. It also contains an alias program which alters one byte in any other alias program so that it can be used as a STARTUP.COM on a 58k TPA Kaypro ZCPR3 system and a .DOC file. [ 04:05:03 AM Jan 23, 1986 ] ---- KISOR.ART - Other Henry Kisor computer column no longer appears in The Seattle Times. This is copy of his last piece. ---- KMD.HQP - CP/M Help file telling how to transfer files with KMD. Beneficial for new CP/M users who are unfamiliar with file transfer protocols. Will hopefully save SYSOPs a lot of time trying to answer individual questions. Even the experienced CP/M user might find the information of interest/value. There are perhaps functions available some users are not aware exist and might find useful to their normal operation. ---- KMD22.LBR - GENERAL CP/M KMD is used by most RCPM systems for handling file transfers to/from the remote user. This version uses Bob Freed's routines which allow downloading member files from an .ARC archive library. It also uses a concept similar to that used for IMP, MDM7 and MEX permitting easy and rapid installation, via a master overlay merged with the object code file. This permits a modest sized library. 33k, 259 records. ---- LABELG10.LBR LABELG10.LBR is a Turbo Pascal file that can be used to create Multiple Labels, store label information to disk, write to list Disk Labels, and finally act as a MailMerge-type creator of a form letter and the appropriate address label file. A COM file is included that will run on any CP/M-type system. All source files are also included. ------ LASM3.LBR This is an enhanced version of Pete Mack's LASM assembler which was it- self an improved version of Ward Christenson's LINKASM assembler. All of the Z80 op codes have been added in the style of the 8080. Also the symbol cross reference (requested by the XREF directive) will now be printed on the console if the normal listing has been directed there (the previous version only generated the XREF listing if the normal listing was directed to a .PRN file). ---- LRUN23.LBR Slight improvement over the already-good LRUN22. Program now shows the bad command, with an LRUNZ-style error display, if it's not in the default or selected LBR. (03:09:56 AM Jul 11, 1985) ---- LSTOOL11.LBR - CP/M Jim Gronek's utility program designed to extend the usefulness of the MCAT/XCAT or LCAT/XLCAT Disk Cataloging System. LST-TOOL can read the .LST files produced by XCAT/XLCAT and report useful information on them back to you. V1.1 utilizes a technique to automatically determine available memory at run-time. ---- LUZ3.LBR ZCPR3 library tools. LGET to extract and optionally unsqueeze files from a library, LLF to display files in a library, LX to run files from a library, LHELP to process HLP/HQP files in a library. From Rick Conn. ---- M80VMN.DOC - ZCPR3 Examples of what can be done with Z3's MENU, accessing editor, assembler, debugger, help system for writing programs with syslib. Sure beats the L80 command line. [ 06:00:55 AM Nov 09, 1985 ] ---- MACPRINT.LBR - CP/M Public domain fancy printing program that really does enhance Epson compatibles! -- Triple height, "MAC" style characters from a standard ASCII text file or the keyboard, runs under CP/M, and as the signon warns, don't hold your breath if you're running it on floppies! ---- MAKBATCH.LBR - CP/M Fast, easy way to create and execute submit-like commands, without submit.com or the need for an editor. Instead of a secondary .sub file you get a primary .com file, ready to go. [ 06:11:25 AM Oct 16, 1985 ] ---- MBINDX.LBR This program produces an index of the variables and reserved words used in a MBASIC program file. The file to be indexed MUST be saved in the 'A' (=ASCII) mode. ---- MEMCOM.LBR These programs establish a virtual "ram disk", drive "E:", of various sizes, using space from TPA. All that one must do is execute one of the MEMx.COM programs within this .LBR and a virtual disk will be created. All subsequent references to "E:" will deal with the ram disk. It appears that once installed, the only way to remove the ram disk is to reboot the system. ---- MENU40.LBR Joe Wright reworks MENU. Many interesting new features, such as a 'default' command on each menu, recognition of the quiet flag, better handling of default directory, and more. Anyone volunteer to do a new .HLP file? The changes are described more fully in the source code comments. Also, try the included DEVMENU.MNU for a taste of what can be done with this new version. ---- MEX114-U.LBR (20 July 1985 Ron Fowler/NightOwl Software, Inc.) This release repairs several bugs reported in version 1.12, and adds support for 1k XMODEM file transfer packets. ---- MEXIT110.LBR - RCPM/BBS MEXIT version 1.1 is Kevin Murphy's newest MEXIT/MUT library. A MUST for any METAL/Z-MSG BBS system. Now supports the new features in KMD 11 or later so that you may select a ratio of downloads to uploads and disallow downloads if the ratio is exceeded. The user is informed of this status. Also MUT109 has a new feature to allow a data file output from the USERS file, tag selectable. ---- MCOPY43.LBR Latest revision to MCOPY. Adds the 'N' or 'no replace' option which AUTOMATICALLY refuses to copy when the file exists already in the destination disk/user. Handy in aliases for setting up ramdisks on cold boot -- mcopy43 c15:=a15:*.* N, for example, will only do the copy if the file isn't already on the Ramdisk. ---- MKLINE.LBR - ZCPR3 CP/M and ZCPR3 utility that will insert file names into a line of text and write them out to a disk file for use with ZEX or SUBMIT. Wildcards are allowed for multiple lines. Read the .INF or .DOC file for more information. Written in BDS C ver 1.50a. Source and .COM file included. jwm ---- MKRCP1.LBR All the tools (except MAC.COM) you need to make Resident Command Packages for your Z3 system. ---- MLOAD24.LBR Multi-file Hex Load Utility for CP/M. MLOAD replaces the old CP/M LOAD and elminates the need for the 'SAVE' command. Read the preface in MLOAD24.ASM for usage and details. ---- N41.LBR A very useful and easily used program that converts numebers to hex, binary or decimal. Can also use Boolean arithmetic. Almost any computer user has needed to convert hex addresses to decimal or vice- versa. Source code and an interesting .DOC file included. Assembly level code. Should run on any CP/M-80 system. ---- NEWARC.LBR - CP/M David Rand's rewrite of Rubenstein's original programs for archive files. Includes .com files for adding, deleting, sorting directories, running programs from archive, etc. These are faster, take up 10% of the space that the originals did, and have otherwise been improved. ---- NEWRITE7.LBR - CP/M This file is used to print out the files created with TOUR (the PD outline processor). It improves on and replaces WRITEGEN.COM. The Turbo PASCAL source code is included. [ 05:17:19 AM Jun 26, 1986 ] ---- NULU151.LBR - CP/M The BEST Library utility. ---- PASTE2.LBR - CP/M PASTE2 - combines two input files into a third, joining side by side. v1.1 corrects a bug discovered in v1.0 which dropped CRLF when second file expired first. Added option to erase destination file if it exists or abort. Added info on optional [du:]filename.typ to usage message. Originally written in a first wonderful encounter with SYSLIB 3.3! ---- PATCH&GO.LBR - CP/M This is a COM file adaptation of the Z3 POKE&GO technique for non-Z3 systems, or for those whose Z3 implementations don't include the required functions. ---- PBBS03.LBR - RCPM/BBS PBBS v3.0 is used as the BBS program on many RCP/M systems. PBBS is by far the best public domain BBS system in existance, and better than any non-public domain system surveyed. This version adds many new features, including multiple bulletin boards, enhanced ZCPR3 sup- port, 25th status line and much more. Requires BYE508 with a real- time clock installed. Will work on any Z80 based computer. Support files and conversion files in PBBSUP-3.LBR. 211k, 17 min at 2400 bps ---- PBBSFAST.LBR - RCPM/BBS Submit-type utilities for making a fast assembly/linking of the PBBS v3.0 system. 7k, 30 secs at 2400 bps. ---- PBBSUP-3.LBR - RCPM/BBS Support files required for PBBS v3.0. Includes utilities to convert several existing user file formats to PBBS formats, including OxGate to PBBS. 88k, 7 min at 2400 bps. ---- PBBSUSR1.LBR - RCPM/BBS Offline utilities for the Sysop to use with PBBS v3.0, mainly for listing the user's file and stats on the callers file. ---- PDLN10.LBR - CP/M A new Public-Domain Linker, including a highly informative .DOC file. For Z80 only, not for ZCPR only. [ 06:13:17 AM Apr 10, 1986 ] ---- PICKNUM.LBR A super MEX support program. Contains PICK106 which will go through your .PHN files and select the numbers you want to put in a new .PHN file. This contains updated versions of PICK and DLMX contained in Bill Norris' MEXELEC2.LBR ---- PPIP.LBR - Digital Research CP/M slick pip - the z80 version is fast - crc and verify options - can assemble to pip to destination from source or 'copy from source to destination' - accepts DU: - other toggles/switches - pip to text file with built in editor - - ---- PRICES11.RQS - Z-System (ZCPR3+ZRDOS) Slightly changed price list from Echelon...use for orders as of 11 August and beyond... ---- PRINTHLP.LBR This program will print out an entire help tree. If you configure it for your printer it will highlight the text that is highlighted on the screen while running help. Thus if you want a nice document of all of the SYSLIB files just run it on SYSLIB.HLP and it will pick up all of the nested help files. ---- PROLINK.LBR - CP/M NightOwl Software releases ProLink, the great proprietary linkage editor, to the public for free distribution. Included is LINKMAP, a REL file display utility. ProLink is said to be vastly superior to L80 as a linker. Get this one if you do anything at all with relocatable assembler. ---- PSET15X.AQM - CP/M Upgrades PSET14 to include a real command line mode for batch and/or ALIAS use. Only program that allows you to set print type from the command line prompt. For Epson RX-80 and Gemini printers. ---- QEDIT125.ARC - MS-DOS This is an update of QEDITA and includes lots of new gimmicks. QEDIT is a fast, memory resident editor which has it all over the likes of WORDSTAR for programming. ---- QLIST14.LBR - CP/M Ian Cottrell, Ottowa ICBBS fixes reported bugs in QLIST14. QLIST is a file lister that will automatically unsqueeze files before listing. QLIST allows you to select formatting options for the listing, including; left margin setting, line feed recognition, page headers, compressed print for body of listing and expanded print for the headers and page to start/stop printing. See .DQC file for updates. ---- QWIKFONT.LBR - CP/M Sets FONT and type styles for Epson and compatible printers. May be set up for differenct terminals and printers by use of SUPERZAP, etc. Also prints out quick labels with ability to change font in the mid- dle of the line. [ 05:48:02 AM Nov 08, 1985 ] ---- RCPTRAPS.LBR - ZCPR3 A little I/O redirection for ZCPR3 systems, in the form of Resident Command Packages. Two files are included in the library, one sends all output going to the printer to a disk file, the other sends all output going to the screen to a disk-file. The code is lean enough that this could be incorperated into your standard RCP. ---- READONLY.LBR - CP/M Sets the disk system in a CP/M Version 2.x operating system to read/only. Once executed the only way to return the disk system to read/write to do a system reset (cold boot). This "safety" is intended to prevent untested software from changing any data on any disk. [ 08:18:28 AM Oct 06, 1985 ] ---- RELHEX11.LBR Small, fast, accurate program that converts REL files to HEX format. Now RMAC owners can trash MAC & ASM, keep ZAS for Zilog mnemonics. ---- RESQ14.LBR - General This little program will help you out if you are using WS and get a 'disk full' error when you try to save your work. ---- ROS34.LBR - CP/M Remote Operating System v3.4. A stand-alone RBBS, BYE, XMODEM, SD all included in one program. Written in Pascal. For CP/M systems. ---- SAME.LBR - CP/M Checks two files to see if they are the same. Can erase one. Read the .DOC file for various attributes. [ 06:14:22 AM Oct 14, 1985 ] ---- SAP50.LBR - CP/M Sort and Pack. Cleans up your directories and eliminates deleted entries. ---- SAVESTAR.LBR - CP/M Saves WordStar 3.3 and Turbo text if you have 'lost' it all with a system crash or other accident. From Profiles. [ 02:16:14 AM Feb 08, 1986 ] ---- SB180OVR.AQM - Other This is an overlay file that ports MDM730 to the SB180. It's pretty rough, but as 'they' say in computer rooms across the land... "It works." I'ld appreciate messages from anyone that can tell me how to do it right. Thanks - aaron. CRC after unsqueeze = 3FF1. ---- SETDRU13.LBR A clever way to enable you to use programs that require OVR (WordStar Perfect Writer, etc) any where on a hardisk. ---- SCAN12.LBR How about a TYPE that types files forwards/backwards/sideways and even works on squeezed files!! [ 04:29:50 AM Nov 19, 1985 ] ---- SCI-12.LBR - CP/M Small-C interpreter. Even if you just know a little BASIC, a great way to get started with "C". ---- SIDEMT.LBR - CP/M A program to print sideways on a MT printer, for CP/M-80, NOT PC/MS-DOS! ---- SFILE26.LBR - CP/M Searches all allowed drives and user areas for a requested file or files. An equate allows for searching into all libraries as well, atlhough this usually takes considerably longer. Used on many RCPM systems with large disk drives and many user areas. Very useful on any large hard disk system. The .COM file is only 3k. Source code included. This version fixes a bug in the abort routine. ---- SHOWLOC.OBJ ANY 8 BIT CP/M COMPUTER CAN USE THIS. IT SHOWS THE LOCATION OF A FILE ON A DISK BY BLOCK NUMBER, TRACK AND SECTOR NUMBER. (07:39:23 AM Aug 08, 1985) ---- SLTRAP.LBR SLTRAP -- RCP which captures Screen and List output and stores it on disk. ---- SPOOLER.LBR - CP/M A new spooler/despooler utility. Print and work at the same time. ----- SODU.LBR - CP/M A screen-oriented version of the DU Disk Utility program for CP/M 2.2. ---- SSTAT18.LBR - CP/M A very nice, SWEEP/NSWP/DISK7-style replacement for STAT, PROT, etc. Does everything except change device assignments, and what it does it pulls off with great pizazz. ---- SUPZAP33.LBR - CP/M Updated version of SUPERZAP. Doesn't have all the features of some other patching programs. but is menu driven, easy to use and FAST. Source code included for adapting to diferent computers. Now Also supports CPM3. ---- SYSRCP14.LBR - Z3 This library contains version 1.4 of SYSRCP.ASM, the code for the resident command package. Version 1.4 has no significant differences from version 1.3. Two small problems were fixed. ---- T3T-24-1.ZQ0 - ZCPR3 Echelon releases a "telephone interface" for TERM III that supports 300/1200/2400 baud modems such as the Hayes 2400, USR Courier 2400, and Racal-Vadic 2400V. This TI allows full use of these modem's advanced features. [ 03:32:45 AM May 25, 1986 ] ---- TELENET.LBR - CP/M Turbo Pascal program to auto-log on PC Pursuit. Comes in two versions, one set up for the video Kaypros and the other generic. ---- TELL02.LBR This is a small utility used to find out various locations of what and where various addresses are within the CP/M for which this utility operates. Quite useful if your writing software for CP/M, but need to find out the EXACT addresses that some CBOIS routines are operating when the occasion arises that the software CAN'T access it through CP/M, like rewriting FORMAT programs and such utilities as those..... ---- TEXTCOM.OBJ - CP/M Compares two ASCII files, reports differences and may, optionally, write same to a disk file. [ 04:04:16 AM Nov 19, 1985 ] ---- TPA3.LBR Indicates the TPA space available. (08:52:50 PM Jun 08, 1985) ---- TYPELZ15.LBR - CP/M Type any file (or library member) whether SQUEEZED, CRUNCHED, or ASCII, to CONSOLE or PRINTER. If set for RCPM use, non-WHEEL users can't type SYSTEM files or access printer, and can be limited to a set number of lines. Use .COM file and TZINST15.DOC along with DDT or PATCH to configure without reassembly. SYSOPS note, makes a great LUXTYP replacement to add CRUNCHED typing to LUX Library mode. Source code included (Z80). ---- UNARC10.LBR - CP/M UNARC is a CP/M utility which allows the listing and extraction of subfiles contained in MS-DOS/PC-DOS archives (*.ARC files). Requires CP/M 2.x or higher and Z80 only. The library (88K) includes the Z80 assembly language source; for minimum download: extract just UNARC10.COM and UNARC10.DQC (squeezed documentation). [ 03:21:21 AM May 09, 1986 ] ---- UNERAS12.LBR - ZCPR3 Rescues those 'erased' files. ---- UNSPOL38.LBR - General An unspooler that works with squeezed files. [ 06:14:31 AM Sep 17, 1985 ] ---- USQFST19.LBR - CP/M Steve Greenberg's Fast Unsqueezer, v1.9 - 04/02/86. Takes wildcards. Z80 only. ---- VALIAS.LBR - ZCPR3 Jay Sage's official release version of VALIAS, the full screen alias maker, editor, with built in help. Great utility that replaces ALIAS. ---- VCED16LBR - ZCPR3 Paul Pomerleau's Video Command Editor. Now doubles as an error handler. Features a help menu, the ^O FIND option that searches the buffer for your command, and a command buffer locater that tells you exactly where in the circular buffer your command is located. New version is faster. ---- VDE22.LBR - Text/Documentation Latest version of the handy little text editor. Word-wrap, margin setting (left and right), crude windowing. More WS-like with commands. ---- VERROR17.LBR - ZCPR3 Version 1.7 prompts you for edit and is more responsive to keys hit before VERROR's message appears. VERROR is a Z3 'error handler' that lets you edit mistyped commands before you get the famous '?'. Try it. ---- VERSION.LBR - CP/M A small program that will allow you to add a comment line, version number, serial number and date to each program on your disk. I have not tried it yet, but the DOC file looks interesting. ---- VFILER41.LBR - ZCPR3 This is the latest version of VFILER4 from Jay Sage. Jay's improvements now make VFILER the most powerful multi-faceted SUPER utility availabe. You can find a match in MS-DOS, CP/M or ....whatever. ---- VIRUS.TQT - Other This is an interesting description of computer viruses. Subtopics include worms. Definately more subtle and more devastating than 'bugs'. ---- VMENU18.LBR - ZCPR3 This is the latest update of misc and bug fixes. Changes made are: 1 - "< & >" bugs fixed no longer drops to system. 2 - it now knows what menu to use when changing user areas. 3 - Command line no longer doubles up. 4 - Minor cosmetic changes in banner line. 5 - Now displays 4 lines by 5 colums, also added 1 menu line. ---- VTYPE17.OBJ - Z-System (ZCPR3 + ZRDOS) This is Dennis Wright's video oriented text file display utility. Use is easy: VTYPE dir:filename.typ Once started enter '/' for commands and options. ---- W20.LBR - ZCPR3 Steve Cohen's new Z utility, "W" is a wild-card processing shell. It allows you to give wild-card function to program that otherwise will not handle wild-cards. [ 12:48:01 AM Feb 27, 1986 ] ---- WINDEX21.LBR Latest version of WINDEX, a superior index generator, with improvements that allow use via the "R" command in Wordstar. ---- WIS105.LBR - CP/M Uploaded another copy becauses someone commented that the first had a trashed directory. This is the same one and NULU and LU both extracted the file fine! Hope this fixes the problem! ---- WS-BIBLE.DQC - General The comprehensive WordStar patch document, covering WS 2.26, 3.0, and 3.30. All you need is DDT or equivalent. [ 01:37:42 AM Dec 21, 1985 ] ---- WS-UROM.FQX - Z3 How to patch Kaypro's U-ROM Wordstar for use with "Z-SYSTEM." ---- WSFAST24.LBR Sanders' latest update to the Wordstar speedup patch. Also provides half- intensity reverse video for those who wish to preserve vision and CRT life. ---- WTEXT102.LBR - CP/M NLQ driver for Epson LX. Proportional letter widths, ragged margins. May also work on other FX/RX units. Draft type for MX w/Graftrax. The appearance of the Letter type on an LX is much better than Epson's fixed pitch NLQ, and better than anything else in the public domain. ---- XIZI-3.LBR - CP/M Irv Hoff's update contains two translators, one for Intel 8080 to Zilog Z80 source code and the other for Z80 to 8080 source code. Very fast. This version fixes an obscure op code in the Z80 to 8080 translator that has been present in virtually all such translators - check the "READ.ME" file for more information. Will allow a single Z80 assembler to be used for all CP/M work. Replace such pgms as XLATE6, ZTOI, ITOZ, XLT8-80, XLT80-8, XLTZ80, ZCON, etc. 20k, 152 records. [ 06:29:43 AM Jun 19, 1986 ] ---- XUSER11.LBR - CP/M Utility permits you to use all 32 user areas. See doc file for system constraints. Interesting utility. [ 07:12:29 AM Nov 16, 1985 ] ---- Z-DEMO2.LBR Some great examples of how to utilize Z3's MENU power. ---- Z-RIP.LBR - ZCPR3 Paul Pomerleau's newest Z-System contribution installs all ZCPR3 utilities in a user area or in all user areas. A fast way of re- installing if you have changed your memory map location of the environment descriptor. [ 06:30:14 AM Jun 19, 1986 ] ---- Z3KEY14.LBR - ZCPR3 This latest version of the Z3 key-string utility includes the public domain Z80 assembler and a ZEX file to automate the assembly process. That should take care of all the assembly problems. ---- Z3NEW085.LBR - RAS-specific (Remote Access System) A ZCPR3 utility -- this replaces NEW andd provides many additional features. This is a test version written by Edi Cramp of Tampa, FL. It has not been tested. It needs to be run through its paces to see where the bad bugs may be lurking. ---- Z80MU310.ARC - MS-DOS Runs Z80/CPM programs under MS-DOS. Very good emulation. All standard programs seem to run (those not doing disk I/O on a track/sector basis, but using file open/closes) very well. This program has the best interactive debugger, disassembler, line assembler, symbolic debugger I have seen, and it is built in so it does not require TPA space. (which is 63k by the way!!) ----- Z8E.LBR THE Z80 debugger. Described as the best thing since Wonder...... ---- ZAP.LBR - ZCPR3 The ZAP Debugger as a RCP. A "SYSTEM MONITOR," most desirable for either the industrial or the hobbyist/experimenter environment. This monitor may be classified as a "DEBUG" monitor. That is, it contains all needed tools to fully debug both hardware & software. ---- ZAP34B.LBR - CP/M SUPERZAP 3.4 (b version). A revision of SUPERZAP v3.3 to include string and hex-sequence search capabilities on a given file, and some 'enhancements' to the TYPE option, including 80 col. display, and allowances for viewing word-processed files of some commoner kinds. ---- ZAPN#1.LBR - ZCPR3 The first of a series of application notes on the Z-System. This one discusses the ZCPR3 Shell system 'from the inside'. The target audience for these application notes are programmers and equipment manufacturers; however, there is probably a little something for everyone. ---- ZDR.LBR - CP/M A small ( <7 records, <1k ), but complete disk directory program. Its small size, and horiZontal format (the Z in ZDR) are suited to the screen of, say, the portable Epson Geneva PX-8. ---- ZDP.LBR - CP/M Z.D.P. is a Z80 assembly lang. program de-bugging, tracing, editing utility which runs on any CP/M based system. The working code occupies just over 4k RAM positionable on any 256 byte page (e.g. can also trace code running in the CCP area). Inaddition to a self contained symbolic address feature; there are byte, word, & string search commands plus some other features not in DDT or ZSID. (for which this package serves as a useful supplement/replacement. Library has several files including complete manual & implementation notes, etc. ---- ZFILE2.LBR - CP/M A replacement for FILE and SFILE.....for use primarily by RCPM/RAS systems with large Hard disks....Based on FINDF by R. Conn. Uses std low memory max drive and max user locations in BYE5xx/KMD (3dh 3eh,3fh). May be used by any cpm system, compiled with any compiler. Added ^x to abort, ^s to pause, FIVE times faster than as FILE OR SFILE. ---- ZIPP.LBR Public doman utilities exist which execute the concatenation of files (i.e. join them end to end). ZIPP was written to join up to seven ASCII files in a side to side or column sense. Useful for data analysis, spreadsheets, reports, etc. [ This is a RENamed version of ZIP.LBR. This was done to avoid a name conflict with Ashton-Tate's ZIP.COM, the screen design program for dBASE II. ] ---- ZTP-INS2.LBR - ZCPR3 Auto-installer for Turbo-Pascal programs on ZCPR3 systems. Some of you may remember the earlier ZTP-INS.LBR. That one used a Turbo-Pascal program to do the job, this one is a Z3 utility written in z80 assembler. Other features include options to Turn off or reverse high and low video. ---- ZSIG-FOR.ALL - General N.A.O.G, the North American One-Eighty Group, becomes NAOG/ZSIG, the NAOG ZCPR Systems Interest Group, and embraces all users of ZCPR3. Jay Sage is Software Librarian, Richard Jacobson is RAS Coordinator, and Bruce Morgen is Director and Editor of the ONE-EIGHTY FILE. Membership application and full information are available in this file. A users group for advanced programmers to share their dis- coveries and novices to learn. ---- ZSYSTEM.IQS A master checklist for all to assess their collection of Z-System (ZCPR3 + ZRDOS) utility programs, to determine where upgrades might be necessary or perhaps even acquire missing programs. Altogether, lists 102 programs and 1 database, all distributed by Echelon, and nearly all available on Z-Node Central. 102 programs...What other operating system comes with 102 utility programs? Wow! (Dated 20 July 1986; will probably become inaccurate rapidly, due to the large amount of activity within Z-System.) ---- ZX31.LBR - CP/M CP/M program that includes an alphabetized (horizontally) directory listing, erase, unerase, scroll, type (forwards or backwards) rename, copy, a sector-oriented text editor, and other useful functions. Re- quires a Z80 processor. Library includes an extensive .DOC file. ---- ZWORD.TQT - General Richard Conn ('Mr ZCPR3') answers the four most asked Z-system questions. ---- [ End of SEPTBEST.LST Contact Seattle's `downspout' at 206-325-1325 for more details. 24 hours: 1200/2400 baud; 9am - 3pm [PST] 300 baud. ] 1-Sep-86 16:54:42-MDT,1342;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 1 Sep 86 16:54:21-MDT Received: from simtel20.arpa by AMSAA.ARPA id a011453; 1 Sep 86 18:28 EDT Date: Mon, 1 Sep 1986 16:16 MDT Message-ID: Sender: KPETERSEN@SIMTEL20.ARPA From: Keith Petersen To: Info-Cpm@AMSAA.ARPA, Info-Micro@BRL-VGR.ARPA Subject: Electronic Communication Privacy Act (S.2575) update The latest version of the Electronic Communication Privacy Act (S.2575), dated August 12, 1986, is now available from SIMTEL20, thanks to Bill Bogstad , who added them into the posting by Glenn Tenney. Filename Type Bytes CRC Directory PD: PRIVCY2.BILL.1 ASCII 75835 4E46H For those who can handle binary FTP transfers and unsqueeze: Directory PD: PRIVCY2.BQL.1 BINARY 45056 D16DH Reviewing: The Electronic Communications Privacy Act of 1986, which has passed the House, now is a bill in the Senate (S.2575). This one Act affects every usenet, bitnet, bbs, shortwave listener, TV viewer, etc. --Keith Petersen Arpa: W8SDZ@SIMTEL20.ARPA uucp: {ihnp4,allegra,cmcl2,decvax,mcnc,mcvax,vax135}!seismo!SIMTEL20.ARPA!w8sdz GEnie Mail: W8SDZ RCP/M Royal Oak: 313-759-6569 2-Sep-86 07:12:10-MDT,2686;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 2 Sep 86 07:11:50-MDT Received: from wiscvm.arpa by AMSAA.ARPA id a016887; 2 Sep 86 8:00 EDT Received: from (UZ32112)SG2.BITNET by WISCVM.WISC.EDU on 09/02/86 at 07:01:44 CDT Date: Tue, 02 Sep 86 14:00:23 ULG To: INFO-CPM@AMSAA.ARPA From: UZ32112%SG2.BITNET@wiscvm.ARPA Subject: NOTE from UZ32112 Date: 2 September 1986, 13:57:59 ULG From: Andre PIRARD +32 (41) 520180(449) UZ32112 at BLIULG12 SEGI - Universite de Liege 15, av. des Tilleuls B4000 LIEGE (Belgique) UZ32112%BLIULG12.BITNET@WISCVM.WISC.EDU To: INFO-CPM at AMSAA Subject: Commodore 128 [line eater bait] I am the owner of a Commodore 128 and a 1571. I bought it for its versatility and would not mind its slow speed if there were no exageration and it were bug free. But it is not the case. I would like to know if these problems show up on U.S. or recent machines or does anyone have comments or cure for the following: 128 Mode: -The DOS shell file copy function exhibits the stange behaviour of adding one byte to the file being copied. Harmless for program files, it is a nuisance for text files. I'd be glad to have a correction for this otherwise very handy program. -The 1571 is double sided and faster than the 1541... until I get to filling side two. On that side, writing is VERY slow. The drive alternately accesses the data and the directory sectors for EACH sector being written. Looks like it reads and/or writes the BAM (block availability map) for each sector. On side one, the directory is accessed only between a group of records. The SAVE command does however fill both sides without directory access. It only occurs during other I/O's (e. g. program output or file copy). -The capslock key has no effect on the letter Q. CP/M mode: -Is there a way to assign the printer logical unit to the user port to a parallel printer? -There is a device driver supposed to drive a 6251 rs232 chip. But the 128 has none. What is it there for? I would appreciate to do rs232 I/O (not modem). -There is an evident lack of keyboard buffering and auto repeat. -The screen output is very slow (80 column). -Commodore statement of a 4MHz Z80 is a very subtle lie. It DOES 4MHz, but only HALF of the time (each other half cycle of a 2MHz clock). Really 2MHz. Would they pay half time employees at full rate? -The CPM+ makes ridiculous little use of the alternate memory bank for I/O buffers. -In other words, is there a better CP/M than the one we get with the machine? [These are not opinions, but facts] 2-Sep-86 10:17:05-MDT,902;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 2 Sep 86 10:16:42-MDT Received: from wiscvm.arpa by AMSAA.ARPA id a025220; 2 Sep 86 11:32 EDT Received: from (MEK)UMASS.BITNET by WISCVM.WISC.EDU on 09/02/86 at 10:33:26 CDT Message-ID: <860901174021.000001F4.ADSF.MA@UMass> Date: Mon, 1 Sep 86 17:40:21 EDT From: mek%UMass.BITNET@wiscvm.ARPA Subject: BYE510/C128/1670? To: info-cpm@AMSAA.ARPA I'm trying to set up BYE510 on my C128 with 1670 modem. I put in the proper insert, and have it running, except when I type BYE E I get some information about the number of calls, and then, continuously: A Echo error A Echo error I assume this is something I'm doing wrong in the Modem configuartion section. What should the modem settings be for the 1670? Thanks in advance! -Matt Kimmel, mek%UMass.BITNET@wiscvm.ARPA 2-Sep-86 13:06:42-MDT,602;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 2 Sep 86 13:06:27-MDT Received: from nosc.arpa by AMSAA.ARPA id a000817; 2 Sep 86 14:16 EDT Received: by bass.ARPA (5.31/4.7) id AA08308; Tue, 2 Sep 86 11:17:04 PDT Message-Id: <8609021817.AA08308@bass.ARPA> Date: Tue, 2 Sep 86 11:00:28 PDT From: Marc Wilson To: info-cpm@AMSAA.ARPA Subject: Re: NOTE from UZ32112c Get yourself a copy of the newest CP/M system, dated 6 December 1986. It addresses many of the problems you note, but adds a few new ones. 3-Sep-86 05:14:50-MDT,1272;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 3 Sep 86 05:14:44-MDT Received: from wiscvm.arpa by AMSAA.ARPA id a007475; 3 Sep 86 6:43 EDT Received: from (SINGPANG)HLERUL5.BITNET by WISCVM.WISC.EDU on 09/03/86 at 02:45:38 CDT Date: From: SINGPANG%HLERUL5.BITNET@wiscvm.ARPA MMDF-Warning: Parse error in preceding line at AMSAA.ARPA Subject: BITNET mail follows To: info-cpm@AMSAA.ARPA X-Original-To: info-cpm@amsaa.arpa, SINGPANG I am asking these questions on behalf of a friend all the way in South America. The questions are about the Commodore 128 1. Is there a mailing list for the C128? If so can you give me the net address? 2. Are there any communication programs (eg. Kermit) for the C128? 3. Is there any way to read C64 disk files in C128 mode? 4. The same problem, but now reverse. Can I read C128 CP/M disk files in C64 mode? 5. Has anybody experience in using a modem with the C128? What modem is it and what communication program do you use? 6. Can I expect problems when buying generic CP/M 2.2 or 3.0 programs? How compatible is the Commoder CP/M version on the C128? Thanks in advance. Please mail to: SINGPANG%HLERUL5.BITNET@WISCVM.ARPA 3-Sep-86 05:25:17-MDT,1442;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 3 Sep 86 05:25:09-MDT Received: from brl-smoke.arpa by AMSAA.ARPA id a007566; 3 Sep 86 6:57 EDT Received: from USENET by SMOKE.BRL.ARPA id a020229; 3 Sep 86 6:48 EDT From: "The News System " Newsgroups: net.micro.cpm Subject: Date: Message-ID: <3506@brl-smoke.ARPA> Date: 3 Sep 86 10:48:33 GMT To: info-cpm@AMSAA.ARPA From: SINGPANG%HLERUL5.BITNET@wiscvm.ARPA MMDF-Warning: Parse error in preceding line at AMSAA.ARPA Subject: BITNET mail follows To: info-cpm@AMSAA.ARPA X-Original-To: info-cpm@amsaa.arpa, SINGPANG I am asking these questions on behalf of a friend all the way in South America. The questions are about the Commodore 128 1. Is there a mailing list for the C128? If so can you give me the net address? 2. Are there any communication programs (eg. Kermit) for the C128? 3. Is there any way to read C64 disk files in C128 mode? 4. The same problem, but now reverse. Can I read C128 CP/M disk files in C64 mode? 5. Has anybody experience in using a modem with the C128? What modem is it and what communication program do you use? 6. Can I expect problems when buying generic CP/M 2.2 or 3.0 programs? How compatible is the Commoder CP/M version on the C128? Thanks in advance. Please mail to: SINGPANG%HLERUL5.BITNET@WISCVM.ARPA 3-Sep-86 06:29:30-MDT,1041;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 3 Sep 86 06:29:18-MDT Received: from mit-mc.arpa by AMSAA.ARPA id a008808; 3 Sep 86 7:46 EDT Date: Wed 3 Sep 86 07:47:43-EDT From: Mark Becker Subject: Bondwell machine To: Info-CPM@AMSAA.ARPA Message-ID: <12235962180.13.CENT.MBECK@OZ.AI.MIT.EDU> Hello - I've seen several references on the net for a portable CP/M machine going by the name of "Bondwell". Who is selling these things in the Maryland area? Also, some questions to those already owning this portable: Are schematics and tech info available? I believe there are two Bondwell machines - one runs CP/M 2.2, the other runs 3.0 . True? How many and which of the CP/M utilities (ASM, PIP, ED, etc) are supplied? How much documentation is supplied? Is it bundled with any other software? If I get sufficient queries, I'll post a summary to the net. Thanks - Mark Becker ------- 3-Sep-86 10:57:06-MDT,6150;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 3 Sep 86 10:56:35-MDT Received: from nadc.arpa by AMSAA.ARPA id a012495; 3 Sep 86 9:23 EDT Date: 3 Sep 1986 09:18:37-EDT From: prindle@nadc.ARPA To: info-cpm@AMSAA.ARPA Subject: C128 info Cc: singpang@hlerul5.bitnet, wiscvm@nadc.ARPA MMDF-Warning: Parse error in preceding line at AMSAA.ARPA Reply to request from singpang%hlerul5.bitnet: 1. The only widely utilized mailing list for the C64/C128 is the USENET list called "net.micro.cbm". This list is *not* gatewayed into the Arpanet. I have no idea if there is a USENET/BITNET gateway that passes this list. You can *submit* postings to "net.micro.cbm" by sending mail to microcomputer.cbm@rutgers.arpa. However, you cannot receive the postings because of the lack of a bidirectional gateway. Therefore, if you do submit a posting that requires a reply, be sure to ask for a carbon-copy to be sent directly to your address. 2. There are many communications programs, including Kermit, for the C128 in C64 mode. There are a few (no Kermit) for the C128 in native mode. There are at least 3 (IMP, MEX, and Kermit) for the C128 in CP/M mode. In short, there is no shortage of comm. programs - it's just a matter of finding the one you want. All 3 CP/M programs are in the SIMTEL20 archives (I know, BITNET people can't get those yet, but in time.....). 3/4. C64 and C128 disks are virtually identical (there are two flavors, single sided and double sided, but with a 1571 drive, either machine can read or write either format). There are currently bugs in the drive ROM which make it semi-pointless to use double sided with C64 or C128 mode. CP/M disk formats are simply random accessed variants of the basic C128 double or single sided formats - the three possible MFM formats are documented in the (Commodore) C128 Programmer's Reference Manual, and with this knowledge, it is not tough reading or writing CP/M disk formats from non-CP/M modes (hint: use the U1 and U2 random access functions of the drive DOS). On the other hand, CP/M cannot log in a non-CP/M formatted diskette, so reading or writing such from CP/M might be a hassle, if it is possible at all. 5. With the right communication software, a modem works great with the C128 in any mode at 300 or 1200 baud. The 128 has no UART, so there is so-called "bit-banging" code in both the ROM Kernal and in the CP/M BIOS to support receiving and sending bits at the right rate via internal clock interrupts. At 1200 baud, this eats up plenty of CPU time, but for general comm. functions (terminal emulation, uploading, downloading, capture buffer), this is no problem as long as the remote system can handle an occasional XON/ XOFF flow control sequence. I say "with the right communication software" because there are bugs in the Kernel ROM, so you cannot use the RS-232 port code by the book. You have your choice of either a TTL/Commodore User Port compatible modem (from several manufacturers including Commodore), or an ordinary RS-232 modem. If you use an RS-232 modem, you need level converters between the user port and the modem - Commodore and others sell such converters, or you can make your own. I use an Andersen-Jacobson 1259 RS-232 modem with homebrew (transistor even!) inverters. I use IMP, MEX, and Kermit in CP/M mode, TERM.PLUS, Kermit, XMOBUF, and Punter programs in C64 mode. The only semi-useful program I've used in 128 mode is called MicroVT-128 and it has not matured into a stable product yet. 6. C128 CP/M 3.0 is a very faithful implementation of banked CP/M 3.0 with a 58K TPA. You should be using the 6DEC85 or 8DEC85 versions to get the full benefit of bug fixes, RS-232 port support, and RAM expansion support. The only reason *any* CP/M 3.0 program would not run on the 128 would be that is was not configurable for the terminal emulation used by the 128 BIOS, that is an ADM31 (almost). Many CP/M 2.2 programs will work without any problem at all; in this case, any incompatibility (in addition to terminal emulation) would be in the form of 2.2/3.0 differences; fortunately, these are minimal since 3.0 was designed to be largely compatible with 2.2, while adding new features. One example of incompatibility is that some 2.2 "unerase" programs are confused by the volume header and/or time stamps of 3.0 and thus will not work. But the vast majority of CP/M 2.2 products seem to work just fine (try before you buy!). The 1571 disk drive will sense (and cause the BIOS to adapt to) MFM diskettes formatted for the Osborn (SSDD), Kaypro II, Kaypro IV, Epson (something or other...), and IBM-PC CP/M-86, and possibly some others; consult the manual for details. Beware, the 128, even in CP/M mode, is not without it's faults. The Z-80 is only running at 2Mhz., so don't expect the performance of a 6Mhz. system. Screen updates are moderately slow (but not unusable - equivalent to somewhere around 300 characters/second). You should set the baud rate down to 110 whenever you are not using the RS-232 port to minimize interrupt processing overhead, and maximize *your* use of the CPU. Diskette reads (on a 1571 drive) are pleasingly fast (from MFM formatted diskettes), but writes are quite a bit slower (there is a utility available which almost doubles the write speed - much better). 40 column mode is almost useless (sideways scrolling) for CP/M, so you better use an RGB or monochrome 80 column monitor. And finally, ROM bugs in the 1571 drive make it nearly useless to try to use double sided formatted diskettes in the non-CP/M modes (this has been fixed by Commodore, but it is still not obvious how to get the new ROMS - new ROMS are being used in newly manufactured units, but it would be hard to say if a given drive on a dealer's shelf had the old or the new). Sincerely, Frank Prindle Prindle@NADC.arpa 3-Sep-86 21:45:09-MDT,767;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 3 Sep 86 21:45:03-MDT Received: from wiscvm.arpa by AMSAA.ARPA id a010207; 3 Sep 86 23:08 EDT Received: from (MEK)UMASS.BITNET by WISCVM.WISC.EDU on 09/03/86 at 10:06:10 CDT Message-ID: <860903105954.000012D6.AFCB.MA@UMass> Date: Wed, 3 Sep 86 10:59:54 EDT From: mek%UMass.BITNET@wiscvm.ARPA Subject: Mailing list for C128 To: info-cpm@AMSAA.ARPA Yes, there is a general Commodore mailing list on the network. Its address is: CBMList%UMass.BITNET@wiscvm.ARPA All requests to be added to or deleted from the mailing list should be sent to: MKimmel%UMass.BITNET@wiscvm.ARPA -Matt Kimmel, CBMList coordinator. mek%UMass.BITNET@wiscvm.ARPA 4-Sep-86 04:33:02-MDT,3189;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 4 Sep 86 04:32:46-MDT Received: from brl-smoke.arpa by AMSAA.ARPA id a011022; 4 Sep 86 5:47 EDT Received: from USENET by SMOKE.BRL.ARPA id a012958; 4 Sep 86 5:40 EDT From: Marc Lewert Newsgroups: net.micro.cpm Subject: Re: Bondwell machine Message-ID: <119@triada.UUCP> Date: 4 Sep 86 00:55:37 GMT To: info-cpm@AMSAA.ARPA In article <3508@brl-smoke.ARPA>, Cent.Mbeck%OZ.AI.MIT.EDU@mit-xx.ARPA (Mark Becker) writes: > Also, some questions to those already owning this portable: > > Are schematics and tech info available? I don't know, one would presume so, but I don't know where to get them. > I believe there are two Bondwell machines - one runs CP/M 2.2, > the other runs 3.0 . True? True. The Bondwell Model 12 runs,CP/M 2.2, Model 14 (which I have) runs 3.0 > How many and which of the CP/M utilities (ASM, PIP, ED, etc) > are supplied? Quite a Few. PIP, ED, at least one macro assembler, I will have to make a list and get back to you on that, but there is quite a bit of stuff > How much documentation is supplied? Documentation is so-so. Better in some areas than others. The DDT documentation is non-existant, the ED documentation is ok, I guess, the PIP documentation seems complete. One of the manuals is just on the CPM utiltities. There is at least one page for each utiltiy, but it does not always cover all that you need to know > Is it bundled with any other software? Yes, Wordstar and Mailmerge (minus spelling checker), Calcstar, Datastar, Reportstar. All of these include manuals put out by Micropro. No language is included however. I considered this a problem, but purchased Turbo Pascal the next week. The Bondwell 14 can read and write several different disk formats including Kaypro II, and Osborne 1 double density, but cannot format anything but it's own format. I ended up getting a couple of disks formated by an Osborne system and keep them for passing data to other systems. The Bondwell is supposed to be a Kaypro II compatable system, and so far it has been. I have not bought much in the way of software (a spelling checker, Turbo Pascal, Zork III, Right-Hand Man), but all was purchased as if I were using a Kaypro II, and seems to work. The only exception is the Right-Hand Man, which I specified CP/M 3.0, and thinks there are only 24 lines on the screen (the screen is 25 lines X 80 Characters/line). Please note all of the above is off the top of my head, and about a Bondwell 14. I do not have any direct knowledge of the bondwell 12. -- ========================================================================= Marc Lewert UUCP: ...hplabs!pyramid!triada!marc Triad Systems Corp. PO Box 61779 MA Bell: (408) 734-9720 Sunnyvale, Ca. 94088-1779 Disclaimer: All views are my own and do not reflect those of my employer, friends, or family unless otherwise noted. ========================================================================= 4-Sep-86 04:45:12-MDT,1125;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 4 Sep 86 04:45:06-MDT Received: from nosc.arpa by AMSAA.ARPA id a011173; 4 Sep 86 6:18 EDT Received: by bass.ARPA (5.31/4.7) id AA27292; Thu, 4 Sep 86 03:19:03 PDT Message-Id: <8609041019.AA27292@bass.ARPA> Date: Thu, 4 Sep 86 02:53:54 PDT From: Matt Smiley To: info-cpm@AMSAA.ARPA Subject: Re: C128 info/CP/M 3.0 Something else as to using CP/M and a modem... You must have the December 6(?) overlay for your CP/M 3.0. The system included with the machine is *not* capable of using a modem! This overlay is available on Quantum-Link for sure, and possibly GENIE. I have not used a 128 for over six months, however, and CBM may be including the new version of CP/M with the machines by now. Surefire way to tell: Look at the release date when you boot the system. If it's August, it's the old one. The new one is dated December '85 or later. I suggest you use IMP or MEX for your modeming. They are superior to anything I have seen in the C-128 public domain world. 4-Sep-86 08:53:22-MDT,972;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 4 Sep 86 08:53:01-MDT Received: from wiscvm.arpa by AMSAA.ARPA id a018050; 4 Sep 86 10:12 EDT Received: from (MAILER)UNBMVS1.BITNET by WISCVM.WISC.EDU on 09/04/86 at 09:13:25 CDT Date: 04 Sep 86 10:57:06 ADT From: SEA%UNBMVS1.BITNET@wiscvm.ARPA MMDF-Warning: Parse error in preceding line at AMSAA.ARPA To: INFO-CPM@AMSAA.ARPA Message-ID: Date/Time: 86/09/04 10:45 AST From: Steve Allain, University of New Brunswick, Canada SEA@UNBMVS1.BITNET To: Users of MULTIFLEX CPM 2.2 Is anyone out there familiar with the MULTIFLEX S-100 system (Z-80 CPU, Floppy Controller, Video/Keyboard Card and MULTIFLEX CPM 2.2 )? Before I order any software (on disk), I want to know which types of 5-1/4 " disks it can read with the existing CBIOS - eg. KAYPRO, OSBORNE... 4-Sep-86 10:01:55-MDT,12639;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 4 Sep 86 10:01:12-MDT Received: from simtel20.arpa by AMSAA.ARPA id a019602; 4 Sep 86 10:55 EDT Date: Thu 4 Sep 86 08:56:24-MDT From: "Frank J. Wancho" Subject: New Service Available! To: INFO-CPM@AMSAA.ARPA Message-ID: <12236258673.9.WANCHO@SIMTEL20.ARPA> This message marks an historic moment, and a bit of background history which has brought us to this moment is in order. Please bear with me while you read this lead-in to details you have all been eagerly awaiting at the end of this message. Seven years ago this past Friday, August 29, 1979, INFO-CPM was formed as a spin-off of INFO-MICRO, both homed at the time on MIT-MC. The following month Keith Petersen's Royal Oak RCP/M system was discovered, and Keith was invited to directly participate in the INFO-CPM discussions. Through Keith's direct access, he was able to upload, crudely at first, selected files for FTP from MIT-MC from his vast up-to-date RCP/M collection. As new files became available, Keith made the announcements to the INFO-CPM list. New contributions and updates to existing files were likewise made available from other ARPANET users. Thus, the CP/M archives was born, with disk space courtesy of the MIT-MC management. This activity caused the development of several mainframe versions of CP/M utilities, such as the first mainframe implementation of the Christensen Protocol, in MacLisp, by Ed Barton, called LMODEM. Then Gail Zacharias developed MMODEM, USQ, HEXFIY, COMIFY, MAKLBR, DE-LBR and others, some of which were modified for use on TOPS-20 systems. Bill Westfield wrote the original and invaluable MODEM program for TOPS-20, which has recently been overhauled into TMODEM. Disk space was inherently limited on MIT-MC, and when the Macsyma Consortium was dissolved at the end of September, 1983, SIMTEL20 at White Sands Missile Range (WSMR) was already online and had disk space to spare on the required 176MB RP06 boot disk. (SIMTEL20 is a contraction of the name of the branch which then owned the machine, SIMulation and TELeprocessing, DECSYSTEM-20.) During that month, the CP/M collection was moved from MIT-MC to the RP06, designated as the MICRO: structure, on SIMTEL20. Already purchased for a closely related project, the then named DARCOM Microcomputer Software Sharing System (DMSSS), were the entire sets of the CPMUG, SIG/M, and PC/BLUE distributions, which were uploaded as-is to MICRO:. Since then we managed to get placed on the tail end of the regional distribution of both the SIG/M and PC/BLUE update sets which periodically extend both of those collections. As this was all going on, it became evident that a collection of Unix/C versions of the CP/M utilities would be required and that collection was started. That collection has since come under the sponsorship of another organization within the Army Materiel Command (AMC) to which WSMR belongs. That organization, Logistics Systems Support Activity, LSSA, provided the funds for the 512MB disk drive known as PD:, to which all the collections residing on the out-grown MICRO: structure were moved in November, 1985. In November, 1984, Rick Conn volunteered to start the extremely popular Ada Software Repository, originally on PS: as there was no room on MICRO:, and then moved to PD: when that device came online. As with the CP/M archives in PD: being considered the best and most recent, the MSDOS archives are also in the process of being similarly organized in PD:, with files culled from the latest releases of the PC/BLUE collection as well as the INFO-IBMPC collections on ISI-B and Pete Galvin's collection on UTEXAS-20. When the CP/M collection first started, there was only one directory with subdirectories, and several not-necessarily CP/M-related directories lived under that tree. Recently, a new top-level directory was created on PD:, named PD:. Now those generic subdirectories in PD:, PD:, and PD: are being moved to that new directory tree. The original INFO-CPM list was maintained on MIT-MC until 1983 and then moved to BRL, where it was maintained by Ron Natalie for a short while. Ron, who has been the maintainer of INFO-MICRO, among other lists, drafted Dave Towson to maintain the INFO-CPM list on AMSAA. Dave has been continuously maintaining the list since November 1983, periodically rewriting and distributing the SIMTEL20 Archive Users Guide, commonly referred to as the "Archive Blurb" and answering numerous user requests for information on access to the SIMTEL20 collections. As the subscription list to INFO-CPM grew, it was gatewayed into the USENET community, first as fa.info-cpm, and now as a two-way newsgroup, net.micro.cpm. Later, members from other communities joined the list from CSNET, BITNET, and others. Meanwhile, new files and entire collections were added to the SIMTEL20 archives and announced to the INFO-CPM list. Access to these files was inherently limited to those with Internet FTP access to SIMTEL20, unless some kind soul volunteered to mail selected files on request. Recently, there was a flurry of messages pleading for some form of automated access to the SIMTEL20 archives via net mail. About two weeks ago, while reading these pleadings while on travel in the mountains of Colorado, I said that all the pieces were falling into place to be put together to provide that service. Maybe it was the altitude that made me say that, but everything eventually did fall into place in the two weeks since then. A Mail File Server was written in C using a beta version of an about to be released compiler for TOPS-20 systems. If it wasn't for the quick turnaround on reported bug fixes by the two principal maintainers of that compiler and run-time library, Ken Harrenstien and Ian Mackey at SRI-NIC, this program could not have been developed in such a short time by a person whose only other claim to fame in C programming is one other C program he co-authored two years ago. The original concept for this service came from a similar service developed by Jack Dongarra of the Argonne National Laboratory and Eric Grosse of AT&T Bell Laboratories called NetLib, which is available from ANL-MCS for mail access into its collection of well-indexed and documented high quality public domain mathematical software routines. Their work was supported, in part, by the National Science Foundation. From their sources came that part of the package which extracts the requestor's return address from the request file. The SIMTEL20 version of this service has been in beta test for almost two weeks now, with new features added and many bugs fixed since then. While credits are being handed out, I wish to thank Matt Kimmel for checking out access from the BITNET side, and Eric Hildum from the USENET side. And, to Keith Petersen, Dave Towson, Bernie Eiben, Rick Conn, and Mark Crispin for participating in a lively discussion of the principles of operation of this service. Now, before I bombard you with details on how to access the files, let me caution you that this system is experimental. There is no such thing as finding the "last" bug in any program. Furthermore, I sit in awe and fear that even selective and judicious use of this system by the potential audience this message will eventually reach may overload this machine or some of the fragile mail links between hosts on the various networks connecting us all together. This means that those of you already with FTP access to SIMTEL20 must not use this service and continue using FTP. There is no blocking mechanism in place right now, but I will consider taking the time to install one if you choose to ignore this request. Those of you on USENET, BITNET, and CSNET hosts should consider appointing one point of contact through which you should funnel your requests and the reconstructed files from the replies from this service should be made available to all your local users. This particularly applies to the HELP, INFO, and BOOTSTRAP messages and the files they point to. This message is being sent only to the readers of INFO-CPM so that we can gauge the impact on the system. Please do not redistribute this message to any other mailing list or newsgroup. Their time will come. What follows is the message you get in response to the SEND HELP command... Enjoy! Frank -------------------- HOW TO ACCESS THE SIMTEL20 ARCHIVES VIA NET MAIL To obtain one or more files by netmail from the public domain archives kept on SIMTEL20.ARPA, send a message to: ARCHIVE-REQUEST@SIMTEL20.ARPA, or via uucp: ...!seismo!simtel20.arpa!archive-request ...!ucbvax!simtel20.arpa!archive-request ...!uw-beaver!simtel20.arpa!archive-request The message body must contain lines beginning with the keyword SEND, one SEND line for each file requested. Case is not significant. The general syntax of a SEND line is: SEND format filename In general, a filename consists of the following components: device:file.type.generation "device:" is usually PD:, and the combination of PD: is expected unless an alias has been advertised of the form "alias:", which takes the place of both device and directory fields. The generation field may be left off and defaulted to the highest generation number. "file.type" follows the usual filenaming conventions. In all formats listed below, if the file to be sent is larger than 55K, the file is sent in numbered parts. The parts must be reassembled in order and edited to remove any headers, preface, and trailers before the process can be reversed to reconstruct the original file. Allowable formats are: SEND HELP This file you are reading now. SEND INFO A detailed description of the SIMTEL20 Archives, which includes this file, pointers to certain key files, and descriptions of various file transfer programs and related utilities. SEND BOOTSTRAP A brief quick reference listing of filenames of the key utilities used to reconstruct files sent by the compression and encoding techniques listed below. SEND DIR filespec This format returns a CRC list of the requested files, and is the only format which allows wildcard filenames (but not wildcard directory names). The list is sent as an ASCII text file. The wildcard characters are "*" and "%". The asterisk means any number of characters, while the percent sign means exactly one character. Either or both may appear in any combination in either or both the file or type fields, while only the asterisk may appear in the generation field. SEND RAW filename If the file is ASCII, it is sent as-is, regardless of size. This format is the least efficient over network and mail gateway resources. Use this format only if you absolutely must to get yourself bootstrapped. Then please use one of the other formats listed below. With the four formats listed below, if the file is ASCII and under 25k characters, it is sent as-is, as if RAW format was requested. Binary files are always processed according to the requested format. However, a request for ARC or SQ processing of files with type .ARC, .LBR, or .%Q% is ignored and the original file is either uuencoded or hexified (if possible), according to the requested format. If the file was not sent RAW, a short preface is inserted at the front of the message describing the process actually taken and a CRC entry describing the original file. SEND ARE filename or SEND filename The original file is made into a uuencoded ARC file. SEND ARH filename The original file is made into a hexified ARC file if the ARC file is under 64K bytes long. Otherwise, an apology is returned instead of the requested file. SEND SQE filename The original file is made into a uuencoded SQueezed file. SEND SQH filename The original file is made into a hexified SQueezed file if the Squeezed file is under 64K bytes long. Otherwise, an apology is returned instead of the requested file. To get started in finding your way around the SIMTEL20 archives, send another request: SEND INFO The ARCHIVE-REQUEST address is serviced by a batch job that reschedules itself one hour after it completes the current pass. That frequency is subject to change. ==================== ------- 4-Sep-86 12:01:51-MDT,664;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 4 Sep 86 12:01:44-MDT Received: from ll.arpa by AMSAA.ARPA id a023413; 4 Sep 86 13:19 EDT Date: Thu 04 Sep 1986 13:15:15 EDT From: SAGE@LL.ARPA MMDF-Warning: Parse error in preceding line at AMSAA.ARPA Subject: Peter Kendell's Address To: INFO-CPM@AMSAA.ARPA Cc: sage@ll.ARPA Message-ID: I still have heard nothing from Peter Kendell, whose request for information got swallowed up in a system crash here. Peter, are you out there? My mailing address is Jay Sage, MIT Lincoln Lab, PO Box 73 Lexington, MA 02173-0073 USA. 5-Sep-86 04:10:46-MDT,1131;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 5 Sep 86 04:10:37-MDT Received: from brl-smoke.arpa by AMSAA.ARPA id a005142; 5 Sep 86 5:32 EDT Received: from USENET by SMOKE.BRL.ARPA id a005346; 5 Sep 86 5:30 EDT From: Dustin Clampitt Newsgroups: net.micro.apple,net.micro.cpm Subject: Re: Home Accounting? Message-ID: <171@lpi.UUCP> Date: 3 Sep 86 18:49:03 GMT To: info-cpm@AMSAA.ARPA In article <2fcfc504.46@apollo.uucp>, nazgul@apollo.uucp (Kee Hinckley) writes: > > I highly recommend "Time is Money (personal)" from Turning Point Software > (11A Main St., Watertown, MA 02172). It's easy, it's quick and it's......... .......not available for CP/M. I just called them, this product is for apple and IBM only. I need a product like this (home accounting) for cp/m or zcpr3/zrdos. Please mail me any suggestions you might have. Thanks, Dustin Clampitt -- Dustin Clampitt "Is it Saturday yet?" ..!decvax!linus!axiom!lpi!jdc [][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][] 5-Sep-86 04:14:47-MDT,1242;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 5 Sep 86 04:14:28-MDT Received: from brl-smoke.arpa by AMSAA.ARPA id a005195; 5 Sep 86 5:46 EDT Received: from USENET by SMOKE.BRL.ARPA id a005506; 5 Sep 86 5:35 EDT From: David Shanks Newsgroups: net.lang.f77,net.micro.pc,net.micro.cpm Subject: Fortran compiler quality query Message-ID: <107@atelabs.UUCP> Date: 2 Sep 86 20:36:47 GMT To: info-cpm@AMSAA.ARPA Can anyone out there tell me anything good or bad about the Utah Fortran compiler from Ellis Computing that I see advertised in Byte? This compiler (along with compilers for Cobol and Pascal, and intrepreters for Basic and Pilot) is advertised at $39.95. Normally I'd guess that it's a low quality product (you usually get what you pay for) but this company has been around for several years marketing the same thing for CP/M (called Nevada Fortran). I also know that there ARE some good quality compilers out there for a low price. Does anyone know if this is one of them? Thanks. -- Dave Shanks ..!tektronix!tessi!atelabs!cds AT&E Laboratories 1400 NW Compton Suite 300 Beaverton, OR 97006 (503) 690-2000 5-Sep-86 06:47:18-MDT,1276;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 5 Sep 86 06:47:07-MDT Received: from mitre.arpa by AMSAA.ARPA id a007440; 5 Sep 86 8:17 EDT Full-Name: Jeff Edelheit Organization: The MITRE Corp., Washington, D.C. Return-Path: Received: from localhost by ernie.mitre.org (2.2/SMI-2.2) id AA13566; Fri, 5 Sep 86 08:19:43 edt Message-Id: <8609051219.AA13566@ernie.mitre.org> To: jdc%lpi.uucp@BRL.ARPA Cc: info-cpm@AMSAA.ARPA Subject: Re: Home Accounting? In-Reply-To: Your message of 3 Sep 86 18:49:03 GMT. <171@lpi.UUCP> Date: Fri, 05 Sep 86 08:19:21 -0500 From: edelheit@MITRE.ARPA Dustin - If you are interested in tracking expenses by user-defined catagories, just grab any dbms (like dBase) and set up a few fields like ck. no., date, payee, amount, and catagory. Once your check register(s) are loaded, you can just sum by catagory. I have been doing this for about 5 years and it works like a champ. (The only problem comes up when my wife says things like "We spent HOW MUCH at the supermarket last year!!!???") Regards, Jeff Edelheit (edelheit@mitre.arpa) The MITRE Corporation, 1820 Dolley Madison Blvd. McLean, VA 22102 (703) 883-7586 5-Sep-86 09:21:21-MDT,1331;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 5 Sep 86 09:19:55-MDT Received: from wiscvm.arpa by AMSAA.ARPA id a011867; 5 Sep 86 10:30 EDT Received: from (FISHER)RPICICGE.BITNET by WISCVM.WISC.EDU on 09/05/86 at 09:31:32 CDT Date: 5 September 86 10:30-EST From: FISHER%RPICICGE.BITNET@wiscvm.ARPA To: INFO-CPM@AMSAA.ARPA X-Acknowledge: Subject: BITNET mail follows Date: 5 September 1986, 10:19:08 EAS From: FISHER at RPICICGE To: INFO-CPM at AMSAA.ARPA Re: Previous request-for-information about P2DOS Many thanks to the those who responded. As pointed out by "Bernie " my only real problem was that the .COM file created using the utilites provided in the .LBR is just a touch to large. A LOAD/SAVE 14 restores the file to its actual and proper size. After that it suddenly worked just fine.... ...Well, almost: If others attempt to install P2DOS, be forwarned that as distributed the search path table is stored at 0040H and following. This area is designated as reserved for BIOS use (not for the BDOS). So, confirm first that your BIOS does not use this scratch area or move the search path table elsewhere. (My H89 BIOS--vanilla from Heath--does use it :-) John S. Fisher FISHER@RPICICGE.BITNET 5-Sep-86 19:48:11-MDT,830;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 5 Sep 86 19:17:44-MDT Received: from xerox.arpa by AMSAA.ARPA id a000498; 5 Sep 86 20:40 EDT Received: from Burger.ms by ArpaGateway.ms ; 05 SEP 86 15:15:36 PDT Sender: Larry_Shilkoff.ElSegundo@xerox.ARPA Date: 5 Sep 86 13:02:13 PDT (Friday) Subject: Re: C128 info From: Larry_Shilkoff.ElSegundo@xerox.ARPA To: prindle@NADC.ARPA cc: Larry_Shilkoff.ElSegundo@xerox.ARPA, info-cpm@AMSAA.ARPA, singpang%hlerul5.BITNET@wiscvm.ARPA, wiscvm@NADC.ARPA In-Reply-to: prindle%nadc:ARPA:Xerox's message of 3-September-86 (Wednesday) 7:29:27 PDT Message-ID: <860905-151536-1257@Xerox> Can somebody tell me all the CP/M formats (double sided as well as single sided) the Commodore 128 will read and convert to run. Larry 5-Sep-86 21:34:45-MDT,7571;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 5 Sep 86 21:34:17-MDT Received: from simtel20.arpa by AMSAA.ARPA id a000796; 5 Sep 86 22:40 EDT Date: Fri, 5 Sep 1986 19:55 MDT Message-ID: Sender: KPETERSEN@SIMTEL20.ARPA From: Keith Petersen To: Info-Cpm@AMSAA.ARPA Subject: Assembling SYSLIB with ZAS and Z80ASM (SLR) Reply-To: SAGE@LL.ARPA Relayed from my RCP/M...I've had complaints from users about not being able to assemble the new SYSLIB, Z3LIB and VLIB wihout purchasing the ZAS assembler. It used to be possible to use M80/L80. This file tells about one alternative. --Keith --cut here--ZAS-SLR.DOC--cut here-- ASSEMBLING SYSLIB WITH ZAS AND Z80ASM (SLR) Jay Sage September 4, 1986 I was moved to write these comments after reading Richard Conn's article on the libraries (SYSLIB, Z3LIB, and VLIB) in Micro/Systems Journal. In that article he states that ZAS is the only assembler that is capable of assembling the new version 3.6 release of SYSLIB. This statement seemed both odd and self-serving, odd because ZAS is always promoted as being compatible with other standard assemblers and self-serving because Conn is now an employee of Echelon, which distributes ZAS. I began to do a little investigating. Please understand that I am generally a strong supporter of Echelon, the company marketing the Z-System and its support programs. They are, I believe, the last hope for 8-bit CP/M-type computers, and we should support them by buying their products and encouraging our friends to do the same. However, ZAS has been a sticking point for me. I formed a less than enthusiastic opinion of ZAS at the beginning and tried to help the author make an honest Z-System program out of it. Unfortunately, its subsequent development has done nothing to change my original opinion (more on that below). Once the superbly written, high performance assembly-language tools from SLR Systems became available at a comparable (slightly higher) price, I saw no reason to settle for the mediocrity of ZAS. If Conn had said in the article that the SYSLIB source was written to be assembled using ZAS and might require slight modifications for other assemblers, I would not be writing this comment. I found it hard to believe that Z80ASM would have any significant problem assembling SYSLIB, so I gave it a try. The complete assembly of 189 source modules to Microsoft-format REL files took only 11 minutes and 25 seconds on my Ampro floppy-based system, an average of 3.6 seconds per module (considering the tremendous disk thrashing required to read 189 source files and write 189 REL files, things would have been much faster with a hard disk). It turned out that very strictly speaking Conn was right. There were five files, the ones dealing with library management (SLUDIR, SLUOPEN, SLUCLOSE, SLUREAD, and SLUINIT), that produced error messages. The reason was their use of ZAS's idiosyncratic ".IN" insert pseudo-op. If one spends a moment with a text editor and changes the five instances of ".IN" to ".INCLUDE", then Z80ASM works beautifully. Knowing Steve Russell of SLR, I would not be surprised if the next version of Z80ASM recognizes the ".IN" pseudo-op. It already tolerates ZAS's peculiar requirement of square brackets where other assemblers use normal parentheses. Changing ".IN" to "MACLIB" and putting in the ".Z80" directives might even make M80 work (I did not try that). If anyone reading Conn's comment thought that he should buy ZAS just to be able to work with the SYSLIB source code, he was seriously misled. I am sure that almost any assembler using Zilog mnemonics can be made to work with very little effort. Since the code appears to use no Zilog-only instructions, one could probably even convert the source back to the Intel mnemonics in which Conn wrote the original routines and use an Intel assembler. Having gone through the assembly process with Z80ASM, I was now curious to see how ZAS would perform. I got out a copy of ZAS version 2.3. Since ZAS does not support internal script files and multiple assemblies as Z80ASM does, I prepared a ZEX script file to perform the task. At first I wrote the script to invoke ZAS for each module. Then it occurred to me that it was unfair to force ZAS to reload for each module when Z80ASM only had to load once. So I decided to use the ZCPR "GO" command for all but the first module. For some reason I decided first to make sure that ZAS could be rerun using "GO", as Z-System programs generally should. I tried it manually on a pair of files with the command line "ZAS FILE1;GO FILE2". It seemed to work fine. I ended up with two appropriately named REL files, but something about the ZAS output message made me suspicious -- both files were reported as having the same number of lines, symbols, etc. Sure enough -- ZAS messed up. It gave the appearance of working but in fact did not, the worst kind of failure. I don't know exactly what ZAS is doing, since the second output REL file did not correspond to either the second or the first source file. One thing is for sure. The author of ZAS still does not fully understand the principles of Z-System programming. [My first disillusionment with ZAS came when I tried for many months to get the author to make it support the ZCPR3 program error flag (I even sent the code to do it). Steve Russell grasped the principle immediately and implemented it quickly and correctly; he even made the logical extensions of the concept to CP/M3 (set CP/M3 error flag) and CP/M2.2 (kill $$$.SUB submit file).] ZAS apparently relies on the initial loading of ZAS.COM from disk to initialize some data space. Programs that are to work under the "GO" command must, obviously, perform all required initializations in code. Otherwise the buffers, flags, and file control blocks will not necessarily be in their initialized state when the program is rerun using "GO". With a ZEX script that reloaded ZAS for each assembly (I had no choice), ZAS took 43 minutes and 30 seconds to assemble SYSLIB, nearly four times as long as Z80ASM. Carrying out the five source changes to make SYSLIB compatible with other assemblers, including Z80ASM, would take much less than the 22-minute time difference. One final note on the SYSLIB code itself. There are some unfortunate inconsistencies in the code due to reliance on the truncated external references of the Microsoft REL format. The SLR assemblers can optionally generate special SLR-format REL files (only the SLR linker can process these) that, among other advantages, support 16-character external names. When assembling SYSLIB to SLR-format REL files, however, one discovers that the external and internal names of some routines in SYSLIB are not consistent. The module S0FILEIO.Z80 makes reference to the externals "FI$CLOSE" and "FO$CLOSE". However, the module SFILEIO, which defines these references, specifies the public names as "FI$CLOS" and "FO$CLOS". With Microsoft truncation of externals to 6 or 7 characters (I don't know which ZAS does), these are equivalent. In making the SLR versions of the libraries (SYSSLR.REL, Z3SLR.REL, and VSLR.REL), I had to correct these inconsistencies. 6-Sep-86 14:36:20-MDT,7885;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Sat 6 Sep 86 14:36:00-MDT Received: from simtel20.arpa by AMSAA.ARPA id a003337; 6 Sep 86 15:38 EDT Date: Sat 6 Sep 86 13:39:33-MDT From: Rick Conn Subject: Some data on ZCPR 3.3 To: info-cpm@AMSAA.ARPA cc: sage@LL.ARPA Message-ID: <12236834507.7.RCONN@SIMTEL20.ARPA> The New Z System by Richard Conn, 6 Sep 1986 I have been working quietly on the development of the new Z System for quite some time, and I feel that I must speak out now on what I am doing so that people will know the true story. This presentation is short and not complete, but it is enough to answer some basic questions without taking too much of my time away from the development activities. Why create a new Z System? -------------------------- First of all, why am I creating a new Z System? There are many reasons: 1) I have studied the old Z System for over two years now, reviewing it for flaws and weaknesses. From the beginning, I have stated that the Z System is evolutionary, and I have enough new ideas now to implement the next step in this evolution. 2) I have been learning many new things about other environments, including Ada Programming Support Environments (APSEs), UNIX, SUN window-based systems, TOPS-20, VAX/VMS, and Symbolics workstations. I have seen many good ideas that I would like to incorporate into my personal computer environment, the Z System. 3) My next real goal is the development of a banked Z System followed by a multitasking Z System. An improvement in the current non-banked Z System is a logical step along the way, giving me a platform from which to experiment with some of the new ideas before fully incorporating them into the new systems. ZCPR 3.3 is not a goal, but is a milestone along the road to a goal. 4) My needs have changed and are continuing to change, and the old Z System no longer meets my needs. I have to change the system in order to continue advancing toward my other goals. At a recent talk I gave at the Trenton Computer Festival, someone asked me if I plan to move over to the IBM community. If I was motivated by profit to a large extent, my answer would obviously have been yes. But my principal motivation is to learn and grow and to have fun doing it. The money is a very nice side effect, but it is not the driving side effect. I definitely intend to keep learning through the Z System. The Z System, coupled with the very rich computer environment I am accessing through my communications system, has enough potential to meet my needs for many years to come. New Standards ------------- Good software engineering principles and common sense indicate that a lot of benefit can be derived through standards. The evolving ZCPR 3.3 and Z System now have a number of standards going for them: 1) a common language, implemented by the ZAS assembler 2) a common support library, implemented by SYSLIB, Z3LIB, and VLIB 3) a common format for all assembly language programs, implemented by PPAL - the Pretty Printer for Assembly Language 4) a common operating system and support base, implemented by ZCPR3 and ZRDOS 5) a common documentation format which allows easier upgrading of the documentation as the programs change; this system is for both hardcopy (MAN) and online (HELP) mediums 6) a common configuration management system, CONFIG, which allows users to easily identify their configuration and determine if all of their programs are current 7) page-relocatable structures for system segments, ZCPR 3.3 itself, and ZRDOS, which server to further support transportability and make installation easier 8) a very robust communications protocol, supporting packet sizes from 1 data byte to 4K data bytes You will see all of these in the months to come. The Libraries ------------- One key point to make here is that I purposely did not mention a common binary structure, like the Environment Descriptor. The Environment Descriptor is not a standard, but the interface to it, namely Z3LIB and VLIB, is. This was purposely done so that future growth would be supported. As the Z System evolves, it will probably be necessary to delete old features which are no longer needed in favor of new features which provide new capabilities. If the binary structures, like the Environment Descriptor, are to preserved, then the growth will be hampered by the lack of availability of space in which to implement the new features. By standardizing on the interface to the Environment Descriptor and not the structure of the descriptor itself, then the Environment Descriptor can take any desired form without concern for the impact on other programs. Specifically, ld hl,envadr ; get base address of env ld de,offflag ; get offset to a flag add hl,de ; point to the flag ld a,(hl) ; get the flag value would be severly impacted if the structure of the Environment Descriptor changed, but a call like: ext getflag ; reference library routine to get flag ... call getflag ; return flag in A would not be impacted at all by such a change. The library containing the GETFLAG routine would be impacted, but it is a lot easier to change one module in a library and reassemble 100 programs than it is to track the necessary changes in, edit, and then reassemble 100 programs. With one exception, the routines in the new Z3LIB for ZCPR 3.3 have the same names and interfaces as the routines in the old Z3LIB. Conversion is simple - reassembly is all that is required. Unfortunately, many programmers have not yet learned this lesson. They continue to write code which does not use the libraries. Imagine the work that will be required to go through their programs, modifying the references in order to be compatable with the banked ZCPR3. Imagine them going through the work again for the multitasking ZCPR3, and again and again as ZCPR3 continues to evolve. Thanks to Echelon, ZCPR 3.3 is still compatable at the binary level in terms of the Environment Descriptor. Certain values have been replaced with others, so changes will still be necessary, but many of the key values have stayed in the same places with the same meanings. My original approach was to free up all of the dead space left by the removed values, making more room at the end for growth, but Echelon convinced me that the impact on programs written by those who didn't understand the basic principle of the libraries would be devastating. Thanks to the new design, it only took me 3 hours to convert back with no loss of functionality -- yet another benefit from the new structured design of the system -- but I can guarantee that the future systems will not be converted in this manner. If everyone starts thinking in terms of the libraries, the future growth of the Z System is assured. If people cling to the old ideas of not using the libraries, then it is clear that growth will be curtailed. The Bottom Line --------------- I am moving forward with the development of the new ZCPR 3.3 and the new Z System. As you can see, there are many changes in it, and I have barely skimmed the surface. I will move ahead and release it only when I am satisfied that it is usable to others. Documentation must go with the release, so the release will not take place until the documentation is ready. My goal is to meet my needs, as outlined above, and this goal will be met. I thank those of you who have been supportive in the efforts of Echelon and myself, and I sincerely hope that you will share in my enthusiasm for the new ZCPR 3.3 when I release it to you. Rick Conn ------- 6-Sep-86 15:12:56-MDT,5971;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Sat 6 Sep 86 15:12:39-MDT Received: from simtel20.arpa by AMSAA.ARPA id a003332; 6 Sep 86 15:37 EDT Date: Sat 6 Sep 86 13:38:42-MDT From: Rick Conn Subject: Response to Sage's comments To: info-cpm@AMSAA.ARPA cc: sage@LL.ARPA Message-ID: <12236834351.7.RCONN@SIMTEL20.ARPA> ZAS (from Echelon)/Z80ASM (from SLR), and the Z System Libraries by Richard Conn, 6 September 1986 Jay Sage's recent comments in the file ZAS-SLR.DOC are understood, although somewhat in error, and I feel that it is necessary to clarify my position on the subject. First, as Jay admits, there are no errors in the article. ZAS is the only assembler (to my knowledge and his) that can assemble the libraries without error at this time. Granted, I'll take Jay's word for it that five library modules (LUDIR, LUOPEN, LUCLOSE, LUREAD, and LUINIT) can be modified in a minor way to allow Z80ASM to assemble them. What Jay doesn't know is that the new Z3LIB requires all 70+ modules to be edited and reassembled in order to use the SLR assembler with them. Second, Jay is totally wrong and uninformed about my relationship with Echelon. I am not an employee of Echelon and have never been an employee of Echelon. I receive royalty checks from Echelon for the sale of my books and software and I work closely with them. The sale of ZAS has no impact whatsoever on my income. Obviously, the sale of the libraries does, since the libraries constitute a product line of which I am the author. I really resent Jay's insinuations and feel they reflect very poorly on him. Third, ZAS is the only assembler I use today. I use it for the following reasons: (1) it meets my needs, (2) it represents a standard language that Echelon and I have some influence on, (3) it is reliable in the way I use it, and (4) it is supported. I have been an advocate of Ada for many years now, and the reasons for my love of Ada include the same reasons given in the previous sentence (with the exception that I don't have as extensive influence on the development of Ada as I do of ZAS). I have seen the benefits of having a standard language and am completely sold on them. Among many other reasons, having a standard language like ZAS allows us to change the language definition as our needs change, and I definitely have such changes in mind for the future. Fourth, I have nothing whatsoever against SLR or any other company or its products. I have heard others say that the SLR tool is a fine tool, and I have no reason to doubt such a statement. I have never used the SLR Z80ASM tool, but this may change since SLR contacted me and wanted to send me a copy. Fifth, we are not at an impass. Taking a lesson from the Ada community, we see Ada as a standard language with over 50 different compilers for it. All of these compilers implement the same language, which means that there are no subsets or supersets, and I can write an Ada program on any computer using any one of these compilers and port this program to any other computer using any other of these compilers. Porting the program amounts to placing the source code on the target system, compiling, and running. No change to the source code at all. But these compilers are not all identical. Some are faster than others, some generate more efficient code than others. I want to see the same thing happen in the Z System community. Any source code program can be ported to any Z System machine and assembled with the standard assembly language. This was my goal in standardizing on ZAS from the beginning. Echelon will soon be offering an implementation of C, which I haven't seen yet, but if it meets the four requirements outlined above, I imagine that I will adopt it in the same way. This action does not close the Z System market in any way, just like Ada did not close the compiler market. The vendors who wanted a piece of the Ada action simply (actually, after enormous investments) marketed their own Ada compilers which were validated. Validation meant that each compiler was approved by the US Government Ada Joint Program Office after passing through a suite of over 4000 tests to assure that it compiled Ada programs with no supersets or subsets. This test suite was not exhaustive, and some minor differences exist in the compilers, but the test suite is under constant revision to make it progressively better. Echelon supports something called the "Z Team", which is a team of people developing products for the Z System. The authors of ZAS, DSD, ZDM, the new C compiler, etc., as well as myself are on this team. We receive our own mailings from Echelon as a team and are kept up to date with each other's activities. We also receive internal data on what Echelon is up to. I understand that Echelon and SLR, which is the subject of this particular message, discussed the possibility of SLR joining the Z team (ie, Echelon carrying their product), but an agreement was not reached. The Z Team works well together overall. If SLR or any other company wants to join in Echelon's adventure with the Z System, there is no reason that yet another team, one concerned with the Z System standard language (which is now ZAS only) and other details of the Z System development, can be formed. It is not appropriate to use the Echelon Team for this purpose, since companies that may be competators of Echelon may be involved. The Z System as a standard goes beyond specific companies. With a standard language, call it ZA, then ZAS and Z80ASM could become products which compete with each other fairly and we could still have ONE language for the Z System. One language is what I want, and I don't care if it is just ZAS or a group of assemblers made by a group of companies. ------- 6-Sep-86 15:34:07-MDT,1484;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Sat 6 Sep 86 15:34:00-MDT Received: from simtel20.arpa by AMSAA.ARPA id a003524; 6 Sep 86 16:05 EDT Date: Sat 6 Sep 86 14:07:19-MDT From: Rick Conn Subject: New files in ZSYS To: info-Cpm@AMSAA.ARPA Message-ID: <12236839562.7.RCONN@SIMTEL20.ARPA> Thanks to Keith for uploading most of them. PD: Bytes(SZ) AUTOZINS.CCP.1 1420(7) -- also in PD: DU312.LBR.1 64896(8) -- also in PD: PPAL.DOC.1 11755(7) -- also in PD: VF41.IQF.1 11008(8) -- also in PD: VF41H.LBR.1 27776(8) -- also in PD: ZAS-SLR.DOC.1 7613(7) -- also in PD: ZAS-STD.DOC.1 5564(7) -- also in PD: ZHELPR16.RQS.1 2688(8) -- also in PD: ZSTD.DOC.1 7484(7) -- also in PD: AUTOZINS.CCP is about modifying the old ZCPR 3.0 to install Z3 tools it loads; this will be unnecessary with ZCPR 3.3 DU312.LBR and VF41H.LBR and new versions of DU3 and VFILER PPAL.DOC is short doc on PPAL (Pretty Printer for Assembly Language) for the beta testers ZAS-SLR.DOC is Jay Sage's message in response to my article in Microsystems ZAS-STD.DOC is my response to ZAS-SLR.DOC ZSTD.DOC is some information on the new ZCPR 3.3 ZHELPR16 is the latest list of Z System helper volunteers ------- 6-Sep-86 15:55:07-MDT,1467;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Sat 6 Sep 86 15:55:00-MDT Received: from simtel20.arpa by AMSAA.ARPA id a003654; 6 Sep 86 16:53 EDT Date: Sat 6 Sep 86 14:41:14-MDT From: Rick Conn Subject: New file in ZSYS To: info-cpm@AMSAA.ARPA Message-ID: <12236845735.7.RCONN@SIMTEL20.ARPA> Sorry if this is a repeat ... PD: Bytes(SZ) AUTOZINS.CCP.1 1420(7) -- also in PD: DU312.LBR.1 64896(8) -- also in PD: PPAL.DOC.1 11755(7) -- also in PD: VF41.IQF.1 11008(8) -- also in PD: VF41H.LBR.1 27776(8) -- also in PD: ZAS-SLR.DOC.1 7613(7) -- also in PD: ZAS-STD.DOC.1 5564(7) -- also in PD: ZHELPR16.RQS.1 2688(8) -- also in PD: ZSTD.DOC.1 7484(7) -- also in PD: AUTOZINS.CCP is about modifying the old ZCPR 3.0 to install Z3 tools it loads; this will be unnecessary with ZCPR 3.3 DU312.LBR and VF41H.LBR and new versions of DU3 and VFILER PPAL.DOC is short doc on PPAL (Pretty Printer for Assembly Language) for the beta testers ZAS-SLR.DOC is Jay Sage's message in response to my article in Microsystems ZAS-STD.DOC is my response to ZAS-SLR.DOC ZSTD.DOC is some information on the new ZCPR 3.3 ZHELPR16 is the latest list of Z System helper volunteers ------- 6-Sep-86 16:29:51-MDT,12439;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Sat 6 Sep 86 16:29:19-MDT Received: from simtel20.arpa by AMSAA.ARPA id a003380; 6 Sep 86 15:40 EDT Date: Sat 6 Sep 86 13:42:02-MDT From: Rick Conn Subject: Some info on PPAL To: info-cpm@AMSAA.ARPA cc: sage@LL.ARPA Message-ID: <12236834960.7.RCONN@SIMTEL20.ARPA> The following is the documentation now being used by PPAL's (PPAL = Pretty Printer for Assembly Language) beta testers. I don't know when or how PPAL will be released yet, but PPAL is working fine right now. I ran it on all of Z3LIB the other day without any problems. Rick ;%BEGIN 0 ;%Program: PPAL ;%Author: Richard Conn ;%Version: VERS equ 2 ;%Date: 3 Sep 1986 ;%Revision History: ;1. 1 Sep 86, Richard Conn ; Initial beta-test release ;2. 3 Sep 86, Richard Conn ; Fixed Z3INS compatability problem ; Created LSy option to control colons after labels of MACRO, SET, ; and EQU ; Placed IF/ELSE/ENDIF at same indentation level ; Change Iy option to IIy option ; Added IMy option for MACRO/ENDM indentation ; Added directives I+ and I- for manual increment and decrement of ; indentation level ; Fixed input line counting problem ;%Invocation: PPAL file_list [directive_list] ;%Index: Pretty Assembler ;%Index: PPAL ;%Index: Pretty Printer ;%Description: ; PPAL is a Pretty Printer for Assembly Language for the Z System. ;Its purpose is to reformat assembly language source programs in order to ;have all Z System programs conform to a standard structure. PPAL is highly ;configurable, accepting directives from both the command line and the source ;code itself, so that PPAL may be used to format programs in different ways ;for a variety of standards. ; Directives for specific configuration of the pretty printing process ;may be presented on the command line or within the body of the code in ;special comment lines, beginning with ";#". The following directives are ;recognized. In each general case (like, Au), the first letter indicates the ;directive name, and the following letters indicate types of characters which ;may be specified; specifically: ; o - option chars specific to the directive ; u - case indication, U for Upper-case, L for Lower-case, ; X for unchanged ; y - yes/no indication, Y for Yes, N for No, X for unchanged ; ; Au - controls the case of operands (arguments) ; AU makes non-quoted alphabetic argument characters upper-case ; AL makes non-quoted alphabetic argument characters lower-case ; AX leaves the case of argument characters unchanged ; By - remove blank lines ; BY (yes) turns on removal of blank lines ; BN (no) turns off removal of blank lines ; BX (unchanged) is the same as BN ; Cou, Coy - comment line formatting (a comment line is a line beginning ; with a semicolon, as opposed to an embedded comment) ; CWy controls removal of the space character after the ; semicolon ; CWY (yes) removes the space after the semicolon if a ; space is present, else no change ; CWN (no) inserts the space after the semicolon if no ; space is present, else no change ; CWX (unchanged) makes no change ; CFu controls case of the first character in the comment line ; CFU makes the first character upper-case ; CFL make the first character lower-case ; CFX leaves the case of the first character unchanged ; CAu controls case of all characters in the comment line ; except the first character if CFU or CFL is in effect ; CAU makes all characters upper-case ; CAL makes all characters lower-case ; CAX leaves the case of all characters unchanged ; Eou, Eoy - embedded comment formatting ; ECy controls placement of the embedded comment if it begins ; after field4 (column 33) ; ECY (yes) places embedded comments on the next line ; ECN, ECX (no, unchanged) leaves embedded comments ; on the same line ; EWy controls removal of the space character after the ; semicolon ; EWY (yes) removes the space after the semicolon if a ; space is present, else no change ; EWN (no) inserts the space after the semicolon if no ; space is present, else no change ; EWX (unchanged) makes no change ; EFu controls case of the first character in the comment ; EFU makes the first character upper-case ; EFL make the first character lower-case ; EFX leaves the case of the first character unchanged ; EAu controls case of all characters in the comment ; except the first character if EFU or EFL is in effect ; EAU makes all characters upper-case ; EAL makes all characters lower-case ; EAX leaves the case of all characters unchanged ; Ioy - indent lines subordinate to IFs or MACROs ; I+ increases the indentation level by 1 character ; I- decreases the indentation level by 1 character (0 min) ; IIy controls indentation for the IF/ELSE/ENDIF pseudo-ops ; IIY causes all opcodes subordinate to an IF to be ; indented one character; each successive IF ; causes another indentation; ENDIF brings the ; indentation level out; ELSE temporarily brings ; the indentation level out for the ELSE pseudo-op ; only ; IIN, IIX (no, unchanged) causes indentation under IFs ; to not take place ; IMy controls indentation for the MACRO/ENDM pseudo-ops ; IMY causes all opcodes subordinate to a MACRO to be ; indented one character; ENDM brings the ; indentation level out ; IMN, IMX (no, unchanged) causes indentation under ; MACROs to not take place ; Lou, Loy - control format of labels ; LFu controls the case of the first character of a label ; LFU makes the first character upper-case ; LFL makes the first character lower-case ; LFX leaves the case of the first character unchanged ; LAu controls the case of all characters in a label except ; the first character if LFU or LFL is in effect ; LAU makes all characters upper-case ; LAL makes all characters lower-case ; LAX leaves the case of all characters unchanged ; LCy controls the presence of a colon after a normal label ; LCY ensures that there is a colon after each label ; LCN ensures that there is no colon after each label ; LCX has no effect on a trailing colon; if one was ; present in the input, it is present in the output ; LSy controls the presence of a colon after a special label, ; where a "special" label is a label in front of a MACRO, ; SET, or EQU pseudo-op ; LSY ensures that there is a colon after a special label ; LSN ensures that there is no colon after a spec label ; LSX has no effect on a trailing colon; if one was ; present in the input, it is present in the output ; LLy controls the presence of a new line following a label ; LLY places a new line after a label ; LLN, LLX does not place a new line after a label ; L8y controls the presence of a new line following a label ; which is longer than 8 characters ; L8Y places a new line after an 8+ character label ; L8N, L8X does not place a new line after an 8+ ; character label ; Ou - controls the case of opcodes ; OU makes opcodes upper-case ; OL makes opcodes lower-case ; OX leaves the case of opcodes unchanged ; ; In addition to the above directives, four predefined formats ;are available via the Fn directive, where 0 <= n <= 3. The predefined ;formats are: ; F0 - reset all directives to null ; Remove blank lines (B): No ; Comment lines ; First char (CF): Unchanged ; All chars (CA): Unchanged ; Remove Space after ; (CW): Unchanged ; Embedded comments ; First char (EF): Unchanged ; All chars (EA): Unchanged ; Remove Space after ; (EW): Unchanged ; Next line if after col 33 (EC): No ; Indentation ; of IFs (II): No ; of MACROs (IM): No ; Labels ; First char (LF): Unchanged ; All chars (LA): Unchanged ; Colon after label (LC): Unchanged ; Colon after special label (LS): Unchanged ; Line after label (LL): Unchanged ; Line after 8+ char label (L8): Unchanged ; Opcode case (O): Unchanged ; Operand (argument) case (A): Unchanged ; ; F1 - Z System standard format ; Remove blank lines (B): No ; Comment lines ; First char (CF): Unchanged ; All chars (CA): Unchanged ; Remove Space after ; (CW): Unchanged ; Embedded comments ; First char (EF): Unchanged ; All chars (EA): Unchanged ; Remove Space after ; (EW): Yes ; Next line if after col 33 (EC): Yes ; Indentation ; of IFs (II): Yes ; of MACROs (IM): Yes ; Labels ; First char (LF): Unchanged ; All chars (LA): Upper ; Colon after label (LC): Yes ; Colon after special label (LS): No ; Line after label (LL): Yes ; Line after 8+ char label (L8): Yes ; Opcode case (O): Lower ; Operand (argument) case (A): Lower ; ; F2 - special format ; Remove blank lines (B): Yes ; Comment lines ; First char (CF): Unchanged ; All chars (CA): Unchanged ; Remove Space after ; (CW): Yes ; Embedded comments ; First char (EF): Upper ; All chars (EA): Lower ; Remove Space after ; (EW): Yes ; Next line if after col 33 (EC): Yes ; Indentation ; of IFs (II): Yes ; of MACROs (IM): Yes ; Labels ; First char (LF): Upper ; All chars (LA): Lower ; Colon after label (LC): Yes ; Colon after special label (LS): No ; Line after label (LL): Yes ; Line after 8+ char label (L8): Yes ; Opcode case (O): Lower ; Operand (argument) case (A): Lower ; ; F3 - special format ; Remove blank lines (B): Yes ; Comment lines ; First char (CF): Unchanged ; All chars (CA): Unchanged ; Remove Space after ; (CW): No ; Embedded comments ; First char (EF): Upper ; All chars (EA): Lower ; Remove Space after ; (EW): Yes ; Next line if after col 33 (EC): Yes ; Indentation ; of IFs (II): Yes ; of MACROs (IM): Yes ; Labels ; First char (LF): Unchanged ; All chars (LA): Upper ; Colon after label (LC): Yes ; Colon after special label (LS): No ; Line after label (LL): Yes ; Line after 8+ char label (L8): Yes ; Opcode case (O): Upper ; Operand (argument) case (A): Upper ; ; If no directives are given, the format F1 is selected. F1 is always ;selected as the default format, and directives can be used to vary specific ;settings or all settings within this default. ; ; Examples of various forms a label may take on: ; Forms AbCd hello EXEC ; -------- ---- ----- ---- ; LFX, LAX AbCd hello EXEC ; LFU, LAX AbCd Hello EXEC ; LFL, LAX abCd hello eXEC ; LFX, LAU ABCD HELLO EXEC ; LFU, LAU ABCD HELLO EXEC ; LFL, LAU aBCD hELLO eXEC ; LFX, LAL abcd hello exec ; LFU, LAL Abcd Hello Exec ; LFL, LAL abcd hello exec ; ; Directives may be placed in any order with any or no delimiters: ; "LFXLAU" "LFX LAU" "LFX,LAU" ;have the same meanings. This applies to both command lines and embedded ;comments. ; PPAL file1,file2 LFX LAU ; ;#LFX, LAU ; Note that allowing directives embedded in the files they are acting ;on allows one part of the file to take on one format and another part of the ;file to take on another format. ; ; Sample file before processing by PPAL: ; ; ; Sample file to illustrate PPAL ; mymac macro ; if debug ; this is a test ; call print ; db 'debug macro',0 ; else ; call print ; db 'no debug macro',0 ; endif ; endm ; loop: ; if debug ; if debug2 ; call print; this is only a test ; db 'debug2',0 ; else ; call print ; db 'debug',0 ; endif ; else ; call print ; db 'not debug',0 ; endif ; jp loop ; end ; ; Sample file after processing by PPAL: ; ; ; Sample file to illustrate PPAL ; MYMAC macro ; if debug ;this is a test ; call print ; db 'debug macro',0 ; else ; call print ; db 'no debug macro',0 ; endif ; endm ; LOOP: ; if debug ; if debug2 ; call print ;this is only a test ; db 'debug2',0 ; else ; call print ; db 'debug',0 ; endif ; else ; call print ; db 'not debug',0 ; endif ; jp loop ; end ; ;%END ------- 7-Sep-86 03:58:33-MDT,3484;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Sun 7 Sep 86 03:58:24-MDT Received: from brl-smoke.arpa by AMSAA.ARPA id a004947; 7 Sep 86 5:32 EDT Received: from USENET by SMOKE.BRL.ARPA id a007242; 7 Sep 86 5:32 EDT From: Chris Gray Newsgroups: net.micro.cpm Subject: New shareware compiler Message-ID: <266@myrias.UUCP> Date: 4 Sep 86 19:08:44 GMT Posted: Thu Sep 4 15:08:44 1986 To: info-cpm@AMSAA.ARPA Greetings fellow CP/M'ers. I have over a Megabyte of new CP/M software that I would like to get out in the world as shareware. It was originally intended to be a commercial product, but I think the time has passed for that. What I want to know is how to go about doing it. Posting it to the net might raise just a few hackles, so I'm reluctant to do that. Also, spending a few hundred dollars to ship it to a BBS a thousand or so miles away doesn't sound attractive. (I'm physically in Edmonton, Alberta - home of West Edmonton Mall.) What I have to give away is a full programming language system. The language, called Draco (pronounced Drayko), has been in use for a couple of years now, so the compiler is fairly stable, as are the other utilities. The compiler compiles at about 1500 lines per minute (5 MHz 8085) directly to relocatable object files. The linker is similarly capable. Code produced is about on par with the best produced by any C or Pascal compiler I've heard of. As an example, the compiler itself is about 10000 lines. It compiles on a single 8" floppy in under 10 minutes, yielding about 40K of code. For small programs, under 100 lines, the time to load the compiler is easily the dominant factor. All of the tools are easy to use, and fit well into CP/M. Again, as an example, to build the compiler from scratch, I just type draco dr* link dr1 dr2 dr3 dr4 dr5 dr6 dr7 dr8 dr9 -sodraco (I built file patterns into the compiler, but not the linker - sigh.) The entire package includes fairly complete documentation on everything, a few thousand lines of sample sources (including a CRT-oriented adventure game system needing only a scenario), and several utilities. Major programs: draco.com - the compiler itself link.com - the linker drlib.com - the library builder ddis.com - the disassembler das.com - a simple, one-pass assembler xref.com - call cross referencer trrun.lib - 8080 version of run-time library (quite comprehensive) trcpm.lib - CP/M-80 interface stubs crt.lib - terminal independent CRT I/O library (facilities vary from simple cursor addressing up through on screen formatter, menu builder and forms input routines) config.com - program to configure .set programs to a given terminal config.dat - database of terminal definitions (from a termcap) ded.set - visual programming editor hedit.set - visual hex editor/viewer cmp.set - visual file comparer - several CRT oriented games. Some are trivial, but two are major entities in their own right. OK, so what should I do with this stuff? (Nasty comments can be directed to /dev/null.) I'm willing to package up one or two copies (takes 5 single sided single density disks) and send them to major sites (note that the stuff is SHAREWARE, not FREEWARE), but I do not want to get into distributing it myself - I figure I'm better off porting my compiler to the 68000 family. Chris Gray (...alberta!myrias!cg) 7-Sep-86 09:53:29-MDT,509;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Sun 7 Sep 86 09:53:19-MDT Received: from simtel20.arpa by AMSAA.ARPA id a005415; 7 Sep 86 11:24 EDT Date: Sun 7 Sep 86 09:26:07-MDT From: Rick Conn Subject: Z-NEWS.509 Available To: info-cpm@AMSAA.ARPA Message-ID: <12237050513.12.RCONN@SIMTEL20.ARPA> In PD: are Z-NEWS.509 and 5Q9. In PD: is Z-NEWS.5Q9. Thanks to Keith for the upload. Rick ------- 7-Sep-86 12:24:40-MDT,1273;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Sun 7 Sep 86 12:24:30-MDT Received: from nadc.arpa by AMSAA.ARPA id a005635; 7 Sep 86 13:54 EDT Date: 7 Sep 1986 13:51:58-EDT From: prindle@nadc.ARPA To: info-cpm@AMSAA.ARPA Subject: c128 cp/m disk formats Cc: microcomputer.cbm@rutgers.ARPA The C128 can (in CP/M mode with a 1571 disk drive) read, write, and format the following diskette formats: Single Sided Commodore GCR CP/M 2.2 (32 tracks of 17 (256 byte) sectors) Single Sided C128 CP/M 3.0 GCR (680 logical tracks of 1 (256 byte) sector) Double Sided C128 CP/M 3.0 GCR (1360 logical tracks of 1 (256 byte) sector) Epson QX10 DS MFM (80 tracks of 10 (512 byte) sectors) IBM CP/M 86 SS MFM (40 tracks of 8 (512 byte) sectors) IBM CP/M 86 DS MFM (80 tracks of 8 (512 byte) sectors) Kaypro II SS MFM (40 tracks of 10 (512 byte) sectors) Kaypro IV DS MFM (80 tracks of 10 (512 byte) sectors) Osborn DD MFM (80 tracks of 5 (1024 byte) sectors) Hope this clarifys things. Most Commodore documentation implies there are additional formats, but without committing to what they are. Thus, the above are obviously all the "official" formats! Frank Prindle Prindle@NADC.arpa 7-Sep-86 16:39:55-MDT,950;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Sun 7 Sep 86 16:39:47-MDT Date: Sun, 7 Sep 86 18:01:09 EDT From: David Towson (SECAD) To: Rick Conn cc: info-cpm@AMSAA.ARPA, sage@LL.ARPA Subject: Re: Response to Sage's comments Rick - After reading Jay,s message and your reply regarding SYSLIB, I decided to take a look to see whether the archives still contained a version of SYSLIB that could be assembled with M80. I was surprised when the string-search of CPM.CRCLST failed to come up with ANY entry for SYSLIB. I thought for sure it would be in the ZCPR2 directory. How about restoring to the archives the latest version of SYSLIB that will still work with the tools lots of people already have? It seems a shame to limit the use of such a good thing to those who wish to purchase a new assembler. Dave 7-Sep-86 18:07:26-MDT,10281;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Sun 7 Sep 86 18:06:57-MDT Received: from simtel20.arpa by AMSAA.ARPA id a006311; 7 Sep 86 18:58 EDT Date: Sun, 7 Sep 1986 16:59 MDT Message-ID: Sender: KPETERSEN@SIMTEL20.ARPA From: Keith Pet