CP/M/CPM_CDROM.iso/simtel/archives/cpm/8608-1.txt

Text File | 1993-02-12 | 233KB | 5,412 lines

 1-Aug-86 02:27:44-MDT,906;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 1 Aug 86 02:27:38-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id aa03039; 1 Aug 86 3:56 EDT
Received: from USENET by SMOKE.BRL.ARPA id a008372; 1 Aug 86 3:46 EDT
From: "Lynn B. Dobbs" <[e-mail]>
Newsgroups: net.micro.cpm
Subject: Kaypro 4 (1983) bug
Message-ID: <[e-mail]>
Date: 31 Jul 86 22:47:36 GMT
To:       [e-mail]

When Mike tries to run his serial port above 1200 baud, characters
begin dropping out of the text.  The system works very well at 1200
or below.  Different terminal programs have been tried, as well as
different modems.

When logged onto a vax running unix, the vax understands all characters
sent from the Kaypro, but the display still drops characters.

Has anyone seen this problem?  And does any one have a fix?

Thanks.
 1-Aug-86 03:12:01-MDT,1191;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 1 Aug 86 03:11:51-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a003039; 1 Aug 86 3:56 EDT
Received: from USENET by SMOKE.BRL.ARPA id a008364; 1 Aug 86 3:46 EDT
From: novick <[e-mail]>
Newsgroups: net.micro.cpm
Subject: Osborne I terminal emulation?
Message-ID: <[e-mail]>
Date: 29 Jul 86 18:56:00 GMT
Nf-ID: #N:uoregon:140800001:000:610
Nf-From: uoregon!novick    Jul 29 10:56:00 1986
To:       [e-mail]

[]

What terminal does the Osborne I emulate?  I have an original tan-case with
the official double-density and 80/104 column upgrades.  I recall reading in
an old issue of The Portable Companion that the O1 emulated a tvi920.  However,
using this driver results in 1) control codes being displayed on the screen,
and 2) no line-feeds.  If you're using an O1 to communicate with another
system and you've got a terminal emulation that works, please let me know.

Thanks.

David Novick
Computer and Information Science Department
University of Oregon
Eugene, Oregon  97403

{tek|hp-pcd|ogc-vax}!uoregon!novick
 1-Aug-86 07:09:44-MDT,1315;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 1 Aug 86 07:09:34-MDT
Received: from mitre.arpa by AMSAA.ARPA id a006152; 1 Aug 86 8:23 EDT
Full-Name: Thomas Reid
Message-Id: <[e-mail]>
Organization: The MITRE Corp., Washington, D.C.
To: dobbs%marlin.uucp@BRL
Cc: [e-mail]
Subject: Re: Kaypro 4(9183) bug
Date: Fri, 01 Aug 86 08:23:49 -0500
From: [e-mail]

I had a KP 2x (1984) with the same "feature".  The graphics screen monitor
is so slow that it cannot keep up above 1200 baud.  Microcornucopia sells
a new ROM for Kaypros which is supposed to get you up to about 4800 baud.
The problem is with the line feed portion of the memory mapped I/O.  From
the time that you issue a LF at 9600 baud until the routine returns, you
have "missed" 3 or 4 characters at the modem port.

A possibility is to modify your modem 7 clone or kermit to issue an XOFF
just before you do a line feed to shut off the incoming characters, do the
LF, and then XON to continue receiving. (Your host will hate you.)

What you really need is an asynchronous modem port handler.  Check with the
local Kaypro gurus and see if there is one.  The problem can't be all that
rare that someone hasn't done something.

Good luck.
 1-Aug-86 08:34:33-MDT,1126;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 1 Aug 86 08:34:25-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a008992; 1 Aug 86 9:47 EDT
Received: from USENET by SMOKE.BRL.ARPA id a015362; 1 Aug 86 9:43 EDT
From: Peter Arrgh Korn <[e-mail]>
Newsgroups: net.micro.cpm
Subject: Kaypro question
Message-ID: <[e-mail]>
Date: 1 Aug 86 07:40:09 GMT
Sender: [e-mail]
To:       [e-mail]

First off, many thanks to the many replies I've gotten re: my Plea for
help on a SuperBrain problem.  I'll be posting my results shortly (I'm
taking an alternate route to solve the problem).

And now for my question:  Is there a way to take a Kaypro 2/4 and modify
it to be IBM compatible?  I've heard rumors to this effect, but as
yet I've gotten no names of places that'll do it.

Thanks again,
Peter

-------                          "Fred Astaire?  Ginger
Peter Korn                       Rogers did everything
[e-mail]               he did, backwards
{decvax,dual,hplabs,sdcsvax,ulysses}!ucbvax!korn   and in high heels!"
 1-Aug-86 13:48:08-MDT,2129;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 1 Aug 86 13:47:50-MDT
Received: from lll-mfe.arpa by AMSAA.ARPA id a013417; 1 Aug 86 13:02 EDT
Date: Fri, 1 Aug 86 13:01 EST
From: [e-mail]
Subject: Kaypro-as-terminal problems
To: [e-mail]

From:    <[e-mail]>   (Richard C. Secrist)
Date:    Fri,  1-AUG-1986 13:02 EST
To:      [e-mail]
Message-ID: <[OAK.SAINET.MFENET].EB197AE0.008F2CA7.SECRIST>
Header-Disclaimer: I don't like my headers either.
Quote: "May your future be limited only by your dreams." -- Christa McAuliffe
Organization:  Science Applications Int'l. Corp., Oak Ridge, Tenn., USA
CompuServe-ID: [71636,52]
X-VMS-Mail-To: CPM

>       From: "Lynn B. Dobbs" <[e-mail]>
>       Subject: Kaypro 4 (1983) bug
>       Date: 31 Jul 86 22:47:36 GMT
>
>       When Mike tries to run his serial port above 1200 baud, characters
>       begin dropping out of the text.  The system works very well at 1200
>       or below.  Different terminal programs have been tried, as well as
>       different modems.
>
>       When logged onto a vax running unix, the vax understands all characters
>       sent from the Kaypro, but the display still drops characters.
>
>       Has anyone seen this problem?  And does any one have a fix?
>
>       Thanks.

I have had similar problems using a friend's '2 on a VAX under VMS.  I
could do like 3600 if I turned up the NULLS, but the problem then was
his monitor displayed them as /@@@@/ for however many I turned on, which
loses.

Are you familar with Micro Cornucopia magazine ?  Amongst their
public doman collections for the Kaypro is a terminal program that does
the Right Thing for Kaypros (whatever that is) so I could run 9600 no
problem without nulls.  The Micro-8 monitor ROM upgrade (?!) from the
same folks also took care of the null-echo problem.

If you don't have an address I can go find it and post it.

r c s
[e-mail]
 1-Aug-86 13:49:10-MDT,1359;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 1 Aug 86 13:48:52-MDT
Received: from lll-mfe.arpa by AMSAA.ARPA id a013675; 1 Aug 86 13:12 EDT
Date: Fri, 1 Aug 86 13:10 EST
From: [e-mail]
Subject: Osborne I emulation
To: [e-mail]

From:    <[e-mail]>   (Richard C. Secrist)
Date:    Fri,  1-AUG-1986 13:11 EST
To:      [e-mail]
Message-ID: <[OAK.SAINET.MFENET].3D6750A0.008F2CA9.SECRIST>
Header-Disclaimer: I don't like my headers either.
Quote: "May your future be limited only by your dreams." -- Christa McAuliffe
Organization:  Science Applications Int'l. Corp., Oak Ridge, Tenn., USA
CompuServe-ID: [71636,52]
X-VMS-Mail-To: CPM

>       From: novick <[e-mail]>
>       Subject: Osborne I terminal emulation?
>       Date: 29 Jul 86 18:56:00 GMT
>
>       What terminal does the Osborne I emulate?  I have an original...
>                                       ...
>                                       ...
>       David Novick

If you don't have any luck getting an answer (or if someone out there has
an "unknown" type) we could compile a list of say, all known DEL EOL
sequences and you could just write a program to try them all until one
connected...

r c s
 1-Aug-86 14:43:30-MDT,1181;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 1 Aug 86 14:43:16-MDT
Received: from rand-unix.arpa by AMSAA.ARPA id a019167; 1 Aug 86 15:58 EDT
Received: from rondo.RSAC (rondo) by rand-unix.ARPA; Fri, 1 Aug 86 11:55:31 pdt
Received: from holst by rondo.RSAC; Fri, 1 Aug 86 11:53:40 PDT
From: Chris McMenomy <[e-mail]>
Message-Id: <[e-mail]>
To: [e-mail]
Cc: [e-mail]
Cc: [e-mail]
Subject: Re: Osborne I emulation
In-Reply-To: Your message of Fri, 1 Aug 86 13:10 EST.
             <[e-mail]>
Date: Fri, 01 Aug 86 11:52:34 PDT




The Osborne I (brown case) emulates the old televideo 920.  I have used
the standard TERMCAP for the tvi920 with the columns modified to 51 for
four years, and been able to use the Rand editor and play rogue (under a
version that thought 51 columns was okay) and do other heavy cursor
package routines from home with a hayes modem at 1200 baud and the public
domain OTERM terminal package.

Hope that helps.


Christe McMenomy
Rand Corporation

 1-Aug-86 22:28:09-MDT,848;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 1 Aug 86 22:27:57-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a021823; 1 Aug 86 21:51 EDT
Received: from USENET by SMOKE.BRL.ARPA id a013410; 1 Aug 86 21:42 EDT
From: Tim Born <[e-mail]>
Newsgroups: net.micro.cpm
Subject: Can Ampro R/W other floppies?
Message-ID: <[e-mail]>
Date: 1 Aug 86 07:37:45 GMT
To:       [e-mail]

The Ampro little board is pretty flexible as far as disk formats.  I'm trying
to figure out the parameters for the Ampro so it can read and write disks
from an Apple (running CP/M) and an AT&T 6300 (also running CP/M).  If you
have twiddled with the Ampro's disk formats before, please let me know what
your experience has been.

Regards,
tim

...ihnp4!hvlpb!tborn
 2-Aug-86 04:13:27-MDT,715;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sat 2 Aug 86 04:13:20-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a025385; 2 Aug 86 5:43 EDT
Received: from USENET by SMOKE.BRL.ARPA id a016226; 2 Aug 86 5:41 EDT
From: Stephen King <[e-mail]>
Newsgroups: net.micro.cpm
Subject: wanted: PD DBMS or spreadsheet
Message-ID: <[e-mail]>
Date: 30 Jul 86 17:52:36 GMT
To:       [e-mail]

/* munch */

Hello! Does anyone know of a public domain (or cheap) data base
manager for a cp/m-80 machine? (Epson QX) A spreadsheet with
data base capabilities would do just as well. Thanks.

                    ...sjk
    ...!ihnp4!utzoo!dciem!king
 2-Aug-86 04:30:44-MDT,2084;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sat 2 Aug 86 04:30:32-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a025503; 2 Aug 86 5:55 EDT
Received: from USENET by SMOKE.BRL.ARPA id a016310; 2 Aug 86 5:44 EDT
From: dick gardner <[e-mail]>
Newsgroups: net.micro.cpm
Subject: Re: Text Editors
Message-ID: <[e-mail]>
Date: 31 Jul 86 14:54:55 GMT
To:       [e-mail]

This doesn't qualify as a Public Domain entry, but the price is
so low, it's almost stealing.

I have used the MIX editor that you've seen advertised everywhere
for $29 with great success.

My system: in case it's important, is a Lobo Max-80.  It is a 5 Mhz
Z80-based system w/128k RAM, 2 serial ports, built-in 5" and 8" floppy
drivers, as well as SASI H.D. interface, Real Time Clock, etc.
It runs Radio Shack MIII programs (under LDOS) and also runs CPM 2.2
and CPM PLUS (3.0).

I won't clutter up the net with a lot of specs (unless someone requests
specific information), but this Editor made it possible for me to use
CPM effectively. Previously, I was not able to do very much in the way
of programming, lacking a decent editor.

Quickie, condensed specs:  all of the commands are based on those that
Micropro's Wordstar uses. They are just about exactly the same.  If you
don't like that, you can change all the key bindings. This thing does
windows, multiple files, long files, split screens, etc.  You can set
up initialization files so that different versions are available.
It has a very nice Macro command facility.

Quite a bargain for $29 bucks!

Usual disclaimer: I have no vested interest in this company, am just
a satisfied user.


=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#

             Dick Gardner
             Eastman Kodak Co.
             Rochester, New York  14650
             [phone]
       UUCP: rochester!kodak!gardner

To err is human -- to really screw it up
           you need a computer!
=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#

 2-Aug-86 04:53:59-MDT,1048;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sat 2 Aug 86 04:53:53-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a025505; 2 Aug 86 5:56 EDT
Received: from USENET by SMOKE.BRL.ARPA id a016357; 2 Aug 86 5:46 EDT
From: Russ Herman <[e-mail]>
Newsgroups: net.micro.cpm,net.micro.pc
Subject: CP/M-86 help wanted
Message-ID: <[e-mail]>
Date: 31 Jul 86 17:41:45 GMT
To:       [e-mail]

I am trying to use CP/M-86 ver 1.1 (Mar. 83) on an 2-floppy XT clone. At some
point in the boot process, it goes beserk from receiving an interrupt from
the hard disk controller. Is there any patch available to make the system
totally oblivious of the hard disk? Please E-mail if you can help. Thanks.
--
  ______            Russ Herman
 /      \            {allegra,ihnp4,pyramid,decvax}!utzoo!aesat!rwh
@( ?  ? )@
 (  ||  )            The opinions above are strictly personal, and
 ( \__/ )            do not reflect those of my employer (or even
  \____/            possibly myself an hour from now.)
 2-Aug-86 22:21:29-MDT,5289;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sat 2 Aug 86 22:21:11-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a025959; 2 Aug 86 7:51 EDT
Received: from USENET by SMOKE.BRL.ARPA id a017274; 2 Aug 86 7:43 EDT
From: Erik Lindberg <[e-mail]>
Newsgroups: net.micro.pc,net.micro.cpm
Subject: Running CPM *and* Z80 code under DOS!!
Message-ID: <[e-mail]>
Date: 1 Aug 86 23:34:24 GMT
Keywords: Greatest Public Domain Program ever.
To:       [e-mail]

This posting is in response to an article requesting information on
running CPM applications under MS-DOS (not for him, for his sister :-)
One response suggested a V20 chip, but that really doesn't help, because
that only handles the 8080 instructions (most CPM machines are Z80) and
also does not provide you with the BDOS interface critical to any CPM
program. But there is a good solution:

Tell your sister it *is* possible to run almost any program from a true
CPM environment, where "true" is defined as one that does not depend on
any hardware specific features of the system it was running under. The
efficiency of the operation depends on your implementation.

1) FREE: This is the method I use. It is also the slowest method, but
   has some side benefits I find irresistable, besides the price. There
   is a public domain program that fully implements the Z80 instruction
   set and all the relevant CPM BDOS calls. It also provides a VT52
   emulator which may be turned on or off with a simple command. You can
   suspend your CPM task at any time and examine memory, debug, set break
   points, disassemble, even execute a DOS subshell, and then pick up
   execution where it left off. In fact it includes a very flexible and
   complete symbolic debugger as part of the "CPM" environment, which
   even has an option to generate an output file that may be recompiled
   with MAC80 to create the original COM file. Variables and labels are
   assigned on the fly or read from an initialization file.

   I have run DbaseII, SuperCalc, Laboratory Microsystems FORTH, Turbo
   pascal and MS-BASIC under the shell with no problems. You get a
   63k TPA, too, which I have never seen in any *real* CPM system!
   Utilities like STAT, directory sorters, and the like don't work, they
   make no sense given the environment you are in. You use the resident
   PC utilities for that stuff by prefixing it with "!" (just like the
   big boys on Unix Ma!).

   For number crunching we are hurting in this department. A typical PC
   at 4.77Mhz benchmarks at the equivalent of a 250 Khz Z80 CPU, not too
   impressive (or impressive in a negative sense of the word :-). File
   access is done in native mode, so it is alot better. On my 8Mhz AT
   the emulator benchmarks at 1.2 Mhz equivalent Z80 speed, but the file
   access is so much faster that my Dbase applications run at the same
   speed they did under my 4Mhz Z80 CPM system. And that was the original
   reason *I* was interested in this.

   If anyone is interested in this program, E-mail me and we can setup
   some way to get it to you. I won't send it over the net, it is too big.
   But you could download it from me, or send me a disk, or something.

2) <$100: Buy the V20 chip and one of the commercial emulators that provide
   emulation of the missing Z80 opcodes and the CPM environment. Total cost
   will be very nearly $100. From a speed standpoint this solution is vastly
   superior. From a compatibility standpoint, somewhat less so. I tried this
   method first, and was disappointed. Besides not haveing the great
   environment of (1), allowing DOS execution and debugging, there was
   generally a poor user interface and compatibility problem. Without going
   into a more lengthy discussion, I found that some packages would work in
   one environment and not in another. Some packages require you to go to
   painfull contortions to get the application up and running.

3) >$250: Buy a Z80 host board and plug it into your PC. I am currently
   considering this option. Logically you could expect the best of all
   worlds in this case. You have a true Z80 processor, with it's own
   memory, and it only depends on the PC for doing it's I/O. You
   could have *real* CPM running on this hummer! At 8 Mhz! I have seen
   several different boards to do this, the cheapest one which seems to
   have the capabilities I would be looking for is advertised in last
   months Byte magazine for only $199. The catch here is that you are
   dependant on how they wrote their BIOS as to whether you have a really
   useable system. I don't have any experience with the company, so I
   can't really say how good it is likely to be, but if you are not
   in a hurry, I will probably be buying this system and I could post a
   review to the net. For about $600-$800 you can get the original "Blue"
   board, which has a good reputation for compatibility.

Hope this helps!!


del (Erik Lindberg) aka Hugable


Hugs: One of the few good things in life that are still free.
--

del (Erik Lindberg) aka Hugable


Hugs: One of the few good things in life that are still free.
 3-Aug-86 04:27:46-MDT,1534;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sun 3 Aug 86 04:27:33-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id aa02489; 3 Aug 86 5:50 EDT
Received: from USENET by SMOKE.BRL.ARPA id a002498; 3 Aug 86 5:44 EDT
From: [e-mail]
Newsgroups: net.micro.cpm
Subject: Re: CP/M Text Editors
Message-ID: <[e-mail]>
Date: 1 Aug 86 09:54:19 GMT
Posted: Fri Aug  1 09:54:19 1986
To:       [e-mail]

>
> f anyone wants more information about PMATE, I would welcome their
> nquiries, since I am probably the most active supporter around of the 8-bit
> ersion of PMATE (there are 16-bit versions, too).  A special section (with
> estricted access) of my remote access system, the Newton Z-Node
> 617-965-7259, pw=DDT), is devoted to PMATE support.  It includes a bulletin
> oard with suggestions and tips on exploiting PMATE's capabilities and an
> xtensive collection of macros.

        My apologies for posting this; my attempt at sending email
        to you bounced.

        This sounds like the greatest thing since unsliced bread!
        Can you point me (and perhaps other USEnetters) to where
        PMATE can be obtained, please?  Particularly, outside the USA.
--
    Peter Kendell <[e-mail]>

    ...!mcvax!ukc!stc!pete

    "Lord Finchley tried to mend the Electric Light,
     Himself.
     It Struck him Dead! And Serve him Right!
     It is the Duty of the Wealthy Man,
     To give Employment to the Artisan."
 3-Aug-86 04:50:14-MDT,1374;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sun 3 Aug 86 04:50:07-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a002489; 3 Aug 86 5:50 EDT
Received: from USENET by SMOKE.BRL.ARPA id a002481; 3 Aug 86 5:43 EDT
From: Bob Amen <[e-mail]>
Newsgroups: net.micro.cpm
Subject: Re: Text Editors
Message-ID: <[e-mail]>
Date: 1 Aug 86 22:39:58 GMT
To:       [e-mail]

In article <[e-mail]>, [e-mail] (dick gardner) writes:
> This doesn't qualify as a Public Domain entry, but the price is
> so low, it's almost stealing.
>
> I have used the MIX editor that you've seen advertised everywhere
> for $29 with great success.
>

    What sounds like an even greater deal is their current
package price for both the editor and their C compiler...does
anybody know whether their compiler is any good???  They claim
its a complete C...how about code size and compile times.  If
anybody has any experience with their compiler I, for one,
would like to heare about it.  I'm currently looking for
a decent C for my Z80 CP/M system that's not too costly.
$55 sounds pretty good.

    Bob Amen

UUCP:  seismo!umcp-cs!aplcen!quequeg!amen

USPS:    Chesapeake Bay Institute
    4800 Atwell Rd
    Shady Side, MD 20764-0037

Voice:    [phone]
    [phone] (Balt.)
 3-Aug-86 20:22:15-MDT,2369;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sun 3 Aug 86 20:22:07-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a005632; 3 Aug 86 21:46 EDT
Received: from USENET by SMOKE.BRL.ARPA id a004903; 3 Aug 86 21:41 EDT
From: "Willie Smith, LTN Components Eng." <[e-mail]>
Newsgroups: net.micro.cpm
Subject: re: MIX editor
Message-ID: <[e-mail]>
Date: 3 Aug 86 16:37:06 GMT
Sender: [e-mail]
To:       [e-mail]

