fredag den 11. marts 2022 kl. 08.18.19 UTC+1 skrev Randy McLaughlin:
> Please consider sending complete copies of the patched code to Gaby:
>
> http://www.cpm.z80.de/
>
> That is where it truly belongs.
>
>
> Randy

I Agree - I wrote a mail to Gaby.

Regards,
MogensB

fredag den 11. marts 2022 kl. 18.20.32 UTC+1 skrev MogensB:
> fredag den 11. marts 2022 kl. 08.18.19 UTC+1 skrev Randy McLaughlin:
> > Please consider sending complete copies of the patched code to Gaby:
> >
> > http://www.cpm.z80.de/
> >
> > That is where it truly belongs.
> >
> >
> > Randy
> I Agree - I wrote a mail to Gaby.
>
> Regards,
> MogensB

I am happy to tell you that I was able to contact the founder of Silicon Valley Software, Inc. (which dissolved back in 1988) who is also the author of the compilers. He kindly granted permission to freely use and distribute the SVS Compilers for CP/M-68K at no cost, only request is that we maintain the original copyright notice in the software. Gaby is informed, and is about to make the SVS FORTRAN-77 compiler available on the website.
I gave credits to you guys in this forum for your help getting the binary files patched back into working condition. The original binaries for the compilers were unfortunately lost, also with the founder of Silicon Valley Software. He told me, that the SVS Pascal compiler was the tool used for developing the SVS FORTRAN compiler, so it would be great if that one could be fixed as well ;-) - and for Gaby to make available this compiler too!

Regards,
MogensB

søndag den 13. marts 2022 kl. 12.41.16 UTC+1 skrev MogensB:
> fredag den 11. marts 2022 kl. 18.20.32 UTC+1 skrev MogensB:
> > fredag den 11. marts 2022 kl. 08.18.19 UTC+1 skrev Randy McLaughlin:
> > > Please consider sending complete copies of the patched code to Gaby:
> > >
> > > http://www.cpm.z80.de/
> > >
> > > That is where it truly belongs.
> > >
> > >
> > > Randy
> > I Agree - I wrote a mail to Gaby.
> >
> > Regards,
> > MogensB
> I am happy to tell you that I was able to contact the founder of Silicon Valley Software, Inc. (which dissolved back in 1988) who is also the author of the compilers. He kindly granted permission to freely use and distribute the SVS Compilers for CP/M-68K at no cost, only request is that we maintain the original copyright notice in the software. Gaby is informed, and is about to make the SVS FORTRAN-77 compiler available on the website.
> I gave credits to you guys in this forum for your help getting the binary files patched back into working condition. The original binaries for the compilers were unfortunately lost, also with the founder of Silicon Valley Software. He told me, that the SVS Pascal compiler was the tool used for developing the SVS FORTRAN compiler, so it would be great if that one could be fixed as well ;-) - and for Gaby to make available this compiler too!
>
> Regards,
> MogensB

The FORTRAN compiler binaries are now available on http://www.cpm.z80.de/binary.html - just look for "SVS FORTRAN".
@Martin and @David - you got credited for your effort to patch the corrupt binaries - I hope you are OK with being mentioned in Gaby's website :-) if not, just drop a line to Gaby about it.

Regards,
MogensB

On 3/13/22 9:57 AM, MogensB wrote:
> @Martin and @David - you got credited for your effort to patch the corrupt binaries - I hope you are OK with being mentioned in Gaby's website :-) if not, just drop a line to Gaby about it.
>

I know that memory is supposed to get a bit flaky with age but I do not
recall doing anything to patch those binaries. Other than suggesting
that it might be possible.

--
http://davesrocketworks.com
David Schultz

søndag den 13. marts 2022 kl. 17.49.09 UTC+1 skrev David Schultz:
> On 3/13/22 9:57 AM, MogensB wrote:
> > @Martin and @David - you got credited for your effort to patch the corrupt binaries - I hope you are OK with being mentioned in Gaby's website :-) if not, just drop a line to Gaby about it.
> >
> I know that memory is supposed to get a bit flaky with age but I do not
> recall doing anything to patch those binaries. Other than suggesting
> that it might be possible.
> --
> http://davesrocketworks.com
> David Schultz

