Files that have no filename extensions (used by Windows and OS X, but not by OS 9) and have lost their Type and Creator codes (used by OS 9, but not by Windows or OS X), and are then written to a DOS-formatted disc by OS 9 and copied back to a Mac disc, are usually if not always misidentified by the OS X Finder as Unix executables.
Your company's old files, created in applications that ran in OS 9, probably have never had any filename extensions. Their Type and Creator codes have evidently been lost; those are what OS 9 uses to link the files to the applications that created them. If the files have also been written by OS 9 to any disk or flash drive formatted for Windows, i.e. FAT16 or FAT32, they have also lost their resource forks. The resource fork is a portion of a Mac file that has no analogous structure in a PC file. When a Mac file that contains data in its resource fork is written by OS 9 to a PC-formatted storage device, there's no place in the Windows file structure for that data — so it is simply discarded. When the Mac file is later copied back onto a Mac-formatted storage device, its resource fork is gone along with whatever data it contained, and the file may for all practical purposes be destroyed. OS X handles writing Mac files to Windows-formatted drives more gracefully, but passing files back and forth between OS 9 and OS X via a Windows-formatted storage device is asking for trouble.
I don't know just what practices have been used in moving these files from the Macs they were created on to the one you're trying to open them on now, but I suspect there has been some unwitting demolition in the process.
If copies of these files are still stored on the old Mac on which they were created, and that Mac still works, get on it and double-click the saved copies of the files to open them in the program(s) that created them, and make notes of which application opens each of the files. Be aware that the folder structure containing the files may have to be preserved exactly as it is for the files to open properly — do not reorganize anything. It may be essential, for example, for a PageMaker file to be kept in the same folder as all the individual files that have been "placed" in it using the Place command in PageMaker. If any of those files are moved elsewhere, they may be missing from the PageMaker document when it opens. I've never used Quark or Freehand, so I don't know whether they have the same requirement, or other requirements that are less than obvious.
Any of the old manuals that you're able to open in their original applications can be saved as PDF files using an invaluable OS 9-based "printer driver" called
PrintToPDF. They can then be opened in Adobe Reader or Preview on your G5 running OS X, though you won't be able to edit them easily. If you require the ability to edit these files on the G5, rather than on the old computer using the apps that originally created them, you will need first to discover which OS 9-based application created each one, and then ascertain what if any current OS X-based application is able to open the file format used by that old application. In the case of PageMaker files, that will probably be Adobe InDesign or nothing. InDesign may also open old Quark files; I don't know. Aldus or Adobe Freehand files may be openable using Adobe Illustrator. These are just guesses.
Dragging and dropping the files onto MS Word or TextWrangler may reveal, buried somewhere in them, the name of the application(s) that created them. I know a PageMaker file, opened as plain text, will always contain the word "PageMaker". As for other file formats, I'm not sure.
Message was edited by: eww
Message was edited by: eww