- #STUFFIT EXPANDER MAC SYSTEM 7 HOW TO#
- #STUFFIT EXPANDER MAC SYSTEM 7 MAC OS X#
- #STUFFIT EXPANDER MAC SYSTEM 7 ARCHIVE#
- #STUFFIT EXPANDER MAC SYSTEM 7 SOFTWARE#
Once the software is installed, you’ll end up with a Stuffit icon in your menu bar.
#STUFFIT EXPANDER MAC SYSTEM 7 MAC OS X#
If you opted not to have DropStuff and Expander Aliases created on your desktop, find the apps in their original install location you chose.įor Mac OS X 10.0 – 10.3 use Stuffit Standard 8.0.2, 10.0.2 or the above mentioned Stuffit Standard 7.0.3.
#STUFFIT EXPANDER MAC SYSTEM 7 ARCHIVE#
sit archive that is placed in the same directory as the source file/folder. Now grab any file or folder and drop it on the DropStuff icon. With that set hit OK and close the preferences. In there set compression level to “Fastest” as shown below (why we do this will be explained in the notes at the end of this article). Open DropStuff and go to the Preferences. Once the software is installed (your Mac will need a restart), you end up with icons on your desktop for Expander and DropStuff. Requires: Mac OS 8.6 or 9.x (Also works on PPC OS X up to 10.5) Requires: Mac OS 7.1 – 9.x (works on PPC as well)
#STUFFIT EXPANDER MAC SYSTEM 7 HOW TO#
I won’t cover how to open archives because if you have the below software installed to create archives, you’ll automatically end up with the software you need to open these archives.Ĭreating an archive is as simple as dropping a file or folder on the DropStuff application and a. sit archive in each OS and which software you’ll need to do it. So for best compatibility across ALL Mac OS versions, for archiving and preservation purposes stick with. toast image should also preserve resource forks but you end up with much bigger files as there is no compression, or at least not as efficient compression. bin will preserve the resource forks and preserve file integrity when stored in a non-Apple file system. bin file formats are also not preferred though when done properly. tar do not support Mac OS resource forks so don’t use those to archive classic data. You can grab the below mentioned resources from the Wired server. This article will go over the available options for creating such archives for each major OS version. Once the Classic file is compressed, it’s resource fork is preserved, letting you upload to an FTP site or Non-Mac computers safely. The resource fork is used mostly by executables, but every file is able to have a resource fork.įor example, uploading a Classic file or application directly to an FTP site or to a non-Macintosh computer will likely render the data useless.Ī good way to safely transfer Classic files is to first compress them using a resource fork friendly compression utility like DropStuff to create a. For example, a word processing file might store its text in the data fork, while storing any embedded images in the same file’s resource fork. A resource fork stores information in a specific form, containing details such as icon bitmaps, the shapes of windows, definitions of menus and their contents, and application code (machine code). When we deal with old Mac software or files, eg Classic (pre-OS X) there are resource forks to consider. But first, for those not in the know, why even bother? What makes Classic data so fragile?
Below is a list of Mac OS versions and architectures and the best Stuffit for them. So I took what Steve talked about on Mac Yak and ran with it. The topic was “How to transfer files between old and new Macs” and got me thinking, how far back can we go to send files between different Macs and OS versions? What really is the best way to package this data to ensure it survives transfers to Windows PC’s, Linux servers over FTP etc? Recently on Mac Yak episode #11 (which unfortunately got horribly mangled by YouTube so it’s not easy to watch) the topic of Classic data preservation and transfer was brought up.
0 kommentar(er)
