[Prev][Next][Index][Thread]

Re: Executor/Win95



>>>>> "Tim" == Zoology  <Tim> writes:

    Tim> In your message (Wed, 17 May 1995 23:20:26 -0400), you wrote:
    >> If a Win95 port for Executor is made, then it should have long
    >> filenames even outside of an HFV file.  Many aspects of the
    >> Win95 environment are Mac-like.  You might want to try to
    >> implement some of them.  Also, running Mac programs directly
    >> from the Win95 desktop would be nice.
    >> 
    >> SimBoss

    Tim> Win95 will render the HFV obsolete (Executor/Linux does not
    Tim> by default use HFV files for precisely this reason; ext2fs
    Tim> allows 255 character filenames), so Mac folders become
    Tim> ordinary directories with two files for each Mac file
    Tim> 'filename' and '%filename' which are the resource and data
    Tim> forks.

[pedant mode on]

Actually, it will make HFV files much less important, but not totally
render them obsolete, since there are a few esoteric uses of HFV files
that remain.  In fact, we may be switching E/L and E/NS to use a HFV
file for the volume that holds the system folder because of one of
them.

Some programs find out where the System Folder is and then decide they
want to write something at the "root" of that volume.  On a UFS (UNIX
File System) implementation of the Mac FS, this has apps trying to
write in directories that normally won't have write permission.  Ugh.
The easiest way to get around this is to have the System Folder be in
an HFV.

In addition, some programs, like Norton Utilities (NU 1.0 runs under
Executor) know about disk layout and require an HFV or other hfs
formatted medium to work.  Of course you don't *need* NU if you're
using a UFS based implementation, but it's just an example.

[pendant mode off]

	--Cliff



Follow-Ups: References: