Welcome to DU! The truly grassroots left-of-center political community where regular people, not algorithms, drive the discussions and set the standards. Join the community: Create a free account Support DU (and get rid of ads!): Become a Star Member Latest Breaking News General Discussion The DU Lounge All Forums Issue Forums Culture Forums Alliance Forums Region Forums Support Forums Help & Search

bbernardini

(9,938 posts)
Wed May 13, 2020, 05:50 PM May 2020

Trying to show the package contents of an old app on my Mac, but it's showing up as a TextEdit file.

When I say old, I'm talking 1994. Back then, it would show as an executable app. I've extracted it from the CD-ROM to my current Mac (running Catalina), but the file is now showing as a TextEdit file. Even if there's no hope of running it on my current machine, I would still like to try and view the package contents. Does anybody know of a way to do this? (I've tried looking for a solution, but I can't seem to find the right combination of search terms.) Thanks!

2 replies = new reply since forum marked as read
Highlight: NoneDon't highlight anything 5 newestHighlight 5 most recent replies
Trying to show the package contents of an old app on my Mac, but it's showing up as a TextEdit file. (Original Post) bbernardini May 2020 OP
1994! CloudWatcher May 2020 #1
Wow, thanks! bbernardini May 2020 #2

CloudWatcher

(1,850 posts)
1. 1994!
Wed May 13, 2020, 06:27 PM
May 2020

Well you're talking about an app that was working with "Classic" Mac OS (probably system 7). Files back then had two parts bundled together, a "data" fork and a "resource" fork. The modern MacOS, since Mac OS-X, mostly(*) got rid of that notion, since it was pretty foreign to Unix filesystems (* I'm simplifying a lot).

When you copied the file off the CD, it's possible it just copied the data fork. To check, fire up a unix shell with terminal, and use the "ls" command. If the file is called "foo" ...

ls -l "foo

Ls will show the size of the data fork (in bytes). But ...

ls -l "foo/..namedfork/rsrc"

will show how big the source fork is (in bytes). (ref: http://xahlee.info/UnixResource_dir/macosx.html)

If you used Finder to copy the file it should have all of it, but "cp" and some other utilities would copy just the data fork by default.

And now ... you'll probably want to use a "resource fork editor" to pull apart the pieces. Apple used to call this "resedit" but now you'll probably want to use something like ResKnife (from sourceforge.net). Alternatively, you can install Xcode and use the DeRez command line tool to get to the pieces Some background: https://en.wikipedia.org/wiki/Resource_fork

But .. you might be more than casually interested in Sheepsaver.

https://sheepshaver.cebix.net

It's an emulator that will (with appropriate disk images) let you boot Classic Mac OS and run your app. I've not run it for years, but it worked pretty well when I tried it last (pre-Catalina, so I don't know if it works anymore). The github page for it is active, so I'm guessing it works still

https://github.com/cebix/macemu

Good luck! Be sure and wear a decent mask, the dust flying off these old apps can get pretty nasty

Latest Discussions»Culture Forums»Apple Users»Trying to show the packag...