Subject:  Increasing Number of Sessions with NetBIOS .  
          (A Revision of the FYI Sent out Earlier on NetBios) 
Date:   March 7, 1989  . . . . . . . . . . . . . . . .  
 
  
OS VERSION:           All  
SHELL VERSION:        All  
  
GENERAL INFORMATION:  There needs to be some clarification on 
                      how to increase the number of sessions with 
                      NetBIOS.  Two things must be done to       
                      increase the number of sessions.  First, the  
                      SHELL.CFG file must be amended to include  
                      NETBIOS SESSIONS = X (where x is the 
                      number of sessions desired).  Then a  
                      software reset must be done.  Since most 
                      application programs do not do this reset, 
                      the user will have to do for themselves.  
                      Setting the number of sessions in the 
                      SHELL.CFG file is not enough.  
  
PROBLEM:              Most users do not know how to do the 
                      software reset.  
  
TEMPORARY SOLUTION:   For now, the user should be able to 
                      increase the number of sessions by doing the 
                      following:  
                 
                      1.  Use 2.15 shell.  
                      2.  Use 2.15 NetBIOS.  
                      3.  Use a program called NET to do the      
                          software reset 
 
                       The files mentioned above along with a     
                       README file containing instructions on     
                       how to accomplish the reset are on  
                       NetWire under BIOS.ARC.  
  
                       To use NET, at each station do the         
                       following:  
 
                       1.  Make sure that the SHELL.CFG file, the 
                           NETBIOS file, and the NET file are in  
                           the same directory or that they  
                           have search drives mapped to them.  
 
                       2.  Make sure that the SHELL.CFG for each 
                           station that will be using NetBIOS      
                           commands contains  
                           NETBIOS SESSIONS = X.  
 
                       3.  Use a 2.15 shell to boot each 
                           workstation that will be using NetBIOS. 
 
                       4.  Login.  
 
                       5.  Type NETBIOS<CR> to activate the      
                           NetBIOS emulator.  
 
                       6.  Type NET<CR> to execute NET.  
  
                       7.  Type RESET<CR>.  
 
                       8.  When the prompt appears, enter the     
                           number of sessions you want to have.   
                           This number should not be larger  
                           than the number specified in the        
                           SHELL.CFG file.  
 
                       9.  The next prompt is for command blocks. 
                           Enter the number you want.  This      
                           number could be the same as for the  
                           number of sessions.  
 
                       10. When the : prompt appears, the software 
                          reset has been done.  Type an E<CR> to 
                          return to DOS prompt.  
  
PERMANENT SOLUTION:    A new release of our NetBIOS is being 
                       developed.  When this version is released,   
                       the user will only need to include  
                       NETBIOS SESSIONS = X in the SHELL.CFG  
                       file.  The user will not have to do a        
                       software reset.  
 
Subject:   Novell UPS Monitoring only SS Keycard . . .  
Date:   March 3, 1989  . . . . . . . . . . . . . . . . 
  
 
OS VERSION:           SFT V2.15  
REVISION:             Part # 810-000139-003 Rev. D  
                      (please note the -003 end number.  This  
                      part number is the same as the regular  
                      SS keycard except the last three digits.)  
  
  
GENERAL INFORMATION:  Novell Engineering has approved a       
                      MODIFIED SS Keycard for use as a UPS     
                      monitoring device.  The modifications have  
                      completely and permanently disabled the      
                      keycard portion of the unit.  Listed below is 
                      a brief summary of the tests performed:  
  
                      Supporting Hardware:     
                      386A as a server,  
                      386AE as a workstation                      

                      Novell DCB, P/N 810-162-101, rev. A (with 
                      serial number hardware and a UPS monitoring 
                      port)  
                      Novell Keycard, P/N 810-000061-001, rev. B  
                      American Power Conversion 1200 VX UPS  
                      American Power Conversion UPS monitoring 
                      cable  
  
  
                      1.   This card performed correctly at both 
                           the primary (230h) and secondary       
                           addresses (238h.)  A broadcast message  
                           regarding loss of power was sent to the 
                           workstation at the proper time.         
                           Restoration of AC power within the     
                           delay period was sensed and handled  
                           correctly by the SFT software.  
 
                      2.   The serial number portion of the board  
                           appeared to be completely disabled and  
                           did not conflict with any of the other  
                           serial number devices listed under       
                           Supporting Hardware above.  
  
                      3.   The contents of the SERVER.CFG file   
                           used in testing this board with SFT     
                           NetWare v2.15 were:  
  
                           tts wait=10  
                           vap wait=10  
                           ups t=3  
                           ups io=230    (238 when the 
                                         alternate port was  
                                         tested)  
                           ups d=2  
                           ups w=15  
  
  
 
FYI # 030389gn  
 Subject:  NACS and Login Scripts . . . . . . . . . . . 
Date:  March 2, 1989 . . . . . . . . . . . . . . . . . 
 
THIS INFORMATION HAS NOT BEEN VERIFIED BY NOVELL. 
 
 
GENERAL INFORMATION:   Running Netware 2.12, using PDI Arcnet 
                       with a NACS server, we did an if..then      
                       statement in the system login script to allow 
                       us to exit to a batch file if a certain user  
                       logged into the network.  This was the    
                       method we used to start the NACS gateway. 
                       This would mean that if there was a        
                       problem, a user would just log on to the    
                       network through a certain machine, using a 
                       certain account, and the gateway would  
                       fire up. 
 
PROBLEM:               When the above described method was used 
                       we got the following error: 
 
                       OEM Error 
                       Contact your distributor 
 
                       If we typed the same information in the    
                       batch file at the command line, everything  
                       worked fine.  If we executed the same batch 
                       file at the command line, again everything  
                       worked. 
 
SOLUTION:              We thought it might be a timing problem. 
                       We used the if..then exit command in the 
                       system login script to call a batch file called 
                       GATEST.BAT, which in turn called the      
                       GATE.BAT file that actually started the     
                       gateway. 
 
                       The OEM error indicates that the software 
                       could not find the PAL that is specific to   
                       Novell. 
 
 
 
FYI # 030289 
 
Subject:  Dbase IV . . . . . . . . . . . . . . . . . 
Date:  March 8, 1989 . . . . . . . . . . . . . . . . 
 
THIS INFORMATION HAS NOT BEEN VERIFIED BY NOVELL 
 
 
OS VERSION:          2.0a, 2.1x 
 
PROBLEM:             Dbase IV apparently has a direct conflict 
                     with any network interface card using IRQ 3. 
                     Most Ethernet cards are set to IRQ3 by       
                     default, presenting a problem to 2.0a users who 
                     have only the one shell option.  2.1x users    
                     just need to know there is a conflict and to  
                     reconfigure IPX. 
 
SOLUTION:            In 2.0a, a user can either call Lanswer 
                     for a preconfigured IRQ 2,4,5 etc. or access  
                     the private area on NetWire.  They could also 
                     rename, for instance, a 2.1x ETHSH.OBJ to the 
                     2.0a format of SHELLDRV.OBJ, copy it to the 
                     appropriate subdirectory on the GENSH-1      
                     diskette, generate the shell and then use      
                     DCONFIG.EXE (from the 2.1x AUXGEN        
                     diskette) to configure for a different option. 
 
 
FYI # 030889an 
 Subject:  No Disk Process available with 2 Gigabytes  
Date:   March 2, 1989 . . . . . . . . . . . . . . . . 
 
OS VERSION:            2.15 
SHELL VERSION:         2.15 
 
GENERAL INFORMATION:   Several people have reported that after 
                       they get above 1.2 to 2.0 gigabytes they run 
                       out of server processes.  It appeared that   
                       the operating system may no longer be able 
                       to handle that much disk capacity.          
                       Engineering set up an SFT 2.15 file server  
                       with 2 Gigabytes, and successfully booted it 
                       up.  They had one server process left.  They 
                       weren't able to do much before it had no   
                       server processes left.  There were 13  
                       users logged into it, and each could only    
                       have about four logical drives defined. 
 
                       The system was configured with four (4) 
                       DCB's and two (2) internal disk drives 
                       making two disk drivers linked in, and 
                       it had one (1) interface card linked in. 
                       The card used was a PS110 board. 
 
PROBLEM:               Some of the parameters are not set       
.                      properly for the large amount of disk       
                       capacity, therefore the file server will run  
                       out of disk processes. 
 
SOLUTION:              During the disk installation process it was 
                       necessary to NOT CACHE the disk drive.    
                       Also, when it asks for the number of       
                       directories, it was necessary to put it at    
                       512, the lowest setting. 
 
 
FYI # 030289gn 
 
Subject:  NSNIPES . . . . . . . . . . . . . . . . . .  
Date: March 7, 1989 . . . . . . . . . . . . . . . . . 
 
OS VERSION:          All versions 
 
PROBLEM:             When attempting to play the game NSNIPES, 
                     it returns the message "I'm too late to  
                     play this game", even when playing alone. 
 
SOLUTION:            NSNIPES only recognizes the first 24 
                     connections.  You must be one of these first 
                     24 connections to play. 
 
COMMENTS:            Believe it or not, this was a "technical" 
                     question that a customer called us twice on. 
 
 
 
FYI # 030789mr 
 Subject:  System Messages Manual . . . . . . . . . . . 
Date:  March 7, 1989 . . . . . . . . . . . . . . . . . 
 
 
GENERAL INFORMATION:   Customers who want to order System   
                       Messages Manuals can call 1-800-453-1267   
                       and ask for Jan Levie (pronounced like the  
                       501 jean). 
 
 
FYI # 030789-2mr 
 SUBJECT:  Token Ring Shell Disables COM1 and COM2.  
          Token Ring Shell conflicts with model 30 and  
          PC/XT hard disks . . . . . . . . . . . . . .  
 DATE:    March 9, 1989  . . . . . . . . . . . . . . . 
  
OS VERSION:         2.11  
SHELL VERSION:      2.11  
  
PROBLEM:            The 2.11 Token Ring Shell conflicts with     
                    the model 30 hard disk drive, and with most   
                    PC/XT compatibles' hard disk drives.  
                    A second problem that exists with the 2.11     
                    Token Ring shell is that it disables COM1 and  
                    COM2 for use as a local device on workstations. 
 
SOLUTION:           It isn't known whether this is resolved in    
                    the 2.12 release.  However, the 2.15 release    
                    resolves both of these issues.  The Token Ring 
                    Driver dated 12/16/88 and any drivers released 
                    after that date will not have the problems     
                    listed above. 
SUBJECT:  Volume Overrun Disk Error . . . . . . . . . . 
DATE:     03/09/89  . . . . . . . . . . . . . . . . . . 
  
 
THIS INFORMATION HAS NOT BEEN VERIFIED BY NOVELL 
 
 
OS VERSION:           2.1x  
REVISION:             ALL 
  
GENERAL INFORMATION:  Vrepair returns a "Volume overflow disk" 
                      error on some external subsystem units.      
                      Internal drives don't seem to have the same  
                      problem.  
  
PROBLEM:              Vrepair must look at these drives a little  
                      differently than the NetWare OS does,       
                      because the OS has no problem mounting the 
                      drive.  The subsystem having this particular  
                      problem was ADIC's 740-A which comes with 
                      two Priam 336 mg drives running off of      
                      Novell DCB's.  
  
SOLUTION:             The drives will usually continue to mount  
                      and function properly.  If the disk problem   
                      becomes too bad...COMPSURF.  
  
COMMENTS:             Novell approved VADDs do not have this  
                      problem.  
  
 
FYI # 030989an-a 
SUBJECT:  Gateway Ethernet Drivers  . . . . . . . . . . 
DATE:     03/13/89  . . . . . . . . . . . . . . . . . . 
  
 
THIS INFORMATION HAS NOT BEEN VERIFIED BY NOVELL 
 
 
OS VERSION:         2.1x  
 
  
PROBLEM:            Users using Gateway's Ethernet series have   
                    been experiencing hang-ups, lock-ups at        
                    workstations and at the file server.  
 
SOLUTION:           Gateway has released new drivers and this has 
                    already solved two of the problems that we've  
                    been working on.  These drivers have been     
                    tested and approved by Novell. 
  
FYI # 031389va 
SUBJECT:  Print Symbiont Problem w/NW for VMS . . . . . 
DATE:     3/17/89 . . . . . . . . . . . . . . . . . . .  
 
 
GENERAL INFORMATION:  Under the VMS, operating system, print 
                      jobs are handled by so-called "print          
                      symbionts" which send a print job to the     
                      actual printer device.  InterConnections      
                      connectivity products use the VMS print     
                      symbionts indirectly by submitting any print  
                      jobs sent by remote systems (ie. PC          
                      workstations) to the VMS Queue Manager,    
                      which in turn uses a print symbiont to print 
                      the job.  
 
PROBLEM:              The default VMS print symbiont cannot     
                      handle files with records exceeding 32K.      
                      Files sizes greater than 32K are a common   
                      occurrence with print jobs generated by      
                      workstations using CAD/CAE systems,        
                      spreadsheet graphics and desktop publishing.  
                      The problem manifests itself by displaying    
                      garbage characters in an output plot file or  
                      graph.  Users may also encounter the        
                      following error message when experiencing   
                      the print symbiont problem:  
 
                        "%PSM-E-READERR, error                 
                         reading_UV3$DUA1:[IDG]S$011E494.LIS;  
                         2-RMS-W-RTB,37405 byte record too large 
                         for user's buffer."  
  
  
SOLUTION:             To address this problem, InterConnections  
                      has developed a modified VMS print symbiont 
                      which is capable of printing in true binary   
                      mode, eliminating all VMS specific record    
                      processing problems.  
  
                      The executable code for the InterConnections 
                      print symbiont (IC-PSM) is included on the   
                      NetWare for VMS v2.01 distribution tape.     
                      When NetWare for VMS v2.01 is installed, the 
                      print symbiont program is automatically      
                      placed in the SYS$SYSTEM: directory.  
  
                      In order to direct an execution print queue to 
                      use the IC-PSM symbiont instead of the      
                      system's default PRTSMB symbiont, simply  
                      add the /PROCESSOR=IC-PSM option to the  
                      INITIALIZE/QUEUE or the START/QUEUE    
                      command of the print queue of interest.  
  
  
NOTE:                 If you require further information, please    
                      contact InterConnection's Customer Support  
                      Department @ 206-881-5773.  
 
  
  
FYI # 031489mm  
SUBJECT:  DBASE III+ . . . . . . . . . . . . . . . . .  
DATE:     03/17/89   . . . . . . . . . . . . . . . . . 
  
 
THIS INFORMATION HAS NOT BEEN VERIFIED BY NOVELL 
 
OS VERSION:           2.1x, maybe 2.0a  
  
GENERAL INFORMATION:  A user had an internet of 5 Compaq     
                      servers running SFT 2.12, using 3COM 3c505's 
                      in the server and NE1000's in the            
                      workstations.  The only intensive            
                      applications work they did involved DBASE   
                      III+.  
  
PROBLEM:              All five servers would intermittently lock  
                      up, displaying no messages or clues as to     
                      why.  
  
SOLUTION:             After interviewing all of his network users, 
                      the client discovered one particular user     
                      loading the stand-alone version of DBIII+ and 
                      using capture to direct his printer output to 
                      the network printers.  This user was attached 
                      to all of the servers and as soon as his print 
                      job was through, all five of his servers      
                      locked up.  As soon as this user quit  
                      loading the stand-alone version the problem  
                      disappeared. 
  
COMMENTS:             The moral of this story is this....when  
                      diagnosing the strange and unknown, bring   
                      the network configuration back to its original 
                      unadulterated state, using 1 or 2             
                      workstations, then start adding the rest of   
                      the hardware (cables, hubs, repeaters etc.)   
                      and software (applications) one at a time    
                      until you can recreate and pinpoint the     
                      problem.     
 
  
FYI # 031789an 
SUBJECT:  SMC PC500 . . . . . . . . . . . . . . . . . . 
DATE:     03/17/89  . . . . . . . . . . . . . . . . . . 
  
 
THIS INFORMATION HAS NOT BEEN VERIFIED BY NOVELL 
 
OS VERSION:           2.1x  
  
GENERAL INFORMATION:  SMC has a new board out. 
  
PROBLEM:              The documentation for this new board tells 
                      how to correctly set up the board.  However, 
                      the illustration is incorrect.  
 
SOLUTION:             Read the documentation and don't look at  
                      the pictures.  
  
  
FYI # 031789an1 
SUBJECT:  Printing with Pconsole v1.02a and v1.02b . .  
DATE:     March 17, 1989 . . . . . . . . . . . . . . . 
  
  
GENERAL INFORMATION:  When trying to print from a local drive 
                      using Pconsole v1.02a and v1.02b, if you are  
                      not in the root directory, a DOS error code 3 
                      will appear:  "specified directory was not     
                      found".
  
  
PROBLEM:              For instance, if a user's local drive is at  
                      c:\dos\data, the user would go into Pconsole, 
                      print queue information, and try to insert a  
                      job using the insert choice to choose the    
                      drive path to a sub-directory to print a file. 
                      Then after choosing the print job            
                      configuration and saving, the error screen  
                      appears: " DOSOpen returned an error code  
                      of 3. Description: an attempt to open the  
                      file failed because the specified directory was 
                      not found."  After escaping to continue, the  
                      job is entered into the queue with a never   
                      ending status of adding.  The file created in 
                      the queue is very small.  Pconsole will path  
                      to the sub-directory; however, if c: is left at 
                      the root it will work properly.  
  
SOLUTION:             Leave c: at the root level.  
  
 
FYI # 031789sb 
SUBJECT:  WordPerfect 5.0 and DiskError 88 . . . . . .  
DATE:   March 15, 1989 . . . . . . . . . . . . . . . 
  
  
GENERAL INFORMATION:  WordPerfect has renamed their "Diskerror 
                      88" error message to "Network Device Fault" 
                      in WP 5.0 only.  This change was effective as 
                      of the version dated 1/3/89. This change is   
                      described in the publication "The            
                      WordPerfectionist" Vol. 3 No. 5 in an article 
                      entitled "WP 5.0 Fixes and Changes."  WP 4.2 
                      has not renamed its error message and will  
                      still show the error as "Diskerror 88".  
  
  
COMMENTS:             This is NOT a fix to the problem of       
                      receiving a diskerror 88.  It is simply a  
                      renaming of an error message.  
  
 
  
FYI # 032089dl  
SUBJECT:  HotServer v1.2 causing workstations to hard hang 
DATE:     March 14, 1989 . . . . . . . . . . . . . . .  
  
 
THIS INFORMATION HAS NOT BEEN VERIFIED BY NOVELL 
 
OS VERSION:           SFT 2.12  
SHELL VERSION:        2.12b  
  
GENERAL INFORMATION:  HotServer is a $69.00 software package  
                      which allows users to share a workstation's  
                      local printer (peer-to-peer printing).  It is   
                      similar to LanSpool.  HotServer has been     
                      renamed to Printer Assist.  
  
PROBLEM:              On a ProNet-4 network or a Token Ring   
                      network, if HotServer as installed, a  
                      workstation could hang (requiring a cold  
                      boot) when running various applications.  
                      Most noticeably this occurred when  
                      running MS Word v4.0.  
 
SOLUTION:             Upgrade to Printer Assist v2.2 (formerly    
                      called HotServer).  
  
 
  
FYI # 032089dl1 
SUBJECT:  Patch for Adaptec 23XX . . . . . . . . . . .  
Date:     03/13/89 . . . . . . . . . . . . . . . . . .  
  
 
THIS INFORMATION HAS NOT BEEN VERIFIED BY NOVELL 
 
OS VERSION:           2.1x  
  
GENERAL INFORMATION:  In the TIDB there is a patch which     
                      allegedly allows 2.1x to run with the Adaptec 
                      23XX controllers. The patch is a number of  
                      changes done with DEBUG to the ATDISK.OBJ 
                      file from DSK_DRV_.001 as well as          
                      instructions on how to run some firmware on 
                      the controller from DEBUG.  
  
PROBLEM:              Unfortunately, it does not work on the 2.15 
                      ATDISK.OBJ, because the pattern you have to 
                      search for to make the patch is not found.  

