Author Topic: Amiga - SAS/C Compiler v6.50  (Read 7303 times)

Offline peo

  • Newbie
  • *
  • Posts: 15
    • Email
Amiga - SAS/C Compiler v6.50
« on: December 26, 2017, 01:39:47 AM »

Anyone have their original disks of SAS/C 6.50 ? I've just backed up my set of original floppies, and compared the checksums I got against TOSEC..

(my disks)
SASC_6.50_Disk_1.adf, md5: 83cfb3686b2b83f715f4e930088adbc5
SASC_6.50_Disk_2.adf, md5: 895206db5bce424eebe77589db4ba313
SASC_6.50_Disk_3.adf, md5: d82e73dc04879437f1d0252c2fda7650
SASC_6.50_Disk_4.adf, md5: 2d43eda18bb37cdbfd7fa7f055cd7bc3
SASC_6.50_Disk_5.adf, md5: c60e15b7787868f82a907d16837e8e7b
SASC_6.50_Disk_6.adf, md5: 3ce814e273aac17c830b5c9e9e13f289

Only the first disk matches one of the checksums in "Commodore Amiga - Applications - [ADF] (TOSEC-v2017-10-15_CM).dat", and as the "altered" image:

SAS C Compiler v6.50 (1992)(SAS Institute)(Disk 1 of 6)[a][HD].adf
md5="83cfb3686b2b83f715f4e930088adbc5"
SAS C Compiler v6.50 (1992)(SAS Institute)(Disk 1 of 6)[HD].adf
md5="8571212608c489f32eecaed406c2f265
SAS C Compiler v6.50 (1992)(SAS Institute)(Disk 2 of 6)[HD].adf
md5="aa11fa3a393776854705f34b589bfd10"
SAS C Compiler v6.50 (1992)(SAS Institute)(Disk 3 of 6)[HD].adf
md5="d6130a83ff838340343016b8ad207219"
SAS C Compiler v6.50 (1992)(SAS Institute)(Disk 4 of 6)[HD].adf
md5="0efb203094d3bcb8427d85a84c6337f4"
SAS C Compiler v6.50 (1992)(SAS Institute)(Disk 5 of 6)[HD].adf
md5="3fc3ea729db8ed97af56183a73b856ee"
SAS C Compiler v6.50 (1992)(SAS Institute)(Disk 6 of 6)[HD].adf
md5="04d13e5c1bdf89cb22771a0d91a74730"


Of the 18 (unaltered) SAS/C 6.5.1 patch floppies I had, 17 gave of them gave the same checksum (this disk does not exist in TOSEC)
bd088aac3a23304b95d8eba3294bb768  SASC_6.51_Patch-d1.adf
bd088aac3a23304b95d8eba3294bb768  SASC_6.51_Patch-d10.adf
bd088aac3a23304b95d8eba3294bb768  SASC_6.51_Patch-d11.adf
bd088aac3a23304b95d8eba3294bb768  SASC_6.51_Patch-d12.adf
bd088aac3a23304b95d8eba3294bb768  SASC_6.51_Patch-d13.adf
bd088aac3a23304b95d8eba3294bb768  SASC_6.51_Patch-d14.adf
bd088aac3a23304b95d8eba3294bb768  SASC_6.51_Patch-d15.adf
bd088aac3a23304b95d8eba3294bb768  SASC_6.51_Patch-d16.adf
bd088aac3a23304b95d8eba3294bb768  SASC_6.51_Patch-d17.adf
bd088aac3a23304b95d8eba3294bb768  SASC_6.51_Patch-d2.adf
bd088aac3a23304b95d8eba3294bb768  SASC_6.51_Patch-d3.adf
bd088aac3a23304b95d8eba3294bb768  SASC_6.51_Patch-d4.adf
bd088aac3a23304b95d8eba3294bb768  SASC_6.51_Patch-d5.adf
9db7091eaa4b218da92a5d101baa752d  SASC_6.51_Patch-d6.bad.adf
bd088aac3a23304b95d8eba3294bb768  SASC_6.51_Patch-d7.adf
bd088aac3a23304b95d8eba3294bb768  SASC_6.51_Patch-d8.adf
bd088aac3a23304b95d8eba3294bb768  SASC_6.51_Patch-d9.adf
bd088aac3a23304b95d8eba3294bb768  SASC_6.51_Patch.adf

In the unlikely event that the checksums in TOSEC are from unaltered original disks, my first disk seems to have been changed exactly in the same way that the one that is in the database..

.. or may there have been different set of original disks sent out at some point ? I ordered 25 of the SAS/C packages when they had a big sale-out in 1997 or 1998, and the order was placed directly with Lattice/SAS.



Offline tomse

  • Global Moderator
  • Full Member
  • *****
  • Posts: 160
Re: Amiga - SAS/C Compiler v6.50
« Reply #1 on: December 26, 2017, 08:48:35 AM »
I think you mistake the [a] tag, it's an alternate version not altered

