Subject:  TIDB Updates  
Date:  3-Feb-89   
   
PROBLEM 1:  When a customer reinstalls or re-runs (for the second
time) the UPDATE.BAT for the TIDB updates he will have problems. 
He will get "access denied", "file creation errors" and an error in   
the TWINDEX part of the process.  This is because the customer has
not read the README file and followed the instructions.   
   
SOLUTION 1:  When the customer has to re-run the UPDATE1.BAT 
file to reinstall the updates, the README file says to delete the   
directories and that is correct.  If the customer does not do this   
he will get more errors when running the update again.  He must   
follow the instructions to delete the directories.  Delete only the   
new ones created in that update.   
   
PROBLEM  2:   While installing the updates to the TIDB to a   
standalone hard disk drive, we get the error "bad command or   
filename".   
   
SOLUTION 2:  This error occurs because of the flag command in   
the batch file for the network version.  The network version flags  
files back and forth between "sro" and "srw".  On the standalone   
version there is no need to worry.   
Subject:  Shell Errors  
Date:  2-Feb-89   
   
OS VERSION:  2.12 and 2.15    
SHELL VERSION:  Shells included in 2.12 and 2.15    
    
PROBLEM:  While loading the shell we get the message "No free   
connection slots available."    
    
There hasn't been enough data gathered at this time but it looks   
like this may be happening more often with file servers that are   
running on unapproved VADDS, particularly Core's 300MB drives.    
We don't believe it has been seen with any approved disk drivers.   

The problem is that the server runs out of service processes.    
We discovered this purely by accident 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.     
   
SOLUTION  :  The only solution is to cut back the size and/or   
number of drivers linked into the O.S.  The only other variables   
that are used in this 64K block (Dynamic Memory 1 in PConsole) are
for workstation mappings so you can reduce the number of   
workstations that are connected to the file server, or reduce the   
number of drive mappings that each workstation is using.    