SOLUTION:             We succeeded using an earlier ATDISK.OBJ, 
                      and linked it to a 2.15 COMPSURF.  
 
 
FYI # 031389rr 
SUBJECT:   Incompatibility between 3C523 & Model 80  .  
DATE:      March 15 1989 . . . . . . . . . . . . . . . 
 
OS VERSION    :2.12 Advanced  
SHELL VERSION :2.12  
  
THIS IS UNVERIFIED INFORMATION.  USE IT FOR 
TROUBLESHOOTING PURPOSES ONLY.  
  
PROBLEM:            20MHz Model 80 servers (ie 80-111 & 80-311) 
                    fitted with 3Com 3C523 MCA boards           
                    consistantly lock up after 5 to 10 minutes if   
                    run at high utilisation for instance 90%.  No  
                    Abend message, beeps, or disk leds occur.      
                    The keyboard is frozen.  Several Model 80s,    
                    cards and options were tried, with no          
                    improvement.  This problem doesn't occur with 
                    Western Digital MCA Ethernet boards.  The    
                    servers involved with this problem have 8MB of 
                    RAM.  
  
SOLUTION:           There is no known solution yet. 
  
 
FYI # 032089pr  
SUBJECT:  MAC VAPS and Kinetics Card . . . . . . . . .  
DATE:     3-21-89  . . . . . . . . . . . . . . . . . . 
  
 
THIS INFORMATION HAS NOT BEEN VERIFIED BY NOVELL 
 
OS VERSION:           2.15  
 
GENERAL INFORMATION:  Using MAC IIx and MAC IIcx  
  
PROBLEM:              When the VAPS are loaded onto a MAC IIx 
                      or MAC IIcx, several lines of data should    
                      appear.  If these lines of data, which are    
                      about the copyright don't appear, this means 
                      that the server or bridge ran out of memory 
                      to load the VAPS.   This can occur because  
                      the VAPS don't check to see if there is      
                      enough memory for themselves to load.  
 
PROBLEM:              MAC IIx and MAC IIcx need to use a      
                      system with v6.03.
  
SOLUTION:             For kinetics boards the setting should be   
                      cnet == thin-net-port.   
                      For Ethernet cards the setting should be     
                      enet == trans-receiver  
  
 
 
Fyi # 032189kr  
SUBJECT:  COORDINATOR I and II . . . . . . . . . . . .  
DATE:     3/24/1989  . . . . . . . . . . . . . . . . .  
  
PROBLEM:            Coordinator I users can't "answer" a         
                    communication sent from someone using  
                    Coordinator II because the 1st package doesn't 
                    recognize the full name listed in Coordinator II. 

SOLUTION:           Those using Coordinator II need to set "full  
                    addressing off" to alleviate this problem.  
                    (This is a good idea for anyone using          
                    Coordinator II, until the majority of           
                    Coordinator users upgrade.)  
                    This is done by using the following commands: 

                                Alt T     (Tools menu)  
                                C         (Customization)  
                                M         (MHS Delivery)  
                     "Enter" on Full Addressing to change it to Off. 

                     Choose option to SAVE SETTINGS...then  
                     "OK". 
  
  
  
FYI # 032489mr  
SUBJECT:  GPI ERRORS . . . . . . . . . . . . . . . . .  
DATE:     3/24/1989  . . . . . . . . . . . . . . . . . 
 
OS VERSION  :ANY  
  
GENERAL INFORMATION:  GPI ERRORS are  almost always         
                      (approximately 98% of the time) hardware    
                      problems, according to our Maintenance      
                      Engineering Department. 
  
PROBLEM:              Technicians often send the GPI Stack Dump 
                      form to customers when the problem isn't    
                      really software related.  We end up wasting a 
                      lot of time for both the customer and the    
                      Engineers who decipher the GPI forms.  
  
SOLUTION:             Please inform GPI victims of this fact and  
                      realize that the GPI stack dump will only    
                      help if we are ABSOLUTELY sure that ALL  
                      the hardware has been thoroughly checked or 
                      replaced. 
 
 
FYI # 032489mr1  
Subject:  NT2000 Support . . . . . . . . . . . . . . .  
Date:     3/27/89  . . . . . . . . . . . . . . . . . . 
  