Hi David - I am sorry if I misunderstood your comments in this thread, I was just thinking you were the one correctly identifying the root cause of the problem with the files - the EOF markers being deleted from the files? This was why I thought I would mention your name to Gaby. Please let me know, I can of course ask Gaby to remove your name from the site, if you don't feel it belongs there! I just wanted to make it clear that I was not the one capable of fixing the files :-)

Best Regards,
MogensB

Am 03/13/2022 12:41 PM, MogensB schrieb:
> fredag den 11. marts 2022 kl. 18.20.32 UTC+1 skrev MogensB:
>> fredag den 11. marts 2022 kl. 08.18.19 UTC+1 skrev Randy McLaughlin:
>>> Please consider sending complete copies of the patched code to Gaby:
>>>
>>> http://www.cpm.z80.de/
>>>
>>> That is where it truly belongs.
>>>
>>>
>>> Randy
>> I Agree - I wrote a mail to Gaby.
>>
>> Regards,
>> MogensB
>
> I am happy to tell you that I was able to contact the founder of Silicon Valley Software, Inc. (which dissolved back in 1988) who is also the author of the compilers. He kindly granted permission to freely use and distribute the SVS Compilers for CP/M-68K at no cost, only request is that we maintain the original copyright notice in the software. Gaby is informed, and is about to make the SVS FORTRAN-77 compiler available on the website.
> I gave credits to you guys in this forum for your help getting the binary files patched back into working condition. The original binaries for the compilers were unfortunately lost, also with the founder of Silicon Valley Software. He told me, that the SVS Pascal compiler was the tool used for developing the SVS FORTRAN compiler, so it would be great if that one could be fixed as well ;-) - and for Gaby to make available this compiler too!
>
> Regards,
> MogensB
>

This are *fantastic* news!

And just in time, I finished the repair of SVS-Pascal :-D

I used the files in "ERG_68K_Pascal",
the same explanations as for the SVS-Fortran patches:

1) Convert all files into an ascii byte stream
2) Apply the following patch
3) Convert all files back to binary

==== 8< ====
--- CODE.REL.xxd
+++ CODE.REL.xxd
@@ -10879,2 +10879,3 @@
60
+1a
20
@@ -39934,2 +39935,3 @@
ff
+1a
66
@@ -66941,2 +66943,3 @@
00
+1a
00
--- PASCAL.REL.xxd
+++ PASCAL.REL.xxd
@@ -4863,2 +4863,3 @@
60
+1a
42
@@ -7038,2 +7039,3 @@
60
+1a
2f
@@ -42749,2 +42751,3 @@
00
+1a
70
@@ -68988,2 +68991,3 @@
00
+1a
ff
@@ -88955,2 +88959,3 @@
66
+1a
2f
@@ -94970,2 +94975,3 @@
67
+1a
4a
@@ -96633,2 +96639,3 @@
01
+1a
4a
--- FTNLIB.OBJ.xxd
+++ FTNLIB.OBJ.xxd
@@ -50431,2 +50431,3 @@
00
+1a
b0
@@ -83454,2 +83455,3 @@
00
+1a
20
--- PASLIB.OBJ.xxd
+++ PASLIB.OBJ.xxd
@@ -11391,2 +11391,3 @@
6e
+1a
48
@@ -11902,2 +11903,3 @@
00
+1a
4e
@@ -17661,2 +17663,3 @@
08
+1a
00
--- ULINKER.REL.xxd
+++ ULINKER.REL.xxd
@@ -6143,2 +6143,3 @@
60
+1a
41
@@ -13822,2 +13823,3 @@
ff
+1a
2a
==== 8< ====

Have fun !!!

