Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uunet!microsoft!alistair
From: alistair@microsoft.UUCP (Alistair BANKS)
Newsgroups: comp.os.os2.misc
Subject: Re: MS LAN Man: HPFS386/DOS compat., non-/dedicated
Message-ID: <71202@microsoft.UUCP>
Date: 11 Mar 91 21:08:16 GMT
References: <323.27c8ea45@mbcl.rutgers.edu> <6943@mentor.cc.purdue.edu> <328.27cb8759@mbcl.rutgers.edu> <1991Mar4.173710.11284@ingres.Ingres.COM>
Reply-To: alistair@microsoft.UUCP (Alistair BANKS)
Organization: Microsoft Corp., Redmond WA
Lines: 22

In article <1991Mar4.173710.11284@ingres.Ingres.COM> seg@ingres.com (scott e garfinkle) writes:
>It is also worth noting that, if you simply replace HPFS386 with HPFS, you
>may "lose" part of your directory tree.  I imagine this has to do with the
>limit to the number of EAs in HPFS (I forget what it is) that is removed with
>HPFS386.  Anyway, a coworker did this, and suddenly, a whole directory
>disappeared.  It came back when he reloaded HPFS386.  He needed to do a
>complete backup, reformat, and restore to use HPFS.  This was, btw, HPFS386
>from Lanman 2.0 and HPFS from OS2 1.3 SE.


You don't actually "lose" any part of your disk - HPFS386 _is_ secure,
so when you replace it with HPFS, it would be crazy if that simply
removed all security - so those parts of your disk you think you are
losing, are actually those parts with restricted access - as recorded
in the ACL entries on the disk.

So the solution is, if you want to move from hpfs386 to hpfs, first
remove all ACL entries on the HPFS386 partition, then switch.

See the NET ACCESS command.

Alistair Banks, Microsoft.