you can read more about the naming convention here:
https://www.tosecdev.org/tosec-naming-convention

I'm in doubt if there is a question in your post?
Do you want to contribute your dumps that aren't in tosec?

other than that, can you make scans of your originals ?
a guide on the format http://www.retro-commodore.eu/the-rules-of-scanning-for-preservation/
« Last Edit: December 26, 2017, 10:07:59 AM by tomse »

Offline peo

  • Newbie
  • *
  • Posts: 15
    • Email
Re: Amiga - SAS/C Compiler v6.50
« Reply #2 on: December 26, 2017, 10:50:21 AM »
Ah, my mistake about the [a] (have read that naming convention guide a long time ago, but didn't recheck). So there is different set of disks that were sent out at some point, and the only contributed from that set is the first disk..
This SAS/C 6.50 was supplied with the full manual (but no binders, those unavailable-in-Europe 3-ring US-binders), and the plastic sleeves for the floppies + that extra 6.5.1 update I mentioned.

Is scanning the originals a new part of TOSEC ? I will of course scan and submit the labels and manuals if it will be useful for adding to TOSEC-PIX or an entirely new project.

I will re-read the info about contributing to TOSEC, since I also noticed I had a couple of other disks not there (ScanQuix, Amiga Computing coverdisks 108 and up and a few other missing). I guess my first step is to use RomVault or similar to sort a copy of my saved floppy images.

While half-off-topic, is there a manager for the Unix (Ubuntu, Buffalo, FreeBSD, QNAP), command-line environment ? Windos file handling is sooo slow, even with SSD.. just "moving" a file needs windows to "calculate" what time it will take before it tries to move it...

Sorry for all stupid questions, I'm new on the forum, definitely not new on Amiga (programming since 1989 up to 2005) or data rescue/recovery/preservation.

Offline tomse

  • Global Moderator
  • Full Member
  • *****
  • Posts: 160
Re: Amiga - SAS/C Compiler v6.50
« Reply #3 on: December 26, 2017, 11:18:14 AM »
Ah, my mistake about the [a] (have read that naming convention guide a long time ago, but didn't recheck). So there is different set of disks that were sent out at some point, and the only contributed from that set is the first disk..
This SAS/C 6.50 was supplied with the full manual (but no binders, those unavailable-in-Europe 3-ring US-binders), and the plastic sleeves for the floppies + that extra 6.5.1 update I mentioned.
My guess is that there has been 2 releases (without having checked the actual disk dumps), maybe just a timestamp has changed, I can't say.
It appears that the SAS/C 6.50 manual is online  (though imo in a low quality of 200dpi)
https://archive.org/details/sasc-65-lib
https://archive.org/details/sasc-650-vol2
If you have a document scanner, scans of the manual in 600dpi would be much appreciated.

Is scanning the originals a new part of TOSEC ? I will of course scan and submit the labels and manuals if it will be useful for adding to TOSEC-PIX or an entirely new project.
yes and no.. as you mention this will go to PIX, not directly to TOSEC. PIX is a heavy part, same goes with ISO hence they're separated :-)
If you look at the site mentioned earlier, you'll see loads of scans already (not yet part of TOSEC but they'll be in the future).
Basically anything that can be put on a scanner should be scanned, backside of disks excluded ofc if there is no label part there.

I will re-read the info about contributing to TOSEC, since I also noticed I had a couple of other disks not there (ScanQuix, Amiga Computing coverdisks 108 and up and a few other missing). I guess my first step is to use RomVault or similar to sort a copy of my saved floppy images.
That sounds great, we're always looking for more contributions, but there is no guarantee that they'll get added for the next release though, backlog is huge :-)
Personally I use RomVault, though it could be improved with better thread handling it's the best tool imo.


While half-off-topic, is there a manager for the Unix (Ubuntu, Buffalo, FreeBSD, QNAP), command-line environment ? Windos file handling is sooo slow, even with SSD.. just "moving" a file needs windows to "calculate" what time it will take before it tries to move it...
I'm not familiar with any <> Win apps that are similar to RomVault -is that the manager you're asking for?-, but for file navigation midnight commander does the trick (package name "mc"), Total Commander for windows also skip those "calculations" for deleting, moving etc, and you can queue up other file operations.
TC also have plugins to read ADF and D64 files

Sorry for all stupid questions, I'm new on the forum, definitely not new on Amiga (programming since 1989 up to 2005) or data rescue/recovery/preservation.
They are not stupid, but quite valid questions, no need for appologizing :-)

We don't have a proper contribution platform
but for Amiga related uploads, Mai and Crashdisk are using eab.abime.org forum/the zone..
otherwise you can send them using wetransfer.com
if you decide the later (specially for scans) I can PM you my email, and I'll make sure they are distributed to the right people

Offline peo

  • Newbie
  • *
  • Posts: 15
    • Email
