Date   : Wed, 13 Apr 1988 05:48:47 GMT
From   : hp-sdd!ncr-sd!crash!mwilson@hplabs.hp.com (Marc Wilson)
Subject: CP/M Directory Entries

In article <144@pt1.Wichita.NCR.COM> blair@pt1.Wichita.NCR.COM (Brian Lair)
writes:
>In article <948@anasaz.UUCP>, chad@anasaz.UUCP (Chad R. Larson) writes:
>> 
>> In addition, under CP/M 3.x, files in user area 0 with the system
>> attribute may be opened in read-only mode by programs running in any
>> user area.  Makes a good way to stash all your .com files.
>
>Does anyone know of a way to accomplish this in CP/M 2.2 ?

     Yes.  There is a patch for the 2.2 BDOS from Plu*Perfect Software
that will enable this feature.  Look for PUBPAT.LBR on your local RCP/M.
Or, you can email me, and I'll send you a copy.

     On the other hand, there is a better way.  Install a different BDOS.
You can use ZRDOS, from Echelon.  This allows you to mark a specific DU:
as "public."  Any file you place there can be found from anywhere else.
 
     There is also P2DOS/SUPRDOS/Z80DOS/etc.  These do roughly the same
thing, although better ( im my opinion ).  They use attribute bit F2
to mark a file as public.  If this bit is set, the file can be found
from anywhere else on the drive.  Example:  I have WS.COM and the overlays
in user 0 with the F2 bit set.  Now, I try to edit a file in C5:.  WS
looks in C5:, and doesn't find its overlays.  Next, it switches to drive
A:.  The files aren't in A5:, but in A0:.  The BDOS, on the other hand,
makes it *look* like they're in user 5, so that WS works.

     Any more questions?
-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Marc Wilson
     ARPA: ...!crash!mwilson@nosc.mil
           ...!crash!pnet01!pro-sol!mwilson@nosc.mil
     UUCP: [ cbosgd | hp-sdd!hplabs | sdcsvax | nosc ]!crash!mwilson
     INET: mwilson@crash.CTS.COM
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~