Am 03/13/2022 05:59 PM, MogensB schrieb:
> søndag den 13. marts 2022 kl. 17.49.09 UTC+1 skrev David Schultz:
>> On 3/13/22 9:57 AM, MogensB wrote:
>>> @Martin and @David - you got credited for your effort to patch the corrupt binaries - I hope you are OK with being mentioned in Gaby's website :-) if not, just drop a line to Gaby about it.
>>>
>> I know that memory is supposed to get a bit flaky with age but I do not
>> recall doing anything to patch those binaries. Other than suggesting
>> that it might be possible.
>> --
>> http://davesrocketworks.com
>> David Schultz
>
> Hi David - I am sorry if I misunderstood your comments in this thread, I was just thinking you were the one correctly identifying the root cause of the problem with the files - the EOF markers being deleted from the files? This was why I thought I would mention your name to Gaby. Please let me know, I can of course ask Gaby to remove your name from the site, if you don't feel it belongs there! I just wanted to make it clear that I was not the one capable of fixing the files :-)
>
> Best Regards,
> MogensB
>

No offence please, this is my view of the things,
he has not much to do with the restoration

*BUT*

Without his emulator, I never had finished this project !!!

I also have to thank *Randy McLaughlin* to make this possible,
because of his efforts to not only archive these files, but many, many more!

And finally the founder of Silicon Valley Software, Inc., to make his
compiler available to us.

And please forgive me, if I have forgotten onyone else :-)

Martin

søndag den 13. marts 2022 kl. 18.56.02 UTC+1 skrev Martin:
> Am 03/13/2022 05:59 PM, MogensB schrieb:
> > søndag den 13. marts 2022 kl. 17.49.09 UTC+1 skrev David Schultz:
> >> On 3/13/22 9:57 AM, MogensB wrote:
> >>> @Martin and @David - you got credited for your effort to patch the corrupt binaries - I hope you are OK with being mentioned in Gaby's website :-) if not, just drop a line to Gaby about it.
> >>>
> >> I know that memory is supposed to get a bit flaky with age but I do not
> >> recall doing anything to patch those binaries. Other than suggesting
> >> that it might be possible.
> >> --
> >> http://davesrocketworks.com
> >> David Schultz
> >
> > Hi David - I am sorry if I misunderstood your comments in this thread, I was just thinking you were the one correctly identifying the root cause of the problem with the files - the EOF markers being deleted from the files? This was why I thought I would mention your name to Gaby. Please let me know, I can of course ask Gaby to remove your name from the site, if you don't feel it belongs there! I just wanted to make it clear that I was not the one capable of fixing the files :-)
> >
> > Best Regards,
> > MogensB
> >
> No offence please, this is my view of the things,
> he has not much to do with the restoration
>
> *BUT*
>
> Without his emulator, I never had finished this project !!!
>
> I also have to thank *Randy McLaughlin* to make this possible,
> because of his efforts to not only archive these files, but many, many more!
>
> And finally the founder of Silicon Valley Software, Inc., to make his
> compiler available to us.
>
> And please forgive me, if I have forgotten onyone else :-)
>
> Martin

Once again, very well done, Martin! Using your patches, I can also confirm that the SVS Pascal compiler seems to be running smoothly in my 68k-mbc CP/M-68k system :-)

I am very happy that both compilers are in working condition. I will arrange that Gaby receives the patched set of files for the Pascal compiler too, and offer those along with the FORTRAN compiler.

Thx to *everyone* helping to make these important contribution to the CP/M software collections. It is amazing to see how I started with posting a question in search of a FORTRAN compiler, and now we have two almost "lost" significant compilers working on CP/M-68K.

/MogensB

On 3/13/22 5:19 PM, MogensB wrote:
> Thx to *everyone* helping to make these important contribution to the CP/M software collections. It is amazing to see how I started with posting a question in search of a FORTRAN compiler, and now we have two almost "lost" significant compilers working on CP/M-68K.
>
> /MogensB
There is another, kind of. The sources for the PLM compiler hosted on a
VAX were made available some time ago. In FORTRAN. I tried to get it to
compile using the GCC version of FORTRAN but didn't get very far.

