Metropoli BBS
VIEWER: os2u1.txt MODE: TEXT (ASCII)
NOVELL TECHNICAL INFORMATION DOCUMENT

TITLE:  OS/2 Utilities for NetWare v3.12 and v4.10
README FOR:  OS2U1.EXE

NOVELL PRODUCTS and VERSIONS:
NetWare 3.12
NetWare 4.02
NetWare Client for OS/2 2.11
NetWare 4.1
NetWare Client for OS/2 2.12

ABSTRACT:

  OS2U1.EXE Supercedes OS2UTP.EXE
 This file contains updated OS/2 utilities for NetWare v3.12, NetWare v4.02 and
 NetWare v4.10 as 20 September 1995.
 The updated utilites are to be used with NetWare Client for OS/2 v2.1x.
 Also included is a OS/2 PM version of Rconsole.
 These utilities have not been submitted to Novell system test.


 -----------------------------------------------------------------
 DISCLAIMER
 THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL.  NOVELL
MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION.  HOWEVER, THE
INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY.  NOVELL
MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION.
 -----------------------------------------------------------------


ISSUE: 

PATCHES AND FIXES FOR V3.12 ONLY:

 SYMPTOM
 The following error is displayed when selecting "Directory Contents" in filer
 Description: Error returned from SplitPath ccode is 899b.
 Severity: The current operation cannot be completed.

 SOLUTION
 Apply FILER.EXE 273421 03-29-95 4:51p.

 SYMPTOM
 A problem was identified when the last PC to login, or PC with the highest
 connection slot to the NetWare server, was an OS/2 PC and a message is sent
 with the SEND.EXE utility to a group of which this OS/2 PC was a member.
 Under these circumstances the message is sent to all members of the group but
 then SEND.EXE continues to try and send the message to all the remaining
 un-used connections on the NetWare server generating an error for each un-used
 connection.  The included versions of SEND.EXE should resolve this problem.

 SOLUTION
 For OS/2 apply SEND.OS2    17790  1-06-95  5:36p
 For DOS apply SEND.DOS    34512  1-06-95  5:33p
 (Rename SEND.DOS to SEND.EXE and copy to sys:public)

 SYMPTOM
 SYSCON.EXE resolves a problem with earlier SYSCON, when creating a User home
 directory. Error:  "SetDrivePath returned error -30717".  Version 3.77 of
 Syscon will generate a SYS1811:  Trap 000d if you delete a user ID that is
 logged in.

 SOLUTION
 Apply SYSCON.EXE, 273468 bytes,  08-22-94.

 SYMPTOM
 The included version of CAPTURE.3X addresses issues of running login.exe from
 a CALL statement in the OS/2 config.sys and hanging if a #capture existed in
 the OS/2 login script.   This problem occurs with the CAPTURE.EXE that ships
 with NetWare 3.1x, including CAPTURE.EXE v3.75, dated 5-20-93, that ships with
 NetWare 3.12.

 SOLUTION
 Apply CAPTURE.EXE, 37103 bytes, 1-22-91.
 This version of capture should NOT be used with 4.X NetWare.


 PATCHES AND FIXES FOR V4.02 ONLY:

 SYMPTOM
 Error: CAPTURE-4.03-700: The mode, <MODE> of device, <DEVICE>, cannot be found
 in the PRINTDEF database.  Either specify a valid mode or create a new mode
 with the specified name. This occurs when using an NDS queue object that is
 set up to redirect a print job through the 4.x queue object to a 3.x print
 server queue. To duplicate the error you need to define and use a Device and
 Mode. This occured with capture.exe 5-05-94 that shipped with NetWare v4.02.

 SOLUTION
 Apply CAPTURE.EXE, 105149 bytes,  09-02-94 and CAPTURE.MSG, 30953 bytes,
 05-05-94. (See Installation Instructions)
 CAPTURE.EXE that ships NetWare v4.10 also resolves this issue.

 SYMPTOM
 Using CX before logging in will return the following errors:
  SYS3175: A program generated an access violation at 0001:09f5 CX.EXE.
  SYS1811: The process has stopped.
 The software diagnostic code (trap number) is 000D.

 SOLUTION
 Apply CX.EXE, 45408 bytes, 5-13-94.
 CX.EXE that ships with the v2.11 OS/2 Client Kit also resolved this issue.
 CX.EXE that ships with NetWare v4.10 also resolves this issue.
 CX.EXE that ships with the V2.12 OS/2 Client also resolves this issue

 PATCHES AND FIXES FOR v3.12 and v4.10:

 SYMPTOM
 NDIR.EXE was unable to locate files if more than 255 directories searched.
 NDIR.EXE was giving memory allocation errors when searching directories with
more
 than 200 LongFileNames. NDIR.EXE was modified to display KB's instead of Bytes
