Path: utzoo!censor!geac!torsqnt!hybrid!scifi!bywater!uunet!microsoft!gregj
From: gregj@microsoft.UUCP (Greg JONES)
Newsgroups: comp.os.os2.misc
Subject: Re: MS LAN Man: HPFS386/DOS compat., non-/dedicated
Summary: HPFS386 security, memory consumption
Message-ID: <70976@microsoft.UUCP>
Date: 1 Mar 91 01:09:26 GMT
References: <6694@mentor.cc.purdue.edu> <323.27c8ea45@mbcl.rutgers.edu>
Organization: Microsoft Corp., Redmond WA
Lines: 40

In article <323.27c8ea45@mbcl.rutgers.edu>, goldman@mbcl.rutgers.edu writes:
> In article <6694@mentor.cc.purdue.edu>, lairdkb@mentor.cc.purdue.edu (Kyler Laird) writes:
> > I noticed that by using HPFS386 (and local security) I give up my ability
> > to use the DOS box.  It makes sense to me that OS/2 1.3 is designed around
> > the 286 and HPFS386 around the 386 so that's the problem (in an abstract way),
> > but I want to know if this remains a problem when running OS/2 2.0
> You don't have to give up the DOS box if you don't want to.  What you can do
> is use the old (286-specific) version of HPFS, and then change the 
> "PROTECTONLY=YES" statement to "PROTECTONLY=NO".  (If you use the HPFS386,
> then you'll get an error message on boot.)  I understand that if you do this,
> you lose user file security on the server, if you run user security.

HPFS386 doesn't support the DOS box because handling interrupts (especially
network interrupts) in real mode, in 386 code on a 286 OS, is an incredible
pain in driver-level software.  Because DOS boxes work differently in OS/2 2.0
this restriction will disappear then.  (Disclaimer:  I have no idea whether
or not HPFS386 will exist for OS/2 2.0.  I'm not privy to long-term strategy.)

Using HPFS286 you can still have user-level security remotely, just as you
can on FAT file systems.  Local security is out though.  The bit about
"reformatting as HPFS386" is probably misleading documentation.  HPFS386
and HPFS use the same disk format;  it's just the access information that's
stored differently, so when you switch filesystems your ACLs have to be
moved.  I believe the LANMAN installer will do this for you;  if not, I
believe BACKACC and RESTACC are the utilities you need to run.

> > Also, I am planning to run some (not many) tasks at the server.  I have 16MB
> > RAM, 386DX/33.  At the server, I'll be running MS SQL Server, Imara Document
> > Filing System (Server Edition), Sytron's Sytos Plus Backup, file replication,
> > and some various utilities (using 'at').

SQL Server needs a fair amount of memory to run well.  Set up as non-
dedicated.  "Dedicated" really refers to the file server itself;  it's
for servers that do nothing but provide file service (plus occasional
apps like backup and so forth).  Bigger systems like SQL qualify as
"non-dedicated".

uunet!microsoft!gregj
Greg Jones, MS network development
[I just happen to work here.  Sheer coincidence.]