In a previous article, Dick (kodak!gardner) Gardner sang the
praises of the MIX editor ($30 through MIX Software), and I
thought I should give equal time to an opposing view.  I bought
the MIX editor about a year ago and had all sorts of problems
with it.  A quick look at it with a debugger, and the setting
up of a new stack pointer at the beginning of the program helped
some of the more serious (random) crashes, but I still had some
problems with it.  It seemed to crash if you reached the end of
the memory buffer without _manually_ swapping buffers, it took
_forever_ to do a block move, there was no easy way to back up
in large files, and it would occasionally go away at random
times.  I have renamed it to the MIXmaster editor and stuffed
it into a drawer somewhere.  I called the company to tell them
about my partial fix (the stack pointer) and they denied there
was a problem, treated me like an idiot {I may be one, but I
resent the attitude of 'there couldn't be anything wrong with
_our_ software, dummy'}, and made me call their 'technical'
line (my dime) with my bug report.
    Admittedly, this is a (potentially) wonderful program, as
when it was working, it worked really well, I was able to set
it up about halfway between RSX KED and Wordstar, and was very
powerful and extensable.  However, unexplained random crashes
and serious problems with large files made me put it aside and
purchase Wordstar...
    My system is a (primarily) Compupro S-100 machine running
CP/M 2.2N with (at the time) 64K, 6MHz Z-80, no interrupts, and
2 8 inch floppies.

Willie Smith
UUCP:    decwrl!wookie.dec.com!smith
Internet:    [e-mail]

The opinions above are those of myself, and I have no affiliation
(other than that of a customer) of Compupro, MIX Software, or
Digital Research, whose trademarks appear above.
 3-Aug-86 22:00:50-MDT,14296;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sun 3 Aug 86 22:00:09-MDT
Received: from simtel20.arpa by AMSAA.ARPA id a006107; 3 Aug 86 23:14 EDT
Date: Sun, 3 Aug 1986  21:14 MDT
Message-ID: <[e-mail]>
Sender: [e-mail]
From: Keith Petersen <[e-mail]>
To:   [e-mail]
Subject: New CP/M files on SIMTEL20 30-Jun-86 thru 31-Jul-86

Below is a list of new files added to SIMTEL20's <CPM.*> directories
between 30-Jun-86 and 31-Jul-86.

For a complete list of all files, get:

PD:<CPM>CPM.CRCLST - directory name, filename, type, size and CRC
PD:<CPM>FILES.DIR  - directory and filenames only
PD:<CPM>FILES.IDX  - directory name, file name, size, date on each line

        Filename                Type     Bytes   CRC

PD:<CPM.BASIC>
        B-COMPIL.LBR.1          BINARY   87424  D5E5H
        BASCMNOT.LBR.1          BINARY    9088  6FB0H
        CODECRAK.LBR.1          BINARY    2048  2CB5H

PD:<CPM.BBSLISTS>
        FIDOLIST.80.1           ASCII    85556  0921H
        FINDRCPM.LBR.1          BINARY   13184  FEA9H
        PBBS002.LQT.1           BINARY    6528  2A00H
        RBBS-26G.LST.1          ASCII    34235  9DD3H
        RCPM077.LQT.1           BINARY   58240  D3E8H

PD:<CPM.BDOS>
        P2DOS21.LBR.1           BINARY  101120  A508H (PD BDOS replacement)

PD:<CPM.BYE5>
        B5C-ADV.IQS.1           BINARY    1536  B0A3H
        FFOR.AQM.1              BINARY    8320  6DCBH
        KMD21.LBR.1             BINARY   48000  B30CH
        NEW06.AQM.1             BINARY   13056  A794H

PD:<CPM.COMMODORE>
        CP4-C128.LBR.1          BINARY   15872  1712H (Kermit for C128)
        VDE211C8.LBR.1          BINARY   21248  F30EH (C128 Video editor)

PD:<CPM.CPM3>
        CCP104P.LBR.1           BINARY   84608  B7EAH (original name CCP104+)
        HISTPLUS.LBR.1          BINARY   11520  DA26H (original name HIST+)

PD:<CPM.CPMLIB>
        CPMSHAR.LBR.1           BINARY   32768  0DE6H (extract/make SHARs)

PD:<CPM.DATABASE>
        CHEF.LBR.1              BINARY   98048  6869H (Recipe database)
        CHEFDOC1.WQ.1           BINARY    4480  74C0H   "
        CHEFREC.4Q.1            BINARY   26368  2337H   "
        CHX8010A.LBR.1          BINARY   85760  BD24H
        CHX8010B.LBR.1          BINARY  111744  1B1FH
        FILECARD.LBR.1          BINARY   95616  2E40H (Filecard database)
        FMLYTRE2.LBR.1          BINARY   16000  9A2BH (Family Geneology)
        GENSTAT.LBR.1           BINARY   68864  54D9H (General statistics)
        HIPPO11C.LBR.1          BINARY  165504  9964H (Investment portfolio)
        MAIL20.LBR.1            BINARY  176000  4507H (Mailing list database)

PD:<CPM.DIRUTL>
        MAKE26.AQM.1            BINARY   23296  49B0H
        MAP104.LBR.1            BINARY   16640  11EBH
        RECOVER.LBR.1           BINARY    5248  51D7H
        SD120.LBR.1             BINARY   78208  B8ABH
        SETDRU13.LBR.1          BINARY   45056  DBA8H
        WHERFIND.LBR.1          BINARY   47872  824BH

PD:<CPM.DSKUTL>
        MEGADISK.LBR.1          BINARY   42112  C94AH

PD:<CPM.EDUCATION>
        PR11.LBR.1              BINARY   54784  975BH

PD:<CPM.FILCPY>
        NEWNC115.LBR.1          BINARY    8960  C08DH

PD:<CPM.FILE-DOCS>
        JULBEST.LQT.1           BINARY   29184  D221H
         ^--Read this to see what's new in the public domain world
            (file updated monthly)

PD:<CPM.GENDOC>
        BONDWEL2.MQR.1          BINARY    1408  EB12H
        BONDWEL2.RQV.1          BINARY    8320  4F29H
        CRYPTANA.LBR.1          BINARY   24320  BA96H
        FUTUREOF.CQM.1          BINARY   12160  0591H
         ^--discusses future of CP/M

PD:<CPM.IMP>
        I2TV-4.AQM.1            BINARY   10112  5E0EH
        IMP-SP.LBR.1            BINARY   50176  599AH

PD:<CPM.KAYPRO>
        HARDNOTE.TQT.1          BINARY    9344  4B92H
        KAYEASEL.LBR.2          BINARY  101760  B6EAH (graphics easel)
        TRANSKP4.LBR.1          BINARY   41472  1549H
        TROMPAT1.LBR.1          BINARY   66432  1DD6H
        TRPATCH1.LBR.1          BINARY   27648  7997H
        TRSTATLN.LBR.1          BINARY    8832  D8CCH
        TURBKPEX.LBR.1          BINARY    1792  3B59H
        TURBOROM.DQC.1          BINARY   24064  A2DEH
        TURBOSAF.LBR.1          BINARY    6016  1773H

PD:<CPM.LIST>
        BRAD-DOC.LBR.1          BINARY   12288  CBD4H
        FONT-FOG.LBR.1          BINARY  145024  A664H
        PSET16A.LBR.1           BINARY   38528  D30CH (printer set util)

PD:<CPM.MBBS>
        MBYE45.LBR.1            BINARY   84224  FC89H

PD:<CPM.MEX>
        MXM-2410.AQM.1          BINARY   19072  FBEDH (2400/1200 auto step)
        MXO-RS4P.AQM.1          BINARY   15104  FC65H (Rs mod 4 ovly)
        MXO-SM4P.AQM.1          BINARY    5376  15B3H   "

PD:<CPM.MISC>
        INTEREST-GROUPS-1.TXT.61        ASCII    68715  8636H (Arpa groups)
        INTEREST-GROUPS-2.TXT.61        ASCII    68281  4450H (Arpa groups)

PD:<CPM.MODEM>
        2400$389.MDM.1          ASCII     1312  8F0EH
        FR21.LBR.1              BINARY   11776  6007H
        MNP-INTV.TXT.2          ASCII    12726  1D17H
        X25.LBR.1               BINARY  142080  923AH

PD:<CPM.PCPURSUIT>
        PCSAVE$.DOC.2           ASCII    16039  1F5CH
        PURSUIT.PCW.1           ASCII     4757  92CBH

PD:<CPM.RCPM>
        CHAT46.LBR.1            BINARY   28544  727EH
        LUX52.LBR.1             BINARY   88064  3BF7H
        PBBS-MSD.HQK.1          BINARY    6528  5402H
        PBBS3-01.FIX.1          BINARY    1152  030FH
        PBBS3-02.FIX.1          BINARY     768  3976H
        PBBS3-03.FQX.1          BINARY    1408  3313H
        PBBSCPM3.NQT.1          BINARY    1408  B736H
        PBBUTL-3.LBR.1          BINARY   11520  6C95H
        PBYE3-01.FIX.1          BINARY    1280  2A3AH
        PBYEHACK.ADD.1          ASCII     1063  F6E8H
        PCHAT01.MQC.1           BINARY    4992  866AH
        PCHAT11.MQC.1           BINARY    5376  4727H
        PHACKS01.LBR.1          BINARY   10240  78D4H
        SURVEY.LBR.1            BINARY   18688  A8BFH
        WHATSA-T.WIT.1          ASCII     3119  7E8BH
        XFRTABLE.LBR.1          BINARY   31104  E573H
        XMDM125.LBR.1           BINARY  114816  295DH

PD:<CPM.ROS>     (Remote BYE/BBS/XMODEM in Turbo Pascal - Z80 only)
        ROS-MAC.LBR.1           BINARY   87936  6288H
        ROS1K.LBR.1             BINARY   12160  26D3H
        ROS34.LBR.1             BINARY  128128  7B2EH
        ROSMISC.LBR.1           BINARY   30080  F86CH

PD:<CPM.SCREENGEN>
        SFGR.LBR.1              BINARY   60160  6008H

PD:<CPM.SQUSQ>
        TYPELN13.LBR.1          BINARY   10880  98AEH
        TYPELZ13.LBR.1          BINARY   31872  4BE1H

PD:<CPM.SYSUTL>
        CPM22PAT.LBR.1          BINARY    8064  AC4CH (official DR 2.2 pats)
        DOSLIKE.LBR.1           BINARY   14848  D688H (CP/M 2.2 MSDOS-like)

PD:<CPM.TOPS-20>
        TMODEM.MAC.401          ASCII   129054  AB9AH

PD:<CPM.TURBODOS>
        LUX53-TD.LBR.1          BINARY   51968  AB72H

PD:<CPM.TURBODOS-SIGI>  (Sigi Kluger Turbo-DOS utilities and patches)
        -READ.ME.1              ASCII     3461  079AH <--read this first
        ALLDIR.COM.1            BINARY    1408  C538H
        ALLDIR.DOC.1            ASCII      622  8C9AH
        ATTREM.AQ.1             BINARY    3968  51F4H
        ATTREM.CMD.1            BINARY    1024  67FDH
        ATTREM.COM.1            BINARY     512  D9E3H
        ATTREM.MAC.1            ASCII     2466  A627H
        BINDEC.A.1              ASCII     1185  BF92H
        BREAKO.MAC.1            ASCII     1492  EC06H
        CBTOD.AQM.1             BINARY    2688  3526H
        DCHECK.COM.1            BINARY    2304  6F40H
        DCHECK.DOC.1            ASCII      933  5961H
        DCHECK.MQC.1            BINARY    4480  02F1H
        DELALL.MQC.1            BINARY    4608  0C9DH
        DIRPAT3.COM.1           BINARY    6656  F4D8H
        DIRPAT3.MQC.1           BINARY   13824  2825H
        DIRPAT3.MQN.1           BINARY    9344  D256H
        DPINST.COM.1            BINARY    1536  81B7H
        DPINST.MQC.1            BINARY    1920  6CBAH
        DSKRAM.AQ.1             BINARY    3200  0DDBH
        DSKRAM.DQC.1            BINARY    2176  3514H
        DSKRAM.O.1              BINARY     512  B5CEH
        DUT.COM.1               BINARY    3584  4203H
        DUT.DO.1                ASCII       46  A4A8H
        DUT.MQC.1               BINARY    8192  D708H
        EMPTY.DOC.1             ASCII      335  70EEH
        EMPTY.MAC.1             ASCII     1104  04B2H
        EMUL.AQ.1               BINARY    8064  2237H
        EMUL.CMD.1              BINARY    2432  FD17H
        EMUL.DQC.1              BINARY    5248  2698H
        FANLED.AQ.1             BINARY   11904  2AB9H
        FANLED.DQC.1            BINARY    6528  7460H
        FANLED.MQC.1            BINARY    9344  D05FH
        FKEY.A.1                ASCII     1342  094BH
        FKEY.DQC.1              BINARY    2176  0253H
        FKEY.MAC.1              ASCII     1290  0426H
        FREE.MAC.1              ASCII      918  BF97H
        HEXDEC.A.1              ASCII      861  244DH
        HXDC24.MQC.1            BINARY    2176  5976H
        MENU.AQ.1               BINARY    7168  E6F6H
        MENU.GEN.1              ASCII        6  1B41H
        MENU.PAR.1              ASCII     2923  04FCH
        NSWPT.COM.1             BINARY   11648  F868H
        NSWPT.DQC.1             BINARY    3456  39FAH
        NSWPT.GEN.1             ASCII        7  F0BDH
        NSWPT.MQC.1             BINARY   40832  50D7H
        NSWPT.PAR.1             ASCII      490  9312H
        NSWPT.REL.1             BINARY   12544  32A4H
        PD.MAC.1                ASCII     1135  82A2H
        PDIR.DOC.1              ASCII      617  5062H
        PDIR.MAC.1              ASCII      676  4211H
        REMCH0.A.1              ASCII     1530  E217H
        REMCH0.MAC.1            ASCII     1354  EE91H
        REMCH1.A.1              ASCII     1530  4326H
        REMCH1.MAC.1            ASCII     1354  EF4FH
        REMDRV.AQ.1             BINARY    2816  C248H
        REMDRV.DQC.1            BINARY    6656  B95BH
        REMDRV23.MQC.1          BINARY    2688  B12EH
        RETBIT.MAC.1            ASCII      929  F23AH
        RS.COM.1                BINARY    2816  D8F0H
        RS.MQC.1                BINARY    5504  44FFH
        RS16.MQC.1              BINARY    3072  03CEH
        RTDS14.LBR.1            BINARY   84992  AA39H
        RTDS15UP.LBR.1          BINARY   33280  5A81H
        SUSPEND.COM.1           BINARY     640  9AE4H
        SUSPEND.MAC.1           ASCII     1168  548FH
        SYSTAT.DOC.1            ASCII     1251  ECF1H
        SYSTAT.MAC.1            ASCII     3608  2624H
        TCHECK.MAC.1            ASCII      937  2C90H
        TERMINAL.CFG.1          ASCII     1300  AB09H
        TIME.A.1                ASCII      794  CFC3H
        TIMECL.A.1              ASCII     1209  C053H
        TIMECL.DOC.1            ASCII      369  F0F7H
        TIMECL.MAC.1            ASCII     1358  6373H
        TIMECL.O.1              BINARY     256  F571H
        TIMECL1.MAC.1           ASCII     1358  0B06H
        TIMEDIF.AQ.1            BINARY    3840  6021H
        TIMEDIF.ASM.1           ASCII     4345  DFA6H
        TLOGOFF.COM.1           BINARY     896  C2F6H
        TLOGOFF.MQC.1           BINARY    2944  FE1EH
        TLOGON.COM.1            BINARY    4480  ED55H
        TLOGON.DO.1             ASCII       80  6B20H
        TLOGON.MQC.1            BINARY   10752  FED9H
        TLRS.COM.1              BINARY     640  F027H
        TLRS.MAC.1              ASCII     1160  F3D6H
        TSHELL.ANN.1            ASCII     6490  293CH
        TSHELL.DEF.1            ASCII     2720  B800H
        TSHELL.DO.1             ASCII      133  185BH
        TSHELL.FCN.1            ASCII     2609  62DBH
        TSHELL.IDS.1            BINARY     256  DBB7H
        TSHELL.MQC.1            BINARY    9216  BA32H
        TSHELL.SCR.1            ASCII      752  69FAH
        TYPEL.MQC.1             BINARY   11136  AA5AH
        UNDATE.REL.1            BINARY     512  58B1H
        USRSTAT.DOC.1           ASCII      452  B310H
        USRSTAT.MQC.1           BINARY    1792  8F14H
        WHO.MAC.1               ASCII      271  94CAH
        WILDEX.MAC.1            ASCII     1016  7D9FH
        WSPAT.ASM.1             ASCII     1474  D785H

PD:<CPM.TURBOPAS>
        MAP17.LBR.1             BINARY   19712  1BD6H
        RNF-PAS.LBR.1           BINARY  105088  60C2H (roff in Pascal)
        SORTDIR.PQS.1           BINARY   15104  3169H
        SQZTURBO.LBR.1          BINARY   59648  A571H (squeeze/unsqueeze)
        TP-LA1.LBR.1            BINARY   27776  A5D2H
        TRUN.LBR.1              BINARY   16896  1F0EH (chain programs)

PD:<CPM.VDOEDIT>    (Video editor)
        VDE211.LBR.1            BINARY   47232  3C91H
        VDE211H8.AQM.1          BINARY    8320  D9B1H

PD:<CPM.WSTAR>
        KEYSTOWS.AQT.1          BINARY   18560  E216H
        SAVESTAR.LBR.1          BINARY    6272  94CFH
        WS-MACRO.TQT.1          BINARY   21120  089FH (macros for WS)
        WSKEYS.MQS.1            BINARY   26240  3498H
        YANKBACK.TQT.1          BINARY    3840  A6D9H (yank killed txt)

PD:<CPM.ZMODEM>
        GZ..2                   ASCII       15  0792H
        RBSB.C.3                ASCII     7748  E717H
        RZ.1.2                  ASCII     6295  3EBAH
        RZ.C.2                  ASCII    24907  AA2BH
        RZ.MAN.3                ASCII     6978  7093H
        SZ.1.3                  ASCII     8834  9FE7H
        SZ.C.2                  ASCII    26587  3998H
        SZ.MAN.4                ASCII    10211  63E9H
        ZM.C.2                  ASCII     9913  3DB9H
        ZMODEM.H.2              ASCII     4400  F9F1H

--end--
 4-Aug-86 07:52:15-MDT,1135;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 4 Aug 86 07:52:05-MDT
Received: from wiscvm.arpa by AMSAA.ARPA id a012378; 4 Aug 86 9:01 EDT
Received: from (GA.OLS)ISUMVS.BITNET by WISCVM.ARPA on 08/04/86 at
  08:01:24 CDT
Date:      Sun,  3 Aug 86 20:40:06 CDT
To:  [e-mail]
MMDF-Warning:  Parse error in preceding line at AMSAA.ARPA
From:        Rob Olson <[e-mail]>
Subject:   Looking for a good C compiler

I am looking into learning C and I wondered if anyone would have
any suggestions on what compilers are worthwhile.  I have the
following requirements arranged in some sort of order of importance:

1.  Cheap.
2.  I would like a unit that is also available for the IBM PC because
    I am slowly rebuilding my system to be 8088 based.
3.  Something with at least a rotten tutorial since I've never used
    the language.

I have been looking into a compiler from MIX corp. and Dr Dobb's
small Compiler.  If anyone has any comments about these, I'd love to
hear them!

Thanks in advance,
Rob
<[e-mail]>

 4-Aug-86 09:09:33-MDT,1697;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 4 Aug 86 09:09:23-MDT
Received: from nadc.arpa by AMSAA.ARPA id a018813; 4 Aug 86 10:20 EDT
Date: 4 Aug 1986 10:08:57-EDT
From: [e-mail]
To: [e-mail]
Subject: Mix C+

There is a review of Mix C in the June 86 issue of BYTE magazine.  May I add
that I own a copy for CP/M-80 and have found that it works in general, though
a bit slower than Aztec C; the generated code is somewhat more bulky and runs
more slowly too.  It also has some strange characteristics for the unwary -
for example, string substitutions (from #defines) eat up the whitespace
following the token to be replaced, and if the replacement string does not
include a trailing comment, no whitespace is replaced. E.G.:

#define EXTERN extern
EXTERN int noodle;

expands to:

externint noodle;

Which, of course, generates a compiler error.  The solution is to add a comment
to the end of the #define with intervening whitespace:

#define EXTERN extern /**/

Also, it's treatment of comments is somewhat nonstandard - I believe something
like this blows off:

    /*commented out        inode++; /*increment node pointer*/

All in all, such things wouldn't bother you once you know about them, but they
are a pain if trying to port a program written for another compiler.  So for
$40.00, you probably get more than you pay for, though not everything you always
wanted, and there is a huge book included (not the best C tutorial I've
ever seen, but acceptable).  Suggest you read the Byte article for more
details on the cans and cannots.

Sincerely,
Frank Prindle
[e-mail]
 4-Aug-86 10:00:23-MDT,435;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 4 Aug 86 10:00:18-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a022022; 4 Aug 86 11:24 EDT
Date:     Mon, 4 Aug 86 11:18:57 EDT
From:     Lee A Butler (Space Telescope|mike) <[e-mail]>
To:       [e-mail]
Subject:  deletion

please remove me from the info-cpm mailing list

        Lee Butler
        [e-mail]
 4-Aug-86 10:54:56-MDT,955;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 4 Aug 86 10:54:32-MDT
Date:     Mon, 4 Aug 86 12:15:26 EDT
From:     David Towson (SECAD) <[e-mail]>
To:       Keith Petersen <[e-mail]>
cc:       [e-mail]
Subject:  Bad files in <CPM.TURBODOS-SIGI>

Keith - I just FTPed the whole directory and started unsqueezing all squeezed
files.  Two of them, "dpinst.mqc" and "nswpt.mac" failed to unsqueeze, and
caused a UNIX error.  The UNIX error is an artifact of the particular
unsqueezer program I am using, but the cause is real enough:  There is a
high-bit set in the name-field at the beginning of each file.  I used a UNIX
file-dumper program (od -h filename) to make this determination.  It is
interesting to note that the TOPS-20 unsqueezer is able to deal with this
situation.  I copied and unsqueezed the files on SIMTEL20 without difficulty.


Dave

 4-Aug-86 12:08:58-MDT,822;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 4 Aug 86 12:08:50-MDT
Received: from nosc.arpa by AMSAA.ARPA id a024885; 4 Aug 86 13:18 EDT
Received: by bass.ARPA (5.31/4.7)
    id AA11989; Mon, 4 Aug 86 10:19:12 PDT
Received: by trout.ARPA (5.31/4.7)
    id AA00638; Mon, 4 Aug 86 10:19:08 PDT
Date: Mon, 4 Aug 86 10:19:08 PDT
From: Alan Gordon <[e-mail]>
Message-Id: <[e-mail]>
To: [e-mail]
Cc: [e-mail]
Subject: Re: Kaypro 4 (1983) bug
In-Reply-To: Your message of Fri Aug  1 01:22:00 1986

-------
There is a dumb terminal program in the Kaypro section of the SIMTEL20
archives called FASTTERM.COM which will not drop characters, even at
9600 baud.

Al Gordon
[e-mail]
-------

 5-Aug-86 04:20:01-MDT,1735;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 5 Aug 86 04:19:53-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a005616; 5 Aug 86 5:45 EDT
Received: from USENET by SMOKE.BRL.ARPA id a004250; 5 Aug 86 5:45 EDT
From: dick gardner <[e-mail]>
Newsgroups: net.micro.cpm
Subject: Re: Text Editors
Message-ID: <[e-mail]>
Date: 4 Aug 86 15:45:05 GMT
Keywords:MIX C compiler, speed, size
To:       [e-mail]

I am not an expert on C compilers, but I did buy and use the MIX C and
found it to be adequate for the programs that I write. (Occasional)

The main concern about MIX C is that it compiles into psuedo-code, and
requires a run-time support package, which translates to a rather large
code size.  The run-time package can exist separately or be included in
the program.

Included in the package are utilities to optimize for size and/or speed.
MIX C programs run noticeably slower than those that create assembler
source, naturally.  A simple test of a software timing loop resulted in
code 1/4 the speed of Aztec C, for example.  Keep in mind that the
cost is about 1/3.

It is a full-blown implementation of C, with some nice enhancements.
The tutorial/manual is excellent, with sensible examples, and clear
explanations.

All in all, the package is certainly worth $59.

=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#

             Dick Gardner
             Eastman Kodak Co.
             Rochester, New York  14650
             [phone]
       UUCP: rochester!kodak!gardner

To err is human -- to really screw it up
           you need a computer!
=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#

 5-Aug-86 06:42:42-MDT,985;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 5 Aug 86 06:42:21-MDT
Received: from xerox.arpa by AMSAA.ARPA id a007769; 5 Aug 86 7:54 EDT
Received: from Burger.ms by ArpaGateway.ms ; 05 AUG 86 04:54:19 PDT
Sender: [e-mail]
Date: 5 Aug 86 04:53:52 PDT (Tuesday)
Subject: Re: wanted: PD DBMS or spreadsheet
From: [e-mail]
To: [e-mail]
cc: [e-mail], [e-mail]
In-Reply-to: king%dciem.uucp%BRL:ARPA:Xerox's message of 2-August-86
 (Saturday) 7:17:02 EDT
Reply-to: [e-mail]
Message-ID: <860805-045419-2096@Xerox>

If you're in to programming, Borlunds Turbo Pascal and Turbo Toolbox (or
Database Toolbox) is well worth the investment.  Mail order is cheapest.
The source code supplied will allow you to create B-Tree type indexes
that provide almost immediate look-up and access of very large files.

mak
 6-Aug-86 14:37:29-MDT,6746;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 6 Aug 86 14:36:38-MDT
Date:     Wed, 6 Aug 86 11:23:10 EDT
From:     Dave Towson (info-cpm-request) <[e-mail]>
To:       [e-mail]
Subject:  Posting software directly to info-cpm or net.micro.cpm:

Fellow CP/Mers - On the 19th of July I went on a one week vacation.  While I
was gone, a revolutionary thing happened on this list: messages with sizes in
the thirty to forty thousand byte range containing software encoded for
transmission via mail channels started showing up.  Now, I am beginning to
receive queries from info-cpm readers wanting to know what's going on.

     To understand this reaction, one must recall some fairly recent history:
For at least the last several years (the time during which I have been
maintaining this list), we have from time to time received requests from the
USENET community to not post messages containing tens of thousands of
characters because much of the USENET relies on dialup telephone connections
for transmission, and these telephone calls cost money.  Similar requests have
been heard from the DDN side because info-cpm is a mail-list, and some readers
have accounts that are subject to disk storage quotas.  I can personally
attest that this is a problem for some people, because I must from time
to time temporarily delete people from the list because they have gone on
vacation (or whatever) and their mail has built up to the point that their
disk quotas have been exceeded, causing all subsequent mail to be rejected
(which causes automated "nastygrams" to be returned to me as list maintainer,
and to originators of messages to info-cpm).

     But during this same time, a very important evolution has occurred:
"mail-only" connections have been established between the DDN and several
other networks.  And thus, a significant number of people using these networks
have begun receiving info-cpm (and net.micro.cpm via the automatic message
forwarding service provided by the Army Ballistic Research Laboratory).  Many
of these people are from overseas (England, Germany, Norway, Denmark, Sweden
and Holland come to mind).  And at a time when we are hearing that "CP/M is
dead", the enthusiasm of these people seems to suggest that some sort of
"rebirth" of CP/M may be occurring overseas.  Now imagine (if you're not one
of them) how frustrating it must be for these new readers to constantly read
messages describing the wealth of free software available from SIMTEL20 to
those of us using hosts connected to the DDN.  (Readers in the CSNET and
USENET, into which info-cpm has been relayed for some time, don't have to
imagine how this feels; THEY KNOW.)  As far as these "outsiders" are
concerned, SIMTEL20 might as well be on the planet Pluto.

     To deal with this situation as best I can, I have created separate
"welcome" messages to be sent to new info-cpm subscribers.  The one for the
DDN people contains the "archive blurb" (a sort of SIMTEL20 archives
handbook), while the one for non-DDN readers explains that the archives are
not available to them, and includes the nice writeup by Jeff Edelheit
describing alternate sources for much of this software.  Also, when I update
the blurb, I limit the distribution of the new version to DDN subscribers
so as not to burden the non-DDN people with something that can only be a
source of frustration.  I wish I could do more, but I don't know how.

     So given this situation, along come some folks who have worked up CP/M
versions of programs used in the UNIX world to transmit groups of files (the
functional equivalent of a CP/M archive) and encoded binary files via ordinary
mail channels.  AND all this stuff can be processed on UNIX machines before
downloading to a micro.  Suddenly, there is a ray of hope for the hordes of
"disenfranchised" readers, and from the limited reactions I have seen so far
THEY LOVE IT!

     Now the idea of sending software via mail and news-feed channels is not
new:  This has been going on in newsgroups like the USENET's net.sources for
quite a while.  But USENET sites can arrange to not receive selected
newsgroups if the disk storage or transmission costs are more than they wish
to bear.  I would not like to see info-cpm dumped into the "bit bucket" for
such a reason.  Frankly, I am surprised that I have not seen "screams of
anguish" from the USENET community in response to the recent high-volume
activity in info-cpm/net.micro.cpm.  Maybe everybody has fat wallets and huge
disks these days...

     So what to do?  It has been suggested that a separate USENET newsgroup,
something like "net.cpm.sources", could be established.  This would be a nice
solution for USENET, I think, because it would allow each site the option I
mentioned above.  But it would not do much for people in other networks.  What
other possibilities are there?  And is anyone willing to VOLUNTEER to provide
some sort of archive service in the other networks (I believe BITNET has
something going now, but I don't really know anything about it)?  And most
important, how do you feel about direct software distribution via info-cpm.

     I realize that asking these questions is likely to start a free-for-all,
but I think this is a really important issue.  It is, for example, conceivable
that the info-cpm <-> net.micro.cpm message forwarding service might have to
be discontinued if things get really out of control, but I in my opinion this
would be EXTREMELY UNDESIRABLE.  I am not implying that such a move is at
all imminent; it is NOT.  But we are faced with an important policy decision
concerning how we want our newsgroup to operate.  This issue is muddied
somewhat by the "government interest".  The US Army provides considerable
resources to maintain the SIMTEL20 archives, and info-cpm is one of the
channels through which the contents of those archives are made known to
government users.  So I think the Government has some rights regarding how
this list is operated, although I'm not sure what they are.  I hope Frank
Wancho will comment on this.

     So please send your comments and opinions regarding this matter to the
list as a whole, and not just to me as list maintainer.  I think this needs to
be an open discussion.  And please "make sure your brain is running before
putting your mouth (or fingers, in this case) in gear".  There are diverse
interests at stake here, and this is not a trivial question.  Let's do the
best we can.



                Looking forward to a good discussion,

                Dave Towson <[e-mail]>
                info-cpm list maintainer


 6-Aug-86 15:26:00-MDT,623;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 6 Aug 86 15:25:51-MDT
Received: from bbnccc.arpa by AMSAA.ARPA id a027295; 6 Aug 86 16:10 EDT
Date: Wed, 6 Aug 86  7:30:11 EDT
From: "Jack D. Hill" <[e-mail]>
Subject: foot notes for WS 3.3
To: [e-mail]

Does anyone know of a utility, PD or otherwise, that allows you to enter and
format foot notes in Word Star? I have version 3.3. While browsing through a
book store, I read in a Word Star tutorial that such a utility exists, but it
didn't mention where.
Thanks,
Jack Hill
jdhill@bbnccc

 6-Aug-86 15:27:57-MDT,2422;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 6 Aug 86 15:27:45-MDT
Date:     Wed, 6 Aug 86 15:55:52 EDT
From:     David Towson (SECAD) <[e-mail]>
To:       [e-mail]
Subject:  [Keith Petersen:  Bad files in <CPM.TURBODOS-SIGI>]

Fellow CP/Mers - A couple days ago I sent Keith Petersen a message (with a
copy to this list) describing what I perceived to be a problem with certain
squeezed files in the <CPM> archive.  Basically, when I tried to unsqueeze
these files on a BSD 4.2 UNIX system, I got a core dump.  The problem was
being caused by high-bits set in the filename field inside the squeezed file.
The contents of this field are read during unsqueezing, and determine the
filename under which the unsqueezed file will be stored.  When UNIX tried to
create files having high-bits set in the filename, it really "lost it".  Here
is Keith's reply to my message:


----- Forwarded message # 1:

Date: Mon, 4 Aug 1986  22:04 MDT
From: Keith Petersen <[e-mail]>
To:   David Towson (SECAD) <[e-mail]>
Subject: Bad files in <CPM.TURBODOS-SIGI>

Dave, the UnSQueezer program is supposed to strip off the high order
bits of the filenames in case they had any CP/M attributes set when
they were LBR'ed.  This was added to the specification for USQ some
time ago after some SysOps started using attributes inside LBRs for
certain controls over privacy and downloading by callers.

--Keith

----- End of forwarded messages

     The unsqueezer I have been using is from <UNIX.CPM>XUSQ107.C in the
SIMTEL20 <UNIX> archive.  A look at the source code reveals that the high-
bits of the filename characters are indeed not being stripped.  The fix is
very simple.  Here it is:

    p = origname;                /* Get original file name */
    do {                    /* send it to array */
        *p = getc(in);
        *p &= 0177;    <---------------- ADD THIS LINE
    } while(*p++ != '\0');


The new line goes after line number 136 (at least in my copy).

     I don't know whether a similar change would be desirable for XTYPE107.C
and/or XSQ107.C as I haven't looked.  If you would like to know whether the
unsqueezer you are using can handle filenames having CP/M attribute (high)
bits set, grab a copy of <CPM.TURBODOS-SIGI>DPINST.MQC from SIMTEL20 and try
to unsqueeze it.

     Thanks for your help, Keith.



Dave

 7-Aug-86 08:36:14-MDT,741;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 7 Aug 86 08:35:52-MDT
Received: from crdc-vax3.arpa by AMSAA.ARPA id a011311; 7 Aug 86 9:28 EDT
Date:     Thu, 7 Aug 86 9:27:22 EDT
From:     "Jack H. Smith" <[e-mail]>
To:       [e-mail]
Subject:  Posting software


    Dave,

        I see nothing particularly distasteful with the idea of
    posting software to the list. My only suggestion is that we
    devise a subject-naming convention that would give readers a
    clue as to which messages are software, etc.

        This way the readers could look at the headers and see
    if they want to read them or delete them.

                    More later,

                    Jack H. Smith


 7-Aug-86 09:28:48-MDT,588;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 7 Aug 86 09:28:39-MDT
Received: from wiscvm.arpa by AMSAA.ARPA id a014588; 7 Aug 86 10:32 EDT
Received: from (PFENNIGE)CGEUGE51.BITNET by WISCVM.ARPA on 08/07/86 at
  09:31:47 CDT
Date: 7 AUG 86 10:48-N
From:  [e-mail]
To:  [e-mail]
Subj: RAM expansion modules for C128

Can anyone tell me from where can I obtain the circuit diagram for the 128k
or 512k versions of the RAM expansion modules for the Commodore 128. Many
thanks in advance.
 7-Aug-86 09:44:17-MDT,1454;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 7 Aug 86 09:44:11-MDT
Received: from nadc.arpa by AMSAA.ARPA id a016016; 7 Aug 86 11:13 EDT
Date: 7 Aug 1986 11:06:43-EDT
From: [e-mail]
To: [e-mail]
Subject: re: Posting software

What is distasteful about posting software to the list are all the negatives
that Dave mentioned plus:

Software ends up being "kept" in two places and in two different forms.  Thus
DDN users (who may have just joined the group and haven't received previous
mail) must not only "look" at the CP/M,CPMUG,and SIGM directories on SIMTEL
where software is stored in it's natural form (files), but must also "look"
for more software embedded throughout the mail archives.  One cannot, un-
fortunately, even if he knew the subject line or date of a pertinent mailing
which contained software, ftp a single mail item from the mail archives, but
must retrieve a whole year's mail and then edit through it to separate out
the software of interest.  Also, this form of storage is very inefficient:
instead of taking up less space than the original file (i.e. by using sq, lu,
or arc), software ends up taking much *more* space than the original file
because it's encoded.  In other words, though there may be reasons to do
it for the non-DDN community, it is clearly detrimental to the DDN side.

Sincerely,
Frank Prindle
[e-mail]
 7-Aug-86 11:14:13-MDT,920;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 7 Aug 86 11:14:05-MDT
Received: from nadc.arpa by AMSAA.ARPA id a017133; 7 Aug 86 12:03 EDT
Date: 7 Aug 1986 11:56:01-EDT
From: [e-mail]
To: [e-mail], [e-mail]
Subject: re: [Keith Petersen: Bad squeezed files....]

Gee, Keith, I've been using the unsqueezer from <cpm.squ-port> it seems like
forever, and it sure doesn't strip off the high bit from file name characters,
and this is the first file I've heard of it doesn't work with.  With this
program, under UNIX 4.1BSD, you get a file name with a ? in it that you can't
delete without writing a program to unlink it!  Are you implying that the
portable "usq" needs to be updated to be compatible with newer "sq" programs?
Does this problem affect any version of "usq" running under CP/M?

Frank Prindle
[e-mail]

 7-Aug-86 15:29:25-MDT,1281;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 7 Aug 86 15:28:58-MDT
Received: from simtel20.arpa by AMSAA.ARPA id a000743; 7 Aug 86 16:38 EDT
Date: Thu, 7 Aug 1986  14:37 MDT
Message-ID: <[e-mail]>
From: [e-mail]
To:   [e-mail]
Cc:   [e-mail], [e-mail], [e-mail]
Subject: Posting software
In-reply-to: Msg of 7 Aug 1986  09:06-MDT from prindle at nadc.ARPA

Frank has brought up a very important point.  The INFO-CPM mail
archives are also stored here (in PS:<ARCHIVES.CPM>) from Day 1 (less
some holes), completely unedited, except to occassionally split the
current file into "manageable" chunks.  We also hold the mail archives
for 18 other mailing lists.  The intent is to keep all archives
online.  However, with disk space currently at a premium, the
duplication would quickly use up whatever's left.

So, from our standpoint, we would much rather prefer a new spin-off
list be formed, ala net.sources or mod.sources, perhaps named either
net.micro.cpm.sources or net.sources.cpm or mod.sources.cpm, or
whatever is correct by the prevailing convention(s), and leave
net.micro.cpm off that newsgroup, please.

--Frank
 7-Aug-86 20:46:39-MDT,1017;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 7 Aug 86 20:46:33-MDT
Received: from acc.arpa by AMSAA.ARPA id a001714; 7 Aug 86 20:18 EDT
Date: 7 Aug 86 17:04:00 PST
From: [e-mail]
MMDF-Warning:  Parse error in preceding line at AMSAA.ARPA
Subject: mailing software
To: info-cpm <[e-mail]>
cc: [e-mail]
Reply-To: [e-mail]
MMDF-Warning:  Parse error in preceding line at AMSAA.ARPA

With all of the wizzards out there, there aught to be
a demon that accepts mail with a path/filename in it.
This demon takes the path/filename, goes into the simtel20
archive, gets the file, encodes it, and mails it back out.
The only person effected, is the requestor. Is something like this
possible? even if only parts of it are demonable, maybe it
would be much easier for someone to keep up?
    I'm just a hardware type, stuck here in the
real world, so one of you software types will have to answer this.
    [e-mail]

------
 8-Aug-86 02:32:53-MDT,1790;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 8 Aug 86 02:32:45-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a002982; 8 Aug 86 3:57 EDT
Received: from USENET by SMOKE.BRL.ARPA id a003811; 8 Aug 86 3:45 EDT
From: Ross Alford <[e-mail]>
Newsgroups: net.micro.cpm
Subject: Re: Kaypro question
Message-ID: <[e-mail]>
Date: 6 Aug 86 04:18:25 GMT
To:       [e-mail]


Your question re Kaypro-->PClone modification is something I've
wondered about.  The SWP board is more useful as a ramdisk than as
a MSDOS system--I have the 256k version, and it's great under CP/M,
but almost completely IBM-uncompatible, and there is very little
truly generic software around for MSDOS.  However, just because SWP
hasn't done it doesn't mean it can't be done:  A Kaypro provides
almost all of the parts you would need to build a PClone, except for
the motherboard--a nice sturdy case, power supply, keyboard (which
would need either modification or a tricky BIOS), two disk drives,
and an external-synch monitor.  It also has a large base of installed
systems, many of the owners of which are feeling that the world is
passing them by.  A clever hardware person ought to be able to install
one of these 'little-board' style all-in-one (serial, parallel
interfaces and pseudo color- or mono- graphics adapter all on the
board) motherboards in a Kaypro case for little more than the cost of
the board.  A REALLY clever hardware/software person could probably
even build in Z80 support so the Kaypro could continue to fulfill
its original role.  I suspect that a kit of this sort could sell
briskly for around $400-500 and make someone a mint.

Ross Alford
   ...mcnc!ecsvax!alford
 8-Aug-86 03:30:52-MDT,1443;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 8 Aug 86 03:30:40-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a002974; 8 Aug 86 3:54 EDT
Received: from USENET by SMOKE.BRL.ARPA id a003736; 8 Aug 86 3:42 EDT
From: Jay Denebeim <[e-mail]>
Newsgroups: net.micro.cpm
Subject: Re: Kaypro question
Message-ID: <[e-mail]>
Date: 5 Aug 86 13:41:36 GMT
To:       [e-mail]


    The answer to your question is 'sort of'.  SWP makes (made?) a piggy
back board that contained an 8088  and 256/512K of memory.  It gave you a ram
disk in Kaypro mode, and allowed you to run MS-DOS on the 8088.  NOTE this does
not mean IBM compatible.  It had no graphics, and the memory map doesn't look
at all like the IBM.  It will run MS-DOS software, not IBM software.  This
constitutes around 10% of the total IBM software.  WordStar 3.0 would run, but
not 3.3, DBase II, but not DBase III etc.  The reason for this is the IBM is
*SLOW* and people found the only way to get decient speed out of the beast  was
to blow the DOS away and drive the hardware directly, added to this MS-DOS has
no graphics support in it, and you'll see that not very much IBM software is
going to run on the thing.

--
Jay Denebeim                "One world, one egg, one basket."
UUCP:  {seismo,decvax,ihnp4}!mcnc!rti-sel!ethos!jay
BBS:   Deep Thought, ZNode #42 300/1200/2400 919-471-6436
 8-Aug-86 04:35:03-MDT,1479;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 8 Aug 86 04:34:55-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id aa03721; 8 Aug 86 5:58 EDT
Received: from USENET by SMOKE.BRL.ARPA id a007425; 8 Aug 86 5:48 EDT
From: Bdale Garbee <[e-mail]>
Newsgroups: net.micro.cpm
Subject: Re: Can Ampro R/W other floppies?
Message-ID: <[e-mail]>
Date: 7 Aug 86 02:44:17 GMT
To:       [e-mail]

In article <[e-mail]> [e-mail] (Tim Born) writes:
>If you
>have twiddled with the Ampro's disk formats before, please let me know what
>your experience has been.

I have an Ampro Little Board, and have read and written a wide variety of
disks on it.  Don't know about the ATT box, it came out since I stopped using
that machine as my primary (own a unix box now, you know how it is...).  I
wish you luck with the Apple disks though, the controller uses an entirely
different concept for storing information on the disk.  I've not seen a
standard disk drive ever be able to read/write from one.  I worked for a
dealer for a while, and so aquired a bunch of apple hardware.  Neat, but
very incompatible with the rest of the world.
--


Bdale Garbee, N3EUA
uucp: {bellcore, crash, hp-lsd, hpcsma, pitt, symmetric, vixie}!winfree!bdale
arpa: [e-mail]    phone: [phone] h, 303/590-2868 w
fido: sysop of 128/18        packet: n3eua @ wb0blv, Colorado Springs
 8-Aug-86 04:51:02-MDT,528;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 8 Aug 86 04:48:42-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a003867; 8 Aug 86 6:18 EDT
Received: from USENET by SMOKE.BRL.ARPA id a007954; 8 Aug 86 5:57 EDT
From: Trey Chapman <[e-mail]>
Newsgroups: net.micro.cpm.ctl
Subject: newgroup net.micro.cpm
Message-ID: <[e-mail]>
Date: 7 Aug 86 12:07:57 GMT
Control: newgroup net.micro.cpm
To:       [e-mail]

This is net.micro.cpm.
 8-Aug-86 05:19:50-MDT,2550;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 8 Aug 86 05:19:34-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a003721; 8 Aug 86 5:58 EDT
Received: from USENET by SMOKE.BRL.ARPA id a007419; 8 Aug 86 5:48 EDT
From: Bdale Garbee <[e-mail]>
Newsgroups: net.micro.cpm
Subject: Re: Looking for a good C compiler
Message-ID: <[e-mail]>
Date: 6 Aug 86 13:58:14 GMT
To:       [e-mail]

In article <[e-mail]> [e-mail] (Rob Olson) writes:
>I am looking into learning C and I wondered if anyone would have
>any suggestions on what compilers are worthwhile.
> ...
>I have been looking into a compiler from MIX corp. and Dr Dobb's
>small Compiler.  If anyone has any comments about these, I'd love to
>hear them!

We used the MIX compiler for the PC in a consulting job a while back, and were
not very happy with it.  I wasn't using it myself, so comments are all at
least second hand, but I think the docs were poor, and the compatibility with
other C compilers seemed to be lacking.  Again, this was about a year ago, and
I wasn't the one hacking with it.

SmallC is fun, and a neat way to learn the language, but I feel it is
insufficient for doing any "real", large applications.  Sources have been
posted a couple times, and I'm sure you can get an executable by asking
around.

I used the C/80 compiler for CP/M for quite a while, and was pretty happy with
it.  It can be purchased with the floating point stuff and a good tutorial for
about $100 from several places.  I got mine from Sprite Software, I think.

Currently, the compiler I use the most is the Aztec family from Manx.  The
fact that versions are available for a wide variety of targets is a big plus.
I've got the CP/M and MS-Dos versions, both seem to work pretty well.  Good
correlation with the 4.2bsd compiler, and a fair set of runtimes.
Unfortunately, Aztec compilers are NOT cheap.

In any case, get a copy of Kernighan and Ritchie's "The C Programming
Language"... there may be better tutorials around, and there may be more
complete references for modern compilers, but my graphic-designer girlfriend
learned C with it... and gave it high marks for understandability.

--


Bdale Garbee, N3EUA
uucp: {bellcore, crash, hp-lsd, hpcsma, pitt, symmetric, vixie}!winfree!bdale
arpa: [e-mail]    phone: [phone] h, 303/590-2868 w
fido: sysop of 128/18        packet: n3eua @ wb0blv, Colorado Springs
 8-Aug-86 06:21:12-MDT,919;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 8 Aug 86 06:21:03-MDT
Received: from xerox.arpa by AMSAA.ARPA id a005088; 8 Aug 86 7:33 EDT
Received: from Riesling.ms by ArpaGateway.ms ; 08 AUG 86 04:33:30 PDT
Sender: [e-mail]
Date: 8 Aug 86 04:32:58 PDT (Friday)
Subject: Re: foot notes for WS 3.3
From: [e-mail]
To: [e-mail]
cc: [e-mail], [e-mail]
In-Reply-to: jdhill%CCC.BBN:COM:Xerox's message of 7-August-86
 (Thursday) 4:40:29 EDT
Reply-to: [e-mail]
Message-ID: <860808-043330-1815@Xerox>

Jack, I beleive that StarIndex by MicroPro is the utility that you're
looking for.  It uses dot prompts like Mailmerge to do its thing.  I
assume that you're aware that you can assign a footer message in
WordStar using a ".fo" dot command.

Mike
 8-Aug-86 18:18:08-MDT,1597;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 8 Aug 86 18:17:55-MDT
Received: from mit-ai.arpa by AMSAA.ARPA id a000368; 8 Aug 86 19:49 EDT
Date: Fri,  8 Aug 86 19:52:33 EDT
From: "Michael A. Patton" <[e-mail]>
Subject:  Posting software directly to info-cpm or net.micro.cpm:
To: [e-mail]
cc: [e-mail], [e-mail]
In-reply-to: Msg of Wed 6 Aug 86 11:23:10 EDT from Dave Towson (info-cpm-request) <cpmlist at AMSAA.ARPA>
Message-ID: <[AI.AI.MIT.EDU].81139.860808.MAP>


It seems to me that there is a simple solution (if everyone goes
along).  That is to split the source distribution on Usenet off from
the main list (call it net.micro.cpm.source or net.source.cpm or
whatever they want to use), then to gateway that list in the same way
that the main list is now, but as a seperate list.  All of the non-DDN
subscribers will probably want to be on the list as well as some on
the DDN side.  It would also be useful if someone in the DDN world
would extract useful things and submit them to the archive, but I
suspect the more useful entries will end up there eventually anyway.

A more elaborate form of this might be to allow some automated
procedure to extract items from the "sources" list and keep them
somewhere for a while.  Then people submitting source could send a
note to the main list and DDN types could get a copy of useful stuff
without being required to receive and store it all.  This is similar
to the way many UNIX (tm) sites handle net.sources now.

Mike Patton

 8-Aug-86 21:24:57-MDT,582;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 8 Aug 86 21:24:52-MDT
Received: from mit-ai.arpa by AMSAA.ARPA id a000714; 8 Aug 86 22:55 EDT
Date: Fri 8 Aug 86 22:24:30-EDT
From: Mark Becker <[e-mail]>
Subject: Re: TVX source code
To: [e-mail]
Message-ID: <[e-mail]>

[Sacrifice to the line eater]

My thanks to all who informed me the TVX source code is available in
the SIMTEL20 archives, specifically in:

    PD:<MSDOS.TVX-EDITOR>

Mark
-------
 8-Aug-86 22:42:15-MDT,6804;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 8 Aug 86 22:41:48-MDT
Date:     Sat, 9 Aug 86 0:10:44 EDT
From:     Dave Towson (info-cpm-request) <[e-mail]>
To:       [e-mail]
Subject:  [prindle:  access to SIMTEL20 from other nets]

Fellow CP/Mers - Thanks to all who have contributed to this discussion so
far.  The comments have all been quite thoughtful and reasonable, in my
opinion.  With this note, I am relaying a message sent to me at the list
maintainer's address for the reason stated therein.  This message, like some
others, suggests an approach that would require the development of some new
software.  Assuming that a host to run some special software (not necessarily
exactly as described here, but something new) were available, does anyone care
to volunteer to write such software?


Dave


----- Forwarded message # 1:

Received: from nadc.arpa by AMSAA.ARPA id a013593; 7 Aug 86 10:11 EDT
Date: 7 Aug 1986 10:07:44-EDT
From: prindle@NADC
To: cpmlist@amsaa
Subject: access to SIMTEL20 from other nets

Dave,
I am sending this to you rather than the whole list because:

1. It is long.
2. It may be totally out in left field!

If you think it has any merit, then by all means post it to INFO-CPM and/or
INFO-ADA.  But if you think I'm crazy, tell me so, 'cause I still have plenty
to learn about networks.

Incidentally, if for no other reason, CP/M re-birth may be attributed partially
to the Commodore 128.  That's certainly why I'm here!

Thanks,
Frank Prindle

--------------------------------Cut Here--------------------------------------
I know I have gotten requests to help non-DDN people get selective pieces of
software from the SIMTEL20 archives.  To do this manually, while tolerable in
extreme moderation, is impossible on any sort of large scale.  On the other
hand, wholesale distribution of software over the INFO-xxx mailing lists is
just not practical.

There is, perhaps, a technical solution to the problem of how to allow non-DDN
network users to submit software to, and extract software from, the SIMTEL20
public domain archives (CP/M, MSDOS, UNIX, and ADA). First let's work up to
the solution with some observations:

First -

DDN hosts seem quite capable of receiving mail from, and mailing to, hosts on
other networks through a fairly extensive network of relay sites.  Although
there seem to be a variety of syntax variations, the following form (from the
DDN side) seems more or less universally understood:

    mail [e-mail]

where "relayhost" has access to both "mydomain" and "hisdomain" networks.

 (e.g.) mail [e-mail]

I don't know the details of mail syntax from other networks to get the mail to
a relay site, but it obviously can be done, and if it gets to a relay addressed
to someone%somewhere.arpa, it will no doubt make it to it's DDN destination.
(This will undoubtedly be somewhat complicated soon, as there is a movement
afoot to have DDN hosts adopt more exotic domain names as opposed to just
plain ".arpa".  This will just blow off about half the mailers and mail
servers in the world for a few months until all the software gets modified to
handle the new domain syntax).

Second -

The "person" to whom mail is addressed may, in actuality, be an automaton
(e.g. a re-distribution list) as opposed to a real person who sifts through
mail.  Thus, properly formatted mail might easily be processed as input to
a computer program, the actions of which would be directed by the contents
of the mail.  A simple example of this would be a periodic batch demon
checking a user's mailbox every hour or so and sending out a canned reply
to the sender: SORRY, I AM OUT OF TOWN FOR TWO WEEKS - WILL REPLY 8/16/86.
Of course, the demon would have to have a few ounces of intelligence; for
example, it would be most unkind to send such a reply to a distribution list
like INFO-CPM, for this would start an endless loop (don't laugh, it has
happened!).

Now, for the potential solution -

Instead of a non-DDN user posting an encoded form of his software to the entire
world, he would mail his encoded software (adhering to specific formatting
rules) to a DDN "server" mailbox.  If "uuencode" were used, perhaps it would
be best if this server were on a UNIX machine rather than TOPS-20, but other
encoders/decoders (e.g. public domain atob/btoa) could be used.  The server
would scan the sender's message, sense that it was a submission and properly
formatted, send an acknowledgement back to the sender, and queue the decoded
files for "ftp" transmission to SIMTEL20 archive administrators (the last step
would not be necessary if the "server" were SIMTEL20 itself).  When and if the
archive adminstrator put the software in the archives, he/she would notify the
original user by mail, who in turn could post a short note to the mailing list
abstracting the software and noting that it was now in the archives.

When a non-DDN user wished files or a directory from a particular archive,
he would again mail to the "server", this time formatted as a "software
request" rather than a submission.  The server would scan the sender's message,
sense that it was a software request, ftp the requested software from SIMTEL20,
encode it according to the rules, and mail it to the requestor.

When the "server" receives an ill-formatted message, notice to that effect is
simply returned to the sender.  A single server need not handle all the
SIMTEL20 archives, nor is it necessary for a single server to handle both
the submissions and the software requests for a single archive (i.e. sharing
the burden!).

But can it work? -

Now I'm not saying such an approach is without substantial technical risk or
complexity.  It obviously represents a potentially large increase in computing
resource burden to be absorbed by the administrator(s) of the server(s).  It
may also be administratively unacceptable to the DDN regulators or to the
regulators of the other networks.  It also may not work at all, for a variety
of technical reasons (e.g. mail messages on USENET are generally limited to
100000 bytes, so large files would have to be broken up).  By building a new
(and inefficient) File Transfer Protocol on top of the mail connections, it
probably borders on heresy!  Furthermore, interactions with "net.sources" and
other such special arrangements should be considered.  Finally, it represents
a lot of work to implement.

Nuff said - I'll ramble no further.  Perhaps this discussion should be moved
to INFO-NETS.
                        Frank Prindle
                        [e-mail]

----- End of forwarded messages
 8-Aug-86 23:01:34-MDT,1547;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 8 Aug 86 23:01:25-MDT
Date:     Sat, 9 Aug 86 0:33:02 EDT
From:     Dave Towson (info-cpm-request) <[e-mail]>
To:       [e-mail]
Subject:  [rbthomas:  Re: Posting software directly to info-cpm or net.micro.cpm:]

Fellow CP/Mers - Here is another message sent to the list maintainer's
address.  I see no reason why a separate DDN cpm sources list could not be set
up and gatewayed with the USENET.  But I am not keen on making the existing
info-cpm list the starting point for the new distribution.  I am open to
rebuttal, though.


Dave


----- Forwarded message # 1:

Received: from ru-caip.arpa by AMSAA.ARPA id a010087; 8 Aug 86 10:51 EDT
Received: by caip.rutgers.edu; Fri, 8 Aug 86 10:51:27 edt
Date: Fri, 8 Aug 86 10:51:27 edt
From: [e-mail] (Rick Thomas)
Message-Id: <[e-mail]>
To: [e-mail]
Subject: Re: Posting software directly to info-cpm or net.micro.cpm:
In-Reply-To: USENET article <[e-mail]>

Can a separate mailing list (gatewayed to the proposed separate usenet
newsgroup) be setup for sources only (info-cpm-sources???) Then people
could subscribe or not as they chose.  I would (personally) like to
see the initial list of recipients for the new mailing list be a clone
of the present info-cpm mailing list, but that could be worked out.

Rick Thomas
[e-mail]

----- End of forwarded messages
 8-Aug-86 23:20:43-MDT,1042;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 8 Aug 86 23:20:37-MDT
Received: from nosc.arpa by AMSAA.ARPA id a000206; 8 Aug 86 18:51 EDT
Received: by bass.ARPA (5.31/4.7)
    id AA03167; Fri, 8 Aug 86 15:13:54 PDT
Received: by cod.ARPA (5.31/4.7)
    id AA07235; Fri, 8 Aug 86 15:13:51 PDT
Message-Id: <[e-mail]>
Date: Fri, 8 Aug 86 13:51:49 PDT
From: Marc Wilson <crash!pnet01!pro-mercury![e-mail]>
To: pnet01!crash!noscvax![e-mail]
Subject: Re: Can Ampro R/W other floppies?
Cc: [e-mail]
Resent-Date:  Sat, 9 Aug 86 0:38:28 EDT
Resent-From:  [e-mail]
Resent-To:    [e-mail]

     The current AMPRO BIOS allows the reading of over 60 different disk
formats, but sadly, Apple is not among them. An Apple drive uses GCR coding,
rather than the MFM format that most drives use. I'm not saying that it's
impossible, but I don't think it can be done.

Marc Wilson
crash!pnet01!pro-mercury!mwilson@nosc
 8-Aug-86 23:35:18-MDT,820;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 8 Aug 86 23:35:13-MDT
Received: from nosc.arpa by AMSAA.ARPA id a001129; 9 Aug 86 0:45 EDT
Received: by bass.ARPA (5.31/4.7)
    id AA03875; Fri, 8 Aug 86 21:45:44 PDT
Received: by cod.ARPA (5.31/4.7)
    id AA15243; Fri, 8 Aug 86 21:45:42 PDT
Message-Id: <[e-mail]>
Date: Fri, 8 Aug 86 21:22:54 PDT
From: Matt Smiley <crash!pnet01![e-mail]>
To: crash!noscvax![e-mail]
Subject: Re:  Posting software directly to info-cpm or net.micro.cpm:

Being very new and inexperinced in this field, I would like some more
information on accessing the files at SIMTEL20. Is it true an ASCII file (such
as a .LBR file) can be sent to you in mail? I do not have on-line access to
SIMTEL20.
 9-Aug-86 00:13:41-MDT,714;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sat 9 Aug 86 00:13:35-MDT
Received: from wiscvm.arpa by AMSAA.ARPA id a001232; 9 Aug 86 1:42 EDT
Received: from (BW2)HARVARDA.BITNET by WISCVM.ARPA on 08/04/86 at
  13:10:11 CDT
Date:   Saturday, 2 August 1986, 13:05:03 EDT
From:     Bruce Waldman <[e-mail]>
To:  [e-mail]
Subject:   Bondwell CP/M computers

I have just seen an ad for a Bondwell model 12 for $399.  Anyone have any
experience with this portable?  Does it intrinsically emulate any common
CP/M machine?  Also a model 14 with double-sided drives and 128K for
$100 more.  Seem like bargains unless ..... ????

 9-Aug-86 04:00:59-MDT,920;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sat 9 Aug 86 04:00:51-MDT
Received: from wiscvm.arpa by AMSAA.ARPA id a001601; 9 Aug 86 5:32 EDT
Received: from (CADS074)CALSTATE.BITNET by WISCVM.ARPA on 08/07/86 at
  17:45:53 CDT
Date: Thu, 07 Aug 1986 15:25 PDT
From:   "Mr. Bill" <[e-mail]>
Subject: BDS C on an Apple //e
To:  [e-mail]
MMDF-Warning:  Parse error in preceding line at AMSAA.ARPA

   Can anyone out there help me in getting BDS C (ver. 1.50) working
on an Apple //e?  I'm running CP/M 2.23 on an ALS Z-card.  Everything
runs fine until the second phase of the compiler.  About 30 seconds
after phase two starts, the screen fills with garbage and then
hangs.  Any help would be appreciated.

                                     Bill Wood
                                     Bitnet:  CADS074@CALSTATE

 9-Aug-86 18:46:46-MDT,1296;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sat 9 Aug 86 18:46:40-MDT
Received: from uci-icsa.arpa by AMSAA.ARPA id a003322; 9 Aug 86 16:10 EDT
Received: from localhost by ICS.UCI.EDU id a001534; 9 Aug 86 13:09 PDT
To: "Mr. Bill" <[e-mail]>
cc: [e-mail]
cc: [e-mail]
Subject: Re: BDS C on an Apple //e
In-reply-to: Your message of Thu, 07 Aug 1986 15:25 PDT.
Date: Sat, 09 Aug 86 13:08:44 -0800
Message-ID: <[e-mail]>
From: Jerry Sweet <[e-mail]>


I have a related experience that might help.  It seems that when I
tried to install the 60K version of Microsoft CP/M on my Apple ][ Plus,
BDS C would roll over and croak.  I was forced to go back to 56K CP/M.
I hypothesize that in 60K CP/M, Microsoft folds the CCP (and possibly
other parts of CP/M) into the alternative 4K memory bank on the
language card, and BDS C makes direct use of memory locations or
routines in the CCP.

Conclusion: you must somehow switch the CCP in and out of the normal
address space during compilation in such a way that BDS C can make use
of both the CCP and the CP/M system services (a difficult, perhaps
impossible task), or use a 56K version of CP/M.

-jns
 9-Aug-86 18:47:00-MDT,862;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sat 9 Aug 86 18:46:52-MDT
Received: from mit-mc.arpa by AMSAA.ARPA id a003453; 9 Aug 86 17:50 EDT
Date: Sat 9 Aug 86 17:54:32-EDT
From: Mark Becker <[e-mail]>
Subject: Info Request - DTC 510A Winnie controller
To: [e-mail]
Message-ID: <[e-mail]>

Hello -

     I recently traded some hardware with a local and discovered a
Data Technology Corp DTC-510A controller plus User Manual in the
collection.

     If you've interfaced such a thing to a CP/M system, I would
appreciated your sending mail.  Before I go and lay out the $ for a
drive, I'd like to ask some questions.

     If there is enough interest, I can post a summary to the net.

Thanks in advance..

Mark
-------
 9-Aug-86 18:58:02-MDT,1207;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sat 9 Aug 86 18:57:53-MDT
Received: from ucb-vax.arpa by AMSAA.ARPA id a003299; 9 Aug 86 15:52 EDT
Received: by ucbvax.Berkeley.EDU (5.53/1.14)
    id AA26601; Sat, 9 Aug 86 12:52:46 PDT
Received: by jade.Berkeley.Edu (5.31 (CFC 4.21)/5.6.2)
    id AA02583; Sat, 9 Aug 86 12:52:42 PDT
Received: by amber.Berkeley.Edu (4.20/5.6)
    id AA09492; Sat, 9 Aug 86 12:52:41 pdt
Date: Sat, 9 Aug 86 12:52:41 pdt
From: [e-mail]
Message-Id: <[e-mail]>
To: [e-mail], [e-mail]
Subject: Re:  foot notes for WS 3.3

There exists a PD footnoting utility for WordStar called (not surprisingly)
FOOTNOTE.  It appeared in volume 34 of our library (Bay Area Kaypro Users and
Programmers, or BAKUP, 412 61st St., Oakland, CA 94609).  Our library disks are
available only to our members ($10 per year, $1.50 for a listing of the disks
in the library), but the DOC file with FOOTNOTE has the name of the author -
Eric Meyer, 427 N. Washington, Bloomington, IN 47401.

Hope this is of use.

Steve Willett ([e-mail])
BAKUP Librarian

 9-Aug-86 22:28:45-MDT,4106;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sat 9 Aug 86 22:28:29-MDT
Received: from simtel20.arpa by AMSAA.ARPA id a003949; 10 Aug 86 0:05 EDT
Date: Sat, 9 Aug 1986  21:58 MDT
Message-ID: <[e-mail]>
Sender: [e-mail]
From: Keith Petersen <[e-mail]>
To:   [e-mail], [e-mail]
Cc:   [e-mail]
Subject: Telenet PC Pursuit will not upload certain files

The following is relayed from GEnie's CP/M RoundTable.

--Keith Petersen
Arpa: [e-mail]
uucp: {ihnp4,allegra,cmcl2,dual,decvax,mcnc,mcvax,vax135}!seismo!w8sdz
GEnie Mail: W8SDZ
RCP/M Royal Oak: 313-759-6569

---forwarded message---
TO:       All PC Pursuit Users

WARNING:  PC Pursuit will not upload certain files!

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

As if the busy signals and disconnects were not enough (sigh),
listen to this...

Under certain circumstances, files may not be uploaded to a
remote system with Christensen ("XMODEM") protocol using the PC
Pursuit service of GTE Telenet.  In particular, the three-byte
ASCII sequence <CR, '@', CR> (binary <0DH, 40H, 0DH>) is ALWAYS
interpreted as an escape to Telenet command level.  If this
sequence occurs in an appropriate place within a file, that file
cannot be uploaded!  The typical effect with most file transfer
programs is the occurrence of repeated local timeout errors, and
an apparent loss of connection when the user returns to terminal
mode to attempt recovery after the transfer is aborted.

I have verified the above with Telenet customer service and
engineering representatives.  Their response was that this is an
unfortunate result of the established Telenet command structure,
and it is not likely that any attempt will be made to provide a
solution to this problem for PC Pursuit customers!  (Considering
the difficulty of making network connections at almost any hour
of the night, I'm sure there must be A LOT of us PC Pursuers out
there...  At $25 per month each, I had hoped we deserved a better
response than that.)

Note that this situation is unlikely to occur within an ASCII
text file produced on CP/M or MS-DOS systems, since CR is almost
always followed by LF in such files.  But it is certainly
possible within a binary (e.g. .COM) file.  (The high bit of each
byte is insignificant to Telenet, so there are actually eight
different 3-byte binary sequences which may cause this problem.)
Also, there is a small likelihood of this occurring even during a
text file transfer, due to the binary record count and checksum
or CRC bytes which are generated by the protocol.  From my own
experience, the problem seems most likely to occur within
SQueezed files.

As a possible workaround to this problem, I would suggest trying
either of the following:

1.  Change the file compression.  I.e., (un)SQueeze or (un)CRUNCH
    the file, as appropriate to its original form.  Then leave a
    message to the remote system's SysOp requesting that the file
    be restored after it is received.

2.  If you are using XMODEM-CRC mode, try Checksum mode (or vice-
    versa).  If you are using 1K-byte (YMODEM) transfers, try
    using the slower 128-byte transfers instead.  Either of these
    changes may allow recovery from a small class of situations
    which could cause the problem.

The following facts should also be noted:

1.  This problem occurs only with uploads.  Downloads from a
    remote system are not affected.

2.  Once such a file transfer has been aborted, you have NOT lost
    your connection to the remote system!  Simply issue the
    command CONT (continue) at the Telenet @ prompt.

I hope this information will save others the hours of aggravation
it has caused me.

                                Bob Freed
                                Newton Centre, MA
                                August 6, 1986

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
 9-Aug-86 23:09:20-MDT,2002;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sat 9 Aug 86 23:09:07-MDT
Received: from nosc.arpa by AMSAA.ARPA id a004006; 10 Aug 86 0:41 EDT
Received: by bass.ARPA (5.31/4.7)
    id AA06289; Sat, 9 Aug 86 21:42:05 PDT
Received: by cod.ARPA (5.31/4.7)
    id AA25637; Sat, 9 Aug 86 21:42:03 PDT
Message-Id: <[e-mail]>
Date: Sat, 9 Aug 86 19:34:18 PDT
From: Matt Smiley <crash!pnet01![e-mail]>
To: crash!noscvax![e-mail]
Subject: Re:   Bondwell CP/M computers

Yes, I owned a model 12 for a month or so before I picked up my Kaypro. I must
say it was an excellant machine. The thing is essentially a Kaypro 4-84, with
a 4 meg clock, two drives, and a 9" amber monitor. In addition you get
function keys, an external monitor output, and (in my case) WordStar,
DataStar, CalcStar, and a couple other Star's with complete documentation,
i.e. copies of Micro Pro's complete manuals. The cabinet design is far
superior to the Kaypro's. It is made of a thick plastic, with all the controls
(power, contrast, reset) on the front next to the monitor. The cord stores in a
compartment on the back, which, when closed, protects all the plugs, (monitor
output, 2 RS-232, 1 serial, power input). The only reason I didn't keep it was
that I needed double sided drives, which your $399 model probably doesn't have.
(although they *are* manufactured with DSDD drives, for what would have cost me
$400 more). It also comes with a program that allows it to read and write to
Kaypro II, Osbourne, and some other strange make disks, although it cannot
format Kaypro, etc.

I would avoid the model 14, which uses CP/M 3.0 like the Commodore 128. Not
that there's anything wrong with 3.0, it's just that there evidently isn't a
whole lot of machines that use it.

BTW, Kaypro is selling model 1's again for $595! You may want to look into one
of those. You can buy them directly from the factory at that price.
10-Aug-86 16:45:31-MDT,2338;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sun 10 Aug 86 16:45:18-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a005600; 10 Aug 86 18:11 EDT
Received: from USENET by SMOKE.BRL.ARPA id a003266; 10 Aug 86 17:43 EDT
From: Jim Gilbert <[e-mail]>
Newsgroups: net.micro.apple,net.micro.cpm
Subject: PCPI Applicard Tech Info
Message-ID: <[e-mail]>
Date: 7 Aug 86 16:48:43 GMT
To:       [e-mail]


I would like to obtain the following reference information for the PCPI
Applicard Z-80 processor and the accompanying CP/M implementation.
I think that Personal Computer Products Inc. was purchased by Micropro or
went out of business.

I know some people know this (employees of Empathy Software, former
PCPI employees), and there must be somewhere to write to obtain
at least some hardware reference information.

Now it gets boring:

    Apple View of Applicard:
        - use of standard slot-dependent addresses for scratch
          RAM, ROM, and interprocessor communication
        - interrupt daisy chain handling
        - dma daisy chain handling
        - location, size, and entry points of 6502 monitor
        - boot sequence
    Applicard view of itself and the Apple
        - RAM and ROM addressing/bank switching
        - i/o space resources
        - ports used to interface to 6502
        - boot sequence
        - writing and installing device drivers
    Hardware
        - schematics
        - meaning of the 2x4 and the 2x25 jumpers or expansion
          connectors

I have done various CP/M OEM ports, written drivers, spoolers, etc. and
am very familiar with all the insides of the Microsoft Softcard implementation.

I know I can figure all this out again by disassembling lotsa code.
And I can figure out the hardware by tracing the etch of
both sides of the board and reverse-engineering the schematics.  This is
just an extremely tedious process.

I would be willing to pay a modest amount, e.g. under $20 for significant
portions of the information mentioned.  I have no commercial interest in
any of this.  I am merely exploring this implementation.

Thank you kindly for your interest if you have read this far.  Any assistance
will be appreciated.


    Jim Gilbert
    FileNet Corporation
    3530 Hyland Ave.
    Costa Mesa, CA 92626

    ihnp4!trwrb!felix!jim
10-Aug-86 17:18:08-MDT,1409;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sun 10 Aug 86 17:17:55-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id aa05664; 10 Aug 86 18:28 EDT
Received: from USENET by SMOKE.BRL.ARPA id a004610; 10 Aug 86 18:13 EDT
From: William Swan <[e-mail]>
Newsgroups: net.micro.cpm
Subject: Re: Looking for a good C compiler
Message-ID: <[e-mail]>
Date: 8 Aug 86 15:44:59 GMT
To:       [e-mail]

In article <[e-mail]> [e-mail] (Bdale Garbee) writes:
><[e-mail]> [e-mail] (Rob Olson) writes:
>>I am looking into learning C and I wondered if anyone would have
>>any suggestions on what compilers are worthwhile. [...]
>>I have been looking into a compiler from MIX corp. and Dr Dobb's
>>small Compiler.  If anyone has any comments about these, I'd love to
>>hear them!
>We used the MIX compiler for the PC in a consulting job a while back, and were
>not very happy with it. [...]

I have heard that MIX C is slow, and has a *huge* run-time package.

I've been using BDS C, which works pretty well, but the i/o is non-standard.
It has a few other shortcomings, some of which have been quite irritating,
but all-in-all, it works.

I've a friend who's been using Ecosoft C (for Z80), and rates it quite highly.
It's not cheap, but it's apparently pretty good.
10-Aug-86 17:37:31-MDT,1095;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sun 10 Aug 86 17:37:24-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a005664; 10 Aug 86 18:28 EDT
Received: from USENET by SMOKE.BRL.ARPA id a004508; 10 Aug 86 18:11 EDT
From: Steve Neighorn <[e-mail]>
Newsgroups: net.micro.cpm,net.micro.trs-80,net.wanted
Subject: LNW-80 Owners?
Message-ID: <[e-mail]>
Date: 7 Aug 86 18:53:43 GMT
To:       [e-mail]

The LNW-80 is a Radio Shack TRS-80 Model 1/CPM computer rolled into one box.
LNW went out of business awhile ago, and I am wondering if there are any
other fellow LNW'ers on the net.

           We have been orphaned, but we can still band together!

Send me net mail if you have one of these little white boxes and we'll see
what we can get going.
--
Steven C. Neighorn               tektronix!reed!percival!qiclabs!neighorn
Portland Public Schools      "Where we train young Star Fighters to defend the
[phone] ext 229          frontier against Xuir and the Kodan Armada"
10-Aug-86 17:44:18-MDT,2194;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sun 10 Aug 86 17:44:09-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a005666; 10 Aug 86 18:29 EDT
Received: from USENET by SMOKE.BRL.ARPA id a004675; 10 Aug 86 18:16 EDT
From: dick gardner <[e-mail]>
Newsgroups: net.micro.cpm
Subject: Re: Looking for a good C compiler
Message-ID: <[e-mail]>
Date: 8 Aug 86 15:48:23 GMT
To:       [e-mail]

I've used the MIX C compiler under CP/M and find it to be OK for
light and ocassional use.  I wouldn't recommend it for a developer.

It does not compile to assembler, but rather to psuedo-code.  It
creates somewhat large programs, since the the run-time support
must be included (or exist on the system separately)  It doesn't
compare in speed, since it runs sort of like it was an interpreter.
It is complete, with some nice enhancements. The tutorial/manual
is pretty good.  There is a version of MIX C available for the PC.

Since you mentioned the PC, I have just bought a Turbo clone, and
got a copy of ECO-C88 from ECOSOFT for $59.  This is a pretty nice
package, at least for my needs.  It does limit you to a small
memory model, though.(64k)  The manual is adequate, but not great.
The compiler is quite good -- fairly fast and complete.  You must
use the IBM Linker (no problem for me since I'm using PC-DOS).
The only problem I've found is that it is a little difficult to use
on a 'floppy-only' machine.  The size of the libraries means swapping
disks alot.  Since I've gotten my 10 megger, though, it simplified
things greatly. I'm quite happy with this package.
I DO think that I would buy something else if I was in business
writing C programs. (just in case I needed a larger memory model)

I hope this information is helpful.


=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#

             Dick Gardner
             Eastman Kodak Co.
             Rochester, New York  14650
             [phone]
       UUCP: rochester!kodak!gardner

To err is human -- to really screw it up
           you need a computer!
=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#

10-Aug-86 23:22:19-MDT,1459;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sun 10 Aug 86 23:22:13-MDT
Received: from brl-aos.arpa by AMSAA.ARPA id a007327; 11 Aug 86 0:50 EDT
Received: from nosc.arpa by AOS.BRL.ARPA id a011362; 11 Aug 86 0:43 EDT
Received: by bass.ARPA (5.31/4.7)
    id AA09079; Sun, 10 Aug 86 21:40:23 PDT
Received: by cod.ARPA (5.31/4.7)
    id AA06747; Sun, 10 Aug 86 21:40:21 PDT
Message-Id: <[e-mail]>
Date: Sun, 10 Aug 86 21:18:48 PDT
From: Irwin Hom <crash!pnet01![e-mail]>
To: crash!noscvax![e-mail]
Subject: Re: PCPI Applicard Tech Info
Cc: crash!noscvax!info-cpm@BRL

No, PCPI did not go out of business.  The last I heard, they were phasing
out on Apple stuff and concentrating on the IBM market.  The PCPI card
alone contains 64k of onboard memory.  The 2x5 and 2x25 expansion pins
are used to piggy-back another memory module onto the Appli-Card.  Each
memory module can contain up to 128k of memory.  Only two modules max
may be added, though.  This gives you a RAM disk with a 222k workspace,
-2k for the directory, and - 32k for software management.

PCPI offers an OEM package for about $50 that gives the technical info you
need.  Also included are two disks which contains sample drivers, a 6502
cross assembler and loader.  You might want to contact them to see if this
package is still offered.

--Irwin Hom     ...crash!ihom!pnet01!@nosc
10-Aug-86 23:26:12-MDT,2079;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sun 10 Aug 86 23:26:05-MDT
Received: from lll-mfe.arpa by AMSAA.ARPA id a007344; 11 Aug 86 0:55 EDT
Date: Mon, 11 Aug 86 00:31 EST
From: [e-mail]
Subject: Gilbert PCPI Query
To: [e-mail]

From:    <[e-mail]>   (Richard C. Secrist)
Date:    Mon, 11-AUG-1986 00:31 EST
To:      [e-mail]
Message-ID: <[OAK.SAINET.MFENET].A4B456E0.008F341A.SECRIST>
Header-Disclaimer: I don't like my headers either.
Quote: "May your future be limited only by your dreams." -- Christa McAuliffe
Organization:  Science Applications Int'l. Corp., Oak Ridge, Tenn., USA
CompuServe-ID: [71636,52]
X-VMS-Mail-To: CPM

Just a short note on your
PCPI query - perhaps more
will follow very soon.

PCPI is still alive and
well, although the PCPI
Applicard is no longer
marketed.  They do still
support the card, however,
and do a nice job of it.

Much of the info you
desire is in the OEM
support package with
that is
available from PCPI.
It includes sample drivers
for all device classes,
a 6502 assembler that
runs under the Z80, and
other software information.

The OEM package was about
$35 or $40.

There is very little about
the PCPI hardware in
print.  The best sources
of this are calling PCPI
technical support directly
or Laing Electronics (or
the Laing BBS).  The PCPI
technical people (make
sure you ask for tech
support) were very nice
about answering all of
my questions, and in
as much detail as I cared
to pursue on the hardware
side of things.  Don't
press on the software,
buy the OEM package.  There
are people on this list
who have had a fair amount
of experience with both.

PCPI
1150 W. Bernado Ct.
San Diego, CA 92127
619/485-8411

Laing Electronics BBS
714/534-1547

[I am a satisfied PCPI
app
Applicard owner and have
no affiliation with the
Arizona State Department
of Argiculture.]

r c s
[e-mail]
11-Aug-86 07:18:34-MDT,1777;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 11 Aug 86 07:18:16-MDT
Received: from decwrl.arpa by AMSAA.ARPA id a013193; 11 Aug 86 8:47 EDT
Received: from DEC-RHEA.ARPA (rhea.dec.com) by decwrl.DEC.COM (4.22.05/4.7.34)
    id AA28818; Mon, 11 Aug 86 05:48:12 pdt
Message-Id: <[e-mail]>
Date: 11-Aug-1986 0843
From: "Sink me! 'Twas lovely, havin' this little chat!" <[e-mail]>
To: [e-mail]
Subject: Another exotic WordStar query

I'm trying to use MailMerge to assemble letters containing multiple lines of
information extracted from multiple data files, without success.

I have two data files, one containing a list of people who are to be included
in a seminar, and the other containing a list of the people who will moderate
the seminar (actually three or four different seminar groupings, all to run
concurrently).  I need to generate two sets of letters:

1.  Extract a data record from list 1 to be the addressing information, and a
    data record from list 2 to tell the addressee when and where the seminar
    is to be, and by whom it will be moderated.  (For a seminar with three
    groups, this set will contain between 15 and 18 letters.)

2.  Extract a data record from list 2 to be the addressing information, and
    six selected records from list 1, to tell the addressed moderator the
    names, etc., of the people who will be in his or her group.  (For a
    seminar with three groups, this set will contain three letters.)

Am I trying to do the impossible?

Thanks for any help,
Dick Binder   (The Stainless Steel Rat)

uucp:    { decvax, allegra, ucbvax... }!decwrl!asd.dec.com!binder
ARPA:    [e-mail]
11-Aug-86 11:28:26-MDT,837;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 11 Aug 86 11:28:18-MDT
Received: from xerox.arpa by AMSAA.ARPA id a021179; 11 Aug 86 12:43 EDT
Received: from Riesling.ms by ArpaGateway.ms ; 11 AUG 86 09:43:28 PDT
Sender: [e-mail]
Date: 11 Aug 86 09:42:11 PDT (Monday)
Subject: Re: Bondwell CP/M computers
From: [e-mail]
To: [e-mail]
cc: [e-mail], [e-mail]
In-Reply-to: BW%HARVARDA.bitnet%WISCVM.WISC:EDU:Xerox's message of
 9-August-86 (Saturday) 2:56:37 PDT
Message-ID: <860811-094328-1469@Xerox>

As I understand it, the Bondwell CP/M computers are able to
read/write/run Kaypro and Osborne compatible disks. There may be other
formats compatible.

Larry
11-Aug-86 11:56:30-MDT,1140;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 11 Aug 86 11:56:20-MDT
Received: from 192.5.14.155 by AMSAA.ARPA id a021848; 11 Aug 86 13:01 EDT
Received: by tp5; Mon, 11 Aug 86 09:40:58 pdt
Message-Id: <8608111640.AA14765@tp5>
To: Keith Petersen <[e-mail]>
Cc: [e-mail], [e-mail], [e-mail],
    [e-mail]
Subject: Re: Telenet PC Pursuit will not upload certain files
In-Reply-To: Your message of Sat, 9 Aug 1986  21:58 MDT.
         <[e-mail]>
From: "A. Ross Johnson" <[e-mail]>
Date: 11 Aug 86 09:40:53 PDT (Mon)
Sender: [e-mail]


Is there really no way to disable the escape sequence with Telenet?
Foreign data networks (about which I know more) all provide for this, with
standard international paramater no. 1 for PAD (packet assembler and
disassembler) protocols, according to a CCITT standard.  When paramater
no. 1 is set to 0, you cannot escape to net command level in that session
and so can upload binary files.

Ross Johnson
11-Aug-86 14:49:38-MDT,4173;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 11 Aug 86 14:49:12-MDT
Received: from csnet-relay.arpa by AMSAA.ARPA id a028439; 11 Aug 86 15:41 EDT
Received: from gmr.com by csnet-relay.csnet id aa28878; 11 Aug 86 15:23 EDT
Date:     Sat, 9 Aug 86 15:08 EST
From:     RLH <[e-mail]>
To:       [e-mail]
Subject:  posting software to the net

I would like to encourage some kind of posting of software in addition
to the archives at SIMTEL20. As one the the low-class non-DDN people, I
feel the frustration that has been expressed by others when I see glowing
descriptions of some new public-domain software that sounds useful only
to find out that the only way to get it is thru FTP on ARPANET. Ther are
some excellent nearby RCP/M bulletin board systems that I use, but not all
the stuff I want shows up there.

WE do have to be careful about this, however. From my perspective, the
phone charges are insignificant, but other restrictions would prohibit
indiscriminant whole-sale mailing of software. I do have mass storage
limitations that could easily be exceded if tons of software poured in
while I was away on vacation. Since our local CSNET software is the
store-and-forward variety, it would interprete disk quota problems as
an incomplete delivery and re-try every hour, generating MANY error
messages to the system administrator along the way. You can imagine
that this might cause unfriendly feelings. Other people do have
problems with the telephone charges, and would not want to get large
volumes of unwanted software.

AT the same time, I am greatly in favor of distributing source code.
I have no sympathy for the argument that says "please send executables
only since I have only a BASIC interpreter." I have a least one compiler
for all the major languages (C, PASCAL, FORTRAN, BASIC) as well as
several assemblers and interpreters. Of course my BDS-C compiler is
would force me to modify code intended for MIX-C or C-80 or XYZ-C
compilers, but that's the way it goes. AT least I have a chance to
do so. If I get executable or object code, there is no reasonable
way for me to modify it for the particulars of my machine. Besides,
I like to look at the source code to get ideas and learn new techniques.
I believe that most CP/M enthusiasts (as opposed to users) would agree.

My idea of the optimum situation would be one in which announcements
of new software would be distributed thru INFO-CPM and have the source
code accessable somewhere via a mail request. The when I see something
interesting, I could send off a mail message asking to have the source
code mailed to me. I don't think it is reasonable to expect the originator
of the software to do this. Often it is quite dificult to figure out
mail return addresses that come from some other net, even given the
mail header info and what the person thinks is his return address. I know
that I would be less than excited about mailing out hundreds of messages
to unknown people if I had to spend a number of minutes deciphering
addresses and dealing with an uncooperative mail system. The ideal system
would be to have an mail server installed in a central site that
would accept requests for source code and automatically send the request
source via return mail. I think that the major impediment is getting
software to implement such a server - or does this kind of thing already
exist somewhere?

Second best would be having a seperate mailing list (maybe info-cpm-sources)
send out to a subset of the INFO-CPM mail list. Individuals would have to
request to be on the source mailing list. We would get some software
that we weren't interested in, but people who don't want it at all would
not be bothered by it.

I guess all this verbage boils down to:

        1) distribute source code, not object code

        2) have a seperate, parallel mail list for the sources

        3) myabe try to develope an automatic server

