This page is a wiki. Please login or create an account to begin editing.

Checksum 1.3

Your rating: None Average: 5 (11 votes)
Year released:
[www].se [ftp].se [mirror].us [mirror].de
Checksum_0.sit (272.39 KB)
MD5: e63a76b937006f44a26ec2a7042f4ef0
For System 6.x - Mac OS 9
[www].se [ftp].se [mirror].us [mirror].de
This app works with: SheepShaver, Basilisk II, Mini vMac

Here is Checksum 1.3 - a utility allowing you to check the MD5sum of downloaded files via a Classic Mac.

Any Mac that can run a Mac OS from version 6 through to 9.2.2 that is!

MD5 checksum & file name: e63a76b937006f44a26ec2a7042f4ef0 *Checksum_0_0.sit

Hint: On your first time use of Checksum 1.3 to match an MD5 Checksum: Under Options menu, uncheck everything except for RSA MD5 and Data fork (see image 3 of 4 this page) then go File menu Open and navigate to the location of the file you want to check, select and [OK] to run your checksum.

Checksum 1.3 will remember your last used settings. Supports drag and drop (on Macs that support "Macintosh Drag & Drop") and can do batch checksumming of folder contents.

Free for personal and educational use - Enjoy.

Architecture: 68k

Runs on Mac Plus through to G4, also Mini vMac, Basilisk II and SheepShaver.

If "drag & drop" does not appear to work for you with Checksum 1.3, you should try rebuilding your desktop database files, i.e; Start up or Restart your Mac with the "Option" & "Command" keys held down until the Mac boots up and presents you with a dialog window asking if you wish to "Rebuild the Desktop" of your hard drive[s], click [OK]. You should be able to drag files onto Checksum's icon to automatically launch and obtain a checksum after doing this.


MikeTomTom's picture
by MikeTomTom - 2020, May 11 - 7:53am

Sorry SkyCapt, but for an original app that was designed to run under Systems 6 & 7 your fix wasn't a fix.

That Checksum 1.3 also works in OS 8 & 9 is great, but it's of no use in OS X and besides there are better tools for checksumming already built-in with OS X.

Discarding the original icon was not a good thing to do in OS 6 & 7 apps as the OS 9 type icons are only backwards compatible with Mac OS 8.5 and newer.