Re: Amiga - SAS/C Compiler v6.50
« Reply #4 on: December 26, 2017, 12:46:09 PM »
It appears that the SAS/C 6.50 manual is online  (though imo in a low quality of 200dpi)
https://archive.org/details/sasc-65-lib
https://archive.org/details/sasc-650-vol2
If you have a document scanner, scans of the manual in 600dpi would be much appreciated.
I have a scanner with document feeder at work, but as SAS/Lattice printed the manual on toilet paper, pages might get stuck somewhere.. 600dpi is no problem with that scanner, I've scanned a few (50-ish) (swedish) Amiga magazines manually on that one.

Is scanning the originals a new part of TOSEC ? I will of course scan and submit the labels and manuals if it will be useful for adding to TOSEC-PIX or an entirely new project.
yes and no.. as you mention this will go to PIX, not directly to TOSEC. PIX is a heavy part, same goes with ISO hence they're separated :-)
If you look at the site mentioned earlier, you'll see loads of scans already (not yet part of TOSEC but they'll be in the future).
Basically anything that can be put on a scanner should be scanned, backside of disks excluded ofc if there is no label part there.
Great that ISO and PIX is not forgotten/dead..  Haven't been updated in a long time..
Recognized quite a few of the hardware and software manuals on that site.

I will re-read the info about contributing to TOSEC, since I also noticed I had a couple of other disks not there (ScanQuix, Amiga Computing coverdisks 108 and up and a few other missing). I guess my first step is to use RomVault or similar to sort a copy of my saved floppy images.
That sounds great, we're always looking for more contributions, but there is no guarantee that they'll get added for the next release though, backlog is huge :-)
Personally I use RomVault, though it could be improved with better thread handling it's the best tool imo.


While half-off-topic, is there a manager for the Unix (Ubuntu, Buffalo, FreeBSD, QNAP), command-line environment ? Windos file handling is sooo slow, even with SSD.. just "moving" a file needs windows to "calculate" what time it will take before it tries to move it...
I'm not familiar with any <> Win apps that are similar to RomVault -is that the manager you're asking for?-, but for file navigation midnight commander does the trick (package name "mc"), Total Commander for windows also skip those "calculations" for deleting, moving etc, and you can queue up other file operations.
TC also have plugins to read ADF and D64 files
Midnight Commander will probably do no good in this case, just for those who are afraid of typing commands :) (and messy for those not afraid). I will probably end up writing something myself (PHP and MySQL), my primary need is to sort and rename files so they match the current names in TOSEC.

Offline peo

  • Newbie
  • *
  • Posts: 15
    • Email
Re: Amiga - SAS/C Compiler v6.50
« Reply #5 on: December 26, 2017, 09:14:20 PM »
Getting somewhere :)

Offline tomse

  • Global Moderator
  • Full Member
  • *****
  • Posts: 160
Re: Amiga - SAS/C Compiler v6.50
« Reply #6 on: December 27, 2017, 09:54:50 PM »
php / MySQL is an easy way of doing it, could also be a very useful tool for others if you end up releasing it to the public :-)

it actually could be useful on our website as well.. for single file lookups, ISO part has been on my todo for ages.. but alas, more time wanted :-)

Offline peo

  • Newbie
  • *
  • Posts: 15
    • Email
Re: Amiga - SAS/C Compiler v6.50
« Reply #7 on: April 12, 2018, 02:21:41 PM »
My "work in progress" (or actually "work in coma" for a while) checker is fully working, probably missing some of the not-at-all planned functionality.
As for the tool itself it's actually two parts: one that parses the dat files and populates the database, and the other, lot more complex, that recursively checks for matching files and moves them into the correct folder as parsed from the info in the dats.

I will probably make an attempt on adding block-level md5 to my database, and build some (php) tool to check partial matching files. Will probably only be a valid check for ADFs (901120 bytes, 1760 blocks to compare)

Offline idrougge

  • Newbie
  • *
  • Posts: 25
Re: Amiga - SAS/C Compiler v6.50
« Reply #8 on: July 27, 2018, 08:26:07 PM »
Peo, be aware that the Amiga part of TOSEC is basically unchecked, and is pieced together from private ADF collections. What is marked as [a] right now may in fact be a [!], but an altered or cracked version was added first.

Offline rhialto

  • Newbie
  • *
  • Posts: 3
    • Email
Re: Amiga - SAS/C Compiler v6.50
« Reply #9 on: May 08, 2020, 04:29:27 PM »
There is also a 6.55 patch for SAS/C, it seems. But I don't have it as an ADF, just as a LHA file of the contents. How to contribute that?

-rw-r--r--  1    901120 Oct 19  2005 Sas-C-6.0-Docs.adf
-rw-r--r--  1    436162 Oct 19  2005 Sas-C-6.0-Docs.lha
-rw-r--r--  1   1067535 Mar 23  1995 Sc655pch.lha
-rw-r--r--  1    468722 Jan 25  1994 sc651pch.lha


Edited to add: it is well possible that the last few patches were originally distributed via BBSes as .lha files. So this may even be the original file.
« Last Edit: May 08, 2020, 07:31:27 PM by rhialto »