Currently Being ModeratedMar 31, 2012 6:57 PM (in response to Don Archibald)
Yes - I have CD and it is working well. I do not have 7.6.x I have 7.5.3 with FDD likte backup on HD. Beside this I have CD with OS 8 ... unfortunately in German version. I also own OS 9 but it needs more RAM than amout installed on my PB
Currently Being ModeratedMar 31, 2012 7:07 PM (in response to BigLynx)
I seem to recall that some Stuffit archives were "self-extracting", however, I believe they used a different extension (.sea?)
Try the following link - beware that it will start downloading automatically. The file type is .hqx and I don't know if 7.5.3 will know what to do with that either:
Wish I could do better BigLynx; it's been something like 20 years since I used Stuffit.
Currently Being ModeratedMar 31, 2012 10:47 PM (in response to BigLynx)
OS 8 and 9 Install CDs usually include an uncompressed version of Stuffit Expander; the same may be true for the OS 7.5.3 CD.
Insert the CD in the drive while the machine is running OS 7.5.3; do not boot the machine to the CD. Once the CD mounts and is accessible, open it.
The location for Stuffit Expander on the CD varies a bit from version to version, but it should be located in a folder named Aladdin Software somewhere on the CD.
Try looking in the folder named Software Installers; if the Aladdin Software folder is not 'loose' in there, look for one named Internet Access and see if it's in that.
Once you locate the Aladdin Software folder, dig into it and you should find an uncompressed copy of Stuffit Expander. Copy that item to your hard drive. You should be able to use it right away.
You can then use that to decompress newer versions of Stuffit Expander if you wish.
Currently Being ModeratedApr 2, 2012 9:43 AM (in response to Don Archibald)
Don - it was very good tip. Thank you. I found uncompressed Stuffit on Mac OS 9.x PL CD and install it successfully on Version 7.5.3. Works excellent!
I also found on this CD great DiskCopy tool - also works on V7 and mounts img files (also those created on Mac OS 9).
On MacOS 8 DE (german) CD there is no Stuffit at all.
Now - I have one problem more. I do not have on my Mac OS 7.5.3 a tool to mount .SMI file. It should be self-mounting but probably on systems starting from Version 9. On 10.7 system says that file is too old for mounting and should be converted ... but I do not have idea how.
I unstaffed .SMI file but still need some idea how to extract from it drivers for my ORiNOCO PCMCIA Ethernet card to make it working on 7.5.3 and connect PB 1400 to the net :-;
Currently Being ModeratedApr 2, 2012 11:42 AM (in response to BigLynx)
A .smi disk image is a Self-Mounting Image file type - it should open when double-clicked. If it needs any help opening, Disk Copy should be able to provide that.
However, Stuffit Expander can interfere with the normal process of managing and mounting disk image files. The solution - double-click Stuffit Expander, and open its Preferences (under the File menu). Select "Disk Images" from the list on the left, then turn off (uncheck) "Mount Disk Images". Quit Stuffit Expander.
Currently Being ModeratedApr 2, 2012 3:24 PM (in response to Don Archibald)
yes - I was trying to mount .smi but it is recognized by my system as ... ClarionWorks document. Disk Copy is ignoring it (no on the list of possible files to open). Stuffit is ignoring the file (doing nothing) when pointed for opening.
Currently Being ModeratedApr 4, 2012 8:33 AM (in response to Don Archibald)
I was trying on three .smi files and the result is the same. I also found that DiskCopy terminates with error "The file <file> does not have a recognized file type" when dragging&dropping file on running application
Currently Being ModeratedApr 5, 2012 12:45 PM (in response to BigLynx)
From the error message it sounds like the .smi file has lost its File Type or Creator code, or both. This can happen during transit across the web, such as when the file is not protected during download; or when it has been downloaded or processed using a machine running Windows or even OS X.
Open ResEdit, and using its Open function open one of the .smi files.
• Fixing the Creator code:
In the array of items presented in the ResEdit window, look for one named BNDL - double-click it to open it. In the new window, double-click the item named 128 in the ID column.
At the top of the new window will be a text box named "Signature". It should contain the four-letter code
If it does not contain that, fix it. Then close that window and close the BNDL window.
• Fixing the File Type code:
In the array of items in the ResEdit window, locate the one named FREF - double-click it to open it. In the new window, double-click the item named 128 in the ID column.
At the top of the new window should be a text box named "File Type". It should contain the four-letter code
If it does not contain that, fix it. Then close that window and close the FREF window.
• Then either choose Save from ResEdit's File menu, or close the last window - you'll be asked if you want to save changes; click OK. (If you made no changes, there will be no opportunity to Save, of course.)
Then test the .smi file by double-clicking it.
General notes re using ResEdit -
1) All File Type and Creator codes are exactly four characters long. These characters can include non-text characters, such as numbers or even punctuation characters (including a space as a character).
2) All File Type and Creator codes are case sensitive - capitalization or lack thereof does make a difference. They must be absolutely correct in order to work.
3) Good practice says that one should use ResEdit only on a copy of something, not on the only one available. This aids in recovery if something goes wrong.