Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
CP/M-68K in Pascal?
233 views
Skip to first unread message
Floppy Software
Mar 11, 2015, 1:48:53 PM3/11/15
to
Hi all!
While searching information on TEX from DR, I have found a CP/M-68K internal doc. with interesting information.
It is a memo called cpm0706.nro regarding the development of CP/M-68K.
This file is in the v101 directory of cpm68k1.zip file, downloaded time ago from the Unofficial CP/M Website.
In the memo, there are two interesting things:
--quote--
The Pascal
version of CP/M-68K must be translated into C and shipped as
a product as soon as possible following the preliminary
release.
--unquote--
and
--quote--
Portable CP/M will have to wait.
--unquote--
In fact, in the website we can read:
--quote--
Reading v101/doc/ and v102a/doc/ makes interesting trivia: 1."The Pascal version of CP/M-68K..." (cpm0706.rno)
--unquote--
Then, two interesting things I believe:
- There was a CP/M written in Pascal.
- Portable CP/M (CP/M coded in C) was a DR product,
as discussed some time ago in this newsgroup.
The document in full is as follows, after formatting:
--quote--
Memo: Vincent Alia
Ruth Driscoll
Bill Fitler
Bob Herlien
Tim McCormick
Bill Tyler xc: Tom Rolander Re: Minutes of CP/M-68K
Status Meeting 07/06 From: Steve Williams
As we discussed this morning, the status of the CP/M-68K
project is as follows: BDOS ---- The BDOS is 99% coded,
lacking only the Set exception vector, program chain and
flush buffers functions. Approximately 60% of this code is
tested. Bob has committed to a working BDOS by 7/16. CCP ---
The CCP lacks BATCH processing. It is felt that this is a
desirable feature, but that the system would be usable
without it. BATCH processing is therefore a candidate for
featurectomy if need be. Bootstrap --------- No progress has
been made on a bootstrap loader for CP/M on the EXORmacs.
DDT --- DDT lacks File I/O and program load functions. It is
not usable without program load. Bill has promised program
load by 7/12. File I/O is another candidate for
featurectomy. Diskette Format Utility
----------------------- Nothing has been done about a
diskette format utility for the EXORmacs. Utilities
--------- A problem exists somewhere between XLINK and the
Motorola linker. Initialized data areas in the utilities do
not have the right values in the right places after the link
process. Chaki will attempt to use the Alcyon linker to
correct this problem. ED and STAT work completely when
linked into the system. Debugging is starting on the PIP
utility. There is some problem with random I/O which needs
to be fixed to complete this debugging. Bob will coordinate
with Chaki to resolve the problem. Assembler / Linker
------------------ No further work has been done on the
Alcyon assembler / linker since getting these to work on the
VAX under VMS. Work will begin this week on re-hosting this
software to run under CP/M-68K. C Runtime Library
----------------- Bill Fitler joined the project team today
as the C runtime library person. A specification for this
library now exists, and work will begin immediately. Bill
has promised a schedule by the end of the week. C Compiler
---------- Barring unforeseen problems, we will receive the
source code to the Alcyon compiler 7/12. This will be put up
on the VAX using the same interface library used to port the
assembler and linker. Documentation ------------- Ruth has
promised an outline for the Programmer's Manual by 7/8, and
also to begin writing this manual on that date. We will be
using the Motorola 68000 book plus Bill Allen's
documentation for the assembler and linker, at least for
B-testing purposes. Quality Assurance -----------------
Vincent distributed the attached assurance plan. Bob, Bill
and Chaki must coordinate with him on getting time on the
EXORmacs. I will be assuming the role of Q/A interface
person. Other Issues ------------ The following decisions
were reached by myself and Tom Rolander 7/6: The Pascal
version of CP/M-68K must be translated into C and shipped as
a product as soon as possible following the preliminary
release. This will entail a second field test. Portable
CP/M will have to wait. I will manage this conversion
project. pricing is in line with CP/M-86. From Last Week
-------------- No minutes
were distributed from last week's meeting. Here are the key
decisions that were made: portions of the code.
serialization utilities. (Serialization does not have to be
ready 7/31). work under CP/M-68k. a Programmer's Guide, a
User's Guide, and a Quick Reference. For the 7/31 shipment,
the following items have priority: Programmer's Guide. The
Alcyon documentation on the assembler and linker plus the
Motorola book on the 68000 must serve for documentation on
the assembler / linker programs. The CP/M-86 User's guide
must serve as documentation for user commands. It was also
decided that the ".COM" file equivalent for CP/M-68K would
be ".68K". Submit files would have the extension ".SUB". The
"SUBMIT " command prefix will be optional. The ability to
retrieve ALL directory entries in SEARCH functions by coding
a "?" in the drive field of the FCB under CP/M 2.2 will be
preserved under CP/M-68K.
--unquote--
Regards.
While searching information on TEX from DR, I have found a CP/M-68K internal doc. with interesting information.
It is a memo called cpm0706.nro regarding the development of CP/M-68K.
This file is in the v101 directory of cpm68k1.zip file, downloaded time ago from the Unofficial CP/M Website.
In the memo, there are two interesting things:
--quote--
The Pascal
version of CP/M-68K must be translated into C and shipped as
a product as soon as possible following the preliminary
release.
--unquote--
and
--quote--
Portable CP/M will have to wait.
--unquote--
In fact, in the website we can read:
--quote--
Reading v101/doc/ and v102a/doc/ makes interesting trivia: 1."The Pascal version of CP/M-68K..." (cpm0706.rno)
--unquote--
Then, two interesting things I believe:
- There was a CP/M written in Pascal.
- Portable CP/M (CP/M coded in C) was a DR product,
as discussed some time ago in this newsgroup.
The document in full is as follows, after formatting:
--quote--
Memo: Vincent Alia
Ruth Driscoll
Bill Fitler
Bob Herlien
Tim McCormick
Bill Tyler xc: Tom Rolander Re: Minutes of CP/M-68K
Status Meeting 07/06 From: Steve Williams
As we discussed this morning, the status of the CP/M-68K
project is as follows: BDOS ---- The BDOS is 99% coded,
lacking only the Set exception vector, program chain and
flush buffers functions. Approximately 60% of this code is
tested. Bob has committed to a working BDOS by 7/16. CCP ---
The CCP lacks BATCH processing. It is felt that this is a
desirable feature, but that the system would be usable
without it. BATCH processing is therefore a candidate for
featurectomy if need be. Bootstrap --------- No progress has
been made on a bootstrap loader for CP/M on the EXORmacs.
DDT --- DDT lacks File I/O and program load functions. It is
not usable without program load. Bill has promised program
load by 7/12. File I/O is another candidate for
featurectomy. Diskette Format Utility
----------------------- Nothing has been done about a
diskette format utility for the EXORmacs. Utilities
--------- A problem exists somewhere between XLINK and the
Motorola linker. Initialized data areas in the utilities do
not have the right values in the right places after the link
process. Chaki will attempt to use the Alcyon linker to
correct this problem. ED and STAT work completely when
linked into the system. Debugging is starting on the PIP
utility. There is some problem with random I/O which needs
to be fixed to complete this debugging. Bob will coordinate
with Chaki to resolve the problem. Assembler / Linker
------------------ No further work has been done on the
Alcyon assembler / linker since getting these to work on the
VAX under VMS. Work will begin this week on re-hosting this
software to run under CP/M-68K. C Runtime Library
----------------- Bill Fitler joined the project team today
as the C runtime library person. A specification for this
library now exists, and work will begin immediately. Bill
has promised a schedule by the end of the week. C Compiler
---------- Barring unforeseen problems, we will receive the
source code to the Alcyon compiler 7/12. This will be put up
on the VAX using the same interface library used to port the
assembler and linker. Documentation ------------- Ruth has
promised an outline for the Programmer's Manual by 7/8, and
also to begin writing this manual on that date. We will be
using the Motorola 68000 book plus Bill Allen's
documentation for the assembler and linker, at least for
B-testing purposes. Quality Assurance -----------------
Vincent distributed the attached assurance plan. Bob, Bill
and Chaki must coordinate with him on getting time on the
EXORmacs. I will be assuming the role of Q/A interface
person. Other Issues ------------ The following decisions
were reached by myself and Tom Rolander 7/6: The Pascal
version of CP/M-68K must be translated into C and shipped as
a product as soon as possible following the preliminary
release. This will entail a second field test. Portable
CP/M will have to wait. I will manage this conversion
project. pricing is in line with CP/M-86. From Last Week
-------------- No minutes
were distributed from last week's meeting. Here are the key
decisions that were made: portions of the code.
serialization utilities. (Serialization does not have to be
ready 7/31). work under CP/M-68k. a Programmer's Guide, a
User's Guide, and a Quick Reference. For the 7/31 shipment,
the following items have priority: Programmer's Guide. The
Alcyon documentation on the assembler and linker plus the
Motorola book on the 68000 must serve for documentation on
the assembler / linker programs. The CP/M-86 User's guide
must serve as documentation for user commands. It was also
decided that the ".COM" file equivalent for CP/M-68K would
be ".68K". Submit files would have the extension ".SUB". The
"SUBMIT " command prefix will be optional. The ability to
retrieve ALL directory entries in SEARCH functions by coding
a "?" in the drive field of the FCB under CP/M 2.2 will be
preserved under CP/M-68K.
--unquote--
Regards.
Floppy Software
Sep 6, 2015, 1:43:08 PM9/6/15
to
El miércoles, 11 de marzo de 2015, 18:48:53 (UTC+1), Floppy Software escribió:
> Hi all!
>
> While searching information on TEX from DR, I have found a CP/M-68K internal doc. with interesting information.
>
> It is a memo called cpm0706.nro regarding the development of CP/M-68K.
>
> This file is in the v101 directory of cpm68k1.zip file, downloaded time ago from the Unofficial CP/M Website.
>
> In the memo, there are two interesting things:
>
> --quote--
> The Pascal
> version of CP/M-68K must be translated into C and shipped as
> a product as soon as possible following the preliminary
> release.
> --unquote--
Well, while surfing the net searching for a CP/M thing, I found the following:
> Hi all!
>
> While searching information on TEX from DR, I have found a CP/M-68K internal doc. with interesting information.
>
> It is a memo called cpm0706.nro regarding the development of CP/M-68K.
>
> This file is in the v101 directory of cpm68k1.zip file, downloaded time ago from the Unofficial CP/M Website.
>
> In the memo, there are two interesting things:
>
> --quote--
> The Pascal
> version of CP/M-68K must be translated into C and shipped as
> a product as soon as possible following the preliminary
> release.
> --unquote--
http://www.dreamtimestudioz.com/MichaelGLehman-CV.html
--quote--
From: 1981 Digital Research, Inc. (DRI)
To: 1984 Pacific Grove, CA
Title: Director of Research and Development/VP Languages
...
* Wrote a version of CP/M in Pascal/MT+68k for the Motorola 68000 processor.
--unquote--
Then, it's seems confirmed: there was a CP/M-68K written in Pascal!
Dennis Boone
Sep 6, 2015, 1:53:46 PM9/6/15
to
> http://www.dreamtimestudioz.com/MichaelGLehman-CV.html
De
> From: 1981 Digital Research, Inc. (DRI)
> To: 1984 Pacific Grove, CA
> To: 1984 Pacific Grove, CA
> * Wrote a version of CP/M in Pascal/MT+68k for the Motorola 68000 processor.
Write to the guy and ask if he still has a copy?
De
Floppy Software
Sep 7, 2015, 5:54:30 AM9/7/15
to
By the way, I found another reference:
http://blogs.msdn.com/b/mglehman/archive/2004/08/23/218971.aspx
--quote--
Michael Lehman 23 Aug 2004 10:40 AM
...
Pascal/MT+ was used to create many successful products as well as the first version of CP/M 68K (in 1982).
--unquote--
Maybe it has been discovered another forgotten CP/M history page!
retrogear
Sep 7, 2015, 1:20:17 PM9/7/15
to
So where would it have initially been cross-compiled? Evidently the Alycon Assembler was being developed on a Vax running VMS
Larry G
Larry G
Floppy Software
Sep 11, 2015, 4:04:02 AM9/11/15
to
El lunes, 7 de septiembre de 2015, 19:20:17 (UTC+2), retrogear escribió:
> So where would it have initially been cross-compiled? Evidently the Alycon Assembler was being developed on a Vax running VMS
Mr. Lehman replied to me that he did write a prototype for CP/M-68K in early 1982.
> So where would it have initially been cross-compiled? Evidently the Alycon Assembler was being developed on a Vax running VMS
It was written in Pascal/MT+68K which was also a prototype at that time.
He wrote the file system with the CCP commands DIR, ERA, REN, TYPE, etc.
Later, there was a debate about if they would go to a complete Pascal version, or to a new in the C language.
We already know what happened (the DR memorándum).
Unfortunately, it seems that sources and binaries are lost.
Mr. Lehman is the author of Pascal/MT, Digital Research C, and a lof more.
0 new messages