OS VERSION:    2.15  
SHELL VERSION: n/a  
  
GENERAL INFORMATION:  LAN_DRV_107 REV. C and REV. D      
                      provided support for the NE2000 and NT2000. 
                      The title was NE2000/NT2000.  

                      There is now a LAN_DRV_107 REV. E.  This 
                      latest revision removes NT2000 from the title. 

COMMENTS:             Novell will not be selling the NT2000  
                      board.  
  
 
 
FYI # 032789gn 
Subject:  PCOX Gateway support . . . . . . . . . . . .  
Date:     03/27/89 . . . . . . . . . . . . . . . . . . 
 
  
THIS INFORMATION HAS NOT BEEN VERIFIED BY NOVELL 
  
The only gateway that Novell formally supports is PCOX's gateway.
PCOX is the only gateway that we test when we test NetWare.  
However, because we love our customers, we do the best we can to
try to get other gateways up and running.  If, after our best  
efforts, we still cannot get the third party gateway to work,  
we shed a few tears and explain that we fully support PCOX's 
gateway.  
  
In helping people with their third party gateway, there are a few  
things to keep mind.  Most all gateway problems are a result of  
memory or vector conflicts.  In many cases, a utility like RMAP  
is useful for spotting conflicts.  The ZERO7A patch solves the most
common conflict between IPX and gateways.  
  
IBM's 3270 emulation (Entry Level and Version 3.0) works fairly  
well with NetWare; however, Work Station version will not work at
all with our shell.  There is a vector conflict between our shell  
and IBM's Work Station software.  People seem to have varied  
success running IBM's emulation with Token Ring.  Our 2.1 Token  
Ring shell seems to be the most trouble free with IBM's  
emulation; Although there are people running with 2.11, 2.12, 2.15  
Token Ring shells just fine.  
  
Please remember that 2.12 shells has a problems dropping NetBIOS 
Sessions.  Those people will have to obtain the 2.15 ipx.obj and  
NetBIOS.exe files then re-link.  
  
