Subject: Re: StarGroup 3.2 w/Dos 6.2?
Newsgroups: comp.sys.att,comp.sys.ncr
Followup-To: comp.sys.att,comp.sys.ncr
References: <CInvy1.1E5@chinet.chinet.com>

Leslie Mikesell (les@chinet.chinet.com) wrote:
: We have a couple of offices running StarGroup 3.2 software with
: SysVr3 on the server.  They are reasonably happy with the current
: performance and service and thus don't want to spend a lot to
: upgrade to a new release.  However, they are buying newer machines
: as DOS clients and want to be able to use larger disk drives than
: Dos 3.3 allows.  Is there a way to make the 3.2 client software run
: under a current release of MSDOS?

	The following is a copy of some instructions we received from AT&T
back in the good old days when we had a contract with them.  This has been
working pretty well for us - can't say about DOS 6.x 'cause we don't have
any of those beasties, but for 5.x and windows 3.1 it is okay.  Information
was theirs, typos are mine.

	02/25/94 Update.
	Using the following instuctions I have been able to get StarGROUP 3.2
to load under DOS 6.0, and by using DOS 6.0's redir.exe I was able to get
StarGROUP to load under DOS 6.2.

	Tell Windows that your network is "Mircosoft Network (or 100% 
Compatable".



---------------------------------- CUT HERE ------------------------------

Issue Date: 7/18/91

Installing DOS 5.0 on an existing 3.2 StarGROUP Client machine:

Note>>	AT&T Computer Systems does not plan to certify 3.2 StarGROUP software
	with DOS 5.0.  The StarGROUP 3B2/386 Server Program V3.2 has been
	manufactured discontinued.  The instructions presented here are an
	enhancement of the instructions included in the "Microsoft MS-DOS
	Getting Started" guide.  These instructions assume that the user
	purchased the Microsoft Retail DOS 5.0 UPDATE package.

1.  If the client workstation is currently running a version of MS-DOS other
    than DOS 4.01, re-install the 3.2 StarGROUP client software.  Select "Yes"
    in response to "Will you be using DOS version 4.0/4.01?".

    The REDIRVER variable in the PROFILE.SYS file will read "REDIRVER=4".  The
    location of the PROFILE.SYS file can be found by issuing the SET command
    to display the machine's PROFILE environment variable.

	SET [Enter]
	.
	.
	PROFILE=c:\attnet\profile.sys
	.

	TYPE C:\ATTNET\PROFILE.SYS [Enter]
	.
	.
	REDIRVER=4

2.  Run the StarGROUP RECONFIG program and make the following changes:

	Select "Edit parameter settings" from the "Configuration and Tuning" 
	Menu.

	Set "Prompt to Load [Y]" to "Y".

3.  Install DOS 5.0 per the instructionsincluded with the DOS release.

	See the "Microsoft MS-DOS Getting Started" guide pp 5-12.

4.  After DOS 5.0 reboots, answer "N" to the "AT&T StarGROUP(TM) Software
    Version 3.2, Do you want to load the software? (Y/N)" prompt.

5.  Locate the DOS 5.0 diskettes containing the network redirectors.

	3-1/2" Floppies - Disk 3
	5-1/4" Floppies - DISK 6

6.  Update the rediector and setname programs in the ATTNET subdirectory on
    the workstation with the redirector and setname programs provided with
    DOS 5.0.  Follow the instructions provided in the "Microsoft MS-DOS
    Getting Started" guide, Chapter 3 "Updating Networks for MS-DOS Version
    5.0" under the section "Microsoft MS-Net and 100-percent Compatable".
    There is no need to do step 3 of these instructions. i.e., In the 
    RULES.LST fine in the ATTNET directory, the "setname.exe%COMPUTERNAME"
    command line can remain after the "rdrload.exe %RDRPARMS" command line.

	General syntax of the command lines to copy setname and redirector
	programs:

	expand [A:|B:]\redir.2x_ [driveid:]\attnet\redir.exe
	expand [A:|B:]\setname.ex_ [driveid:]\attnet\setname.exe

7.  Run the SETVER routine to instruct the clients loader for the redirector
    program to execute as if it were loaded on a DOS 4.0 machine:

	SETVER RDRLOAD.EXE 4.00
	(The following line we added at CSU)
	SETVER ATTSTART.EXE 4.00

	Note>> The 4.00 parameter in SETVER command line is related to the
	       REDIRVER variable value in the PROFILE.SYS file.

8.  If necessary, run the RECONFIG program to make the following change:
    (This step is done if you want the client software to load automatically
    on boot)

	Select "Edit Parameter Settings" from the Configuration and Tuning"
	menu.

	Set "Prompt to Load [Y/N]" to "N".

9.  Reboot the machine and load the network software.


Notes:

1.  Changes to the "Microsoft MS-DOS Getting Started" guide:

	In chapter 3, page 20, "Mircosoft MS-Net and 100-percent Compatable"
	Section:  ignore Step 3.  In the RULES.LST file, the "setname.exe
	%COMPUTERNAME" command line can remain after the "rdrload.exe
	%RDRPARMS" command line.