spexet@ux.acs.umn.edu (D. Robert Spexet II) (10/13/90)
Has anybody here been having problems with the PROFILE.BAT files in IBM's OS/2 LAN Server 1.2? Here is the situation: We've set up a network, using the OS/2 LAN Server 1.2 software for the file server, and the DOS LAN Requester program for the workstations. For those that use this software (which probably includes those that are running LAN Manager), one can set up a file called PROFILE.BAT, which in- cludes a series of DOS commands that will be executed when a user logs on, much like the AUTOEXEC.BAT file. The PROFILE.BAT file is placed within the DCDB\USERS\userid subdirectory, one for each user. For reference, here is the PROFILE.BAT file I'm using: =========================================================== PATH %PATH%;D:\;E:\ SET TEMP=D:\WINDOWS\TEMP =========================================================== where D:\ and E:\ are network volumes. The problem we're running into is this: While the PROFILE.BAT file is being executed, the environment variables (like TEMP and PATH) appear to be set correctly. But, when the PROFILE.BAT file stops running, all the environment variables are reset to what they were before the PROFILE.BAT file was exe- cuted. (i.e., the PATH is reset to what it was before the PROFILE.BAT file was executed, and the TEMP variable disappears, as if it were never set.) Has anybody else run into this problem? And, if so, does anybody know how it can be fixed? Thanks, -D. Robert Spexet II, Post Office Box 14909, Minneapolis, Minnesota 55414-0909 Internet: spexet@ux.acs.umn.edu BITNET: spexet@umnacux.BITNET UUCP: rutgers!umn-cs!ux.acs.umn.edu!spexet
tracy@casbah.acns.nwu.edu (Phil Tracy) (10/15/90)
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