Because we do not test or support third party gateways (including 
IBM's), the best we can do for people is to help customers spot  
conflicts and review with them the basics to avoid obvious screw  
ups.  If our best is not good enough, PCOX gateways are fully  
supported.  Remember, do not send anyone to PCOX who does not 
already own the PCOX software.  
  
 
 
FYI # 032789kp  
Subject:  OS/2 Requestor . . . . . . . . . . . . . . .  
Date:     03/28/89 . . . . . . . . . . . . . . . . . . 
 
 
 
THIS INFORMATION HAS NOT BEEN VERIFIED BY NOVELL 
 
OS VERSION:         2.1 and above  
 
 
PROBLEM:            When users upgrade to the NetWare OS/2     
                    Requestor v1.1 (for IBM's OS/2) but still use   
                    the .DLL files from the previous version (1.0),  
                    they will not be able to execute the .EXE files 
                    if the .EXE files are located on a network     
                    drive.  If the user changes his default drive to 
                    a local drive, then the .EXE files will execute  
                    as usual. 
  
SOLUTION:           Do not mix the two versions of the Requestor. 
                    Make certain that when you upgrade, you delete 
                    the old *.DLL files.  
  
 
FYI # 032889cw  
Subject:  PCMOS . . . . . . . . . . . . . . . . . . . . 
Date:     3/27/88 . . . . . . . . . . . . . . . . . . . 
 
 
THIS INFORMATION HAS NOT BEEN VERIFIED BY NOVELL 
  
OS VERSION  : 2.1 and above  
 
  
PROBLEM:            PCMOS has come out with a new version of  
                    MOS; however, there is a problem with v3.0    
                    using mosnet.  After the device drivers are     
                    loaded properly, and the user runs mosnet, if he 
                    attaches to a server, returns the servers name, 
                    and the workstation then hangs, this means that 
                    he has forgotten to run the patch to MOSNET 
                    that was described in the read.me file that     
                    came with PCMOS.  
  
 
FYI # 032889-1cw 
Subject: 386A CGA Option . . . . . . . . . . . . . . .  
Date:    3-28-89 . . . . . . . . . . . . . . . . . . . 
 
THIS INFORMATION HAS NOT BEEN VERIFIED BY NOVELL 
 
  
PROBLEM:            According to the 386A Service Guide p.1-8,   
                    the way to enable CGA capability is to move   
                    the jumper setting to W8.  However, there is   
                    no W8.  
  
SOLUTION:           It is mislabeled; it should be W9. 
  
 
  
FYI # 032889mn  
Subject:  OS/2 Requestor Files on NetWire . . . . . . . 
Date:     3 April 1989  . . . . . . . . . . . . . . . . 
 
 
Anyone who wishes to have a copy  of the latest update to the 
OS/2 Requestor can access the copy in the NOVFOR subdirectory 12.
(i.e. X:\NOVFOR\12\OSREQA.ARC through OSREQM.ARC)  Remember
the manual to the OS/2 Requester is in OS211M.ARC.  This is a 
pre-release of the OS/2 Requester.  
  
We have been getting many calls about the latest update not 
working.  This problem can be attributed to the fact that four files
where left out of the archived set when the last upload was made 
into NetWire.  The four files are out there now in the archived file
OSREQM.ARC.  The names of the four files are as follows:  
 
Whoami.exe  
Tlist.exe  
Version.exe  
Userlist.exe  
  
All of the archived files needed for the pre-release OS/2  
Requester v1.1 (Developers Kit) can be found on NetWire in 
NOVFOR data library 12 (New Uploads).
  
  
FYI # 032989js  
Subject:  Btrieve 4.11 VAP Upgrade to 5.0 VAP . . . . . 
Date:     3-30-89 . . . . . . . . . . . . . . . . . . . 
  
THIS INFORMATION HAS NOT BEEN VERIFIED BY NOVELL 
 
 
PROBLEM:            After installing the 5.0 VAP without         
                    uninstalling the 4.11 VAPS, users will get the  
                    error: 
  
                    ERROR : bserver2.00 - 5.00 login failure in     
                    server  
                    RC = FC  
  
SOLUTION:           Follow the following steps: 
           
                    login as supervisor  
                    uninstall 5.00  
                    uninstall 4.11  
                    run bindfix  
                    reinstall 5.00  
  
                    You cannot have both VAPS in the bindery     
                    files.  Also, if you run SECURITY.EXE you will 
                    get information about bad objects in  the      
                    binderies.  
  
 
FYI # 032989kr  
Subject:   Asynchronous Bridges in File Servers  . . .  
Date:      4-3-89  . . . . . . . . . . . . . . . . . .  
 
GENERAL INFORMATION:  Our stand on asynchronous bridges in   
                      the file server has changed.  In v2.1 and     
                      v2.11 we do not support the "IBM ASYNC    
                      (COM1/COM2)" option when running         
                      NETGEN.  The way users have been working 
                      around this was by copying the COMX.LAN   
                      file over to their AUXGEN directory.  This   
                      would work for users, but we did not        
                      support it if there were any problems.  
 
                      It has been pointed out that when NetWare  
                      v2.12 and v2.15 is shipped, that the          
                      COMX.LAN is placed on the AUXGEN diskette 
                      as well as the BRGEN-1 diskette.  
  
  
 
FYI # 033089kp  
Subject:  286TERMINAL, AT TERMINAL . . . . . . . . . .  
Date:     03-30-89 . . . . . . . . . . . . . . . . . .  
 
THIS INFORMATION HAS NOT BEEN VERIFIED BY NOVELL 
 
 
OS VERSION:           2.0A, 2.1X  
 
GENERAL INFORMATION:  Remote reset uses one connection to    
                      read the IBM$DOS.SYS file and one          
                      connection to login.  The boot code  
                      is then supposed to clear the first connection 
                      and keep the second.  
  
PROBLEM:              The 286terminal and ATterminal boot code  
                      do not clear the first connection.  This is a  
                      big problem for people using ELS I with     
                      more than two stations.  
 
SOLUTION:             Manually clear the station connection,  
                      install a floppy drive and bypass the remote  
                      reset. 
 
COMMENTS:             The PCTerminals do not have this problem. 
 
 
FYI # 033089an 
