Subject:  User Validation Error . . . . . . . . . . . . 
Date:  7-Feb-89 . . . . . . . . . . . . . . . . . . . . 
 
 
GENERAL INFORMATION:  This is an explanation of a potential 
problem with Netware for VMS, concerning the "Guest user profile 
validation error "RMS-E-FNF. File not found."  If any user should 
experience this error, please follow the suggested solution.  
This is a temporary work-around.  The fix has been incorporated in 
the Netware for VMS 2.01 r1.09, which is scheduled for shipment to 
Novell later this week.  
  
PROBLEM:  We have discovered a problem with the installation     
procedure for Netware for VMS, versions 1.08 and older.  The 
problem is manifested once the installation has been completed and a
user attempts to bring up Netware for VMS.  Upon beginning the 
Netware for VMS file server process, the user may encounter the 
following error, "Class 1 {date/time} Guest user profile validation 
error.  RMS-E-FNF.  File not found."  
  
EXPLANATION:  On the VAX/VMS side there is a file that may or 
may not be on your system called the RIGHTSLIST.DAT file.  This 
is NOT a mandatory file for VMS, however it is necessary for 
running Netware for VMS.  If the file did not exist at the time of 
the Netware for VMS installation, the process continues on as if 
everything is ok.  This RIGHTSLIST.DAT file needs information 
appended to it in order for Netware for VMS to function.  Because
the file did not exist, the information could not be appended and 
therefore Netware for VMS is operational and the above error 
occurs.  
  
SOLUTION:   If a user should encounter this problem, please follow
the steps below:  
  
        A)  Using the AUTHORIZE utility, run Sys$System:Authorize 
           1)   Use the "Create/Rights" command to create the 
                RIGHTSLIST.DAT.  
  
                        UAF> Create/Rights  

           2)  Add information to the newly created              
               RIGHTSLIST.DAT file.  The correct syntax is:  
  
                 UAF> Add/id  ITNS$_access/value=id:%xFDAC200  
  
Once this information has been added to the RIGHTSLIST.DAT file, 
the user will be able to login to the Netware for VMS server 
without any further problems.  
Subject: Invalid Drive Passed to Disk Process . . . . .   
Date:  7-Feb-89   . . . . . . . . . . . . . . . . . . .   
   
   
OS VERSION:         2.12 and 2.15    
REVISION:           All    
SHELL VERSION:      All    
    
FYI:                An "Invalid Drive Passed to Disk Process"  
                    error was reported on a PS/2 model 70 with a  
                    60MB ESDI drive.  To resolve this  problem,   
                    there is another ESDI.OBJ driver.  By renaming 
                    the old ESDI.OBJ on the dsk_drv_.001 disk,    
                    copying the new one, and regenerating the OS, 
                    the problem was solved.  The size of the       
                    ESDI.OBJ is 5213 bytes, and it is dated        
                    01/09/89.   This problem has only occurred on  
                    the 60MB drive so far.   
 
Subject:  ADIC 740B, 740B-2, 740B-DP Subsystems . . . .    
          (330 MB Priam drives) . . . . . . . . . . . .    
Date:  February 16, 1989  . . . . . . . . . . . . . . .     
     
OS VERSION:           v2.15 (not exclusively)     
              
GENERAL INFORMATION:  ABEND:  Adding Generic SCSI Driver    
                      during NETGEN when selecting "Installation" 
                      from the NETGEN menu.     
     
PROBLEM:              ADIC's subsystems should have the 
                      terminating resistors installed on the back of 
                      the machine in order to be properly          
                      terminated.  However, when the terminating  
                      resisters were installed, we could not get    
                      the drives to install.     
     
SOLUTION:             We removed the terminating resistors from  
                      the back of the machine and the installation 
                      went forward without any problems.  ADIC   
                      does not recommend running in this way,     
                      however, because it could short out the      
                      drives.  ADIC discovered that PIN 38 on the 
                      50 pin side of the 37-50 pin cable was       
                      shorting out the resistors.  They have stated 
                      that all of their cables will be reworked from 
                      this time forward but cables can be purchased 
                      from other sources which could have the same 
                      problem.     
    
COMMENTS:             If someone needs to rework their cable    
                      themselves, ADIC did caution that PIN 38    
                      should be cut back as far as possible to avoid 
                      any possibility of shorting out again.  
 
Subject:  NP600, NP600A-3 . . . . . . . . . . . . . . .   
Date:  2/23/89  . . . . . . . . . . . . . . . . . . . .   
    
OS VERSION:         n/a    
REVISION:           XB, AC, AF    
SHELL VERSION:      n/a    
    