thanks for listening to (reading) me.


Bob Haar        ( [e-mail] )
G.M. Research Labs

11-Aug-86 20:47:53-MDT,607;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 11 Aug 86 20:47:46-MDT
Received: from lll-mfe.arpa by AMSAA.ARPA id a002236; 11 Aug 86 22:11 EDT
Date: Mon, 11 Aug 86 06:50 PDT
From: [e-mail]
Subject: DTC-510A
To: [e-mail]


To Mark at cent.mbeck%oz.ai.mit.edu and others of interest:
I found the DTC-510 to be a terrible controller. It is slooooooow. It would
not interface well with the BB-II that I had although I did get it working
for a while.  I eventually returned it and got a XEBEC.  One person's
comments...
--Neil
12-Aug-86 01:07:06-MDT,3932;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 12 Aug 86 01:06:48-MDT
Received: from simtel20.arpa by AMSAA.ARPA id a003518; 12 Aug 86 2:25 EDT
Date: Tue, 12 Aug 1986  00:25 MDT
Message-ID: <[e-mail]>
Sender: [e-mail]
From: Keith Petersen <[e-mail]>
To:   "A. Ross Johnson" <[e-mail]>
Cc:   [e-mail], [e-mail]
Subject: Telenet PC Pursuit file upload problem solved

