OS/2 NetWare Requester FAQ
The following is based on an oloder NetWare TID, which may or may not still be available. It is provided here as a service to the OS/2 and NetWare communities at large. My version was previously hosted in the Rosenthal & Rosenthal knowledgebase, but as that is currently down for a rebuild, and as I have an upcoming eComStation-to-NetWare consultation, I thought I might put this up here.
Q. What are the default drive mappings in OS/2?
A. L: is mapped to the SYS:\LOGIN directory and P: is mapped to the SYS:\PUBLIC directory after login.
Q. Why is the drive mapping to public SYS:\PUBLIC and not SYS:\PUBLIC\OS2?
A. All network drives mapped in OS/2 are map rooted. Do not map drive P: to SYS:\PUBLIC\OS2. The search path is set to SYS:\PUBLIC\OS2 by default, which will give you access to the OS/2 utilities. If you change the drive to P: and execute a utility, the DOS version of the utility will be executed.
Q. If I try to go to the F drive to login I get the error message "SYS0015: The system cannot find the specified drive."
A. L: maps to the SYS:\LOGIN directory, however if the active drive is changed to L:, typing LOGIN will execute the DOS login. Therefore, login from the OS/2 boot drive (usually C: or D:) and LOGIN.EXE will be executed from the NETWARE subdirectory or from the L:\LOGIN. L:\OS2 is added to the OS/2 path by the client install giving a search path to the OS/2 LOGIN.EXE.
- Note: The default login drive (L:) can be changed in the NET.CFG.
Q. Is there a LASTDRIVE statement in OS/2?
A. Yes, change the DOS_LASTDRIVE setting in the DOS Settings Notebook to the last local drive. This needs to be manually changed for each DOS and WIN-OS2 session. For details on how to change the settings, see the IBM OS/2 online documentation Master Help Index.
- Note: NetWare Client for OS/2 does not support a LASTDRIVE statement in the CONFIG.SYS. For example, If a LASTDRIVE=E is placed in the CONFIG.SYS, an REQ0815 error will occur and no network drives will be mapped.
Q. What is the filename for the OS/2 login script?
A. In NetWare 3, the file is SYS:\PUBLIC\NET$LOG.OS2. For NetWare 4 and above, the container login script is used for both DOS and OS/2. Profile login scripts are typically used for OS/2 users.
-
Note: NetWare 4 and above supports:
IF OS="OS2" THEN...ELSE...END
in container login scripts.
Q. What DOS login script commands are not supported under OS/2?
A. The following login script commands are not supported under OS/2:
- COMSPEC
- DOS BREAK
- MACHINE NAME
- EXIT "file"
- MAP Sx (where x is a number from 1-16)
- Search drives are not supported under OS/2 (simply add additional drives/paths to the local CONFIG.SYS)
Q. How can I automate the login process?
A. There are two ways to implement this:
Method 1: NETWARE TOOLS AND STARTUP.CMD
1. Map all drives needed.
2. Capture any printer ports needed.
3. Save the settings as LOGIN.NWS or any filename of your choice. (The extension .NWS is added automatically.)
4. Add the following to the startup.cmd:
nwtools login.nws autoexit
exit
Notes:
- NWTOOLS does not execute a login script.
- Startup.cmd is executed each time OS/2 boots. It should be located at the root of the boot drive. You can create it as an OS/2 command file if it does not exist.
Method 2: CONFIG.SYS
Add the following lines to the end of the CONFIG.SYS.
CALL=C:\NETWARE\LOGIN.EXE
For OS/2 Warp, eCS, or OS/2 2.11 (with IBM CSD applied), use NWSTART.EXE from the OS2C1.EXE patch file.
CALL=C:\NETWARE\NWSTART.EXE
CALL=C:\NETWARE\LOGIN.EXE
Notes:
-
A local login script can be specified using the LOGIN.EXE /S command line option. For example:
CALL=C:\NETWARE\LOGIN.EXE /S C:\LOGIN.TXT SERVER\USER
- Remember that CALL waits for a return before processing continues, and RUN processes asynchornously. While RUN can improve the processing flow of some operations, in this case, CALL is more desirable, as the requester may take longer than expected to start.
Last Updated on by
Leave a comment
You must be logged in to post a comment.