on Large 4GB volumes or Directoies

 SOLUTION
 NDIR.EXE 154448 09-07-95 9:49a
 NDIR.MSG 14761 08-07-95 11:36a

 SYMPTOM
 LOGIN.EXE did not correctly pass login environment variables to spawned
 processes.  For example, if a CMD file was called from the login script, the
 CMD file could not make use of variables that had been set in the login
 script. LOGIN.EXE 10-24-94 129904 didn't parse login scripts using  "IF MEMBER
 OF "GROUP1" THEN BEGIN" when the groups names only differed by the last
 character. After executing LOGIN.EXE the first available non local  drive
 would be mapped to SYS: ie D:=Server/sys:. This drive is now deleted  unless
 the login script maps the drive.

 SOLUTION
 Apply LOGIN.EXE 128704 6-22-95 & LOGIN.MSG 11333 9-22-94.
 This is a 4.10 utility and can be used in a 3.X enviorment to resolve this
 issue. LOGIN.MSG ships with NetWare v4.10.
 LOGIN.EXE that ships with OS/2 v2.12 Client (Intranet Ware OS/2 client)also
resolves this issue.

 SYMPTOM
 Versions of OS/2 NCOPY prior to this patch would cause extended attribute
 corruption and also would fail to release resources back to the alloc short
 term memory pool on v3.x NetWare servers. NCOPY /S from local drive to network
 dirve would not correctly create subdirectories on network drive.
 Prior versions of DOS NCOPY would fail to process extended attribute
 information correclty.

 SOLUTION
 For OS/2 apply NCOPY.EXE 74606   08-31-95.
 For DOS apply NCOPY.DOS 313464  10-19-94.
 (Rename NCOPY.DOS to NCOPY.EXE and copy to sys:public)
 For both DOS & OS/2 use NCOPY.MSG 7733   9-21-94.
 NCOPY.DOS and NCOPY.MSG ship with NetWare v4.10.
 This is a v4.10 utility and can be used in a 3.X enviorment to solve the above
 symptom.


Self-Extracting File Name: os2u1.exe

Files Included     Size     Date      Time

..\
       OS2U1.TXT     (This file)
..\312\
     CAPTURE.EXE           37103         1-22-91     11:31:10 pm
       FILER.EXE          273421         3-29-95     11:51:10 pm
        SEND.DOS           34512          1-7-95     12:33:16 am
        SEND.EXE           17790          1-7-95     12:36:54 am
      SYSCON.EXE          273468         8-22-94     10:12:54 pm
..\402\
     CAPTURE.EXE          105149          9-2-94     10:15:22 pm
     CAPTURE.MSG           30953          5-5-94     11:28:26 pm
          CX.EXE           45408         5-13-94      5:26:26 pm
..\410\
       LOGIN.EXE          128704         6-22-95     10:30:28 pm
       LOGIN.MSG           11333         9-22-94      9:59:06 pm
       NCOPY.DOS          313464        10-19-94      4:06:54 pm
       NCOPY.EXE           74608         8-31-95      7:52:46 pm
       NCOPY.MSG            7733         9-21-94      8:24:28 pm
        NDIR.EXE          154448          9-7-95      4:49:08 pm
        NDIR.MSG           14761          8-7-95      6:36:08 pm
..\REMCON\
    BTRCALLS.DLL           40674         9-20-91      8:23:26 am
       DBAPI.DLL          139477        11-18-92      5:05:52 am
     REMOCON.EXE          168464         4-14-93      3:32:12 pm
     REMOCON.HLP            2695         1-15-93      7:03:12 pm


Installation Instructions:

To Install NetWare Utilities:
 1) Make backup copies of the the current OS/2 utilities files found in the
 PUBLIC\OS2 or LOGIN\OS2 directories on your system.
 2) Then copy the OS/2 utilities found in 312, 402 or 410 to the respective
PUBLIC\OS2
  LOGIN\OS2 directories on your system.
 3) On 3.12 servers put *.MSG files in the same directroies  as the utilitiy.
On 4.x
 Servers put the *.MSG files in PUBLIC\NLS\ENGLISH Directory
 TO INSTALL REMOCON:
 Copy the following files to a local or network directory:
 REMOCON.EXE
 REMOCON.HLP
 DBAPI.DLL
 BTRCALLS.DLL
 REMOCON.EXE can be executed from an OS/2 command line  the DLL's
 must be in the current directory or found in the LIBPATH. REMOCON.EXE
 can also be launched from  an OS/2 Icon.
 Use the following information when Creating an OS/2 Icon.
      Path =      <path>\REMOCON.EXE
      Parameters =    <none>
      Working Dir  =  <path>



 -----------------------------------------------------------------
 Any trademarks referenced in this document are the property of their
respective owners.  Consult your product manuals for complete trademark
information.
 -----------------------------------------------------------------

[ RETURN TO DIRECTORY ]