A fix for the PC Pursuit XMODEM file upload problem has been found.

--cut here--PCP-FIX.MSG--cut here--
TO:       All PC Pursuit Users

SUBJECT:  PC Pursuit file upload problem solved!

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

My previous warning message (PCP-WARN.MSG) reported the inability
of GTE Telenet's PC Pursuit service to upload certain files using
Christensen ("XMODEM") protocol.  In particular, files containing
the three-byte ASCII sequence <CR, '@', CR> (binary <0DH, 40H,
0DH>) cannot normally be uploaded, since this sequence (and any
variation with high bits set in any of the three bytes) causes an
escape to Telenet command level.

In response to my initial inquiry about this problem, Telenet
customer service and engineering representatives informed me that
no solution was likely.  I am now pleased to report that this
information was incorrect!  It is possible to upload files
containing the three-byte Telenet escape sequence by following
the procedure described below.

After connecting to the remote modem (C DIALxxx/xx command),
escape to Telenet command level by typing (cr) @ (cr).  Then
issue the following two commands at the Telenet @ prompts (where
(cr) indicates RETURN or ENTER as appropriate to your keyboard):

        @SET? 1:0 (cr)
        PAR1:0

        @CONT (cr)

The SET? (Set Parameter) command disables subsequent recognition
of the normal Telenet escape sequence.  (The PAR1:0 message is a
response from Telenet.)  The CONT (Continue) command then returns
control to the remote modem.  Note that the above commands may be
entered at any time after connecting to the remote dialing area
via the Telenet C (Connect) command (i.e., before or after
issuing a Hayes modem ATDT dialing command to connect to a remote
system).  However, these commands should be used with caution...
Once they have been entered, there is no way to escape back to
Telenet command level in order to issue a D (Disconnect) command!
I.e., connection to another dialing area can only be made by
hanging up (dropping carrier) and then re-dialing into your local
Telenet access node.

My thanks to Telenet Director of Marketing, Kevin Abt (the
"Father of PC Pursuit") for researching this problem and
providing the above information.  Kevin also reports that GTE is
actively responding to the enormous popularity of PC Pursuit by
expanding capacity and enhancing the system.  They have just
completed a several-week effort to increase the number of
outgoing modems in each of the 14 metropolitan areas currently
served by PC Pursuit.  (I have personally noticed a marked
improvement in the time required to obtain network connections.)
They are now in the process of testing 2400 bps service and new
modems which provide enhanced call progress reporting, for
deployment in all PC Pursuit cities.  They are also soliciting
requests for additional cities for future service.  To keep
abreast of the latest developments and/or to provide feedback to
Kevin, call the NET-EXCHANGE, a FIDO BBS in the Washington, DC
(DIAL202) area at (703)-689-3561.


                                Bob Freed
                                Newton Centre, MA
                                August 11, 1986

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
12-Aug-86 06:21:17-MDT,1723;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 12 Aug 86 06:21:07-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a006645; 12 Aug 86 7:42 EDT
Received: from USENET by SMOKE.BRL.ARPA id a004241; 12 Aug 86 7:33 EDT
From: [e-mail]
Newsgroups: net.micro.cpm
Subject: Another exotic WordStar query
Message-ID: <[e-mail]>
Date: 11 Aug 86 12:48:57 GMT
Sender: [e-mail]
To:       [e-mail]