I suggest that if anyone is sharing file storage between OS X and 9 and wants to have this app included on that storage, that they place it in a Disk Copy 6 image file for safe keeping and easy access (as that won't upset unmounting media in OS X).

SkyCapt's picture
by SkyCapt - 2020, January 30 - 11:38pm

I fixed it for me, and uploaded a repaired version. This was killing me, it might also been making my archive images warn about damaging my system, I checked: the repaired app mounts and unmounts clean. I found I've collected other things that make my archive images warn of damage, and found a way around that too, by creating folder-based images rather than device-based images.

How it was repaired: made an empty file (in Terminal "cat > myfile" then ctrl-z) assigned app attributes to it & created an empty resource fork all by opening it with ResEdit 213, then I copied and pasted the resources from old file to new file. The Checksum program has zero datafork. I discarded the low res pre-OS9 icon info, hope that's no trouble for anybody.

SkyCapt's picture
by SkyCapt - 2020, January 15 - 6:49am

Looking in OS923's doc for his md5 applet, it gives a link to the algorithm. This can still be newly programmed as a standalone and in a low level language to make it fast, hopefully make it for files > 2GB and FAT binary.

Jatoba's picture
by Jatoba - 2020, January 15 - 4:28am

"With perfection" only for what I need it to do, that's the keyword. So far, I have only used it to compare some downloads and check some key files. I don't mean the app is perfect as a whole. That issue you are having in OS X just from its mere existence is indeed very strange. I'll put it on my OS X install and see if I have the same issues you mentioned.

About OS923's resolution, the dev mentioned he patched it later so people can use lower resolutions, too. It has to be some later version (which I don't know if it's uploaded here). There's a mirror of his old site for it here, if you wanna take a look. There are also OS923 and OS93 threads that he made in MacOS9Lives, with his latest updates on everything.

Hmm, too bad, but not surprising, that things didn't work out in a more modular way. When I feel courageous enough, I'll poke at it wholly, and see if there's any hidden candy. Smile

MikeTomTom's picture
by MikeTomTom - 2020, January 15 - 3:56am

@SkyCapt: Yeah that is weird behavior. I suggest archiving it into an NDIF image file in your image backup so OSX doesn't barf on it and it's still available by mounting the NDIF. Or simply archiving it as ".sit" if not used from the backup.

SkyCapt's picture
by SkyCapt - 2020, January 15 - 3:52am

Ya, I'm running it from native OS 9.2 where it's ok there. But ive got an image backup of my OS9 collection, which I reference into all the time when I'm in Tiger my main productivity OS. The image and the SSD having bootable OS9 both refuse to unmount when Tiger sees this file. Never found this before.

MikeTomTom's picture
by MikeTomTom - 2020, January 15 - 3:40am

Perfection I can't say, no eject is pretty bad

@SkyCapt: What are you running this on? Native Mac OS 9.2.2 or earlier? Or Classic on Mac OS X? If the latter, why would you be using it in classic mode? There's no point in having this in classic when OS X has md5 built-in. If it is causing issues when ejecting USB drives, archive it into an NDIF image file so OSX doesn't barf on it and it's still available by mounting the NDIF. Or dump it altogether and forget about it. It's not needed in classic on OS X.

MikeTomTom's picture
by MikeTomTom - 2020, January 15 - 3:33am

@Jatoba: I have taken a brief look at OS923's MD5 program. It may be Mac OS 9.x only.

On SheepShaver running Mac OS 8.6, it crashes the emulator without warning.

On my G4 eMac running 9.2.2 it errors on me with Error Message 2 and exits. On my 3rd attempt to get it to checksum a single flat file, the eMac locked up solid and I was forced to switch the power off at the outlet.

I had attempted drag & drop and also running the program itself by double-clicking it's icon.

If you are expected to additionally install his "updated" Finder extensions to get this to work, I'm not going there.

Perhaps someone else would care to try, but I'm sticking with Checksum on classic Mac OS's Wink

SkyCapt's picture
by SkyCapt - 2020, January 15 - 3:37am

Perfection I can't say, no eject is pretty bad - this is the first example I've identified acting that way. While I can avoid this app's folder and then eject, I'm afraid that if I leave the volume mounted too long, then osx might have a crawler in the background and then I can't eject only because I left it mounted too long? I'll try some more. Anyway, I can eject an image (not hardware) via logging out then back in.

Well I looked into the 923 and found all the little applets funnel down to shared libraries, and the libraries seem to be trying to access GPU which I don't have, so (almost) nothing works. It might be using GPU to enforce its 1600x1200 screen resolution minimum. They say that 923 suite requires 1600x1200 min.

Jatoba's picture
by Jatoba - 2020, January 15 - 12:44am

@MTT It could be incorrect, it certainly needs some investigation. I believe some of the apps are even FAT or 68k, most of which were compiled with REALBasic and CodeWarrior. The dev is also a member here (OS923), and although his tools have the goal of "developing Mac OS further", hence the "9.2.3" name and statements being 9.2.2-centric, there's some chance some of the tools will work way back.

I'm just bringing it up in case anyone is curious enough to investigate and find out what's up with it.

Personally, Checksum 1.3 already does, with perfection, everything I need it to.

MikeTomTom's picture
by MikeTomTom - 2020, January 14 - 9:45pm

@Jatoba: Requiring Mac OS 9.2.2 only, is somewhat of a limitation for a classic checksummer (if that info on the page is correct).

Jatoba's picture
by Jatoba - 2020, January 14 - 12:10pm

It seems there's potentially one more tool that perhaps may do checksums under Mac OS besides this one.

All I know is that it's part of the """OS 9.2.3""" package, found here. If anyone decides to poke at any of this, it is advisable to backup your entire drives first. It is unknown how stable or bug-free any of those tools really are.

SkyCapt's picture
by SkyCapt - 2020, January 6 - 4:43am

Weird behavior in Tiger, I don't mean running this, I mean just having the files laying around is doing a bad thing. I have both a multi GB imagefile of my OS9 software collection and an ejectable rw ssd, when I mount them in Tiger I can eject them, but if I so much as open a directory containing this app or its text files (its pdf files are ok) then I can't eject anymore because it becomes those files are "in use". Can't erase them the usual way either, because "in use". Again, not even opening the files but just using Tiger to scan the directory and icons. I can open my archive in OS9 (Disk Copy v6.5b13) without snagging "in use" so this is like a Tiger thing, but I am seeing a corruption/error in programming in the resource forks looking at em with ResEdit 2.1.3

I'm erasing my copies of these text documentation (the pdf is good enough) and then instead of having this app in my Applications folder, I'll tuck it inside its own subdirectory, and then I should be able to once again browse my OS9 docs and apps in Tiger without hooking into an "in use" non-eject.

SkyCapt's picture
by SkyCapt - 2019, December 30 - 12:09am

Ok, I got new test results. This program always reports the wrong md5 of resource forks, rats, then as you say the data forks report the correct md5 ... but only when the file is less than 2.0GB, more than 2.0GB is reporting wrong md5 with no error or warning about it.

MikeTomTom's picture
by MikeTomTom - 2019, December 29 - 10:00pm

This program is reporting wrong md5 results for about half the files I scan

Not for me. See "Hint" in page description. I'm only interested in MD5 checksumming of the data fork and nothing else. If anything, it is very slow, but this is Mac OS 9 and earlier.

SkyCapt's picture
by SkyCapt - 2019, December 29 - 9:03pm

Trouble here. This program is reporting wrong md5 results for about half the files I scan, but correct for the other half. Program's own checksum (its internal one) matches the documentation, it's not corrupted. I am mindful of the two forks, and this program is consistently wrong with many files, not randomly wrong. I also use osxterminal & another program named "Integrity 2.0" (which happens to be too SLOW for everyday use) & those two always have matching md5 results. Not this'un. Mem allocated to app, size of file being scanned, which fork(s), and launch via real OS9 vs emulation, none factor in - it's as if this program's md5 algorithm is flawed.

Also, standard "crc32" isn't supported here. OSX terminal does it when u replace the "md5 " shell command with "crc32 " instead. This here prog has a bunch of crc/32 algos but not one that matches today's standard.

md5 in osxterminal Hints:
See the md5 of just the resource fork, this way >
md5 {filename}/rsrc

Empty file or empty resource fork is always this >

See the md5 of a file's combined forks, this way >
cat {filename} {filename}/rsrc | md5

MikeTomTom's picture
by MikeTomTom - 2010, October 13 - 1:39am

It is an easy program to use, and for a Classic Mac, the only one I know of that does MD5 checksumming (there may be others but I don't know of them offhand).

On Mac OS X tho', I use the built-in MD5 checksummer via Terminal. Its also very easy to use and faster than starting Classic (if you have Classic) and much faster that this program. Terminal command is: md5(+ a space) drag icon of file to check into Terminal window after the space (to get filename and PATH to it into Terminal) and hit "enter" or "return" key.

Vitoarc's picture
by Vitoarc - 2010, October 12 - 4:54pm

A very easy program to use, and it works well in Classic Mode. Everyone who uploads critical software, such as System Software, should consider taking the couple of extra minutes to perform/add a checksum along with the upload. Smile

MikeTomTom's picture
by MikeTomTom - 2010, August 22 - 1:43am

The archived file should return the MD5 checksum:
e63a76b937006f44a26ec2a7042f4ef0 *Checksum_0_0.sit