• Updated 2023-07-12: Hello, Guest! Welcome back, and be sure to check out this follow-up post about our outage a week or so ago.

Desperately seeking Mac OS Anthology 2000 & 2001 Edition

olePigeon

Well-known member
Not to add any anxiety, but gee wiz this was up on eBay last month.  $100 seems like a steal, and only 1 bid.  1999-2001.  Heck of a set.

https://www.ebay.com/itm/Mac-OS-Anthology-1999-2001-Mac-OS-7-X-on-DVD/183244330361?hash=item2aaa369579:g:O18AAOSwQKlbCZrg

There was another 2000/2001 set back in April.  That one went for over $200.

Don't know if it was a fluke.  I'm gonna watch eBay, hope to snag one.  I asked my local Apple repair guy, and he said he used to have it but not anymore.

 
Last edited by a moderator:

uyjulian

Well-known member
When I extracted the files from 1999 Mac OS Anthology, the only image that failed the checksum check while converting to dmg was the Swedish 7.5.3 image. I used an image from my Apple Support Area archive to replace the damaged file.

Here are the hacked extractors, so @max1zzz can fix his files: https://transfer.sh/giJWz/unar_hacked_overflow.zip

Try one. If it doesn't extract correctly, use the other one.

Changes in unar source code:

In XADStuffit5Parser.m, on lines 340, 341, 349, use numberWithUnsignedLongLong.

In the same file with each argument, add  | (1ULL << 32) .

 

Alex

Well-known member
Not to add any anxiety, but gee wiz this was up on eBay last month.  $100 seems like a steal, and only 1 bid.  1999-2001.  Heck of a set.

https://www.ebay.com/itm/Mac-OS-Anthology-1999-2001-Mac-OS-7-X-on-DVD/183244330361?hash=item2aaa369579:g:O18AAOSwQKlbCZrg

There was another 2000/2001 set back in April.  That one went for over $200.

Don't know if it was a fluke.  I'm gonna watch eBay, hope to snag one.  I asked my local Apple repair guy, and he said he used to have it but not anymore.
That's too much bread for me, if you snag one please share those 4 discs if you can.

 

Alex

Well-known member
Changes in unar source code:

In XADStuffit5Parser.m, on lines 340, 341, 349, use numberWithUnsignedLongLong.

In the same file with each argument, add  | (1ULL << 32) .
Hi

I was wondering why you mentioned the 1999 version? Is it because you had a similar issue with that set and the files inside the zip you added helped? To be honest I am not sure how I should proceed with those binaries. Could you provide some steps?

 

uyjulian

Well-known member
Hi

I was wondering why you mentioned the 1999 version? Is it because you had a similar issue with that set and the files inside the zip you added helped? To be honest I am not sure how I should proceed with those binaries. Could you provide some steps?
1. Open Terminal

2. Drag the binary to the window

3. Drag the archive to the window

4. Hit return

 

Alex

Well-known member
Did you build this yourself or download it somewhere. It's clean of viruses right?

 

uyjulian

Well-known member
 What and why did you modify it, I am kind of curious. Do you want to share some of those details. I mean what's the goal of the mod.

 


I have fixed decompression of broken >4GB files. It was an overflow problem. You can easily hack your way around that by bit shifting left 1 32 times and then add that to the (broken) size in the source code of The Unarchiver.
Changes in unar source code:

In XADStuffit5Parser.m, on lines 340, 341, 349, use numberWithUnsignedLongLong.

In the same file with each argument, add  | (1ULL << 32) .

 

Alex

Well-known member
@uyjulian I see what you did now. By the way I tried both binaries and although the files inside the mounted image show proper sizes and at least one of the .img files mounted. Amazing. I am going to go through the 4 discs I have that I suspected were corrupted and careful go through it all.

I may come back and report which of you binaries worked. Dude, amazing! You rock man, this is one heck of a hack you pulled off. I thought these images were long gone.

 

Alex