I'm trying to use MailMerge to assemble letters containing multiple lines of
information extracted from multiple data files, without success.

I have two data files, one containing a list of people who are to be included
in a seminar, and the other containing a list of the people who will moderate
the seminar (actually three or four different seminar groupings, all to run
concurrently).  I need to generate two sets of letters:

1.  Extract a data record from list 1 to be the addressing information, and a
    data record from list 2 to tell the addressee when and where the seminar
    is to be, and by whom it will be moderated.  (For a seminar with three
    groups, this set will contain between 15 and 18 letters.)

2.  Extract a data record from list 2 to be the addressing information, and
    six selected records from list 1, to tell the addressed moderator the
    names, etc., of the people who will be in his or her group.  (For a
    seminar with three groups, this set will contain three letters.)

Am I trying to do the impossible?

Thanks for any help,
Dick Binder   (The Stainless Steel Rat)

uucp:    { decvax, allegra, ucbvax... }!decwrl!asd.dec.com!binder
ARPA:    [e-mail]
12-Aug-86 06:23:03-MDT,1378;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 12 Aug 86 06:22:53-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a006674; 12 Aug 86 7:43 EDT
Received: from USENET by SMOKE.BRL.ARPA id a004310; 12 Aug 86 7:35 EDT
From: Fred Bowen <[e-mail]>
Newsgroups: net.micro.cpm
Subject: Re: RAM expansion modules for C128
Message-ID: <[e-mail]>
Date: 11 Aug 86 18:57:51 GMT
To:       [e-mail]

> Can anyone tell me from where can I obtain the circuit diagram for the 128k
> or 512k versions of the RAM expansion modules for the Commodore 128.

As far as I know, Commodore is has no plans to publish the diagrams.  The RAM
expansion modules consist simply of either 64K x1 or 256K x1 DRAMs and the
8726 (custom) controller.  The controller itself eliminates the need for TTL
address and data buffering.  The controller also provides DRAM refresh.
The C128 (or C64) processor accesses the expansion RAM via instructions to the
controller, which then reads/writes/swaps memory via DMA.  The controller
drives the bus only during phase 2 of the standard 1MHz system clock.
--
Fred Bowen            uucp:    {ihnp4|seismo|caip}!cbmvax!fred
                arpa:    cbmvax![e-mail]
                tele:    215 431-9100

Commodore Electronics, Ltd.,  1200 Wilson Drive,  West Chester,  PA,  19380
12-Aug-86 07:11:23-MDT,1802;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 12 Aug 86 07:11:16-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id aa06674; 12 Aug 86 7:43 EDT
Received: from USENET by SMOKE.BRL.ARPA id a004344; 12 Aug 86 7:36 EDT
From: Marc Lewert <[e-mail]>
Newsgroups: net.micro.cpm
Subject: Bondwell CP/M 3.0
Message-ID: <[e-mail]>
Date: 11 Aug 86 17:10:33 GMT
Keywords: Bondwell CPM CP/M 2.2 3.0
To:       [e-mail]

[sacrafice for the line-eater]

It has been my *very* limited experience with a Bondwell 14 running
CP/M 3.0 that I have had no trouble running CP/M 2.2 programs.  The
14 is supposed to be Kaypro II compatable, and we have had no trouble
running the programs (few they may be) that we bought for it.  This
includes Turbo Pascal, and a couple of communications progams (neither
of which meet our needs).

We have had problems with CP/M 2.2 systems reading our CP/M 3.0 disks.
What we have had to do in those cases is find a mutual read/write format
and have the other machine format a disk to use. We now keep a few disks
around that are in a different format to be used for tansfers.

I am interested in any info about the compatability of CP/M 3.0 and 2.2
programs.  Thanks in advance.
    marc
--
=========================================================================
Marc Lewert                           UUCP: ...hplabs!pyramid!triada!marc
Triad Systems Corp.
PO Box 61779                          MA Bell: [phone]
Sunnyvale, Ca. 94088-1779

Disclaimer:  All views are my own and do not reflect those of my
             employer, friends, or family unless otherwise noted.
=========================================================================

12-Aug-86 07:20:38-MDT,1194;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 12 Aug 86 07:20:31-MDT
Received: from xerox.arpa by AMSAA.ARPA id a007577; 12 Aug 86 8:07 EDT
Received: from Riesling.ms by ArpaGateway.ms ; 12 AUG 86 05:08:23 PDT
Sender: [e-mail]
Date: 12 Aug 86 05:05:54 PDT (Tuesday)
Subject: Re: Another exotic WordStar query
From: [e-mail]
To: [e-mail]
cc: [e-mail]
In-Reply-to: binder%asd.DEC%dec:ARPA:Xerox's message of 11-August-86
 (Monday) 9:31:03 EDT
Reply-to: [e-mail]
Message-ID: <860812-050823-2364@Xerox>

You NEED to buy L. David Stone's book called (something like) "Things
MicroPro Never Told You About WordStar, MailMerge & StarIndex".  The
book is loaded with fairly well documented features that MicroPro
doesn't cover in the manual and with lots of great "tricks" on how to
get your hardware to do (WordStar) things you might otherwise never
dream up yourself.  It sells for between $15 and $20; I don't remember
the exact price; and has a black cover with the title in white and green
printed diagonally across it.

Good Luck
12-Aug-86 20:05:23-MDT,1215;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 12 Aug 86 20:05:16-MDT
Received: from simtel20.arpa by AMSAA.ARPA id a028685; 12 Aug 86 21:30 EDT
Date: Tue 12 Aug 86 19:31:33-MDT
From: "Frank J. Wancho" <[e-mail]>
Subject: Mail access to the SIMTEL20 archives
To: [e-mail]
Message-ID: <[e-mail]>

It now appears that the "best" solution to the problem of
non-Internet access to the files in the SIMTEL20 archives
is to develop a program that will take specifically formatted
mail requests for files, ARC and uuencode the file, and send
the result back to the requestor if the file is under a certain
ceiling.  The alternate suggestion of a "net.sources.cpm" could
still be independently persued, but only one address per site.

The pieces of the mail server technique are falling together.
I currently have a TOPS-20 version of ARC about 95% complete.
A TOPS-20 version of uuencode will be revisited shortly.  The
server to envelope these pieces appears to be "easy" (famous
last words).  Let me see what can be done, and I'll report
back to you all when I come up for air...

--Frank
-------
13-Aug-86 04:43:23-MDT,1906;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 13 Aug 86 04:43:15-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a001905; 13 Aug 86 6:07 EDT
Received: from USENET by SMOKE.BRL.ARPA id a005798; 13 Aug 86 5:51 EDT
From: Bob Amen <[e-mail]>
Newsgroups: net.micro.cpm
Subject: Re: Posting software directly to info-cpm or net.micro.cpm:
Message-ID: <[e-mail]>
Date: 12 Aug 86 12:35:46 GMT
To:       [e-mail]


[munch]

    As a Usenet site with no connections to the ARPA net I have
been drooling over some of the teasers we've gotten in the form of
SIMTEL20 lists.  I requested info from the net regarding existence
of a CP/M BBS in the Maryland area and got no responses.  So I vote
for posting to the net.  However...as a site that pays our own phone
bills from contracts and grants I would like to see it be a moderated
group (say mod.source.cpm) with some reasonable form of archiving.
That might prevent the usual 'I didn't get whizbang...could someone
repost it?'  Perhaps a list of what's available could be kept and
mail to the list maintainer would bounce the list back.  Then
requests for something archived could be mailed to the moderator.
I bet if we thought about it for a bit we could come up with a decent
method of automatically mailing out the requested software.

    So there's my two cents worth.  Not having connections
to the other nets I can't respond to the other concerns that were
raised.  My only concern is that we not raise the ire of the net
any more than it already is due to increased volume (see what's
been happening in net.adm etc).

    I'm glad to see that CP/M lives!


    Bob Amen

UUCP:  seismo!umcp-cs!aplcen!quequeg!amen

USPS:    Chesapeake Bay Institute
    4800 Atwell Rd
    Shady Side, MD 20764-0037

Voice:    [phone]
    [phone] (Balt.)
13-Aug-86 09:08:50-MDT,1371;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 13 Aug 86 09:08:39-MDT
Received: from wiscvm.arpa by AMSAA.ARPA id a009601; 13 Aug 86 10:07 EDT
Received: from (MEK)UMASS.BITNET by WISCVM.ARPA on 08/13/86 at 09:07:02
  CDT
Message-ID:  <860813100023.000003EB.AFNB.MA@UMass>
Date:     Wed, 13 Aug 86  10:00:23 EDT
From:  [e-mail]
Subject:  MAIL ACCESS TO SIMTEL20 ARCHIVES
To:  [e-mail]

(PLEASE EXCUSE THE ALL-CAPS)

I THINK THAT THE IDEA OF A SERVER GETTING MAIL COMMANDS
AND SENDING FILES IS AN *EXCELLENT* IDEA.  HOWEVER, SINCE
NOT ALL NETWORK USERS ARE USING TOPS-20, I THINK THAT FILES
SHOULD BE ABLE TO BE SENT IN OTHER FORMATS, SUCH AS .hex
FILES. FOR EXAMPLE, THERE COULD BE COMMANDS LIKE:


HEX NULU151.COM       -WOULD SEND NULU151.COM IN HEX FORMAT, TO
                       BE LOAD'ED OR HEXCOM'D.

UUE NULU151.COM       -WOULD SEND NULU151.COM IN A UUENCODED
                       FORMAT.

THERE COULD ALSO BE A DIR COMMAND, WHICH, BY ITSELF, WOULD
SEND A LIST OF THE FILE AREAS AVAILABLE, AND WITH A PARAMETER
OF A FILE AREA WOULD SEND A LIST OF THE FILES IN THAT AREA.
I THINK THAT THIS WOULD BE AN EXCELLENT SOLUTION TO THE PROBLEM
OF ACCCESS TO THE SIMTEL20 ARCHIVES BY BITNET, JANET, CSNET,
ETC.

MATT KIMMEL,
[e-mail]
14-Aug-86 05:43:49-MDT,776;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 14 Aug 86 05:43:38-MDT
Received: from wiscvm.arpa by AMSAA.ARPA id a000290; 14 Aug 86 7:11 EDT
Received: from (CSNET)UKANVAX.BITNET by WISCVM.ARPA on 08/13/86 at
  18:05:08 CDT
Date:     Wed, 13 Aug 86 15:57 CDT
From:        [e-mail]
MMDF-Warning:  Parse error in preceding line at AMSAA.ARPA
Subject:  addition for subscription list.
To:  [e-mail]
X-Original-To:  [e-mail], CSNET


Could you please add me to your subscription list for info-cpm.

                                        Thank You,

                                        David Long

                                        [e-mail]

14-Aug-86 08:09:02-MDT,998;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 14 Aug 86 08:08:53-MDT
Received: from ll.arpa by AMSAA.ARPA id a004411; 14 Aug 86 9:23 EDT
Date: Thu 14 Aug 1986 09:21:08 EDT
From: [e-mail]
MMDF-Warning:  Parse error in preceding line at AMSAA.ARPA
Subject: PMATE Text Editor Information
To: [e-mail]
Cc: [e-mail]
Message-ID: <[e-mail]>

   Peter Kendell addressed a message to me over info-cpm because he could
not get mail to me directly.  Well, I cannot get mail to him either (I have
tried using numerous variations on the return address indicated in his
message).  So my apologies to everyone else on the list.

   Peter, please leave a message for me with your postal address, and I
will send you the information you requested about the PMATE text editor.

           Jay Sage
           MIT Lincoln Lab
           Room C-128
           PO Box 73
           Lexington, MA 02173-0073


14-Aug-86 15:41:25-MDT,620;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 14 Aug 86 15:41:17-MDT
Received: from simtel20.arpa by AMSAA.ARPA id a019563; 14 Aug 86 17:05 EDT
Date: Wed 13 Aug 86 23:40:32-MDT
From: Rick Conn <[e-mail]>
Subject: New Z System News
To: [e-mail]
Message-ID: <[e-mail]>

    Thanks to Keith Petersen for the upload:

   PD:<ZSYS.NEW>
          Bytes(SZ)

 Z-NEWS.507.1     21625(7)
   .5Q7.1         13824(8)

 Total of 16 pages in 2 files

    The squeezed file is also in PD:<ZSYS.Z-NEWS>.

        Rick
-------
14-Aug-86 15:58:11-MDT,1463;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 14 Aug 86 15:58:04-MDT
Received: from simtel20.arpa by AMSAA.ARPA id a019584; 14 Aug 86 17:06 EDT
Date: Thu, 14 Aug 1986  01:46 MDT
Message-ID: <[e-mail]>
From: [e-mail]
To:   [e-mail]
Cc:   [e-mail], [e-mail]
Subject: MAIL ACCESS TO SIMTEL20 ARCHIVES
In-reply-to: Msg of 13 Aug 1986  08:00-MDT from mek%UMass.BITNET at WISCVM.ARPA

Matt,

It's not that anybody is running under TOPS-20.  It's just that
TOPS-20 is the operating system used by SIMTEL20.  I feel that the
basic requirement to have ARC and uudecode available on the target
operating system is not too much to ask.  ARC is already native to
MSDOS users, and I believe there is a version of uudecode also
available.  On the CP/M side, there are several variants of at least
the extract portion of ARC available, and I believe uudecode is
available as well.

The reason for choosing these two in combination is that the resulting
message is pretty well guaranteed to be both shorter than the original
and transmittable as an ordinary text mail file.  It's not a parsing
problem; it's simply an arbitrary policy decision, for now, at least.
Let me see how things go and maybe there might be an option made
available to allow retrieval of certain key bootstrap files only in
HEX form.
--Frank
15-Aug-86 00:52:25-MDT,1489;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 15 Aug 86 00:52:18-MDT
Received: from wiscvm.arpa by AMSAA.ARPA id a000825; 15 Aug 86 2:19 EDT
Received: from (IFF095)DJUKFA11.BITNET by WISCVM.ARPA on 08/14/86 at
  10:50:26 CDT
Date: Thu, 14 Aug 86 17:48:13 MEZ
To:  [e-mail]
From:  [e-mail]
Subject: NOTE from IFF095

Date: 14 August 1986, 17:10:34 MEZ
From: Joachim K. Anlauf         [phone]       IFF095   at DJUKFA11
To:   INFO-CPM at AMSAA
Subject: Mail access to the SIMTEL20 archives

I am a Europian BITNET-user and I am in deed a little bit frustrated when
I hear of all the software on SIMTEL20. I only want to make one (new?) point.
If sources are distributed with a new mailing list it is still impossible
to get old, but certainly good, software from SIMTEL20. The solution with
an automatic fileserver sounds much more attractive to my ears.

Now the question arises: do we really have to develop our own software?
There are some other fileservers on the ARPA-net that also work together
with BITNET. For example:

    [e-mail]
You can get more informations with:
    Request:Info
    Topic: Help

and:
     [e-mail]
To receive information mail the following command to NETLIB:

Send index

These are automatic fileservers, as far as I know. Does anyone know,
whether it is possible to use their software?

Joachim
-------
15-Aug-86 04:11:14-MDT,1130;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 15 Aug 86 04:11:08-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a001164; 15 Aug 86 5:48 EDT
Received: from USENET by SMOKE.BRL.ARPA id a011659; 15 Aug 86 5:41 EDT
From: Aaron Temin <[e-mail]>
Newsgroups: net.micro.cpm
Subject: 5 1/4" floppy drives - question
Message-ID: <[e-mail]>
Date: 14 Aug 86 15:23:55 GMT
Keywords: TEK drives, Actrix
To:       [e-mail]

I've got an Actrix running CP/M with sssd TEK FB-501
5 1/4" drives.  I'd like to find dsdd drives to plug in.
I know that TEK FB-503 drives are ok, but can't find
any listed for sale in a recent Byte.  Can anyone out there
tell me where I might buy them, or what other drives might
be compatible?

More generally, what is the difference between various
5 1/4" floppy drives (some are advertised for IBM's, some
for Apple's, etc)?

Many thanks in advance,
Aaron
--
Aaron Temin, CS Dept., University of Texas, Austin, Texas
{gatech,harvard,ihnp4,pyramid,seismo}!ut-sally!temin
[e-mail]
15-Aug-86 05:48:27-MDT,2256;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 15 Aug 86 05:48:14-MDT
Received: from simtel20.arpa by AMSAA.ARPA id a001831; 15 Aug 86 7:06 EDT
Date: Sunday, 10 August 1986  20:58-MDT
Message-ID: <[e-mail]>
Sender: Frank Prindle <[e-mail]>
From: Frank Prindle <[e-mail]>
To: [e-mail]
Subject:   New Commodore C128 CP/M files uploaded to Simtel20
ReSent-From: [e-mail]
ReSent-To: [e-mail]
ReSent-Date: Wed 13 Aug 1986 22:39-MDT

Now available from SIMTEL20:

Filename            Type     Bytes     CRC

Directory PD:<CPM.C128>
C128TVX2.LBR.2            BINARY    200320  12F7H
C8FILCPY.LBR.2            BINARY     11392  2BE8H
C1571-2.COM.1            BINARY      1024  DBA9H

Descriptions:

C128TVX2.LBR -

This is a version of the TVX video-oriented editor configured for the
Commodore 128 running CP/M 3.0.  Executable .COM file, source code and
manual are included.  The program would be usable as-is on other CP/M
systems which support ADM-31 terminal control sequences, but would
have to be recompiled to support other terminals.  In this version,
text buffer sizing is automatic as a function of available TPA, so it
will work with RSXs active (unlike a previous version, TVX-C128).  The
name of the LBR has been changed to allow a version number to be included
to avoid confusion with the older version.

C8FILCPY.LBR -

This is specifically designed for allowing a Commodore 128 user
with a single drive (yes, they do exist) to copy CP/M files without
unnecessary disk swapping.  This program, unlike PIP or SWEEP, buffers
several files between disk swaps, in an effort to mimimize disk swaps.
It uses virtual drive E:.  Source and .COM file included.

C1571-2.COM -

This version, dated 24-Feb-86, is a replacement for C1571.COM.  It
is a disk write speedup utility for the Commodore 1571 disk drive
running with CP/M 3.0 on a C128.  The original one uploaded is an
early Commodore release which has two bugs: MFM operation of the
drive is damaged, and the drive motor refuses to shut off after a
write.  This version fixes those bugs.  Commodore says it's ok to
distribute this, and seeks wide availability.
15-Aug-86 07:50:58-MDT,733;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 15 Aug 86 07:50:51-MDT
Received: from nadc.arpa by AMSAA.ARPA id a006051; 15 Aug 86 9:19 EDT
Date: 15 Aug 1986 09:14:24-EDT
From: [e-mail]
To: [e-mail]
Subject: C128 software info

Additional info on PD:<CPM.C128> files C128TVX2.LBR and C8FILCPY.LBR:

The .COM files were compiled with Z-80 op-codes and may not work without
recompilation on 8080 based systems (are there really such things still
existing?).  This does not affect C128 owners, as this is a Z80 machine.

The FILECOPY program does not support "cross-user" copies (whereas PIP,
and perhaps SWEEP do).

Frank Prindle
[e-mail]
15-Aug-86 09:22:01-MDT,1099;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 15 Aug 86 09:21:34-MDT
Received: from crdec-vax3.arpa by AMSAA.ARPA id a008992; 15 Aug 86 10:54 EDT
Date:     Fri, 15 Aug 86 10:49:05 EDT
From:     "Jack H. Smith" <[e-mail]>
To:       [e-mail]
Subject:  bulk file transfers via xmodem


    Fellow netlanders:

        Being fully aware of the xmodem programs available from
    SIMTEL20, and using them to download software from our BSD4.2 vax
    to my micro....I was wondering if anyone knew of a version of
    xmodem that supports bulk transfers via wildcards and the like.

        I know that 'mget' in ftp allows bulk transfers from
    SIMTEL20 to my local vax system, and my version of MDM730 also
    supports bulk transfers....but the version of xmodem only
    supports single file transfers.

        If anyone out there knows of a version of xmodem that
    does support bulk transfers, I'd surely be interested in hearing
    from him/her. It sure would make life a little easier.


                    Long Live CP/M..

                    Jack Smith


15-Aug-86 11:22:20-MDT,1788;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 15 Aug 86 11:22:10-MDT
Received: from bbnccq.arpa by AMSAA.ARPA id a000189; 15 Aug 86 11:55 EDT
Date: Fri, 15 Aug 86 11:34:34 EDT
From: Bob Clements <[e-mail]>
Subject: Do 8080 systems still exist?
To: [e-mail], [e-mail]
Cc: [e-mail]

Re:  Do 8080 based systems really still exist?

>>   Date: 15 Aug 1986 09:14:24-EDT
>>   From: [e-mail]
>>   Subject: C128 software info
>>   ...
>>   The .COM files were compiled with Z-80 op-codes and may not work without
>>   recompilation on 8080 based systems (are there really such things still
>>   existing?).
>>   ...
>>   Frank Prindle
>>   [e-mail]

I realize that you weren't really trying to suggest that we ignore 8080-based
systems, Frank.

But I thought I would point out that there is actually a GROWING number
of non-Z80 CP/M systems around. Namely those that use the NEC V-20 chip
in an IBM-PC/clone environment.  The V-20 unfortunately doesn't do the
Z-80 opcodes, but it is a GREAT 8080.  I am currently doing all my 8080
and Z80 development work using the 8-bit M80/L80 from a retired CP/M
machine. The V-20 is much faster and it allows me to mix more modern
tools like MAKE and a better editor with the venerable assembler/linker
and some others that I retain from the Z-80 machine. Unfortunately, there
are a few such tools, to which I do not have the source, that won't run
because of the Z-80 opcodes in them.

/Rcc

[Everything above is the trademark of somebody.
My opinions are copyrighted by me.
If you share them, you are violating your license agreement.]

[e-mail]
{ihnp4, decvax, linus}!bbnccv!clements

15-Aug-86 13:53:11-MDT,3723;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 15 Aug 86 13:52:53-MDT
Received: from apg-1.arpa by AMSAA.ARPA id a002047; 15 Aug 86 15:13 EDT
Date: Fri, 15 Aug 86 15:11:46 EDT
From: Robert Bloom AMSTE-TEI 3775 <[e-mail]>
Subject: Any TurboDOS Users out there?
To: [e-mail], [e-mail]
Cc: [e-mail], [e-mail]

I am a new user of TurboDOS, the multi-processor and multi-user
operating system.  I am not yet on the plateau of my learning
curve from the supplied documentation, but am rapidly approaching
it.  The machine in question is a NorthStar Horizon running 8
TurboSlaves, 2 HD18's, 2 printers and some commo ports.  It's
currently running TurboDOS version 1.3 (N* v1.1.1).  (NorthStar
never released a 1.4 version.)

Is there any TurboDOS users out there that can aid me in some
slightly past initial type questions?  (in order of priority:)

     . WordStar does not properly close files when they're saved,
they're truly closed only when WS is exited.  A second person in
a file previously opened but not properly closed is not allowed
to make changes and save them.  (And how I have the COMPAT flag
set, you don't even get an error!)  So, is there a patch so WS
*will* correctly close a file that is saved with the common ^K^D?

     . MXO-TD30 is the MEX overlay for TurboDOS using the printer
port on the user processor.  It works fine for my dial-up Modem.
However, it can't send a <break> on my Earth TurboSlave card.  Of
course, that what I need to do.  Before I try to tackle the
hardware specifics in the overlay, has anyone already solved it?

     . MEX-TDOS is the mex overlay for TurboDOS to use a port off
of the master processor and involves defining a new user (t-41)
call for better response.  Also of course, it's very hardware
specific (written for a JCS s-100 computer.)  Likewise, before I
tackle this one, has anyone done an overlay for the NorthStar
Horizon HSIO/4?

     . d/Multi is a dBase II enhancement that turns it into a
true multi-user DBMS with the record and files locks of TurboDOS.
Anybody use it?  It is any good?  Is there something better?

     . With the potentially huge (well, relivitively huge) 'BIOS'
memory space availability with banked slaves, has any one written
QuickKey or similar function key enhancements?  After 5 years
with a TeleVideo terminal, I *still* haven't found any use for
the unredefinable 'function' keys!  The enhancements I have found
and are working on are fanled and timecl.

     . So far I know of only one book about/for TurboDOS
("TurboDOS made easy," by Steven Marks) other than the two
binders that came with my NorthStar version 1.3.  (The upgrade to
Version 1.4 is on order.)  Are there any other books on the
subject?  (An example: the use of the AUTOLOAD command to create
command line synonyms [or ZCPR3 aliases] is not mentioned at all
and is probably more usefull have the functions that are listed!)
Sure it's fun to figure these things out yourself, but I wonder
what I'm missing.  (mini-review: The Marks book is not bad, adds
sections on why one would want to do things to the information
that already is in the user's guide, written in a plain language.
Unfortunated marred by some bad typos, some which are opposite of
what was wanted.  An example: 'set filename.ext ;-r' sets the r/o
flag *ON*.)


Any of the above need not be public domain and/or 'free', though
it sure does make procurement easier!  As the system in question
belongs to Uncle Sam, some funds should be available somewhere :-)

Bob Bloom

15-Aug-86 20:04:53-MDT,2187;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 15 Aug 86 20:04:43-MDT
Received: from simtel20.arpa by AMSAA.ARPA id a003037; 15 Aug 86 21:30 EDT
Date: Fri, 15 Aug 1986  19:29 MDT
Message-ID: <[e-mail]>
Sender: [e-mail]
From: Keith Petersen <[e-mail]>
To:   [e-mail]
Subject: Quick reference list to SIMTEL20 CP/M directories

Quick reference list to SIMTEL20's PD:<CPM.x> directories
as of August 15, 1986 (where 'x' is one of the names below):

22RSX         CCP           FILUTL        MISC          SQU-PORT
6502          COBOL         FINANCE       MODEM         SQUSQ
AMETHYST      COMND         FORTH-83      MODEM2        STARTER-KIT
APPLE         CPM3          FORTRAN       MODEM7        SUBMIT
ASMUTL        CPM68K        GENASM        MSOFT         SYSUTL
ATARI         CPM86         GENCOM        NEWS          T20-SQUSQ
AZTEC-C       CPMLIB        GENDOC        NSTAR         TERM
BASIC         CPR86         GENIE         NUBYE         TOPS-20
BBSLISTS      CUG           GRAPHICS      OSBORN        TRS-80
BDOS          DATABASE      HAMMING       PACKET        TURBODOS
BDSC-1        DBASEII       HAMRADIO      PASCAL        TURBODOS-SIGI
BDSC-2        DEBUG         HDUTL         PBBS          TURBOPAS
BDSC-3        DIRUTL        HEATH         PILOT80       TXTUTL
BDSC-4        DISASM        HELP          PLOT33        VAXVMS
BSTAM         DISKPLOT      HEX           PPSPEL        VDOEDIT
BYE3          DSKBUF        IMP           PUBKEY        VOICE
BYE5          DSKUTL        INSIDCPM      PUBPATCH      WSTAR
BYT85FEB      EDITC80       KAYPRO        RBBS          XCCP
BYT85JAN      EDITOR        LIST          RBBS4         XLISP
C128          EDUCATION     MACLIB        RCPM          YAM
C64           EMX           MATH          ROS           Z8EDEBUG
C80           EPSON         MBBS          SCREENGEN     ZCPR
CATLOG        FAST2         MEMTEST       SMALLC21      ZCPR2
CB80          FILCPY        MEX           SORT          ZCPR3
CBIOS         FILE-DOCS     MICNET        SPELL         ZMODEM
15-Aug-86 20:10:20-MDT,745;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 15 Aug 86 20:10:14-MDT
Received: from wiscvm.arpa by AMSAA.ARPA id a003051; 15 Aug 86 21:35 EDT
Received: from (MEK)UMASS.BITNET by WISCVM.WISC.EDU on 08/15/86 at
  20:35:00 CDT
