ZPM/ZCCP on the C128

Mike Gordillo

unread,

Sep 3, 1994, 5:51:18 PM9/3/94

to

JHalloran wrote :

>I'm much more familiar with 64 & 128 mode than with CP/M. Do you have any
>advice about installing ZPM on a C128? I picked up the archive, which
>I think was the newest release (name ZPM3N10.ARK?). There was a readme
>file associated with the archive which said that the version's
>MAKEDOS.COM file would work on the C128, while the older versions
>wouldn't.

>The end result was that I followed the instructions, and a "CPM+.NEW"
>file was created without any error messages. I deleted the old
>"CPM+.COM" file and gave the new file that name. The new system
>would partially boot, and then lockup.

>If you have any advice it would be appreciated. Its a matter of
>curiosity more than anything else.
---------------------------------------------------------------------------

I installed the ZPM by re-assembling the entire BIOS and then appending
the ZPM BDOS along the way. This was before that makedos program was
tweaked to work with a 128 (or whatever was done). I think I used it
(later) successfully to latch the ZPM BDOS onto a standard BIOS; the
BIOS I re-assembled being a user-modified project. The system file should
be renamed to CPM+.SYS, not CPM+.COM. This may be your problem, perhaps?

As far as I know, ZPM alone just gives you a history command buffer and
slightly better I/O. With ZPM and ZCCP (CCP.COM replacement) running
together, you get ZCPR3.3 compatibility and better integration of paths
and other stuff (which at least to me) is a pain to do under vanilla cp/m.

If anyone has something constructive to add, please do.

Mike

Ismael Cordeiro

unread,

Sep 5, 1994, 8:40:29 AM9/5/94

to

Mike Gordillo (621...@mercury.utb.edu) wrote:

> I installed the ZPM by re-assembling the entire BIOS and then appending
> the ZPM BDOS along the way. This was before that makedos program was
> tweaked to work with a 128 (or whatever was done).

Where did you find that new version of MAKEDOS?

> As far as I know, ZPM alone just gives you a history command buffer and
> slightly better I/O. With ZPM and ZCCP (CCP.COM replacement) running
> together, you get ZCPR3.3 compatibility and better integration of paths
> and other stuff (which at least to me) is a pain to do under vanilla cp/m.

The problem is that some programs without support for ZCPR don't work. CRR
is an example.

Ismael

Simeon Cran

unread,

Sep 6, 1994, 8:24:56 AM9/6/94

to

In <34ar4m$m...@geraldo.cc.utexas.edu>, 621...@mercury.utb.edu (Mike Gordillo) writes:
>If anyone has something constructive to add, please do.

The author hangs out here... so you could try talking to him. Or email me direct!

simeon

Ismael Cordeiro

unread,

Sep 6, 1994, 2:00:13 PM9/6/94

to

Simeon Cran (sim...@myz80.brisnet.org.au) wrote:

> The author hangs out here... so you could try talking to him. Or email me direct!

Hi, Simeon.

Nice to see you here. I was just thinking about sending you email. The
problem is that a text file at the pub/cbm/os/cpm directory of
ccnga.uwaterloo.ca says that the MAKEDOS.COM in ZPM3N10.ARK would create a
correct CPM+.SYS on the C128 but it doesn't. It creates one that goes almost
to the end of the booting process but then it freezes the system and a reset
is needed. Is it really supposed to create a correct CPM+.SYS on the C128 or
who wrote that text file just assumed it did because there's no mention of
problems with the C128 in the MAKEDOS.TXT file?

By the way, in the list of files that are supposed to be included on
ZPM3N10.ARK there is one called ECHOTERM.COM that is not on the archive.
What happened to it? Could you uuencode it and send me?