Since OS X recognizes them as unix files, is it possible they have
corrupt resource forks or have lost the resource fork? I'm admittedly
not very familiar with That still doesn't explain why they show
completely blank, though.

Here are a couple more ideas to try for viewing that may work better
for binary files:
http://stackoverflow.com/questions/1765311/viewing-file-in-binary-in-terminal
https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man1/od.1.html

Stickman

On Sat, Mar 8, 2014 at 1:17 PM, Tom Frikker <[email protected]> wrote:
> Thanks for all the replies, they're all great ideas.
>
> I'm using TextWrangler for OS X... I tried vim, no difference.
>
> Using cat to make a text file, the resulting file shows the same text as
> just opening the original files with a text editor does.
>
> Using cat to just spit everything into the terminal just results in a long
> line of question marks.
>
> And to clarify, I believe these files are either just resource data files or
> small programs written in 68000 assembly.
>
>
> On Saturday, March 8, 2014 7:52:07 AM UTC-5, Koralatov wrote:
>>
>> On Sat, Mar 08, 2014 at 02:24, Tom Frikker wrote:
>> > I have files to be transferred to a floppy disk for the Mac 128k on my
>> > computer. Two of the files are called Unix Executable Files by my
>> > MacBook Pro. Apparently, according to a text editor, they are empty.
>>
>> Which text editor did you use to open the files?  TextEdit sometimes
>> does that, but I've had more success using vim, which tends to be less
>> clever and treat the file as a string of bytes.
>>
>> > Obviously, this is not the case, as they are both 397KB. Does anyone
>> > know how to open these files, or how to see the code in them? It's
>> > very important that I figure out how to open these files.
>>
>> As above --- try vim.
>>
>> Failing that, have you tried an inelegant brute-force approach and tried
>> to use cat to pipe the file contents into a new file?  Something like:
>>
>>      $ cat OLD_MAC_FILE > TEXTFILE.TXT
>>
>> Hope that helps.
>>
>> --
>>      Mike | <http://koralatov.com>
>>             15.4" `Penryn' MacBook Pro 2.66 | 20" iMac G4
>>                     `Key Lime' iBook G3 466 | G4 Cube 500
>
> --
> --
> -----
> You received this message because you are a member of the Vintage Macs
> group.
> The list FAQ is at http://lowendmac.com/lists/vintagemacs.shtml and our
> netiquette guide is at http://www.lowendmac.com/lists/netiquette.shtml
> To post to this group, send email to [email protected]
> To leave this group, send email to [email protected]
> For more options, visit this group at
> http://groups.google.com/group/vintage-macs
>
> Support for older Macs: http://lowendmac.com/services/
> ---
> You received this message because you are subscribed to the Google Groups
> "Vintage Macs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.

-- 
-- 
-----
You received this message because you are a member of the Vintage Macs group.
The list FAQ is at http://lowendmac.com/lists/vintagemacs.shtml and our 
netiquette guide is at http://www.lowendmac.com/lists/netiquette.shtml
To post to this group, send email to [email protected]
To leave this group, send email to [email protected]
For more options, visit this group at 
http://groups.google.com/group/vintage-macs

Support for older Macs: http://lowendmac.com/services/
--- 
You received this message because you are subscribed to the Google Groups 
"Vintage Macs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to