Well-known member
I have fixed decompression of broken >4GB files. It was an overflow problem. You can easily hack your way around that by bit shifting left 1 32 times and then add that to the (broken) size in the source code of The Unarchiver.
I was wondering about this point. What is broke, I mean the existing version of the unar cli can cope with files over 4GB as is. Could you clarify? I also was told that we were able to already decompress some of the img files in the past but some remained corrupted so this is still ongoing.

Could let me know more about this hacked version that you have. Sorry to derail the conversation but I would like to know more if you are willing to provide more details.

 

uyjulian

Well-known member
I was wondering about this point. What is broke, I mean the existing version of the unar cli can cope with files over 4GB as is. Could you clarify? I also was told that we were able to already decompress some of the img files in the past but some remained corrupted so this is still ongoing.

Could let me know more about this hacked version that you have. Sorry to derail the conversation but I would like to know more if you are willing to provide more details.


It was an overflow problem. 
From https://en.wikipedia.org/wiki/Integer_overflow

In computer programming, an integer overflow occurs when an arithmetic operation attempts to create a numeric value that is outside of the range that can be represented with a given number of bits – either larger than the maximum or lower than the minimum representable value.

 

Alex

Well-known member
I know the images on my server are compressed badly (Large stuffit archives just don't seem to unpack correctly). I can however obtain uncompressed images from what I think was my original source of the images. Do you have any idea what data is missing so I can check these images are good before replacing the ones on my server?
Max, any progress?

 

Alex

Well-known member
@uyjulian @max1zzz

Screen Shot 2018-06-15 at 00.50.50.pngLooks good. First disc tried and every img mounted in os9 VM (sheep shaver)! 

Also, your unar_unc_comp_overflow was the charm, to prove the point I tried straight unar and it gave me an error.

Thanks a million for this solution! 3 discs to go.

Screen Shot 2018-06-15 at 00.54.34.png

 
Last edited by a moderator:

CC_333

Well-known member
To avoid this error in the future (and to allow the unmodified unar to work properly), would it not be prudent to re compress these images and splitting the resultant archive into smaller bits that unaltered unar can "digest"?

Macintosh Garden uses this strategy to alleviate bandwidth limitations?

c

 

uyjulian

Well-known member
To avoid this error in the future (and to allow the unmodified unar to work properly), would it not be prudent to re compress these images and splitting the resultant archive into smaller bits that unaltered unar can "digest"?

Macintosh Garden uses this strategy to alleviate bandwidth limitations?

c
No, use a proper format that supports >4GB files like ZIP64 or 7z.

 

Alex

Well-known member
Changes in unar source code:

In XADStuffit5Parser.m, on lines 340, 341, 349, use numberWithUnsignedLongLong.

In the same file with each argument, add  | (1ULL << 32) .
@uyjulian I would love to edit the file which I have in front of me in Visual Code Studio, the problem is I am not an Objective C programmer so I can't do this on my own.

The only reason I am bringing this up is that disc 6 does not expand successfully. Without having work experience with objective-c I am unable to do 2 things, 1) I can't make changes to the code 2) I can't verify if disc 6 is indeed corrupt or if the source code for XADStuffIt5Parser.m can be altered further to potentially fix the issue or simply prove that the .sit file for disc 6 is simply corrupt and nothing can be done.

What are your thoughts?

—Alex

 

uyjulian

Well-known member
@uyjulian I would love to edit the file which I have in front of me in Visual Code Studio, the problem is I am not an Objective C programmer so I can't do this on my own.

The only reason I am bringing this up is that disc 6 does not expand successfully. Without having work experience with objective-c I am unable to do 2 things, 1) I can't make changes to the code 2) I can't verify if disc 6 is indeed corrupt or if the source code for XADStuffIt5Parser.m can be altered further to potentially fix the issue or simply prove that the .sit file for disc 6 is simply corrupt and nothing can be done.

What are your thoughts?

—Alex
Did you try using the other binary?

 
Top