Perhaps it would work better with the native FORTRAN? If so, then it
would be possible to compile the few CP/M-68K tools (ed, etc.) that are
in PLM.

--
http://davesrocketworks.com
David Schultz

David Schultz schrieb am Sonntag, 13. März 2022 um 23:35:37 UTC+1:
> There is another, kind of. The sources for the PLM compiler hosted on a
> VAX were made available some time ago. In FORTRAN. I tried to get it to
> compile using the GCC version of FORTRAN but didn't get very far.

Sources for the PL/M compiler that build with GNU FORTRAN are available
in the z80pack repository:
https://www.autometer.de/unix4fun/z80pack/#download

On Sunday, 13 March 2022 at 22:35:37 UTC, David Schultz wrote:
> On 3/13/22 5:19 PM, MogensB wrote:
> > Thx to *everyone* helping to make these important contribution to the CP/M software collections. It is amazing to see how I started with posting a question in search of a FORTRAN compiler, and now we have two almost "lost" significant compilers working on CP/M-68K.
> >
> > /MogensB
> There is another, kind of. The sources for the PLM compiler hosted on a
> VAX were made available some time ago. In FORTRAN. I tried to get it to
> compile using the GCC version of FORTRAN but didn't get very far.
>
> Perhaps it would work better with the native FORTRAN? If so, then it
> would be possible to compile the few CP/M-68K tools (ed, etc.) that are
> in PLM.
> --
> http://davesrocketworks.com
> David Schultz
David
I was not aware of a PL/M 68k, where can it be found?
On the internet you can find FORTRAN source for a PL/M 80 cross compiler, which is relatively clean FORTRAN 66 and does work, however you need the later version as the original V2 generates incorrect code. I have also done a conversion to C with some clean-up to remove most of the gotos. It is available on my GitHub site.
Note the version of PL/M supported lacks features of the later resident versions and it is not linkable with other code.

There is also FORTRAN source for PL/M VAX compiler, which I have not managed to build as it appears to use some VAX specific extensions. Looking at the source it seems to support additional key words compared to other PL/M variants.

Mark

ogd...@gmail.com schrieb am Montag, 14. März 2022 um 12:01:47 UTC+1:
> On the internet you can find FORTRAN source for a PL/M 80 cross compiler, which is relatively clean
> FORTRAN 66 and does work, however you need the later version as the original V2 generates incorrect code.

We have versions 2 and 4 of the cross compiler.

mandag den 14. marts 2022 kl. 16.41.01 UTC+1 skrev Udo Munk:
> ogd...@gmail.com schrieb am Montag, 14. März 2022 um 12:01:47 UTC+1:
> > On the internet you can find FORTRAN source for a PL/M 80 cross compiler, which is relatively clean
> > FORTRAN 66 and does work, however you need the later version as the original V2 generates incorrect code.
> We have versions 2 and 4 of the cross compiler.

The reconstructed SVS Pascal compiler for CP/M-68K has been posted online on Gaby's website, we got the permission to publish the compiler on the same terms as the SVS FORTRAN-77 compiler (free to use and distribute at no cost, provided the original copyright notice is maintained).

/MogensB

On 3/14/22 6:01 AM, ogd...@gmail.com wrote:
> I was not aware of a PL/M 68k, where can it be found?

It has been several years so I don't recall. Digging out the remains of
what I tried...

After looking at the gencode.for file it appears to target an abstract
processor. The comments say it puts out MACRO assembly code. The
mnemonic table starts:

C BYTE WORD INTEGER POINTER REAL LONG DOUBLE QUAD

DATA MNEM/
#'ADDB2','ADDW2','ADDW2','ADDL2','ADDF2','ADDL2','ADDD2','---- ',

So even if that were made to work, a suitable package of macros would be
required.

According to the build instructions for ed in the CP/M-68K sources, the
VAX would put out a binary (I think) that was massaged into a .68K
format on an ALTOS using a program called reconv.com.

A hell of a way to run things. Perhaps best forgotten. :-)

--
http://davesrocketworks.com
David Schultz