🚀 go-pugleaf

In article <10408@pasteur.Berkeley.EDU> korn@anableps.berkeley.edu
(Peter "Arrgh" Korn) writes:
>In <1329@ccnysci.UUCP>, alexis@ccnysci.UUCP (Alexis Rosen) said:  
>>Something *VERY* screwy is going on here. I just looked at the boot blocks on
>>my two and they unquestionably say, ten open files. Well, that's a little
>>weird. See, I'm running MultiFinder....
>
>Not screwy at all, when you think about it.  MultiFinder has to play a number
>of games behind-the-scenes in order to work as well as it does.  One of
>these is to look at the number of files that can be opened at once listed
>in the boot blocks and, when MultiFinder is running, increase that number
>by some factor [etc.]

Hm. I've read that Tech Note too, I think.

>>Now, I just tried to open lots of files in ResEdit and I hit a hard limit
>>of three open files.
>What sort of error message did you get using which version of ResEdit under
>which version of the OS when this happened?

Um. The same version that just opened thirteen files with no problems. I
guess I'm going to have to do a bit more exploration.

My question still stands, though- what are those doohickeys (FCBs?) for?
Data forks, Resource forks, or both? if both, do I use up two slots if I
open both a file's data and resource forks? I had originally assumed that
they were for the data fork only...

Alexis Rosen
alexis@ccnysci.uucp