Message-ID:  <860815213242.0000028B.ASHC.MA@UMass>
Date:     Fri, 15 Aug 86  21:32:42 EDT
From:  [e-mail]
Subject:  UUENCODE/DECODE for CP/M?
To:  [e-mail]

Hi!

Does anyone out there know of a version of UUENCODE/DECODE for CP/M??
I've been looking all over for it, but haven't been able to find a
version anywhere.  *PLEASE* let me know if you know of such a thing.
Thanks!!!

Matt Kimmel,
[e-mail]
16-Aug-86 08:43:12-MDT,4922;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sat 16 Aug 86 08:42:57-MDT
Received: from simtel20.arpa by AMSAA.ARPA id a004459; 16 Aug 86 10:16 EDT
Date: Thursday, 14 August 1986  11:20-MDT
Message-ID: <[e-mail]>
Sender: Bob Clements <[e-mail]>
From: Bob Clements <[e-mail]>
To: [e-mail]
Subject:   Version 11.7 of W0RLI Packet Radio Mailbox/Gateway
ReSent-From: [e-mail]
ReSent-To: [e-mail]
ReSent-Date: Sat 16 Aug 1986 08:02-MDT

Version 11.7 of the W0RLI MailBox/Gateway has been released and is now
available from SIMTEL20 as:

Filename            Type     Bytes     CRC

Directory PD:<CPM.PACKET>
PACKT117.ARC.1            BINARY    212704  0B69H

This release is being distributed in ARC format because of the more
efficient packing methods available.  You can extract the files on
your CP/M system using one of the following:

Directory PD:<CPM.STARTER-KIT>
UNARC.COM-Z80.1            BINARY      4096  C209H <--Z80 version
UNARCA.COM-8080.1        BINARY      4736  DF9BH <--8080 version

The changes since the last such posting, version 11.2, are summarized
below in an extract from the CHANGES.TNC file.

For those who have not seen this system before, a brief description:

The W0RLI MailBox and GateWay is a system which runs on a Xerox 820
computer and which operates on Amateur Packet Radio via one or two
TAPR TNCs (or clones). It also runs with TNC-2s.

The W0RLI system is running at over 75 sites in some number of
countries and makes up the majority of the packet mail forwarding
system. It is also used for gatewaying between local packet areas and
long haul links on HF, or to nearby nets on other VHF/UHF bands.
For a more complete description, see NOTES.TNC.

Hank is not on ARPANET or Usenet.  I will be glad to relay comments
and questions to him.  However, he is also in the process of moving
from W1-land to W6-land, so contact is not as solid as it has been.
Also, he won't be doing much coding on this system for a while,
for the same reason.

If you would prefer to get this distribution on ready-to-run
disks for your Xerox 820, send a self-addressed stamped 8" SSSD
disk (in re-usable mailer) to K7PYK at the address below. Two
disks if you want the sources as well.

I will do the same under the same conditions.  I am good in the
Callbook.

NOTE -  Hank is no longer doing distributions himself.  Wes, K7PYK,
has kindly volunteered to take over that job.  Please do NOT send
disks to Hank.

73,
Bob, K1BC

ARPANET: [e-mail]
Usenet:  {ihnp4, decvax, linus, ...}!bbnccv!clements
Packet:  K1BC @ K1BC  145.09 and 221.11, near Boston

[Extract of NOTES.TNC follows]

     W0RLI MailBox and GateWay   Version 11.7 - 6/22/86   Page  1

     Created for packet community by:

            Hank Oredson, W0RLI
            19 North Hill Road
            Westford, MA 01886

     Distributed by:

          Wes Morris, k7pyk
          7422 E. McKinley St.
          Scottsdale, AZ 85257

Many people contibuted to this project, in many ways.
In particular I would like to thank K1BC, KE1G, WB2MNF, W3IWI, WB7DCH
K3RLI, KE3Z, K7PYK for their help and encouragment.

These notes are rough, more release notes and tech notes than
anything else. A SYSOPS Manual (Very nice, 40+ pages) is also
available from Wes. It was written by Jon Pearce, WB2MNF.

[Extract of CHANGES.TNC follows]

     W0RLI MailBox and GateWay   Version 11.7

     Changes and additions since version 11.6 are:

Added 3 second delay between connect and sending "*** LINKED ..."

     Changes and additions since version 11.5 are:

Added FL (File Local users) and FB (File BBS).
Tag in config to enable/disable retention of "F" msgs on forward.
Cleaned up the handling of tnc state changes with MailBox state changes.

     Changes and additions since version 11.4 are:

Login procedure split from TNC.MAC into LOGIN.MAC
Logic changed to allow local users to connect if "only bbs" flag set.
If station connecting is a bbs: bypass # digi check, exclude checks.
New tag in config to exclude connects thru digi with illegal call.

Changes from k1bc (Thank you Bob ...) :
LM now lists messages TO and FROM user.

     Changes and additions since version 11.3 are:

Changes from k3rli (Thank you Ed ... ) :
Help and Info files may be $sys.
WN command for users.
Message type "F" is never killed after forward, only marked.
"Expert user" flag. No logoff message, short prompt.

     Changes and additions since version 11.2 are:

BIOS common code now in files BIOS????.INC
Attempt to upload existing file got error msg twice.
Added EU with no argument prompt through all users for delete.
Added K4NTA code to handle forwarding through a GATOR 2 PAD.
Made UA available to remote sysop.

[End of extracts]
16-Aug-86 09:29:03-MDT,1019;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sat 16 Aug 86 09:28:56-MDT
Received: from simtel20.arpa by AMSAA.ARPA id a004573; 16 Aug 86 11:00 EDT
Date: Sat, 16 Aug 1986  08:59 MDT
Message-ID: <[e-mail]>
Sender: [e-mail]
From: Keith Petersen <[e-mail]>
To:   [e-mail]
Subject: Posting software directly to info-cpm or net.micro.cpm:

If you are unable to access SIMTEL20 because of network restrictions
please remember that MOST of the new files announced to Info-Cpm are
also available on my RCP/M Royal Oak (MI) which may be accessed at
300 bps (Bell 103a), 1200 bps (Bell 212a), or 2400 bps (V.22 bis).
The telephone number is [phone].  They are also available from
the CP/M RoundTable on General Electric Information Services' GEnie.

--Keith Petersen
Arpa:   [e-mail]
GEnie Mail: W8SDZ
uucp:   {ihnp4,allegra,cmcl2,dual,decvax,mcnc,mcvax,vax135}!seismo!w8sdz
16-Aug-86 09:45:04-MDT,1057;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sat 16 Aug 86 09:44:58-MDT
Received: from simtel20.arpa by AMSAA.ARPA id a004635; 16 Aug 86 11:26 EDT
Date: Sat, 16 Aug 1986  09:26 MDT
Message-ID: <[e-mail]>
Sender: [e-mail]
From: Keith Petersen <[e-mail]>
To:   [e-mail]
Cc:   [e-mail]
Subject: UUENCODE/DECODE for CP/M?
In-reply-to: Msg of 15 Aug 1986  19:32-MDT from mek%UMass.BITNET at wiscvm.ARPA

A version of UUENCODE/UUDECODE for CP/M was recently posted to
Info-Cpm.  However, the UUENCODE program has a bug that adds one
additional record to the UUENCODEd file and when you UUDECODE it the
CRCs won't match.  I'm hoping the author will send me a fixed version
which I can then make available on SIMTEL20 and through other means.

--Keith Petersen
Arpa: [e-mail]
uucp: {ihnp4,allegra,cmcl2,dual,decvax,mcnc,mcvax,vax135}!seismo!w8sdz
GEnie Mail: W8SDZ
RCP/M Royal Oak: 313-759-6569
16-Aug-86 14:08:19-MDT,1048;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sat 16 Aug 86 14:08:12-MDT
Received: from lll-mfe.arpa by AMSAA.ARPA id a005528; 16 Aug 86 15:42 EDT
Date: Fri, 15 Aug 86 20:19 EST
From: [e-mail]
Subject: XLISP 1.2 < n
To: [e-mail]

From:    <[e-mail]>   (Richard C. Secrist)
Date:    Fri, 15-AUG-1986 20:21 EST
To:      [e-mail]
Message-ID: <[OAK.SAINET.MFENET].91BDD740.008F37E5.SECRIST>
Header-Disclaimer: I don't like my headers either.
Quote: "May your future be limited only by your dreams." -- Christa McAuliffe
Organization:  Science Applications Int'l. Corp., Oak Ridge, Tenn., USA
CompuServe-ID: [71636,52]
X-VMS-Mail-To: CPM

Has anyone built a version of David Betz' XLISP for CP/M-80 since v1.2 ?
If so, what compiler did you use (anybody tried Small-C ?), and/or where
did you download it from ?

Did the INFO-XLISP list ever get started ?

rcs
[e-mail]
16-Aug-86 15:24:59-MDT,492;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sat 16 Aug 86 15:24:53-MDT
Received: from simtel20.arpa by AMSAA.ARPA id a005874; 16 Aug 86 16:52 EDT
Date: Sat 16 Aug 86 14:51:50-MDT
From: Rick Conn <[e-mail]>
Subject: VMENU18 posted
To: [e-mail]
Message-ID: <[e-mail]>

    In PD:<ZSYS.NEW> and <ZSYS.ZCPR3> is VMENU18.LBR, a recent update
to VMENU.  Thanks to Keith for the upload.
-------
16-Aug-86 16:53:08-MDT,1157;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sat 16 Aug 86 16:53:02-MDT
Received: from office-1.arpa by AMSAA.ARPA id a006295; 16 Aug 86 18:24 EDT
Date: 16 Aug 86 15:23 PDT
From: Alan Bomberger <[e-mail]>
Subject: MIX Editor
To: [e-mail]
Message-ID: <COR-ACB-9R5EL@OFFICE-1>

I must lend my support to the view of Willie Smith, as I too deposited the MIX
editor into my lower left hand drawer.  My syste uses interrupts and the
crashes are not random.  I cannot even run the configuration program.  I did
disable interrupts with a special BIOS and configured MIX.  What I found was a
powerful but incredibly slow editor.  Every operation seemed to require an
overlay to be loaded from disk.  Furthermore only 8K bytes are available to
edit anything.  I use Magic Wand and have over 40K bytes resident with all
commands resident also.  I could not take the performance hit of using MIX in
spite of its features (assuming that I could get it to run with interrupts).  I
am interested in the Stack Fix.   Late in responding as I was in AUstralia for
a month.

16-Aug-86 17:43:44-MDT,794;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sat 16 Aug 86 17:43:37-MDT
Received: from office-1.arpa by AMSAA.ARPA id a006682; 16 Aug 86 19:04 EDT
Date: 16 Aug 86 16:02 PDT
From: Alan Bomberger <[e-mail]>
Subject: Mailing Software
To: [e-mail]
Message-ID: <COR-ACB-9R5GS@OFFICE-1>

Believe it or not there are people out there that have to pay for disk space,
further there are mail systems that insure that the receiver pays for mail
space.  I already resent having to pay for all the headers that go on endlessly
about the itinerary of a message.  I was away for a while and ended up paying
for many "extra" disk pages because of people mailing giant files containing
source.  Go for a separate list.

17-Aug-86 08:03:27-MDT,1873;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sun 17 Aug 86 08:03:19-MDT
Received: from simtel20.arpa by AMSAA.ARPA id a008389; 17 Aug 86 9:42 EDT
Date: Sun, 17 Aug 1986  07:41 MDT
Message-ID: <[e-mail]>
Sender: [e-mail]
From: Keith Petersen <[e-mail]>
To:   [e-mail]
Subject: Bug in CP/M UUENCODE fixed

Several weeks ago UUENCODE and UUDECODE, written in Turbo Pascal for
use on CP/M, were posted to Info-Cpm (net.micro.cpm).  A bug in
UUENCODE caused one additional "garbage" record to be included at the
end of the file.  This caused the resultant UUDECODEd file to be one
record longer than the original file and prevented error checking with
CRCK.  The fixed area is shown below (thanks to Bernie Eiben):

  procedure encode1;

    begin {encode1};
      if numbytes = bytesperhunk then flushhunk;
      endofinfile := not (getbyte(hunk[numbytes]));
      if not endofinfile then numbytes := succ(numbytes)  {No succ at EOF -BE}
    end; {encode1}

I do hope we don't end up using uuencode/uudecode when other means are
available for doing file transfers.  We CP/M'ers have maintained a
relatively error-free environment over the years.  The
Uuencode/Uudecode system contains NO CRC or CHECKSUM error checking!
If we were to add that, the programs would no longer be compatible
with Unix versions.  I suggest that anyone sending files using this
program include a CRC list in the introduction so readers can check
the decoded files with my CRCK program.  CRCK, by the way, is also
available for Unix.  It's in PD:<UNIX.CPM>CRCK2.C here at SIMTEL20.

--Keith Petersen
Arpa: [e-mail]
uucp: {ihnp4,allegra,cmcl2,dual,decvax,mcnc,mcvax,vax135}!seismo!w8sdz
GEnie Mail: W8SDZ
RCP/M Royal Oak: 313-759-6569
17-Aug-86 09:07:10-MDT,1837;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sun 17 Aug 86 09:06:56-MDT
Received: from simtel20.arpa by AMSAA.ARPA id a008456; 17 Aug 86 10:38 EDT
Date: Sun, 17 Aug 1986  08:37 MDT
Message-ID: <[e-mail]>
Sender: [e-mail]
From: Keith Petersen <[e-mail]>
To:   [e-mail]
Subject: UUENCODE/UUDECODE for CP/M-80 now available from SIMTEL20

Thanks to Bernie Eiben we now have the latest versions of UUENCODE and
UUDECODE for CP/M-80 available from SIMTEL20 as:

Filename            Type     Bytes     CRC

Directory PD:<CPM.TURBOPAS>
UUECPM.ARC.1            BINARY     48862  3700H

The ARC contains Turbo Pascal source, executable .COM files and
UUENCODED versions of the .COM files.

If you're interested only in the .COM files, they are available as:

Directory PD:<CPM.STARTER-KIT>
UUDECODE.COM.1            BINARY     10496  00D8H
UUENCODE.COM.1            BINARY     10240  2EAFH

UNARC for CP/M-80 (previously announced) is available as:

Directory PD:<CPM.CPMLIB>
UNARC12.LBR.1            BINARY    104448  AC35H <--with source

If you're interested only in the .COM files, they are available as:

Directory PD:<CPM.STARTER-KIT>
UNARC.COM-Z80.1            BINARY      4096  C209H <--Z80 version
UNARCA.COM-8080.1        BINARY      4736  DF9BH <--8080 version

If you are unable to access SIMTEL20 because of network restrictions
these files are also available on my RCP/M Royal Oak (MI) which may be
accessed at 300 bps (Bell 103a), 1200 bps (Bell 212a), or 2400 bps
(V.22 bis).  The telephone number is [phone].  They can also be
found on the CP/M RoundTable on General Electric Information Services
GEnie.

--Keith Petersen
Arpa:   [e-mail]
GEnie Mail: W8SDZ
uucp:   {ihnp4,allegra,cmcl2,dual,decvax,mcnc,mcvax,vax135}!seismo!w8sdz
17-Aug-86 22:25:51-MDT,805;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sun 17 Aug 86 22:25:42-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a012411; 17 Aug 86 23:58 EDT
Received: from USENET by SMOKE.BRL.ARPA id a022070; 17 Aug 86 23:41 EDT
From: Jon Mandrell <[e-mail]>
Newsgroups: net.micro.cpm
Subject: make for CP/M 2.2?
Message-ID: <[e-mail]>
Date: 14 Aug 86 21:38:27 GMT
To:       [e-mail]

line eater food

  Does anyone know of a 'make' program for vanilla CP/M 2.2?  Public
domain preferably, but I guess I would pay something for it.
  Barring this, if I sit down and write one, would anyone be interested
in it?
--
Jon Mandrell    (ihnp4!uw-beaver!tikal!amc!jon)
Applied Microsystems Corp.

"flames >& /dev/null" - me
18-Aug-86 04:10:24-MDT,1114;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 18 Aug 86 04:10:16-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a014249; 18 Aug 86 5:35 EDT
Received: from USENET by SMOKE.BRL.ARPA id a025167; 18 Aug 86 5:30 EDT
From: Jay Denebeim <[e-mail]>
Newsgroups: net.micro.cpm
Subject: Re: Looking for a good C compiler
Message-ID: <[e-mail]>
Date: 15 Aug 86 13:18:46 GMT
To:       [e-mail]

>I've a friend who's been using Ecosoft C (for Z80), and rates it quite highly.
>It's not cheap, but it's apparently pretty good.

    Depends on what you concider cheap.  Ecosoft C is $49.95.  I like it
alot, but it's HUGE.  I've used bother BDS and Ecosoft, BDS is very fast, and
comes with alot of goodies, but is terribly non-K&R.  Ecosoft is standard,
cheap, and has a good library, but it's slow and the modules have to be very
small to compile under it.

--
Jay Denebeim                "One world, one egg, one basket."
UUCP:  {seismo,decvax,ihnp4}!mcnc!rti-sel!ethos!jay
BBS:   Deep Thought, ZNode #42 300/1200/2400 919-471-6436
18-Aug-86 04:18:14-MDT,1116;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 18 Aug 86 04:18:05-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a014427; 18 Aug 86 5:52 EDT
Received: from USENET by SMOKE.BRL.ARPA id a025624; 18 Aug 86 5:44 EDT
From: Peter Arrgh Korn <[e-mail]>
Newsgroups: net.micro.cpm
Subject: Re: Bondwell laptops
Message-ID: <[e-mail]>
Date: 16 Aug 86 01:37:44 GMT
To:       [e-mail]

In article <[e-mail]> [e-mail] (John Norman) writes:

>For that matter, are there other manufacturers who make CP/M laptops?

Epson's PX-8 is a CP/M laptop.  There are a few stores that still sell
them...in fact, Epson supports them fairly well.  They go up to ~32K I
believe, and come with a word-processor (ski-writer).  3.5" drives
are amoung the accessories available.

Peter
--
-----
Peter "Arrgh" Korn               "Fred Astaire?  Heck, Ginger Rogers did
[e-mail]              everything he did, backwards,
{decvax,dual,hplabs,sdcsvax,ulysses}!ucbvax!korn            and in high heels!"
18-Aug-86 04:54:49-MDT,925;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 18 Aug 86 04:53:15-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a014414; 18 Aug 86 5:50 EDT
Received: from USENET by SMOKE.BRL.ARPA id a025410; 18 Aug 86 5:38 EDT
From: John Norman <[e-mail]>
Newsgroups: net.micro.cpm
Subject: Bondwell laptops
Message-ID: <[e-mail]>
Date: 15 Aug 86 18:42:01 GMT
Sender: [e-mail]
To:       [e-mail]

I have read a fair amount recently about the new Bondwell MSDOS laptop, but
what about the CP/M *laptop*?  What is the list price?  Is it available
more cheaply through discounters?  This computer is apparently different
from the Bondwell which looks like a Kaypro-

For that matter, are there other manufacturers who make CP/M laptops?

harvard!h-sc4!norman
[e-mail]
[e-mail]
-John
18-Aug-86 08:13:01-MDT,1271;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 18 Aug 86 08:12:50-MDT
Received: from ucb-vax.arpa by AMSAA.ARPA id a022942; 18 Aug 86 9:28 EDT
Received: by ucbvax.Berkeley.EDU (5.53/1.14)
    id AA28057; Mon, 18 Aug 86 06:25:32 PDT
Received: by jade.Berkeley.Edu (5.31 (CFC 4.21)/5.6.2)
    id AA06107; Sun, 17 Aug 86 18:04:57 PDT
Received: by lapis.Berkeley.Edu (4.20/5.6)
    id AA10043; Sun, 17 Aug 86 18:04:53 pdt
Date: Sun, 17 Aug 86 18:04:53 pdt
From: David Phillip Oster <[e-mail]>
Message-Id: <[e-mail]>
To: [e-mail]
Subject: Fine old Cp/M machine for sale, $300

I'd like to sell my Exidy Sorceror.  This one has 32k of on-board memory,
and an S-100 card cage holding a 16k memory card and a disk jockey disk
controller, controlling 2 8" double density Discus drives.  The monitor is
by Sony.
Software includes Cp/M 2.2, MBasic, OBasic, Rom Basic, Fig Forth,
and drivers for Wordstar.
The system works fine.  I paid over $3000.00, and I'd like to receive
$300.00 plus the cost of shipping.
--- David Phillip Oster        -- "We live in a Global Village."
Arpa: [e-mail]  --
Uucp: ucbvax!ucblapis!oster     -- "You are Number Six."
18-Aug-86 09:02:49-MDT,961;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 18 Aug 86 09:02:41-MDT
Received: from nadc.arpa by AMSAA.ARPA id a026549; 18 Aug 86 10:28 EDT
Date: 18 Aug 1986 10:19:50-EDT
From: [e-mail]
To: [e-mail]
Subject: possible bug in CP/M 3.0 "PIP"

CP/M 3.0 supports the character "_" (underline) as valid within a filename and
it is so documented.  Builtins such as ERASE and RENAME have no trouble
handling this, nor does either the builtin or transient DIR.  However, PIP just
gets bent out of shape and refuses to accept the syntax (e.g. a:=b:tvx_io.c).
I am referring specifically to the Commodore 128 version of 3.0, but suspect it
is really a generic problem.  Digital Research sent me their set of application
notes, but I didn't see this mentioned as a fixed bug.  I don't suppose there is
any easy fix short of re-writing PIP?

Sincerely,
Frank Prindle
[e-mail]
19-Aug-86 09:22:27-MDT,930;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 19 Aug 86 09:22:09-MDT
Received: from wiscvm.arpa by AMSAA.ARPA id a007121; 19 Aug 86 10:29 EDT
Received: from (FISHER)RPICICGE.BITNET by WISCVM.WISC.EDU on 08/18/86
  at 11:33:31 CDT
Date: 18 August 86 12:30-EST
From:  [e-mail]
To:  [e-mail]
X-Acknowledge:
Subject: P2DOS0 and the H/Z 89

Date: 18 August 1986, 12:17:06 EAS
From: FISHER at RPICICGE
To:   INFO-CPM at AMSAA.ARPA
Subject: P2DOS0 and the H/Z 89

Has anyone successfully installed P2DOS0 on a Heath-89?  ...on any
machine?  (P2DOS0 is a PD BDOS replacement for Z80 machines.)  I
think I correctly patched it over the DR BDOS, but upon booting
the system I get only a lower-case "m" and an otherwise blank stare
from the CRT.  I'm using the Heath version of CP/M 2.2(.0.4).

J.S.Fisher  [e-mail]

19-Aug-86 11:55:28-MDT,624;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 19 Aug 86 11:55:17-MDT
Received: from mitre.arpa by AMSAA.ARPA id a013562; 19 Aug 86 13:10 EDT
Full-Name: Thomas Reid
Message-Id: <[e-mail]>
Organization: The MITRE Corp., Washington, D.C.
To: [e-mail]
Subject: P2DOS0
Date: Tue, 19 Aug 86 13:10:41 -0500
From: [e-mail]

J. S. Fisher was having trouble installing it on his H89.  I looked at
the documentation but did not see any benefits from installing it.
Could someone who is using it explain why.  Thanks to all.  Tom.
19-Aug-86 15:30:00-MDT,785;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 19 Aug 86 15:29:54-MDT
Received: from rand-unix.arpa by AMSAA.ARPA id a021058; 19 Aug 86 16:14 EDT
Received: by rand-unix.ARPA; Tue, 19 Aug 86 10:37:04 pdt
Message-Id: <[e-mail]>
To: Jon Mandrell <[e-mail]>, [e-mail]
Subj: 'make' for cp/m 2.2
Date: Tue, 19 Aug 86 10:36:15 PDT
From: [e-mail]

The DateStamper "toolkit" disk includes a public-domain 'make'
developed by Neil Maron and me from an earlier ms-dos version.
It requires DateStamper, which runs on vanilla CP/M 2.2 and some
2.2 emulators, such as zrdos.

Contact Plu*Perfect Systems [phone], Box 1494, Idyllwild CA 92349.

--bridger mitchell
19-Aug-86 19:42:51-MDT,1098;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 19 Aug 86 19:42:41-MDT
Received: from simtel20.arpa by AMSAA.ARPA id a023893; 19 Aug 86 21:12 EDT
Date: Monday, 18 August 1986  10:29-MDT
Message-ID: <[e-mail]>
Sender: [e-mail]
From: [e-mail]
To: [e-mail]
Subject:   Commodore C128 CP/M file printing program
ReSent-From: [e-mail]
ReSent-To: [e-mail]
ReSent-Date: Tue 19 Aug 1986 19:11-MDT

Now available from SIMTEL20:

Filename            Type     Bytes     CRC

Directory PD:<CPM.C128>
801PRT10.LBR.1            BINARY     26752  59D8H

801PRT10 is a program I wrote for the C128 CP/M and 1525/MPS801/MPS803
printer.  It prints out a text file, but insures that the last lines
aren't dropped, as tends to happen with those printers. It also
filters out linefeeds.  The distribution library includes the DOC
file, the source code in 'C', the COM file and a file listing the
files in the library.

Matt Kimmel,
[e-mail]
19-Aug-86 20:14:14-MDT,1033;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 19 Aug 86 20:14:04-MDT
Received: from simtel20.arpa by AMSAA.ARPA id a023962; 19 Aug 86 21:36 EDT
Date: Tue, 19 Aug 1986  19:35 MDT
Message-ID: <[e-mail]>
Sender: [e-mail]
From: Keith Petersen <[e-mail]>
To:   [e-mail]
Cc:   [e-mail]
Subject: Rev of the uuencode/uudecode programs ...

Klaus, thank you for your message suggesting a change in
uuencode/uudecode because of possible problems sending some
characters through BITNET.

Before you do this, please make some tests with me to see if the
regular uuencoded files will pass through without error.  I have just
received a netmailed uuencoded LBR file from another BITNET user who
wanted to submit a new program to our CP/M archives.  He used my CRCK
program to provide a CRC value for me to check against after
uudecoding.  It matched perfectly.

--Keith Petersen
20-Aug-86 04:37:18-MDT,808;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 20 Aug 86 04:37:12-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a026226; 20 Aug 86 5:45 EDT
Received: from USENET by SMOKE.BRL.ARPA id a008165; 20 Aug 86 5:34 EDT
From: "Andrew M. Moore" <[e-mail]>
Newsgroups: net.micro.cpm
Subject: Re: Bondwell laptops
Message-ID: <[e-mail]>
Date: 18 Aug 86 15:22:43 GMT
To:       [e-mail]

> For that matter, are there other manufacturers who make CP/M laptops?

   I believe that the NEC Starlet and Epson Geneva are CP/M laptops.

Andrew Moore
arpa [e-mail]
uucp ...mit-eddie!moore
 tel [phone] BBS Sat-Sun 3/12/2400  (laptop computer support & more)
  us Box 121, North Quincy, MA  02171
20-Aug-86 06:32:06-MDT,1375;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 20 Aug 86 06:31:47-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id aa28374; 20 Aug 86 7:38 EDT
Received: from USENET by SMOKE.BRL.ARPA id a009715; 20 Aug 86 7:30 EDT
From: Jeffrey Miller <[e-mail]>
Newsgroups: net.micro.cpm
Subject: Re: PCPI Applicard Tech Info
Message-ID: <[e-mail]>
Date: 22 Aug 86 04:12:45 GMT
Posted: Fri Aug 22 00:12:45 1986
To:       [e-mail]



*
Regarding the request for info on the Applicard, please see my response
on net.micro.apple.
                         Jeff


        *************************************************
        *       Jeff Miller                             *
        *       Multimate International Corp.           *
        *       52 Oakland Avenue                       *
        *       East Hartford, CT  06108-9911           *
        *       [phone] x257                     *
        *  UUCP:                                        *
        * ...!seismo!utah-cs!utah-gr!pwa-b!mmintl!jeffm *
        *                                               *
 -->    * P.S. I can't *mail* to ARPA but I can receive *    <--
 -->    * from there.  News I *post* should get there.  *    <--
        *************************************************
