• Updated 2023-07-12: Hello, Guest! Welcome back, and be sure to check out this follow-up post about our outage a week or so ago.

Mac Plus system 7.0.1 question

Wawavoun

Well-known member
Hello,

Pardon if the question is a very basic one...

How can I change what is called in Windows 'file association' into system 7.0.1 ?

I have some .for files probably made with Absoft Fortran and I cant open it with MS Fortran.
Double click give an error about missing application and trying to opent from MS Fortran they are not show into the open file dialog box...

Thanks.
Philippe
 

Crutch

Well-known member
I haven’t used MS Fortran but assuming it is looking for TEXT files, and your .for files are somehow not of type TEXT, you just need to change the file type.

There are many ways to do this but most people have (or can easily get) a copy of ResEdit so I recommend using that: in ResEdit, open your .for file, then choose File —> “Get Info for File Xxxx” (or a similar command, I forgot exactly what it’s called). Then change the filetype (not ‘creator’) from whatever it is to (I assume) TEXT (in capitals) and try again.

That should let you open it from within MS Fortran. If you want to be able to double click it, you will need to change the ‘creator’ code also. To find out the right one, create a new file from MS Fortran and save it. Then do “Get Info…” in ResEdit and note the indicated ‘creator’ code. Change the creator code on all your files to the same thing (along with file type ‘TEXT’) and it should work.
 

MacKilRoy

Well-known member
Macintosh systems prior to OS X did not use .xxx filename extensions to denote what applications opened files.

The 'Mac Desktop' files that are hidden on a disk track the applications that are installed on that disk. When you 'rebuild the desktop', part of the process is that it finds all applications on the disk, and builds a database of file types it can open, so that when you double-click a file, it opens the right program.

File types on the classic Mac system are stored within the file itself, accessible through a tool like ResEdit (using the 'Get Info' within ResEdit).

An application is file type APPL and then it has a unique creator code. You can find the creator type for an app by also using 'Get Info' on an application (again, within ResEdit). I don't know the file type or creator for the Fortran files, but you'll need to assign a file type and creator to the files so that they can open using Fortran.

It's a far simpler solution than Microsoft's 3 character extension, but in some ways far more complex.
 

Wawavoun

Well-known member
Hello there !

Okay now I can edit and compile fortran code without error. I got a 'source_name apl' file in the same directory as source file.

When I try to launch one of these apl (i have try with many demos sample etc...) then each time I see a windows opening and immediately closing and nothing else. No warning no errors etc...
Trying from the file system by double click or from inside MS Fortran by "execute" menu entry give the same result.

Any idea of what happen ? Is there a way to trace this and see where is the problem ?

Regards.
Philippe
 

rjkucia

Well-known member
I haven’t used MS Fortran but assuming it is looking for TEXT files, and your .for files are somehow not of type TEXT, you just need to change the file type.

There are many ways to do this but most people have (or can easily get) a copy of ResEdit so I recommend using that: in ResEdit, open your .for file, then choose File —> “Get Info for File Xxxx” (or a similar command, I forgot exactly what it’s called). Then change the filetype (not ‘creator’) from whatever it is to (I assume) TEXT (in capitals) and try again.

That should let you open it from within MS Fortran. If you want to be able to double click it, you will need to change the ‘creator’ code also. To find out the right one, create a new file from MS Fortran and save it. Then do “Get Info…” in ResEdit and note the indicated ‘creator’ code. Change the creator code on all your files to the same thing (along with file type ‘TEXT’) and it should work.
Is this a common solution for when applications don't want to open files? For example, I've found that StuffIt archives downloaded from the internet can be really hit-or-miss as to whether StuffIt wants to actually open them or not. I'm guessing this is related to the resource forks getting stripped when a file is on a non-HFS filesystem right?
 

Wawavoun

Well-known member
Re,

Some progress...

I found that if I copy the 'pi apl' into the directory 'f77 overlays' then the program start and run well. Its a pure "console" application.

Trying the 'demo apl' which use graphics I have to copy "toolbx.sub" from the subroutine directory again into the f77 overlays directory...
The program start but the os complain about "error 12" and need to restart.

It seems that all theses stuffs from "overlays" directory and "subroutines" directory should be moved or copied to a place where they can be found by any application when they start from anywhere.

I have try to rebuild the desktop but this dont change anything.

I have no documentation so...

Have you an idea what to do and where they should go ?

Regards.
Philippe
 
Top