FYI:                Our Engineering Department has tested some   
                    NP600A-3 boards:   
 
                    Rev XB (part number 625-0601-00),  
                    Rev AC (part number 625-0060-00),  
                    Rev AF (part number 626-0505-01) 
 
                    Even though they are down revision boards     
                    there is no reason for concern on anyone's     
                    part.  If you are working with a customer with 
                    one of these boards who is concerned about    
                    them, you can assure them that the boards     
                    have been tested.  
 
Subject: Creating RIGHTS using GROUP . . . . . . . . .   
Date:  2/23/88 . . . . . . . . . . . . . . . . . . . .   
    
OS VERSION:         2.1x    
    
   
PROBLEM:            Using the group option to grant rights does  
                    not work.  The rights granted are incorrect.   

    
SOLUTION:           There is no solution. 
 
Subject:  Protected-mode Bridge . . . . . . . . . . . .   
Date:  2/23/89  . . . . . . . . . . . . . . . . . . . .   
    
OS VERSION:           v2.15    
    
   
GENERAL INFORMATION:  NetWare v2.15 contains what is          
                      commonly referred to as the protected-mode  
                      bridge.  In the past, only the real-mode      
                      bridge has been included with the OS release. 
                      Following is an explaination of the
difference                        between the two types of bridges. 
  
    
                      The real-mode bridge is the same bridging    
                      product that Novell has shipped since release 
                      2.0a.  It is based on 8086 technology and will 
                      only support 640K of memory.  All programs  
                      on the machine (i.e. DOS, the bridge,        
                      application programs) had to fit in this 640K 
                      limitation.  If the user needed to have more 
                      accessible memory on that machine, they 
                      were simply out of luck.  This was acceptable 
                      to most users who simply made the bridge a 
                      dedicated machine and did not use it as a 
                      DOS workstation.  This worked fine for most 
                      users, however, with the advent of VAPs and 
                      the potential to run them on the bridge 
                      rather than the file server, 640K was no 
                      longer enough memory even if the bridge 
                      was run in a dedicated mode.  This required 
                      the development and release of a bridging 
                      product that would take advantage of 
                      memory above the 640K limitation.  Memory  
                      above the 1MB area is often referred to as 
                      protected-mode.    
    
                      The protected-mode bridge is similar to the 
                      technology that was introduced with the 
                      release of Non-dedicated 286 v2.0a.  The   
                      protected-mode bridge runs in the memory 
                      between 1MB and 16MB.   This creates 
                      several advantages for the user.  Users can 
                      now run VAPs on a bridge that require large 
                      amounts of server memory.  A good example  
                      of this is the six to eight Macintosh VAPs.   
                      These VAPs have to be split across two      
                      separate bridges when they are run in       
                      real-mode.  Under protected-mode they can  
                      all be run on one bridge with memory to     
                      spare.  The fact that all the bridge and    
                      VAP code is running above 1MB also makes it 
                      advantageous to use the bridge in a          
                      non-dedicated mode.  Less than 32K of the   
                      lower 640K is required for the bridge.  The  
                      current BRGEN procedure requires the user   
                      to choose the type of bridge he wants early  
                      in the generation process.  The real-mode    
                      bridge can be run in either a dedicated or   
                      non-dedicated mode.  The protected-mode    
                      bridge can only be run in a non-dedicated    
                      mode.    
    
                      The protected-mode bridge should run with all 
                      versions of NetWare v2.0a and higher similar 
                      to the way that the 2.1 bridge interfaced   
                      with version 2.0a.   
 
Subject:  Session bug . . . . . . . . . . . . . . . . .   
Date:  2/23/89  . . . . . . . . . . . . . . . . . . . .   
    
OS VERSION:         2.12 and above   
    
PROBLEM:            When using the SESSION utility, by accessing 
                    the search path menu, all existing search paths 
                    are changed to forward slashes including those 
                    for the c: drive.  After exiting, the c:/ root   
                    directory fails in subsequent searches.  All     
                    other paths seem to work fine, eg. c:/dos or   
                    c:/util.    
    
SOLUTION:           There is no solution. 
 
Subject:  68 tape backup software . . . . . . . . . . .   
Date:  2/15/89  . . . . . . . . . . . . . . . . . . . .    
    
OS VERSION:           68    
REVISION:             2.01 and above    
   
    
GENERAL INFORMATION:  There appears to be a problem with the 
                      tape backup software version 2.0 for 68b. 
    
PROBLEM:              The back-up software seems to work fine.  
                      When restoring, users get errors such as;     
                      "files cirularly linked," "files multiply        
                      linked." or "files link to zero," all of which  
                      indicate a bad tape.  The problem is actually 
                      in the software.    
    
SOLUTION:             Have the users download RES20A.ARC in the 
                      private area of NetWire.  Once they get this, 
                      if they try to restore to a volume larger     
                      than 128MB they will get an error indicating 
                      the drive is bad.  Have them do a directory  
                      restore instead of volume restore, and        
                      restore less than the 128MB limit.  The fix   
                      for the 128MB limit is in beta test.   
 
Subject:   Checksum error in load file . . . . . . . .  
Date:   2/23/89  . . . . . . . . . . . . . . . . . . . 
  
OS VERSION:           2.15  
  
 
PROBLEM:              VADD developers and their customers may  
                      complain about the error "checksum error  
                      in load file".  There is a fix which 
                      must be done by the VADD developer, not the 
                      END-USER!  
  
SOLUTION:             In their disk driver at the end of the Data 
                      Segment, have the VADD Developer insert the 
                      EVEN directive.  This must be done through  
                      the assembler.  
  
  Subject:  NetWare Control Center . . . . . . . . . .  
Date:  February 27, 1989 
 
THIS INFORMATION HAS NOT BEEN VERIFIED BY NOVELL 
 
OS VERSION:            2.15 
REVISION:              A 
SHELL VERSION:         N/A or AppleShare v2.01 
 
GENERAL INFORMATION:   Running NetWare Control Center on the 
                       Mac SE and II.
 
PROBLEM:               A problem has been reported with the     
                       NetWare Control Center (NCC).  NNC cannot 
                       find NetWare file servers if they are located 
                       on a different zone than that of the        
                       Macintosh.   
 
SOLUTION:              If the fileserver is on the same zone then 
                       there is no problem. 
 
 
FYI # 030389jl 
 
Subject:  ABEND: No Transaction Node found FT Set Transaction   
Date:  2/23/89 . . . . . . . . . . . . . . . . . . . .   
   
THIS INFORMATION IS NOT VERIFIED BY NOVELL  
  
  
OS VERSION:            2.15 SFT w/TTS   
   
  
GENERAL INFORMATION:   The error ABEND: No Transaction Node 
                       found has occurred after users backup  
                       binderies with certain tape backup units.   
   
PROBLEM:               The problem isn't really understood at this 
                       time, but it seems to be linked to the fact  
                       that the binderies were locked, and when   
                       the binderies are released, Set Transaction is 
                       called.  Apparently it notices that some     
                       bindery objects need to be deleted or       
                       changed at that time.  At that point the    
                       server will ABEND.  
   
SOLUTION:              At this time the only workaround is to    
                       have the customer backup the binderies when 
                       there is minimal usage on the network, or   
                       only backup datafiles if they must do this   
                       during heavy usage times.   
   
                       Another workaround might be to disable     
                       TTS.  
 
Subject:  Shell errors . . . . . . . . . . . . . . . .   
Date:  Feb. 2, 1989  . . . . . . . . . . . . . . . . .   
   
OS VERSION:  2.12 and 2.15   
SHELL VERSION:  Shells included in 2.12 and 2.15   
   
  
PROBLEM:               When we load the shell we get the        
                       message "No free connection slots available." 
                       There hasn't been enough data gathered but 
                       it looks like this error may be occurring    
                       most often with file servers that are        
                       running unapproved VADDS, particularly     
                       Core's 300MB drives.  We don't believe we  
                       have seen it happen with any approved disk 
                       drivers.   
   
                       The problem is that the server runs out of  
                       service processes.  We discovered this after 
                       having users type CONFIG at the file       
                       server console and noting that there were 0 
                       service processes.  There is only one 64K   
                       block that holds all the variables used to   
                       run processes.   The server allocates a      
                       maximum of ten processes that share CPU   
                       time.  Any process dealing with server      
                       functions (LAN drivers, VADDS, and other  
                       drivers) are allocated first and leftover    
                       processes are used for workstation requests. 
                       This error occurs because the server        
                       doesn't report that it has run out of        
                       service processes.  We suggest that any     
                       customer receiving this error message should 
                       display an Abend error.   
    
SOLUTION:               The only solution is to cut back the size 
                        and/or number of drivers that the user has 
                        linked into the OS.  The only other        
                        variables that are used in this 64K block   
                        (Dynamic Memory 1 in Pconsole) are for   
                        workstation mappings so the user can  
                        reduce the number of workstations that are 
                        connected to the file server.   
 
