1-Oct-85 05:47:05-MDT,1131;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 1 Oct 85 05:47:01-MDT Received: from brl-tgr.arpa by AMSAA.ARPA id a018220; 1 Oct 85 7:14 EDT Received: from usenet by TGR.BRL.ARPA id a020540; 30 Sep 85 20:01 EDT From: Melinda Shore Newsgroups: net.micro.cpm Subject: Re: wanna buy TurboPascal for CP/M-80 Message-ID: <1148@sphinx.UChicago.UUCP> Date: 27 Sep 85 20:39:46 GMT To: info-cpm@AMSAA.ARPA [] Try the Programmer's Shop in Massachusetts. I've had uniformly excellent experiences buying my software from them. They claim to carry every programmer's tool for CP/M, MS-DOS, and MacIntosh computers. Programmer's Shop 128 Rockland St. Hanover, MA 02339 800-421-8006 I don't know their price for Turbo Pascal, but I know they've got it. [I'm not affiliated with the Programmer's Shop] -- Melinda Shore ..!ihnp4!gargoyle!sphinx!shor University of Chicago Computation Center Staff.Melinda%chip@UChicago.Bitnet "Beavers, by teamwork family life!" [Dr. Bronner] 1-Oct-85 06:10:08-MDT,1815;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 1 Oct 85 06:10:00-MDT Received: from ames-vmsb.arpa by AMSAA.ARPA id a018491; 1 Oct 85 7:24 EDT Date: 30 Sep 85 16:57:00 PST From: nep.pgelhausen@AMES-VMSB.ARPA To: info-cpm@AMSAA.ARPA Reply-To: nep.pgelhausen@AMES-VMSB.ARPA I tried sending this directly, but the net wasn't taking UCHICAGO in the path....oh well, in reply to: > From: Stuart Schmukler > Subject: BREAK on Osborne I > > Does anyone have code that generates a BREAK for the Osborne I? > > I have tried unsuccessfully to add code to Osborne I Kermit to generate a > BREAK. I thought since the Apple ][ CCS 7710A card uses a memory mapped > 6850, that similar code should work on the Osborne I. But of course :-) it > does not work. > > Are there any Osborne Wisards out there that can help? > > SaS The break signal is merely a sustained SPACE signal in the RS-232 connection. (SPACE referring to the MARK/SPACE (1/0) distinction, not the ascii 32 space code...) If you have direct access to the lines on the RS-232 port on your osborne from software, you can create a small routine to pull this line down for a short period. Normally the port carries a MARK signal, broken by a SPACE then 8 bits of ascii code w/ 1 or two stop bits. I may have my usage of MARK & SPACE reversed. It could be carrying the SPACE normally, requiring a sustained MARK to use as BREAK. See your systems documentation on RS-232 port usage (if any....). Hope this helps, -Richard Hartman max.hartman@ames-vmsb P.S.: as long as I am sending this to the net in general, could anyone post the actual mechanics of what I was *trying* to explain? -rmh ------ 1-Oct-85 06:25:22-MDT,676;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 1 Oct 85 06:25:16-MDT Received: from washington.arpa by AMSAA.ARPA id a018718; 1 Oct 85 7:31 EDT Date: Mon 30 Sep 85 18:04:18-PDT From: Ronald Blanford Subject: Bulletin boards To: info-cpm@AMSAA.ARPA I am looking for programs to set up a bulletin board system on a NEC APC. It can be either CP/M-86 or MS-DOS. Since it's extremely unlikely that one exists already configured for the APC, it probably has to include at a minimum the ability to link in or overlay the communications routines. Can anyone give me pointers? -- Ron ------- 1-Oct-85 08:02:32-MDT,658;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 1 Oct 85 08:02:27-MDT Received: from mit-multics.arpa by AMSAA.ARPA id a022497; 1 Oct 85 9:31 EDT Date: Tue, 1 Oct 85 09:30 EDT From: AALevy@MIT-MULTICS.ARPA Subject: program to help WSTAR find overlays To: info-cpm@AMSAA.ARPA Message-ID: <851001133017.582675@MIT-MULTICS.ARPA> There is a program that modified WSTAR and similar programs to find overlays even if they were on another disk or user area. I believe it was called SETDRU (I could be wrong). I do not know if it was PD or not. Any help would be appreciated. Regards, Allan 1-Oct-85 10:18:45-MDT,1025;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 1 Oct 85 10:18:39-MDT Received: from brl-aos.arpa by AMSAA.ARPA id a026279; 1 Oct 85 11:35 EDT Received: from csnet-pdn-gw by AOS.BRL.ARPA id a016103; 1 Oct 85 10:20 EDT Received: from gmr by csnet-relay.csnet id ad01709; 1 Oct 85 10:17 EDT Date: Tue, 1 Oct 85 08:22 EST From: haar%gmr.csnet@CSNET-RELAY.ARPA MMDF-Warning: Parse error in original version of preceding line at CSNET-RELAY.ARPA To: info-cpm@BRL.ARPA Subject: D.R.C. S-100 RamDisk Have any of you used the 256K S-100 Solid State Disk Simulator (ramdisk) from Digital Research Computers ? If so, I would like to hear your comments. I am thinking about getting one since the price has dropped to less than $200. They provide BIOS code for CP/M 2.2. Does anyone have a CP/M Plus version? Is it really S-100 (IEEE 696) compatible? Is it reliable? I would appreciate any advice on this product/company. thanks, Bob Haar 1-Oct-85 11:12:57-MDT,1138;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 1 Oct 85 11:12:50-MDT Received: from rand-unix.arpa by AMSAA.ARPA id a028074; 1 Oct 85 12:39 EDT Return-Path: Received: by rand-unix.ARPA; Tue, 1 Oct 85 09:44:16 pdt From: Bridger Mitchell Message-Id: <8510011644.AA14995@rand-unix.ARPA> Date: 01 Oct 85 09:44:14 PDT (Tue) To: AALevy@MIT-MULTICS.ARPA Cc: info-cpm@AMSAA.ARPA, bridger@RAND-UNIX.ARPA Subject: Re: program to help WSTAR find overlays In-Reply-To: Your message of Tue, 1 Oct 85 09:30 EDT. <851001133017.582675@MIT-MULTICS.ARPA> SETDRU is one method. PUBlic files are another, one that requires no patches to the program and uses no tpa, but does patch the bdos. PUBPATCH, in the simtel20 directory of that name, is a z80 patch to an UNMODIFIED cp/m 2.2 bdos that makes a file PUBlic when attrribute bit 2 is set in the directory. A PUBlic file is accessible from all user numbers on the disk. See our article in Dr. Dobbs' Jrnl. Oct (or Nov) 1984 for further description. --bridger mitchell 1-Oct-85 11:25:16-MDT,1126;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 1 Oct 85 11:25:11-MDT Received: from apg-1.arpa by AMSAA.ARPA id a028506; 1 Oct 85 12:53 EDT Date: Tue, 1 Oct 85 12:46:23 EDT From: Robert Bloom AMSTE-TOI 3775 Subject: Re: program to help WSTAR find overlays In-Reply-To: Your message of Tue, 1 Oct 85 09:30 EDT To: AALevy@MIT-MULTICS.ARPA Cc: info-cpm@AMSAA.ARPA setdru.lbr is the file name of the program you asked for to let WordStar find its overlays files in other user areas. However, I don't think that is what you *really* want. For that, look to pubpat.lbr. That is a BDOS patch that allows *any* program to cross user lines for overlays. (I use it for WordStar, dBase and SuperCalc with no problems.) One activatives a file to be accessable in any area by setting the high-bit of second character of the file-name. I use NSWP for this, the pubpat libarary has it's own program for it. There are some side effects but none as bad as those in setdru. As Jerry says, recommended. -bob bloom 1-Oct-85 13:13:36-MDT,7758;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 1 Oct 85 13:13:20-MDT Date: Tue, 1 Oct 85 14:14:36 EDT From: David Towson (SECAD) To: info-cpm@AMSAA.ARPA Subject: 7000+ character tutorial on sending BREAK: Fellow CP/Mers - In response to a recent request for information regarding how to send BREAK from a microcomputer, here is a 7000+ character tutorial on the subject. Sample code is included. The American Standard Code for Information Interchange (ASCII) defines a set of 128 characters that are encoded as the various combinations of seven bits. When this code is used over a serial asynchronous communications link, some additional bits are added to the seven ASCII bits to form the total "package" that is transmitted for each character sent. The term "asynchronous" means that the receiver doesn't know in advance when a character is coming. It just sits in an "idle" state until some special event signals the start of a new character. This idle state is caused by the presence of a steady logic-one signal at the receiver input, and it can last indefinitely. The "special event" that signals the beginning of a new character is a transition from the idle-state logic-one signal to a logic-zero which lasts for one bit-time, and is known as a "start-bit". A start-bit "wakes-up" the receiver, which then records in some sort of memory, typically a shift-register, the states of the next seven or eight bits. Whether seven or eight bits are recorded depends on whether "parity" is being used. Parity is a simple error detection scheme that, though easily deceived, is better than nothing. It is implemented by adding an extra bit (the eighth bit) to the existing seven ASCII bits such that the total number of logic-one bits in the eight-bit group is either odd or even, depending on whether "odd parity" or "even parity" is being used. For example, the ASCII representation for "A" is "1000001", which has an even number of 1's. Therefore, adding even parity results in "01000001", which still has an even number of 1's, whereas the odd parity representation is "11000001". After the start-bit and seven or eight "data-bits", the receiver expects to see a return to the logic-one state to signify the end of the character. This logic-one state lasts for at least one bit-time, and is known as a "stop-bit" (or bits). Typically, one stop-bit is used for all speeds greater than 110 baud, and two stop-bits are used at 110 baud and below. This convention derives from the mechanical roots of teleprinting, where the electro-mechanical devices used to decode and print the received characters needed time to stop quivering after each character before being ready to decode and print the next. To summarize then, an ASCII character sent via an asynchronous serial channel consists of one start-bit, seven or eight data-bits (depending on whether parity is being used), and one or two stop-bits (depending on the speed of transmission). This brings us (at last) to the BREAK signal. The BREAK signal has its roots at least as far back as the days of mechanical teleprinters, perhaps all the way back to electro-mechanical telegraphy. Early teleprinters used an electro-mechanical device called a "selector" to perform the decoding function now done electronically by devices such as the Universal Asynchronous Receiver Transmitter (UART). The start-bit caused a current flowing in the selector electro-magnet to cease, thereby releasing a clutch that set into motion a complex mechanical process that resulted in the printing of the received character. This process made a considerable noise, even when a non-printing character such as a space was received. If a steady logic-zero signal (no current in the selector magnet) was presented to the receiving teleprinter, the machine emitted a steady rhythmic clunking that was impossible to ignore. Consequently, the machines had a key labeled BREAK that merely opened the series DC circuit connecting all transmitters and receivers in the teleprinter network, thereby getting the attention of all operators. There was also a BELL character, but this had to be correctly decoded by a receiver in order to ring the bell, whereas the BREAK was a "non-character" that could be used to interrupt a transmission- in-progress, since it simply disrupted the whole network and made a lot of noise at each receiving teleprinter. Today, the BREAK signal performs a similar function in a similar manner. It is used now most often to gain the attention of a computer or other machine, rather than to alert a human operator. But it is still generated by sending a logic-zero signal of indeterminate length, although by convention some specific durations (typically in the 300 - 500 millisecond range) have been adopted. Modern electronic receiving circuits such as those whose names end with "ART" (as in UART) interpret the beginning of the BREAK as a start-bit followed by seven or eight logic-zero data-bits (the ASCII NUL character). But the expected stop-bit (return to logic-one state) is missing. This causes the receiving circuit to generate an error condition called "framing error", which is typically signaled by the setting of an error-bit in the status register of the receiving device. How the "user machine" responds to this condition is determined by the user-machine's software. The example to follow shows how a BREAK can be sent via software control of a 1602 UART. This device, which is typical of many such devices, has a command instruction that forces the output to a logic-zero state until the complementary instruction is issued. The code is taken from my MODEM7 overlay for the TRS-80 Model-I computer. All code not needed for this specific example has been deleted. ;..... ; RESETP: EQU 0E8H ;Reset port for UART. BAUDP: EQU 0E9H ;Data-rate port for UART. CONTROLP: EQU 0EAH ;Status/control port for UART. BRKMASK: EQU 0FBH ;And-mask to turn on break. ; ;..... ; ; ; UART initialization routine for TRS-80 Model I. ; TRSINIT: OUT RESETP ;Reset UART (data in A register is ;insignificant). MVI A,55H ;Use 55H for 300 baud. ;Use 77H for 1200 baud. OUT BAUDP ;Set UART data-rate. ; MVI A,0ECH ;Set UART for 8-bit word, ;no parity, no break and OUT CONTROLP ;DTR and RTS on. STA CONTROLB ;Save the UART control byte. RET ; ; ; ;..... ; ; CONTROLB: DB 0 ;UART control byte save. ; ; ;..... ; ; ; Routine to send a break-tone of approximately 300 ms duration. ; SENDBRK: PUSH B ;Save all double registers. PUSH D ; PUSH H ; LDA CONTROLB ;Get current UART control byte. ANI BRKMASK ;Change bit to turn on break. OUT CONTROLP ;Send new byte to control port. MVI B,3 ;Set count for timer. CALL TIMER ;Wait 300 milliseconds. LDA CONTROLB ;Restore original control byte OUT CONTROLP ;to turn off break. POP H ;Restore double registers. POP D ; POP B ; RET ; ; ; ;..... Note that the particular control-bytes needed to program the 1602 UART were determined from the 1602 data sheet. It is pointless to attempt writing this kind of code unless you have access to this kind of information. Many readers of info-cpm can help in this regard. Many other examples can be found in the overlay files on SIMTEL20 in directories PD: and PD:, available via FTP with login username "anonymous" and password "ftp" (or any other printing string). Dave 1-Oct-85 13:34:12-MDT,2747;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 1 Oct 85 13:34:03-MDT Received: from brl-aos.arpa by AMSAA.ARPA id a002463; 1 Oct 85 14:50 EDT Received: from mit-mc.arpa by AOS.BRL.ARPA id a025834; 1 Oct 85 14:32 EDT Received: from CSNET-RELAY.ARPA by MIT-MC.ARPA 1 Oct 85 14:32:53 EDT Received: from gte-labs by csnet-relay.csnet id ab03440; 1 Oct 85 14:23 EDT Received: by bunny.UUCP (4.12/5.03) id AA19995; Tue, 1 Oct 85 10:37:14 edt for Date: Tue, 1 Oct 85 10:37:14 edt From: Alan Gunderson To: info-cpm%mit-mc.csnet@BRL.ARPA Subject: SB180 help I have purchased a SB180 board and have wired it into a power supply and installed two Tandon TM-65-2 48 tpi 5-1/4" DSDD drives (80 tracks per drive, unformatted 500K bytes maximum storage). These drives do not support the READY line, so I have installed the JP 6 jumper on the SB180, which makes the disk controller think the disk drives are always ready. The ROM monitor on the SB180, when it see's that the drives are ready, assumes that the user wants to autoboot from the floppy. When I try to boot the ZRDOS operating system, I get the operating system sign-on for version 2.1 of ZRDOS. According to the manual, this indicates that ZRDOS has been correctly loaded into memory. I then get the message Read Error on A: I have installed a switch as part of my JP 6 jumper, so I can make the monitor think that the floppies are not ready and thus enter the command entry state. From the monitor, I have not been able to format floppies. The program disappears for a time and then aborts with a dump of the disk controller status registers and the head, track, and sector in which the format dies. Using the monitor R command, I am able to read sectors from the operating system diskette. When I go beyond sector 9 with the read, I get the same disk controller status register dump. The Tandon drives do not support the Head Load line in the interface. This is pin 4 and is listed as a spare for the floppy. The SB180 manual alludes to the fact that Head Load is not required but is desirable to extend the life of the diskettes. Is this line required? Is there any way to make the Tandon drives support the READY line (pin 34)? The Tandon manual alludes to this line being optionally enabled, but does not tell how. There is no jumper documented. Has anyone else tried to interface this type of drive to the SB180? If so, please provide any hints or insights. Any other SB180 ideas?? Thanks in advance. ====Alan Gunderson uucp: ...!seismo!harvard!bunny!asg0 csnet: asg0%gte-labs.csnet@csnet-relay.arpa 2-Oct-85 06:41:19-MDT,1896;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 2 Oct 85 06:41:11-MDT Received: from usc-isid.arpa by AMSAA.ARPA id a004267; 2 Oct 85 7:34 EDT Date: 2 Oct 1985 06:30-EDT Sender: ABN.ISCAMS@USC-ISID.ARPA Subject: Re: program to help WSTAR find overlays From: ABN.ISCAMS@USC-ISID.ARPA To: bridger@RAND-UNIX.ARPA Cc: AALevy@MIT-MULTICS.ARPA, info-cpm@AMSAA.ARPA Message-ID: <[USC-ISID.ARPA] 2-Oct-85 06:30:37.ABN.ISCAMS> In-Reply-To: <8510011644.AA14995@rand-unix.ARPA> Re PUBPATCH in finding WS overlays.. PUBPATCH will look to "root" disk same user, then "root" disk user 0, for .COM files but will NOT find overlays! (Had this problem with WS, Turbo Pascal, others.) Also, while within WS, you can't RUN programs not in your immediate user area because WS doesn't seem to use the BDOS calls to find files. So PUBPATCH won't be of much help in this case. I ended up keeping one copy of WS.COM in my "root" disk, A0, along with "original" copies of the required overlays. Then used DUPUSR (another public domain program .. copies a directory entry to another user area but NOT the program, saving MUCH disk space) to copy overlay file names to all required user areas. STATed them protected and invisible so the names wouldn't be in the way. Could then run WS from any disk any user, with NO increased disk usage. Worked fine, did the same with Turbo Pascal and a couple other programs that had associated data files. Yep, there is a WS patch program in the SIMTEL20 archives, and I think it IS named SETDRU.COM. Patches WS directly, as I recall, so WS is then smart enough to find its overlays at a selected "root" disk/user. A little more elegant than my DUPUSR kludge, but then I'd used DUPUSR for other things and kind of got in a rut. Regards, David Kirschbaum Toad Hall ABN.ISCAMS@USC-ISID 2-Oct-85 07:09:21-MDT,844;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 2 Oct 85 07:09:16-MDT Received: from brl-aos.arpa by AMSAA.ARPA id a003341; 2 Oct 85 7:10 EDT Received: from simtel20.arpa by AOS.BRL.ARPA id a001682; 2 Oct 85 1:36 EDT Date: Monday, 30 September 1985 13:50-MDT Message-ID: Sender: "B.Eiben LCG Ext 617-467-4431" From: "B.Eiben LCG Ext 617-467-4431" Subject: CPM:Floppy.fmt ReSent-From: KPETERSEN@SIMTEL20.ARPA ReSent-To: Info-Cpm@BRL.ARPA ReSent-Date: Tue 1 Oct 1985 23:34-MDT Filename Type Bytes CRC SIMTEL20 directory MICRO: FLOPPY.FMT.5 ASCII 10708 7BDDH Has been updated [thanks to Hal Bower] with AMPRO-info - and some entries have been corrected too. 2-Oct-85 07:11:18-MDT,1230;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 2 Oct 85 07:11:12-MDT Received: from lll-mfe.arpa by AMSAA.ARPA id a003458; 2 Oct 85 7:14 EDT Date: Tue, 1 Oct 85 16:49 EDT From: SECRIST%OAK.SAINET.MFENET@LLL-MFE.ARPA Subject: CCPPATCH.ASM To: INFO-CPM@AMSAA.ARPA There is some code on [the fine] Royal Oak BBS (ergo SIMTEL20) called CCPPATCH.ASM. It's purpose in life is similar to that of the Wordstar user-number hoppers that have been discussed of late, only it's more generic - instead of user numbers it works with drives. For example, if I try to fire up an image on C: and it's not there, CCPPATCH makes the system look on A: before it errors-out on you. My problem is - what do you build it with and/or does it work ? I blindly threw it at ASM, but ASM wasn't fond of it - undefined labels. I dunno - maybe those are Z80 ops. Basically, I want a tool to do this intended purpose, and if you have had luck with CCPPATCH and can correct my brain damage or have a similar tool, I'll be happy to summarize the responses to the net. Richard Secrist Science Applications Int'l. Corp., Oak Ridge, Tenn. SECRIST%OAK.SAInet.MFEnet@LLL-MFE.Arpa 2-Oct-85 07:15:28-MDT,659;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 2 Oct 85 07:15:22-MDT Received: from css-ring-gw by AMSAA.ARPA id a003824; 2 Oct 85 7:23 EDT Return-Path: Received: from wucs.UUCP by seismo.CSS.GOV with UUCP; Tue, 1 Oct 85 21:21:09 EDT Received: by wucs.WU.UUCP; Tue, 1 Oct 85 19:36:05 CDT Date: Tue, 1 Oct 85 19:36:05 CDT From: Steve Cousins Message-Id: <8510020036.AA22977@wucs.WU.UUCP> To: info-cpm@AMSAA.ARPA, info-cpm-request@AMSAA.ARPA Subject: Please remove me from the info-cpm list Please take my name off of the list. Thanks. Steve Cousins 2-Oct-85 07:19:08-MDT,1631;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 2 Oct 85 07:19:00-MDT Received: from brl-tgr.arpa by AMSAA.ARPA id aa04022; 2 Oct 85 7:27 EDT Received: from usenet by TGR.BRL.ARPA id a007076; 1 Oct 85 16:20 EDT From: Chuck McManis Newsgroups: net.micro.cpm Subject: Re: Little Board / SB180 compatibility Message-ID: <104@intelca.UUCP> Date: 30 Sep 85 15:40:34 GMT To: info-cpm@AMSAA.ARPA > For AMPRO/Little Board and Ciarcia HD64180 board owners. > An undocumented feature that I discovered is that the > 5 1/4 disc formats are identical for both machines. > > Now what engineer in his right mind would have made that > unforgivable error? Must be a bug... > ------- Hardly undocumented, since it says so right in the article. Yet why consider it a bug? Are we missing a smiley face here? So now that I have built my new system into a Fraggle Rock lunch box where do I put my sandwich? Kaypro eat your heart out. \\ :: \\ :: || || (a poor attempt at a LARGE smiley face) :: || :: // // --Chuck -- - - - D I S C L A I M E R - - - {ihnp4,fortune}!dual\ All opinions expressed herein are my {qantel,idi}-> !intelca!cem own and not those of my employer, my {ucbvax,hao}!hplabs/ friends, or my avocado plant. :-} 2-Oct-85 07:38:09-MDT,898;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 2 Oct 85 07:38:04-MDT Received: from brl-aos.arpa by AMSAA.ARPA id a006240; 2 Oct 85 8:25 EDT Received: from simtel20.arpa by AOS.BRL.ARPA id a004470; 2 Oct 85 8:15 EDT Date: Monday, 30 September 1985 22:56-MDT Message-ID: Sender: David Roth From: David Roth To: w8sdz@SIMTEL20.ARPA Subject: Converting 8080/z80 to 'C'? ReSent-From: KPETERSEN@SIMTEL20.ARPA ReSent-To: Info-Cpm@BRL.ARPA ReSent-Date: Wed 2 Oct 1985 06:12-MDT Is there any easy way to convert 8080/Z80 asm. language to 'C'? Like some kind of translator or something? (I have a feeling I am wishing!) Thanks in advance. David A. Roth ...decvax!pur-ee!isrnix!pugsly Indianapolis,IN 2-Oct-85 07:44:26-MDT,780;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 2 Oct 85 07:44:19-MDT Received: from usc-eclb.arpa by AMSAA.ARPA id a006924; 2 Oct 85 8:41 EDT Date: 2 Oct 1985 05:42-PDT Sender: STANLEY@USC-ECLB.ARPA Subject: Compiler Patches From: STANLEY@USC-ECLB.ARPA To: info-cpm@AMSAA.ARPA Message-ID: <[USC-ECLB.ARPA] 2-Oct-85 05:42:32.STANLEY> I seem to remember reading about a short patch that enabled one to buy compoilers (such as FORTRAN & COBOL) written for the Heath 89/90 and run them on things like the Osborne, thus saving money since the Zenith product was cheaper. Trouble is, I can't find the original article. Anyone have any ideas or remembrances? Thanks. ...Dick Stanley 2-Oct-85 08:13:44-MDT,1004;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 2 Oct 85 08:13:33-MDT Received: from brl-aos.arpa by AMSAA.ARPA id a007081; 2 Oct 85 8:43 EDT Received: from xerox.arpa by AOS.BRL.ARPA id a005138; 2 Oct 85 8:38 EDT Received: from Muscat.ms by ArpaGateway.ms ; 02 OCT 85 05:35:08 PDT Date: Wed, 2 Oct 85 08:00 EDT From: Kushall.henr@XEROX.ARPA Subject: Re: D.R.C. S-100 RamDisk In-reply-to: "haar@gmr.CSNet.AG's message of Tue, 1 Oct 85 08:22 EST" To: haar%gmr.CSNet@CSNET-RELAY.ARPA cc: info-cpm@BRL.ARPA Message-ID: <851002-053508-1280@Xerox> I haven't used there RAM disk board, but have used other boards from them S-100 static RAM and ROM boards all with no problems, these boards seemed well designed and the PWB was of good quality. The instructions were good(I built mine from the bare boards) PS: Digital Research Computers brought out a single board computer called "Big Board", Xerox later based the 820 on this design. ED 2-Oct-85 09:24:06-MDT,8338;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 2 Oct 85 09:23:49-MDT Received: from xerox.arpa by AMSAA.ARPA id a010863; 2 Oct 85 10:39 EDT Received: from Salvador.ms by ArpaGateway.ms ; 02 OCT 85 07:42:36 PDT Sender: "Leonard A. Raye.EIS"@XEROX.ARPA Date: 2 Oct 85 07:40:00 PDT (Wednesday) Subject: 7000+ character tutorial on sending BREAK: From: towson@AMSAA.ARPA To: info-cpm@AMSAA.ARPA Message-ID: <851002-074236-1350@Xerox> GVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGV From: David Towson (SECAD) To: info-cpm@AMSAA.ARPA Subject: 7000+ character tutorial on sending BREAK: Return-Path: Redistributed: XeroxInfo-CPM^.wbst Received: from AMSAA (AMSAA.ARPA) by Xerox.ARPA ; 01 OCT 85 12:31:46 PDT GVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGV Fellow CP/Mers - In response to a recent request for information regarding how to send BREAK from a microcomputer, here is a 7000+ character tutorial on the subject. Sample code is included. The American Standard Code for Information Interchange (ASCII) defines a set of 128 characters that are encoded as the various combinations of seven bits. When this code is used over a serial asynchronous communications link, some additional bits are added to the seven ASCII bits to form the total "package" that is transmitted for each character sent. The term "asynchronous" means that the receiver doesn't know in advance when a character is coming. It just sits in an "idle" state until some special event signals the start of a new character. This idle state is caused by the presence of a steady logic-one signal at the receiver input, and it can last indefinitely. The "special event" that signals the beginning of a new character is a transition from the idle-state logic-one signal to a logic-zero which lasts for one bit-time, and is known as a "start-bit". A start-bit "wakes-up" the receiver, which then records in some sort of memory, typically a shift-register, the states of the next seven or eight bits. Whether seven or eight bits are recorded depends on whether "parity" is being used. Parity is a simple error detection scheme that, though easily deceived, is better than nothing. It is implemented by adding an extra bit (the eighth bit) to the existing seven ASCII bits such that the total number of logic-one bits in the eight-bit group is either odd or even, depending on whether "odd parity" or "even parity" is being used. For example, the ASCII representation for "A" is "1000001", which has an even number of 1's. Therefore, adding even parity results in "01000001", which still has an even number of 1's, whereas the odd parity representation is "11000001". After the start-bit and seven or eight "data-bits", the receiver expects to see a return to the logic-one state to signify the end of the character. This logic-one state lasts for at least one bit-time, and is known as a "stop-bit" (or bits). Typically, one stop-bit is used for all speeds greater than 110 baud, and two stop-bits are used at 110 baud and below. This convention derives from the mechanical roots of teleprinting, where the electro-mechanical devices used to decode and print the received characters needed time to stop quivering after each character before being ready to decode and print the next. To summarize then, an ASCII character sent via an asynchronous serial channel consists of one start-bit, seven or eight data-bits (depending on whether parity is being used), and one or two stop-bits (depending on the speed of transmission). This brings us (at last) to the BREAK signal. The BREAK signal has its roots at least as far back as the days of mechanical teleprinters, perhaps all the way back to electro-mechanical telegraphy. Early teleprinters used an electro-mechanical device called a "selector" to perform the decoding function now done electronically by devices such as the Universal Asynchronous Receiver Transmitter (UART). The start-bit caused a current flowing in the selector electro-magnet to cease, thereby releasing a clutch that set into motion a complex mechanical process that resulted in the printing of the received character. This process made a considerable noise, even when a non-printing character such as a space was received. If a steady logic-zero signal (no current in the selector magnet) was presented to the receiving teleprinter, the machine emitted a steady rhythmic clunking that was impossible to ignore. Consequently, the machines had a key labeled BREAK that merely opened the series DC circuit connecting all transmitters and receivers in the teleprinter network, thereby getting the attention of all operators. There was also a BELL character, but this had to be correctly decoded by a receiver in order to ring the bell, whereas the BREAK was a "non-character" that could be used to interrupt a transmission- in-progress, since it simply disrupted the whole network and made a lot of noise at each receiving teleprinter. Today, the BREAK signal performs a similar function in a similar manner. It is used now most often to gain the attention of a computer or other machine, rather than to alert a human operator. But it is still generated by sending a logic-zero signal of indeterminate length, although by convention some specific durations (typically in the 300 - 500 millisecond range) have been adopted. Modern electronic receiving circuits such as those whose names end with "ART" (as in UART) interpret the beginning of the BREAK as a start-bit followed by seven or eight logic-zero data-bits (the ASCII NUL character). But the expected stop-bit (return to logic-one state) is missing. This causes the receiving circuit to generate an error condition called "framing error", which is typically signaled by the setting of an error-bit in the status register of the receiving device. How the "user machine" responds to this condition is determined by the user-machine's software. The example to follow shows how a BREAK can be sent via software control of a 1602 UART. This device, which is typical of many such devices, has a command instruction that forces the output to a logic-zero state until the complementary instruction is issued. The code is taken from my MODEM7 overlay for the TRS-80 Model-I computer. All code not needed for this specific example has been deleted. ;..... ; RESETP: EQU 0E8H ;Reset port for UART. BAUDP: EQU 0E9H ;Data-rate port for UART. CONTROLP: EQU 0EAH ;Status/control port for UART. BRKMASK: EQU 0FBH ;And-mask to turn on break. ; ;..... ; ; ; UART initialization routine for TRS-80 Model I. ; TRSINIT: OUT RESETP ;Reset UART (data in A register is ;insignificant). MVI A,55H ;Use 55H for 300 baud. ;Use 77H for 1200 baud. OUT BAUDP ;Set UART data-rate. ; MVI A,0ECH ;Set UART for 8-bit word, ;no parity, no break and OUT CONTROLP ;DTR and RTS on. STA CONTROLB ;Save the UART control byte. RET ; ; ; ;..... ; ; CONTROLB: DB 0 ;UART control byte save. ; ; ;..... ; ; ; Routine to send a break-tone of approximately 300 ms duration. ; SENDBRK: PUSH B ;Save all double registers. PUSH D ; PUSH H ; LDA CONTROLB ;Get current UART control byte. ANI BRKMASK ;Change bit to turn on break. OUT CONTROLP ;Send new byte to control port. MVI B,3 ;Set count for timer. CALL TIMER ;Wait 300 milliseconds. LDA CONTROLB ;Restore original control byte OUT CONTROLP ;to turn off break. POP H ;Restore double registers. POP D ; POP B ; RET ; ; ; ;..... Note that the particular control-bytes needed to program the 1602 UART were determined from the 1602 data sheet. It is pointless to attempt writing this kind of code unless you have access to this kind of information. Many readers of info-cpm can help in this regard. Many other examples can be found in the overlay files on SIMTEL20 in directories PD: and PD:, available via FTP with login username "anonymous" and password "ftp" (or any other printing string). Dave 2-Oct-85 11:40:27-MDT,1193;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 2 Oct 85 11:40:11-MDT Received: from apg-1.arpa by AMSAA.ARPA id a015354; 2 Oct 85 13:09 EDT Date: Wed, 2 Oct 85 12:58:05 EDT From: Robert Bloom AMSTE-TOI 3775 Subject: Re: program to help WSTAR find overlays In-Reply-To: Your message of 2 Oct 1985 06:30-EDT To: ABN.ISCAMS@USC-ISID.ARPA Cc: info-cpm@AMSAA.ARPA David, Maybe your BDOS is not standard .... i.e. I do exactly what you say doesn't work - I have WS.COM, WSOVLY.COM and WSMSGS.ORVR in user 0 disk A. Now, any disk, any user can type 'WS' and expect to get WordStar (running the ZCPR2 patches also.) The 'r' command of WordStar doesn't work as you stated unless the target program is also marked public. Note that the WS internal search for overlay must have the proper drive where the overlays are located (label DEFDSK) I used to use the DUPUSR kludge but got burned by it from (my) carelessness. pubpatch is more 'elegant'. (All of this on a NorthStar Horizon w/352k running TSS/C, a multi-user CP/M system using one Z80 and bankswitching. [yes, it *is* slow at times!]) -bob 3-Oct-85 06:48:54-MDT,1747;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 3 Oct 85 06:48:45-MDT Received: from brl-tgr.arpa by AMSAA.ARPA id a023637; 3 Oct 85 7:56 EDT Received: from usenet by TGR.BRL.ARPA id a011597; 3 Oct 85 6:42 EDT From: Eric Hestenes Newsgroups: net.micro.cpm Subject: Re: Classified ads Message-ID: <991@sdcsla.UUCP> Date: 29 Sep 85 20:43:52 GMT To: info-cpm@AMSAA.ARPA > REF: Msg by Jack H. Smith on classified ads in mail. What exactly is an unwanted ad? Is it a For Sale ad, or is it a request for the latest version of MODEM ? Is it and ad that implies exchange of cash, or exchange of floppies? Is this group therefore just for technical info, and not a place to connect with other users? It seems silly to forbid most ads for personal entities ( not commmercial entities ) because they mostly involve give and take between legitimately interested parties. The primary assumption of the "personal" ad here is that the ad will be used on one occasion, e.g. to get rid of your cpm system. Abuses therefore include only those people who try to get rid of more than a few of an item ( "I've got 300,000 cpm systems to get rid of and a special rate for net people" ). the whole point of using the net is that it allows you to interact with people with a common interest. If you take out the common interest variable by placing the ad in a general-purpose mailing group, then you defeat this purpose. Ads that did not relate to cpm *would* be objectionable. eric [ these views are my own, not the views of my employer. ] arpanet: hestenes@nprdc.ARPA other: ucbvax!sdcsvax!sdcsla!hestenes or hestenes@sdcsla.UUCP 3-Oct-85 07:00:32-MDT,1362;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 3 Oct 85 07:00:26-MDT Received: from brl-tgr.arpa by AMSAA.ARPA id a023876; 3 Oct 85 8:03 EDT Received: from usenet by TGR.BRL.ARPA id a012915; 3 Oct 85 7:46 EDT From: amc543%uiucuxa.uiuc.arpa@BRL.ARPA Newsgroups: net.micro.cpm Subject: Two CP/M Computers for Sale Message-ID: <10100001@uiucuxa> Date: 27 Sep 85 16:43:00 GMT Nf-ID: #N:uiucuxa:10100001:000:788 Nf-From: uiucuxa.Uiuc.ARPA!amc543 Sep 27 11:43:00 1985 To: info-cpm@AMSAA.ARPA I have the following two computers for sale: 1) Kaypro 2X transportable 64k CP/M computer. 9" hi-res green monitor, two 5.25" floppy drives holding 390k each, excellent Selectric keyboard, WordStar, MailMerge, MBASIC, spreadsheets, and lots and lots of public domain software. The whole machine is one suitcase-like carryable package, like a Compaq. Includes 2 serial ports, 1 parallel port. Asking $900 or offer. 2) Epson Geneva battery-powered laptop computer with separate battery- powered 3.5" floppy drive included. 64k CP/M system with 80 x 8 display, runs all the regular CP/M software including Turbo Pascal and dBASE II. Includes WordStar, Portable Calc, Portable Scheduler, BASIC, more. Fantastic portable word processing system. $700. Aaron Contorer, (217) 332-4226. 3-Oct-85 08:39:52-MDT,1934;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 3 Oct 85 08:39:43-MDT Received: from mitre.arpa by AMSAA.ARPA id a026992; 3 Oct 85 10:01 EDT Received: by mitre.ARPA (4.12/4.7) id AA12747; Thu, 3 Oct 85 10:05:27 edt Message-Id: <8510031405.AA12747@mitre.ARPA> To: Eric Hestenes Cc: info-cpm@AMSAA.ARPA Subject: Re: Classified ads In-Reply-To: Your message of 29 Sep 85 20:43:52 GMT. <991@sdcsla.UUCP> Date: 03 Oct 85 10:03:04 EDT (Thu) From: Jeff Edelheit Eric - Since I started the discussion, I'd like to reply to your comments. There were several reasons for the establishment of the ARPANET. First, and foremost, was to develop the concept of packet switching. Once you could do that, it seemed that a logical use was to foster communications of technical issues between interested parties. Requests for help in bringing-up the latest version of a package (proprietary or public domain) is valid. Comments on the use of a proprietary object (software, hardware) are valid, as well, in my opinion, the experiences had with a commercial vendor (I have had a bad experience with XYZ, Inc). All of these topics allow for the passing of information between interested parties. I, for one, would like to know that if you buy a product from XYZ for either employment/research or personal-related work, the kind of support you might get from the vendor. The ARPANET was not intended for use as an advertising medium for either commercial concerns or individuals to sell goods and/or services. My comments are based on the idea that ARPANET is a DoD-funded activity, not funded and supported by the private sector. The above comments are strictly personal and do not reflect those of either my employer, DoD or any other government agency. Jeff Edelheit (edelheit@mitre.arpa) 3-Oct-85 11:50:23-MDT,666;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 3 Oct 85 11:50:18-MDT Received: from su-sushi.arpa by AMSAA.ARPA id a001030; 3 Oct 85 13:05 EDT Date: Thu 3 Oct 85 10:04:33-PDT From: Sam Hahn Subject: Re: Two CP/M Computers for Sale To: amc543%uiucuxa.uiuc.arpa@BRL.ARPA cc: info-cpm@AMSAA.ARPA In-Reply-To: Message from "amc543%uiucuxa.uiuc.arpa@BRL.ARPA" of Fri 27 Sep 85 16:43:00-PDT I may be interested in the Epson laptop. How can I find out about this machine, before I make a bid? -- Sam Hahn [Tried sending this directly, but got a "host unknown" message] ------- 3-Oct-85 13:03:56-MDT,1058;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 3 Oct 85 13:03:50-MDT Received: from brl-tgr.arpa by AMSAA.ARPA id a003845; 3 Oct 85 14:25 EDT Received: from usenet by TGR.BRL.ARPA id a026000; 3 Oct 85 14:09 EDT From: David Roth Newsgroups: net.micro.cbm,net.micro.cpm,net.wanted Subject: Wanted: Screen editor for CP/M on the C64. Message-ID: <575@isrnix.UUCP> Date: 30 Sep 85 16:17:58 GMT Xref: seismo net.micro.cbm:1810 net.micro.cpm:5058 net.wanted:7787 To: info-cpm@AMSAA.ARPA I have the CP/M option for my C64. I have used many CP/M systems in the past and have been spoiled by the use of screen editors. Does anyone know if any exists for the C64's CP/M option? ED is about to drive me up a wall. Anyone got WordStar working on it...like the WS for the apple using the Z80 card? Please reply by mail. Thanks in advance. David A. Roth ...decvax!pur-ee!isrnix!pugsly Indinapolis,IN 4-Oct-85 06:08:50-MDT,854;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 4 Oct 85 06:08:44-MDT Received: from sdcsvax.arpa by AMSAA.ARPA id a010753; 4 Oct 85 7:34 EDT Received: by sdcsvax.ARPA (5.5/4.41) id AA09354; Fri, 4 Oct 85 00:27:18 PDT hops=0 From: crash!kevinb@SDCSVAX.ARPA Message-Id: <8510040727.AA09354@sdcsvax.ARPA> Date: Thu, 3 Oct 85 22:46:06 PDT To: Info-CPM@AMSAA.ARPA Subject: CP/M 2.2 Autoload info needed I can get an autoload at cold and warm boot time, but am seeking a way to get a menu up at coldboot time only. How can I get my machine, an Advanced Digital Super Quad, to do this? my CCP starts at DC00, according to the PD program PROBE.COM. Thanks in advance, Kevin J. Belles - UUCP {ihnp4,cbosgd,sdcsvax,noscvax}crash!kevinb ~~~~~ ~~ ~~~~~~ - ARPA crash!kevinb@{ucsd,nosc}.ARPA 4-Oct-85 06:32:02-MDT,889;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 4 Oct 85 06:31:54-MDT Received: from xerox.arpa by AMSAA.ARPA id a011437; 4 Oct 85 7:50 EDT Received: from Muscat.ms by ArpaGateway.ms ; 04 OCT 85 04:52:46 PDT Date: Fri, 4 Oct 85 07:52 EDT From: Kushall.henr@XEROX.ARPA Subject: Re: Wanted: Screen editor for CP/M on the C64. In-reply-to: <575@isrnix.UUCP> To: David Roth cc: info-cpm@AMSAA.ARPA Message-ID: <851004-045246-3186@Xerox> This may sound silly, but TURBO PASCAL is available for the C64 CPM option. In fact TURBO-PASCAL is the only product ever offered for the C64 CPM option.(on the Commodore disk format) TURBO comes with a screen editor that mimics WS in the non-document mode. The editor works well and is fast. It is limited to files that can fit in memory. ED KUSHALL 4-Oct-85 07:09:54-MDT,675;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 4 Oct 85 07:09:50-MDT Received: from usc-isid.arpa by AMSAA.ARPA id a012295; 4 Oct 85 8:35 EDT Date: 4 Oct 1985 00:13-EDT Sender: ABN.ISCAMS@USC-ISID.ARPA Subject: Re: Two CP/M Computers for Sale From: ABN.ISCAMS@USC-ISID.ARPA To: amc543%uiucuxa.uiuc.arpa@BRL.ARPA Cc: info-cpm@AMSAA.ARPA Message-ID: <[USC-ISID.ARPA] 4-Oct-85 00:13:52.ABN.ISCAMS> In-Reply-To: <10100001@uiucuxa> Oh NOOOOOO.. Not right in the middle of our quarterly "Shall There Be Ads" feud... Is this salt in the wound or oil in the fire? Regards, David Kirschbaum ABN.ISCAMS@USC-ISID 4-Oct-85 07:12:35-MDT,1192;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 4 Oct 85 07:12:27-MDT Received: from usc-isid.arpa by AMSAA.ARPA id a012301; 4 Oct 85 8:36 EDT Date: 4 Oct 1985 00:19-EDT Sender: ABN.ISCAMS@USC-ISID.ARPA Subject: Re: Classified ads From: ABN.ISCAMS@USC-ISID.ARPA To: edelheit@MITRE.ARPA Cc: hestenes%sdcsla.uucp@BRL.ARPA, info-cpm@AMSAA.ARPA Message-ID: <[USC-ISID.ARPA] 4-Oct-85 00:19:22.ABN.ISCAMS> In-Reply-To: <8510031405.AA12747@mitre.ARPA> For what it's worth... I concur with Jeff's comments on inappropriateness of private or any other ads on the ARPANet. (I'm sure DoD is vastly reassured and encouraged by that.) But I would hate to lose the ties/links with those other nets that work with us on the ARPANet who DO permit these adds. Regrettably, some people's distribution schemas will shoot ads across to us .. a good application for AI maybe? To filter them out? Any messages with "FOR SALE", "CHEAP", "SUCH A DEAL"? Regards, David Kirschbaum ABN.ISCAMS@USC-ISID (and this net is my ONLY affiliation with the Govt except for my retirement check and income taxes, so no disclaimers are required.) 4-Oct-85 08:15:30-MDT,1409;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 4 Oct 85 08:15:14-MDT Date: Fri, 4 Oct 85 9:22:27 EDT From: David Towson (SECAD) To: info-cpm@AMSAA.ARPA Subject: Re: 7000+ character tutorial on sending BREAK: Fellow CP/Mers - I received the following note in response to my recently posted tutorial on sending BREAK over serial asynchronous links: From: (Richard Kenner) To: Subject: RE: 7000+ character tutorial on sending BREAK: Minor correction to your very good lesson on asynch for those who believe the world started with the microcomputer: The convention as I have always heard it is to default to 2 stop bits for baud rates 150 and below, not 110 and below. In field test versions of some DEC operating system (I think RSX, but am not sure), they also originally had 110 and changed it to 150 when I reported it to them. Thanks, Richard. Anybody know what hardware was originally responsible for the use of 150 baud? 110 baud was derived from a nominal rate of 10 characters-per-second, with 11 bits (one start, eight data and two stop) per character (10 x 11 = 110). 150 baud appears to be based on 15 characters-per- second with 10 bits (only one stop-bit) per character. Who made the first 15 cps printer? Dave 4-Oct-85 09:59:08-MDT,1489;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 4 Oct 85 09:59:00-MDT Received: from bbnccq.arpa by AMSAA.ARPA id a016530; 4 Oct 85 11:23 EDT Date: Fri, 4 Oct 85 11:10:42 EDT From: Bob Clements Subject: 150 baud terminals To: David Towson (SECAD) Cc: info-cpm@AMSAA.ARPA, clements@BBNCCQ.ARPA >> Anybody know what hardware was originally responsible for the >> use of 150 baud? ... Who made the first 15 cps printer? The first major printer at 150 baud (maybe the first of all, I don't know) was the Teletype model 37. Its mechanism was a lot like the model 35, but with a bigger type basket. It was Teletype's first machine with lower case letters. We used them on some of the early PDP-10 processors as consoles. [We = DEC engineering of about 1969.] And the person who corrected the tutorial by saying that 150 baud machines used two stop bits was wrong. The model 37 used one stop bit. I think the 37 was the only machine I ever saw that was fully mechanical at that speed. That is, the "UART" function (serial <--> parallel conversion) was mechanical, not electronic. It rattled its little heart out at a good clip, but couldn't really stand up to the effort. They didn't last long before wearing themselves out and dying. /Rcc ARPA: CLEMENTS@BBN.ARPA USENET: {ihnp4, decvax, ...}!bbncca!clements Ham Packet: K1BC Telco: 617-497-3612 4-Oct-85 11:02:58-MDT,1313;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 4 Oct 85 11:02:51-MDT Received: from dca-eur.arpa by AMSAA.ARPA id a019773; 4 Oct 85 12:20 EDT Date: 4 Oct 85 16:04:43 GMT From: bower@dca-eur.ARPA Subject: Re: 150 baud terminals To: clements@BBNCCQ.ARPA CC: info-cpm@AMSAA.ARPA Must strongly disagree with the statement that Model 37's wear out fast. I have one (currently in storage) that was the ONLY printer on my home system(s) for over 3 years, often printing large assembly listings lasting over 6 hours. As long as you gave them an annual oil change and lube, they will last almost indefinately. The one I have is set for 10 pitch, although I understand some were 12-pitch, and printed only 69 characters before inducing an automatic line feed. The 150 bps speed appears to be an early effort into the standard rates governed by the "75 times 2 to the nth" rule comprised of 75, 150, 300, 600, 1200...etc bit rates. One quirk on some Model 37s is that many had the MIL-STD-188C inter- faces which use a POSITIVE voltage for a logical "1" whereas RS-232 uses a NEGATIVE voltage for a logical "1". This means that an extra inverter is required when driving the device from commonly available interfaces. Hal 7-Oct-85 05:47:33-MDT,2712;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 7 Oct 85 05:47:25-MDT Received: from brl-tgr.arpa by AMSAA.ARPA id ab06693; 7 Oct 85 7:20 EDT Received: from usenet by TGR.BRL.ARPA id a006412; 3 Oct 85 23:59 EDT From: Ted Emigh Newsgroups: net.micro.cpm Subject: SCAN -- a program to look at text and squeezed files Message-ID: <512@ecsvax.UUCP> Date: 1 Oct 85 15:30:46 GMT To: info-cpm@AMSAA.ARPA SCAN Version 1.00 SCAN, based on the program BISHOW, is a program to view text and squeezed text files. It can be used to take quick looks at files without unsqueezing them or loading a large text editor, or to examine another file with the RUN command while in Wordstar. You can display the file in either direction, search for strings, or view only selected columns of the file. In function, it is identical to BISHOW Version 1.11 with two major additions the search function, and the ability to bishow a squeezed file. The program is written for Z80's only, and the addition of the unsqueezing routines has ballooned the program to just under 4K. The various commands for SCAN are: 1) Display the Next Page (Forward a Page) 2) Display the Previous Page (Back a Page) 3) Display the Next Line (Next Line) 4) Display the Previous Line (Back a Line) 5) Display the First Page (Top of File) 6) Display the Last Page (End of File) 7) Quit (End SCAN) 8) Set Screen Parameters 9) Search for a String of Characters Searching includes wild card characters, forward and backward search, and option to ignore upper/lower case. 10) Display Help As distributed, SCAN contains a small patch file (SCANPAT.ASM). This allow changing the various default parameters, as well as the commands and terminal characteristics. Look at this file for information about modifying SCAN. The distributed version of SCAN is configured for the standard command names and a "plain vanilla" CRT. This should work for most terminals. If you are interested in the program, please E-mail me a message. If there is enough interest, I will distribute it via net.sources, otherwise I'll E-mail it back to you. The normal distribution package includes SCAN.DOC, SCANPAT.ASM, AND SCAN.HEX. The sources is written in Zilog mnemonics and is not being distributed at this time. -- Ted H. Emigh Genetics and Statistics, North Carolina State U, Raleigh NC USENET: {akgua decvax duke ihnp4 unc}!mcnc!ecsvax!emigh ARPA: decvax!mcnc!ecsvax!emigh@BERKELEY BITNET: NEMIGH@TUCC 7-Oct-85 05:50:19-MDT,1290;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 7 Oct 85 05:50:13-MDT Received: from ucb-vax.arpa by AMSAA.ARPA id a006813; 7 Oct 85 7:21 EDT Received: by UCB-VAX (5.28/5.12) id AA04053; Sat, 5 Oct 85 15:10:31 PDT Message-Id: <8510052210.AA04053@UCB-VAX> Received: by ihnp4.ATT.UUCP id AA09824; 5 Oct 85 15:59:30 CDT (Sat) Received: by inuxc.ATT.UUCP, id AA01183; 5 Oct 85 15:57:41 EST (Sat) Date: Sat, 5 Oct 85 15:15:50 EST From: David Roth Received: by isrnix.UUCP; id AA29785; Sat, 5 Oct 85 15:15:50 EST To: iuvax!seismo!XEROX.ARPA@ucb-vax.ARPA, pugsly%isrnix.uucp@BRL.ARPA Subject: Re: Wanted: Screen editor for CP/M on the C64. Cc: info-cpm@AMSAA.ARPA No, I don't think that is silly at all. My main reason for wanting the editor is to avoid using ED to create and edit .ASM files. Does the editor with TURBO support .ASM and .TXT file type? I also got a copy of VDO.hex that Keith Petersen was nice enough to send me and I am going to try that out too. Have to dig out that program that lets you xfer files from C64 DOS<=>C64 CP/M. What does Turbo Pascal for the C64 CP/M cost? Thanks in advance. David A. Roth ...decvax!pur-ee!isrnix!pugsly Indianapolis,IN 7-Oct-85 08:13:40-MDT,652;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 7 Oct 85 08:13:32-MDT Received: from simtel20.arpa by AMSAA.ARPA id a007210; 7 Oct 85 7:33 EDT Date: Sat 5 Oct 85 05:19:59-MDT From: Jim Forrest Subject: Backup on VCR To: INFO-CPM@SIMTEL20.ARPA, INFO-MICRO@SIMTEL20.ARPA cc: JFORREST@SIMTEL20.ARPA Message-ID: <12148663178.11.JFORREST@SIMTEL20.ARPA> A friend of mine would like to know if there is a RELATIVELY "easy and inexpensive" way to back up the hard disk on his Kaypro 10 to his VCR. Appreciate response from anyone with expertise in this area. Jim ------- 7-Oct-85 08:18:04-MDT,1930;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 7 Oct 85 08:17:48-MDT Received: from brl-tgr.arpa by AMSAA.ARPA id a007859; 7 Oct 85 7:55 EDT Received: from usenet by TGR.BRL.ARPA id a009276; 5 Oct 85 23:44 EDT From: Chuck McManis Newsgroups: net.micro.cpm Subject: Re: D.R.C. S-100 RamDisk Message-ID: <110@intelca.UUCP> Date: 3 Oct 85 15:37:15 GMT To: info-cpm@AMSAA.ARPA [No amount of incanting will entice my mailer to accept your address so we go to plan B, the news route. ] > Have any of you used the 256K S-100 Solid State Disk Simulator (ramdisk) > from Digital Research Computers ? If so, I would like to hear your comments. > I am thinking about getting one since the price has dropped to less than $200. > > They provide BIOS code for CP/M 2.2. Does anyone have a CP/M Plus version? > Is it really S-100 (IEEE 696) compatible? Is it reliable? > > I would appreciate any advice on this product/company. > > thanks, > > Bob Haar I have dealt with Digital Research Computers (of Texas) a couple of times and had good results. The lab where I worked bought a bunch of their ZRT-80 boards to upgrade some otherwise scrap terminals. The only difficulty was in teaching them to handle a P.O. (they wanted to know how to "cash" it) The boards worked fine on power-up so I can't say how they would handle a service call. As for the RAM disk I keep seeing it and wondering if I should risk it. If you do get one please post your experiences with it to the net. --Chuck -- - - - D I S C L A I M E R - - - {ihnp4,fortune}!dual\ All opinions expressed herein are my {qantel,idi}-> !intelca!cem own and not those of my employer, my {ucbvax,hao}!hplabs/ friends, or my avocado plant. :-} 7-Oct-85 08:40:18-MDT,706;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 7 Oct 85 08:39:59-MDT Received: from brl-aos.arpa by AMSAA.ARPA id a008059; 7 Oct 85 7:59 EDT Received: from mit-mc.arpa by AOS.BRL.ARPA id a005519; 5 Oct 85 23:21 EDT Date: Sat, 5 Oct 85 23:20:50 EDT From: "Stephen C. Hill" Subject: CRC procedure needed To: INFO-MICRO@MIT-MC.ARPA, INFO-CPM@MIT-MC.ARPA, INFO-KERMIT@MIT-MC.ARPA cc: STEVEH@MIT-MC.ARPA Message-ID: <[MIT-MC.ARPA].669828.851005.STEVEH> Does anyone have a version of the CRC error checking algorithm in C or Pascal? I would like to put it in a version of KERMIT that I am writing for the State of Illinois. 7-Oct-85 08:40:59-MDT,780;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 7 Oct 85 08:40:49-MDT Received: from brl-tgr.arpa by AMSAA.ARPA id aa07859; 7 Oct 85 7:55 EDT Received: from usenet by TGR.BRL.ARPA id a013659; 6 Oct 85 2:44 EDT From: "Robert A. Dukelow" Newsgroups: net.micro.pc,net.micro.cpm Subject: Looking for WATFOR compiler Message-ID: <41@noscvax.UUCP> Date: 2 Oct 85 00:08:44 GMT Xref: seismo net.micro.pc:5942 net.micro.cpm:5065 To: info-cpm@AMSAA.ARPA Does anyone know if a compiler named WATFOR is available for either PC-DOS or CP/M? If so, where? My daughter is learning it in her high school class and would like to have it at home to make life easier. --Bob Dukelow (dukelow@nosc) 7-Oct-85 09:08:38-MDT,1066;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 7 Oct 85 09:08:27-MDT Received: from brl-tgr.arpa by AMSAA.ARPA id aa06837; 7 Oct 85 7:21 EDT Received: from usenet by TGR.BRL.ARPA id a002073; 4 Oct 85 20:14 EDT From: cindy%ada-uts.uucp@BRL.ARPA Newsgroups: net.micro.cpm Subject: Re: Orphaned Response Message-ID: <16800002@ada-uts.UUCP> Date: 2 Oct 85 17:40:00 GMT Nf-ID: #R:brl-tgr:-141400:ada-uts:16800002:177600:493 Nf-From: ada-uts!cindy Oct 2 13:40:00 1985 To: info-cpm@AMSAA.ARPA If you're talking about the MD-11 system from MORROW, there is a phone number for their California office (415) 430-1970. I called recently since I'm having trouble with my hard disk. For the Boston area the nearest official Morrow service place is near Nashua NH. They're Computer Data Services (or Systematic Solutions) (603) 673-7375 The Meeting Place Mall, Amherst, NH 03031. They might be able to help you. NET: {harpo, allegro, bellcore, ihnp4}!inmet!ada-uts!cindy ---------- 7-Oct-85 09:09:12-MDT,1007;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 7 Oct 85 09:09:05-MDT Received: from brl-aos.arpa by AMSAA.ARPA id a008068; 7 Oct 85 8:00 EDT Received: from simtel20.arpa by AOS.BRL.ARPA id a008650; 6 Oct 85 15:52 EDT Date: Saturday, 5 October 1985 22:34-MDT Message-ID: Sender: David Roth From: David Roth Subject: Commodore 64 CP/M problem ReSent-From: KPETERSEN@SIMTEL20.ARPA ReSent-To: Info-Cpm@BRL.ARPA ReSent-Date: Sun 6 Oct 1985 13:45-MDT I had my C64 replaced with a new one about a month ago. I didn't see any new changes in the new C64 but I guess there is since my C64 CP/M doesn't work now. Does anyone know why? I bought it in Nov. 83. Of course I might be stuck with it now, worst is that I can't run CP/M on my c64 now. David A. Roth ...decvax!pur-ee!isrnix!pugsly Indianapolis,IN 7-Oct-85 09:11:02-MDT,1555;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 7 Oct 85 09:10:55-MDT Received: from brl-tgr.arpa by AMSAA.ARPA id a006877; 7 Oct 85 7:22 EDT Received: from usenet by TGR.BRL.ARPA id a004184; 4 Oct 85 21:12 EDT From: jp@LANL.ARPA Newsgroups: net.micro.cpm Subject: Re: D.R.C. S-100 RamDisk Message-ID: <31283@lanl.ARPA> Date: 2 Oct 85 05:42:03 GMT To: info-cpm@AMSAA.ARPA I don't know about their RAM boards, but their ZRT-80 board is pretty good. I don't know if the same person that designed the ZRT-80 (Bill White) did the RAM boards or not. But, if so, the RAM boards are probably pretty solid. I have built three ZRT-80's from kits. It's not a problem for someone who has built similar boards before, but the manuals are definitely not in the same category as those from Heathkit. The instructions for the ZRT-80 kit are three pages long. One of the things I like about dealing with DRC is that, in the case of the ZRT-80 board, they make the software source code available on a disk for a reasonable price. Also, the manual includes a nice writeup on how to use it and how it works. My only beef is that they always quote 2 weeks delivery, and they mean it. I don't know if they sit on the orders for two weeks or if they are always two weeks behind, but they deinitely do not ship your order the next day. (maybe they are just very organized?) If DRC had something that I wanted I would definitely give them an order. Jim Potter jp@lanl.arpa 7-Oct-85 09:13:53-MDT,1338;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 7 Oct 85 09:13:45-MDT Received: from brl-tgr.arpa by AMSAA.ARPA id aa06877; 7 Oct 85 7:22 EDT Received: from usenet by TGR.BRL.ARPA id a006091; 4 Oct 85 22:02 EDT From: The Polymath Newsgroups: net.micro.cpm Subject: Re: wanna buy TurboPascal for CP/M-80 Message-ID: <738@ttidcc.UUCP> Date: 30 Sep 85 18:41:43 GMT To: info-cpm@AMSAA.ARPA In article <111@birtch.UUCP> oleg@birtch.UUCP (Oleg Kiselev x258) writes: >> Yes I know there's JRT, but was told that it can be worse than useless ...) > >You were told correctly. Some time ago when I worked for UCLA Extension >we bought JRT Pascal compiler for CPM2.2 on hp125. It stunk. Turbo Pascal >was WAY better. However, JRT had a new version of their compiler since >then. ... I've got it. It still stinks. I'm going to trash it and go with Turbo for my next project. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ The Polymath (aka: Jerry Hollombe) Citicorp(+)TTI Common Sense is what tells you that a ten 3100 Ocean Park Blvd. pound weight falls ten times as fast as a Santa Monica, CA 90405 one pound weight. (213) 450-9111, ext. 2483 {philabs,randvax,trwrb,vortex}!ttidca!ttidcc!hollombe 7-Oct-85 09:16:16-MDT,693;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 7 Oct 85 09:16:09-MDT Received: from mit-multics.arpa by AMSAA.ARPA id a007005; 7 Oct 85 7:27 EDT Date: Fri, 4 Oct 85 20:20 EDT From: "Paul E. Woodie" Subject: Osborne 1 Break To: info-cpm@AMSAA.ARPA Message-ID: <851005002032.238163@MIT-MULTICS.ARPA> Although I have not checked it out, I assume that the overlays for the MEX (and perhaps a few other ) modem program(s) for the O1 have the assembly code for implementing a "break" using the uart chip in the O1. These overlays can be found in the simtel20 archives: micro:. --Paul Woodie 7-Oct-85 09:52:49-MDT,13564;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 7 Oct 85 09:51:46-MDT Received: from brl-aos.arpa by AMSAA.ARPA id a007115; 7 Oct 85 7:31 EDT Received: from simtel20.arpa by AOS.BRL.ARPA id a003177; 5 Oct 85 12:03 EDT Date: 2 Oct 85 05:03:34 GMT Message-ID: Sender: "Ian D. Allen" From: "Ian D. Allen" Newsgroups: net.dcom Subject: Description and Review of USR Courier 2400 bps modem Organization: University of Waterloo ReSent-From: KPETERSEN@SIMTEL20.ARPA ReSent-To: Info-Cpm@BRL.ARPA ReSent-Date: Sat 5 Oct 1985 10:01-MDT Product description, evaluation, and bug report: US Robotics Modem Courier 2400 (FCC CJE794) Ser. #30-05816 ROM set #242 Bell 103/113 Bell 212-A CCITT V.22bis compatible (300/1200/2400 bps) Approved by DOC Communications Canada 550 1169 A Ringer Equivalence: 0.4 Canadian Modem Load Number 36B Warranty: Two years. Description: - plastic case; help summary printed on the bottom; connections via rear - on-line help screens for everything (AT$ ATS$ ATD$) - all current modem settings displayable in an on-line table - internal speaker; slide volume-control on right side of unit - records duration of call, or use timer as real-time clock - detailed call progress result codes (e.g. BUSY, RINGING, VOICE) - automatically repeat-dial a busy line up to 10 times - ability to dial alphabetic phone numbers, e.g. 1-800-DIAL USR - outgoing baud rate set automatically according to terminal baud rate - automatic switch from 2400 to 1200 if called modem is 1200 - optional adaptive DTMF (Touch Tone) dialling - optionally uses DTMF if line can handle it, otherwise uses pulse - two RJ11C jacks; one for wall and one for phone - can dial-out with Answer instead of Originate tones - can toggle switch hook, e.g. to transfer a call - can wait for second dial tone - can wait for "answer" - silence after a ring - optional fast dial-tone detect - Morse Code capability - 1270Hz tone 62ms dot 186ms dash Result Codes: OK CONNECT CONNECT 1200 CONNECT 2400 RING RINGING BUSY VOICE ERROR NO CARRIER NO ANSWER NO DIAL TONE 'AT' Command set: $ HELP Command Reference Screen (this list) S$ HELP S-register Reference Screen D$ HELP Dial Reference Screen A Force answer mode A/ Repeat last command AT Prefix Cn n=0 Transmitter OFF (modem becomes receive-only) n=1 Transmitter ON (normal operation) Ds Dial telephone number s=0..9#* @WTPR,;"! En n=0 No echo of commands n=1 Echo commands to screen Fn n=0 Half Duplex-local echo n=1 Full Duplex-no local echo Hn n=0 Hang up n=1 Go off-hook In n=0 Show product code n=1 Do checksum n=2 RAM test n=3 Call duration/Clock I3=s Set Clock s=Hours:Min:Sec n=4 Show current modem settings Kn n=0 Call Duration mode n=1 Real Time Clock mode Mn n=0 Speaker OFF n=1 Speaker ON until Carrier n=2 Speaker always ON n=3 Speaker OFF during Dial O Return on-line after command Qn n=0 Show result codes n=1 Suppress result codes Sr=n Set register "r" to "n" Sr? Query register "r" (see also I4) Vn n=0 Numeric result codes n=1 Verbal result codes Xn n=0 Standard result codes set (Hayes X0) n=1 Extended (1200) result code set (Hayes X1) n=2..6 Advanced result code sets Z Software reset and reading of DIP switches > Repeat command until cancelled; repeat Dial at most 10 times S-Register Functions (can be set to 1..255): S0 Number of rings before answering S1 Counts number of rings S2 Set Escape-Code character S3 Set Carriage-Return character S4 Set Line-Feed character S5 Set Backspace character S6 Set Dial Tone wait time (seconds) S7 Set Carrier wait time (seconds) S8 Set Comma and Repeat pause time (seconds) S9 Set Carrier Detect recognition time (1/10 seconds) S10 Set Carrier Loss/Hang-up time (1/10 seconds) S11 Set Touch-Tone spacing (milliseconds) S12 Set Escape-Code guard time (1/50 seconds) S14 Smartcom 2.0 kludge to pretend modem is 1200 bps S16 0 = Data Mode 1 = Analog Loopback 2 = Dial Test 4 = Test Pattern 4 = Analog Loopback and Test Pattern Dip Switches: - DTR (pin 20) normal / DTR always on - Verbal result codes / Numeric result codes - Suppress result codes / Display result codes - Echo off-line commands / Don't echo off-line commands - Auto-answer on Ring / Suppress auto-answer - Normal Carrier-Detect (pin 8) / Carrier-Detect always ON - Single phone connection RJ11 / Multiple phone connection RJ12/RJ13 - Disable AT command set / Enable AT command set - Disconnect with +++ / Can go back on-line after +++ - Reserved - Pins 2 and 3 standard / Reverse pins 2 and 3 LED front-panel: - High Speed (2400 bps communication) - Auto Answer; Answer mode - Carrier Detect - Off Hook - Receive Data - Send Data - Terminal Ready (DTR from terminal or with DTR over-ride ON) - Modem Ready; Power - Analog Loopback (self-test mode) Initial Performance: No errors during 10 hours at 2400 bps from home (1 crow mile from UofW) into some 2400 bps modem (make unknown) attached to Sytek network at UofW. No errors when using the Courier to dial out from MATH into the Sytek at 2400bps and then logging back into MATH again. Many errors on MATH end during two of several 1200 bps calls into WATMATH ttyd0 (Gandalf/Cermetek SAM 212A modem). The errors were always BREAK followed by a "{". Unlike the Hayes 1200 modem I normally use, taking an extension phone off the hook at 1200bps made the MATH errors much worse rather than better. (The Hayes 1200 is virtually error-free with the phone off the hook at 1200bps.) Calling in to MATH and ROSE modems (Gandalf/Cermetek SAM 212A modems) produced lots and lots of noise when I tried calling out and back in using the Courier at 1200bps. Using the Courier to call in to WATCGL, WATDAISY, and WATMUM (Vadic 3451 modems) showed no noise. As I said, at 2400bps, calling out from MATH into the unknown 2400 bps modem using the Courier showed no noise at all. UUCP Our byte rate to ihnp4 in Chigago is usually about 70-90 bytes/sec at 1200 bps; using the 2400 bps Courier changed that up to about 145 bytes/sec. Looking at the amount of illumination of the send/receive data LEDs, I get the feeling that the limiting factor is still the load on ihnp4, not the speed or quality of the line or modem. ihnp4 would not respond for long periods of time; this would often cause our end to time out. I babysat the modem and kept calling back whenever this happened. ihnp4 has an ARK 2400 bps modem inbound, and uses a Concord outbound. In town here, we do a maximum of 110 bytes/sec at 1200 bps; using the Courier upped that to about 215 bytes/sec. If they ever start charging for local calls, the higher speed will be useful. Calling utzoo in Toronto, our 1200 bps byte rate is about 109 bytes/sec. I tried to use the Courier into their 2400 bps modems (they have a Racal-Vadic 2400PA), but the noise on the line usually prevented the login from succeeding. In the rare cases where it did succeed, the error rate was so high that the byte rate was only 24 bytes/sec, with so many timeouts that the overall rate was less than half that. 1200 bps on the same line, a UofW FX Toronto line, worked just fine. I tried avoiding the FX line and just dialling long distance and got about the same error rate, so I don't think it's the FX line that's awful. (After all, we call ihnp4 at 1200 and 2400 bps using the same set-up with much better results.) I put the Courier onto its own dedicated phone line, getting it off the UofW SL-1 extension altogether, and called utzoo again. Byte rate went up to 150 bytes/sec, provided I could get logged in. Still lots of noise on the line. I called linus (Boston), who have Concord Data 2400 bps modems, and noticed no noise on the line during the brief call there. I sent them /etc/termcap (74355 bytes) and got a byte rate of 210 bytes/sec. (Very Nice!) I called utai (Toronto) briefly, and noticed no noise there either. (No uucp account, so I couldn't send anything.) To sum up: it seems the University's SL-1 switch might be damaging communications a bit. Regardless of that, the Courier just doesn't like talking to the Vadic at utzoo at 2400 bps no matter what line I use. The Courier calls all four other 2400 bps modems I know of okay. henry@utzoo says their 2400 bps calls to linus average over 200 bytes/sec both ways; we seem to do the same to linus, but can't talk to utzoo. Just shows that things that can talk to the same thing can't necessarily talk to each other! Observed Quirks with this modem: If you are connected to something at 2400bps, you use +++ to get back to the command mode, you display and *interrupt* a HELP menu, then go back on line, you get lots of repeating junk on your screen. You have to use +++ to go off-line again, display a HELP menu *without interruption*, then go back on line. If you try the same thing at 1200bps, you get *no* junk if you interrupt the HELP menu and go back on line, and you get the repeating junk if you let it finish and go back on line! At 1200 bps, I had the modem hang three times when this junk started appearing. When the junk is printing, the Receive Data light is flashing madly and pulling out the phone cord gives an immediate NO CARRIER. When the modem hung, the RD light went out, the SD light would flash when characters were typed, but nothing appeared on the screen and +++ and AT had no effect. Pulling out the phone cord did not affect the hung modem; it just did not respond to anything and I had to power down every time. Looks like you'd better not need any on-line help screens in the middle of a session. We took the modem to a country exchange, long distance to UofW, and saw the same sort of junk appear when we tried calling the unknown 2400 bps modem at UofW. The 2400 would answer, signal 2400 bps, and the Courier would respond with CONNECT 1200 (!?) and then lots of incessant junk. We usually had to power off the modem to get it back. The incessant junk looked the same as the junk that kept spewing out in the above- mentioned help-menu bug. It's almost as if the answering modem were sending a 2400 bps carrier that the Courier was mis-interpreting at 1200 bps, resulting in a continuous stream of junk. Actually using the Courier to call out at 1200 bps on the same country line worked just fine. Nothing I tried could get the modem to recognize my VOICE in the extended result code set. I set parameter X6 and phoned from my home line to my data line and answered the phone myself - the Courier said RINGING and then eventually NO CARRIER, no matter what I said into the phone. A friend tried the same thing and yelled a few times into the phone, and it recognized his voice as VOICE. I picked up my extension phone, dialed a '5' to get rid of the dial tone, and then told the Courier to dial a number on the same line. If I said nothing, it would correctly detect NO DIAL TONE. If I talked while it came off-hook, it would usually mistake my voice for a dial tone, dial the number into my voice, and then say either BUSY or RINGING followed eventually by NO CARRIER. Register S10 (timer for loss of carrier) claims to be scaled in tenth- seconds, but setting it to 254 and unplugging the telephone cable causes carrier loss after only a second or two, not 25 seconds. Setting S10 to 255 and unplugging the cable hangs the modem. It gets stuck off-hook with the CD light on, and refuses to respond to anything except power-off, even with the cable plugged in again. The manual says you can type the command set in upper or lower case. What it doesn't say is that both letters of the AT prefix must be the *same* case -- "AT" and "at" work; "aT" and "At" do not. "A/" repeats the last command, and the last command is cleared the instant the letters AT appear, so if you intended to repeat the last command but type AT followed by backspace followed by /, it's too late. Backspace only deletes command chars, not the prefix itself. This is a "feature" of Hayes modems, too. The "guard band" register (S12) behaves a bit non-intuitively when set to small values. Not only does the guard band decrease, but the length of time in which you have to type all three "+"s goes down too! At small settings, you have to use the repeat key to get it fast enough. At the smallest settings, I think you're required to type the "+"s faster than the baud rate will allow... Summary: I could have put up with the help-menu problem if I hadn't also tripped over similar junk when using the modem in the country. Looks like the modem's state transition diagram has a loophole. UofW needs a modem that can talk 2400 bps to utzoo in Toronto, ideally using the cheap FX line through the UofW SL-1 exchange, and this one can't do that very well. (In fact the ratio of line costs, FX versus using DDD on a private line, is almost exactly the ratio of byte rates, meaning we save no money going to 2400 bps on the DDD line instead of using 1200 bps on the FX line.) -IAN 7-Oct-85 13:10:28-MDT,789;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 7 Oct 85 13:10:20-MDT Received: from xerox.arpa by AMSAA.ARPA id a020627; 7 Oct 85 14:39 EDT Received: from Muscat.ms by ArpaGateway.ms ; 07 OCT 85 10:57:32 PDT Date: Mon, 7 Oct 85 13:01 EDT From: Kushall.henr@XEROX.ARPA Subject: Re: Looking for WATFOR compiler In-reply-to: <41@noscvax.UUCP> To: "Robert A. Dukelow" cc: info-cpm@AMSAA.ARPA Message-ID: <851007-105732-1146@Xerox> WATFOR stands for WATerlooFORtran and is an interactive Fortran interputer. It was developed by Waterloo University in Canada. The first machine to use it was the Commadore 9000 (Super PET). I don't know if ever was made available for any other machines. Ed 7-Oct-85 13:38:00-MDT,1410;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 7 Oct 85 13:37:53-MDT Received: from xerox.arpa by AMSAA.ARPA id a020651; 7 Oct 85 14:40 EDT Received: from Muscat.ms by ArpaGateway.ms ; 07 OCT 85 10:58:00 PDT Date: Mon, 7 Oct 85 13:15 EDT From: Kushall.henr@Xerox.ARPA Subject: Re: Wanted: Screen editor for CP/M on the C64. In-reply-to: <8510052210.AA04053@UCB-VAX> To: David Roth cc: iuvax!seismo!XEROX.ARPA@ucb-vax.ARPA, pugsly%isrnix.uucp@BRL.ARPA, info-cpm@AMSAA.ARPA Message-ID: <851007-105800-1147@Xerox> David: To the best of my knowledge there is nothing unique about .ASM and .TXT files, that is they are sequential ASCII text files. Using the TURBO-PASCAL etitor you can give a file any name and extension that is a legal CP/M file name. Thus you should be able te create and edit .ASM and .TXT files with out any problems. In fact the TURBO editor can make a file of the type NAME.COM but CP/M won't like it! The only restriction is the file size is <62K (the manual says 64K) and the file must fit in available memory, thus on CP/M 80 systems the file size will be much less than 62K by the size of TURBO and the resident CP/M RAM space. When you do a save from the TURBO editor the existing file NAME.EXT is renamed NAME.BAK and a new NAME.EXT file is created. Ed Kushall 7-Oct-85 13:59:31-MDT,1228;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 7 Oct 85 13:59:22-MDT Received: from brl-tgr.arpa by AMSAA.ARPA id a020716; 7 Oct 85 14:42 EDT Received: from usenet by TGR.BRL.ARPA id a026304; 7 Oct 85 13:53 EDT From: jp@LANL.ARPA Newsgroups: net.micro,net.micro.cpm,net.micro.pc,net.lang.pascal,net.sources Subject: SoftWare Tools in Pascal posted to net.sources Message-ID: <31464@lanl.ARPA> Date: 6 Oct 85 04:54:04 GMT Xref: seismo net.micro:12947 net.micro.cpm:5079 net.micro.pc:5951 net.lang.pascal:383 net.sources:3605 To: info-cpm@AMSAA.ARPA I have received several requests for copies of Software Tools in Pascal that I recently received by e-mail. Since some of the requests were from sources that our mailer has been unable to find a return path I am posting the Software Tools in Pascal to net.sources. I am interested in adapting the Tools to run under Turbo Pascal. If anyone else is interested in pursuing this, as a least one person has indicated, please contact me and perhaps we can share the task. Jim Potter jp@lanl.arpa (505) 667-9615 work 843-9615 work - FTS (505) 6625804 home 7-Oct-85 14:28:57-MDT,1348;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 7 Oct 85 14:28:49-MDT Received: from xerox.arpa by AMSAA.ARPA id a022211; 7 Oct 85 15:12 EDT Received: from CheninBlanc.ms by ArpaGateway.ms ; 07 OCT 85 11:58:56 PDT Date: 7 Oct 85 10:48:26 PDT (Monday) From: Bicer.ES@XEROX.ARPA Subject: IBM <==> Compupro/Viasyn To: INFO-IBMPC@USC-ISIB.ARPA cc: XeroxInfoIBMPc^.ES@XEROX.ARPA, info-cpm@AMSAA.ARPA, Bicer.ES@XEROX.ARPA, WantAds^.ES@XEROX.ARPA, info-micro@BRL-VGR.ARPA Reply-To: Bicer.ES@XEROX.ARPA Message-ID: <851007-115856-1256@Xerox> Hi, Recently, I have started programming on an IBM PC, and have the following problem: I have a Compupro/Viasyn 816 at home, which is an S-100 machine. For my work, I need an IBM PC compatible system. I know that I can buy a PC board, more memory and a hard disk for my system, but the price tag is too high. So, what I'd like to find out is: 1- Is there a cheaper way to convert a Compupro into an IBM PC compatible machine? 2- Is it possible to trade in or exchange my sytem for a PC or a compatible? 3- If possible, what steps should I take to sell my system? I need to resolve this issue as quickly as possible, so please, any info will be greatly appreciated. Thanks in advance, Jack Bicer Bicer.ES@XEROX.ARPA 8-Oct-85 05:49:46-MDT,2580;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 8 Oct 85 05:49:38-MDT Received: from brl-tgr.arpa by AMSAA.ARPA id a000922; 8 Oct 85 7:23 EDT Received: from usenet by TGR.BRL.ARPA id a016157; 8 Oct 85 2:51 EDT From: "G.PECKHAM" Newsgroups: net.micro.cpm Subject: Computer for Sale Message-ID: <376@hounx.UUCP> Date: 7 Oct 85 14:41:19 GMT To: info-cpm@AMSAA.ARPA I am selling a Zenith Z90 computer system for $2000. In addition to being a good CPM machine, the system is great for experimenting. The Zenith manuals detail everything both hardware and software. TOTAL PACKAGE PRICE: $1500 ************************************** The System includes the following and more: (Original) ITEM Retail Price Hardware: Zenith Z90 computer $ 3195.00 64k ram 2 - 5.25" hard sectored drive (100k) 1 - 5.25" soft sectored drive (620k) dbl. sided, dbl. density 1 - 10 Meg.byte Winchester drive 2495.00 approx. 80 diskettes 240.00 Software: Operating Systems - CPM 80 150.00 HDOS 150.00 ZCPR2 public domain, unix like system nc Languages - C - Whitesmith's 630.00 Plink II (linker for above) 350.00 Mbasic 80 interpreter 175.00 Mbasic 80 compiler 250.00 Cbasic 150.00 Fortran 80 195.00 Cobol 80 395.00 USCD Pascal 395.00 Mac 80 85.00 Database systems - FMS/80 995.00 Dbase II 700.00 Datastar 295.00 Word Processing - Wordstar 395.00 Magic Wand 295.00 Spreadsheet - Supercalc 295.00 Accounting Pkgs. - Accounting Plus G/L, A/R, A/P, Payroll 1900.00 Peachtree G/L, A/P 790.00 Demo pkgs. for sales support - Accounting Plus G/L, A/R, A/P, Payroll, 175.00 Sales Order, Purchase Order, Inventory, Point of Sale. Professional Time Acctg. 60.00 PK Attorney Time & Billing 75.00 DAGAR's Pharmacy System 125.00 Misc. - all types of games, disk utilities, - etc. ____________ TOTAL retail value $14,955.00 I am selling this all as a pkg. for $1500.00 The system is in mint condition and works perfectly. The system is 2.5 yrs old. If you are interested please send me mail or call me. Home number (201) 367-1688, Work number (201) 949-1831. Gary Peckham N.J. hounx!gtp or houxf!hounx!gtp or ihnp4!hounx!gtp 8-Oct-85 06:55:56-MDT,1170;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 8 Oct 85 06:55:50-MDT Received: from uci-icsc.arpa by AMSAA.ARPA id a003042; 8 Oct 85 8:18 EDT Received: from localhost by UCI-ICSC.ARPA id a017223; 7 Oct 85 15:04 PDT To: Kushall.henr@XEROX.ARPA cc: "Robert A. Dukelow" , info-cpm@AMSAA.ARPA, young@UCI-ICSC.ARPA Subject: Re: Looking for WATFOR compiler In-reply-to: Your message of Mon, 7 Oct 85 13:01 EDT. <851007-105732-1146@Xerox> Date: 07 Oct 85 15:02:56 PDT (Mon) From: Michal Young WATFOR was NOT first implemented on the SuperPET. It's immediate successor, WATFIV, is mentioned in the 1979 edition of the dragon book (Aho and Ullman), so WATFOR was around a long time before SuperPET. The version I am aware of was available on IBM mainframes and was not an interpreter; it was a very fast compiler optimized for handling multiple compiles submitted in a batch. It was specially designed for student use, concentrating on quick compile and good error checking rather than optimized object code. --Michal Young, young@uci 8-Oct-85 07:18:30-MDT,565;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 8 Oct 85 07:18:26-MDT Received: from brl-vat.arpa by AMSAA.ARPA id a004080; 8 Oct 85 8:39 EDT Date: Tue, 8 Oct 85 8:40:21 EDT From: Earl Weaver (VLD/ASB) To: Kushall.henr@XEROX.ARPA cc: "Robert A. Dukelow" , info-cpm@AMSAA.ARPA Subject: Re: Looking for WATFOR compiler I used WATFOR/WATFIV back in '72 on U of Mich's IBM 360/67. Presumably that predates the "Commadore 9000 (Super PET)." 8-Oct-85 08:14:54-MDT,1273;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 8 Oct 85 08:14:28-MDT Received: from brl-aos.arpa by AMSAA.ARPA id a007810; 8 Oct 85 9:40 EDT Received: from mit-mc.arpa by AOS.BRL.ARPA id a008615; 8 Oct 85 9:37 EDT Received: from Xerox.ARPA by MIT-MC.ARPA 8 Oct 85 09:33:22 EDT Received: from Muscat.ms by ArpaGateway.ms ; 08 OCT 85 06:31:05 PDT Date: Tue, 8 Oct 85 09:30 EDT From: Kushall.henr@XEROX.ARPA Subject: Re: CRC procedure needed In-reply-to: <[MIT-MC.ARPA].669828.851005.STEVEH> To: "Stephen C. Hill" cc: INFO-MICRO@MIT-MC.ARPA, INFO-CPM@MIT-MC.ARPA, INFO-KERMIT@MIT-MC.ARPA Message-ID: <851008-063105-1948@Xerox> Steven: There was a very good article that included this in the June 85 Dr. Dobbs Journal. The article title is "Christensen Protocols in C" by Donald Krantz. The article starts on P66 and there is a special section on CRC on p.68. This CRC is based on the CCITT polynomial X^16+X^12+X^5+1 (Someone must know what that means). The Source Code in C for the entire XFR communications package can be downloaded from the TCOG BBS (612) 724-7779 @300/1200 baud Perhaps this article and code can help you with a KERMIT version of CRC. Ed Kushall 8-Oct-85 12:54:42-MDT,1430;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 8 Oct 85 12:54:21-MDT Received: from brl-tgr.arpa by AMSAA.ARPA id a016139; 8 Oct 85 14:02 EDT Received: from usenet by TGR.BRL.ARPA id a002097; 8 Oct 85 13:50 EDT From: "Colin Campbell [DCS]" Newsgroups: net.micro.pc,net.micro.cpm Subject: Re: Looking for WATFOR compiler Message-ID: <1724@watdcsu.UUCP> Date: 7 Oct 85 15:13:53 GMT Xref: seismo net.micro.pc:5960 net.micro.cpm:5087 To: info-cpm@AMSAA.ARPA > Does anyone know if a compiler named WATFOR is available for either > PC-DOS or CP/M? If so, where? My daughter is learning it in her high > school class and would like to have it at home to make life easier. > --Bob Dukelow (dukelow@nosc) WATFOR77 is available for PC-DOS from: WATCOM Products Inc 415 Phillip Street Waterloo, Ontario, Canada N2L 3X2 (519) 886-3700 Telex 06-955 458 It is available for other systems, too (e.g. IBM VM/CMS), but I don't think it runs under CP/M. It supports the full FORTRAN 77 standard. Your daugther may be using WATFOR on a DEC mini in which case I believe it would be a FORTRAN 66 compiler (from the same people). (btw WATCOM Products markets software developed by the WATCOM Group, as well as software developed at the University of Waterloo - where I am employed.) 8-Oct-85 13:18:08-MDT,1665;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 8 Oct 85 13:17:50-MDT Received: from brl-aos.arpa by AMSAA.ARPA id a017023; 8 Oct 85 14:22 EDT Received: from mit-mc.arpa by AOS.BRL.ARPA id a019023; 8 Oct 85 13:54 EDT Received: from isi-vaxa.ARPA by MIT-MC.ARPA 8 Oct 85 13:49:00 EDT Received: by isi-vaxa.ARPA (4.12/4.7) id AA17910; Tue, 8 Oct 85 10:09:14 pdt Message-Id: <8510081709.AA17910@isi-vaxa.ARPA> Date: 8 Oct 1985 1009-PDT (Tuesday) To: "Stephen C. Hill" From: berman@ISI-VAXA.ARPA Cc: INFO-MICRO@MIT-MC.ARPA, INFO-CPM@MIT-MC.ARPA, INFO-KERMIT@MIT-MC.ARPA > Steven: > There was a very good article that included this in the June 85 Dr. > Dobbs Journal. The article title is "Christensen Protocols in C" by > Donald Krantz. > The article starts on P66 and there is a special section on CRC on p.68. > This CRC is based on the CCITT polynomial X^16+X^12+X^5+1 (Someone must > know what that means). > The Source Code in C for the entire XFR communications package can be > downloaded from the TCOG BBS (612) 724-7779 @300/1200 baud > Perhaps this article and code can help you with a KERMIT version of CRC. > Ed Kushall Warning: I just implemented CRC from this article, and it is vague in one serious point: It says simply that the CRC is generated by running "each byte of the packet" through the generator. In Christensen protocol, this would normally include the header info, as when calculating checksum, but (at least in Christensen) for CRC you only want the actual data bytes to be CRC'd. Note: Your mileage may differ. RB 9-Oct-85 06:07:03-MDT,935;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 9 Oct 85 06:06:55-MDT Received: from wiscvm.arpa by AMSAA.ARPA id a025439; 9 Oct 85 7:22 EDT Received: from (MAILER)UCF1VM.BITNET by WISCVM.ARPA on 10/08/85 at 22:10:56 CDT Return-path: WOODRUFF%UCF1VM.BITNET@WISCVM.ARPA Received: by UCF1VM (Mailer X1.21) id 7340; Tue, 08 Oct 85 22:32:32 EST Date: Tue, 8 Oct 85 22:27 EST From: Mark Subject: CRC checking and more To: INFO-CPM@AMSAA.ARPA MMDF-Warning: Parse error in preceding line at AMSAA.ARPA A recent issue of Dr. Dobbs Journal (was it August? September?) contained a good example of CRC checking. Dr. Dobbs' frequently publishes interesting things for CP/M programmers. Check it out. Regards, Mark. P.S. Does anyone know why the "==" line of mail files is 73 characters long by default? 9-Oct-85 06:32:29-MDT,4607;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 9 Oct 85 06:32:15-MDT Received: from mit-mc.arpa by AMSAA.ARPA id aa25442; 9 Oct 85 7:24 EDT Date: Wed, 9 Oct 85 05:49:29 EDT From: "Paul R. Grupp" Subject: CRC in C (Nov 83 rerun) To: info-cpm@AMSAA.ARPA Message-ID: <[MIT-MC.ARPA].673383.851009.GRUPP> Someone recently asked for CRC code in C but I've forgotten who. So here it is again. Date: 9 Nov 83 5:35:04-PST (Wed) From: harpo!floyd!clyde!burl!hou3c!hocda!machaids!djj at ucb-vax About a month ago I put a request for CRC (Cyclic Redundancy Codes) information on this net. I received in a number of good programs and comments, and several requests to forward whatever I discovered. Since I have not been able send mail to several of the people who made requests, I'll put this summary on the net. It appears that CRC calculations are based on a polynomial that is not standardized, so it is possible to have several different valid CRC values for the same file simply by using different polynomials. There is an article in the June 83 issue of IEEE Micro which gives a little background on CRC and on a method for calculating same. Unfortunately, the examples are given in assembler. One of the C programs I received, and modified slightly produces CRC values identical to those produced by CRCK.COM and "uc" the UNIX/CPM communications program that is intended to replace "umodem". Here is the source code ---- "crck.c" (118 lines; 493 words; 2874 bytes): /* * ---- crck.c ---- * * Version 1.0 - 4/9/83 * * This UN*X program performs a file hashsum calculation consistent * with the de facto standard (but misnamed) "CRCK" program for CP/M. * * Usage: crck [-w] filename... * * The -w flag suppresses the warning message that normally * is printed when a file is found not to be a multiple of * 128 bytes in size. (Such a file cannot be a faithful copy * of a CP/M file, since CP/M files are always a multiple of * 128 bytes). * * Notes: * 1. Two versions of the CRCK program exist in the CP/M * world. Variants of Keith Petersen's original program * are the de facto standard, even though they misuse the * underlying CRC calculation subroutine and therefore don't * really perform a "CRC" function. This program produces * hashsums consistent with Petersen's scheme, currently * found in the "CRCK4x.ASM" series. * * 2. In order for valid comparisons to be made between the * CP/M and UNIX copies of a file, the file must, of course, * have been transferred intact; i.e., with the "-rb" option * of umodem, or the "-b" option of rb. * * Jeff Martin * Naperville, Il. * 4/9/83 * Version 1.1 -- djj Oct 13, 1983 * Changed output print format, to make it more readable! * Don Jackowski, Mine Hill, NJ */ #include #include #define CPMSEC 128 main(argc, argv) int argc; char *argv[]; { int c, fdi, warn, wflg; char *s, *in_file; char cbuf[CPMSEC]; unsigned crc, crck(); warn = 1; while (--argc > 0 && (*++argv)[0] == '-') { for (s = argv[0]+1; *s != '\0'; s++) { switch (*s) { case 'w': warn = 0; break; default: printf("illegal option: '%c'\n", *s); argc = 0; break; } } } if (argc < 1) { printf("Usage: crck [-w] filename...\n"); exit(1); } while (argc-- > 0) { in_file = (argv++)[0]; fdi = open(in_file, O_RDONLY); if (fdi < 0) { printf("Cannot access %s\n", in_file); continue; } crc = wflg = 0; while ((c = read(fdi, cbuf, CPMSEC)) > 0) { if ((c != CPMSEC) && warn) { wflg++; } crc = crck(cbuf, c, crc); } printf("%14s --> %04X", in_file, crc); if(wflg)printf(" <-- not CP/M sector sized.\n"); else printf("\n"); close(fdi); continue; } } /* * The only good thing to be said about the following function is that * it faithfully emulates the 8080 code in the CRCK4x.ASM series. It * does NOT perform a CRC calculation, but does a rather bizarre hash * sum. */ unsigned crck(buf, size, oldcrc) char *buf; int size; unsigned oldcrc; { register unsigned newcrc, tmp; register int i, qbit; newcrc = oldcrc; for (i = 0; i < size; i++) { qbit = newcrc & 0x8000; newcrc <<= 1; tmp = (newcrc + *buf++) & 0xff; newcrc = (newcrc & 0xff00) | tmp; if (qbit) { newcrc ^= 0xA097; } } return (newcrc); } 9-Oct-85 07:23:30-MDT,3012;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 9 Oct 85 07:23:22-MDT Received: from usc-isi.arpa by AMSAA.ARPA id a027795; 9 Oct 85 8:31 EDT Date: 9 Oct 1985 02:07:04 EDT Subject: SB180 quirks From: Rex Buddenberg To: info-cpm@AMSAA.ARPA cc: BUDDENBERGRA@USC-ISI.ARPA Some experiences with the Ciarcia SB180 computer board. The SB180 board has some gotchas attached. It is a solid machine, but not without some rough edges. Here is what a couple of us have found: Reset. A cold boot doesn't always. The system is supposed to come up in monitor if no disk is present in A: (or no drives attached). System is supposed to reboot CPM if the disc is loaded. In both cases, it often takes several resets to get action. Discs. Read the manual carefully. Few drives come correctly configured out of the box. If you put an 8" drive on the system (eg as C:), you gotta turn it on every time you use the machine. If you don't (or turn it off without shutting down the rest of the system), you get this Gawd-awful buzz in the 5" drives. Configuration. I hooked up a couple Qume 542's and found that you want to pull ALL the shunts except the drive select strap. Regarding 8" drives, a Qume DT8 came up OK after fiddling around with the settings for a bit. A Tandon half height has yet to decide to cooperate. Kermit. And modem programs. Haven't yet figured out the I/O. The CP4 'generic' Kermit will not talk to the modem for some reason. Yes, I tried all the port settings. If someone gets a Kermit front end for this thing, let me know... ASCI ports. You get a terminal and a modem port. The basic bits come right out of the 64180 and only the 1488/1489 RS-232 drivers are between your terminal and the CPU. Which is just enough. My printer is wired as a DTE, but the modem is a DCE. So to avoid fooling around with null modems and such, try this. Get a 26 pin crimp-on connector to attach the ribbon to the board. Get your length of ribbon cable and crimp the connector to it in the middle. Then wire each end to the DB-25s however you need them. I got one female DTE and one male DCE so both peripherals plug in correctly. Z-DOS. You have to sort thru all the stuff on the masters and figger out that you don't need the 4 directory programs supplied -- 1 will do nicely. Unfortunately there isn't a lot of help in setting up a usable working disc configuration. Take out too much and you get warmed over CPM. Put in too much and you have disc-bloat. Not obvious where to discriminate. But I guess this is a bit like inheriting your million and not knowing where to spend it all. There is no readily apparent way to get from CPM to the monitor. The reverse is obvious. Summary. This board did not come up quite as slickly as my AMPRO Little Board, which has become my workhorse for general stuff. But it is in the same league. b ------- 9-Oct-85 07:46:10-MDT,942;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 9 Oct 85 07:46:05-MDT Received: from crdc-vax2.arpa by AMSAA.ARPA id a028826; 9 Oct 85 9:07 EDT Date: Wed, 9 Oct 85 9:08:45 EST From: "Jack H. Smith" To: info-cpm@AMSAA.ARPA Subject: watfor compiler Bob, You might try SSS fortran, 'Small System Services', Super- soft Fortran IV Extended with Ratfor. As a reference manual, it suggests 'Fortran IV with Watfor & Watfiv', a text that I used in 1971 in high school. 'SSS Fortran' has most of the features of Watfor or Watfiv except for the inherent differencs caused by implementation on an 8-bit micro. It runs on my Intertec Compustar which is running standard CP/M 2.2. Supersoft's address is P.O. Box 1628, Champaign, IL zip 61820 and phone is 217-359-2112.... Hope this helps, Jack H. Smith 9-Oct-85 14:38:23-MDT,2573;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 9 Oct 85 14:38:07-MDT Received: from jpl-vlsi.arpa by AMSAA.ARPA id a013074; 9 Oct 85 15:54 EDT Date: Wed, 9 Oct 85 12:56:45 PDT From: dantas@JPL-VLSI.ARPA Subject: please post on info-cpm To: info-cpm@AMSAA.ARPA From: VLSIDC::ST%"cpmlist@AMSAA.ARPA" 9-OCT-1985 12:16 To: DANTAS Subj: [dantas: EXOR S-100 SYSTEM INFO] Received: from AMSAA by JPL-VLSI.ARPA with INTERNET ; Wed, 9 Oct 85 12:16:24 PDT Date: Wed, 9 Oct 85 14:38:06 EDT From: Dave Towson (info-cpm-request) To: dantas@jpl-vlsi.ARPA Subject: [dantas: EXOR S-100 SYSTEM INFO] Bob - The address "info-cpm-request@amsaa.arpa" is for matters dealing with the operation of the mailing list (additions, deletions, changes, etc.). Please send general articles such as this one to "info-cpm@amsaa.arpa" (i.e., leave off the "request"). Thanks, Dave ----- Forwarded message # 1: Received: from jpl-vlsi.arpa by AMSAA.ARPA id a023189; 3 Oct 85 7:47 EDT Date: Wed, 2 Oct 85 14:42:26 PDT From: dantas@JPL-VLSI.ARPA Subject: EXOR S-100 SYSTEM INFO To: info-cpm-request@amsaa.arpa I AM A MEMBER OF THE OKOK (OSBORNE KOMPUTER OWNERS KLUB), WHICH MEETS AT CALIF. INSTITUTE OF TECHNOLOGY IN PASADENA. THE CLUB AQUIRED AN EXOR S-100 COMPUTER SYSTEM TO DEDICATE IT FOR OPERATION OF A CLUB BULLETIN BOARD. THIS SYSTEM OPERATES WITH CP/M 2.2, AND INCLUDES ONE 360K DS/DD FLOPPY DRIVE AND ONE 5MEG HARD DISK DRIVE. THE SYSTEM WORKS FINE. BUT, UNFORTU- NATELY CAME WITHOUT DOCUMENTATION. WE CAN SEND OR RECEIVE BUT HAVE NOT BEEN ABLE TO OPERATE IT IN DUPLEX MODE USING XMODEM. IF ANYONE HAS A COPY OF THE DOCUMENTATION FOR THIS SYSTEM WE WOULD BE HAPPY TO PAY FOR ANY CHARGES IN RECEIVING A COPY OF SAME. BARING THIS WE WOULD LIKE TO REQUEST INFO ON PATCHING FOR BULLETIN BOARD OPERATION ON XMODEM. IF THIS IS IMPOSSIBLE THEN WE WOULD CONSIDER SELLING THE SYSTEM AND INTERESTED PARTIES MAY CONTACT ME AT: BOB DANTAS 1180 NO. HUDSON AVE. PASADENA, CALIF. 91104 (818) 798-9903 LEAVE MESSAGE OR % JET PROPULSION LABORATORY 4800 OAK GROVE DR. MAIL SLOT T-1180 PASADENA, CALIF. 91109 DANTAS@JPL-VLSI.ARPA ----- End of forwarded messages 10-Oct-85 06:14:34-MDT,1067;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 10 Oct 85 06:14:28-MDT Received: from brl-tgr.arpa by AMSAA.ARPA id aa20215; 10 Oct 85 7:34 EDT Received: from usenet by TGR.BRL.ARPA id a029617; 9 Oct 85 18:51 EDT From: ir320 Newsgroups: net.micro.cpm Subject: A way to read 48 tpi disks on 96 tpi drives? Message-ID: <2229@sdcc6.UUCP> Date: 5 Oct 85 16:37:40 GMT To: info-cpm@AMSAA.ARPA Hello netlanders, I am getting a new computer and need to decide whether to get 96 tpi drives or 48 tpi drives. I know I get double the storage with 96 tpi, but I also give up disk compatability with them don't I? Is there a way I could read/write a 48 tpi disks on a 96 tpi machine. (The system is question is the new SB180 system described in Byte.) Can other systems write disks for these drives? John Antypas UC San Diego uucp: ...!{ ucbvax, decvax, ihnp4, noscvax, bang}!sdcsvax!sdcc6!ir320 arpa: ir320%sdcc6@sdcsvax.ARPA sdcsvax!sdcc6!ir320@Berkeley.ARPA 10-Oct-85 06:17:09-MDT,767;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 10 Oct 85 06:17:02-MDT Received: from brl-tgr.arpa by AMSAA.ARPA id a020262; 10 Oct 85 7:35 EDT Received: from usenet by TGR.BRL.ARPA id a002196; 9 Oct 85 21:52 EDT From: branflick Newsgroups: net.micro.cpm Subject: FTP for Tekelec Message-ID: <571@mruxc.UUCP> Date: 8 Oct 85 20:36:43 GMT To: info-cpm@AMSAA.ARPA Subject: FTP for Tekelec Newsgroups: net.micro.cpm Is anyone on the net aware of a public domain FTP or Modem7 overlay for the Tekelec TE707 Protocol Analyzer? Please respond by Email as I am sure most (all?) folks on the net have never heard of this rather specialized piece of test gear. Thanks, Don 10-Oct-85 06:41:03-MDT,1295;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 10 Oct 85 06:40:56-MDT Received: from simtel20.arpa by AMSAA.ARPA id a020464; 10 Oct 85 7:41 EDT Received: from mitre-bedford by SIMTEL20.ARPA with TCP; Wed 9 Oct 85 15:23:03-MDT Date: Wednesday, 9 Oct 1985 12:48-EDT From: tom@MITRE-BEDFORD.ARPA To: info-cpm@SIMTEL20.ARPA Cc: info-apple@BRL.ARPA, info-kermit@CU20B.ARPA, tom@MITRE-BEDFORD.ARPA Subject: RESEND OF CPM KERMIT REQUEST From: Trevor O. McCarthy: I sent a request three weeks ago for information on kermit-80 for the APPLE II series. I cannot get it to run with an Applied Engineering Z80+ card in slot #7 (using their CPM called "CPAM 4.1"). I have heard that some people cannot get kermit-80 to run with Microsoft CP/M in any slot except 4 or 5. Is this true? I can't change my slot assignments as all other slots have cards or products already set up for them. I realise that someone may already have responded to my previous message, but our ARPANET box was down, and I did not receive any mail. Anyone who might have sent a response got it returned as undeliverable. I would appreciate a "resend" of any responses to my first message, as well as any other replies, advice, or comments. Thanks. 10-Oct-85 11:29:52-MDT,2133;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 10 Oct 85 11:29:32-MDT Received: from usc-eclb.arpa by AMSAA.ARPA id a029168; 10 Oct 85 12:46 EDT Date: 10 Oct 1985 09:49-PDT Sender: STANLEY@USC-ECLB.ARPA Subject: Re: A way to read 48 tpi disks on 96 tpi drives? From: STANLEY@USC-ECLB.ARPA To: ir320%sdcc6.uucp@BRL.ARPA Cc: info-cpm@AMSAA.ARPA Message-ID: <[USC-ECLB.ARPA]10-Oct-85 09:49:46.STANLEY> In-Reply-To: <2229@sdcc6.UUCP> Received: from AMSAA.ARPA by USC-ECLB.ARPA; Thu 10 Oct 85 05:19:47-PDT from brl-tgr.arpa by AMSAA.ARPA id aa20215; 10 Oct 85 7:34 EDT from usenet by TGR.BRL.ARPA id a029617; 9 Oct 85 18:51 EDT Date: 5 Oct 85 16:37:40 GMT From: ir320 To: info-cpm@AMSAA.ARPA Subject: A way to read 48 tpi disks on 96 tpi drives? Return-Path: Message-ID: <2229@sdcc6.UUCP> Newsgroups: net.micro.cpm Hello netlanders, I am getting a new computer and need to decide whether to get 96 tpi drives or 48 tpi drives. I know I get double the storage with 96 tpi, but I also give up disk compatability with them don't I? Is there a way I could read/write a 48 tpi disks on a 96 tpi machine. (The system is question is the new SB180 system described in Byte.) Can other systems write disks for these drives? John Antypas UC San Diego uucp: ...!{ ucbvax, decvax, ihnp4, noscvax, bang}!sdcsvax!sdcc6!ir320 arpa: ir320%sdcc6@sdcsvax.ARPA sdcsvax!sdcc6!ir320@Berkeley.ARPA -------------------- John, You can read 48 tpi disks on 96 tpi drives by double-stepping the head for each track; Heath H89's have been doing this for a long time. Writing in 48 tpi from a 96 tpi drive is another thing. I've been told it can be done, and have seen it happen occasionally on an IBM PC/AT, but my experience tells me it is a very dicey business. Reading can be done dependably, but not writing. ...Dick Stanley 10-Oct-85 13:57:39-MDT,1409;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 10 Oct 85 13:57:30-MDT Received: from xerox.arpa by AMSAA.ARPA id a005151; 10 Oct 85 14:58 EDT Received: from Aurora.ms by ArpaGateway.ms ; 10 OCT 85 11:59:51 PDT Date: Thu, 10 Oct 85 11:35 EDT From: Kushall.henr@XEROX.ARPA Subject: Re: A way to read 48 tpi disks on 96 tpi drives? In-reply-to: <2229@sdcc6.UUCP> To: ir320 cc: info-cpm@AMSAA.ARPA Message-ID: <851010-115951-1795@Xerox> I have a DEC Rainbow that uses DEC RX50 single sidded 96 tpi drives, under MS-DOS I can read IBM PC single sidded 48 tpi disks. There is also a program called Media Master that allows reading(and writing) of many popular 96 & 48 tpi disks. MM even allows the 96 tpi drive to format a disk to the popular 48 tpi formats, Kaypro, IBM PC, Osborne. One problem that can occur in writing is that the 96 tpi head width is narrower than with a 48tpi drive (At least DEC claims it is) and a 48 tpi drive might have trouble reading a 48 tpi disk written with a 96 tpi drive. I have had very good results with this, but always use a 'new' disk to avoid data residue that could be left from a 48 tpi write that may not erase completly with a 96 tpi head. To make a long story short, with the right software you can read the 48 tpi disks on the 96 tpi drives! ED KUSHALL 10-Oct-85 14:42:32-MDT,719;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 10 Oct 85 14:42:17-MDT Received: from cmu-cs-c.arpa by AMSAA.ARPA id a007593; 10 Oct 85 15:49 EDT Received: ID ; Thu 10 Oct 85 15:52:13-EDT Date: Thu 10 Oct 85 15:52:08-EDT From: Drew Anderson Subject: 96/48 TPI compatibility To: info-cpm@AMSAA.ARPA I have been told that reading and writing of 48TPI format disks can be done with double stepping (for reading) and bulk erased and reformatted (both, not one or the other - for writing) disks. If the disks are just reformatted, there can be some confusion on the 48TPI drive's part. Drew Anderson ------- 11-Oct-85 06:02:52-MDT,932;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 11 Oct 85 06:02:43-MDT Received: from brl-tgr.arpa by AMSAA.ARPA id ab11051; 11 Oct 85 7:13 EDT Received: from usenet by TGR.BRL.ARPA id a018078; 10 Oct 85 22:34 EDT From: u557593877ea Newsgroups: net.micro.cpm Subject: C compiler info Message-ID: <132@ucdavis.UUCP> Date: 10 Oct 85 09:20:00 GMT To: info-cpm@AMSAA.ARPA *** I DID REPLACE THIS LINE WITH MY MESSAGE *** I am interested in purchasing a C compiler and am consider the BDS compiler. I am using a Z80 system with CP/M80. I would appreciate any thoughts or experiances on this or other low-priced compilers (under $200). Thanks in advance... Bruce Martin ps Please reply by E-mail! (ARPA) ucdavis!deneb!u557593877ea@ucb-vax.arpa (UUCP) ...!{ucbvax,dual}!ucdavis!deneb!u557593877ea 11-Oct-85 06:19:13-MDT,614;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 11 Oct 85 06:19:06-MDT Received: from pica-lca.arpa by AMSAA.ARPA id a012082; 11 Oct 85 7:52 EDT Date: Fri, 11 Oct 85 7:48:36 EDT From: "Kenneth E. Van_Camp" (LCWSL) To: stanley@USC-ECLB.ARPA cc: info-cpm@AMSAA.ARPA Subject: read/write 48 tpi disks on 96 tpi drives I disagree with Dick Stanley on writing 48 tpi disks on 96 tpi drives. I've been reading & writing this way on my IBM PC AT for quite a while with no complications (DOS 2.10). --Ken Van Camp 11-Oct-85 10:38:38-MDT,7426;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 11 Oct 85 10:38:12-MDT Received: from lanl.arpa by AMSAA.ARPA id a021036; 11 Oct 85 11:54 EDT Received: from a.ARPA by LANL.ARPA (4.12/4.7) id AA17687; Fri, 11 Oct 85 09:56:45 mdt Received: by a.ARPA (4.12/4.7) id AA09030; Fri, 11 Oct 85 09:56:24 mdt Date: Fri, 11 Oct 85 09:56:24 mdt From: Richard Thomsen Message-Id: <8510111556.AA09030@a.ARPA> To: info-cpm@AMSAA.ARPA Subject: Request for CP/M help on Find Next I need some help on using the CP/M Find First/Find Next commands. I use the following routine to find the first file on the disk by using the Find First CP/M command, then open the file and print the file name. Then I close the file and use the same routine to find the next file. On calling this routine, the ambigious file name is pointed to by reg HL, and the last file found is pointed to by reg DE. Reg A contains the value zero on the first call, and 7 on successive calls. I stepped through this code with DDT, and everything seems proper, but the Find Next call always returns with Reg A = 0FFH to indicate no files found. But files exist! I got this code from _The CP/M Programmer's Handbook_ by Andy Johnson-Laird, but it never finds the second or later files. Another version of code using this routine finds some, but not all, of the files on the disk. What am I doing wrong??? I looked through the INSIDCPM.LBR, but they are not really doing anything similar. When I modify the program to not open the files that were found, but just print the names, and also to not do the Find First again, then it finds all the files. But I need to open the files and copy them, and this seems to screw up the Find Next! Can anyone help????? ;++ ; ; TITLE: GETNEXTF ; ; TYPE: Subroutine ; ; ABSTRACT: ; ; This subroutine gets the next file FCB from a possibly ambiguous file ; name. The actual FCB is stored in the destination FCB. ; ; ; INPUTS: ; ; Reg HL -- Address of the possibly ambiguious file name FCB. ; Reg DE -- Address of FCB to contain the file name found ; Reg A -- File control byte. ; Zero to return the first file name that matches ; Non-zero to return the next file name that matches ; ; OUTPUTS: ; ; Carry -- Exit status ; Set -- File not found ; Clear -- File name found and FCB set up ; ; SIDE EFFECTS: ; ; Address pointed to by reg DE is set to file name found. ; DMA address is changed. ; ; REGISTERS CHANGED: A, B, C ; ;-- ; ; Define the data areas and values used by this subroutine ; GNFFCBMOVSIZE EQU 13 ;Define size of FCB to be moved GNFDIRBUF DS 128 ;Define buffer area for directory ; ; Start of code -- save the FCB addresses ; GETNEXTF: PUSH D ;Save destination FCB on stack PUSH H ;Save source FCB on stack PUSH PSW ;Save First/Next flag on stack ; ; Set the DMA address to the directory buffer ; LXI D,GNFDIRBUF ;Get address of directory buffer MVI C,SETDMA ;Get code for set DMA CALL BDOS ;Call BDOS to set the DMA address ; ; DMA address set -- see if first or next ; POP PSW ;Restore First/Next flag ORA A ;Check First/Next flag JNZ GNFNEXT ;If next, use that call ; ; Request is to get the first file name ; POP D ;Get address of source file FCB for search PUSH D ;And save it again MVI C,SEARCHF ;Get code to search for first filename CALL BDOS ;Call BDOS to perform search POP H ;Restore address of source FCB POP D ;Restore address of destination FCB CPI 0FFH ;See if file was found JZ GNFFILENOTFND ;If not, then just exit with error JMP GNFGETFCB ;Otherwise, get the FCB ; ; Request is to get the next file name -- search for next ; First, the context of the file name must be restored by again ; searching for the last one found. ; GNFNEXT: ; ; Request is to get the next file name -- search for next ; First, the context of the file name must be restored by again ; searching for the last one found. ; GNFNEXT: POP H ;Recover address of source file name FCB POP D ;Recover address of destination FCB PUSH H ;Save them again, but in opposite order PUSH D CALL GNFZEROFILE ;Clear all but the name from the FCB POP D ;Recover the destination FCB address PUSH D ;And save it again MVI C,SEARCHF ;Get code to search for the last file found CALL BDOS ;And re-find that file *** At this point, it finds the file again, as it should *** ; ; Now the FCB is set to what it was at the end of the last search. ; Move the source FCB into the destination FCB and search for the next. ; POP D ;Get the address of the destination FCB POP H ;Get the address of the source FCB PUSH D ;Save them again in the opposite order PUSH H PUSH D ;Save address of destination FCB again MVI C,FCBSIZE ;Get the size of the FCB's CALL MOVE ;Set the destination FCB to the source FCB ; ; Now call the BDOS to search for the next occurance of the FCB ; POP D ;Get address of destination FCB CALL GNFZEROFILE ;And clear all but the name MVI C,SEARCHN ;Get code to search for next file name CALL BDOS ;Call the BDOS to do the search *** At this point, it returns with Reg A = 0FFH, indicating no more files POP H ;Restore the address of the source FCB POP D ;Restore the address of the destination FCB CPI 0FFH ;See if file was found JZ GNFFILENOTFND ;If not, then just exit with error ; ; ; File was found -- save the filename found in the save area for ; next search ; GNFGETFCB: PUSH H ;Save the address of the source FCB PUSH D ;Save the address of the destination FCB ADD A ;Multiply return code by 32 to get offset ADD A ;4 ADD A ;8 ADD A ;16 ADD A ;32 LXI H,GNFDIRBUF ;Get address of directory buffer MOV E,A ;Put offset into reg E MVI D,0 ;Clear reg D to get 16-bit offset DAD D ;Add to directory buffer POP D ;Get address of destination FCB PUSH D ;And save it again MVI C,FCBSIZE ;Get size of entry to save CALL MOVE ;Move name into save area POP D ;Get the address of the destination FCB POP H ;Get the address of the source FCB MOV A,M ;Get the disk/user number from source STAX D ;Store disk/user number in destination FCB ; ; FCB now set to next disk -- zero fill it for any disk commands ; PUSH D ;Save the address of the destination FCB PUSH H ;Save the address of the source FCB CALL ZEROFCB ;Zero fill the FCB POP H ;Restore the address of the source FCB POP D ;Restore the address of the destination FCB XRA A ;Clear carry to indicate success RET ;And return to caller ; ; File not found -- return error code to user ; GNFFILENOTFND: STC ;Set carry to indicate error RET ;And return to caller ; ; Clear the FCB except for the disk, file name, file type, and extent ; Address of FCB is in reg DE. ; GNFZEROFILE: LXI H,13 ;Bypass the file name and extent stored DAD D ;Get the address of the part to clear MVI C,36-13 ;Get number of bytes to clear GNFZEROFILELP: MVI M,0 ;Clear the byte INX H ;Increment to next byte DCR C ;Decrement count JNZ GNFZEROFILELP ;Continue for all bytes RET ;Otherwise, return to caller ; Version 2.2 (I believe) of CP/M on a DEC Rainbow 100+. Richard Thomsen rgt@lanl 11-Oct-85 11:23:20-MDT,1507;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 11 Oct 85 11:23:12-MDT Received: from usc-eclb.arpa by AMSAA.ARPA id a021995; 11 Oct 85 12:36 EDT Date: 11 Oct 1985 09:38-PDT Sender: STANLEY@USC-ECLB.ARPA Subject: Re: read/write 48 tpi disks on 96 tpi drives From: STANLEY@USC-ECLB.ARPA To: kvancamp@PICA-LCA.ARPA Cc: stanley@USC-ECLB.ARPA, info-cpm@AMSAA.ARPA Message-ID: <[USC-ECLB.ARPA]11-Oct-85 09:38:40.STANLEY> In-Reply-To: The message of Fri, 11 Oct 85 7:48:36 EDT from Kenneth E. Van_Camp (LCWSL) Received: from PICA-LCA.ARPA by USC-ECLB.ARPA; Fri 11 Oct 85 04:56:14-PDT Date: Fri, 11 Oct 85 7:48:36 EDT From: Kenneth E. Van_Camp (LCWSL) To: stanley@usc-eclb.arpa Cc: info-cpm@amsaa.arpa Subject: read/write 48 tpi disks on 96 tpi drives Return-Path: I disagree with Dick Stanley on writing 48 tpi disks on 96 tpi drives. I've been reading & writing this way on my IBM PC AT for quite a while with no complications (DOS 2.10). --Ken Van Camp -------------------- Ken, I'm glad to know it can be done with repeatability. Any hints you can offer on how to get the write part to work dependably will be greatly appreciated. My H89 won't do that at all, and out PC/AT at the office bats no better than .400. ...Dick 11-Oct-85 12:41:29-MDT,1598;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 11 Oct 85 12:41:17-MDT Received: from brl-aos.arpa by AMSAA.ARPA id a024962; 11 Oct 85 14:15 EDT Received: from hi-multics.arpa by AOS.BRL.ARPA id a019213; 11 Oct 85 14:06 EDT Date: Fri, 11 Oct 85 12:56 CDT From: "David S. Cargo" Subject: ? Info request of Baby Blue 2 & Earth TurboSlave To: info-cpm@BRL.ARPA Message-ID: <851011175646.693832@HI-MULTICS.ARPA> I was hoping to add some hardware supported CP/M-80 capabilities to an IBM-compatible computer. I checked with two vendors who advertise in BYTE (Oryx Systems Inc. and Progressive Micro Distributors) to see if they had the Xedex/Microlog Baby Blue II. Both listed it, but neither of them had it in stock. Both said the vendor is "going bankrupt" and it is therefore hard to get stock. Question 1: Is there some other vendor that does have the Baby Blue II in stock? A second alternative which now is appearing is the TurboSlave from Earth computers. This TurboSlave-PC has a Z80H, 128K of RAM, two RS232 ports, and TurboDOS. The price, $495 list, seems quite reasonable. I just am not sure I want to be the first person to try it. Question 2: Is there anyone out there who has tried this board (and liked it)? Please send your responses to Cargo at HI-Multics. If I get any responses I will summarize. If I get other people asking for the results of my query I will try to keep in touch. $500 is not the kind of money I would like to risk without taking a deeper look. 11-Oct-85 13:25:09-MDT,1131;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 11 Oct 85 13:25:03-MDT Received: from rand-unix.arpa by AMSAA.ARPA id a025737; 11 Oct 85 14:47 EDT Return-Path: Received: by rand-unix.ARPA; Fri, 11 Oct 85 10:02:25 pdt From: Bridger Mitchell Message-Id: <8510111702.AA00100@rand-unix.ARPA> Date: 11 Oct 85 10:02:22 PDT (Fri) To: Richard Thomsen Cc: info-cpm@AMSAA.ARPA, bridger@RAND-UNIX.ARPA Subject: Re: Request for CP/M help on Find Next In-Reply-To: Your message of Fri, 11 Oct 85 09:56:24 mdt. <8510111556.AA09030@a.ARPA> The cp/m 2.2 search first/search next functions must be used with NO INTERVENING bdos or bios file i/o calls. Search-next proceeds from internal bdos pointers and the bios's directory buffer contents; a close-function, for example, will change both and a subsequent search-next will be proceeding from the end of the directory. It is ok to use selected other (non-file i/o) calls between search function calls, e.g. print-character. --bridger mitchell 11-Oct-85 13:50:58-MDT,989;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 11 Oct 85 13:50:50-MDT Received: from mitre.arpa by AMSAA.ARPA id a026115; 11 Oct 85 15:03 EDT Received: by mitre.ARPA (4.12/4.7) id AA13975; Fri, 11 Oct 85 15:07:46 edt Message-Id: <8510111907.AA13975@mitre.ARPA> To: STANLEY@USC-ECLB.ARPA Cc: kvancamp@PICA-LCA.ARPA, info-cpm@AMSAA.ARPA Subject: Re: read/write 48 tpi disks on 96 tpi drives In-Reply-To: Your message of 11 Oct 1985 09:38-PDT. <[USC-ECLB.ARPA]11-Oct-85 09:38:40.STANLEY> Date: 11 Oct 85 15:07:14 EDT (Fri) From: Jeff Edelheit For what it's worth, we were so concerned about read/write of 48 tpi on our PC/AT we spent the extra $200+ and got the optional 48 tpi second drive. Dick, one thing to note in Ken's earlier note was that he said he used 2.1 not 3.1. If the 2.1 is a typo, then he is having much better luck than anyonelse I know. Jeff Edelheit (edelheit@mitre) 12-Oct-85 05:43:47-MDT,861;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Sat 12 Oct 85 05:43:42-MDT Received: from brl-tgr.arpa by AMSAA.ARPA id a002479; 12 Oct 85 7:18 EDT Received: from usenet by TGR.BRL.ARPA id a008391; 11 Oct 85 18:40 EDT From: Ted Medin Newsgroups: net.micro.cpm Subject: Re: Looking for WATFOR compiler Message-ID: <51@noscvax.UUCP> Date: 10 Oct 85 19:58:52 GMT To: info-cpm@AMSAA.ARPA In article <1953@brl-tgr.ARPA> Kushall.henr@XEROX.ARPA writes: >WATFOR stands for WATerlooFORtran and is an interactive Fortran interputer. >It was developed by Waterloo University in Canada. > >The first machine to use it was the Commadore 9000 (Super PET). >I don't know if ever was made available for any other machines. > I first used WATFOR on an IBM 360/65 in '66 or so. 12-Oct-85 06:01:52-MDT,1235;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Sat 12 Oct 85 06:01:46-MDT Received: from csnet-pdn-gw by AMSAA.ARPA id a002515; 12 Oct 85 7:20 EDT Received: from umass-cs by csnet-relay.csnet id ae25906; 12 Oct 85 1:04 EDT Date: Fri, 11 Oct 85 10:11 EST From: "Robert (LISPer 68K) Heller" To: Info-CPM@AMSAA.ARPA, Info-Micro@BRL.ARPA Subject: looking for a micro I am looking for a cross-assambler for the 6502 type micro-processor to run under CP/M-68K. I doubt that such a program exists in a ready-to-run form. I will settle for such an assambler coded in C, FORTRAN or Pascal in source form, which I could then translate (if not C) and compile for my CP/M-68K system. As another alternitive, an assambler that runs on the VAX will be ok, if that is all that is available. Robert Heller Visions Group COINS Dept. UMass/Amherst Electronic mail: UMass/RCF: HELLER UMass/ECS, Smith College, Hampshire College: VAX1::HELLER Amherst College: LISP UMass/Cyber: HELLER@RCF.MAIL CSNet: Heller@UMass-cs.CSNET ARPANet: Heller%UMass-cs.CSNET@CSNet-Relay.ARPA 12-Oct-85 06:13:50-MDT,908;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Sat 12 Oct 85 06:13:45-MDT Received: from csnet-pdn-gw by AMSAA.ARPA id a002516; 12 Oct 85 7:20 EDT Received: from umass-cs by csnet-relay.csnet id bm25906; 12 Oct 85 1:14 EDT Date: Sat, 12 Oct 85 00:11 EST From: One word is worth 10**-3 pictures To: info-cpm@AMSAA.ARPA Subject: CP/M-68K compatibility Do any of you folks know just what the degree of compatibility is between CP/M-68K and CP/M-8{0,6}? i (will) have CPM-68K and would like toknow what CP/M programs i can run under it. Are the call-outs to BIOS done the same way? i guess this request will also serve the purpose of letting me find out what CP/M programs are available in source form. -neville Newman@UMass (CSnet) Newman%UMass@CSnet-Relay (ARPAnet) 12-Oct-85 06:22:15-MDT,1253;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Sat 12 Oct 85 06:22:09-MDT Received: from brl-tgr.arpa by AMSAA.ARPA id a002577; 12 Oct 85 7:24 EDT Received: from usenet by TGR.BRL.ARPA id a014426; 12 Oct 85 5:41 EDT From: Ted Medin Newsgroups: net.micro.cpm Subject: Re: Looking for WATFOR compiler Message-ID: <52@noscvax.UUCP> Date: 10 Oct 85 20:04:10 GMT To: info-cpm@AMSAA.ARPA In article <1980@brl-tgr.ARPA> young@UCI-ICSC.ARPA (Michal Young) writes: > >WATFOR was NOT first implemented on the SuperPET. It's immediate successor, >WATFIV, is mentioned in the 1979 edition of the dragon book (Aho and >Ullman), so WATFOR was around a long time before SuperPET. The version I am >aware of was available on IBM mainframes and was not an interpreter; it was >a very fast compiler optimized for handling multiple compiles submitted in a >batch. It was specially designed for student use, concentrating on quick >compile and good error checking rather than optimized object code. I believe you are wrong about the interpreter part. But you are right about all the rest. It was the best diagnostic compiler/interpreter I have ever worked with. 12-Oct-85 06:34:27-MDT,1648;000000000000 Return-Path: Received: from AMSAA by SIMTEL20.ARPA with TCP; Sat 12 Oct 85 06:34:21-MDT Received: from brl-tgr.arpa by AMSAA.ARPA id aa02577; 12 Oct 85 7:24 EDT Received: from usenet by TGR.BRL.ARPA id a014467; 12 Oct 85 5:42 EDT From: Bob Halloran Newsgroups: net.micro.cpm Subject: Re: Backup on VCR Message-ID: <308@pedsgd.UUCP> Date: 9 Oct 85 12:16:47 GMT To: info-cpm@AMSAA.ARPA Organization : Perkin-Elmer DSG, Tinton Falls NJ In article <1945@brl-tgr.ARPA> JFORREST@SIMTEL20.ARPA (Jim Forrest) writes: >A friend of mine would like to know if there is a RELATIVELY >"easy and inexpensive" way to back up the hard disk on his Kaypro >10 to his VCR. >Appreciate response from anyone with expertise in this area. >Jim At one time, Corvus offered an option for their hard disk systems called the 'Mirror', which allowed backing up hard disks to a VCR. I don't know whet