1-Nov-82 04:18:00,804;000000000000 Date: 1 November 1982 06:18-EST From: Jerry E Pournelle Subject: last message... To: info-cpm at BRL Via: Mit-Mc; 3 Nov 82 17:45-EST Via: Brl; 3 Nov 82 18:01-EST Via: Brl-Bmd; 3 Nov 82 19:06-EST Regretably this will be my last sending to this mail list. Indeed, even this one will cost me dearly. I had over a hundred "MAIL MEMO" messages tonight; all because the mail memo demon --and demon it is--insists on telling me ALL about everyone on the list who no longer gets mail. I am weary of learning that goldfarb doesn't get message and a copy is being returned. Also that--well, you get the idea. A hundred of those is too many. I suppose I will get this one back a dozen times; as I said, it will cost me. Surely there is a remedy? But I do not know it. 3-Nov-82 13:33:00,1101;000000000000 Date: 3 Nov 1982 1233-PST From: Ted Shapin Subject: Big Board Magazine To: INFO-CPM at BRL Postal-address: Beckman Instruments, Inc. Postal-address: 2500 Harbor X-11, Fullerton, CA 92634 Phone: (714)970-3393 Via: Usc-Ecl; 3 Nov 82 16:24-EST Via: Brl; 3 Nov 82 16:57-EST Via: Brl-Bmd; 3 Nov 82 18:36-EST I am pleased with "Micro Cornucopia" a journal devoted to the "Big Board" CP/M system. It comes out 6 times a year from PO Box 223, Bend, Oregon 97709. Subscriptions are $16. Issues average about 24 pages with hardware and software hints such as adding a RAM power supply protection circuit, configuring MODEM7, disk drive jumper options, etc. So far the 8 issues have all been on the original Big Board, but the editor is building a Big Board II and I expect future issues will have articles on both. A good article on disk drive maintenance in No. 8 saved me a lot of trouble. I had a drive that would make errors after about track 42. ... Turned out it had lost the head load pressure pad! Back issues are available at $3. ------- 3-Nov-82 16:19:00,905;000000000000 Date: 3 November 1982 18:19-EST From: Charlie Strom Subject: New files on MC To: INFO-CPM at BRL Via: Mit-Mc; 3 Nov 82 18:19-EST Via: Brl; 3 Nov 82 18:45-EST Via: Brl-Bmd; 3 Nov 82 19:08-EST I have uploaded to MC the following files: AR20:CPM;CPYFST 43ASM CPYFST 40DOC COPYFAST is a very useful disk copy program. It uses RAM up to capacity to buffer data and has provision for installation using either direct calls to disk controller firmware (a few implementations are present as assembly-time conditionals) or BDOS calls. The latter option also permits several alternative run-time behaviors such as copying system tracks only, data tracks only, a specified range of tracks, etc. Note that the program must be adapted to the number of sectors/track, number of tracks, etc. for the target system and can be fine-tuned to allow very rapid disk copying. 3-Nov-82 22:14:00,820;000000000000 Date: 3 Nov 1982 at 2314-CST From: mknox at Utexas-11 Subject: CP/M disk logins To: info-cpm at BRL Via: Utexas-11; 4 Nov 82 0:31-EST Via: Brl; 4 Nov 82 1:17-EST Via: Brl-Bmd; 4 Nov 82 1:23-EST The answer to this is probably obvious, to those who know the answer. What flag or field or whatever shows that a disk has been 'logged in'? This comes up two ways: o Something used by BDOS to tell it to 'login' a disk and build a directory check table and allocation table. o Some way for the BIOS to know that the disk drive has a new disk and it needs to be checked (i.e. density, format, etc.). Obviously the BIOS doesn't want to do this everytime SELDSK is called. I strongly suspect a word in the DPH table, but which one? ?????????? tnx ------- 4-Nov-82 06:48:00,475;000000000000 Date: 4 November 1982 08:48-EST From: Roger L Long To: LIN at Mit-Mc cc: info-micro at BRL, info-cpm at BRL Via: Mit-Mc; 4 Nov 82 8:51-EST Via: Brl; 4 Nov 82 9:23-EST Via: Brl-Bmd; 4 Nov 82 9:52-EST I've started reading my mail using BABYL, and got someone to figure out what it too to remove those blasted lines (BABYL already restructures the headers), because at 300 baud they really get in the way. Look at MC:GUEST0;BYTE EVARS. -roger 4-Nov-82 09:31:00,727;000000000000 Date: 4 Nov 82 12:31-EDT (Thu) From: Robert Heller To: info-vax at Sandia cc: info-cpm at Mit-Mc Subject: VMS disk ACPs for RT11 and CP/M 8" Floppies (RX02 drives on a VAX-11/780) Via: UMASS-COINS; 7 Nov 82 3:59-EST Via: Mit-Mc; 8 Nov 82 12:48-EST Via: Brl; 8 Nov 82 16:28-EST Via: Brl-Bmd; 8 Nov 82 17:17-EST I am interested in writing or getting RX02 disk ACPs for VMS to allow a VAX/VMS machine to easily read/write/etc. either RT11 or CP/M 8" floppy disks. We have a pair of RX02 disks on one of our VAX-11/780s. If you have any information, please send me mail: heller.umass-coins@udel-relay thank you in advance. robert heller 4-Nov-82 09:50:00,1527;000000000000 Date: 4 Nov 1982 09:50 EST From: clark.wbst at Parc-Maxc Subject: Re: Godbout 8085/8088 In-reply-to: goldfarb.ucf-cs's message of 28 Oct 82 20:43:50 EST (Thu) To: Ben Goldfarb Cc: Info-micro at BRL, info-cpm at BRL Via: Parc-Maxc; 4 Nov 82 10:05-EST Via: Brl; 4 Nov 82 10:35-EST Via: Brl-Bmd; 4 Nov 82 10:52-EST About your 7E's... it has been a while, but am pretty sure that 7E is the opcode of the instruction your monitor uses to do the memory fetch, probably a 'MOV A,M'. I have had this before... First I will explain where I have seen it; I don't see a clear match with your problem, but then I am not familiar with your hardware... If you have a processor with no buffering, when you do the MOV A,M the opcode (7E?) gets put on the bus. When the processor does the read the bus is tri-stated, and the opcode is still hanging around from capacitance. Since there is no memory out there, nobody drives the bus, so you read the opcode. If you have a running processor you can see this by writing a memory poker that uses a different instruction, like ldax b or d... then you see their opcode. This certainly would not explain your problem with EI's etc. Actually, not much of anything would run since on the 8080 all jumps, ret, and I think calls have the upper bit set. Since you DID seem to get the memory dumper of some description to run, it must not drop them ALL the time. Anyway, good luck ! I hope this helped some... --Ray Clark 4-Nov-82 10:29:00,1654;000000000000 Date: Thursday, 4 Nov 1982 09:29-PST To: HONEYCUTT at Mit-Mc Cc: INFO-CPM at BRL, AMETHYST-USERS at Mit-Mc Cc: bridger at Rand-Unix, Roger L Long Subject: Catching function key sequences From: bridger at Rand-Unix Via: Rand-Unix; 4 Nov 82 12:49-EST Via: Brl; 4 Nov 82 13:18-EST Via: Brl-Bmd; 4 Nov 82 13:39-EST My bios CONIN has an option to enter a countdown loop when an ESC is received. If the next char is received within that time, it assumes both the escape and the follow-on character were sent by a function key. It then discards the ESC and sets the high bit of the follow-on character to signal the application program. If it timesout without receiving anything, the ESC is presumed to have been typed as the escape key and is returned. You could have your editor patch in its own CONIN to do this while it's running, then restore the bios CONIN on exit from the editor. The timing constant is based on the CPU speed and the baud rate for the terminal channel and presumes that the follow-on character will be sent by the terminal's ROM as soon as the baudrate permits. Let me know if you pursue this. On reading Roger Long's message, I see that this technique may need to be extended another character for the 3-character sequences from the H-19 alternate keypad. A useful feature of this approach is that it allows the editor to distinguish between ESC-char sent as separate keystrokes, and a function key that transmits the same sequence. This permits binding the function keys to anything without conflicting with bindings chosen for the separate keystroke commands. bridger. 4-Nov-82 13:48:53,6565;000000000000 Date: 4 Nov 82 15:48:53-EST (Thu) From: Rick Conn To: info-cpm at BRL, info-micro at BRL Subject: SYSLIB Via: Brl; 4 Nov 82 16:17-EST Via: Brl-Bmd; 4 Nov 82 16:30-EST I am very pleased (yeah, and kind of proud since it WAS a lot of work) to announce the release of SYSLIB for CP/M 2.2. I am sending this to both INFO-CPM and INFO-MICRO since SYSLIB can be used to create programs which run on ANY 8080 or Z80 microcom- puter, not necessarily just CP/M, altho CP/M is required to do the assembly. SYSLIB is an extensive set of utility subroutines, writ- ten in 8080 assembly language. There are over 130 subroutines in over 70 modules in the library. The following shows the scope of the library by showing you all the files which are required to contain it and its documentation. SYSLIB is documented in two ways. A 100+ page user and reference manual exists which tells you about each of the rou- tines and gives you 7 sample programs which you can study to see how SYSLIB is used. Additionally, 13 HLP (for use with my HELP program for online documentation) files are available which con- tain the same information the routine description sections of the user and reference manual contains. You can effectively index into the user and reference manual quickly by using the HLP files. A second, following message which is much longer than this one has been prepared to tell you exactly what SYSLIB is and does. This was done so that those not interested in SYSLIB need not read thru all of the basic description information. M80.COM, L80.COM, and SYSLIB.REL are required to do SYSLIB programming. All the other files are source and documentation. Information on the files making up SYSLIB follows: SYSLIB -- An Integrated Library of Assembly Language Utility Subroutines for use with the Microsoft M80 Assembler Distribution Statement and Listing of SYSLIB Files Distribution Statement SYSLIB is released to the public domain. Anyone who wishes to USE it may do so with no strings attached. The author assumes no responsibility or liability for the use of SYSLIB. It is copyrighted by the author, Richard Conn, who has sole rights to it. SYSLIB and its associated documentation may be sold by itself or as an independent part of a package of programs only with the express, written consent of the author. The author, however, supports the use of SYSLIB by commercial software developers, and places no restriction on the sale of programs which are based on SYSLIB and use routines contained within SYSLIB to perform their major functions. Source Files to SYSLIB Modules Filename.Typ Size K Filename.Typ Size K Filename.Typ Size K -------- --- ------ -------- --- ------ -------- --- ------ S0FILEIO.MAC 2 SCOMP .MAC 2 SEVAL4 .MAC 2 S1FILEIO.MAC 2 SCOMPHD .MAC 2 SFCLOS .MAC 2 S2FILEIO.MAC 2 SCONDIN .MAC 2 SFDEL .MAC 2 S3FILEIO.MAC 2 SCOUT .MAC 2 SFEXIST .MAC 2 SBBLINE .MAC 4 SCPOUT .MAC 2 SFILEIO .MAC 10 SBDOS .MAC 2 SCRC .MAC 4 SFILL .MAC 2 SBIOS .MAC 4 SCRC1 .MAC 4 SFMAKE .MAC 2 SBLINE .MAC 4 SCRLF .MAC 2 SFNAME .MAC 6 SCAPS .MAC 2 SCST .MAC 2 SFOPEN .MAC 2 SCAPSTR .MAC 2 SDIR .MAC 34 SFREAD .MAC 2 SCATH .MAC 2 SEN .MAC 2 SFRENAME.MAC 2 SCCOUT .MAC 2 SEVAL .MAC 4 SFWRIT .MAC 2 SCIN .MAC 2 SEVAL1 .MAC 2 SHDR .MAC 2 SCLOUT .MAC 2 SEVAL2 .MAC 2 SINITFCB.MAC 2 SCODEND .MAC 2 SEVAL3 .MAC 2 SINLINE .MAC 6 SINSTR .MAC 2 SMHL5DC .MAC 4 SSCANNER.MAC 2 SLA2HC .MAC 2 SMOVE .MAC 4 SSORT .MAC 14 SLADC .MAC 2 SPA2HC .MAC 2 SUD .MAC 2 SLCRLF .MAC 2 SPADC .MAC 2 SYSTEST .MAC 4 SLHL4HC .MAC 2 SPAUSE .MAC 4 SYSTEST1.MAC 4 SLHL5DC .MAC 2 SPHL4HC .MAC 2 SYSTEST2.MAC 4 SLOUT .MAC 2 SPHL5DC .MAC 2 SYSTEST3.MAC 4 SLPRINT .MAC 2 SPOUT .MAC 2 SYSTEST4.MAC 6 SLPSTR .MAC 2 SPRINT .MAC 2 SYSTEST5.MAC 2 SMA2HC .MAC 2 SPSTR .MAC 2 SYSTEST6.MAC 6 SMADC .MAC 2 SRAND .MAC 2 SZCPR .MAC 8 SMATH .MAC 6 SRIN .MAC 2 SZFNAME .MAC 12 SMHL4HC .MAC 2 82 Files Occupying 278K SYSLIB.REL Library File Filename.Typ Size K RS -------- --- ------ -- SYSLIB .REL 14 1 File Occupying 14K SYSLIB Help Files for Online Documentation Filename.Typ Size K Filename.Typ Size K Filename.Typ Size K -------- --- ------ -------- --- ------ -------- --- ------ SYSLIB .HLP 16 SYSLIB5 .HLP 6 SYSLIB9 .HLP 8 SYSLIB1 .HLP 14 SYSLIB6 .HLP 4 SYSLIBA .HLP 8 SYSLIB2 .HLP 4 SYSLIB7 .HLP 6 SYSLIBB .HLP 6 SYSLIB3 .HLP 8 SYSLIB8 .HLP 6 SYSLIBC .HLP 8 SYSLIB4 .HLP 6 13 Files Occupying 100K SYSLIB Document Files, Including User and Reference Manual Filename.Typ Size K Filename.Typ Size K Filename.Typ Size K -------- --- ------ -------- --- ------ -------- --- ------ SYSLIB .WS 104 SYSLIBI .WS 10 SYSLIBR .WS 4 SYSLIBHD.WS 16 SYSLIBID.WS 4 SYSLIBS .WS 42 6 Files Occupying 180K 4-Nov-82 13:50:44,15098;000000000000 Date: 4 Nov 82 15:50:44-EST (Thu) From: Rick Conn To: info-cpm at BRL, info-micro at BRL Subject: SYSLIB Details Via: Brl; 4 Nov 82 16:17-EST Via: Brl-Bmd; 4 Nov 82 16:34-EST From the SYSLIB User and Reference Manual: SYSLIB User and Reference Manual SYSLIB -- An Integrated Library of Assembly Language Utility Subroutines for use with the Microsoft M80 Assembler 1.0 Introduction 1.01 What is SYSLIB? SYSLIB (SYStem LIBrary) is a collection of over 130 subrou- tines which are designed to provide to the CP/M 8080/Z80 assembly language programmer a set of functions upon which he can build his programs. This library is intended to relieve the programmer of the task of frequently "reinventing the wheel" and to provide him with an tool environment which encourages structured programming at the assembly language level. Each subroutine within SYSLIB can be viewed as a reliable "black box." The subroutines in SYSLIB are completely documented within this 100+ page manual and the SYSLIBx.HLP files, and the programmer is consistently provided with the following informa- tion: 1. Name of Subroutine 2. Function it performs 3. What its inputs are 4. What its outputs are 5. What registers are affected by it 6. What other library routines it calls upon 7. What errors can occur and how it handles them The routines within SYSLIB are designed to work together and complement each other. Parameter passing is consistent between the various subroutines; for instance, all routines which need to be passed a pointer to a File Control Block are passed that pointer in the DE register pair. Also, as a general rule, if a register is not returned as an output from the SYSLIB subroutine, then its value is not affected (it has the same value when the routine is exited as it had when the routine was called). SYSLIB itself is a library of relocatable object modules created in the Microsoft M80 relocatable object format. All subroutines within SYSLIB are grouped within functionally-related modules. Once a routine is referenced (by the EXT statement in the M80 assembly language program), its module is loaded and it is available to the programmer by means of a simple subroutine call. All other subroutines within that particular module are also loaded, but they are not available to the programmer unless he has also referenced them by EXT statements. The module is loaded only once, regardless of how many routines within the module are referenced. For this reason, I have designed each module to contain routines which are frequently used together or are called by each other (one routine within the module calls another routine within the module). 1 - Introduction Page 1 SYSLIB User and Reference Manual 1.02 What is Needed to Use SYSLIB? You need an 8080- or Z80-based microcomputer with at least 48K bytes of contiguous memory running CP/M 2.2, the Microsoft M80 assembler tool set (specifically, the M80 assembler and the L80 linker), and the usual set of software development tools (an editor and, preferably, a debugger) to use SYSLIB. 1.03 What Does SYSLIB Buy Me? The bottom line is that, to the experienced SYSLIB program- mer, SYSLIB has the potential of being a significant tool which enables him to: 1. Solve his programming task quickly -- because he spends less time writing com- monly-used subroutines and worrying about how his regis- ters are affected by these subroutines and more time concentrating on the problem at hand 2. Write space- and speed-efficient code -- because all of the SYSLIB routines have been gone over time and time again to reduce their size and make them more efficient in terms of speed; for example, the SORT routine is a Shell Sort that can be called to perform the sort using pointers (in which case it exchanges pointers rather than records when it needs to do a swap) or perform the sort without using pointers (when space is a factor and there may not be enough room for a pointer table) 3. Write more maintainable code -- because SYSLIB is designed with structured programming philosophy in mind; each subroutine is equi- valent to a process box, having (1) only one entrance and one exit, (2) a precisely-defined function, and (3) a precisely-defined set of input and output parameters; having used SYSLIB for some time now, the author has noted that his programming thought processes and program designs have tended more and more toward end-in (top- down from the objective point of view and bottom-up from the SYSLIB subroutine point of view), structured designs that he can go back to at a later date and readily decipher and modify 1 - Introduction Page 2 SYSLIB User and Reference Manual 4. Reduce the programming effort -- because SYSLIB provides a number of very involved routines which would, in themselves, take quite some time to code; for example, the DIRF routine will load the directory of a disk into memory, select a set of files from that loaded directory as specified by a File Control Block and a flag which indicates whether to include System or Non-System files and what user area is to be examined, packs the loaded directory (removing entries not selected from the memory buffer), alphabet- izes the directory entries by file name and type or by file type and name, and returns a pointer to the first entry and a count of the number of entries selected In many ways, SYSLIB brings some of the advantages of pro- gramming in a High-Order Language, like C or Pascal, to the assembly language programmer. It allows him to maintain the smaller code size and greater efficiency which can be realized in assembly language programming and simultaneously realize a re- duced life-cycle cost (from development to fielding to post- fielding maintenance and modification) over assembly language programming without a SYSLIB-like tool set. 1.04 How Do I Assemble with SYSLIB? Each example in Section 21 of this manual shows an assembly of the sample program. I frequently use a command file, which I call M80.SUB, to assemble my programs. This command file takes only one parameter, the name of the file to be assembled WITHOUT its type (MAC is assumed). Warning: The command MUST be: SUB M80 filename and it MUST NOT be: SUB M80 filename.typ If it is of the latter form, the source code will be deleted during the assembly process! You may wish to remove the ERA $1.BAK command in the M80.SUB file to eliminate this problem. I only do this for a space savings. 1 - Introduction Page 3 SYSLIB User and Reference Manual My M80.SUB command file is: ; M80.SUB -- MACRO-80 Assembler and Linker M80 =$1 SUB /A PLEASE ABORT IF ERROR(S) EXIST ERA $1.BAK ERA $1.COM L80 /P:100,$1,A:SYSLIB/S,$1/N,/U,/E ERA $1.REL ; ASSEMBLY COMPLETE I run ZCPR2 instead of the CP/M 2.2 CCP, and I am always on Drive B: doing my development work, while my editors and assemblers (and SYSLIB.REL) are on Drive A:. Note that this is reflected in M80.SUB, where L80 looks for A:SYSLIB for the scan. 1.05 How Do I Learn to Use SYSLIB Effectively? This is, of course, opinion, but I feel that the best way to learn how to use SYSLIB would involve the following steps: 1. Study the SYSLIB manual in an overview fashion, familiarizing yourself with the functions of the subroutines available 2. Study in some detail the sample source programs in Section 21, jumping back to the main body of the manual from time to time to see why the routines I selected in the programs were used in the way I used them 3. Try coding a couple of the routines in this manual, copying them verbatim and assembling them 4. Try making up a few simple problems of your own and use SYSLIB to code them 5. Apply SYSLIB to a significant program you want to write I am a strong advocate of writing programs in order to learn how to program, and I feel that it is most important to (1) gain as much familiarity with the SYSLIB routines as you can and (2) to write programs using these routines. 1 - Introduction Page 4 SYSLIB User and Reference Manual 1.06 Who May Use SYSLIB? SYSLIB is hereby released to the public domain. Anyone who wishes to USE it may do so with no strings attached. The author assumes no responsibility or liability for the use of SYSLIB. It is copyrighted by the author, Richard Conn, who has sole rights to it. SYSLIB and its associated documentation may be sold by itself or as an independent part of a package of programs only with the express, written consent of the author. The author, however, supports the use of SYSLIB by commercial software devel- opers, and places no restriction on the sale of programs which are BASED on SYSLIB and use routines contained within SYSLIB to perform their major functions. I hope you enjoy using SYSLIB and find it to be as useful a tool as I do. Richard Conn 1 - Introduction Page 5 SYSLIB User and Reference Manual SYSLIB -- An Integrated Library of Assembly Language Utility Subroutines for use with the Microsoft M80 Assembler Functional Listing of SYSLIB Routines 2.0 Directory Manipulation Routines - 6 DIRF, DIRFS: 7 DBUFFER: 8 DPARAMS: 9 DFREE: 9 FSIZE: 10 DIRLOAD, DIRSLOAD: 11 DIRALPHA: 12 DIRSEL: 12 DIRPACK: 13 DIRNPACK: 14 3.0 Numeric String Evaluation Routines - 15 EVAL: 15 EVAL16: 16 EVAL10: 16 EVAL8: 17 EVAL2: 17 4.0 Byte-Oriented File Input/Output Routines (0-n-3) - 18 FIn$OPEN: 19 FOn$OPEN: 20 FIn$CLOSE: 20 FOn$CLOSE: 20 Fn$GET: 21 Fn$PUT: 21 5.0 CP/M File Input/Output Routines - 23 F$OPEN: 23 F$MOPEN: 24 F$CLOSE: 24 F$MAKE: 25 F$DELETE: 25 F$RENAME: 26 F$EXIST: 26 F$READ: 27 F$WRITE: 27 6.0 File Name String Parser and FCB Init - 28 FNAME: 28 INITFCB: 29 7.0 Input Line Editors - 30 BBLINE: 31 BLINE: 31 INLINE: 32 8.0 String Output Routines - 34 PRINT, LPRINT: 34 PSTR, LPSTR: 34 9.0 Numeric Output Routines - 35 PHL4HC, LHL4HC: 35 MHL4HC: 35 PHL5DC, LHL5DC: 36 MHL5DC: 36 PHLDC, LHLDC: 36 MHLDC: 37 PA2HC, LA2HC: 37 MA2HC: 37 PA3DC, LA3DC: 38 MA3DC: 38 PADC, LADC: 38 MADC: 39 10.0 String and Value Comparison Routines - 40 COMPHD: 40 COMPB, COMPBC: 40 SCANNER: 40 INSTR: 41 11.0 Character-Oriented Input/Output Routines - 42 CRLF, LCRLF: 42 CONDIN: 42 CST: 43 CIN, RIN: 43 COUT, LOUT, POUT: 43 CCOUT, CLOUT, CPOUT: 44 12.0 Math Routines - 45 ADDHD: 45 SUBHD: 45 MULHD: 46 DIVHD: 46 NEGH: 46 CMPH: 46 ROTLH: 47 ROTRH: 47 SHFTLH: 47 SHFTRH: 48 ANDHD: 48 ORHD: 48 XORHD: 48 13.0 CRC Routines - 49 CRCCLR, CRC1CLR: 50 CRCUPD, CRC1UPD: 50 CRCDONE, CRC1DONE: 50 CRCK, CRC1K: 51 14.0 Random Number Generator Routines - 52 RNDINIT: 52 RNDSEED: 52 RND: 53 15.0 User/Disk Manipulation Routines - 54 PUTUD: 54 GETUD: 55 LOGUD: 55 RETUD: 55 16.0 Sort Routines - 56 SSBINIT: 57 SORT: 57 17.0 ZCPR2 Feature-Specific Routines - 58 ZINIMC: 58 ZINIEXT: 59 ZCPRSET: 59 ZCPRQ: 60 ZMCPTR: 61 ZPFIND: 61 ZFSTAT: 62 18.0 ZCPR2-Specific Named Directory Routines - 63 ZFNINIT: 64 ZDNFIND: 64 ZFNAME: 65 19.0 Miscellaneous Routines - 66 BDOS: 67 BIOS: 67 CAPS: 68 CAPSTR: 68 CATH: 69 CODEND: 69 EN: 69 FILLB, FILLBC, HFILB, HFILBC: 70 MOVEB, MOVEBC, HMOVB, HMOVBC: 71 PAUSE: 71 4-Nov-82 17:30:16,5381;000000000000 Date: 4 Nov 82 19:30:16-EST (Thu) From: Rick Conn To: info-cpm at BRL Subject: XDIR3, Version 1.2 Via: Brl; 4 Nov 82 19:43-EST Via: Brl-Bmd; 4 Nov 82 19:46-EST XDIR3, complete with its installation program (XDIR3INS) and its HLP file, are now ready for distribution on MIT-MC. Keith will let you know where the files are when he is ready. Some documentation on what XDIR3 is and does follows: Overview of XDIR3 XDIR3 is an extended directory display utility designed to run under CP/M 2.2 and support some of the extended features of ZCPR2 as well. Any conventional CP/M 2.2 user may use XDIR3, but he should make sure he turns off the ZCPR2-specific features by running the XDIR3 Installation Program, XDIR3INS, and manually turning them off before using XDIR3. XDIR3 automatically adapts to any Org-0 CP/M 2.2 system, regardless of the size of its disks. It reads the disk parameter block information from the operating system to determine what the attributes of the disk it is working with are, and it then presents its display information accordingly. XDIR3 runs in two basic modes: . as a directory display utility . as a file scanner utility (File Name Buffer Facility) XDIR3 is a ZCPR2 utility which supports the extended ZCPR2 features, particularly named directories. As a directory display utility, it displays to you information about the files on a particular disk in all or a particular user area. It gives you the following information: . Name of File . Size of File (in K bytes) . Attributes of File (R/O or System) . Sum of Sizes of All Files Displayed . Total Number of Files on Disk . Amount of Space Remaining on Disk . What Disk and What User Area you are looking at As a file scanner utility, it does the following: . Logs a group of selected files to disk for later scan . Prints the contents of such a log file . Scans a log file and compares it with the files selected by you, telling you what files are missing and what files are additional XDIR3 is quite human-oriented, with many built-in features which provide a human-interface type of service to the user. Some of these include: . Named Directories may be specified . The file listing is alphabetized by file name and type or file type and name, depending on user preference . The file listing is organized vertically or horizontally, depending on user preference . Output may also be send to disk or printer . XDIR3 is designed to run quickly, having an optimum design in its directory load and sort modules Basic Use of XDIR3 under ZCPR2 XDIR3 is invoked by one of the following command lines: XDIR afn oooo... or XDIR afn /oooo... and XDIR /oooo... where all elements after the XDIR command are optional. 'afn' is an ambiguous file reference, as described on the following frames. 'o' is an option letter, which is one or more of the options described on the next frame. Note that since a slash denotes that an option follows, an afn may not begin with a slash. This can be changed by an equate in the source code of XDIR3 if desired. Aa - Set the attributes of the files to be displayed a=S for System Files, a=N for Non-System Files a=A for All Files (Non-System and System) D - Send Output to Disk Ff - Engage File Name Buffer Facility f=L to Log File Names to Disk f=P to Print Names Logged to Disk f=S to Scan Disk for File Names and Compare to Log G - Toggle Grouping (group files by name and type or type and name) H - Toggle Horizontal or Vertical display format I - Inspect files selected by FL option N - Negate Selection; select those files which do NOT match the ambiguous file name P - Send Output to Printer 'afn' is an ambiguous file reference, of the general form: dir:filename.typ where filename.typ is a conventional CP/M ambiguous file name (wild card characters of ? and * are OK, but file name must NOT start with /) dir: is a ZCPR2 directory specification, which may be one of the following forms: d: where 'd' is a disk letter (A-P) to indicate the current user area on that disk u: where 'u' is a user number (0-31) to indicate that user on the current disk; 'u' may be a '?', in which case all user areas are selected du: where 'du' specifies both disk and user name: where 'name' is the name of a directory (disk/user area) 4-Nov-82 19:08:00,1261;000000000000 Date: 4 November 1982 21:08-EST From: Robert L Plouffe To: INFO-CPM at BRL Via: Mit-Mc; 4 Nov 82 21:08-EST Via: Brl; 4 Nov 82 21:12-EST Via: Brl-Bmd; 4 Nov 82 21:25-EST I have uploaded files to AR47:CPM; at MIT-MC that permits users of North Star CP/M vers 1.1.0 to have two additional floppy disk formats on 5 1/4 in drives. North Star supports Octal (N drives) in that version but with 4kb directory blocks. I have added an additional format that gives 2kb directory blocks. Additionally, there is an alternate format provided for Quad drives (doubleside,doubledensity) that permits 80 tracks vs the North Star 70 track support. You can intermix diskettes and drives for the North Star supported formats as well as these (except for obvious physical constraints). The main file is NEWFRM 11ASM which patches into your system with DDT (after assembly). Use GENSYS 41COM instead of your SYSGEN program to write the patched system to your system tracks. Also get the formatter and copier, NEWFMT COM and NEWCOPY COM to work with his system. GENUSR 45ASM is an extensive patch file that incorporates many user features including an extended CCP - and has the two new disk formats already built into it. enjoy 5-Nov-82 04:15:54,844;000000000000 Date: 5 Nov 82 6:15:54-EST (Fri) From: Rick Conn To: Eric O Stork cc: info-cpm at BRL, info-micro at BRL Subject: SYSLIB Location Yet to be Determined Via: Brl; 5 Nov 82 6:23-EST Via: Brl-Bmd; 5 Nov 82 6:32-EST Eric, Thank you for your interest in SYSLIB. The location of the SYSLIB routines will be posted to the net within a week. The reason I left out where the routines are at this time is because Keith (w8sdz) is trying to find a place for them at this time. Everyone will be informed when they are placed on the net. For the time being, the library itself, the HLP files, and (I hope) the user's manual will be placed on MIT-MC. The source code, being so huge, may not necessarily be placed on MIT-MC, but it will be showing up in the SIG/M disks. Rick 5-Nov-82 05:26:18,1657;000000000000 Date: 5 Nov 82 7:26:18-EST (Fri) From: Keith Petersen To: Info-Micro at BRL, Info-Cpm at BRL Subject: [Donald E. Hopki: Cheep disks] Via: Brl; 5 Nov 82 7:36-EST Via: Brl-Bmd; 5 Nov 82 7:50-EST Appologies to those who get duplicate copies. The info is so useful I couldn't resist forwarding. ----- Forwarded message # 1: Date: 5 November 1982 00:07-EST From: Donald E. Hopkins Subject: Cheep disks To: INFO-APPLE at MIT-MC Via: Mit-Mc; 5 Nov 82 0:16-EST I've found a very good source for Control Data disks. A box of 12 5-1/4" (or 10 8" disks) costs only $19.90... There is a $3 P&H charge for 1 to 4 boxes, and a $4 charge for 5 or more (no limit). They are error free, have a 1 year warranty, and come with hub rings installed. I ordered a box, and they arrived promptly. They seem like good disks. I haven't given them extensive tests yet, as I've just recently gotten them, but none of them have zonked out (I've had that happen to me with other brand new disks). Overall, it seems like a good deal. For all interested in trying some, here are the phone numbers that were listed on the sheet: 1-800-521-5700 (Everywhere but:) 1-800-482-4770 (Michigan) 313-557-3036 (Detroit) 312-992-0076 (Chicago) 614-221-1788 (Columbus) 513-621-1518 (Cincinnati) Telex: 810-224-4646 (Yes, I proofread the numbers, and there are no typos (any more)) Well, I must terminate this messagge, as my rabbit, Spike, is nibbling on phone cord, and I must chase her out of the room... "Share and Enjoy." -Don yy~~y&_^?^? ----- End of forwarded messages 5-Nov-82 07:05:00,467;000000000000 Date: 5 Nov 1982 0805-CST From: G.TI.DAK at Utexas-20 Subject: VT180 used with a Vax To: info-vax at Sandia, info-cpm at BRL Via: Utexas-20; 5 Nov 82 9:09-EST Via: Brl; 5 Nov 82 9:20-EST Via: Brl-Bmd; 5 Nov 82 10:14-EST I would like to find out who is using a VT180 with a Vax. We have resently purchased some VT180 and would like to file out WHO has and WHAT used the VT180 are being used for. Thanks, Don Kassebaum(G.TI.DAK@UTexas) ------- 5-Nov-82 07:36:11,2299;000000000000 Date: 5 Nov 82 9:36:11-EST (Fri) From: Rick Conn To: info-cpm at BRL cc: info-micro at BRL Subject: SYSLIB Files Now on MIT-MC Via: Brl; 5 Nov 82 9:51-EST Via: Brl-Bmd; 5 Nov 82 10:44-EST The SYSLIB and XDIR3 files are now on MIT-MC in the CP/M archives. All files except the SYSLIB source are available now. We are currently debating as to if the source should be placed there as well, largely because of its excessive size. Thanks to Keith Petersen for doing the legwork in creating the archives without blowing away the CP/M directory. Enjoy! Rick :listf ar19:cpm The SYSLIB?.HLP files are in ASCII text, source form. The SYSLIB.REL file is in relocatable object form (binary). The SYSLIB??.WQ files (manual) are WordStar-formatted files which have been SQueezed by the SQ program to reduce their storage space. You will have to run USQ on them after downloading in order to get the original text back. Be sure to LMODEM these files as COM files. MC ARMTE AR19 SYSLIB 0 DEBUG MAC Outdated SYSLIB Debug Package -- Will be Upgraded Later 0 SYSLB HLP Root Node of SYSLIB Help Tree 0 SYSLB WQ Main Body of SYSLIB Manual 0 SYSLB1 HLP \ 0 SYSLB2 HLP \ 0 SYSLB3 HLP \ 0 SYSLB4 HLP \ 0 SYSLB5 HLP \ 0 SYSLB6 HLP \ SYSLIB Help Files 0 SYSLB7 HLP / Lower Nodes of the SYSLIB Help Tree 0 SYSLB8 HLP / 0 SYSLB9 HLP / 0 SYSLBA HLP / 0 SYSLBB HLP / 0 SYSLBC HLP / 0 SYSLBH WQ Table of Contents, Indexes of SYSLIB Manual 0 SYSLBS WQ Section 21: Sample Programs Section of SYSLIB Manual 0 SYSLIB REL SYSLIB Relocatable Library File :listf ar23:cpm XDIR3.MAC and XDIR3INS.MAC are written using SYSLIB, and SYSLIB is required for any reassembly. The Installation Program, XDIR3INS, eliminates the need for reassembly for customization purposes, by and large. MC CPM AR23 DIRUT2 0 XDIR3 COM Object to XDIR3 0 XDIR3 HLP Help File for XDIR3 0 XDIR3 MAC Source to XDIR3 0 XDIR3I COM Object to XDIR3INS (XDIR3 Installation Pgm) 0 XDIR3I MAC Source to XDIR3INS (XDIR3 Installation Pgm) 5-Nov-82 17:22:00,317;000000000000 Date: 5 November 1982 19:22-EST From: Frank J Wancho Subject: CIO.C for OSBORNE To: INFO-CPM at Mit-Mc Via: Mit-Mc; 5 Nov 82 19:24-EST Via: Brl; 5 Nov 82 19:30-EST Via: Brl-Bmd; 5 Nov 82 19:42-EST Has anybody converted CIO.C to work with an OSBORNE? If so, please let me know. --Frank 5-Nov-82 23:41:00,628;000000000000 Date: 6 November 1982 01:41-EST From: Michael C Adler Subject: JRT Pascal file I/O bug? To: Info-cpm at BRL Via: Mit-Ml; 6 Nov 82 1:43-EST Via: Brl; 6 Nov 82 1:56-EST Via: Brl-Bmd; 6 Nov 82 2:10-EST Whenever I attempt to do sequential I/O in text mode with JRT Pascal, I am unable to read a character at a time. Whenever I read 1 character, the next character returned by a word request is the first character after the next space. Thus, two read requests on the string "THIS WORD" in a file would return T and W. The same code on another system produced "THIS WORD". Any fixes? -Michael 6-Nov-82 09:49:00,362;000000000000 Date: 6 Nov 1982 1149-EST From: Andrew Scott Beals Subject: Re: CIO.C for OSBORNE To: FJW at Mit-Mc cc: INFO-CPM at Mit-Mc In-Reply-To: Your message of 6-Nov-82 0157-EST Via: Mit-Mc; 8 Nov 82 12:25-EST Via: Brl; 8 Nov 82 13:04-EST Via: Brl-Bmd; 8 Nov 82 17:09-EST yes, I have. if you want, i'll upload it to mc. ------- 6-Nov-82 16:37:00,398;000000000000 Date: 6 November 1982 18:37-EST From: Charlie Strom Subject: LU file To: INFO-CPM at BRL Via: Mit-Mc; 8 Nov 82 12:37-EST Via: Brl; 8 Nov 82 13:09-EST Via: Brl-Bmd; 8 Nov 82 17:14-EST I have just uploaded AR29:CPM;LUDEF DOC to MC. This text file is from the author of LU and specifies the format of LU-created library files so that they can be used by other programs. 6-Nov-82 23:22:21,930;000000000000 Date: 6-Nov-82 22:22:21-PST (Sat) From: UCBARPA.dag at Ucb-C70 (David Allen Gewirtz) Subject: Morrow Terminal Message-Id: <8210070622.28862@UCBARPA.BERKELEY.ARPA> Received: by UCBARPA.BERKELEY.ARPA (3.224 [10/16/82]) id A28861; 6-Nov-82 22:22:22-PST (Sat) Received: from UCBARPA.BERKELEY.ARPA by UCBVAX.BERKELEY.ARPA (3.227 [10/22/82]) id A01726; 8-Nov-82 14:56:52-PST (Mon) To: info-cpm at BRL Via: Ucb-C70; 9 Nov 82 7:28-EST Via: Brl; 9 Nov 82 7:50-EST Via: Brl-Bmd; 9 Nov 82 8:55-EST Hi, I have the Morrow terminal on loan for evaluation and I am trying to configure it for WordStar. Documentation is very sparse. I have it configured as an ADM-31, which was the way it was configured in a local computer store. Are there any special patches that should be made to wordstar to make the thing work right? Any patches to anything else...I am using 3.0 of wordstar. Thanks in advance, David 7-Nov-82 08:10:00,1149;000000000000 Date: 7 Nov 1982 0710-PST From: BHUBER at Usc-Ecl Subject: JRT Pascal multiplication fix To: INFO-CPM at BRL, INFO-APPLE at Mit-Mc cc: BHuber at Usc-Ecl Via: Usc-Ecl; 8 Nov 82 11:58-EST Via: Brl; 8 Nov 82 12:24-EST Via: Brl-Bmd; 8 Nov 82 17:07-EST I was discussing a small documentation problem with the JRT folks in San Francisco via telephone last week. Upon completion of the main part of our discussion, I mentioned a rather nastily worded rebuttal to the benefits of JRT Pascal which was contained in last week's Infoworld. It seems that under certain circumstances JRT Pascal could not correctly multiply a number times zero and come up with zero. I was immediately provided with the fix. Use DDT on EXEC.COM. Change an "ED" (echo delta) code in location 563C (five six three charlie) to "EB" (echo bravo). After exiting DDT, then savethe modified version with SAVE 90 EXEC.COM. I have little experience (so far) with JRT Pascal, but am learning slowly. I have found the JRT people to be very helpful in the three conversations that I have had over the last six weeks. Hope this helps, Bud ------- 7-Nov-82 11:26:02,440;000000000000 Date: 7-Nov-82 10:26:02-PST (Sun) From: UCBVAX.decvax!goutal at Ucb-C70 Subject: LCHECK.C Message-Id: <8210071826.12342@UCBVAX.BERKELEY.ARPA> Received: by UCBVAX.BERKELEY.ARPA (3.227 [10/22/82]) id A12340; 7-Nov-82 10:26:05-PST (Sun) To: ucbvax!C70: info-cpm at Ucb-C70 Via: Mit-Ai; 8 Nov 82 12:28-EST Via: Brl; 8 Nov 82 13:06-EST Via: Brl-Bmd; 8 Nov 82 17:12-EST Would it be inappropriate to post LCHECK.C to net.sources? 8-Nov-82 01:39:55,803;000000000000 Date: 8-Nov-82 00:39:55-PST (Mon) From: UCBARPA.dag at Ucb-C70 (David Allen Gewirtz) Subject: getting rid of header lines... Message-Id: <8210080839.28078@UCBARPA.BERKELEY.ARPA> Received: by UCBARPA.BERKELEY.ARPA (3.224 [10/16/82]) id A28075; 8-Nov-82 00:39:57-PST (Mon) Received: from UCBARPA.BERKELEY.ARPA by UCBVAX.BERKELEY.ARPA (3.227 [10/22/82]) id A02967; 8-Nov-82 15:40:11-PST (Mon) To: LIN at Mit-Mc, info-cpm at BRL, info-micro at BRL Via: Ucb-C70; 9 Nov 82 7:25-EST Via: Brl; 9 Nov 82 7:48-EST Via: Brl-Bmd; 9 Nov 82 7:58-EST I cheat. I run the mail through a filter that sees things like via: and deletes the line. Since its a Unix system I am on, such filtering works real well with pipes. You may have to do something rather grotesque in ITS. Good Luck, David 8-Nov-82 11:11:04,418;000000000000 Date: 8 Nov 1982 11:11:04 CST (Monday) From: Mike Meyer Subject: ZCPR2 To: info-cpm at BRL Cc: mwm at Okc-Unix Via: Okc-Unix; 8 Nov 82 12:15-EST Via: Brl; 8 Nov 82 12:56-EST Via: Brl-Bmd; 8 Nov 82 17:08-EST I finally get around to bringing up ZCPR, when I start hearing about another version. Can somebody tell me where I can get a copy of this mysterious creature? Thanx, Centronics Printer Interface To: Info-CPM at BRL cc: Info-Printers at Mit-Mc Via: Parc-Maxc; 8 Nov 82 17:29-EST Via: Brl; 8 Nov 82 17:52-EST Via: Brl-Bmd; 8 Nov 82 18:05-EST I'm looking to interface an Epson printer to a Vector Graphics System B using the parallel port on the BitStreamer I board. The hitch is, the data path must be 8 bits wide. That is, all 8 bits must be able to be transmitted from the computer to the printer. Has anyone done this? Any advice? Thanks, Bob 8-Nov-82 18:02:53,3247;000000000000 Date: 8 Nov 82 20:02:53-EST (Mon) From: Rick Conn To: Bomberger at Office-2 cc: info-cpm at BRL, info-micro at BRL Subject: SYSLIB, Copying Files, the ACG-NJ, and SIG/M Via: Brl; 8 Nov 82 20:24-EST Via: Brl-Bmd; 8 Nov 82 20:27-EST Alan, No, I don't like to get into the distribution business. If I do, I end up spending all my time copying files for people and not getting any work done. That's why we use MIT-MC like we do. The designer does not have to spend a lot of time doing such tasks, and those who want the files need only make the investment in time to get them. SIG/M, who will be receiving all of SYSLIB, is set up to do the copying for you. Their charge, if you supply the disks, is only $1/disk, and the money goes to the Amateur Computer Group of NJ to support SIG/M and club activities further. They charge $4/disk if they have to supply the disk. Typically, you have to be a club member to use SIG/M, and this costs only $14/year, and, with ACG-NJ being over 1100 members strong and putting out a very nice 20-page newsletter every month, I think it is well worth it. The ACG-NJ is also a major sponsor of the Trenton Comput- er Festival, which typically is held in April and includes a 5 acre flea market and many talks by various people in the micro- computer community. Sol Libes, who has a monthly column in Byte, is a very active member of the ACG-NJ, and the festival also in- cludes talks by him and others, such as Gary Kildall. The club is by no means devoted to CP/M, altho all the SIG/M disks are. The following user groups are present within the club: SIG/M, CP/M TRS-80 SIG68, 680x Apple PET 6502 North Star as well as the following software libraries: SIG/M North Star TRS-80 Disk Apple and special interest groups: Pascal 1802 Heath POLY-88 S-100 Atari IBM-PC If you wish to find out more about SIG/M and the ACG-NJ, the address is: Amateur Computer Group of New Jersey % Union County Technical Institute - Scotch Plains Campus 1776 Raritan Rd Scotch Plains, NJ 07076 I greatly perfer SIG/M to CP/M UG because (1) it is de- finitely a not-for-profit organization and you don't end up pay- ing a company for public domain software and (2) the prices are much more reasonable. The ACG-NJ will ship the entire SIG/M li- brary (now up to 75 8" disks) to any valid computer club, and they may distribute to their members absolutely free of charge (which is the way public domain software SHOULD be handled, as opposed to selling it, in my opinion). All the computer club has to do is pay for the disks. SIG/M has a published catalog, and their disks include, among other things, the old CP/M 1.4 SYSLIB and ZCPR1. Rick 8-Nov-82 18:08:51,552;000000000000 Date: 8 Nov 82 20:08:51-EST (Mon) From: Rick Conn To: Keith Petersen cc: Info-Micro at BRL, Info-Cpm at BRL Subject: Re: [Donald E. Hopki: Cheep disks] Via: Brl; 8 Nov 82 20:24-EST Via: Brl-Bmd; 8 Nov 82 20:29-EST One thing I forgot to mention about the ACG-NJ: they frequently put together group purchases on things, such as disk drives, disks, etc, and with 1100 members, if you get 1-10% involved, you have a LOT of buying power, which frequently results in very nice prices. Rick 9-Nov-82 03:06:22,811;000000000000 Date: 9-Nov-82 02:06:22-PST (Tue) From: UCBARPA.dag at Ucb-C70 (David Allen Gewirtz) Subject: morrow terminal Message-Id: <8210091006.25644@UCBARPA.BERKELEY.ARPA> Received: by UCBARPA.BERKELEY.ARPA (3.224 [10/16/82]) id A25641; 9-Nov-82 02:06:25-PST (Tue) Received: from UCBARPA.BERKELEY.ARPA by UCBVAX.BERKELEY.ARPA (3.227 [10/22/82]) id A17344; 9-Nov-82 02:09:24-PST (Tue) To: info-cpm at BRL Via: Ucb-C70; 9 Nov 82 7:29-EST Via: Brl; 9 Nov 82 7:52-EST Via: Brl-Bmd; 9 Nov 82 9:00-EST I have found the answer to my initialization problem. It seems that the morrow terminal acts like an adm-31, with a single exception...the row and column cursor commands are reversed. By making a patch to a designated address in wordstar, this problem was reasonably avoided. Thanks, David 9-Nov-82 03:08:50,815;000000000000 Date: 9-Nov-82 02:08:50-PST (Tue) From: UCBARPA.dag at Ucb-C70 (David Allen Gewirtz) Subject: modem77 Message-Id: <8210091008.25673@UCBARPA.BERKELEY.ARPA> Received: by UCBARPA.BERKELEY.ARPA (3.224 [10/16/82]) id A25672; 9-Nov-82 02:08:51-PST (Tue) Received: from UCBARPA.BERKELEY.ARPA by UCBVAX.BERKELEY.ARPA (3.227 [10/22/82]) id A17251; 9-Nov-82 02:06:14-PST (Tue) To: info-cpm at BRL Via: Ucb-C70; 9 Nov 82 7:27-EST Via: Brl; 9 Nov 82 7:49-EST Via: Brl-Bmd; 9 Nov 82 8:46-EST I have brought up modem version 7.70 to do transfers between two local machines. The protocol seems to work reasonably well at 1200 baud, but doesn't seem to be able to sync at 9600 baud. Is there any way to cause modem to work with itself at higher baud rates without a complete rewrite? Thanks, David 9-Nov-82 08:41:00,2760;000000000000 Date: 9 Nov 1982 (Tuesday) 1141-EDT From: PLATTS at Wharton-10 (Steve Platt) Subject: when to log-in a new disk? To: mknox at Utexas-11 cc: info-cpm at BRL Via: Wharton-10; 9 Nov 82 20:40-EST Via: Brl; 9 Nov 82 21:04-EST Via: Brl-Bmd; 9 Nov 82 21:09-EST When to (physically) log in a new disk? I've been using CP/M for 6 years now, and haven't seen a good answer. My new system, a US MICRO XOR (S100-12) system [side-note: excellent system, literally "plug it in and run", well worth the $$] has a BIOS which does disk format selection as follows: Upon warm-start, each disk is marked "unaccessed". The first time a disk is used (from the BIOS's point of view), a "format-check" operation is performed: track 0 sector 1 is read: this will *always* have 128 bytes -- and the last byte is checked for format information... E5 means SSSD 8", 1A means SSDD 8", etc. Unfortunately, the log-in of a disk from the BDOS's (and hence the program's) point of view is seperated completely from the BIOS login; so if you insert a new disk and do a BDOS(RELOG_DISK), the BDOS will note (for its use) that this is a new disk, the block-table must be recomputed, etc. The BIOS never hears of this... if the disk formats don't match (see program SWEEP, for instance), the system tends to die when accessing is attempted. This is an inherent flaw in the way *this particular BIOS* was designed -- I've seen BIOSs which use the timeout-overflow standard to check for disk format change. How did I get around this? I haven't, yet. I have planned out a solution, and will implement it when time allows. The solution is rather hacky, some of you out there may appreciate more than I: I assume that when a new disk is inserted, the first operation will be one which accesses the directory, starting at the beginning. This may be a directory search, DIR, file-open, whatever. So every time I go to do a READ, I check the TRACK/SECTOR combination to see if it is the combination which means "beginning-of-directory". (This can be precomputed for any and all disk formats based on the DPB.) If I *am* seeking the begin-dir., I over-seek to track 0 sector 1, read it in, and double-check the format. If this seems overly gross to you, try instead this: trace out in the BDOS to find the sequence of operations performed to login a disk... at some point, it will mark the disk (in the BDOS logged-in vector) as "unused" -- insert a call at this point to your routine in the BIOS which will perform the same operation, keeping its own version of the LOGIN_VECTOR. Then, when SELDSK is called, check it and.... Ain't CP/M wonderful? Isn't the concept of multiple-densities well handled? -Steve 9-Nov-82 13:08:24,1624;000000000000 Date: 9 Nov 1982 12:08:24-PST From: Cory.cc at Ucb-C70 To: human-nets at Rutgers, info-cpm at Mit-Mc, info-micro at BRL, info-pc at Usc-Eclb, ucbvax.net-general at Ucb-C70, ucbvax.net-misc at Ucb-C70, ucbvax.net-wanted at Ucb-C70 Subject: Request for donations Via: Mit-Mc; 9 Nov 82 18:55-EST Via: Brl; 9 Nov 82 19:19-EST Via: Brl-Bmd; 9 Nov 82 19:25-EST We, the Computer Science Undergraduate Association (CSUA) of the University of California at Berkeley, are launching a hardware drive to acquire equipment to provide the students of UCB with a varied computing environment. We are a part of the Associated Students of the University of California, and as such are a non-profit organization. We would be happy to write out a receipt for any and all computer equipment donated to us so it can be claimed as a tax exemption, and provided the equipment is received before the end of the year, it can be claimed as a deduction for this year. We are in need of terminals, lineprinters, modems, disk drives, and any other peripherals. We would accept any type of computing equipment, ranging from a Vax 11/780 running VMUnix to a 6800 system running Flex. We would also accept just the PC boards, or a full system. Anything would be greatly appreciated. In addition, we would especially like to acquire 16 bit processors capable of running Unix, since almost all the students here program on Unix systems. If you or your company can donate equipment, or if you know someone who might be able to help us, please reply to: csua@berkeley (ARPA) ucbvax!csua (UUCP) 9-Nov-82 19:11:00,387;000000000000 Date: 9 November 1982 21:11-EST From: Keith Petersen Subject: HEXified SYSLIB.REL To: Info-Cpm at BRL Via: Mit-Mc; 9 Nov 82 21:20-EST Via: Brl; 9 Nov 82 21:32-EST Via: Brl-Bmd; 9 Nov 82 21:47-EST There have been several requests for HEXifying SYSLIB.REL. That has been done so that those who cannot FTP COM files may get it. It's in AR19:CPM;SYSLIB RELHEX 9-Nov-82 19:15:00,410;000000000000 Date: 9 November 1982 21:15-EST From: Charlie Strom Subject: New LU doc file To: info-cpm at BRL Via: Mit-Mc; 9 Nov 82 21:21-EST Via: Brl; 9 Nov 82 21:33-EST Via: Brl-Bmd; 9 Nov 82 21:48-EST Gary Novosielski, the author of LU (Library Utility), has revised (actually corrected) the file documenting the structure of LU library files. The new file is on MC - AR29:CPM;LUDEF1 DOC. 9-Nov-82 19:56:00,2117;000000000000 Date: 9 November 1982 21:56-EST From: Paul L Kelley Subject: MODEM781 To: INFO-CPM at BRL cc: W8SDZ at Mit-Mc, FJW at Mit-Mc, PLOUFFE at Mit-Mc, RGF at Mit-Mc, CSTROM at Mit-Mc, STORK at Mit-Mc, RIZZI at Usc-Isib Via: Mit-Mc; 10 Nov 82 7:13-EST Via: Brl; 10 Nov 82 9:35-EST Via: Brl-Bmd; 10 Nov 82 10:20-EST The directory JCAF; on MIT-MC contains the following files: MODEM 781ASM MODEM 781COM MODEM 781HEX MODEM 78LIB MODEM 781HIS MCNFG 781ASM MNUM 781ASM This version of MODEM7 has not been put in AR61:CPM; since Keith is going to upload another version for me to combine with the present version. In the meantime some of you may want to use this version. A description of the changes follows: ;11/10/82 Combined MODEM771 and MODEM780 as follows: ; ; 1. Used erase file function in 780, ; 2. Used 780 code to make display of error count start at 1 ; and changed display to decimal, ; 3. Used 780 idea for throttled output on terminal mode ; transfer of text file to remote but wrote new routines ; including one for user to set speed, ; 4. Moved disk reset to DIR routine as in 780, ; 5. Used 780 code to give kbytes free on DIR command but ; modified to give kbytes free on requested drive instead ; of default drive. ; ; Made the following changes: ; ; 1. Eliminated IMSAI front panel routines, ; 2. Changed so PMMI control-D (disconnect) checks for file ; open on returning to menu mode, ; 3. Fixed file display on bulk transfer so that spaces are ; eliminated and period is inserted if required, ; 4. Changed M(enu) to H(elp) command, ; 5. Added code to allow echo mode to use optional toggling of ; send linefeed after carriage return, ; 6. Added toggling of Checksum/CRC modes on file receive, ; 7. Added optional code to clear to end of screen on next line ; from current cursor position when returning from terminal ; mode, this eliminates jumbled screen when working remote ; which positions cursor. ; ;P.L.Kelley 10-Nov-82 02:54:29,618;000000000000 Date: 10 Nov 82 02:54:29 EST (Wed) From: Ben Goldfarb Subject: Re: CP/M disk logins To: mknox at Utexas-11, info-cpm at BRL Via: UCF-CS; 10 Nov 82 3:53-EST Via: Udel-Relay; 10 Nov 82 7:05-EST Via: Brl; 10 Nov 82 9:34-EST Via: Brl-Bmd; 10 Nov 82 10:13-EST The BDOS asks the BIOS to log in a disk by passing a flag in the E register when calling SELDSK. As to how the BDOS knows that a log in is necessary, I can only surmise that the directory checksum is verified before any disk write, but I have nothing with which to back that up. Ben Goldfarb 10-Nov-82 06:58:54,369;000000000000 Date: 10 Nov 82 8:58:54-EST (Wed) From: Rick Conn To: info-cpm at BRL cc: info-micro at BRL Subject: SYSLIB.REL Hex File Via: Brl; 10 Nov 82 10:08-EST Via: Brl-Bmd; 10 Nov 82 11:34-EST The CP/M SYSLIB AR on MIT-MC now contains a HEX file of SYSLIB.REL for those who can't download binary, thanks to Keith. Enjoy. Rick 10-Nov-82 17:53:56,1682;000000000000 Date: 10 Nov 82 19:53:56-EST (Wed) From: Rick Conn To: info-cpm at BRL cc: info-micro at BRL Subject: SYSLIB Index Via: Brl; 10 Nov 82 20:01-EST Via: Brl-Bmd; 10 Nov 82 20:13-EST At the request of some users, an index of the SYSLIB files now on MIT-MC in AR19:CPM is available. This file will be placed in AR19:CPM shortly, but for current reference, here it is: **** SYSLIB Files on MIT-MC in AR19:CPM **** The SYSLIB?.HLP files are in ASCII text, source form. The SYSLIB.REL file is in relocatable object form (binary). The SYSLIB??.WQ files (manual) are WordStar-formatted files which have been SQueezed by the SQ program to reduce their storage space. You will have to run USQ on them after downloading in order to get the original text back. Be sure to LMODEM these files as COM files. DEBUG MAC Outdated SYSLIB Debug Package -- Will be Upgraded Later INDEX SYSLIB This index to the files SYSLB HLP Root Node of SYSLIB Help Tree SYSLB WQ Main Body of SYSLIB Manual SYSLB1 HLP \ SYSLB2 HLP \ SYSLB3 HLP \ SYSLB4 HLP \ SYSLB5 HLP \ SYSLB6 HLP \ SYSLIB Help Files SYSLB7 HLP / Lower Nodes of the SYSLIB Help Tree SYSLB8 HLP / SYSLB9 HLP / SYSLBA HLP / SYSLBB HLP / SYSLBC HLP / SYSLBH WQ Table of Contents, Indexes of SYSLIB Manual SYSLBS WQ Section 21: Sample Programs Section of SYSLIB Manual SYSLIB REL SYSLIB Relocatable Library File SYSLIB RELHEX SYSLIB Relocatable Library File in Hex Form (ASCII text) so people who can't download binary files can get to SYSLIB 10-Nov-82 18:53:00,458;000000000000 Date: 10 Nov 1982 2053-EST From: Andrew Scott Beals Subject: Re: JRT Pascal file I/O bug? To: MADLER at Mit-Ml cc: Info-cpm at BRL In-Reply-To: Your message of 10-Nov-82 2000-EST Via: Mit-Mc; 10 Nov 82 20:53-EST Via: Brl; 10 Nov 82 21:19-EST Via: Brl-Bmd; 10 Nov 82 21:24-EST what do you expect for $29.95? then again, what do you expect from (ugh!) pascal? use C, and you'll sleep easier. -andy ------- 10-Nov-82 22:52:00,587;000000000000 Date: 10 Nov 1982 at 2352-CST From: mknox at Utexas-11 Subject: CP/M disk logins in BIOS To: info-CPM at BRL Via: Utexas-11; 11 Nov 82 11:19-EST Via: Brl; 11 Nov 82 11:37-EST Via: Brl-Bmd; 11 Nov 82 11:59-EST My thanks to Ben Goldfarb for pointing out the secret. An undocumented feature in BDOS provides that the LSB of the E-register is a 0 if this is the first time (i.e. after a cold or warm boot) that SELDSK has been called to select the disk specified in the C-register. Calls for a disk which has been previously logged in all have that LSB set. ------- 11-Nov-82 02:31:52,354;000000000000 Date: 11 Nov 82 4:31:52-EST (Thu) From: Richard Conn (CENTACS CSSD) To: info-cpm at BRL cc: info-micro at BRL Subject: SYSLIB INDEX FIle Via: Brl-Bmd; 11 Nov 82 11:24-EST An index to the available SYSLIB files is on MIT-MC in AR10:CPM as INDEX SYSLIB. This explains what the files in AR19:CPM are. Rick 11-Nov-82 14:36:38,500;000000000000 Date: 11 Nov 82 16:36:38-EST (Thu) From: Rick Conn To: Mike Meyer cc: info-cpm at BRL, mwm at Okc-Unix Subject: Re: ZCPR2 Via: Brl; 11 Nov 82 16:51-EST Via: Brl-Bmd; 11 Nov 82 17:00-EST ZCPR2 and its utilities are currently in beta testing. Alpha testing results are quite positive (to be exact, I'm running ZCPR2 at this moment), and I expect to release ZCPR2 by Christmas. ZCPR2 is not yet released to the public domain. Rick 11-Nov-82 17:35:00,401;000000000000 Date: 11 November 1982 19:35-EST From: Charlie Strom Subject: modem77 To: UCBARPA.dag at Ucb-C70 cc: Info-CPM at BRL Via: Mit-Mc; 12 Nov 82 10:40-EST Via: Brl; 12 Nov 82 11:04-EST Via: Brl-Bmd; 12 Nov 82 11:30-EST David, Try running MODEM770 in the quiet transfer mode. Doing this prevents display of the console messages and ought to enable you to run at 9600 baud. 11-Nov-82 17:52:00,686;000000000000 Date: 11 November 1982 19:52-EST From: Gail Zacharias Subject: getting rid of header lines... To: UCBARPA.dag at Ucb-C70 cc: LIN at Mit-Mc, info-cpm at BRL, info-micro at BRL Via: Mit-Mc; 12 Nov 82 10:40-EST Via: Brl; 12 Nov 82 11:05-EST Via: Brl-Bmd; 12 Nov 82 11:32-EST On ITS or Twenex, you don't need to do anything nearly as grotesque as running your mail through another program. BABYL filters out any header lines you wish, Via: or anything else, all you have to do is tell it what header fields you don't care to see. (Golly gee, I sure do hope your filter didn't screw up your mail just because I had a line beginning with "Via:" in the text) 11-Nov-82 18:18:00,556;000000000000 Date: 11 Nov 1982 2018-EST From: Andrew Scott Beals Subject: Re: modem77 To: UCBARPA.dag at Ucb-C70 cc: info-cpm at BRL In-Reply-To: Your message of 11-Nov-82 1722-EST Via: Mit-Mc; 12 Nov 82 10:41-EST Via: Brl; 12 Nov 82 11:06-EST Via: Brl-Bmd; 12 Nov 82 12:08-EST i've been using modem2 (orig wc version) at 9600 baud VERY reliable for 6 mos now...your problem is that modem7 is a toatal crock of , and is written VERY poorly! ------- 11-Nov-82 21:28:51,621;000000000000 Date: 11-Nov-82 20:28:51-PST (Thu) From: UCBARPA.dag at Ucb-C70 (David Allen Gewirtz) Subject: modem77 Message-Id: <8210120428.1590@UCBARPA.BERKELEY.ARPA> Received: by UCBARPA.BERKELEY.ARPA (3.224 [10/16/82]) id A01586; 11-Nov-82 20:28:57-PST (Thu) Received: from UCBARPA.BERKELEY.ARPA by UCBVAX.BERKELEY.ARPA (3.227 [10/22/82]) id A07002; 11-Nov-82 20:26:05-PST (Thu) To: CSTROM at Mit-Mc, UCBARPA.dag at Ucb-C70 Cc: Info-CPM at BRL Via: Ucb-C70; 12 Nov 82 10:43-EST Via: Brl; 12 Nov 82 11:11-EST Via: Brl-Bmd; 12 Nov 82 12:09-EST Thanks... I will try it and let you know how it turns out. David 12-Nov-82 00:30:07,912;000000000000 Date: 11-Nov-82 23:30:07-PST (Thu) From: UCBARPA.dag at Ucb-C70 (David Allen Gewirtz) Subject: Morrow terminal Message-Id: <8210120730.3459@UCBARPA.BERKELEY.ARPA> Received: by UCBARPA.BERKELEY.ARPA (3.224 [10/16/82]) id A03458; 11-Nov-82 23:30:09-PST (Thu) Received: from UCBARPA.BERKELEY.ARPA by UCBVAX.BERKELEY.ARPA (3.227 [10/22/82]) id A11385; 11-Nov-82 23:27:07-PST (Thu) To: info-cpm at BRL Via: Ucb-C70; 12 Nov 82 10:44-EST Via: Brl; 12 Nov 82 11:11-EST Via: Brl-Bmd; 12 Nov 82 12:11-EST I have found the answer to my question about the morrow terminal. To correct some confusion however, it was not information about how to install things into wordstar, but the peculiarities of the morrow terminal. The thing came with no documentation at all, so all of the control sequences had to be worked out by trial and error (and a call to Morrow). Thanks for all the help. David 12-Nov-82 09:46:00,437;000000000000 Date: 12 Nov 1982 1046-CST From: John Otken Subject: JRT Pascal To: info-cpm at BRL Via: Utexas-20; 12 Nov 82 11:48-EST Via: Brl; 12 Nov 82 12:04-EST Via: Brl-Bmd; 12 Nov 82 12:31-EST Prospective JRT buyers might want to read the review of it in Dr. Dobbs a month or so back. Their opinion was that it was too unstandard and too unstable even for 29.95. I have never used it myself. John. ------- 12-Nov-82 11:23:00,598;000000000000 Date: 12 Nov 1982 1323-EST From: Chuck Perilli Subject: Re: morrow terminal To: UCBARPA.dag at Ucb-C70 cc: Info-CPM at BRL Postal-address: HQ AFSC/ACDPV, Andrews AFB, DC 20334 Phone: (301)981-2155; AUTOVON: 858-2155 In-Reply-To: Your message of 9-Nov-82 0506-EST Via: Afsc-Hq; 12 Nov 82 13:32-EST Via: Brl; 12 Nov 82 13:34-EST Via: Brl-Bmd; 12 Nov 82 13:42-EST You are absolutely correct. The CBIOS in the Micro Decision is kluged to accomodate this "feature". When other terminals are used on the MD, the kluge must be patched out. ---Chuck ------- 12-Nov-82 15:09:00,965;000000000000 Date: 12 Nov 1982 1709-EST From: Bob Clements Sender: CLEMENTS at Bbna Subject: when to log-in a new disk? To: PLATTS at Wharton-10 Cc: mknox at Utexas-11, info-cpm at BRL Via: Bbna; 12 Nov 82 17:11-EST Via: Brl; 12 Nov 82 17:16-EST Via: Brl-Bmd; 12 Nov 82 17:21-EST In response to your message of 12 Nov 1982 1628-EST Either I misunderstand your question, or the answer is much simpler than Steve's suggestion. Whenever the BDOS calls the SELDSK entry of BIOS, it supplies its idea of whether the drive is new. Bit 0 of register E is a 1 if the drive is already logged, and a 0 if it's new, as determined by the "logged disks" vector. So your BIOS should check that bit and do any needed setup only when the bit is zero. So if you go through the warm boot routine (by typing ^C) when you change media, you're all set. If you're trying to detect changed disks WITHOUT a warm boot, I can't help you. /Rcc ------- 12-Nov-82 22:30:00,913;000000000000 Date: 13 November 1982 00:30-EST From: Ronald G Fowler Subject: [RGF: when to log-in a new disk?] To: info-cpm at BRL Via: Mit-Mc; 13 Nov 82 0:31-EST Via: Brl; 13 Nov 82 0:35-EST Via: Brl-Bmd; 13 Nov 82 0:38-EST Date: 13 November 1982 00:24-EST From: Ronald G. Fowler To: PLATTS at WHARTON-10 cc: RGF, mknox at UTEXAS-11 Re: when to log-in a new disk? Steve, your BIOS should relog a disk whenever its SELDSK entry is called with a 0 in the E register; this bit is actually the "login vector" rotated such that the requested drive's bit is in DE least-significant-bit. This is not documented in the system Alteration guide but is supported for all SELDSK calls in both CP/M 2.x, MP/M II and CP/M III (so I'm told). If DR had bothered to mention this in the original documentation, disk-relogging problems like this would never have come about. --Ron 12-Nov-82 22:31:00,620;000000000000 Date: 13 November 1982 00:31-EST From: Ronald G Fowler Subject: [RGF: CP/M disk logins] To: info-cpm at BRL Via: Mit-Mc; 13 Nov 82 0:32-EST Via: Brl; 13 Nov 82 0:49-EST Via: Brl-Bmd; 13 Nov 82 1:02-EST Date: 13 November 1982 00:27-EST From: Ronald G. Fowler To: goldfarb.ucf-cs at UDEL-RELAY cc: RGF, mknox at UTEXAS-11 Re: CP/M disk logins In fact, once accessed, a disk is considered logged until the next warm-boot, even if it has changed. The bit passed in E is actually the login vector rotated such that e reg bit 0 has the requested login vector bit. --Ron 13-Nov-82 10:45:00,449;000000000000 Date: 13 November 1982 12:45-EST From: Charlie Strom Subject: New Epson files To: info-cpm at BRL cc: INFO-PRINTERS at Mit-Mc Via: Mit-Mc; 16 Nov 82 2:35-EST Via: Brl; 16 Nov 82 6:41-EST Via: Brl-Bmd; 16 Nov 82 9:33-EST I have uploaded the following Epson setup files to MC: AR70:CPM;PRINTR C PRINTR COM This is a nicely written utility that should be easily adapted to printers other than the MX80. 13-Nov-82 12:53:00,734;000000000000 Date: 13 November 1982 14:53-EST From: Keith Petersen Subject: Using MODEM7xx at high baud rates To: Info-Cpm at BRL Via: Mit-Mc; 16 Nov 82 2:36-EST Via: Brl; 16 Nov 82 6:41-EST Via: Brl-Bmd; 16 Nov 82 9:35-EST Date: 12 November 1982 00:33-EST From: Keith Petersen Subject: modem77 To: UCBARPA.dag at Ucb-C70 The secret of running MODEM2 and MODEM7 at high baud rates is to use the "Q" (quiet) mode option. This prevents the console status messages from being printed. It's that delay that causes it to fail. If console status messages are never needed, consider XMODEM. It ALWAYS runs in the quiet mode, which is nice because you don't have to remember to type that option. 13-Nov-82 12:59:00,587;000000000000 Date: 13 November 1982 14:59-EST From: Keith Petersen Subject: when to log-in a new disk? To: PLATTS at Wharton-10 cc: Info-Cpm at BRL, mknox at Utexas-11 Via: Mit-Mc; 16 Nov 82 2:36-EST Via: Brl; 16 Nov 82 6:41-EST Via: Brl-Bmd; 16 Nov 82 9:38-EST Put your density check routine in the CBIOS "HOME" routine. CP/M does a "HOME" (usually translated to a track 0 seek or "restore") before doing directory operations, in order to assure proper re-calibration of the drive. If this works for you, please tell Info-Cpm. If not, tell me. Thanks. --Keith 13-Nov-82 20:49:00,1866;000000000000 Return-path: RIZZI@USC-ISIB Date: 13 Nov 1982 1949-PST From: Bill Rizzi Subject: in defense of modem7 To: info-cpm at BRL Via: Usc-Isib; 16 Nov 82 0:15-EST Via: Brl; 16 Nov 82 6:30-EST Via: Brl-Bmd; 16 Nov 82 7:32-EST Really now, modem7 isn't quite as bad as it has been made out to be in a recent flame to this list. While a size of 52 sectors might be considered a bit hefty by some, its advantages far outweigh its bulk, even when one is limited (such as I) to 241K bytes per disk. I use it every day as a remote terminal and especially for file transfer. While I am aware that older versions had their problems, I find the the latest (modem770+) work quite nicely. The user interface is improved with each version, allowing on-the-fly and initial setting of a variety of parameters that allow provide a customized version. In addition, it is very easy to tailor for any sort of 8080/Z80 hrdand communications hardware. The only machine dependancy in`then the code is the data/status port number and the receive/send bit number. It handles CRC/checksum, wild-card file transfer (eg. *.*), dir and era functions. It has an on-line phone number library and provides a total environment as opposed to modem2 which is a one mode-per-sho-per-shot deal. I have been able to transfer from an IBM PC running modem2 to a Z80 CP/M machine running modem7 at 9600 baud using a null modem cable. I did not even need to use quiet mode. **DISCLAIMER** I have been somewhat involved in the development and testing of the most recent versions of modem7 and can be expected to be somewhat partial to it. While not overly familiar with the code I have used most of the options and find that they work as advertised in the online menu. Bill Rizzi (RIZZI @ ISIB) ------- 14-Nov-82 02:25:00,531;000000000000 Date: 14 November 1982 04:25-EST From: Jerry E Pournelle Subject: JRT Pascal To: CC.Otken at Utexas-20 cc: INFO-CPM at Mit-Mc Via: Mit-Mc; 16 Nov 82 4:23-EST Via: Brl; 16 Nov 82 7:10-EST Via: Brl-Bmd; 16 Nov 82 11:55-EST My view of JRT is that it is worth $29.95 but not much more. The error messages are not Pascal and the language is not Pascal; and the eextensions are not all that good. But that is my view, and perhaps I'm wrong. I say that because I am weary of peopl e who say it for me. 14-Nov-82 06:56:00,640;000000000000 Date: Sunday, 14 November 1982 08:56-EST Sender: X.GYRO.MIT-OZ at BRL From: X.GYRO at Mit-Mc To: PLATTS at Wharton-10 (Steve Platt) Cc: info-cpm at BRL Subject: when to log-in a new disk? In-reply-to: The message of 9 Nov 1982 () 1141-EDT from PLATTS at Wharton-10 (Steve Platt) Via: Mit-Mc; 16 Nov 82 4:23-EST Via: Brl; 16 Nov 82 7:10-EST Via: Brl-Bmd; 16 Nov 82 11:57-EST There is a well-defined (though perhaps not documented; I forget) way for the BIOS to know about BDOS disk resets. When the BDOS calls SELDSK, bit 0 of E is 0 if the BDOS thinks the disk is being accessed the first time, else 1. -- Scott 14-Nov-82 20:22:00,3122;000000000000 Date: 14 Nov 1982 (Sunday) 2322-EDT From: PLATTS at Wharton-10 (Steve Platt) Subject: An open letter to Andrew Scott Beals To: rms.g.bandy.mit-oz at Mit-Mc, info-cpm at BRL Via: Wharton-10; 16 Nov 82 15:46-EST Via: Brl; 16 Nov 82 16:16-EST Via: Brl-Bmd; 16 Nov 82 16:40-EST Dear Mr. Beals, In the course of the past 5 days, you have transmitted the following three letters across the 'net. The first was to me personally, the latter two CC:'ed to the entire INFO-CPM community. The tone existing in each of the three letters is, in my opinion, not befitting to the mature group of individuals sharing these resources. I take personal offense to the first letter: it (my letter) was in response to a request for information; admittedly I was wrong, out of my own ignorance (I have used CP/M and similar OS's for quite a long time, but had never had the actual need to use this particular feature). As to the first letter: Date: 13 Nov 1982 0056-EST From: Andrew Scott Beals Subject: Re: when to log-in a new disk? To: PLATTS at WHARTON-10 if you don't liek it.k, don't use it, you pirate!!! ------- I do not like the tone of the letter; furthermore, the implication of the last phrase is a blatant lie (CP/M license 168-703). As to your second two letters: Date: 10 Nov 1982 2053-EST From: Andrew Scott Beals Subject: Re: JRT Pascal file I/O bug? To: MADLER at Mit-Ml cc: Info-cpm at BRL what do you expect for $29.95? then again, what do you expect from (ugh!) pascal? use C, and you'll sleep easier. -andy ------- Date: 11 Nov 1982 2018-EST From: Andrew Scott Beals Subject: Re: modem77 To: UCBARPA.dag at Ucb-C70 cc: info-cpm at BRL i've been using modem2 (orig wc version) at 9600 baud VERY reliable for 6 mos now...your problem is that modem7 is a toatal crock of , and is written VERY poorly! ------- They further indicate a total lack of tolerance of anything different by yourself; in fact, you seem to desire to aggresively destroy anything you you are not currently enraptured with. Such an attitude is not conductive to harmonious existance, nor towards the development and propagation of knowledge and information. (I know for one, if you were to put out a request for information or some product I had written, I would hesitate to answer, knowing that if it does not fit YOUR purposes exactly you might very well proceed to describe it to others as... well, I will let the latter two letters speak for themselves.) In summary, Mr. Beals, I can only say that I hope you were having an "off" few days when these letters were written and sent; and I hope you will be more considering of your actions in the future. Stephen M. Platt 15-Nov-82 23:55:22,2190;000000000000 Date: 16 Nov 82 1:55:22-EST (Tue) From: Rick Conn To: TBOWERMAN at Office-10 cc: info-cpm at BRL Subject: Assemblers Via: Brl; 16 Nov 82 6:38-EST Via: Brl-Bmd; 16 Nov 82 7:48-EST Tom, The CP/M assembler business IS somewhat confusing with all the similar names and different capabilities for the various assem- blers out there. Here is a quick summary which I hope will answer some of your questions: ASM (I call it ASM2) -- this is the assembler that comes with CP/M 2.2; what I call ASM is the assembler that came with CP/M 1.4, and the major difference is that with ASM, quoted text is always capitalized while ASM2 allows lower-case to pass thru; ASM and ASM2 have no macro capability, but do support conditional assembly, SET, and a few nice operations in the operand field MAC -- this is DR's upgrade to ASM and ASM2 (DR=Digital Research, who wrote CP/M); this is basically the same assembler, but it can use macros and macro libraries; it still generates just HEX files as output M80/L80 -- this is Microsoft's assembler, which is used to assem- ble programs requiring SYSLIB; M80 is the assembler, which sup- ports nice features found in MAC, such as macros, AND supports relocatable libraries (which MAC does not); the output of M80 is a REL file, NOT a HEX file, and this output is then passed to L80; L80 can take a number of REL files and put them together and generate a HEX or a COM file or both; M80 also supports both In- tel and Zilog mnemonics, while MAC and ASM/ASM2 just support In- tel mnemonics, altho there is a Z80 macro library which comes with MAC to allow you to assemble for the Z80-specific instruc- tions, but does not allow Zilog mnemonics Other assemblers are available, but these are the main ones I use and know about. I use M80/L80 for most of the ZCPR2 work, but MAC is required to assemble ZCPR2 itself (and ZCPR1 for that matter). A big difference is that MAC allows longer names than M80 (M80 is limited to 6 chars in my version). Hope this helps. Feel free to write if you still have questions. Rick 16-Nov-82 12:26:00,1089;000000000000 Date: 16 Nov 1982 1126-PST From: Bill Rizzi Subject: C file package wanted To: info-cpm at BRL, info-micro at BRL Via: Usc-Isib; 16 Nov 82 14:27-EST Via: Brl; 16 Nov 82 15:05-EST Via: Brl-Bmd; 16 Nov 82 15:21-EST I am looking for a file management package accessible from a language like C. Ideally, it would consist of individual loader modules which could be linked in with an application written in C. It might also contain separate command language modules. It would be nice to have the source available, particularly if it is C code. A package close to what I am looking for is BT-80 from Microsoft. This package supports b-tree record indexing, however it is written primarily for use with PLI/80, which is required for running BT-80. As interest in such a package has been expressed by several people I have contacted, I will summarize results of any replies which are made directly to me, however I think the topic is of broad enough interest to be discussed on-line. Thanks for any information, Bill (RIZZI@ISIB) ------- 16-Nov-82 14:20:00,618;000000000000 Date: 16 Nov 1982 1620-EST From: ELIOT at Mit-Dms (Eliot Scott Ramey) To: info-cpm at BRL Subject: PSET.SRC Message-id: <[MIT-DMS].249509> Via: Mit-Dms; 16 Nov 82 16:18-EST Via: Brl; 16 Nov 82 17:16-EST Via: Brl-Bmd; 16 Nov 82 17:33-EST The file PSET.SRC (.SRC = Pascal/MT+) is on AR31:CPM; PSET is a printer option selection program. As is, it is set up for the OKIDATA series of printers. Anybody with Pascal/MT+ and a little pascal knowledge can easily modify it for an EPSON. This is NOT a menu driven program. All options are entered on the command-line. Enjoy! -Eliot at Mit-DM 16-Nov-82 19:55:00,1560;000000000000 Date: 16 November 1982 21:55-EST From: Charlie Strom Subject: Cache/Q To: info-cpm at BRL Via: Mit-Mc; 16 Nov 82 22:41-EST Via: Brl; 16 Nov 82 22:44-EST Via: Brl-Bmd; 16 Nov 82 22:51-EST I feel that I must warn potential purchasers of the disk buffering program called Cache/Q that it has serious bugs and is an unacceptable product in my opinion. This program is currently being heavily advertised in Infoworld. The bugs I found about 8 weeks ago are that the feature of specification of file type to buffer does not work (it is an all or nothing choice now) and even more seriously, the author forgot to include a BDOS disk reset upon warm boot. The result is that one cannot switch disks under the buffering program. It appears that development was performed on a hard disk and there were no beta tests using floppies! I have spoken to the author at least four times since I discovered these bugs and have gotten a different excuse each time; my next (and last verbal effort) will be for a request for the source code so I can fix the problems myself, an immediate replacement or a refund. I am not sanguine to say the least. The design of the program, which allows the use of bank-switched memory (a nice feature) is to buffer on a file rather than a track basis - a big mistake. I see in the latest Infoworld ad that Tecne Software will be at the L.A. Computer Showcase Expo Nov. 18-20. Are there any souls interested in calling this guy on the defective software he is peddling? Charlie Strom 16-Nov-82 20:10:19,2684;000000000000 Date: 16-Nov-82 19:10:19-PST (Tue) From: UCBARPA.dag at Ucb-C70 (David Allen Gewirtz) Subject: CHDIR, NOCLR, and BDS C 1.5 Message-Id: <8210170310.22528@UCBARPA.BERKELEY.ARPA> Received: by UCBARPA.BERKELEY.ARPA (3.224 [10/16/82]) id A22526; 16-Nov-82 19:10:21-PST (Tue) Received: from UCBARPA.BERKELEY.ARPA by UCBVAX.BERKELEY.ARPA (3.227 [10/22/82]) id A00484; 16-Nov-82 19:08:27-PST (Tue) To: info-cpm at BRL Via: Ucb-C70; 17 Nov 82 0:59-EST Via: Brl; 17 Nov 82 1:15-EST Via: Brl-Bmd; 17 Nov 82 1:21-EST I have uploaded the file CPM;NOCLR C to MC. NOCLR contains a function called noclrex() which is used to perform a hack on programs like CHDIR, when compiled with version 1.50 of the BDS C Compiler. IT appears that Leor's newest version has the runtime system (C.CCC) clear out the external data area before actually executing the compiled program. Now this is all well and good for nearly all of the programs written. One program that does not work well when the externals are initialized is Rick Conn's CHDIR.C program. What CHDIR does is create directory names and place them in tables that are external variables to the compiler. When the user is done entering names, CHDIR writes itself back out to disk, including the external data, so that the next time it runs, it is already initialized. The problem is that when a compiled program is run, before any of the user-written code is executed, it performs a number of initializations, including clearing external data. NOCLR is used to cause the run-time package to skip the stage where it clears the external data by poking a jump instruction into memory. When CHDIR is executed initially, the external data is cleared. The, when noclrex() is called, a jump instruction is used to bypass the segment that clears the externals. Finally, when the program is written out with changes, this bypass is left in so the externals won't be cleared the next time through. Because some people do not like to have their programs hacked up and because this only affects those using version 1.5 of the compiler, I have not made any changes to CHDIR.C. SHould you need to bypass the phase that clears externals, simply poke a JMP XXXX into the runtime space or use NOCLR.C. A call of noclrex() early on in the program (any time before write-out) will solve the problem. If, for some reason, it doesn't work, check the addresses in NOCLR and C.CCC. My version of C.CCC comes from a pre-release version of BDS C 1.5 and may not be the same as yours. Finally, I would appreciate it if someone would move NOCLR to a proper archive directory. Enjoy,. David 17-Nov-82 05:46:00,414;000000000000 Date: 17 Nov 1982 0746-EST From: Andrew Scott Beals Subject: modem at high baud rates To: w8sdz at Mit-Mc, ucbarpa.dag at Ucb-C70, info-cpm at BRL Via: Mit-Ml; 17 Nov 82 7:49-EST Via: Brl; 17 Nov 82 8:51-EST Via: Brl-Bmd; 17 Nov 82 8:57-EST i've used it just fine at 9600 baud WITHOUT running it in quiet mode. (i think that the console was running at 19.2kbaud) ------- 17-Nov-82 12:50:00,727;000000000000 Date: 17 Nov 1982 (Wednesday) 1450-EST From: MARON at Lll-Mfe Subject: Big Board II request To: info-cpm at BRL Via: Lll-Mfe; 17 Nov 82 17:48-EST Via: Brl; 17 Nov 82 18:19-EST Via: Brl-Bmd; 17 Nov 82 18:34-EST I have gotten my BBII up. Im still building a house for it but when done, maybe this weekend it will have a 5mB Shugart 600 drive hooked on. I built the kit form. I suggest that the anxiety is not worth the savings. Buy a A&T version. The kit is definitely for the very experienced. The point of this query: someone said that they had some software for the PROM programmer feature of the board. I am looking for that software so please respond if you have something running for the BBII.--Neil 17-Nov-82 14:12:00,347;000000000000 Date: 17 Nov 1982 1312-PST From: SWG.LPRESS at Usc-Isi Subject: change of address To: info-cpm at Mit-Mc Via: Mit-Mc; 17 Nov 82 17:45-EST Via: Brl; 17 Nov 82 18:16-EST Via: Brl-Bmd; 17 Nov 82 18:33-EST could you please chnage my distribution address from isisw.moore at rutgers to swg.lpress at isi? Thanks larry press ------- 17-Nov-82 16:37:00,522;000000000000 Date: 17 November 1982 18:37-EST From: Charlie Strom Subject: New LU support files To: INFO-CPM at BRL Via: Mit-Mc; 17 Nov 82 18:44-EST Via: Brl; 17 Nov 82 18:53-EST Via: Brl-Bmd; 17 Nov 82 19:03-EST I have uploaded the following files to MC: AR29:CPM;LDIR C LDIR MSG LDIR COM These files allow a directory function on a .LBR file (produced by LU.COM) and is particularly useful for a remote CP/M system if one does not want to leave LU.COM publicly accessible. 18-Nov-82 02:25:00,669;000000000000 Date: 18 November 1982 04:25-EST From: Jerry E Pournelle Subject: Cache/Q To: CSTROM at Mit-Mc cc: INFO-CPM at Mit-Mc Via: Mit-Mc; 18 Nov 82 4:22-EST Via: Brl; 18 Nov 82 4:38-EST Via: Brl-Bmd; 18 Nov 82 4:49-EST CACHE/Q I never tried, but MicroCache from England looks to be an excellent cache system making use of bank switch memory. MicroCache works essentially invisibly and can be as small as a few K or up to about 8 megabytes for cache memory. Naturally the thing most often accessed is kept; with small memory that is likley to be the directory of the disk most often written to. Even then it speeds things up nicely. JEP 18-Nov-82 06:02:08,1569;000000000000 Date: 18 Nov 82 8:02:08-EST (Thu) From: Rick Conn To: David Allen Gewirtz cc: info-cpm at BRL Subject: Re: CHDIR, NOCLR, and BDS C 1.5 26; 16-Nov-82 19:10:21-PST (Tue) 84; 16-Nov-82 19:08:27-PST (Tue) Via: Brl; 18 Nov 82 8:14-EST Via: Brl-Bmd; 18 Nov 82 8:31-EST Sorry about the inconvenience with CHDIR. I have really considered the need of CHDIR to write itself back out to disk somewhat of a cludge, and have already designed a new CHDIR which runs in the ZCPR2 environment. Am really hoping to get ZCPR2 out before Christmas, and, unlike ZCPR1, ZCPR2 is coming with a whole set of utility programs (probably 30 or 40 before I'm finished) which are intimately linked to each other. CHDIR and CD are parts of the heart of the system, and CHDIR now creates a file containing the directory names rather than storing them internal- ly. The reason for this is that ALL of the ZCPR2 utilities will be supporting a named directory structure, based on the file created by CHDIR. Examples: XDIR JEFF:*.COM ERASE ASM:*.TMP,MYWORK:*.ASM,HELP:*.* MCOPY BACKUP:=WORK1:*.SRC As you can see, ZCPR2 offers quite a difference. Also, anywhere you can use a named directory, you can also use the disk/user form: XDIR B5: For those considering using CHDIR, you may wish to wait until after the ZCPR2 release. Rick 18-Nov-82 14:36:00,363;000000000000 Date: 18 November 1982 16:36-EST From: Eliot Scott Ramey Subject: New Epson files To: CSTROM at Mit-Mc cc: Info-CPM at BRL Via: Mit-Mc; 18 Nov 82 16:34-EST Via: Brl; 18 Nov 82 17:00-EST Via: Brl-Bmd; 18 Nov 82 17:34-EST They may be nicely written utilities, but you didn't mention the important thing: What is it that they do? 18-Nov-82 17:29:00,432;000000000000 Date: 18 November 1982 19:29-EST From: Charlie Strom Subject: New Epson files To: ELIOT at Mit-Mc cc: CSTROM at Mit-Mc, INFO-CPM at BRL Via: Mit-Mc; 18 Nov 82 19:28-EST Via: Brl; 18 Nov 82 19:44-EST Via: Brl-Bmd; 18 Nov 82 19:48-EST Sorry about the omission regarding the new Epson files in AR70:CPM on MC. The program, written in C, initializes the multitude of formatting options on the MX80/100. 18-Nov-82 17:49:00,593;000000000000 Date: 18 Nov 1982 1949-EST Sender: WAGREICH at Bbna Subject: Ibm 3270 tErminal Emulator for Apple II+ From: WAGREICH at Bbna To: Info-MIcro at BRL, Info-CPM at BRL Message-ID: <[BBNA]18-Nov-82 19:49:55.WAGREICH> Via: Bbna; 18 Nov 82 19:45-EST Via: Brl; 18 Nov 82 20:05-EST Via: Brl-Bmd; 18 Nov 82 20:12-EST Does anyone out there know of any IBM 3270 Terminal emulators that can be used with the Apple II+ micro (either with CPM or DOS 3.3 or Apple Pascal operating systems)? I would appreciate any information or leads you may have. Thanks. --Barbara Wagreich 19-Nov-82 02:21:00,425;000000000000 Date: 19 November 1982 04:21-EST From: Robert Elton Maas Subject: pcnet To: INFO-CPM at Mit-Mc cc: BYTE at Mit-Mc Via: Mit-Mc; 19 Nov 82 4:18-EST Via: Brl; 19 Nov 82 4:22-EST Via: Brl-Bmd; 19 Nov 82 4:49-EST Does anybody have software for converting an 8080/z80 assembly language program between CROSS and Microsoft-assembler syntax? (Both directions are needed, although either will be useful.) 19-Nov-82 21:56:00,4572;000000000000 Date: 19 November 1982 23:56-EST From: Paul L Kelley Subject: MODEM792 To: INFO-CPM at BRL cc: W8SDZ at Mit-Mc, PLOUFF at Mit-Mc, STORK at Mit-Mc, ELIOT at Mit-Mc, CSTROM at Mit-Mc, RIZZI at Usc-Isib Via: Mit-Mc; 19 Nov 82 23:59-EST Via: Brl; 20 Nov 82 2:03-EST Via: Brl-Bmd; 20 Nov 82 2:31-EST The following files are now available on MIT-MC in AR61:CPM; MCNFG 792ASM MNUM 792ASM MODEM 768DOC MODEM 792ASM MODEM 792COM MODEM 792HEX MODEM 792HIS MODEM 792INF MODEM 792LIB MODEM 792SET should be available soon. MODEM 768DOC will be updated soon to MODEM 792DOC by one of the authors, Eric Stork. Thanks to Eric, Bill Rizzi, Keith Peterson, and Bob Plouffe for helpful suggestions and comments. The following describes recent changes: ;11/18/81 Combined 11/10/82 and 11/11/82. ; ; Made the following changes: ; ; 1. Added optional routine to overlay file to clear screen ; and home cursor on paging of menu etc., ; 2. Changed printer toggle to terminal mode command and made ; optional with overlay file, ; 3. Changed routines to set MSPEED when changing buad rate with ; SET command, ; 4. Added more information to display of current settings ; and used calls to save space, ; 5. Fixed and shortened bytes free routine, ; 6. Shortened and separated LIB SENDTIME routine into two parts ; so that it can be used in display of current settings, ; 7. Made echo mode part of normal terminal mode to save space ; and make all terminal mode commands available in echo mode, ; 8. Fixed PMMI BYE routine so that it works with overlay file, ; 9. Eliminated F command as redundant, DIR FOO (where FOO is a ; nonexistent file) accomplishes the same thing. ; ;P.L.Kelley ;11/11/82 Made the following changes: ; ; 1. Fixed PMMI dialing routines, ; 2. Added menu command to display current settings ; including bytes remaining in memory buffer, ; 3. Added menu command to change default drive, ; 4. Added menu command for local echo in terminal mode, ; 5. Added menu command to toggle printer on/off, ; 6. Fixed PMMI BYE so warm boots. ; - Irv Hoff ;11/10/82 Combined MODEM771 and MODEM780 (F. Gaude) as follows: ; ; 1. Used erase file function in 780, ; 2. Used 780 code to make display of error count start at 1 ; and changed display to decimal, ; 3. Used 780 idea for throttled output on terminal mode ; transfer of text file to remote but wrote new routines ; including one for user to set speed, ; 4. Moved disk reset to DIR routine as in 780, ; 5. Used 780 code to give kbytes free on DIR command but ; modified to give kbytes free on requested drive instead ; of default drive. ; ; Made the following changes: ; ; 1. Eliminated IMSAI front panel routines, ; 2. Changed so PMMI control-D (disconnect) checks for file ; open on returning to menu mode, ; 3. Fixed file display on bulk transfer so that spaces are ; eliminated and period is inserted if required, ; 4. Changed M(enu) to H(elp) command, ; 5. Added code to allow echo mode to use optional toggling of ; send linefeed after carriage return, ; 6. Added toggling of Checksum/CRC modes on file receive, ; 7. Added optional code to clear to end of screen on next line ; from current cursor position when returning from terminal ; mode, this eliminates jumbled screen when working remote ; which positions cursor. ; ;P.L.Kelley ;11/02/82 Shows the time to send a file. (Routine was placed in ; MODEM791.LIB). Set MSPEED to the speed you normally use. ; Currently set at 300 Baud. Can reset at any time using the ; menu. - Irv Hoff ;10/20/82 Made the following changes: ; ; 1. New 'F' command shows free disk space on default drive ; and resets drive to prevent R/O errors when attempting ; to upload to default disk. ; 2. Requesting DIR also shows free disk space and resets the ; current drive. (From F. Gaude's 780). ; 3. Heading automatically tells if set for PMMI Modem or not. ; (Previously always indicated it was PMMI-only.) ; 4. Grouped all TRUE/FALSE statements together. ; 5. Put 'PMMIBYTE' immediately after ORG 0100H. ; 6. Increased checksum timeout to original value (10 seconds) ; to agree with CRC timeout. This should allow adequate ; time for slow disk systems to write. ; - Irv Hoff 20-Nov-82 00:01:00,866;000000000000 Date: 20 November 1982 02:01-EST From: Herb Lin Subject: diagnostics for new computers, fresh out of box To: info-cpm at BRL, info-micro at BRL Via: Mit-Mc; 20 Nov 82 3:42-EST Via: Brl; 20 Nov 82 3:47-EST Via: Brl-Bmd; 20 Nov 82 4:03-EST can anyone tell me about what i should do in the way of diagnostics when i actually open the box that a new computer comes in? it seems there should be diagnostics that could give the system a workout BEFORE marginal components fail when out-of-warranty. any suggestions for (a) home-programmed tests, (b) diagnostic packages, (c) hardware diddling, (d) anything else? how long should these things be run? also, what is the "recommended" factory burn-in time for components in testing? clearly 200 hours is better than 48, but how much better? i'll post answers to the list. thanks. 20-Nov-82 00:03:00,298;000000000000 Date: 20 November 1982 02:03-EST From: Herb Lin To: info-cpm at BRL Via: Mit-Mc; 20 Nov 82 2:21-EST Via: Brl; 20 Nov 82 2:34-EST Via: Brl-Bmd; 20 Nov 82 2:51-EST can anyone tell me about the graphics facilities of CP/M 3.0, which I think i've heard things about? tnx. 20-Nov-82 00:16:00,281;000000000000 Date: 20 November 1982 02:16-EST From: Paul L Kelley Subject: MODEM 792SET To: INFO-CPM at BRL Via: Mit-Mc; 20 Nov 82 2:22-EST Via: Brl; 20 Nov 82 2:34-EST Via: Brl-Bmd; 20 Nov 82 2:52-EST The file MODEM 729SET is now available in AR61:CPM; on MIT-MC. 20-Nov-82 00:19:00,1570;000000000000 Date: 20 November 1982 02:19-EST From: Herb Lin Subject: GODBOUT/COMPUPRO questions... To: info-micro at BRL, info-cpm at BRL Via: Mit-Mc; 20 Nov 82 2:23-EST Via: Brl; 20 Nov 82 2:34-EST Via: Brl-Bmd; 20 Nov 82 2:55-EST I'm looking for certain information on GODBOUT/COMPUPRO systems... (1) is there error-correcting circuitry available? (or parity checking?) (2) they market an 8086/8087 board, but they claim that the 8086 is restricted to running at 5 MHz "with the 8087", vs. a 10 MHz speed without it. (a) how come? (b) does this mean that the simple existence of the 8087 inhibits 10 Mhz operation, regardless of whether the 8087 is actually in use, or can the 8086 run in 10 Mhz mode while the 8087 is either not in use or somewho disabled? can it be disabled at all? (3) can the 8087 be accessed while running 8 bit software? For example, if I had a fortran program wanting to do number crunchingwhich was running on another card (e.g., their CPU Z card), could I get at the 8087? Or is the 8087 a 16 bit job? (4) how does the 8087 work anyway? does the cpu see it as an I/O device, or what? (5) can anyone recommend a good hard disk (preferably with an integrated tape back-up) which runs well with Godbout/Compupro controllers? (6) I've seen a few ads specifying particlar all-Godbout/Compupro configurations, but for my needs, none of these are just what I need. Does anyone do custom integration by mail? if so, are they reliable, etc...? I will share all replies... many thanks. 20-Nov-82 00:24:00,211;000000000000 Date: 20 November 1982 02:24-EST From: Herb Lin To: info-cpm at BRL Via: Mit-Mc; 20 Nov 82 2:27-EST Via: Brl; 20 Nov 82 2:35-EST Via: Brl-Bmd; 20 Nov 82 2:56-EST What's BIG BOARD? tnx. 20-Nov-82 07:00:00,819;000000000000 Date: 20 November 1982 09:00-EST From: Charlie Strom Subject: RAMDISK files To: INFO-CPM at BRL Via: Mit-Mc; 20 Nov 82 9:02-EST Via: Brl; 20 Nov 82 9:13-EST Via: Brl-Bmd; 20 Nov 82 9:40-EST I have uploaded the following files to MC: AR71:CPM;RAMDSK ASM RAMDSK DOC PRLMOV ASM These files are from Mike Karas' article in Lifelines of a couple of months ago; the programs implement a ram disk by reserving 20K of memory thereby reducing the TPA size. Note that RMAC, LINK, and DISKDEF.LIB (from the CP/M 2.2 distribution disk) are required for assembly. If there are any souls out there brave enough to modify the program to use bank switched/extended addressed memory, please do so! This would be a significant contribution to the public domain CP/M world! 20-Nov-82 08:13:00,738;000000000000 Date: Saturday, 20 November 1982 10:13-EST Sender: X.GYRO.MIT-OZ at BRL From: X.GYRO at Mit-Mc To: Ronald G Fowler cc: info-cpm at BRL Subject: [RGF: CP/M disk logins] In-reply-to: The message of 13 Nov 1982 00:31-EST from Ronald G Fowler Via: Mit-Ml; 20 Nov 82 10:34-EST Via: Brl; 20 Nov 82 10:44-EST Via: Brl-Bmd; 20 Nov 82 11:03-EST Date: 13 November 1982 00:27-EST From: Ronald G. Fowler Re: CP/M disk logins In fact, once accessed, a disk is considered logged until the next warm-boot, even if it has changed. --Ron Not strictly true. There is a "Reset disk subsystem" BDOS call that will un-log all disks without warm booting. -- Scott 20-Nov-82 08:30:00,1271;000000000000 Date: 20 Nov 1982 0730-PST Sender: BILLW at Sri-Kl Subject: Re: GODBOUT/COMPUPRO questions... From: BILLW at Sri-Kl To: LIN at Mit-Mc Cc: info-micro at BRL, info-cpm at BRL Message-ID: <[SRI-KL]20-Nov-82 07:30:52.BILLW> In-Reply-To: Your message of 20 November 1982 02:19-EST Via: Sri-Kl; 20 Nov 82 10:59-EST Via: Brl; 20 Nov 82 10:59-EST Via: Brl-Bmd; 20 Nov 82 11:18-EST The 8087 is a co-processor. When the 8086 want to do floating point operations, it uses the various ESC opcodes. The 8087 reads this from the bus, and by watching the status lines of the 8086, is able to determine when tey are executed. It then can read an operand from the bus (which the 8086 fetches and discards durring the ESC operation). I dont know wgether the 8087 can also control the bus itself, but I assume it must (otherwise it would take several ESC instructions to load a full floating point number...) All this means that there is little chance of getting at the 8087 from another processor. Presumably, the 8087 will only run at 5MHz because is is not as far along the learning curve as the 8086. The first 8086s were 5Mhz too. Due to the above outlined tight coupling between the 86 and 87, they must both run at the same clock speed. BillW 20-Nov-82 12:51:00,718;000000000000 Date: 20 November 1982 14:51-EST From: Charlie Strom Subject: Poor Peoples' Speller To: info-cpm at BRL Via: Mit-Mc; 20 Nov 82 15:02-EST Via: Brl; 20 Nov 82 15:12-EST Via: Brl-Bmd; 20 Nov 82 15:25-EST I have uploaded the Poor Peoples' Speller, a spelling program originally appearing in Dr. Dobbs and subsequently converted to CP/M operation (in Z80 code) to MC: AR72:CPM;SPELL 11ASM SPELL 11COM SPELL 11DOC SPELED 3COM SPELED DOC The former three files comprise the speller proper; the latter two are a recent addition allowing marking of the misspelled words in the text file for later correction, addition of correct words to the dictionary (LEX) file, etc. 20-Nov-82 20:17:00,600;000000000000 Date: 20 Nov 1982 1917-PST Sender: TBOWERMAN at Office-10 Subject: Re: Poor Peoples' Speller From: TBOWERMAN at Office-10 To: CSTROM at Mit-Mc Cc: info-cpm at BRL Message-ID: <[OFFICE-10]20-Nov-82 19:17:10.TBOWERMAN> In-Reply-To: Your message of 20 November 1982 14:51-EST Via: Office-10; 20 Nov 82 22:23-EST Via: Brl; 20 Nov 82 22:26-EST Via: Brl-Bmd; 20 Nov 82 22:53-EST Excellent job, Charlie. I had it downloaded and working in less than an hour, counting the time it took to read your message. My first spell program that works, and it does a good job. Thanks much. Tom 20-Nov-82 23:47:00,1063;000000000000 Date: 21 November 1982 01:47-EST From: Greg Heise To: INFO-CPM at Mit-Mc Via: Mit-Mc; 21 Nov 82 2:04-EST Via: Brl; 21 Nov 82 2:04-EST Via: Brl-Bmd; 21 Nov 82 2:14-EST Has anyone had any experience with the LU program set with libraries over 256k? It seems to be fouling up somehow on the directory: some directory programs report a file length as (true length) mod 256K. I've modified the filefind program so it searches ALL 4 or 16 drives of a cp/m system rather than ending at the first non-existent drive --who should this be reported to? I feel that dirty linen like the recent message set between PLATT and BANDY ought not to be aired; I'm not taking sides -- I just feel that I have better things to do then listen to this nonsense. If you object to someone's behavior, say so *privately*, or ignore it. The only saving grace of twits is that they *eventually* go away if you ignore them. If you just can't take it, then remove the name from the list or take some other pointed action. End of flame. --Greg 21-Nov-82 00:28:00,440;000000000000 Date: Sunday, 21 November 1982 02:28-EST Sender: RG.JMTURN.MIT-OZ at BRL From: RG.JMTURN at Mit-Mc To: info-cpm at BRL Via: Mit-Mc; 21 Nov 82 2:50-EST Via: Brl; 21 Nov 82 2:57-EST Via: Brl-Bmd; 21 Nov 82 3:14-EST Someone on CompuServe claims that someone on INFO-MICRO claimed that the Morrow MicroDecision wouldn't talk to certain terminals. Is this so, and can the Z19 talk to it? Also, add me tto INFO-CPM. James 21-Nov-82 02:00:30,1221;000000000000 Date: 21-Nov-82 01:00:30-PST (Sun) From: UCBARPA.dag at Ucb-C70 (David Allen Gewirtz) Subject: GODBOUT/COMPUPRO questions... Message-Id: <8210210900.11883@UCBARPA.BERKELEY.ARPA> Received: by UCBARPA.BERKELEY.ARPA (3.224 [10/16/82]) id A11882; 21-Nov-82 01:00:31-PST (Sun) Received: from UCBARPA.BERKELEY.ARPA by UCBVAX.BERKELEY.ARPA (3.227 [10/22/82]) id A19732; 21-Nov-82 00:57:14-PST (Sun) To: LIN at Mit-Mc, info-cpm at BRL, info-micro at BRL Via: Ucb-C70; 21 Nov 82 4:03-EST Via: Brl; 21 Nov 82 4:12-EST Via: Brl-Bmd; 21 Nov 82 4:26-EST As far as I can tell, G & G Engineering is the best Godbout integration house around. They seem to know there stuff when it comes to system integration. Since they have Compupros stamp of approval for integration work, it seems that they may be what you want. I spoke with them once and was impressed by their knowledge. (however, they have grown considerably in the half year since then). For your information they are in San Leandro and San Francisco CA, in the 415 area. I believe that their ads are in a number of the trade mags. I also believe they will do stuff by mail. Be forwarned however, they are not cheap. Good Luck, David 21-Nov-82 02:42:00,504;000000000000 Date: 21 November 1982 04:42-EST From: "James Lewis Bean, Jr." Subject: Large Files To: INFO-CPM at Mit-Mc Via: Mit-Mc; 21 Nov 82 5:19-EST Via: Brl; 21 Nov 82 5:30-EST Via: Brl-Bmd; 21 Nov 82 5:45-EST Mabey files loaded to the CPM directory should be squeezed before sending them to MC. Doing this would increase the speed of transfers to and from the machine as well as decreasing the ammount of disk space taken up by these files. lewis bean at mit-mc 21-Nov-82 08:14:00,1132;000000000000 Date: 21 Nov 1982 0714-PST Sender: BILLW at Sri-Kl Subject: Re: Large Files From: BILLW at Sri-Kl To: BEAN at Mit-Mc Cc: INFO-CPM at Mit-Mc Message-ID: <[SRI-KL]21-Nov-82 07:14:32.BILLW> In-Reply-To: Your message of 21 November 1982 04:42-EST Via: Mit-Mc; 21 Nov 82 10:21-EST Via: Brl; 21 Nov 82 10:23-EST Via: Brl-Bmd; 21 Nov 82 10:30-EST Files in CPM; should be compressed. Please dont. Some of us like to look at the program/whatever BEFORE we download it, if it ever gets downloaded at all. I frequently run a program from CPM though a translation process and assemble using a cross assembler... It is particurally annoying, for example, that the documentation for SYSLIB, which is applicable to more than just CPM systems, is essentially unusable without a rather specific cpm environment. (Not that Im complaining - beggars can't be choosy!). The ideal solution would be to write versions of SQUEZE/UNSQUEZE for various large computers (it might even be useful in its own right!). For example, does anyone have it running under UNIX (this should be relatively easy...). Bill Westfield 21-Nov-82 10:35:00,1011;000000000000 Date: 21 November 1982 12:35-EST From: Frank J Wancho Subject: Mainframe CP/M Utilities To: INFO-CPM at BRL Via: Mit-Mc; 21 Nov 82 13:05-EST Via: Brl; 21 Nov 82 13:12-EST Via: Brl-Bmd; 21 Nov 82 13:20-EST For those of you who may not be aware, other than various varieties of MODEM, we have several other utilities available for the CP/M hacker for use on certain mainframes: Ian Mackey's CRC - the ITS and TOPS-20 equivalent of Keith Petersen's CRCK. Contact GREN@MC for availability of the sources, written in MIDAS. Gail Zacharias' COMIFY and HEXIFY, which convert HEX files to COM files, and vice-versa. Contact GZ@MC. Sources are also in MIDAS as I recall - for ITS... As the space availability on MC:CPM; dwindles, and as Bill Westfield points out, utilities such as mainframe versions of SQ, USQ, and TSQ would certainly be welcome additions to the mainframe world in their own right. And UNIX machines do not hold a monopoly on C compilers... --Frank 21-Nov-82 10:38:00,1227;000000000000 Date: 21 Nov 1982 at 1138-CST From: mknox at Utexas-11 Subject: squeezing MC CPM files To: info-cpm at BRL Via: Utexas-11; 21 Nov 82 13:32-EST Via: Brl; 21 Nov 82 13:42-EST Via: Brl-Bmd; 21 Nov 82 14:06-EST Another vote for NOT squeezing files on MC;CPM...AT THIS TIME. Reason against: It has the unfortunate feature of turning text files into binary files, which a still large number of us are not set up to handle. It is already a problem with the .COM files on MC;CPM. Many of them need to be .COMs, because of space requirements; but then the .HEX unloaded version is needed too, taking up even more space due to the duplication. Not to mention needing some kind sole to unload the files each time. Possible solution: A mechanism for performing the UNLOAD function on the MIT machine. This would allow the transfer of binary files, both .COM and .xSx types, by anyone; in the more efficient binary form if the user had the capability, as clear text if not. An alternate sol- ution would of course involve UNLOAD programs for the remote sites, with the advantage of improved ARPANET transmission times, but would then require a large and diverse number of such programs. ------- 21-Nov-82 12:13:00,1264;000000000000 Date: 21 Nov 1982 1113-PST From: Dick Subject: Re: Large Files To: BEAN at Mit-Mc cc: info-cpm at BRL In-Reply-To: Your message of 21-Nov-82 0142-PST Via: Usc-Eclb; 21 Nov 82 15:11-EST Via: Brl; 21 Nov 82 15:12-EST Via: Brl-Bmd; 21 Nov 82 15:33-EST Mail-from: ARPANET site USC-ECL rcvd at 21-Nov-82 0335-PST Mail-from: ARPANET site BRL rcvd at 21-Nov-82 0331-PST Date: 21 November 1982 04:42-EST From: "James Lewis Bean, Jr." Subject: Large Files To: INFO-CPM at Mit-Mc Via: Mit-Mc; 21 Nov 82 5:19-EST Via: Brl; 21 Nov 82 5:30-EST Via: Brl-Bmd; 21 Nov 82 5:45-EST Mabey files loaded to the CPM directory should be squeezed before sending them to MC. Doing this would increase the speed of transfers to and from the machine as well as decreasing the ammount of disk space taken up by these files. lewis bean at mit-mc It is a nice idea. But, unfortunately, I, and perhaps many others, would not be able to transfer squeezed files. I am only able to grab text files intact, and need non-text files Hexed, which, of course, takes up time and room. However, as long as there are helpful people who don't mind requests to hexify some files, I won't mind too much. ------- 21-Nov-82 12:29:32,745;000000000000 Date: 21 Nov 82 14:29:32-EST (Sun) From: Keith Petersen To: Info-Cpm at BRL Subject: CP/M 2.2 for TRS-80 model II Via: Brl; 21 Nov 82 14:30-EST Via: Brl-Bmd; 21 Nov 82 14:57-EST A friend is considering buying a Model II system but wants to run CP/M instead of TRSDOS. I am aware of Pickles & Trout's CP/M for that machine, but there are some things I don't like about their implementation (such as not providing source for the CBIOS, putting serial number checks into several of their utilities which makes it almost impossible to use ZCPR because it has no serial number, etc). Is there another source for CP/M 2.2 for that machine? Alternately has anyone solved the problems I mentioned above? 21-Nov-82 13:09:13,721;000000000000 Date: 21-Nov-82 12:09:13-PST (Sun) From: csuf!csuf!bytebug at Ucb-C70 Subject: Re: CP/M disk logins Message-Id: <8210212009.2414@UCBVAX.BERKELEY.ARPA> Received: by UCBVAX.BERKELEY.ARPA (3.227 [10/22/82]) id A02395; 21-Nov-82 12:09:21-PST (Sun) To: ucivax!ucbvax!info-cpm at BRL Cc: ucivax!ucbvax!goldfarb.ucf-cs at Udel-Relay, ucivax!ucbvax!mknox at Utexas-11 Via: Ucb-C70; 21 Nov 82 15:24-EST Via: Brl; 21 Nov 82 15:29-EST Via: Brl-Bmd; 21 Nov 82 15:46-EST The new CP/M 2.2 documentation defines the SELDSK routine, adding the following statement: "The least significant bit of register E is zero if this is the first occurrence of the drive select since the last cold or warm start." 21-Nov-82 15:44:00,3269;000000000000 Date: 21 November 1982 17:44-EST From: Frank J Wancho Subject: Large Files To: Mead at Usc-Eclb cc: INFO-CPM at BRL Via: Mit-Mc; 21 Nov 82 17:46-EST Via: Brl; 21 Nov 82 17:44-EST Via: Brl-Bmd; 21 Nov 82 18:07-EST As I mentioned in my previous message, there are several mainframe implementations of MODEM, and there are two working versions that run on TOPS-20 machines: Bill Westfield's MODEM and Max Diaz' XMODEM. Sources to both are kept in MC:AR60:. MODEM works on TOPS-20 only and also works through an ARPANET connection using a TIP or TAC, NCP or TCP. XMODEM works on TOPS-20 direct only, and on TENEX either direct or through an ARPANET connection using a TIP or TAC, NCP or TCP. Downloading using either program works at any speed. Uploading works at any speed in direct mode, and through a TIP up to 1200. TACs have an inherent design flaw (a fixed-size 64-byte input buffer) which prevents or severely inhibits uploading at speeds greater than 300. Both uploading and downloading using either program properly handle both text and binary files, including those binary files uploaded to MC via LMODEM which contain a special header word as the first word of the file to indicate that it is a binary file since ITS sites do not have FDBs to indicate file type. Thus, you should no longer need files in HEX or text-only form unless you cannot FTP from MC. Note to UNIX sites: UMODEM is available and does work with both text and binary files in your environment. The trick is to get FTP to transfer the binary files correctly...someone else can tell us how they do that. Further comment on SQueezed vs text vs binary files: binary files are stored as 4 bytes per PDP-10 36-bit word; text files are stored as 5 bytes per PDP-10 word. Storing a text file as a binary file takes up 25% more disk space. Squeezing that file first yields a typical 40% reduction and takes up 15% less disk space. That 15% helps, but that alone is not quite enough justification - converting several files to Library format is. The reason: each file takes up directory entry space, limiting the combined total amount of space for both the files themselves and the directory entry space. By packing several related files into Library format, already a binary file at that point, and then SQueezing the resulting file, we can make *much* more space available for the many files which should have been uploaded by now and haven't, due to that space crunch. I can appreciate Bill Westfield's desire to leave text files alone so that he can manipulate them online, but that is a luxury we can no longer afford. The principal intent of a CPM directory on MC is to have a repository for public domain files of interest to the CP/M community which they can, in turn, download to their micros by whatever means available to them. At first, uploading and downloading was limited to those who had access to MC. Since then, programs like Bill's own MODEM have sprung up to provide similar capabilities to other mainframes. I suspect that it won't be too long before someone converts SQ, USQ, TYPESQ, and LU to mainframe versions of those utilities we have found so handy on our micros... --Frank 21-Nov-82 16:05:00,2397;000000000000 Date: 21 Nov 1982 at 1705-CST From: mknox at Utexas-11 Subject: Model-II To: info-cpm at BRL Via: Utexas-11; 21 Nov 82 18:32-EST Via: Brl; 21 Nov 82 18:42-EST Via: Brl-Bmd; 21 Nov 82 19:07-EST There are a number of CP/M implementations for the Model-II. Briefly, (and in my own humble opinion): o P&T -- I agree with your complaints, but feel that theirs is the best overall product for the price. The provide very good documentation (a rare bird indeed). They support a variety of disk drives, both hard and soft. They provide a good supply of useful, well written utilities. And they provide good customer support (except for certain policies like not providing source). Only one other complaint; the double density disk format they chose is a little strange, 16 sectors of 512 bytes (most use 15 x 512). This does provide more storage than others, but is very hard to read on other machines. o Lifeboat -- The other current major supplier. Not as good an implementation as P&T, and with the usual Lifeboat support (one customer I know of is still waiting for an answer to his question after 2 years!). Does support 8 x 1k disk sectors. o CPU SHOP and FMG -- sold a lot of copies early on, but have mostly faded away, at least as a CP/M Model-II supplier. More expensive. o ATON -- one of the best jobs of fully utilizing the Model-II hardware that I have seen. Only a little more expensive. Fair documentations, actually quite good for a hacker, not near as good as P&T if you are a business turnkey type. The ATON version(s) support disk caching through extra memory cards, and also concurrent operations using multiple banked memory cards. I have no direct experience running the system (called JOBSTREAM), but careful review of the manuals makes it look like it was done by a hacker who knows his way around a system. ATON has only had it out a few months. Conclusion: I'd still go with the P&T. Most products now support it (Word- star, dBASE, etc.), where some of the other implementations may require some effort to install application packages. [Side note: the P&T makes full use of the CRT capabilities, much better than Lifeboat] I am recommending P&T to those who ask me; and using it as a base for a Model-16 or Model-II Enhanced CP/M-68K implementation. ------- 21-Nov-82 18:12:00,508;000000000000 Date: 21 November 1982 20:12-EST From: Keith Petersen Subject: squeezing MC CPM files To: mknox at Utexas-11 cc: Info-Cpm at BRL Via: Mit-Mc; 21 Nov 82 21:01-EST Via: Brl; 21 Nov 82 21:12-EST Via: Brl-Bmd; 21 Nov 82 21:27-EST We have a HEXIFY utility on MIT-MC, thanks to Gail . Anyone who needs a .COM file turned into a .HEX file may do so on MC if they have an account there, or alternatively have Frank or myself make one (send requests to Info-Cpm-Request@Brl). 21-Nov-82 21:16:00,662;000000000000 Date: 21 November 1982 23:16-EST From: Leor Zolman Subject: clearing externals with BDS C v1.5 To: info-cpm at BRL Via: Mit-Mc; 21 Nov 82 23:17-EST Via: Brl; 21 Nov 82 23:24-EST Via: Brl-Bmd; 21 Nov 82 23:34-EST The actual release version of v1.5 (which still hasn't been finalized) will have a new CLINK option which inhibits the clearing of external data, like Dave Gewirtz's NOCLEAR program does. I'll probably be sending a "final" v1.50 to the User's Group for general distribution this week. The new User's Guide is 200 pages long, all run off on my Diablo and much more coherent than the previous patchwork guide... -leor 21-Nov-82 21:50:00,362;000000000000 Date: 21 November 1982 23:50-EST From: Herb Lin Subject: LOGO on CP/M? To: info-cpm at BRL Via: Mit-Mc; 22 Nov 82 0:20-EST Via: Brl; 22 Nov 82 0:28-EST Via: Brl-Bmd; 22 Nov 82 0:36-EST DOes anyone know if such a beast is or will be likely to happen? (Yes, I know CPM doesn't usually support graphics, but I hear that CP/M 3.0 will.) 21-Nov-82 21:57:00,727;000000000000 Date: 21 November 1982 23:57-EST From: Herb Lin Subject: [RMS.G.BANDY: diagnostics for new computers, fresh out of box] To: info-cpm at BRL, info-mirco at BRL Via: Mit-Mc; 22 Nov 82 0:21-EST Via: Brl; 22 Nov 82 0:28-EST Via: Brl-Bmd; 22 Nov 82 0:37-EST Date: 20 Nov 1982 0755-EST From: Andrew Scott Beals To: LIN Re: diagnostics for new computers, fresh out of box well, memory tests. disk read/write tests. i had a simple little program written in mbasic that would fill up the disk, kill the file it just filled up the disk with, then do it again - i used this to test my osborne when i originally got it. the best way to test a computer is through hard use. 21-Nov-82 21:58:00,1628;000000000000 Date: 21 November 1982 23:58-EST From: Herb Lin Subject: [CSTROM: diagnostics for new computers, fresh out of box] To: info-cpm at BRL, info-micro at BRL Via: Mit-Mc; 22 Nov 82 0:21-EST Via: Brl; 22 Nov 82 0:28-EST Via: Brl-Bmd; 22 Nov 82 0:38-EST Date: 20 November 1982 08:31-EST From: Charlie Strom To: LIN Re: diagnostics for new computers, fresh out of box Sudden infant mortality is surely a very common occurrence in the microcomputer field. Memoery tests are very useful; the best I have seen is called the Rasmussen Memory test (MEMR2) from Lifeboat and is most likely available from them for a modest fee. There are also a plethora of public domain memory tests available in the public domain and they are generally useful for "hard" errors only; I have seen several instances of bad memory where the mory tests insist that all is well. Those that exercise the memory at full speed are the best. Look at one called WORM and another called UMPIRE (both in the public domain.) I did just have ocassion to repair a CCS 16K static board on which a 2114 went bad after about 18 months of almost daily use. This is the exception. The best way to burn in the system is to use it in normal operation intensively for a while. I find that the real life conditions will show up any faults much more effectively than the so-called test programs. If your machine runs WordStar for example, chances are that there are no problems. I will leave comments re disk drives and other components to others who are more knowledgeable about them. Regards, Charlie 22-Nov-82 04:37:40,663;000000000000 From: TENNEY at Mit-Ai Date: 11/22/82 04:37:40 Subject: Large files + SQ Via: Mit-Mc; 22 Nov 82 4:38-EST Via: Brl; 22 Nov 82 4:53-EST Via: Brl-Bmd; 22 Nov 82 5:06-EST TENNEY@MIT-AI 11/22/82 04:37:40 Re: Large files + SQ To: info-cpm at MIT-MC Really, the ideal would be: The files are kept SQ'ed; there was a TYPESQ equiv.; MODEMxxx would hexify on the fly if needed. Result: everyone benefits! If TYPESQ were difficult, then keep files UNSQ'ed and let MODEMxxx SQ them on the fly (a bit much, but...). I do think that MODEMxxx should have the hexify option built-in for those of you that can't use 8-bit. Well, enuf for dreaming. Glenn 22-Nov-82 10:01:55,381;000000000000 Date: 22 Nov 1982 10:01:55 CST (Monday) From: Mike Meyer Subject: Your Bios To: pourne at Mit-Mc Cc: info-cpm at BRL, mwm at Okc-Unix Via: Okc-Unix; 22 Nov 82 11:11-EST Via: Brl; 22 Nov 82 11:24-EST Via: Brl-Bmd; 22 Nov 82 11:36-EST What are the chances of us non-godbout people getting to look at the insides of the BIOS you are running? Subject: no graphics on CP/M 3.0 To: lbl-unix!INFO-CPM at BRL Via: Lbl-Unix; 22 Nov 82 19:56-EST Via: Brl; 22 Nov 82 20:04-EST Via: Brl-Bmd; 22 Nov 82 22:40-EST I'd sure like to know where these rumors about "graphics support" under 3.0 are coming from! In all of my discussions with persons about 3.0, and in all of the literature I've seen on the subject, there has been no mention of any kind of graphics. I can't even see how such a thing would be implemented... What KIND of graphics? For what kind of graphics devices? Barring convincing evidence to the contrary, I would brand these rumors as hogwash. In fact, everything I've learned so far about 3.0 leads me to expect it will be about as exciting as a new assembler for the IBM 360. Digital Research seems to have no interest in supporting 3.0 for other than large OEM's with turnkey-type systems. The "advances" of 3.0 all sound pretty dubious, and I understand that the documentation isn't even up to D.R.'s usual low standards. Given that D.R. plans to continue to "support" 2.2, it appears that 3.0 is an attempt to squeeze some bucks out of the "higher-end" Z80 machines currently on the market. I'm not against new software for 8080/Z80's, but I view 3.0 with a considerable lack of interest. --Lauren-- 22-Nov-82 22:33:19,418;000000000000 Date: 22 Nov 82 22:33:19 EST (Mon) From: Ben Goldfarb Subject: Re: Your Bios To: pourne at Mit-Mc Cc: mwm at Okc-Unix, info-cpm at BRL Via: UCF-CS; 23 Nov 82 1:30-EST Via: Udel-Relay; 23 Nov 82 1:53-EST Via: Brl; 23 Nov 82 1:59-EST Via: Brl-Bmd; 23 Nov 82 2:17-EST If there is a chance that you will let us in on your BIOS, I'd like to see it, too. 23-Nov-82 02:06:04,1143;000000000000 Date: 23-Nov-82 01:06:04-PST (Tue) From: UCBARPA.dag at Ucb-C70 (David Allen Gewirtz) Subject: micro decision Message-Id: <8210230906.10356@UCBARPA.BERKELEY.ARPA> Received: by UCBARPA.BERKELEY.ARPA (3.224 [10/16/82]) id A10355; 23-Nov-82 01:06:06-PST (Tue) Received: from UCBARPA.BERKELEY.ARPA by UCBVAX.BERKELEY.ARPA (3.227 [10/22/82]) id A17243; 23-Nov-82 08:29:23-PST (Tue) To: RG.JMTURN.MIT-OZ at BRL, info-cpm at BRL Via: Ucb-C70; 23 Nov 82 15:20-EST Via: Brl; 23 Nov 82 15:43-EST Via: Brl-Bmd; 23 Nov 82 16:30-EST I think I know what they are refering to. Morrow uses his own terminal (an adm-20) with the micro decision. It tends to act like an adm31 with the absolute cursor addressing reversed. The adm-31 does an ESC = Y X to goto a position, while morrows terminal does an ESC = X Y. Morrow therefore has put a hack in the bios that checks for ESC followed by '='. It then intercepts the next two characters and reverses them. I suspect that this is the protential incompatibility problem. Worst case solution for the h19 is re-hacking the BIOS supplied with the micro-decision. David 23-Nov-82 02:10:03,638;000000000000 Date: 23-Nov-82 01:10:03-PST (Tue) From: UCBARPA.dag at Ucb-C70 (David Allen Gewirtz) Subject: CP/M 2.2 for TRS-80 model II Message-Id: <8210230910.10382@UCBARPA.BERKELEY.ARPA> Received: by UCBARPA.BERKELEY.ARPA (3.224 [10/16/82]) id A10380; 23-Nov-82 01:10:05-PST (Tue) Received: from UCBARPA.BERKELEY.ARPA by UCBVAX.BERKELEY.ARPA (3.227 [10/22/82]) id A16655; 23-Nov-82 08:11:10-PST (Tue) To: Info-Cpm at BRL, w8sdz at BRL Via: Ucb-C70; 23 Nov 82 11:27-EST Via: Brl; 23 Nov 82 11:40-EST Via: Brl-Bmd; 23 Nov 82 11:52-EST I believe omicron has a CP/M for the TRS-80 II. I know no more about it than that. David 23-Nov-82 04:22:00,1192;000000000000 Date: 23 November 1982 06:22-EST From: Charlie Strom Subject: no graphics on CP/M 3.0 To: vortex!lauren at Lbl-Unix cc: INFO-CPM at BRL Via: Mit-Mc; 23 Nov 82 6:54-EST Via: Brl; 23 Nov 82 7:00-EST Via: Brl-Bmd; 23 Nov 82 7:07-EST The "graphics support" everyone seems to be taking for granted consists of a couple of BIOS calls to do cursor addressing, clear screen and the like, according to what I have been told. It would make applications programming a little easier, but I strongly suspect that most developers of CP/M software will elect to stay 2.2 compatible. I see 3.0 as a hacker's joy and wonder if it will make much of a dent in the 2.2 installed user base. Running with bank switched memory and deblocking in the BDOS rather than the BIOS, time stamping of files, and the like seem to be the main attractions of 3.0. My understanding is that the current version still has a couple of bugs. D.R. in their infinite(?) wisdom elected not to make 3.0 available to individuals (probably because the doc is up to usual standards of illegibility); I intend to get it as soon as possible, but no way do I see throwing out 2.2. Charlie 23-Nov-82 05:39:31,1075;000000000000 Date: 23 Nov 82 7:39:31-EST (Tue) From: Rick Conn To: info-cpm at BRL, info-micro at BRL Subject: [Sol Libes: SYSLIB, Copying Files, the ACG-NJ, and SIG/M] Via: Brl; 23 Nov 82 7:49-EST Via: Brl-Bmd; 23 Nov 82 7:52-EST Sol has some good info to add to my message re SIG/M and the ACG-NJ. Thought you would like to see it. Rick ----- Forwarded message # 1: Date: 22 November 1982 22:47-EST From: Sol Libes Subject: SYSLIB, Copying Files, the ACG-NJ, and SIG/M To: rconn at BRL cc: SLIBES at MIT-MC, Bomberger at OFFICE-2 Via: Mit-Mc; 22 Nov 82 23:48-EST Dear Rick: Thanks for the plug for SIG/M and ACG-NJ. I wish to just correct you on one thing. One does not have to be a member of ACG-NJ to order or copy SIG/M disks. This service is offered to both members and non-members at no extra charge. Also, SIG/M has now released 85 volumes. A copy of our printed catalog is $1 or $1.50 via mail. It can be ordered from: SIG/M, Box 97, Iselin NJ 08830. ----- End of forwarded messages 23-Nov-82 05:59:00,870;000000000000 Date: 23 November 1982 07:59-EST From: bbtp at Mit-Ml Sender: ___014 at Mit-Ml Subject: microsoft's wimpy copy protection in the Osobrne distributed version of bascom To: info-cpm at BRL cc: decvax!microsof!root at Ucb-C70, decvax!microsof!gordonl at Ucb-C70 Via: Mit-Ml; 23 Nov 82 8:17-EST Via: Brl; 23 Nov 82 8:34-EST Via: Brl-Bmd; 23 Nov 82 8:58-EST early on in the initialization code, this is some osborne dependant code to swap in a set of roms (from 000 to 1ff) and then procede to try to write to them...if it fails, the sucker just warm boots, and if it doesn't, then you're ok. here's the patch so anyone can use it: location 4436h is the starting location of the `anti piracy' code. just insert JMP 4457 with DDT (then `save 128 bascom.com' will give you a copy of bascom that will work on anything! Black Beard, The Pirate 23-Nov-82 20:51:00,1495;000000000000 Date: 23 Nov 1982 2251-EST From: Tony Subject: CP/M 3.0 and graphics To: info-cpm at BRL Via: Rutgers; 24 Nov 82 2:54-EST Via: Brl; 24 Nov 82 9:10-EST Via: Brl-Bmd; 24 Nov 82 10:25-EST Let me put some rumors to rest. (* Disclaimer *) I am a former DR employee, and possibly a future employee. I was a summer-intern in the graphics group. My total time spent hacking CP/M totals only about 3 months. For one of those, I was priviledged enough to be a beta-test for CP/M 3.0. The following information should not be taken as an ad for DR or as any statement of the functions of future DR products. (* End Disclaimer *) 1) Graphics: The new graphics package that DR will come out with will (at last report) be 2.2 compatible. I am not a liberty to discuss the details of implementation, but I can say that there is more to it then Mr. Weinstein suggests. The new graphics subroutine package will support some form of the new GKS graphics standard, level 1B. Again, at last report, it will be accessible from Pl/I, Fortran, and Pascal. CB-80 is also a possibility. I will divulge further info on this as soon as the product hits the market. 2) CP/M 3.0: Again, I was using an early beta test version, but I do think that CP/M 3.0 is a significant upgrade over 2.2 FOR SOME SYSTEMS. In particular, if you are privileged enough to have banked memory, or a hard disk, you might be interested. Tony Li [Li @ Rutgers] ;-) ------- 23-Nov-82 21:59:00,2000;000000000000 Date: 23 November 1982 23:59-EST From: Roger L Long Subject: WordStar and the IDS 480 (Micro Prism) To: info-cpm at BRL, info-micro at BRL Via: Mit-Mc; 24 Nov 82 0:19-EST Via: Brl; 24 Nov 82 8:50-EST Via: Brl-Bmd; 24 Nov 82 10:20-EST I've recently been trying to configure WordStar for an IDS 480 printer. As long as I only tell WordStar that it's a dumb tty-like printer, things work pretty well. But not satisfied with leaving well enough alone, I've been trying to configure it so that it makes use of the proportional spaceing features. Here's where I get into trouble. First of all, the escape sequences on the 480 are NOT binary. For instance, the sequence to space over 15/120ths of an inch would be: <,><1><5><,><$> In other words, for each character you write on the paper, you end up sending eight. Not quite... make that nine, because the printer has already spaced past the character it just printed, so you have to send a backspace, and then the foobar sequence above. As you might expect, WordStar driving the IDS in this mode ends up printing slower than a teletype. The second half of the problem is the prism's automatic proportional spacing and justification mode. In order for this to work, you send the printer a stream of text without carriage returns, and the printer decides how and where to split it into lines. When you finally send a carriage return, that ends the paragraph. Try to tell WordStar how to do that! Does anyone have any bright ideas? Another thought might be to redo the internal printer firmware, so that it accepted the QUME or DIABLO escape sequences. Does anyone know what processor lies in the inards of this beast? Also what type of prom for the firmware, and also what kind of prom/character generator for the fonts? (Obviously I haven't taken this one apart yet, since it isn't mine, and I'm not that desparate... yet...) Thanks in advance for any info. -roger 23-Nov-82 22:57:08,729;000000000000 Date: 23 Nov 82 22:57:08 EST (Tue) From: Ben Goldfarb Subject: Poly 88 / N* problem To: info-cpm at BRL Via: UCF-CS; 24 Nov 82 4:54-EST Via: Udel-Relay; 24 Nov 82 20:03-EST Via: Brl; 24 Nov 82 20:12-EST Via: Brl-Bmd; 24 Nov 82 20:25-EST This may be old stuff to some of you, but I thought I'd post it anyway since it could save considerable time if you don't know about it. Two people here spent a lot of time trying to get the old N* single density disk controller to work with the Polymorphic 8813 CPU with frustrating results. The problem is that the clock interrupt on the CPU card must be disabled for the N* controller to work properly. Ben Goldfarb 24-Nov-82 01:53:00,1814;000000000000 Date: 24 November 1982 03:53-EST From: Frank J Wancho Subject: [PLEHN: forwarded] To: INFO-CPM at BRL Via: Mit-Mc; 24 Nov 82 4:29-EST Via: Brl; 24 Nov 82 9:20-EST Via: Brl-Bmd; 24 Nov 82 10:27-EST Although other high level languages are to be encouraged, Al makes a fair case below for a BASIC software collection. If anyone has authored, or knows of public domain software that can be contributed, please submit your files via mail to INFO-CPM-REQUEST@BRL or FTP them to either MC:FJW; or MC:W8SDZ; with a follow-up message to the same address. As long a space permits, we will move the file(s) to MC:AR30: and let you know. You can then send your own message to the list briefly describing the program. No games, please. --Frank -------------------- Date: 11/22/82 00:20:58 From: PLEHN Do you know of any on-line depository of programs in MBASIC (or other BASICs)? Nobody seems to admit to using BASIC but I find it very useful and, when compiled, fast. I know that lots of good scientific type BASIC programs exist but I would like to avoid typing the source. For example: statistics, navigation, path profiles & propagation loss etc. etc. I don't see much interest in BASIC on the part of the INFO-CPM correspondants. Maybe you know of another host that has a BASIC interest group?? There are lots of programs available for Northstar BASIC thru the user groups but I have found that the programs have bugs or limitations. They are often the contributions of gross amateurs who assume particular system configurations, like POKEs to N* DOS (at an assumed location). A network depository of BASIC programs is, I feel, likely to have well written and reliable programs with continuous user refinement. Know of any such network resource?? Al 24-Nov-82 03:26:15,720;000000000000 Date: 24 Nov 82 03:26:15 EST (Wed) From: Ben Goldfarb Subject: Re: microsoft's wimpy copy protection in the Osobrne distributed version of bascom To: bbtp at Mit-Ml, info-cpm at BRL Cc: decvax!microsof!root at Ucb-C70, decvax!microsof!gordonl at Ucb-C70 Via: UCF-CS; 24 Nov 82 5:00-EST Via: Udel-Relay; 24 Nov 82 20:05-EST Via: Brl; 24 Nov 82 20:19-EST Via: Brl-Bmd; 24 Nov 82 20:27-EST I'd rather not see this kind of thing coming through info-cpm. But then by drawing attention to it I suppose I am reacting as the anonymous author hopes we will. Speaking of wimpy things, bbtp@Mit-ml, I bet you don't have the guts to tell us your real name. 24-Nov-82 09:41:00,412;000000000000 Date: 24 November 1982 1141-EST (Wednesday) From: Ed.DeHart at Cmu-Cs-A To: info-cpm at BRL Subject: cp/net cp/nos Message-Id: <24Nov82 114117 ED80@CMU-CS-A> Via: Cmu-Cs-A; 24 Nov 82 11:56-EST Via: Brl; 24 Nov 82 12:15-EST Via: Brl-Bmd; 24 Nov 82 12:53-EST I would to find someone that has used CP/NOS or CP/NET. If you have tried either of these products, please send mail to me. Thanks, Ed 24-Nov-82 20:18:41,5876;000000000000 Date: Wed Nov 24 1982 20:18:41 PST From: Lauren Weinstein Subject: CP/M 3.0, continued. To: lbl-unix!info-cpm at BRL Via: Lbl-Unix; 25 Nov 82 19:46-EST Via: Brl; 25 Nov 82 19:57-EST Via: Brl-Bmd; 25 Nov 82 20:03-EST I appreciate Tony's message about 3.0, but it leads me to suspect there is still alot of confusion about 3.0 flowing around. First of all, the D.R. Graphics PACKAGE is, as far as I know, a completely separate offering from CP/M itself, and in fact does conform to certain graphics standards. The rumors I was addressing were the ones that said "... and CP/M 3.0 will support graphics". This implies that a graphics package is PART of 3.0, which I have no reason to believe to be true. In fact, Tony DID say that the graphics package was 2.2 compatible. So I guess we've laid *that* rumor to rest. Let's review what we know about CP/M 3.0 to date: (I do not claim this to be an unbiased view, as will rapidly become clear): 1) Provides more "menu-oriented" features/help command. -- probably good for SOME OEM's but probably inadequate for most users, or at least unwanted by many. Probably aimed at the turnkey business market. 2) Automatic searching of USER 0 if program not found on current user area. -- what an advance! ZCPR has provided this sort of functionality, and MUCH, MUCH more, for free, for a long time. 3) Disk blocking/deblocking moved to BDOS. -- this is a feature??? D.R. only claims "functional" compatibility between 2.2 and 3.0. I suspect there are some assumptions about the sophistication of your programs -- I'd bet any reasonable amount that ALOT of heavily used programs will not work without modification under 3.0. 4) Some sort of date/time stamping. -- reasonable I suppose. Most other systems have provided such a feature all along. Whether it is sophisticated enough for easy interfacing to different sorts of clocks, etc. is another matter. See, I am TRYING to be fair! 5) Some sort of file I/O redirection. Gee, just what Microshell does now! Why do I get the feeling that there will be some sort of restrictions to redirection, like, maybe only BDOS output (not BIOS output) will work properly with redirection? (We had to do both for MARC and it was a PAIN.) 6) Memory Usage. Now we get to the real nitty gritty. Supposedly there will be two versions of CP/M 3.0. One for people without bank- switched memory and one for people with additional memroy. If you are running a simple 64K system, the *other* features of CP/M apparently take up at least another 4K from standard 2.2. (We know that these features must be coming from somewhere, and obviously you can no longer overlay that portion of the BDOS which has the disk blocking/ deblocking code unless you a running a very simple program. If you have more than 64K memory, and someone to figure out how to interface it with your new 3.0 bios (apparently D.R. has NO interest in helping other than large, turnkey-type OEM's with such support), you can let the system reside in a different bank of memory, and give yourself a larger TPA. Also, apparently you use the additional memory in such a manner as to provide the same "sort" of functionality that FAST/SPEED have provided under 1.4 and 2.2 to do reasonable disk buffering. How well this works under the D.R. implementation, or how difficult it is to interface, remains to be same. I'll bet that > 64K memory bioses are a real PAIN to get working right, and will be very highly system dependent. The idea of having a larger TPA sounds nice at first, unless you consider having any sort of compatibility with 2.2 to be important! If you plan to write programs that will still run under 2.2, you will still be restricted to the "standard" size TPA's, and there are one hell of alot of 2.2's out there! I claim that the bottom line remains the same -- 3.0 has been oriented almost totally toward the OEM who plans to run many "identical" systems (or nearly so), and doesn't mind a very complex bios since there is only one hardware configuration to worry about. The fact that D.R. has told non-OEM's to "go away" when it comes to 3.0 is highly suspicious. I won't even drag up the issue of documentation quality again... we all know about that. The issue of CP/M 2.2 compatibility is also less important to such OEM's since, often they will just be running their own collection of programs on their hardware, and won't even try to distribute their software more widely. --- In answer to a number of questions I've received, I'm hoping to get MARC out in some form quite early in '83, and I will take a look at the issues of CP/M 3.0 compatiblity. But, frankly, I don't consider it to be a priority task. In fact, I don't know if I really want to take the time to get my complex hard disk/floppy bios running under 3.0! If I use the bank-switched version, I've got system dependencies again, and if I use the the non-banked version, I lose 4K off the top! Neither of these options is particularly appealing. For now, MARC will be a 2.2 compatible product, period. By the way, I've been "warned" that there will be some sort of review of MARC in the December BYTE (apparently as a text "box" included in the review of two other software products). The person who wrote the article is one of the beta test sites -- though he has not had the most up-to-date version of the system or utilities by any means. I think he wrote the article about eight months ago and it has taken until now to get into print! Anyway, it might be amusing reading. I *hope* it's amusing... --Lauren-- 25-Nov-82 02:42:00,415;000000000000 Date: 25 November 1982 04:42-EST From: Keith Petersen Subject: XMODEM58 available To: Info-Cpm at BRL Via: Mit-Mc; 25 Nov 82 4:59-EST Via: Brl; 25 Nov 82 5:11-EST Via: Brl-Bmd; 25 Nov 82 5:23-EST The latest version of XMODEM, the remote CP/M version of Ward Christensen's MODEM2 program, is now available on MC as AR63:CPM;XMODEM 58ASM and AR63:CPM;XMODEM 58HIS (the history file). 25-Nov-82 07:46:00,2140;000000000000 Date: 25 November 1982 09:46-EST From: Roger L Long Subject: Small-C Compiler v.2 To: info-micro at BRL, info-cpm at BRL Via: Mit-Mc; 25 Nov 82 11:03-EST Via: Brl; 25 Nov 82 11:17-EST Via: Brl-Bmd; 25 Nov 82 11:22-EST For those interested and who don't subscribe, I just though I'd mention that the December-82 issue of DR. DOBB'S JOURNAL has the first half of a listing of Small-C V.2. The second half will be published in the January-83 issue. (And hopefully someone will upload it to MC:) I haven't looked at the compiler in detail, however the article states that it differs from V.1 in the following ways: 1. Code optimization has been added. Programs are now typically 15 to 30 percent smaller than before. 2. Data initialization is supported for global variables, arrays, and pointers. Uninitialized objects default to binary zero. 3. Constant expressions are now evaluated at compile time. They may also be used as array dimensions, data initializers, and in "case" statements. 4. the #ifdef, #ifndef, #else, and #endif statements are supported with nesting. 5. The "extern" storage class is supported for global variable, array pointer, and function declarations. The effect is to declare them as external references to the assembler. 6. A mechanism for passing an argument count to called functions is provided. 7. The following new statements are now supported: a. for b. do/while c. switch/case/default d. goto 8. Lists of expressions are now permitted. 9. The assignment operators |=, ^=, &=, +=, -=, *=, /=, %=, >>=, and <<= are now supported. 10. The logical operators || and && are supported. Testing proceeds left to right and ceases when the outcome is known. 11. The operators ~ and ! are now supported 12. Local variables are now local to the block rather than the whole function. 13. The back-slash escape sequences for character and string constants have been added (per DDJ #56). There is more, but I think this gives you an idea what has been done. -roger 25-Nov-82 09:03:00,1070;000000000000 Date: 25 November 1982 11:03-EST From: Charles L Jackson Subject: Random House Thesarus To: info-cpm at BRL Via: Mit-Mc; 25 Nov 82 11:19-EST Via: Brl; 25 Nov 82 11:30-EST Via: Brl-Bmd; 25 Nov 82 11:34-EST This product, advertised in Byte, is excellent -- at least based on a week's experience. It is a thesarus which can be accessed directly or from inside Wordstar! It's extremely fast (for a floppy disc/z80). Much faster in the look-up mode than The Word, for example. It allows one to put the cursor on a word, hit escape twice, and quickly see the thesarus entry for that word. You can then select a word from the thesarus list, it will move the selected word into your text and drop the original word. It gets capitalization right most of the time. Two problems. Price $150 which is reasonable. It uses about 200k of disk space. If you write a lot in wordstar, it's a very handy tool. Regards Clj Ps it's avaliable from Dictronics -- I don't have their address here I'll post it to the net saturday. 25-Nov-82 11:03:00,685;000000000000 Date: 25 Nov 1982 1003-PST Sender: SCHNUR at Usc-Isi Subject: nec7700q/wstar From: SCHNUR at Usc-Isi To: info-cpm at BRL Message-ID: <[USC-ISI]25-Nov-82 10:03:26.SCHNUR> Via: Usc-Isi; 25 Nov 82 13:16-EST Via: Brl; 25 Nov 82 13:24-EST Via: Brl-Bmd; 25 Nov 82 14:20-EST I am looking for patches for wordstar and a nec 7700Q printer. I need to access the extra 32 characters. To interface with the ws program properly i must choose the qume option which does not have the proper sequences for the extra characters. The nec5500 does of course but will not drive the 7700 q properly since the printer uses the qume control and wire sequences. Any help? Joel (NRL-) 25-Nov-82 11:09:00,857;000000000000 Date: 25 Nov 1982 1009-PST Sender: SCHNUR at Usc-Isi Subject: data transfer From: SCHNUR at Usc-Isi To: info-cpm at BRL Message-ID: <[USC-ISI]25-Nov-82 10:09:19.SCHNUR> Via: Usc-Isi; 25 Nov 82 13:12-EST Via: Brl; 25 Nov 82 13:18-EST Via: Brl-Bmd; 25 Nov 82 14:19-EST WE are trying to down load data from a nuclear data multichannel analyzer to a chromemco. The data is in 24 bit numbers. It leaves the nuclear data machine thru a rs232 port as a sequence of 4 byte words the lowest 6 bits are the data the highest 2 tell the order of that particular word. Has anybody written a program to convert the sequence to an ascii real number . Help in this area would be appreciated. The efficiency of the program is of importance sincere are trying to obtain real time graphics on a tektronix 4025 of the data from the experiment. Joel 25-Nov-82 16:41:00,1046;000000000000 Date: 25 Nov 1982 at 1541-PST To: Charles L Jackson cc: info-cpm at BRL, fylstra.tsca at Sri-Tsc Subject: Re: Random House Thesarus In-reply-to: Your message of 25 November 1982 11:03-EST. From: fylstra.tsca at Sri-Tsc Via: Sri-Tsca; 25 Nov 82 15:51-PST Via: Sri-Tsc; 25 Nov 82 19:09-EST Via: Brl; 25 Nov 82 19:15-EST Via: Brl-Bmd; 25 Nov 82 19:40-EST I too read about the RH Thesarus and was impressed by the description. There are other useful programs such as spelling checkers that interface to Wordstar in a similar way. Let's suppose I prefer Mince over Wordstar and would like to interface it to the Thesarus. This is reasonable considering that I (like all Amethyst users) have the C sources to the outer (command interpreter) portion of Mince. Is there a specification for how such external packages get loaded (e.g. as overlays) and how they interact with the text buffer and screen? Is it useful enough to form a general purpose standard for editors in the CP/M environment? Dave Fylstra 26-Nov-82 11:35:00,859;000000000000 Date: 26 Nov 1982 at 1235-CST From: mknox at Utexas-11 Subject: CP/M 3.0 larger TPA To: info-cpm at BRL Via: Utexas-11; 26 Nov 82 13:47-EST Via: Brl; 26 Nov 82 13:56-EST Via: Brl-Bmd; 26 Nov 82 14:14-EST Actually, there are some good cases for a larger TPA. Microsoft (and probably others) seem not to have heard of a virtual memory loader. The L80 program requires that it be able to fit both the loader AND the program in memory at the same time. Couple that to the fact that the loader keeps growing with each version, and that BLANK COMMON takes up room even during load. What you have left is programs that you have to squeeze over and over to make load, but which have lots of memory left free when they are executed. Conclusion: My system needs more memory (at present) than the person who runs a .COM file. ------- 26-Nov-82 14:00:37,761;000000000000 Date: 26 Nov 82 14:00:37 EST (Fri) From: Ben Goldfarb Subject: BYE79 bug To: info-cpm at BRL Via: UCF-CS; 26 Nov 82 20:24-EST Via: Udel-Relay; 26 Nov 82 23:13-EST Via: Brl; 26 Nov 82 23:16-EST Via: Brl-Bmd; 26 Nov 82 23:35-EST There is a bug in the routine that prints the day of the week in the conditionally assembled routine for the Godbout System Support 1 real time clock. I don't know whether it has been reported before. As the code was distributed, it always prints 'Sunday' for the day of the week. This is because the routine is reading a zero byte in the MSM5832 by outputting CREAD+6 to the command port. This should be CREAD+7 to return the 'days one' digit. Ben Goldfarb 26-Nov-82 21:02:00,933;000000000000 Date: 26 November 1982 21:02 cst From: Weinstein.MK541 at Hi-Multics Subject: Bye Program for Model 16 RADIO SHACK Wanted/Model 16 Serial Port Info To: info-cpm at BRL cc: info-micro at BRL Via: Hi-Multics; 26 Nov 82 22:07-EST Via: Brl; 26 Nov 82 22:15-EST Via: Brl-Bmd; 26 Nov 82 22:44-EST I have been trying to get BYE79 up and running on the RADIO SHACK Model 16 and have little information about the serial ports. I know that the Status Port is F6H and the data port is F4H and have gotten the MSTAT,MINPUT,MOUTPUT routines to work ok...my problem is in detecting the carrier. I noticed that if you keep reading F6H....the status lies... there must be something else to do.. I am using a Hayes Smartmodem on the Model 16's Serial Port A. Can someone provide me with the information on the serial ports or... Does anyone have BYE up on the Model 16? Any inputs would be appreciated! Dennis 26-Nov-82 21:28:00,962;000000000000 Date: 26 November 1982 23:28-EST From: Charles L Jackson Subject: Thesarus (RHT) add info To: fylstra.tsca at Sri-Tsc, info-cpm at BRL, jeffrey at Office-2 Via: Mit-Mc; 27 Nov 82 0:54-EST Via: Brl; 27 Nov 82 1:01-EST Via: Brl-Bmd; 27 Nov 82 1:07-EST Two additional points: (1) The Random House Thesarus is available from Dictronics Publishing Inc. 362 Fifth Avenue New York, N.Y. 10001 Dictronics Customer Service (505) 281-5444 Tijeras New Mexico I'm not sure that that number is correct for ordering. (2) Two people asked me it this program RHT could be run from inside Mince or other non-Wordstar Editors. As far as I can tell, the answer is no. The RHT has a standalone mode. The computer will look up words in the thesarus for you. It's not nearly as convenient as using the thesarus inside the word processor! (But, it's faster than a paper, ink, fingers, mind thesarus processor). Regards Chuck 26-Nov-82 22:28:37,1801;000000000000 Date: 27 Nov 82 0:28:37-EST (Sat) From: Rick Conn To: info-cpm at BRL cc: info-micro at BRL Subject: New SYSLIB Version 2.1 Files Via: Brl; 27 Nov 82 0:34-EST Via: Brl-Bmd; 27 Nov 82 1:05-EST The following files are now in AR19:CPM on MC. They reflect the current state of the SYSLIB documentation and SYSLIB itself as released to date. T> SYSLB 1NP 3 11/26/82 T> SYSLB 2NP 4 11/26/82 T> SYSLB 3NP 2 11/27/82 SYSLB HLP 3 11/04/82 SYSLB1 HLP 3 11/04/82 SYSLB2 HLP 1 11/04/82 SYSLB3 HLP 2 11/04/82 SYSLB4 HLP 2 11/04/82 SYSLB5 HLP 2 11/04/82 SYSLB6 HLP 1 11/04/82 SYSLB7 HLP 2 11/04/82 T> SYSLB8 HLP 2 11/26/82 T> SYSLB9 HLP 2 11/26/82 SYSLBA HLP 2 11/04/82 SYSLBB HLP 1 11/04/82 T> SYSLBC HLP 2 11/26/82 B> SYSLIB 21HDWQ 3 11/26/82 B> SYSLIB 21REL 4 11/26/82 SYSLIB 21SWQ 7 11/05/82 B> SYSLIB 21WQ 17 11/26/82 The indicator T> indicates new Text Files (ASCII); the B> indicates new Binary (COM) Files. The COM files have the following CRCs: SYSLIB 21HDWQ -- 0FFD SYSLIB 21REL -- 4D42 SYSLIB 21WQ -- B6A1 To eliminate the need for those with the SYSLIB manual (now 21WQ) to download it again, the ?NP files are the pages in the manual which have changed. The new HLP files also reflect these changes. This new SYSLIB fixes a bug in the CAPSTR function and reflects several ZCPR2 design changes (which should not affect the public in general). The new manual pages are 1-6, 58-66, and 71-75. I hope that SYSLIB will stay stable for some time now. Sorry for any inconvenience this change may have caused. A new XDIR3 will come out shortly which reflects the new SYSLIB. Rick 27-Nov-82 20:43:00,471;000000000000 Date: 27 November 1982 22:43-EST From: Michael C Adler Subject: Thesaurus internals To: info-cpm at BRL Via: Mit-Ml; 27 Nov 82 22:44-EST Via: Brl; 27 Nov 82 22:49-EST Via: Brl-Bmd; 27 Nov 82 22:53-EST Can anybody describe how the thesaurus works, technically? It would be great if I could make Spell do something similar! -Michael i.e. How is it loaded, how does it get the pointer to the word, how does it not destroy text in ram... 28-Nov-82 03:00:15,488;000000000000 Date: 28 Nov 82 03:00:15 EST (Sun) From: Ben Goldfarb Subject: ALLEGED BYE79 BUG To: info-cpm at BRL Via: UCF-CS; 28 Nov 82 7:26-EST Via: Udel-Relay; 28 Nov 82 11:22-EST Via: Brl; 28 Nov 82 11:37-EST Via: Brl-Bmd; 28 Nov 82 11:45-EST Please disregard my previous comment about the supposed bug in BYE79. I must have been seeing things. The code for the day of the week routine is correct as distributed. Ben Goldfarb 28-Nov-82 04:11:16,716;000000000000 Date: 28-Nov-82 03:11:16-PST (Sun) From: UCBARPA.dag at Ucb-C70 (David Allen Gewirtz) Subject: CP/M 3.0 larger TPA Message-Id: <8210281111.13578@UCBARPA.BERKELEY.ARPA> Received: by UCBARPA.BERKELEY.ARPA (3.224 [10/16/82]) id A13577; 28-Nov-82 03:11:18-PST (Sun) Received: from UCBARPA.BERKELEY.ARPA by UCBVAX.BERKELEY.ARPA (3.227 [10/22/82]) id A23818; 28-Nov-82 11:38:13-PST (Sun) To: info-cpm at BRL, mknox at Utexas-11 Via: Ucb-C70; 28 Nov 82 14:47-EST Via: Brl; 28 Nov 82 14:58-EST Via: Brl-Bmd; 28 Nov 82 15:23-EST There are a whole lot of reasons for a larger TPA..that's why bigger micros are so nice. The main problem is one of compatibility.. what should software developers support? 26-Nov-82 14:23:52,7041;000000000000 Date: Fri Nov 26 1982 14:23:52 PST From: Lauren Weinstein Subject: CP/M 3.0 (possible message repeat) To: INFO-CPM at BRL Via: Lbl-Unix; 28 Nov 82 19:20-EST Via: Brl; 28 Nov 82 19:33-EST Via: Brl-Bmd; 28 Nov 82 19:45-EST The following is largely a repeat of a message I sent recently to INFO-CPM. I've been getting a multitude of bizarre error messages back from various network gateways, and I have no way to know if this message reached the majority of intended recipients, thusly this rerun. I will add a couple of comments here in reference to a message I got from someone who *did* receive my message. While I agree that having a big TPA would be nice for development in some cases, my biggest concern is that we will still see more and more programs that will REQUIRE that sort of TPA for program *usage* later on, not just for development. I would suggest that this will lead to a (potentially serious) fragmentation between those with "normal" TPAs and those with "extended" TPAs via unique bank-switched memory schemes. The fact that some linkers, for example, don't efficiently use the available memory is the fault of lazy software designers, and not necessarily the sort of problem at which we should simply "throw more memory" . Enough on that, here's the original message. My apologies to those of you who may have already seen it... --- I appreciate Tony's message about 3.0, but it leads me to suspect there is still alot of confusion about 3.0 flowing around. First of all, the D.R. Graphics PACKAGE is, as far as I know, a completely separate offering from CP/M itself, and in fact does conform to certain graphics standards. The rumors I was addressing were the ones that said "... and CP/M 3.0 will support graphics". This implies that a graphics package is PART of 3.0, which I have no reason to believe to be true. In fact, Tony DID say that the graphics package was 2.2 compatible. So I guess we've laid *that* rumor to rest. Let's review what we know about CP/M 3.0 to date: (I do not claim this to be an unbiased view, as will rapidly become clear): 1) Provides more "menu-oriented" features/help command. -- probably good for SOME OEM's but probably inadequate for most users, or at least unwanted by many. Probably aimed at the turnkey business market. 2) Automatic searching of USER 0 if program not found on current user area. -- what an advance! ZCPR has provided this sort of functionality, and MUCH, MUCH more, for free, for a long time. 3) Disk blocking/deblocking moved to BDOS. -- this is a feature??? D.R. only claims "functional" compatibility between 2.2 and 3.0. I suspect there are some assumptions about the sophistication of your programs -- I'd bet any reasonable amount that ALOT of heavily used programs will not work without modification under 3.0. 4) Some sort of date/time stamping. -- reasonable I suppose. Most other systems have provided such a feature all along. Whether it is sophisticated enough for easy interfacing to different sorts of clocks, etc. is another matter. See, I am TRYING to be fair! 5) Some sort of file I/O redirection. Gee, just what Microshell does now! Why do I get the feeling that there will be some sort of restrictions to redirection, like, maybe only BDOS output (not BIOS output) will work properly with redirection? (We had to do both for MARC and it was a PAIN.) 6) Memory Usage. Now we get to the real nitty gritty. Supposedly there will be two versions of CP/M 3.0. One for people without bank- switched memory and one for people with additional memroy. If you are running a simple 64K system, the *other* features of CP/M apparently take up at least another 4K from standard 2.2. (We know that these features must be coming from somewhere, and obviously you can no longer overlay that portion of the BDOS which has the disk blocking/ deblocking code unless you a running a very simple program. If you have more than 64K memory, and someone to figure out how to interface it with your new 3.0 bios (apparently D.R. has NO interest in helping other than large, turnkey-type OEM's with such support), you can let the system reside in a different bank of memory, and give yourself a larger TPA. Also, apparently you use the additional memory in such a manner as to provide the same "sort" of functionality that FAST/SPEED have provided under 1.4 and 2.2 to do reasonable disk buffering. How well this works under the D.R. implementation, or how difficult it is to interface, remains to be same. I'll bet that > 64K memory bioses are a real PAIN to get working right, and will be very highly system dependent. The idea of having a larger TPA sounds nice at first, unless you consider having any sort of compatibility with 2.2 to be important! If you plan to write programs that will still run under 2.2, you will still be restricted to the "standard" size TPA's, and there are one hell of alot of 2.2's out there! I claim that the bottom line remains the same -- 3.0 has been oriented almost totally toward the OEM who plans to run many "identical" systems (or nearly so), and doesn't mind a very complex bios since there is only one hardware configuration to worry about. The fact that D.R. has told non-OEM's to "go away" when it comes to 3.0 is highly suspicious. I won't even drag up the issue of documentation quality again... we all know about that. The issue of CP/M 2.2 compatibility is also less important to such OEM's since, often they will just be running their own collection of programs on their hardware, and won't even try to distribute their software more widely. --- In answer to a number of questions I've received, I'm hoping to get MARC out in some form quite early in '83, and I will take a look at the issues of CP/M 3.0 compatiblity. But, frankly, I don't consider it to be a priority task. In fact, I don't know if I really want to take the time to get my complex hard disk/floppy bios running under 3.0! If I use the bank-switched version, I've got system dependencies again, and if I use the the non-banked version, I lose 4K off the top! Neither of these options is particularly appealing. For now, MARC will be a 2.2 compatible product, period. By the way, I've been "warned" that there will be some sort of review of MARC in the December BYTE (apparently as a text "box" included in the review of two other software products). The person who wrote the article is one of the beta test sites -- though he has not had the most up-to-date version of the system or utilities by any means. I think he wrote the article about eight months ago and it has taken until now to get into print! Anyway, it might be amusing reading. I *hope* it's amusing.. . --Lauren-- 28-Nov-82 14:33:00,1690;000000000000 Date: Sunday, 28 November 1982, 16:33-EST From: Vinayak Wallace Reply-to: Gumby at Mit-Mc Subject: Using CP/M 3.0 To: Lauren Weinstein Cc: info-cpm at BRL, gumby at Mit-Mc Via: Mit-Mc; 28 Nov 82 17:11-EST Via: Brl; 28 Nov 82 17:17-EST Via: Brl-Bmd; 28 Nov 82 17:48-EST This is just off the top of my head; I know nothing of its logistics or feasability, etc, but.. Date: Wed Nov 24 1982 20:18:41 PST From: Lauren Weinstein Subject: CP/M 3.0, continued. To: lbl-unix!info-cpm at BRL I claim that the bottom line remains the same -- 3.0 has been oriented almost totally toward the OEM who plans to run many "identical" systems (or nearly so), and doesn't mind a very complex bios since there is only one hardware configuration to worry about. The fact that D.R. has told non-OEM's to "go away" when it comes to 3.0 is highly suspicious. I won't even drag up the issue of documentation quality again... we all know about that. What's wrong with a bunch of people getting together (say, 25 or 30 -- a club, perhaps), buying an OEM license, and then helping each other configure similar copies of 3.0 with ZCPR and any other features they want? Perhaps a bunch from the net can get together and un-hair most of the interfacing code -- standardising the parts we use which are the same. I've always wondered what extra info an OEM got on CPM anyway, and as a member of a corporation like this, I would be able to see. I wouldn't be ablle to show other people, but that's about what it's like these days with other software packages. 28-Nov-82 17:19:06,1613;000000000000 Date: Sun Nov 28 1982 17:19:06 PST From: Lauren Weinstein Subject: 3.0 To: GUMBY at Mit-Mc CC: INFO-CPM at BRL Via: Lbl-Unix; 29 Nov 82 18:06-EST Via: Brl; 29 Nov 82 18:12-EST Via: Brl-Bmd; 29 Nov 82 18:50-EST Offhand, I can see a few potential problems with your proposed idea... 1) The way D.R. operates these days, I doubt if 20 or 25 people is what they're thinking of when they're talking about OEM's! I suspect they are thinking much larger numbers. 2) I have reason to believe that the INFO-CPM readership probably represents about the MOST diverse collection of CP/M hardware to be found anywhere -- a real cross-section. This means that it is unlikely that many of us will have identical hardware configurations, particularly in the area of disks, memory, I/O, and the other parameters that can make BIOSes a pain. Anyone out there want to write a 3.0 BIOS for Persci floppies, a Morrow 10 Meg drive, and circa 1979 Microbyte memory boards? Fat chance. 3) Given the additional memory apparently required for 3.0, and the presumed complexity of new BIOSes, it is not clear how many of us would WANT to go to 3.0 even if it were made easier. Many of us have programs that would most likely need substantial modification to run under 3.0, and some people really don't have an urge to throw more money down the CP/M rathole this late in the game. --Lauren-- P.S. I wouldn't stop using MARC in any case. Every time I pop down to CP/M I feel like I've stepped back 10 years. --LW-- 28-Nov-82 18:10:00,852;000000000000 Date: 28 November 1982 20:10-EST From: Keith Petersen Subject: Using CP/M 3.0 To: GUMBY at Mit-Mc cc: Info-Cpm at BRL Via: Mit-Mc; 28 Nov 82 20:13-EST Via: Brl; 28 Nov 82 20:14-EST Via: Brl-Bmd; 28 Nov 82 20:33-EST Sol Libes says that Dave Hardy and Bruce Ratoff are both working on articles which will detail how to set up a CBIOS for CP/M 3.0. The articles are supposed to be published very soon in "Microsystems" magazine and the source code may be made available to the RCPM community so people can call and download them instead of having to type it all into their editors. I will keep everyone informed on this through Info-Cpm. It may be possible to make these files available to the Arpanet community for those who have FTP capability. In the meantime, watch "Microsystems" for the articles to appear. 28-Nov-82 19:46:00,332;000000000000 Date: 28 November 1982 21:46-EST From: Keith Petersen Subject: XMODEM58 bug To: INFO-CPM at BRL Via: Mit-Mc; 28 Nov 82 21:52-EST Via: Brl; 28 Nov 82 22:03-EST Via: Brl-Bmd; 28 Nov 82 22:09-EST XMODEM58.ASM has been withdrawn due to an error in the file. It will be made available again when it's fixed. 28-Nov-82 20:08:00,1344;000000000000 Date: 28 Nov 1982 at 2108-CST From: mknox at Utexas-11 Subject: CP/M 3.0 comments To: info-cpm at BRL Via: Utexas-11; 28 Nov 82 22:33-EST Via: Brl; 28 Nov 82 22:42-EST Via: Brl-Bmd; 28 Nov 82 22:48-EST A few comments concerning Gumby's msg. The idea of a club getting together and purchasing an OEM agreement is probably quite reasonable. The minimum number of copies for a reasonable discount is usually 25, and the discount is usually about 60% of list. I see no reason for DR to not agree to this. As for what extra info OEMers get; virtually nothing. Just a little earlier and a little more unreadable. However, they are for certain on the list for the mailout of fixes, which a good deal of them then do NOT pass on. (Note: P&T is one of the few I know of who send out fixes, both from them- selves and DR, as they come out.) About ZCPR and 3.0. The OEM agreement prevents the OEMer from modifying the BDOS and CCP (or other included processors). He can add additional processors (FORMAT, MEMTEST, FOOBAR, that sort of thing), but he cannot sell CP/M cum ZCPR as CP/M. A legally fine point? It might be permissable to distribute the original CP/M 3.0, unmodified, and with a copy of ZCPR and instructions (or an auto-install program). That might meet the needs of the ARPA community. ------- 28-Nov-82 21:55:00,1005;000000000000 Date: 28 November 1982 23:55-EST From: Roger L Long Subject: SQ/USQ wildcards? To: info-cpm at BRL Via: Mit-Mc; 28 Nov 82 23:57-EST Via: Brl; 29 Nov 82 0:08-EST Via: Brl-Bmd; 29 Nov 82 0:24-EST I recently downloaded SQ-16 and USQ-19 from the MC-CPM archives. The documentation seems to be the old version 15 documentation, and without going through the source (I only downloaded the COMs), I can't seem to get wildcards to work in the manner that I expect they should. Could someone please help me out and tell me what I'm assuming incorrectly? The command that I'm giving that's causing an error is: A>usq b: b:*.doc Now I assume that will squeeze all the .DOC files on B:, placing the resultant .DQC files on B:. It finds the first file, goes through the analysis, and says "S not found" or some such error. I'm assuming (hoping) from the comments in the front of SQ-16 and USQ-19 that they will properly handle wildcards, so I don't need FLS. -roger 29-Nov-82 02:32:29,342;000000000000 Date: 29 Nov 82 02:32:29 EST (Mon) From: Ben Goldfarb Subject: Re: XMODEM58 bug To: Keith Petersen , INFO-CPM at BRL Via: UCF-CS; 29 Nov 82 4:58-EST Via: Udel-Relay; 29 Nov 82 5:04-EST Via: Brl; 29 Nov 82 5:10-EST Via: Brl-Bmd; 29 Nov 82 5:16-EST Aha! I thought so! 29-Nov-82 02:36:00,711;000000000000 Date: 29 November 1982 04:36-EST From: Keith Petersen Subject: SQ/USQ files replaced To: Info-Cpm at BRL Via: Mit-Mc; 29 Nov 82 4:53-EST Via: Brl; 29 Nov 82 4:57-EST Via: Brl-Bmd; 29 Nov 82 5:03-EST Several people have reported problems with SQ and USQ as supplied from AR51:CPM. I checked and found the CRCs did not read correctly. I have replaced both files and made new HEX files for those who cannot FTP COM files. AR51:CPM;USQ-19 COM CRC=2E 55 AR51:CPM;SQ-16 COM CRC=F7 95 The HEX files are in AR13:CPM; For those who do not know, these are the same as SQ-15 and USQ-15 except they now accept wild cards, which means that FLS should no longer be needed. 29-Nov-82 07:57:00,733;000000000000 Date: Monday, 29 November 1982 09:57-EST Sender: RG.JMTURN.MIT-OZ at BRL From: RG.JMTURN at Mit-Mc To: info-cpm at BRL Via: Mit-Mc; 29 Nov 82 10:02-EST Via: Brl; 29 Nov 82 10:15-EST Via: Brl-Bmd; 29 Nov 82 10:42-EST I have found an infintely wrong behavior in the TMODEM V 3.0 porgram (on MIT-OZ). It does not take the last ^Z encountered in the stream as EOF, but rather the first ^Z. This means you can't send a file with a control-Z in it. The right thing to do is to have it keep each packet until it sees if the next character is EOT or SOH, and if it is EOT, go back and remove the ^Zs at the end of the last packet. Do I have to fix the problem, or can someone more proficient at C do it? James 29-Nov-82 15:45:00,544;000000000000 Date: 29 Nov 1982 15:45 PST From: MKrigel.ES at Parc-Maxc Subject: Re: CP/M 3.0 comments In-reply-to: mknox's message of 28 Nov 1982 at 2108-CST To: mknox at Utexas-11 cc: info-cpm at BRL Reply to: MKrigel.es Via: Parc-Maxc; 29 Nov 82 18:57-EST Via: Brl; 29 Nov 82 19:08-EST Via: Brl-Bmd; 29 Nov 82 19:15-EST Hay. If you guys are serious, I've got OEM agreements with several companies and, (if your serious enough to commit to buying CPM 3.0), would be more than willing to get one with DR and pass on the goodies. Marc 29-Nov-82 16:59:30,937;000000000000 Date: 29 Nov 1982 15:59:30-PST From: CCVAX.revc at Nosc-Cc To: info-cpm at BRL Subject: RCP/M help Cc: CCVAX.revc at Nosc-Cc Via: Nosc-Cc; 29 Nov 82 19:05-EST Via: Brl; 29 Nov 82 19:17-EST Via: Brl-Bmd; 29 Nov 82 19:28-EST The San Diego Computer Society is planning to build a software exchange system based on the RCP/M software packages. We would appreciate the following information. 1) Is there a central clearing house for the latest 'official' versions of the software? (Non-Arpa) 2) Are any of the packages proprietary, and if so, who do we contact? 3) Has anyone implemented a multi-user RCP/M? We are looking at a Discovery multi-processor unit configured for a minimum of four dial-in lines. 4) We may have to run a 'Show-and-Tell' program on a large monitor on public display. Have you seen anything that would be good for this? Thanx - Bob Van Cleef revc@NOSC:CCVAX 29-Nov-82 17:50:00,458;000000000000 Date: 29 November 1982 19:50-EST From: Michael C Adler Subject: To: whomever wrote MCAR41:CPM;MODEMA OSBORN To: Info-cpm at BRL Via: Mit-Ml; 29 Nov 82 20:21-EST Via: Brl; 29 Nov 82 20:32-EST Via: Brl-Bmd; 29 Nov 82 20:39-EST I am going to help a friend load files on his Osborne. Contrary to the documentation at the beginning of the program, does this run on one without modification with a dumb modem? thanks, -Michael 29-Nov-82 18:48:00,1195;000000000000 Date: 29 November 1982 20:48-EST From: Charlie Strom Subject: More on CP/M Plus To: INFO-CPM at BRL Via: Mit-Mc; 29 Nov 82 20:51-EST Via: Brl; 29 Nov 82 21:20-EST Via: Brl-Bmd; 29 Nov 82 21:54-EST CP/M Plus (it has already had a name change! formerly CP/M 3.0) will be officially announced at Comdex this week according to a friend of mine at D.R. His comments have also led me to believe that they have had second thoughts about supporting end-users; the manuals are readable! (so he claims) and designed for the hacker to be able to bring the system up without need for valium. D.R. has also announced a CBBS for supporting their products. I have not tried it myself yet, but my friend tells me you need a valis serial number to log in! He also says that their Vax has lost a lot of the older serial numbers, so don't be all that surprised if you have trouble accessing the CBBS (I won't even try out my Imsai CP/M 1.3 serial number!) I get the feeling (maybe its just hope) that D.R. is making a greater effort to support the CP/M community. I hope so. Charlie Strom Yipes - I almost forgot the CBBS number! - 408-649-5186 (300 baud) 30-Nov-82 00:04:50,415;000000000000 Date: 29-Nov-82 23:04:50-PST (Mon) From: UCBVAX.npois!harpo!decvax!goutal at Ucb-C70 Subject: MARC Message-Id: <8210300704.10023@UCBVAX.BERKELEY.ARPA> Received: by UCBVAX.BERKELEY.ARPA (3.227 [10/22/82]) id A10016; 29-Nov-82 23:04:55-PST (Mon) To: harpo!npois!ucbvax!C70: info-cpm at Ucb-C70 Via: Mit-Ai; 30 Nov 82 2:14-EST Via: Brl; 30 Nov 82 2:16-EST Via: Brl-Bmd; 30 Nov 82 2:42-EST What IS it? 30-Nov-82 00:57:00,758;000000000000 Date: 29 November 1982 23:57-PST (Monday) From: Allan M Schiffman Subject: IBM PC and ITS To: info-cpm at Mit-Mc Via: Mit-Mc; 30 Nov 82 6:56-EST Via: Brl; 30 Nov 82 7:12-EST Via: Brl-Bmd; 30 Nov 82 7:22-EST I have a friend with an IBM PC and the Microstuf, Inc. program "Crosstalk" (which is a program for communicating with a serial line). He uses it, of course, to connect to his modem. Does anyone know what terminal this program emulates, if any? Is there a standard set of control character sequences for the PC? Is there any ITS CRTSTY options set up that would make my friend's life more wonderful? Is there some other list I should send this message to? What happened to Info-Micro? Thanks, -Allan 30-Nov-82 10:13:00,725;000000000000 Date: 30 Nov 1982 10:13 PST From: DBrown at Parc-Maxc Subject: DIGITAL RESEARCH -- CBBS To: INFO-CPM at BRL cc: DBrown at Parc-Maxc Via: Parc-Maxc; 30 Nov 82 13:17-EST Via: Brl; 30 Nov 82 13:36-EST Via: Brl-Bmd; 30 Nov 82 13:55-EST I called the number (408-649-5186) and found out it works. The hardware they are using is: Altos 8000-10 microcomputer; (running CP/M 2.2(4FO)); single 8" floppy drive; single 8" Shugart 10 M-byte hard disk; Racal-Vadic VA3450P external modem. Its nice to know you don't have to call during normal working hours. Now I'm able leave a message when I have a problem, not the next working day. Darrah 30-Nov-82 18:07:00,1432;000000000000 Date: 30 Nov 1982 18:07 EST From: clark.wbst at Parc-Maxc Subject: What is MARC? To: info-cpm at Mit-Mc, decvax!goutal at Ucb-C70 Via: Mit-Mc; 1 Dec 82 3:17-EST Via: Brl; 1 Dec 82 3:40-EST Via: Brl-Bmd; 1 Dec 82 4:08-EST MARC looks very much like V6 UNIX to the user. It runs on any micro that runs cp/m, and comes up by absorbing the cp/m bios from the existing system. It is not a multitasking system, so you can't fork things off to run in the background, or do anything that implies two things going on at once. An exception is that pipes from the shell are implemented with intermediate files. MARC has a version of BDS C that is custom made for it, I think with floating point. It also has a version of MINCE (an editor similar to emacs) for it. It has a CP/M emulator so that all but the very largest CP/M software will run under it. I think anything that fits in a 48K TPA will work. I have a many page question and answer type blurb on it along with a sample terminal session that I can send to whoever asks. The material I have is half a year old, and half several years old (When I talked to him 2 or 3 years ago he was surprised it was still around!). I saw it working last July; it really does work! In fact, uucp site "vortex" is a z80 running MARC! vortex!lauren (Lauren Weinstein) is in charge of getting MARC to market. Is that a fair description Lauren? --Ray Clark 30-Nov-82 22:16:00,1198;000000000000 Date: 30 Nov 1982 22:16:00 CST (Tuesday) From: Mike Meyer Subject: MPM 2 bug To: info-cpm at Okc-Unix Cc: mwm at Okc-Unix Via: Okc-Unix; 30 Nov 82 23:25-EST Via: Brl; 30 Nov 82 23:38-EST Via: Brl-Bmd; 30 Nov 82 23:46-EST About 6 months ago, I ran into a (rather nasty) MPM 2.0 bug. While discussing DRI's software support with someone, this came up again. Somebody suggested posting it here, both as a warning, and on the off chance that sombody knows of a fix. The problem is that MPM does NOT reinitialize page zero in a when a process exits, unless page zero of the partition is also page zero for a bank. This is a problem if you have a program that twists things in page zero. Any of the `CCP replacements' (microshell, etc) or a menu-driven system that uses program chainging (Magic Wand II) will trip over this. The sympton is that, after running such a program, you get the thing back the very next time something exits, IF you took a hard (^C or whatever) exit. When I talked to DRI about it, they said `send us a disk with software that displays the problem, and we may look at it.' Just one of the many reasons that I hate DRI. Subject: Wordstar's character width table. To: INFO-CPM at Mit-Mc Via: Mit-Mc; 1 Dec 82 1:21-EST Via: Brl; 1 Dec 82 1:35-EST Via: Brl-Bmd; 1 Dec 82 1:43-EST This is the table that wordstar uses to calculate the size of all of the characters that need to be printed on the printer. Does anyone know the address within WS.COM that this exists? thanks, lewis Bean at Mit-Mc