Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!BROWNVM.BITNET!DANFUZZ
From: DANFUZZ@BROWNVM.BITNET (Dan Bornstein)
Newsgroups: comp.sys.apple
Subject: Re: Sys Disk 5.0 files
Message-ID: <8907240953.aa02146@SMOKE.BRL.MIL>
Date: 24 Jul 89 13:48:36 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 37

(Sorry about the repost; our automated system mis-sent this to just
Bitnet...)

>From:         David Lyons <dlyons@APPLE.COM>
>
>In article <8907121556.AA03760@crash.cts.com> pnet01!pro-sol!mmunz@nosc.mil
> writes:
>>Why can't Apple just update PRODOS to support deleting of extended files..
>>it seems like that would be the simplest solution.
>> ...
>
>Then again...maybe there isn't *room* for the code.  16K isn't just gobs of
>room for an OS.  DESTROY isn't the only command that could conceivably be
>modified to deal with extended files--as soon as people could delete the
>things, they'd also want to be able to OPEN the forks & work with them, so
>most of the calls would need changes.

Yes, I realize that there isn't room for resource stuff in the language card
banks of RAM (funny how it's still called a "language card", no?) But, there
are legitamate reasons for wanting to deal with resources on a II-non-gs,
as Murph has pointed out. So, how 'bout Apple (or somebody) comes up with
a set of utilities which can be included in other programs to deal with
resources? Like being able to read and write files with resources without
getting the odious "Unsupported file type" error.

> Considering that there still wouldn't
>be a resource manager under ProDOS 8, how useful would it be?

Very useful for BBS programs, backup utilities, archive programs, where there
are *reasons* for manipulating files that your specific computer doesn't need.


-dan

Bitnet:    danfuzz@brownvm
Internet:  danfuzz@brownvm.brown.edu
AppleTalk: Find me a long enough cable and I'll see what we can do.