*
20-Aug-86 08:18:58-MDT,2134;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 20 Aug 86 08:18:47-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a028374; 20 Aug 86 7:37 EDT
Received: from USENET by SMOKE.BRL.ARPA id a009710; 20 Aug 86 7:30 EDT
From: Jeffrey Miller <[e-mail]>
Newsgroups: net.micro.apple,net.micro.cpm
Subject: Re: PCPI Applicard Tech Info
Message-ID: <[e-mail]>
Date: 16 Aug 86 03:50:56 GMT
Posted: Fri Aug 15 23:50:56 1986
To:       [e-mail]


In article <[e-mail]> [e-mail] (Jim Gilbert) writes:
>
>
>I would like to obtain the following reference information for the PCPI
>Applicard Z-80 processor and the accompanying CP/M implementation.
>I think that Personal Computer Products Inc. was purchased by Micropro or
>went out of business.

Recently I called PCPI ([phone]) and got lots of their BIOS info just
by talking to one of their tech support people.  They are very helpful.
Their implementation of CP/M is much more elegant and customizable than that
of Microsoft.  I know they're not out of business unless they are advertising
their new laser printer in PC Week for masochistic purposes only.

I'm looking for CP/M 3.0 or ZCPR3 for the Applicard.  Does anyone know if
they are available?
                            Jeff
*

        *************************************************
        *       Jeff Miller                             *
        *       Multimate International Corp.           *
        *       52 Oakland Avenue                       *
        *       East Hartford, CT  06108-9911           *
        *       [phone] x257                     *
        *  UUCP:                                        *
        * ...!seismo!utah-cs!utah-gr!pwa-b!mmintl!jeffm *
        *                                               *
 -->    * P.S. I can't *mail* to ARPA but I can receive *    <--
 -->    * from there.  News I *post* should get there.  *    <--
        *************************************************
(an Apple CP/M guy in a strange MS-DOS land)
*
20-Aug-86 11:34:54-MDT,1155;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 20 Aug 86 11:34:35-MDT
Received: from apg-1.arpa by AMSAA.ARPA id a010784; 20 Aug 86 12:47 EDT
Date: Wed, 20 Aug 86 12:36:16 EDT
From: Robert Bloom AMSTE-TEI 3775 <[e-mail]>
Subject: Re: xmodem bulk transfers
In-Reply-To: Your message of Mon, 18 Aug 86 10:22:54 EDT
To: [e-mail]
Cc: [e-mail], [e-mail]

The 'work around' that I use to make bulk downloads from my unix
machine to my micro is to use MEX in the 'read' mode.  Goes something
like this:
    1. use mget for the simtel20 batch
      2. copy a directory listing down to the micro
    3. while holding the line open, drop to a text editor on
the micro.
        delete the junk at the start and end of the file with
            the directory in it
        change all lines from 'filename' to
            'sendout "umodem -sbl filename";r filename
        save it
    4. go back into mex and give the command 'read filelist' where
filelist has the modified file directory
    5. watch it go
Lots of capability with a read file - once I downloaded 50 files with
one command.

bob bloom

20-Aug-86 21:14:34-MDT,825;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 20 Aug 86 21:14:26-MDT
Received: from simtel20.arpa by AMSAA.ARPA id a000798; 20 Aug 86 22:22 EDT
Date: Wed, 20 Aug 1986  20:21 MDT
Message-ID: <[e-mail]>
Sender: [e-mail]
From: Keith Petersen <[e-mail]>
To:   [e-mail], [e-mail]
Subject: TAC software #113

It appears the the recent update of the TAC software to #113 increased
the input buffers enough to suuport XMODEM protocol (yeh, I know it's
MODEM protocol).  I've been able to upload to SIMTEL20 from TACs that
previously didn't work for that.  If you've been using KERMIT because
your buffer was too small, give TMODEM a try now and see if it works
for uploading.

--Keith
21-Aug-86 05:22:45-MDT,1169;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 21 Aug 86 05:22:37-MDT
Received: from mit-multics.arpa by AMSAA.ARPA id a001558; 21 Aug 86 6:55 EDT
Date:  Thu, 21 Aug 86 06:49 EDT
From:  "John C. Klensin" <[e-mail]>
Subject:  CP/M laptops
To:  [e-mail]
cc:  [e-mail]
Message-ID:  <[e-mail]>

The Epson Geneva (PX-8) definitely is a CP/M machine.  The Starlet (I am
pretty sure) and the SORD can operate as CP/M machines, but have
additional (and default) operating modes that are intended to be
'simple' and that don't look like CP/M.  The PX-8 moves beyond/above
CP/M only in having a menu-selection mode for commands that is easily
shut off.

Incidentally, these three machines are really laptops, with weights in
the 4-5 pound range.  The Bondwell, as I understand it, requires a
somewhat stronger lap.

If anyone cares, I have no affiliation with any of the four companies,
and this should not be construed as a recommendation for or against of
the machines, although I do have a much-travelled and much-abused Epson.
   John
21-Aug-86 09:20:57-MDT,900;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 21 Aug 86 09:20:36-MDT
Received: from apg-1.arpa by AMSAA.ARPA id a008021; 21 Aug 86 10:24 EDT
Date: Thu, 21 Aug 86 10:19:00 EDT
From: Earnie Boyd AMSTE-TEF 4377 <[e-mail]>
Subject: Maryland BB for CPM
To: [e-mail]

There is at least on BB near/in Baltimore that supports CPM, MSDOS & PCDOS.
That is at the Heath Electronic Center.  The BB telephone number is
301-661-2175, the board operates 24 hours a day, with the hours of 6-8am
being reserved for the SYSOPS.  There is no charge, and several of the
users have MILNET (SIMTEL20) access.  The board is closed, you can call in
at 300, 1200 & 2400 baud and get the info for obtaining access - put your
printer on.  The BB is not as busy as on might expect and there is a one
hour limitation unless you are uploading.

21-Aug-86 10:03:14-MDT,1232;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 21 Aug 86 10:03:07-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a006727; 21 Aug 86 9:51 EDT
Received: from USENET by SMOKE.BRL.ARPA id a002006; 21 Aug 86 9:37 EDT
From: Rick <[e-mail]>
Newsgroups: net.micro.cpm
Subject: Re: Posting software directly to info-cpm or net.micro.cpm:
Message-ID: <[e-mail]>
Date: 19 Aug 86 03:49:17 GMT
To:       [e-mail]

>
> [munch]
>
>     As a Usenet site with no connections to the ARPA net I have
> been drooling over some of the teasers we've gotten in the form of
> SIMTEL20 lists.  I requested info from the net regarding existence
> of a CP/M BBS in the Maryland area and got no responses.  So I vote
>          .........
>     I'm glad to see that CP/M lives!
>
>     Bob Amen

      The complete SIG/M library is available FREE from the owners of
      the PUBLIC DOMAIN library for CP/M machines on their BBS. The
      PC-Blue (PC-DOS) software library is also available FREE from
      the same BBS.

      The BBS is in New Jersey, their number is [phone].
      Amatuer Computer Group of NJ (ACGNJ)

       a
>
21-Aug-86 10:30:04-MDT,655;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 21 Aug 86 10:29:53-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a010559; 21 Aug 86 11:48 EDT
Received: from USENET by SMOKE.BRL.ARPA id a005981; 21 Aug 86 11:37 EDT
From: [e-mail]
Newsgroups: net.micro.cpm,net.wanted
Subject: EXIDY SORCEROR VIDEO
Message-ID: <[e-mail]>
Date: 18 Aug 86 10:38:45 GMT
Posted: Mon Aug 18 12:38:45 1986
To:       [e-mail]

Has anyone ever converted an EXIDY to 80 column by 24 line video display?
Please email any ideas/suggestions.

Peter Wright (thanks for looking).
21-Aug-86 10:36:25-MDT,1309;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 21 Aug 86 10:36:13-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a010578; 21 Aug 86 11:48 EDT
Received: from USENET by SMOKE.BRL.ARPA id a006017; 21 Aug 86 11:39 EDT
From: Robert Dale <[e-mail]>
Newsgroups: net.micro.cpm
Subject: ZCPR Info Requested
Message-ID: <[e-mail]>
Date: 5 Aug 86 20:18:55 GMT
Posted: Tue Aug  5 22:18:55 1986
To:       [e-mail]

I'd like to know more about ZCPR before investing time and energy in trying
to bring it up on my Z80-based system.  Can someone provide me with a
reference to an article or book that describes ZCPR - preferably one that is
available outside of the USA?  I seem to recall mention of a book in this
newsgroup some time ago.   Also, frequently there is mention in this
newsgroup of ZSYS software:  is this the same thing, or related?  And how
can someone at my side of the pond obtain this software?  Please mail
responses, and I'll post a summary if it looks to be interesting to others.

--

Robert Dale    University of Edinburgh, Centre for Cognitive Science,
                2 Buccleuch Place, Edinburgh, EH8 9LW, Scotland.

UUCP:    ...!ukc!cstvax!epistemi!rda
JANET:    [e-mail]
21-Aug-86 20:29:08-MDT,1978;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 21 Aug 86 20:28:43-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a020408; 21 Aug 86 19:38 EDT
Received: from USENET by SMOKE.BRL.ARPA id a014745; 21 Aug 86 19:32 EDT
From: "Willie Smith, LTN Components Eng." <[e-mail]>
Newsgroups: net.micro.cpm
Subject: re:    UUENCODE/UUDECODE    MIX(master) Editor
Message-ID: <[e-mail]>
Date: 20 Aug 86 14:32:41 GMT
Sender: [e-mail]
To:       [e-mail]

Many thanks to those who assisted me with getting UUENCODE and
UUDECODE up, in the interests of paying it forward:
    Anyone who needs a HEX version of the latest UUENCODE and
UUDECODE (load with LOAD/DDT/DEHEXIFY/etc) for CP/M, pelase write
me and I will send you the files.

Hmm, it would appear that the MIX editor is really touchy about
stack space, if it can't run with interrupts.  My hack was fairly
simple, I used a debugger (ZDT) to disassemble the program at
0100H and followed the logic as best as I could.  One of the first
things the program does is to set up the stack pointer to a known
value.  I patched this location to set up the stack pointer to FFFFH
(where there is some free room in my BIOS), and the program appeared
to work better (the continual crashes went away).  When I explained
this to the guy at MIX, he said it couldn't be the stack, as the
program used 4K (not a typo, four kilobytes) of stack space.  As it
didn't use that much in that blank space at the end of my bios, I
assumed it set up one stack for the init routines and then another
for the actual execution.  [Special NOTE: the stack builds _down_
from the top, if you do this, point at the _highest_ adress in the
stack space when you say  LD  SP,SPACE].  Even after fixing that
major problem, though, I don't know if it's worth it....

Willie Smith

UUCP:    decwrl!wookie.dec.com!smith
Internet:    [e-mail]
21-Aug-86 21:10:41-MDT,900;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 21 Aug 86 21:10:33-MDT
Received: from ut-ngp.arpa by AMSAA.ARPA id a020777; 21 Aug 86 22:31 EDT
Date: Thu, 21 Aug 86 21:09:44 cdt
From: mknox <[e-mail]>
Posted-Date: Thu, 21 Aug 86 21:09:44 cdt
Message-Id: <[e-mail]>
Received: by ngp.UTEXAS.EDU (4.22/4.22)
    id AA03897; Thu, 21 Aug 86 21:09:44 cdt
To: [e-mail]
Subject: DateStamper query


I would appreciate information from anyone who has used/uses DateStamper.
What restrictions does it place on the host system?  I have modified
my CCP/BDOS somewhat.  Am I going to have problems?  Will it lower
my TPA?  I know a lot of things that "auto-install" hide themselves
below CCP.  This lowers the TPA a *lot*, because most programs overlay
the CCP.

                    tnx,
                        [e-mail]

22-Aug-86 04:05:04-MDT,1206;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 22 Aug 86 04:04:53-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a000257; 22 Aug 86 4:25 EDT
Received: from USENET by SMOKE.BRL.ARPA id a018446; 22 Aug 86 5:30 EDT
From: [e-mail]
Newsgroups: net.micro.cpm
Subject: Re: PMATE Text Editor Information
Message-ID: <[e-mail]>
Date: 20 Aug 86 10:15:10 GMT
Posted: Wed Aug 20 12:15:10 1986
Expires:
Sender:
Followup-To:
Keywords:
To:       [e-mail]


        FAO Jay Sage at MIT and apologies to everyone else.

        Jay,
                Thank you for your offer.

        My snail-mail address is -

                Peter Kendell,
                Dept. 32381,
                STC Telecommunications Ltd.,
                Oakleigh Road South,
                New Southgate,
                London N11 1HB,
                UK
--
    Peter Kendell <[e-mail]>

    ...!mcvax!ukc!stc!pete

    "Lord Finchley tried to mend the Electric Light,
     Himself.
     It Struck him Dead: and Serve him Right!
     It is the Business of the Wealthy Man,
     To give Employment to the Artisan."
22-Aug-86 06:24:03-MDT,991;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 22 Aug 86 06:23:53-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a001459; 22 Aug 86 7:39 EDT
Received: from USENET by SMOKE.BRL.ARPA id a020189; 22 Aug 86 7:32 EDT
From: Richard Foulk <[e-mail]>
Newsgroups: net.micro.cpm
Subject: MEX long distance codes?
Message-ID: <[e-mail]>
Date: 19 Aug 86 14:56:33 GMT
Posted: Tue Aug 19 10:56:33 1986
To:       [e-mail]

A friend was just complaining about the lack of support
for dial code prefixes with MEX.  He'd like to be able
to make calls via Sprint and only have to tell MEX about
his access code, etc., only once.

I haven't used MEX in quite some time, but I thought it
had that capability.

Could someone who knows please mail me a description of
how to use that feature (if it exists).

Thanks very much.


--
Richard Foulk        (..islenet!bigtuna!richard)
Honolulu, Hawaii
22-Aug-86 07:58:51-MDT,1715;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 22 Aug 86 07:58:41-MDT
Received: from wiscvm.arpa by AMSAA.ARPA id a001016; 22 Aug 86 6:07 EDT
Received: from (FISHER)RPICICGE.BITNET by WISCVM.WISC.EDU on 08/20/86
  at 14:51:47 CDT
Date: 20 August 86 15:52-EST
From:  [e-mail]
To:  [e-mail]
X-Acknowledge:
Subject: BITNET mail follows

Date: 20 August 1986, 15:20:07 EAS
From: FISHER at RPICICGE
To:   INFO-CPM at AMSAA.ARPA
Re:   Uuencode/uudecode character transparency over the net

I did some experimenting with the character translation that takes place
when one crosses a BITNET/ARPANET gateway.  Many characters were filtered
during the EBCDIC <==> ASCII conversions, particularly by the UCBJADE
gateway.  However, it appears that ALL of the characters used by the
uuencode/uudecode programs have unique representations on both sides
of the WISCVM gateway.  Also, the translation performed at WISCVM
seems to agree exactly with the translation VM on IBM hosts uses when
communicating with ASCII terminals.  (I do not know if the same
statement can be made for MVS hosts and the non-IBM BITNET machines.)

At any rate, at least for VM BITNET sites, ARPANET to BITNET via the
normal WISCVM path, then to CP/M via something suitable like KERMIT
should yield the desired results.

(**Note**:  The EBCDIC values used for brackets, braces, backslash,
etc, are not same values needed for a TN-train printer.  So, though
clear-text files may look funny when displayed on an IBM printer or
327X terminal, they should still arrive in CP/M-land correctly :-)

J.S.Fisher     [e-mail]

22-Aug-86 10:56:55-MDT,1333;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 22 Aug 86 10:56:43-MDT
Received: from lll-mfe.arpa by AMSAA.ARPA id a007793; 22 Aug 86 11:24 EDT
Date: Fri, 22 Aug 86 11:24 EST
From: [e-mail]
Subject: Trying to send '*' within MEX dialing
To: [e-mail]

From:    <[e-mail]>   (Richard C. Secrist)
Date:    Fri, 22-AUG-1986 11:25 EST
To:      [e-mail]
Message-ID: <[OAK.SAINET.MFENET].E25E51E0.008F3D1A.SECRIST>
Header-Disclaimer: I don't like my headers either !
X-VMS-Mail-To: CPM

I am running MEX 1.14 on my Apple (kudos Nightowl !).  Anyway, either
with or without the Smartmodem overlay, I can't seem to enter a '*'
as part of the number... it's an invalid number if I do.  The MEX doc
says that it doesn't stop you from entering what you want, but I of
course have the source for the overlays I', using and it doesn't do it !
(Sticking to the typical ATDT 1-615-etc. works fine.)  I want to do an
'ATDT *70,' to disable my call-waiting.  Grumble.

Does anybody dial a '*' into their MEX ?  Thanks !

r c s



- - -
P.S.> if you are using the MFE gateway to ARPA from your own subnet and don't
have a double header like I do, could you please tell me how you did it ?
22-Aug-86 12:45:43-MDT,1241;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 22 Aug 86 12:45:32-MDT
Received: from ucb-vax.arpa by AMSAA.ARPA id a000971; 22 Aug 86 13:08 EDT
Received: by ucbvax.Berkeley.EDU (5.53/1.16)
    id AA21441; Fri, 22 Aug 86 10:09:13 PDT
Received: by ucdavis.UCDAVIS.EDU (4.12/4.7)
    id AA25514; Fri, 22 Aug 86 09:51:50 pdt
Received: by clover.ucdavis.edu (4.12/4.7)
    id AA14837; Fri, 22 Aug 86 09:52:09 pdt
Date: Fri, 22 Aug 86 09:52:09 pdt
From: Eric Hildum <ucdavis!clover![e-mail]>
Message-Id: <[e-mail]>
To: ucdavis![e-mail]
Subject: BBS in the California area?


I am also one of those people who does not have access to SIMTEL20 through
the ARPA net.  Are there any BBS systems in or near California that have the
SIMTEL20 software?

We do have a BITNET connection at this site, and I can request that files be
loaded to it if anyone can give me the appropriate instructions on how to do
this.  (Our administrators are considering installing a software package to
allow the server style of transfer - if anyone has information on available
software to do this I would like to hear about it.)

                Thanks,
                  Eric
22-Aug-86 13:11:02-MDT,2678;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 22 Aug 86 13:10:29-MDT
Received: from ll.arpa by AMSAA.ARPA id a000403; 22 Aug 86 14:12 EDT
Date: Fri 22 Aug 1986 14:09:55 EDT
From: [e-mail]
MMDF-Warning:  Parse error in preceding line at AMSAA.ARPA
Subject: P2DOS Information
To: [e-mail]
Cc: [e-mail]
Message-ID: <[e-mail]>

   Below is a copy of an earlier message from Keith Petersen about P2DOS.
This DOS (version 2.1 at least) has many attractive features.  You have the
full source, so you can tailor it as you wish.  It supports time/date
stamping of files in a CP/M3-compatible way.  It has a search path, like
that of ZCPR, but unlike the latter is useful when a running program looks
for other files, such as overlays, swap files, libraries, and so on.  One of
the troublesome limitations of ZCPR is that it can find the main COM file,
such as WS.COM, along the search path, but then when WS looks for its
overlays, it can't find them and the program grinds to a halt.  There are,
of course, other solutions to this problem.  P2DOS now also supports the
archive bit so that modified files can be identified.  The one feature that
ZRDOS has that P2DOS currently lacks is the ability to automatically log in
new disks.

                Jay Sage
                MIT Lincoln Lab

--------  copy of message from Keith Petersen  -------

A Z80fied BDOS replacement, has a public file and DOS-level search
capability, supports time-stamping and RTC setting.  Supplied with a
preconfigured ZCPR2 CCP.  All source code and ZEX file for
assembly/installation included.  Requires M80/L80, not hard to adapt
to other assemblers.  Other new features of P2DOS include testing of
console status after 256 characters output.  Error routines give
more information.  Public files are supported, you can access a
public file from any user number.  File R/O error message occurs if
Public, File R/O, and System files are active.  Disk size can be as
large as one gigabyte.  File size can be as large as one megabyte.

If you are unable to access SIMTEL20 because of network restrictions
please remember that MOST of the new files announced to Info-Cpm are
also available on my RCP/M Royal Oak (MI) which may be accessed at
300 bps (Bell 103a), 1200 bps (Bell 212a), or 2400 bps (V.22 bis).
The telephone number is [phone].  They are also available from
the CP/M RoundTable on General Electric Information Services' GEnie.

--Keith Petersen
Arpa:   [e-mail]
GEnie Mail: W8SDZ
uucp:   {ihnp4,allegra,cmcl2,dual,decvax,mcnc,mcvax,vax135}!seismo!w8sdz


22-Aug-86 14:15:37-MDT,4316;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 22 Aug 86 14:15:10-MDT
Received: from ll.arpa by AMSAA.ARPA id a001360; 22 Aug 86 14:38 EDT
Date: Fri 22 Aug 1986 14:08:19 EDT
From: [e-mail]
MMDF-Warning:  Parse error in preceding line at AMSAA.ARPA
Subject: DateStamper Information
To: [e-mail]
Cc: [e-mail]
Message-ID: <[e-mail]>

   Below is a description of DateStamper that appeared earlier on the net by
one of its authors, Bridger Mitchell.  I would add the following comments.

   The original version poked changes into the BDOS and might have failed to
work with a modified BDOS.  However, the current release includes a version
that will work with any kind of CP/M2.2-compatible BDOS, such as ZRDOS or,
presumably, P2DOS.

   There are two ways to install DateStamper.  The easy way is as an RSX
(resident system extension) below the CCP.  In that case you are right that
it takes up quite a bit of TPA (2K for the CCP plus about 1K more for
DateStamper itself).  If you can move your CCP, BDOS, and BIOS down by about
1K, you can install DateStamper above the BIOS.  Then the TPA space you lose
is only that required for the DateStamper code.  This TPA loss, however, is
permanent; you cannot recover it by not loading DateStamper (you can, of
course, boot from a vanilla CP/M disk).  With DateStamper running as an RSX,
it can be removed from memory when its presence is causing a problem.  Bruce
Morgen and I wrote a program (not yet distributed) called CLRRSX that will
remove DateStamper and any other RSXs present.

   It is very impressive how unobtrusively DateStamper functions.  I had
worried that all the accesses to the time/date file would slow things down,
but it turns out not to be noticeable.  I am very pleased with it.  The only
problem I have encountered is that when files are copied with standard
utilities, the destination file is given the current date/time rather than
the date/time of the source file.  This is, of course, not a defect of
DateStamper but of the utilities.  Gradually, as more of us use DateStamper,
utilities will be modified to support it.  I plan to add it to the next
release of VFILER and would like to add it to some general copy program like
PPIP, MCOPY, and/or AC.

                                        Jay Sage
                                        MIT Lincoln Lab

--------------------  copy of message from Bridger Mitchell follows  -------

DateStamper is a CP/M 2.2 system extension for time-and-date-stamping of
files.  It occupies under 1K of high memory, either above/in the bios
or below the CCP and stamps the created, accessed and modified date-and-time
of each file.  Each directory entry has a corresponding 16-byte
entry in the special datestamper file, which is the first directory entry
and occupies the first unreserved groups on a disk.  A disk is prepared,
once, for datestamping with the PUTDS utility, which creates the file,
moving existing entries/groups if necessary.

Except for the use of the one directory entry and space for the file
(1K per 64 directory entries) DateStamper and non-datestamper disks
are totally compatible.  All disk i/o is done at the bios level,
with little overhead.

DateStamper runs with most any type of real-time clock. Or with none,
in which case it keeps the date plus  "relative time" - one tick per
file access.  The clock interface is portable - applications programs
can read the current time with an extended bdos-getversion call.

The major utilities supplied with DateStamper are SDD - an extension
of Super Directory to include created/accessed/modified dates/times,
and DATSWEEP - a many-featured file-maintenance program that supports
incremental file backup, etc. by date and time.  Applications programs
can obtain a file's datestamps through a specified interface.

DateStamper runs with the standard Digital Research CP/m 2.2 bdos,
with various Apple 2/2e z80 look-alikes, Magnolia-H/Z 89/90, ZRDOS,
and some other variants.  Not, however, with 3.0 or TurboDos.

For more information contact:

PluPerfect Systems [phone]
Box 1494
Idyllwild CA 92349

--bridger mitchell (I am a co-author).


22-Aug-86 16:45:54-MDT,1263;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 22 Aug 86 16:45:36-MDT
Received: from ll.arpa by AMSAA.ARPA id a000430; 22 Aug 86 14:16 EDT
Date: Fri 22 Aug 1986 14:10:54 EDT
From: [e-mail]
MMDF-Warning:  Parse error in preceding line at AMSAA.ARPA
Subject: Lost Pete Kendell's Address
To: [e-mail]
Cc: [e-mail]
Message-ID: <[e-mail]>

The I/O processor connecting me to our IBM 3081 went down just as I was
getting to Pete Kendell's address in his message to me, and when the
machine came back up, the message was gone for good.  So once again
I have to beg everyone's indulgence for posting this message publicly,
since Pete and I have found no way to exchange messages directly.

Pete, please send me your address once again.  If anyone else reading
this message still has a copy of the address, perhaps they could forward
it to me directly.  Anyone else who wants more information on PMATE is
welcome to send me their address, and I will mail out more information
about PMATE.  My wife has found a source for the 8-bit version, and I
supply the modifications to make a somewhat ZCPR3-compatible version.

       Jay Sage
       MIT Lincoln Lab


22-Aug-86 17:09:42-MDT,2059;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 22 Aug 86 17:09:29-MDT
Received: from rand-unix.arpa by AMSAA.ARPA id a003350; 22 Aug 86 15:38 EDT
Received: by rand-unix.ARPA; Fri, 22 Aug 86 11:12:27 pdt
Message-Id: <[e-mail]>
To: mknox <[e-mail]>, [e-mail]
Re: DateStamper requirements
Date: Fri, 22 Aug 86 11:12:13 PDT
From: [e-mail]

DateStamper is a resident extension of the bios and bdos.  The
resident code is less than 1K for standard cp/m 2.2 and about 1.2 K
for apple/zrdos/... variants of cp/m.

Installation options are:

1. locate "above the bios" .  This requires free memory anywhere between
   the bios jump table and the top of memory.  Usually users need to run
   MOVCPM to create a 1K or 1.25K smaller system.  Some ZCPR3 users use
   the IOP buffer area (they don't use IO packages) and leave the system
   size unchanged.

2. locate below the ccp.  This makes the ccp resident too, and uses
   an additional 2K of memory.  The bios' warm-boot routine is bypassed,
   so the ccp/bdos remain resident.  A very few programs assume or require that
   nothing is resident below the ccp; they won't run with this
   installation option, nor with DDT or EX or ...

DateStamper runs with an unmodified cp/m 2.2 bdos and 8080 or z80-type
processors.  The longer (~1.2K) version runs with some non-standard
2.2-type dos's.  It is not compatible with cp/m 3, mpm, and most other networks.

DateStamper does not require a clock, but uses one if available.
If not, file access "times" are sequential numbers, plus the date.

The datestamping file is 1/2 the size of the directory for each disk
prepared for datestamping (usually 1 or 2K).  It must be the first
entry in the directory and occupy the first data groups on the disk.
Except for these requirements, datestamped disks are fully compatible
with any cp/m system.  The PUTDS utility creates this file, once, for
each disk.

--bridger mitchell
22-Aug-86 17:39:38-MDT,2068;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 22 Aug 86 17:39:20-MDT
Received: from simtel20.arpa by AMSAA.ARPA id a000354; 22 Aug 86 19:05 EDT
Date: Fri 22 Aug 86 03:08:29-MDT
From: Rick Conn <[e-mail]>
Subject: Re: ZCPR Info Requested
To: [e-mail]
cc: [e-mail]
In-Reply-To: <[e-mail]>
Message-ID: <[e-mail]>

    You can obtain the Z System software and documentation from:

        Echelon, Inc.
        885 N. San Antonio Road
        Los Altos, CA  94022
        415/948-3820

    Echelon offers three books and a biweekly newsletter on the subject.
The books are:
        1. ZCPR3: The Manual - a comprehensive tech manual on
the system, describing the release version of the system in much detail
        2. ZCPR3: The Libraries - a comprehensive ref manual on
the reusable software components libraries Z3LIB, SYSLIB, and VLIB
        3. Z System User's Guide - a very easy-to-read overview
of the Z System and its capabilities

    There is also a new document, Z-Index, which is a comprehensive
index to the newsletters.

    Echelon also offers an array of Z System-specific commercial products,
including editors, debuggers, assemblers, compilers, data base tools,
communications programs, and a spreadsheet.

    There are Z-Nodes all over the world that you can dial into to
access Z System software and some RCP/M systems also carry it.  There
is also ZSIG, the Z System User's Group, which publishes its own newsletter
and users disks.  The ZSYS archive on SIMTEL20 contains both Z System and
ZSIG software.  There have also been many magazine articles published on the
Z System in Byte, Computer Language, Micro/Systems Journal, Dr Dobbs,
and many manufacturer-specific magazines, such as Heath.
Several distributers and OEMs carry the system, including one in France.

    As a bottom line, I recommend contacting Echelon with your questions,
and they can send you more information.

        Rick Conn (author of ZCPR3 and its toolset)
-------
22-Aug-86 22:17:30-MDT,891;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 22 Aug 86 22:17:22-MDT
Received: from rand-unix.arpa by AMSAA.ARPA id a001332; 22 Aug 86 23:47 EDT
Received: by rand-unix.ARPA; Fri, 22 Aug 86 18:46:58 pdt
Message-Id: <[e-mail]>
To: [e-mail]
Subj: ?big-board I bios defect
Date: Fri, 22 Aug 86 18:46:48 PDT
From: [e-mail]


Beta-testing for BackGrounder has turned up a serious defect in a Big
Board I double-density 8" bios (19 June 83).  It handles sector
deblocking very inefficiently, resulting in a 20-fold slowdown in
effective disk i/o when reading then writing the same random records!

Does someone have a more recent version?  Is the problem present
in the BB II bioses also (the code contains lots of calls to "flush").
Is the author reachable?

--bridger




22-Aug-86 22:32:23-MDT,905;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 22 Aug 86 22:32:13-MDT
Received: from simtel20.arpa by AMSAA.ARPA id a001361; 22 Aug 86 23:59 EDT
Date: Fri, 22 Aug 1986  22:00 MDT
Message-ID: <[e-mail]>
Sender: [e-mail]
From: Keith Petersen <[e-mail]>
To:   [e-mail]
Cc:   [e-mail]
Subject: Trying to send '*' within MEX dialing

I just tried entering a '*' as part of a phone number in MEX114.  It
worked just fine for me.  Do the following (example phone number
used):

MEX>phone my=*70,13135551212

Then you can say CALL MY and it will do it.  Note the comma to allow a
pause after the *70 to allow for time for the second dialtone to come
up.  Don't use dashes or you may exceed the buffer space available for
the number.

--Keith
22-Aug-86 22:55:20-MDT,625;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 22 Aug 86 22:55:12-MDT
Received: from simtel20.arpa by AMSAA.ARPA id a001371; 23 Aug 86 0:03 EDT
Date: Fri, 22 Aug 1986  22:04 MDT
Message-ID: <[e-mail]>
Sender: [e-mail]
From: Keith Petersen <[e-mail]>
To:   [e-mail]
Cc:   [e-mail]
Subject: Trying to send '*' within MEX dialing

Your modem may require a quote to accept the '*'.  If that's the case
then:

MEX>phone my="*70,13135551212

should work.

--Keith
22-Aug-86 23:34:47-MDT,3074;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 22 Aug 86 23:34:36-MDT
Received: from simtel20.arpa by AMSAA.ARPA id a001439; 23 Aug 86 0:54 EDT
Date: Fri, 22 Aug 1986  22:55 MDT
Message-ID: <[e-mail]>
Sender: [e-mail]
From: Keith Petersen <[e-mail]>
To:   Richard Foulk <[e-mail]>
Cc:   [e-mail]
Subject: MEX long distance codes?

The MEX modem program DOES handle alternate long distance codes.  Here
is an excerpt from the manual:

   Appendix 2: Alternate Long Distance Service numbers (ALDS):

This appendix details the use of Alternate Long Distance Service
(ALDS) numbers with MEX.

You may have two ALDS numbers defined; simply enter them as you would
any other number, but give them a name of '>' or '<' (normal delay
characters, passwords, etc may be included).  Then, if you have a
number you'd like to route through your ALDS service, simply prefix it
with the associated '>' or '<'.  An example should clarify this:

You have MCI service, your password is 98765, and it takes 2-4 seconds
to connect after the number is dialed.  You also have Sprint (you
cover all your bases, don't you?), the password is 12345, and it
sometimes takes 6 seconds to reach the number after it is dialed.
Finally, you have a Hayes Smartmodem; a comma in the dialing string is
a 2-second pause (is it really?  I don't have a Hayes, so let's
pretend).

In order to use both services, we'll put one number on the > key:

        [MEX] A0>>PHONE >=555-9122,,98765         <<--- MCI

note the four second delay with the two commas, then the password.

Now Sprint:

        [MEX] A0>>PHONE <=555-8144,,,12345

<longer delay, different password>.

Now RBBS Rockhead is a long, long distance call; it's available only
through Sprint (and, of course, Ma Bell). We decide that if we can't
make it through Sprint, we don't want to call RBBS Rockhead.  Here's
how we enter the number:

        [MEX] A0>>PHONE ROCKHEAD=<202-555-1414

Now RBBS Aristocrat is our favorite BBS; if Sprint is jammed up, we'd
like the option of dialing it over Ma Bell lines.  So we define it
without an ALDS marker, like this:

        [MEX] A0>>PHONE ARISTOCRAT=202-555-2222

Now notice that we can still call Aristocrat through Sprint or MCI
with:

        [MEX] A0>>CALL <ARISTOCRAT              <<--- Sprint
        [MEX] A0>>CALL >ARISTOCRAT              <<--- MCI

But we must explicitly enter the ALDS symbol in the CALL command.

Since Rockhead is defined with a leading '<', it will always go
through MCI; we don't have to supply an ALDS symbol in the CALL
command (we can switch to the other ALDS number, however, by
specifying the other ALDS symbol in the CALL command; eg,"CALL
>ROCKHEAD" will switch to MCI even though we've defined Sprint as
Rockhead's ALDS number).

In short, the left or right arrow specification is treated as if its
ALDS number were part of the number being dialed.
24-Aug-86 09:07:03-MDT,1488;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sun 24 Aug 86 09:06:56-MDT
Received: from simtel20.arpa by AMSAA.ARPA id a006022; 24 Aug 86 10:36 EDT
Date: Sun, 24 Aug 1986  08:31 MDT
Message-ID: <[e-mail]>
Sender: [e-mail]
From: Keith Petersen <[e-mail]>
To:   [e-mail]
Cc:   [e-mail], [e-mail], [e-mail]
Subject: INFO-MODEM7 name changed to INFO-XMODEM

Rich, here is a new entry to replace INFO-MODEM7 on your next
Arpa/Milnet mailing list "list of lists".

--Keith

-------------------------
[e-mail]

   Discussion group for XMODEM Christensen protocol file transfer programs.
   The group is concerned with development, upgrades and bug-fixes.

   The current mail archives on SIMTEL20 for this list are:

   <ARCHIVES.XMODEM>XMODEM-ARCHIV.TXT  for the current messages

   <ARCHIVES.XMODEM>XMODEM.ARCHIV.ymmdd  for the older messages

   <ARCHIVES.XMODEM>MODEM7.ARCHIV.ymmdd  for the older messages before
                                         the list name was changed.

   These files are available via ANONYMOUS FTP for those with TCP/IP
   access to the Internet.

   All requests to be added to or deleted from this list, problems,
   questions, etc., should be sent to [e-mail].

   Coordinator: Keith Petersen <[e-mail]>
24-Aug-86 18:03:33-MDT,500;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sun 24 Aug 86 18:03:26-MDT
Received: from simtel20.arpa by AMSAA.ARPA id a007104; 24 Aug 86 19:38 EDT
Date: Sun 24 Aug 86 17:39:47-MDT
From: Rick Conn <[e-mail]>
Subject: Z-News 508
To: [e-mail]
Message-ID: <[e-mail]>

... is now in PD:<ZSYS.NEWS> as Z-NEWS.508 and 5Q8 and in PD:<ZSYS.Z-NEWS>
as Z-NEWS.5Q8.  Thanks to Keith for the upload.
-------
25-Aug-86 04:30:51-MDT,2943;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 25 Aug 86 04:30:39-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a008163; 25 Aug 86 5:48 EDT
Received: from USENET by SMOKE.BRL.ARPA id a023987; 25 Aug 86 5:30 EDT
From: Jon Mandrell <[e-mail]>
Newsgroups: net.micro.cpm
Subject: Re: Looking for a good C compiler
Message-ID: <[e-mail]>
Date: 20 Aug 86 19:05:31 GMT
To:       [e-mail]

In article <[e-mail]> [e-mail] (Jay Denebeim) writes:
>
>    Depends on what you concider cheap.  Ecosoft C is $49.95.  I like it
>alot, but it's HUGE.  I've used bother BDS and Ecosoft, BDS is very fast, and
>comes with alot of goodies, but is terribly non-K&R.  Ecosoft is standard,
>cheap, and has a good library, but it's slow and the modules have to be very
>small to compile under it.
>

I think you are talking about the PC based version.  I purchased ECO-C for
my system and payed $300, along with a high-speed assembler and linker.
I have used it for quite awhile, and I like it.

Some disadvantages:
1) Comments nest.  Some people like this, but it causes problems when I
   want to port code from UNIX, and someone has commented out a line
   like this:
     /* x=2;   /* set x to 2 */
2) It is slow, but that is fairly well made up for by the assembler
   package.
3) It is missing the fread() and fwrite() routines.  They aren't hard
   to write, but it is a bother.
4) A bug:  if you reference off of a pointer using a negative subscript,
   it will crash the compiler.  that is 'x=ptr[-1];'  instead, I use
   'x= *(ptr-1);', which works just fine.

Some advantages:
1) The assembler they provide with it (SLR, at extra cost) is FAST.  They
   say it will manage six times the speed of M80, and it's true.  To those
   people out there still living with M80 and L80, I highly recommend
   changing over.
2) When the compiler gives error messages, they are good, with multiple
   lines of text, and even referencing a page number in the C book that
   comes along with it.
3) It is complete, with all data types supported, nested structures, unions,
   and all of the other little beasties that you want.
4) It provides routines to access the I/O ports, so you don't need to write
   assembly language routines to do this.
5) The manual is good.  They completely cover all of the function library,
   as well as all of the switches.
6) The provide the math functions.
7) You can get source to the libraries (send them floppies and $10).

I have not seen the problem with large modules mentioned, since I have taken
stuff right off of the net, and compiled it.  It does sometimes barf on
switch statements that contain more than about 128(?) cases.

Disclaimer: Just a happy customer.

--
Jon Mandrell    (ihnp4!uw-beaver!tikal!amc!jon)
Applied Microsystems Corp.

"flames >& /dev/null" - me
25-Aug-86 21:48:56-MDT,975;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Mon 25 Aug 86 21:48:50-MDT
Received: from brl-aos.arpa by AMSAA.ARPA id a000869; 25 Aug 86 23:10 EDT
Received: from mit-mc.arpa by AOS.BRL.ARPA id a004972; 25 Aug 86 23:04 EDT
Received: from LANL.ARPA by MC.LCS.MIT.EDU 25 Aug 86 23:02:16 EDT
Received: by LANL.ARPA (5.51/4.7)
    id AA09469; Mon, 25 Aug 86 21:00:28 MDT
Received: by a.ARPA (4.12/4.7)
    id AA25076; Mon, 25 Aug 86 21:00:01 mdt
Date: Mon, 25 Aug 86 21:00:01 mdt
From: Dale Carstensen <[e-mail]>
Message-Id: <[e-mail]>
To: [e-mail], [e-mail]
Subject: XLISP

The C Users' Group lists volume 176 of its library as XLISP 1.6, but I think
the announcement mentioned it would be updated to be the latest version
whenever Dave Betz updated XLISP.  The address and phone is:
  C Users' Group
  Box 97
  McPherson, KS 67460

 [phone]

26-Aug-86 09:47:46-MDT,1107;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 26 Aug 86 09:47:30-MDT
Received: from brl-aos.arpa by AMSAA.ARPA id a009293; 26 Aug 86 10:49 EDT
Received: from hi-multics.arpa by AOS.BRL.ARPA id a012533; 26 Aug 86 10:43 EDT
Posted-Date:  26 Aug 86 08:57 CDT
Date:  Tue, 26 Aug 86 08:55 CDT
From:  "Wayne M. Stenson" <[e-mail]>
Subject:  change bar utility needed
To:  [e-mail], [e-mail]
Message-ID:  <[e-mail]>


I find myself in need of a utility to automatically insert change bars
into a document prepared by WordStar and printed by MailMerge.  The
preliminary research I have done has uncovered one possibility using
Carousel Microtools DIFF and FORMAT utilities which are similar to the
UNIX tools but run under CPM-80.  Does anyone know of any other tools
which may fit this need either public domain, shareware or proprietary?
The tools must run under either CPM (perferred) or MSDOS.

Please respond to Stenson at HI-MULTICS.

Thanks in advance!

Wayne Stenson
26-Aug-86 22:58:27-MDT,1958;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Tue 26 Aug 86 22:58:20-MDT
Received: from simtel20.arpa by AMSAA.ARPA id a023546; 27 Aug 86 0:16 EDT
Date: Tue, 26 Aug 1986  22:17 MDT
Message-ID: <[e-mail]>
Sender: [e-mail]
From: Keith Petersen <[e-mail]>
To:   [e-mail]
Subject: LZW Cruncher and NSWP/NULU/BISHOW/QLIST

Relayed from RCP/M Royal Oak:

Date: 08/25/86
From: Daniel Patt,
Re:   LZW CRUNCHER and NSWP7 NULU

I have been using the LZW (or is it LWZ) crunch12, uncrunch12 and
typelz15 series. The speed and space savings are great.  I was
wondering if anyone knows or could tell me if NSWP7, NULU, Qlist and
similar programs can be modified to allow both squeezed and crunched
actions.  Has anyone heard if this is being done or do they know where
to get the files to allow one to integrate the LZW into those
programs.  Any info would be helpful to have.

                          Thanks, Dan


Date: 08/25/86
From: Bill Duerr
To:   Daniel Patt
Re:   Crunch Programs

Dan, the "new" programs (NSWP andLU) do not come with source, so
therefor we are at the mercy of the author to modify the programs.
Dave Rand is now in the PC/MS-DOS area and hasn't updated NSWP for
some time.  I don't know whats going on with NULU, there is still an
outstanding bug in that program, but I haven't seen and update for a
while.  The author said he would modify the program for ZCPR3.

Qlist does have source as I recall, but I think that program is
written in 8080 code, so it probably shouldn't be made machine
dependent by adding the CRUNCH routines which only support Z80 code.
There is supposed be a 8080 version of CRUNCH on its way.  Anyway, I
haven't seen any updates to Qlist.

I would like to add BISHOW to you list.  I really miss not working
with CRUNCHed files using that program.

Bill
27-Aug-86 06:19:57-MDT,715;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 27 Aug 86 06:19:49-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a026723; 27 Aug 86 7:34 EDT
Received: from USENET by SMOKE.BRL.ARPA id a007773; 27 Aug 86 7:31 EDT
From: David Shoat <[e-mail]>
Newsgroups: net.micro.cpm
Subject: Simtel20 info wanted
Message-ID: <[e-mail]>
Date: 21 Aug 86 10:34:24 GMT
Posted: Thu Aug 21 12:34:24 1986
To:       [e-mail]

'Scuse the ignorance, but could someone fill me in on the details of accessing
the SIMTEL20 archives from UUCP?

Thanks.

David Shoat
Dept. of Medical Cardiology
Glasgow Royal Infirmary.
27-Aug-86 21:16:26-MDT,1121;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 27 Aug 86 21:16:19-MDT
Received: from nosc.arpa by AMSAA.ARPA id a023619; 19 Aug 86 18:49 EDT
Received: by bass.ARPA (5.31/4.7)
    id AA10625; Tue, 19 Aug 86 15:49:15 PDT
Received: by cod.ARPA (5.31/4.7)
    id AA18052; Tue, 19 Aug 86 15:49:13 PDT
Message-Id: <[e-mail]>
Date: Tue, 19 Aug 86 13:17:26 PDT
From: Marc Wilson <crash!pnet01!pro-mercury![e-mail]>
To: pnet01!crash!noscvax![e-mail]
Subject: Re: P2DOS0 and the H/Z 89
Resent-Date:  Wed, 27 Aug 86 22:25:56 EDT
Resent-From:  [e-mail]
Resent-To:    [e-mail]

     I have implemented P2DOS on an Ampro Little Board successfully. It's not
to difficult. If you're not using M80, then *don't* use LOAD.COM to make the
.COM file. Use MLOAD. LOAD will make a file that is much too big. Load
P2DOS.COM on top of your system image with DDT. In normal DRI CP/M 2.2, the
BDOS is at address 1180 in the system image. Hope this helps!

Marc Wilson
noscvax!crash!pnet01!pro-mercury!mwilson@nosc
27-Aug-86 21:21:56-MDT,1948;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Wed 27 Aug 86 21:21:45-MDT
Received: from nosc.arpa by AMSAA.ARPA id a025532; 20 Aug 86 3:28 EDT
Received: by bass.ARPA (5.31/4.7)
    id AA00924; Wed, 20 Aug 86 00:28:13 PDT
Received: by cod.ARPA (5.31/4.7)
    id AA27903; Wed, 20 Aug 86 00:28:11 PDT
Message-Id: <[e-mail]>
Date: Tue, 19 Aug 86 22:35:38 PDT
From: Marc Wilson <crash!pnet01!pro-mercury![e-mail]>
To: pnet01!crash!noscvax![e-mail]
Subject: Re: P2DOS
Cc: pnet01!crash!noscvax!crash!pnet01!pro-mercury![e-mail]
Resent-Date:  Wed, 27 Aug 86 22:27:57 EDT
Resent-From:  [e-mail]
Resent-To:    [e-mail]

     The documentation that is in P2DOS.LBR is very scanty. Here is a very
brief rundown of some of P2DOS's features.

     o Written in Z80 rather than in 8080. Makes it smaller and presumably
       faster.

     o Supports an RTC through an extra BDOS call. Also supports date & time
       stamping, with the correct routines in your BIOS ( which the docs do
       *not* elaborate on ).

     o Supports Public files through one of the unused attribute bits ( #2, I
       think ). Any file set to a SYStem file, and with this atttribute set,
       can be accessed from any user area.

     o Supports a path-search feature akin to ZCPR3's, except at the BDOS
       level, rather than that of the CCP. Only SYStem files can be found in
       this way.

     o Expanded error messages. You are now told what the error is ( normal
       BDOS message ), what BDOS function caused the error, and the file
       involved, if any.

     I have had the combination of P2DOS and ZCPR3 running on my Ampro for
over a month now, and have noticed no bugs. On the other hand, I'm not using
all the features listed above.

Marc Wilson
noscvax!crash!pnet01!pro-mercury!mwilson@nosc
28-Aug-86 06:25:00-MDT,1100;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 28 Aug 86 06:24:52-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a013651; 28 Aug 86 7:47 EDT
Received: from USENET by SMOKE.BRL.ARPA id a027060; 28 Aug 86 7:37 EDT
From: ModemUserGroupChairman <[e-mail]>
Newsgroups: net.wanted,net.micro.pc,net.micro.cpm
Subject: Kermit/ Xmodem for the DEC Rainbow
Message-ID: <[e-mail]>
Date: 27 Aug 86 20:17:28 GMT
To:       [e-mail]

--

    I am looking for Kermit for the DEC Rainbow-100A. The machine
    has 64K of RAM, 2 disk drives and the standard monochrome monitor.

    If you have source, please send it if it will assemble in 64K.
    If it won't, please send a uuencoded, or some other form of
    the executable.

    I don't care whether it runs under MS-DOS or CPM.


        Thanks for any help I get.

            Anees Munshi


    Anees Munshi
    @ University of Toronto Engineering Comp. Facility :A
    {allegra,ihnp4,linus,decvax}!utzoo!utcsri!utecfa!mugc
    {allegra,ihnp4,linus,decvax}!utzoo!utcsri!utecfb!munshi
28-Aug-86 06:30:24-MDT,1281;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Thu 28 Aug 86 06:30:11-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a013655; 28 Aug 86 7:47 EDT
Received: from USENET by SMOKE.BRL.ARPA id a027111; 28 Aug 86 7:38 EDT
From: Marc Lewert <[e-mail]>
Newsgroups: net.micro.cpm
Subject: Re: Simtel20 info wanted
Message-ID: <[e-mail]>
Date: 27 Aug 86 16:10:44 GMT
To:       [e-mail]

In article <[e-mail]>, [e-mail] (David Shoat) writes:
> 'Scuse the ignorance, but could someone fill me in on the details of accessing
> the SIMTEL20 archives from UUCP?
>
> Thanks.
>
> David Shoat
> Dept. of Medical Cardiology
> Glasgow Royal Infirmary.

me too, please.
--
=========================================================================
Marc Lewert                           UUCP: ...hplabs!pyramid!triada!marc
Triad Systems Corp.
PO Box 61779                          MA Bell: [phone]
Sunnyvale, Ca. 94088-1779

Disclaimer:  All views are my own and do not reflect those of my
             employer, friends, or family unless otherwise noted.
=========================================================================

29-Aug-86 04:12:30-MDT,997;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Fri 29 Aug 86 04:12:24-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a001506; 29 Aug 86 5:40 EDT
Received: from USENET by SMOKE.BRL.ARPA id a016968; 29 Aug 86 5:38 EDT
From: Steve Corbin <[e-mail]>
Newsgroups: net.micro.cpm
Subject: INFO-CPM
Message-ID: <[e-mail]>
Date: 28 Aug 86 19:59:03 GMT
To:       [e-mail]

Can anyone tell me how I can get on the INFO-CPM mailing list?  I tried
sending mail to INFO-CPM-REQUEST@AMSAA but it didn't work.  I am not familiar
with accessing ARPAnet or anything other than UUCP.  Any help for a beginner
would be appreciated.

BTW,  I have a z80 based CPM 2.2 machine that I have been hacking around
with.  It is the Xerox 820-1 board.  Anyone out there know of bulleten boards
or other sources of information for upgrading hardware and software?

Stephen Corbin
{ihnp4, allegra, linus} ! encore ! corbin
30-Aug-86 17:25:21-MDT,922;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sat 30 Aug 86 17:25:08-MDT
Received: from simtel20.arpa by AMSAA.ARPA id a003494; 30 Aug 86 18:59 EDT
Date: Sat, 30 Aug 1986  17:00 MDT
Message-ID: <[e-mail]>
Sender: [e-mail]
From: Keith Petersen <[e-mail]>
To:   [e-mail]
Cc:   [e-mail]
Subject: BYE510 now available from SIMTEL20
In-reply-to: Msg of 30 Aug 1986  07:33-MDT from mek%UMass.BITNET at WISCVM.WISC.EDU

    I found the BYE5 insert for BYE5... But I discovered that it only
    works with BYE510.  Where can I get a copy of the BYE510 library?
    Is there a copy on SIMTEL20 anywhere?

Yes, it's just been uploaded and is now available from SIMTEL20 as:

Filename            Type     Bytes     CRC

Directory PD:<CPM.BYE5>
BYE510.LBR.1            BINARY    174208  2DA0H

--Keith
31-Aug-86 04:07:01-MDT,622;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sun 31 Aug 86 04:06:56-MDT
Received: from brl-smoke.arpa by AMSAA.ARPA id a004545; 31 Aug 86 5:38 EDT
Received: from USENET by SMOKE.BRL.ARPA id a010641; 31 Aug 86 5:30 EDT
From: Dave <[e-mail]>
Newsgroups: net.micro.cpm,net.wanted
Subject: kaypro 10
Message-ID: <[e-mail]>
Date: 29 Aug 86 20:49:58 GMT
Keywords: help
To:       [e-mail]


does anyone have schematic drawings or know where i could get drawings
for a kaypro 10.
        thanks,
        dave
             ...ihnp4!killer!dave
31-Aug-86 10:02:31-MDT,2194;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sun 31 Aug 86 10:02:21-MDT
Received: from simtel20.arpa by AMSAA.ARPA id a005058; 31 Aug 86 11:41 EDT
Date: Sun, 31 Aug 1986  09:42 MDT
Message-ID: <[e-mail]>
Sender: [e-mail]
From: Keith Petersen <[e-mail]>
To:   [e-mail]
Subject: Quick reference list of SIMTEL20 CP/M directories

Quick reference list of SIMTEL20's PD:<CPM.x> directories
as of August 31, 1986 (where 'x' is one of the names below):

22RSX         COBOL         FINANCE       MODEM2        SUBMIT
6502          COMND         FORTH-83      MODEM7        SYSUTL
AMETHYST      CPM3          FORTRAN       MSOFT         T20-SQUSQ
APPLE         CPM68K        GENASM        NEWS          TERM
ASMUTL        CPM86         GENCOM        NSTAR         TOPS-20
ATARI         CPMINFO       GENDOC        NUBYE         TRS-80
AZTEC-C       CPMLIB        GENIE         OSBORN        TURBODOS
BASIC         CPR86         GRAPHICS      PACKET        TURBODOS-SIGI
BBSLISTS      CUG           HAMMING       PASCAL        TURBOPAS
BDOS          DATABASE      HAMRADIO      PBBS          TXTUTL
BDSC-1        DBASEII       HDUTL         PILOT80       VAXVMS
BDSC-2        DEBUG         HEATH         PLOT33        VDOEDIT
BDSC-3        DIRUTL        HELP          PPSPEL        VOICE
BDSC-4        DISASM        HEX           PUBKEY        WSTAR
BSTAM         DISKPLOT      IMP           PUBPATCH      XCCP
BYE3          DSKBUF        INSIDCPM      RBBS          XLISP
BYE5          DSKUTL        KAYPRO        RBBS4         YAM
BYT85FEB      EDITC80       LIST          RCPM          Z8EDEBUG
BYT85JAN      EDITOR        MACLIB        ROS           ZCPR
C128          EDUCATION     MATH          SCREENGEN     ZCPR2
C64           EMX           MBBS          SMALLC21      ZCPR3
C80           EPSON         MEMTEST       SORT          ZMODEM
CATLOG        FAST2         MEX           SPELL
CB80          FILCPY        MICNET        SQU-PORT
CBIOS         FILE-DOCS     MISC          SQUSQ
CCP           FILUTL        MODEM         STARTER-KIT
31-Aug-86 11:48:06-MDT,1318;000000000000
Return-Path: <[e-mail]>
Received: from AMSAA by SIMTEL20.ARPA with TCP; Sun 31 Aug 86 11:47:57-MDT
Received: from simtel20.arpa by AMSAA.ARPA id a005269; 31 Aug 86 13:22 EDT
Date: Sun, 31 Aug 1986  11:23 MDT
Message-ID: <[e-mail]>
Sender: [e-mail]
From: Keith Petersen <[e-mail]>
To:   [e-mail], [e-mail], [e-mail]
Subject: TAC buffer expansion news

BBN recently updated the Arpa/Milnet TAC software to version #113.  As
I mentioned in a previous message, I am now able to upload files using
the 128-byte record "XMODEM Protocol" via any TAC that I have tried.
The input buffers were previously 64 bytes.

Today I tried using the 1k packet size option available in some newer
versions of micro and mainframe implementations of the various
versions of XMODEM.  It worked perfectly at 1200 bps through three
different TACs that I tried!

It would seem safe to assume that BBN has expanded the input buffers
on many, if not all, ports to over 1024 bytes.

If you have had problems in the past uploading to your host via a TAC,
try again.  Your TAC announces in the sign-on banner what version of
the software it is running.  If it says #113, you're in business!

--Keith