Path: utzoo!attcan!uunet!know!sdd.hp.com!wuarchive!julius.cs.uiuc.edu!apple!bionet!hayes.ims.alaska.edu!accuvax.nwu.edu!casbah.acns.nwu.edu!tracy
From: tracy@casbah.acns.nwu.edu (Phil Tracy)
Newsgroups: comp.os.os2.misc
Subject: Re: PROFILE.BAT files in LAN Server 1.2...
Message-ID: <549@casbah.acns.nwu.edu>
Date: 15 Oct 90 16:15:24 GMT
References: <2416@ux.acs.umn.edu>
Sender: news@casbah.acns.nwu.edu
Reply-To: tracy@casbah.acns.nwu.edu (Phil Tracy)
Organization: Academic Computing and Network Services, Evanston, Il.
Lines: 29

D. Robert Spexet II writes [loosely quoted]
	What's up with the PROFILE.BAT files in Lan Server 1.2???

Well, they don't work.  period.  neither do the profile.cmd's  period.
We have been in contact with tech support in Austin and Base Support in
Boca Ratan [sp?] several times in the past, and it's a known problem.
We've been told they're working on it.  

The profile's seem to work for things like COPY, DELETE, etc., but not for
environment variables.  We wanted to to exactly what you're trying to do
for some of our users--set PATH and TEMP vaiables and so forth -- this is
especially handy for OS/2 requesters, which require full paths for any
applications in order to find all of their .DLL files and so forth.  

Our work-around for most things was as follows.  When defining apps with
the full-screen interface, put, e.g., STARTWP.BAT instead of WP.EXE for the
command line to start an application.  Then write those commands in your
batch file, instead of the PROFILE.BAT.  Make the last line of the batch
file
the command you would have typed in the application definition.

I'm posting this, since it seems of general interest, but if anyone wants
to pursue this, please e-mail me (unless this is of more general interest.)
I'm relatively new to this group, but I've been working heavily with
OS/2 Lan Server 1.2 since June.  Bear with me  :-)

Phil Tracy
Northwestern University Academic Computing
tracy@casbah.acns.nwu.edu