Xref: utzoo comp.dcom.lans:6220 comp.sys.att:10605
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!csun!nic.csu.net!csus.edu!ucdavis!csusac!porterg
From: porterg@csusac.csus.edu (Greg Porter)
Newsgroups: comp.dcom.lans,comp.sys.att
Subject: Re: Questions about StarGROUP Software
Message-ID: <1990Oct17.144704.21436@csusac.csus.edu>
Date: 17 Oct 90 14:47:04 GMT
References: <1990Oct16.173745.18064@mccc.uucp>
Reply-To: porterg@csusac.UUCP (Greg Porter)
Organization: California State University, Sacramento
Lines: 22

In article <1990Oct16.173745.18064@mccc.uucp> pjh@mccc.uucp (Pete Holsberg) writes:
>I'm in the process of installing StarGroup software (Version 3.2) on a
>386 running SV/386 R3.2.2 and a bunch of Zenith PCs running DOS, and
>have run into a couple of small things. 
>
>1.  The "DOS Client Server Admin's Guide" mentions that it "...is
>possible to configure a computer as a concurrent client/server..." but
>neither it nor the "386 Server S/w Installation and Admin Guide" tell
>how to do this. 
>
Simul-Task will only allow a concurent client/server to run dos programs
NOT access network resources like shared printers and shared directories.
In order to do both you need BOTH the Simul-Task 386 software AND the  
"StarGROUP Software Simul-Task Client Interface Program".  We have found
that you need to use this only occasionally.  These two packages are big
cpu hogs which can really knock down system performance.  

I hope this helps
-- 
| Greg Porter         |  UUCP:  ..ucdavis!csusac!porterg   -OR-               |
| CSU, Sacramento     |         ..ames!pacbell!sactoh0!csusac!porterg         |
| (916) 278-4734      |  INTERNET:  porterg@csusac.csus.edu                   |