Subject:  ESDI Mirroring on PS/2 Model 80 . . . . . . . 
Date:     April 26, 1989  . . . . . . . . . . . . . . .  
  
OS VERSION:  SFT 2.15  
  
GENERAL INFORMATION:  There have been many questions about 
                      whether the PS/2 Model 80 with two ESDI 
                      disk drives mirrored will function properly.  
                      It will work, but with some variations of its 
                      own.  It seems to work fine until one of the 
                      disk drives go bad.  People have reported 
                      that the machine hangs and that they can't 
                      re-boot.  
  
PROBLEM:              What really happens is that it takes anywhere 
                      from two to ten minutes to recover from a 
                      disk failure.  It isn't really hung; the users 
                      are just not patient enough to wait for it to 
                      come back to life.  The second part of the 
                      problem is that once the file server is 
                      brought down (with one of the disks still 
                      bad), the customer will be unable to re-boot. 
                      The ESDI controller will shut down the disk 
                      drive (it no longer exists to the controller).  
                      The NetWare OS recognizes an inconsistency 
                      (two drives in its table) and therefore an 
                      ABEND occurs when attempting to boot.  
  
SOLUTION:             The best solution is to replace the faulty disk 
                      drive.  If this isn't possible to do right 
                      away, then the second best work-around 
                      option is to run NETGEN and logically remove 
                      the faulty disk.  The last option is to not 
                      take the file server down when one of the 
                      drives has failed until replacement hardware 
                      is obtained.  
  
COMMENTS:             A fix for this is anticipated, but no time 
                      frame at the moment.  A Technical Bulletin 
                      for this will be released soon. 
  
 
FYI # 042689GN  
Subject:  Memory Problems Clarification . . . . . . . .  
Date:     4-28-89 . . . . . . . . . . . . . . . . . . . 
 
  
This FYI refers to the "Memory Problems Clarification" FYI dated  
4-26-89. 
 
GENERAL INFORMATION:  The previous FYI on this subject is highly 
                      misleading and confusing.  The area between 
                      640K and 1024 is NOT refered to as expanded 
                      memory.  It is a "no-mans land" where things 
                      like video RAM, BIOS extensions, and NIC 
                      dual-port buffers reside.  It is also used for 
                      the page frame "window" of LIM/EMS 
                      expanded memory.  
  
                      Next, it is becoming common for 
                      manufacturers to build PCs with 1MB of RAM 
                      as standard on the system board, using 256K 
                      chips or SIMMs.  They the have to decide 
                      what to do with the extra 384K "left over." 
                      With many 386 machines this RAM is "hidden" 
                      away by the BIOS for ROM caching, so it is 
                      not adressable by any software including 
                      NetWare, so there is no problem, except users 
                      complain when they find that NetWare won't 
                      run on their minimum-configuration PC. 
  
                      With many 286 machines and the Novell 286 
                      and 386 machines, the addressing is split so 
                      that the extra 384K is accessable above the 
                      1MB mark.  So we get a memory map which 
                      looks like this:  
  
  
============= <---1408k   
|  384k     |             
+-----------+1MB          
|  BIOS     |             
+-----------+             
|           |  
|"NO MAN'S" |             
+-----------+             
|  VIDEO    |             
+-----------+640K         
|           |             
| DOS AREA  |             
|           |  
|           |             
=============0            
                          
                          
                      Therefore, any additional RAM extended RAM 
                      boards nust be configured to start at the 
                      1408K line.  However, many of them will only 
                      start on Mbyte boundaries, so thay are 
                      useless in these machines. 
 
                      Now, if any customers are installin boards 
                      which are incorrectly configured, or can only 
                      be set to megabyte boundaries, they will end 
                      up with overlapped RAM address space, 
                      resulting in the NMIs and GPIs. 
 
                      Also note, with 4MB systems, such as the 
                      386AE, the same applies, with any extra 
                      boards needing to be set to 4096+384 = 
                      4480K. 
 
Subject:  OS/2 Requestor v1.1 . . . . . . . . . . . . . 
Date:     4/28/89 . . . . . . . . . . . . . . . . . . . 
 
 
GENERAL INFORMATION:  The files for the OS/2 Requester are on 
                      NetWire, but until now there hasn't been any 
                      documentation as to where they go, on what 
                      disks and sub-directories.  
 
PROBLEM:              Where do the files go?  
  
SOLUTION:             There is an archived readme file on 
                      OS211M.ARC which tells the customer which 
                      disks and  sub-directories the files belong 
                      (for both 3.5" and 5.25" media).  
  
COMMENTS:             The readme file is included on the bottom of 
                      this message. 
  
****************************DISCLAIMER************************* 
THIS IS NOT AN OFFICIAL NOVELL TECHNICAL 
BULLETIN/DOCUMENT. IT IS THE RESULT OF INFORMATION 
GATHERED IN LANSWER LABS AND THROUGHOUT THE FIELD.  
USE IT FOR YOUR INFORMATION ONLY. 
*************************************************************** 
  
  
      Files and Sub-Directories on v1.1 Requester Diskettes  
                    (3.5" Diskettes @ 1.44mg)  
   
Requester Diskette:  
  
       1.   Format a 3.5" diskette to 1.44mg.  
       2.   Give it the label "Requester".  
       3.   Put two sub-directories on it named: "1.0" & "1.1".  
       4.   Copy the files de-archived from "1_0.arc" and "1_1.arc" 
            on "OSREQA.ARC" to their respective sub-directories.  
       5.   Copy all the de-archived files from: "OSREQB.ARC" &  
            "OSREQC.ARC" to the root directory.  
       6.   Add these files from the "OSREQD.ARC" archive:         
            SPDAEMON.EXE, SPX.SYS, SPXCALLS.DLL,  
            SYS$ERR.DAT, SYS$MSG.DAT, and TOKEN.SYS. (also in 
            root directory).  
       7.   You are now done with the "REQUESTER" diskette.  
  
Toolkit Diskette:  
  
       1.   Format a 3.5" diskette to 1.44mg.  
       2.   Give it the label "Toolkit".  
       3.   Put two sub-directories on it named: "LIB" & 
            "INCLUDE".  
       4.   Copy the files de-archived from "LIB.ARC" & 
            "INCLUDE.ARC" on "OSREQD.ARC" to their respective 
            sub-directories.  
      5.    You are now done with the "TOOLKIT" diskette.  
  
Public diskette:  
  
       1.   Format a 3.5" diskette to 1.44mg.  
       2.   Give it the label "Public."  
       3.   Copy all the files de-archived from: OSREQE.ARC,   
            OSREQF.ARC, OSREQG.ARC, OSREQH.ARC, OSREQI.ARC, 
            OSREQJ.ARC, OSREQK.ARC, OSREQL.ARC, and 
            OSREQM.ARC to the "PUBLIC" diskette.  
       4.   You are now done with the "PUBLIC" diskette.  
  
   
      Files and Sub-Directories on v1.1 Requestor Diskettes  
                     (5.25" Diskettes @ 360K)  
  
Requester Diskette:  
  
       1.   Format a 5.25" diskette to 360k.  
       2.   Give it the label "Requester".  
       3.   Put two sub-directories on it named "1.0" & "1.1".  
       4.   Copy the files de-archived from "1_0.arc" & "1_1.arc"   
            on "OSREQA.ARC" to their respective sub-directories.  
       5.   Copy all the de-archived files from: "OSREQB.ARC" and  
            "OSREQC.ARC" to the root directory.  
       6.   Add these files from the "OSREQD.ARC" archive:   
            SPDAEMON.EXE, SPX.SYS, SPXCALLS.DLL, 
            SYS$ERR.DAT, SYS$MSG.DAT, and TOKEN.SYS. (also in 
            root directory).  
       7.   You are now done with the "REQUESTER" diskette.  
   
Toolkit Diskette:  
  
       1.   Format a 5.25" diskette to 360k.  
       2.   Give it the label "Toolkit".  
       3.   Put two sub-directories on it named: "LIB" & 
            "INCLUDE".  
       4.   Copy the files de-archived from "LIB.ARC" & 
            "INCLUDE.ARC" on "OSREQD.ARC" to their respective 
            sub-directories.  
       5.   You are now done with the "TOOLKIT" diskette.  
   
Public Diskette:  
  
       1.   Format a 5.25" diskette to 360k.  
       2.   Give it the label "Public".  
       3.   Copy all the files de-archived from: OSREQE.ARC, 
            OSREQF.ARC, OSREQG.ARC, OSREQH.ARC, 
            OSREQI.ARC,OSREQJ.ARC, OSREQK.ARC, OSREQL.ARC, 
            and OSREQM.ARC to the "PUBLIC" diskette.  
       4.   You are now done with the "PUBLIC" diskette.  
  
FYI # 042889LA  
Subject:  Printer Maintenance Selection . . . . . . . . 
Date:     4-28-89 . . . . . . . . . . . . . . . . . . . 
 
 
THIS INFORMATION HAS NOT BEEN VERIFIED BY NOVELL. 
 
OS VERSION:    2.12 and Others 
 
GENERAL INFORMATION:  This problem occurs with the AST 386 
                      Premium. 
  
PROBLEM:              When going into Printer Maintenance to 
                      spool printers for the first time, the box 
                      containing the spooled printer list is full of 
                      ASCII characters and is not readable   
  
SOLUTION:             Initiate the SETUP (Ctrl-Alt-Esc).  Set the 
                      printer ports to be enabled, or ON, and 
                      make sure that they are Interrupt Driven. 
                      Then re-run the Netgen and printer 
                      maintenance.  
  
 
 FYI # 050189kr  
Subject:  VADD Manufacturer's Must Certify Each Drive  
Date:     5/2/89 . . . . . . . . . . . . . . . . . . .  
  
OS VERSION:      All  
REVISION:        All  
SHELL VERSION:   All  
  
GENERAL INFORMATION:  When a company submits their Value Added 
                      Disk Driver (VADD) to Novell's Engineering 
                      Department for certification, our Engineers 
                      make sure that the software performs 
                      correctly as a disk driver.  After it has 
                      passed and is a certified VADD then the 
                      manufacturer must contact our Independent 
                      Product Test (IPT) people and submit each 
                      individual drive to be tested and approved 
                      with their VADD.  
  
                      Some VADD developers have been telling 
                      customers that when we certify their VADD 
                      we also certify any drive that is used with it.  
                      This is not true.  We must have an IPT done 
                      for every drive that the VADD will be used 
                      with.  
  
PROBLEM:              Unsupported drives are being used with a 
                      certified VADD.  
  
SOLUTION:             An IPT must be done for each drive used 
                      with the VADD.  
  
COMMENTS:             Non-supported drives with a certified VADD 
                      may or may not work properly.  One known 
                      problem is with VREPAIR; it works fine on 
                      supported drives, but returns VOLUME 
                      OVERFLOW DISK on some non-supported 
                      drives.  
  
 
FYI # 050289th  
Subject:  IBM AS400 and PCOX Policy. . . . . . . . . . . . . . . . . 
Date:     9 May 1989 . . . . . . . . . . . . . . . . . . . . . . . . 
 
  
GENERAL INFORMATION:  Our PCOX 5250 family of gateway products 
                      can be used to attach to AS400's in the same 
                      way we attach to the System 38's.  The only 
                      limitation is that PC Support is not available. 
 
                      This does not mean you cannot use PC's; it 
                      means that there are certain functions that 
                      the Gateway cannot handle, such as virtual 
                      printing and certain file transfer capabilities.  
                      The product to provide complete support for 
                      the AS400 is due out in the 3rd quarter of 
                      this year.  Both the 5250 gateways and 
                      problems with it, such as with the AS400 will 
                      be handled by Novell Communications 
                      Products Division. 
  
                      IMPORTANT 
                      Contrary to anything stated previously, todays 
                      policy is to refer people to Novell 
                      Communication Products Division (CPD) for 
                      theoretical questions about running PCOX 
                      software on IBM or IRMA hardware.  In doing 
                      this we must be certain to tell these 
                      customers to ask for the Product Information 
                      Department and not Technical Support.  
                      Their Technical Support can help only if the 
                      enduser has already purchased PCOX software. 
                       
 
 
FYI #050489cw  
Subject:  Math Coprocessor with AST Premium 386/20. . . . . . . . .  
Date:     5/8/1989. . . . . . . . . . . . . . . . . . . . . . . . . 
 
OS VERSION:     2.15 SFT  
SHELL VERSION:  2.15  
  
PROBLEM:    There have been reports of users getting the Run-time 
            error R6002, "Floating Point Not Loaded" while running 
            the SYSCON utility, using TMS34010 CPU "C" compiler 
            either logged in or just with the shells loaded.  
  
SOLUTION:   Set the coprocessor type to 287 in ASTSETUP, 
            perform the  operation, then reset the coprocessor type 
            to 387.  
  
  
FYI # 050889st  
Subject:  Using NDIR with Owner Option. . . . . . . . . . . . . . .  
Date:     5/4/1989. . . . . . . . . . . . . . . . . . . . . . . . . 
 
OS VERSION: All versions  
 
GENERAL INFORMATION:  Using the owner option of the Ndir command 
                      line utility with a user name beginning with 
                      "GE" will not work correctly.  "GE" is also 
                      another option stands for "Greater than or 
                      equal to".  So if  a user uses the owner 
                      option by specifying the user name 
                      "GERALD", it will confuse Ndir.  It will 
                      think that the user is trying to list the 
                      filenames greater than or equal to <sub>.  
  
PROBLEM:              The owner option in Ndir will not work 
                      with user name starting with "GE." 
  
SOLUTION:             There is no solution yet.  Novell's 
                      Engineering Department is aware of the 
                      problem.  
  
FYI # 050889st  
Subject:  New Drivers for External Drives -- Compaq. . . . . . . . . 
Date:     9 May 1989 . . . . . . . . . . . . . . . . . . . . . . . . 
 
GENERAL INFORMATION:  Compaq has new drivers for their 
                      external drives.  The diskette is labeled 
                      Version 1.1, but the drivers are actually the 
                      release 1.21.  One client had many problems 
                      with a Compaq drive until he received these 
                      drivers from Compaq.  
Subject:  Printing Using Even Parity . . . . . . . . . . . . . . . . 
Date:     May 8, 1989  . . . . . . . . . . . . . . . . . . . . . . . 
  
OS VERSION  :  2.1 through 2.15  
  
GENERAL INFORMATION:  This problem has been occurring since 
                      the release of v2.1.  
  
PROBLEM:              NETGEN is writing the wrong bit pattern to 
                      sector 15 which interferes with printing on 
                      printers configured for even parity.  The 
                      temporary fix is to use DISKED and correct 
                      the bit pattern.  
  
SOLUTION:             To use DISKED, boot the server up under 
                      DOS, then using UTILEXE-1, type DISKED at 
                      the DOS A:>.  If the system is configured 
                      with more than one hard drive, a menu will 
                      be displayed showing the available drives.  
                      Pick the primary drive (option 1) from the 
                      menu.  At that point the > prompt will 
                      appear.  For on line help type H at the > 
                      prompt.  Type r 15 <ENTER> (read sector 15) 
                      and then press d (dump).  This will display 
                      255 bytes of information to the screen in 
                      the format shown below.  Type d again to 
                      display the next 255 bytes.  The address you 
                      are looking for is 0100h which is the 
                      beginning of the Standard Printer Table. The 
                      Addresses for each row are the four digit 
                      numbers displayed in a column on the left 
                      side of the screen.  
  
                      Depending upon which printer number was 
                      configured in NETGEN to use even parity, the 
                      address of the incorrect bit pattern will vary 
                      in the table.  If printer 0 is configured with 
                      even parity the address of the incorrect bit 
                      pattern will be 0102h.  If printer 1 is 
                      configured the address will be 0112h, and so 
                      on as illustrated below.  
  
       0100    01 00 F3 00 00 00 00 00 00 00 00 00 00 00 00 00  
       0110    00 00 xx 00 00 00 00 00 00 00 00 00 00 00 00 00  
       0120    00 00 xx 00 00 00 00 00 00 00 00 00 00 00 00 00  
       0130    00 00 xx 00 00 00 00 00 00 00 00 00 00 00 00 00  
  
                      To change the bit pattern, type c <address> 
                      and then ENTER.  For example, if the address 
                      that you need to change is at 0102h you 
                      would type c 0102 <ENTER>.  DISKED is 
                      now in a CHANGE mode with the screen 
                      looking something like this, 0102 F3<-_.  The 
                      cursor (represented by the underline) will be 
                      at the end of the entry, waiting for your 
                      input.  Now, look on the table below and 
                      type in the corresponding byte for the 
                      configuration that you want and then press 
                      ENTER, which in this case will be FB.  
  
                      Patterns for all possible options with even 
                      parity are:  
  
                      NETGEN set F2h should be FAh = 9600 baud, 
                           even parity, 1 stop bit, and a 
                           wordlength of 7 bits  
                      NETGEN set F6h should be FEh = 9600 baud, 
                           even parity, 2 stop bits, and a 
                           wordlength of 7 bits  
                      NETGEN set F3h should be FBh = 9600 baud, 
                           even parity, 1 stop bit, and a 
                           wordlength of 8 bits  
                      NETGEN set F7h should be FFh = 9600 baud, 
                           even parity, 2 stop bits, and a 
                           wordlength of 8 bits  
  
                      The next address and corresponding byte will 
                      then be displayed.  To exit from the CHANGE 
                      mode type a period and then ENTER which 
                      will place you back to the > prompt.  Now, to 
                      make sure that the correct byte has been 
                      changed to the correct pattern before 
                      anything is made permanent, type d twice and 
                      look at the changed byte.  Once you are 
                      satisfied that it is correct, type w 15 
                      <ENTER> (write sector 15).  Then to exit 
                      back to DOS type q.  
  
                      NOTE:  Once a byte has been changed and 
                      the Printer Definition window is observed 
                      from NETGEN you will see garbage where the 
                      parity and XON/XOFF are normally displayed 
                      for that particular printer.  Don't worry 
                      about it.  Most importantly, don't use 
                      NETGEN to correct what is displayed or you 
                      will have to run DEBUG all over again.  
  
COMMENTS:             DISKED is part of the 2.1x utilities and is 
                      linked when the operating system is 
                      generated.  It is found on the UTILEXE-1 
                      diskette or, if the OS is generated from hard 
                      drive or network, it is found in the 
                      UTILEXE-.1 subdirectory.  
 
 
FYI # 050889dl  
Subject:  Using Ncopy and copy on large files. . . . . . . . . . . . 
Date:     5/8/89 . . . . . . . . . . . . . . . . . . . . . . . . . . 
  
PROBLEM:    Occasionally we have users report that during the 
            copy of a large file in NetWare they lose their 
            connection to the server.  This copying is normally done 
            from one subdirectory to another on the same server.  
            The error they receive is the standard "error on server 
            XXXXX abort or retry."  In one instance we were able 
            to isolate the problem.  It appears that the interrupt 
            controller chip 206, on the AT motherboard  of certain 
            machines may cause this.  There isn't much you can do 
            except have them check for the presence of a Seamans 
            SAPA2C206 interrupt controller.  This chip when used in 
            conjunction with the Wren III drive creates a problem.  
   
SOLUTION:   Chips and Technology rev. f-1 seems to work.  
 
FYI # 050889cw  
Subject:  Packed File is Corrupt . . . . . . . . . . . . . . . . . . 
Date:     5/4/89 . . . . . . . . . . . . . . . . . . . . . . . . . . 
 
PROBLEM:    The error "Packed file is Corrupt" may be caused by 
            several things; if the file server is running at 16 MHz 
            or above try slowing the server down.  This error can 
            also be caused by an interface card has problems 
            running in a fast server.  We have had reports of both 
            Arcnet and Ethernet cards running into this error.   
  
SOLUTION:   Often a different brand of interface card will solve this 
            problem.  
 
FYI # 050489cw1  
Subject:  BIOS.ARC on NetWire . . . . . . . . . . . . . . . .  
Date:     18 May 1989 . . . . . . . . . . . . . . . . . . . .  
  
THIS INFORMATION HAS NOT NECESSARILY BEEN VERIFIED BY NOVELL 
 
GENERAL INFORMATION:     BIOS.ARC has been re-uploaded to  
                         NOVUSER Data Library 17 on NetWire.  It was  
                         removed from NetWire but is available on  
                         once again.   
   
                    BIOS.ARC contains a temporary solution for  
                    increasing the number of NetBIOS sessions.  A  
                    new release of our NetBIOS is being developed.   
                    This new release will only require the number  
                    of sessions to be set in the SHELL.CFG file. No  
                    software reset will have to be done by the  
                    user.   
   
Subject:  Stack Overflow . . . . . . . . . . . . . . . . . . . . . .  
Date:     5-10-89. . . . . . . . . . . . . . . . . . . . . . . . . .  
  
THIS INFORMATION HAS NOT NECESSARILY BEEN VERIFIED BY NOVELL 
 
OS VERSION:  All versions with Btrieve VAPs   
   
GENERAL INFORMATION:     A Stack Overflow can occur after  
                         installing  Btrieve Vaps.  This "stack  
                         Overflow" means that the Disk process  
                         Stack was not large enough for all the  
                         disk processes that the OS needs and the  
                         BTRIEVE.VAP needs.   
   
PROBLEM:            The stack size is at 140 and the stack size  
                    needs to be increased.  The maximum size the  
                    stack can be increased to is 254.   
   
SOLUTION:           This patch is a DOS Debug for 2.15 SFT only.   
                    Debug the file sft_1.obj on the sftobj diskette   
   
     The hex value of 8C is 140   
     The hex value of FE is 254   
     search for "8B E5 81 06 00 00 8C 00 BB 8C 00 53 BB"   
     modifying the two 8C with FE will increase the stack          
size   
  
   
     debug sft_1.obj   
     S CS:100 FFFF 8B E5 81 06 00 00 8C 00 BB 8C 00 53 BB   
   
     XXXX:5BB4  (this offset value may be different for you)   
     D XXXX:5BB4 (use the offset value returned above)   
     E XXXX:5BBA FE (again, this address will be different for you)  
       
  
     ** ADDRESS 5BBA IS THE LOCATION OF FIRST '8C'   
     E XXXX:5BBD FE (Add 3 to your address for the second offset  
     value)   
  
     ** ADDRESS 5BBD IS THE LOCATION OF SECOND '8C'   
               W   
               Q   
   
     Then regen your OS.   
   
   
COMMENTS:           Hopefully the Advanced version will include this  
                    patch in the maintenance release of 2.15   
   
  
FYI # 051089kr   
Subject:  Addendum - Printing Using Even Parity. . . . . . . . . . .  
Date:     May 11, 1989 . . . . . . . . . . . . . . . . . . . . . . .  
  
THIS INFORMATION HAS NOT NECESSARILY BEEN VERIFIED BY NOVELL 
 
OS VERSION  :  2.1 through 2.15   
  
GENERAL INFORMATION:     This is an addendum to the previous FYI  
                         dated May 8, 1989   
   
PROBLEM:            NETGEN is writing the wrong bit pattern to  
                    sector 15.   
   
SOLUTION:           Additional bit pattern for all other possible  
                    configurations are:   
   
                    NETGEN set D2h should be DAh = 4800 baud,  
                    even parity, 1 stop bit, and a wordlength of 7  
                    bits   
                    NETGEN set D6h should be DEh = 4800 baud,  
                    even parity, 2 stop bits, and a wordlength of 7  
                    bits   
                    NETGEN set D3h should be DBh = 4800 baud,  
                    even parity, 1 stop bit, and a wordlength of 8  
                    bits   
                    NETGEN set D7h should be DFh = 4800 baud,  
                    even parity, 2 stop bits, and a wordlength of 8  
                    bits   
  
                    NETGEN set B2h should be BAh = 2400 baud,  
                    even parity, 1 stop bit, and a wordlength of 7  
                    bits   
                    NETGEN set B6h should be BEh = 2400 baud,  
                    even parity, 2 stop bits, and a wordlength of 7  
                    bits   
                    NETGEN set B3h should be BBh = 2400 baud,  
                    even parity, 1 stop bit, and a wordlength of 8  
                    bits   
                    NETGEN set B7h should be BFh = 2400 baud,  
                    even parity, 2 stop bits, and a wordlength of 8  
                    bits   
  
                    NETGEN set 92h should be 9Ah = 1200 baud,  
                    even parity, 1 stop bit, and a wordlength of 7  
                    bits   
                    NETGEN set 96h should be 9Eh = 1200 baud,  
                    even parity, 2 stop bits, and a wordlength of 7  
                    bits   
                    NETGEN set 93h should be 9Bh = 1200 baud,  
                    even parity, 1 stop bit, and a wordlength of 8  
                    bits   
                    NETGEN set 97h should be 9Fh = 1200 baud,  
                    even parity, 2 stop bits, and a wordlength of 8  
                    bits   
  
                    NETGEN set 72h should be 7Ah = 600 baud,  
                    even parity, 1 stop bit, and a wordlength of 7  
                    bits   
                    NETGEN set 76h should be 7Eh = 600 baud,  
                    even parity, 2 stop bits, and a wordlength of 7  
                    bits   
                    NETGEN set 73h should be 7Bh = 600 baud,  
                    even parity, 1 stop bit, and a wordlength of 8  
                    bits   
                    NETGEN set 77h should be 7Fh = 600 baud,  
                    even parity, 2 stop bits, and a wordlength of 8  
                    bits    
  
                    NETGEN set 52h should be 5Ah = 300 baud,  
                    even parity, 1 stop bit, and a wordlength of 7  
                    bits   
                    NETGEN set 56h should be 5Eh = 300 baud,  
                    even parity, 2 stop bits, and a wordlength of 7  
                    bits   
                    NETGEN set 53h should be 5Bh = 300 baud,  
                    even parity, 1 stop bit, and a wordlength of 8  
                    bits   
                    NETGEN set 57h should be 5Fh = 300 baud,  
                    even parity, 2 stop bits, and a wordlength of 8  
                    bits    
  
                    NETGEN set 32h should be 3Ah = 150 baud,  
                    even parity, 1 stop bit, and a wordlength of 7  
                    bits   
                    NETGEN set 36h should be 3Eh = 150 baud,  
                    even parity, 2 stop bits, and a wordlength of 7  
                    bits   
                    NETGEN set 33h should be 3Bh = 150 baud,  
                    even parity, 1 stop bit, and a wordlength of 8  
                    bits   
                    NETGEN set 37h should be 3Fh = 150 baud,  
                    even parity, 2 stop bits, and a wordlength of 8  
                    bits    
  
                    NETGEN set 12h should be 1Ah = 110 baud,  
                    even parity, 1 stop bit, and a wordlength of 7  
                    bits   
                    NETGEN set 16h should be 1Eh = 110 baud,  
                    even parity, 2 stop bits, and a wordlength of 7  
                    bits   
                    NETGEN set 13h should be 1Bh = 110 baud,  
                    even parity, 1 stop bit, and a wordlength of 8  
                    bits   
                    NETGEN set 17h should be 1Fh = 110 baud,  
                    even parity, 2 stop bits, and a wordlength of 8  
                    bits   
   
  
 FYI #050889dl-a   
Subject:  Strange NetGEN Error Message . . . . . . . . . . . . . . .  
Date:     05/12/89 . . . . . . . . . . . . . . . . . . . . . . . . .  
  
THIS INFORMATION HAS NOT NECESSARILY BEEN VERIFIED BY NOVELL 
 
OS VERSION:  2.1x   
   
PROBLEM:       While using the network installation method,  
               under"NETWORK OPTIONS," a user received the  
               following error message:  '"Nconfig.exe" disappeared  
               from "Auxgen" Vol!'.     
  
SOLUTION:      The node from which he was trying to do the  
               network installation had an AUTOEXEC.BAT which  
               loaded a memory resident program.  As soon as the  
               user rebooted and broke out of the batch file (not  
               allowing the memory resident program to load), the  
               network installation option worked.   
   
COMMENTS:      Memory resident programs (TSRs) cause more  
               problems with NetWare than is commonly realized.   
               Always check *.bat files to see what they are doing.  
   
   
FYI # 051289sm   
Subject:  Compsurf and Viruses . . . . . . . . . . . . . . . . . . .  
Date:     18 May 1989. . . . . . . . . . . . . . . . . . . . . . . .  
  
  
THIS INFORMATION HAS NOT NECESSARILY BEEN VERIFIED BY NOVELL 
 
GENERAL INFORMATION:     Compsurf is *NOT* necessary for any  
                         known virus and will result in a lot of  
                         wasted time.   
   
                         For the 1813/1808 virus and, in fact, for  
                         any virus that adds code to a file you  
                         should :   
   
                         1.  List all files on the network to  
                         establish their size, creation date and  
                         modification information.   
   
                         2.  Compare these sizes and other  
                         statistics with the information from copies  
                         of the original disks - which should have  
                         been write-protected.  
   
                         3.  Identify all files that have inexplicable  
                         size/date information changes (and if you  
                         have the tools CRC and Checksum test the  
                         files), then copy all suspected infected  
                         files to a floppy disk and label it  
                         "DANGER - POSSIBLE VIRUS INFECTION".  
                         Then delete the infected files from the  
                         network.   
   
                         4.  Replace the files from the copies of  
                         the original disks.    
  
                         5.  Audit your backups - they might have  
                         been infected.   
   
                         6.  Restructure your network so users  
                         have rights that don't allow them to  
                         spread viruses, i.e. wherever possible, make  
                         executables Execute-Only and make the  
                         effective rights SRO.  If you go in as  
                         supervisor and don't run anything but  
                         programs that you know are free from  
                         viruses.   
   
                         If you want to go for broke then by all  
                         means delete everything on your network  
                         drives, but don't Compsurf - you're just  
                         wasting time.  Be warned:  There are  
                         viruses that don't add code with an  
                         increase in the length of the file - they  
                         find, for example, internal buffers in the  
                         program and embed themselves there.   
Subject:  Token Ring and Interrupt 2 (IRQ2). . . . . . . . . . . . .  
Date:     May 16, 1989 . . . . . . . . . . . . . . . . . . . . . . .  
   
THIS INFORMATION HAS NOT NECESSARILY BEEN VERIFIED BY NOVELL 
 
OS VERSION:    2.1x (this includes 2.15 and the soon to be  
               maintenance release of 2.15)   
   
GENERAL INFORMATION:     Novell's Token Ring shell driver always  
                         uses IRQ2.  Regardless of what IRQ the  
                         user configures his shell for, the shell is  
                         hard coded to go out and turn on IRQ2  
                         once per machine tick (18 times per  
                         second).  What this means is that if the  
                         user configures his shell to use IRQ3 for  
                         example, then the shell does use IRQ3.  It  
                         also will turn on IRQ2 18 times per second.   
                         If another card is using IRQ2 and that  
                         interrupt is always enabled, then the fact  
                         that we go out and turn it on is  
                         irrelevant.  No problem exists if nothing is  
                         configured to use IRQ2.  However, there is  
                         a problem if a device needs to turn IRQ2  
                         off for a period of time.    
   
PROBLEM:                 The reason this procedure was implemented  
                         is that there are several popular (and  
                         ill-behaved) applications which will turn  
                         off IRQ2 and then they don't restore it.    
                           
                         Applications written in compiled BASIC  
                         will often turn off IRQ2 and IRQ3 when  
                         the application is exited.  This will cause  
                         the workstation to hang after the  
                         application is exited.  This means that if  
                         you have configured for IRQ3 and you are  
                         using an ill-behaved program that turns  
                         off interrupts and doesn't turn them back  
                         on, or you are using a compiled BASIC  
                         application, you run the risk having your  
                         workstation hang.  
  
SOLUTION:                There is no solution at this time except to  
                         use IRQ2 for IBM TOKEN RING wherever  
                         possible.  Novell doesn't perceive this as a  
                         major issue because by and large the IBM  
                         Token Ring customer base is using IRQ2  
                         anyway.  For those of you who really need  
                         something that doesn't continually turn on  
                         IRQ2, be assured that we plan to change  
                         it.  However, the time frame is unknown  
                         for now.  
   
  
FYI # 051689gnSubject:  G/Ethernet GEPCSH.LAN Revision . . . . . . . . . . . . . .  
Date:     5/17/89. . . . . . . . . . . . . . . . . . . . . . . . . .  
  
THIS INFORMATION HAS NOT NECESSARILY BEEN VERIFIED BY NOVELL 
 
OS VERSION  :2.15   
   
GENERAL INFORMATION:     Gateway Communications has shipped v2.2  
                         of the GEPCSH.LAN driver (it goes on the  
                         AUXGEN diskette).   
   
PROBLEM:                 This version has resulted in many  
                         unexplainable problems for clients using  
                         G/Ethernet Nics.  
   
SOLUTION:                Gateway now ships a version 2.5  
                         GEPCSH.LAN.  Make sure the clients are  
                         aware of this if they come across  
                         installation problems.   
   
  
FYI # 051789aw   
Subject:  Novell NE/2 Adapter and IBM PS/2 Model 80. . . . . . . . . 
Date:     26 May 1989. . . . . . . . . . . . . . . . . . . . . . . . 
 
Here, FOR YOUR INFORMATION is a conversation I had with an IBM 
tech via ASKINFO.   
  
QUESTION:                  Are there any problems using the Novell NE/2 
                           adapter with the early versions of the Model 
                           80? 
  
DETAIL ABOUT QUESTION:     Using these, there is an uncontrollable beep 
                           and an eventual hang.  This usually occurs on 
                           the file server, but can also happen on the 
                           workstation.  The system control port (port 
                           61h) is being written with random data.  This 
                           is a system data bus problem, not a problem 
                           with the BIOS software.  This problem occurs 
                           when using a network interface card that 
                           uses programmed I/O, such as NE/2.  I 
                           understand this occurs only on certain 20 
                           MHZ model 80's:  Model 111 S/N 601-9000 
                           and below and model 311 S/N 650-2022 and 
                           below.  The flawed mother boards in these 
                           machines need to be replaced per IBM ECA 
                           #008.  This is according to Novell Technical 
                           Bulletin 241.  My Question:  Is this 
                           information accurate, and what more can you 
                           tell me about this?  
  
RESPONSE:                  We have no information regarding the 
                           NOVELL NE/2 adapter.  The ECA you asked 
                           about does exist, although the details do not 
                           say that the system eventually hangs.  The 
                           details are listed below.   
  
DETAIL ABOUT RESPONSE:     The 8580 speaker makes a crackling noise 
                           and/or short beeps.  The worst-case condition 
                           occurs when the speaker turns on 
                           continuously and cannot be reset.  Only 8580 
                           Models 111 and 311 with an 80387 math 
                           coprocessor installed are affected.  The 
                           system serial number ranges containing 
                           affected planar boards are as follows:  Model 
                           111 below serial number 6019000; Model 311 
                           serial numbers below 6502022.  If a 
                           suspected board is identified in the physical 
                           check portion of this ECA and a math 
                           coprocessor is installed, replace the planar 
                           board.  The planar board FRU is P/N90X7390.  
                            
 
PHYSICAL CHECK:            1) Suspected planar boards can be identified 
                           by checking the P/N stamped on the board.  
                           Manufacturing P/N15F6603, P/N15F6605, and 
                           P/N15F6727 are affected.  P/Ns are stamped 
                           on the planar board near the bar code label 
                           or between the card sockets.   
  
                           2) Check for the installation of the 80387 
                           math coprocessor.  If a coprocessor is 
                           installed and the planar is identified as listed 
                           above, replace the planar board as instructed 
                           in the detail section of this ECA.  If any P/N 
                           other than those listed above is identified or 
                           if there is no 80387 math coprocessor 
                           installed, no further action is required.   
  
                           As we do not support NOVELL, this is all the 
                           information I have.  This information can be 
                           found in the PS/2 Family Service Information 
                           Manual (SIM), order # SA38-0039.  Thank 
                           you.   
 
FYI # 051989ew Subject:  NetWare for VMS. . . . . . . . . . . . . . . . . . . . . . 
Date:     5/19/89. . . . . . . . . . . . . . . . . . . . . . . . . . 
  
THIS INFORMATION HAS NOT NECESSARILY BEEN VERIFIED BY 
NOVELL 
 
PROBLEM:    We have encountered a problem while printing in NetWare for 
            VMS.  Print jobs seem to get sent but never get to the 
            VAX print queue.   
 
SOLUTION:   Make sure that the user can print from the VAX side logging 
            in as a VMS user.  If they can, make sure they have the 
            CONNECT PRINTER issued correctly.  It can be done either 
            from the NetWare console or in the file OPTIONS.DAT.  Also 
            check if they are using DQS (DEC print queue service).  If 
            they are, have them include the NOPARAM parameter in the 
            CONNECT PRINTER command.  
 
FYI # 051989jl Subject:  NetWare Operation with Drives Larger than 255 Megabytes. . 
Date:     May 23, 1989 . . . . . . . . . . . . . . . . . . . . . . . 
 
THIS INFORMATION HAS NOT NECESSARILY BEEN VERIFIED BY 
NOVELL 
 
OS VERSION:  2.15  
 
GENERAL INFORMATION:  Note:  This information will be distributed with 
                      NetWare Ready subsystems that go through the 
                      IMSP program as a note regarding product 
                      performance on NetWare.  
  
PROBLEM:              We have discovered certain conditions regarding 
                      the operation of large drives on NetWare that 
                      users must be familiar with to avoid data loss.  
  
                      In drives exceeding 255MB, disk partitions must be 
                      set to the default parameters.  If a drive partition 
                      is set to anything other than the defaults 
                      recommended during installation (first partition of 
                      255MB, second of the remaining disk space), then 
                      an error can occur during the MIRROR process.  
                      Data may be lost if the partitions are set to 
                      anything other than the recommended default 
                      settings.  
  
                      Furthermore, it appears that the OS is indicating 
                      "finished status" for the REMIRROR process prior 
                      to actual termination of the process.  If the 
                      operator intervenes before the disk is actually 
                      finished with the REMIRROR, the process will 
                      crash.   
 
SOLUTION:             In these cases we recommend two things:  
  
                      -Monitor the disk light during the REMIRROR and 
                      check it once status is reported.  If the disk light 
                      indicates the disk is still being accessed, the 
                      REMIRROR process has not finished.  The operator 
                      should wait until the disk access has finished to 
                      use the keyboard.  
  
                      -Wait one full minute after "finished status" is 
                      reported on the REMIRROR before proceeding.  If 
                      "finished status" is being reported too quickly, one 
                      minute will give a 320MB drive enough time to 
                      finish off the REMIRROR process.  The time 
                      needed for drives larger than 320MB is 
                      undetermined at this time.  
  
                      Until these problems are corrected in a NetWare 
                      maintenance release we recommend that users of 
                      large drives on NetWare 2.15 observe these 
                      precautions.  
  
  
 
FYI # 052389gn Subject:  NE2000 Boards. . . . . . . . . . . . . . . . . . . . . . . 
Date:     5-18-89. . . . . . . . . . . . . . . . . . . . . . . . . . 
 
THIS INFORMATION HAS NOT NECESSARILY BEEN VERIFIED BY 
NOVELL 
 
 
OS VERSION:  2.15  
  
PROBLEM:    Using NE2000 at option 1 will give the error "Error 
            Initializing LAN driver : Ethernet Buffer Memory Failure"  
            OR " *** ETHERNET card not initializing " when initializing 
            the LAN driver.   
  
SOLUTION:   Use option 0 for the NE2000 card  
  
COMMENTS:   This has only occurred with a Novell 286A used as a file 
            server.  It is not known if this same problem will occur in 
            other servers  
  
REPLY:      In the message on the NE2000 I get the feeling this was on 
            a 286A file server.  If this is the case check your BIOS.  
            The older 286A BIOS versions have a major problem with 
            interrupt 2 (Token Ring will not work either with interrupt 
            2).  I think you will find this option functions fine with all 
            other machines.  
 
FYI # 052289kr Subject:  Files on NetWire . . . . . . . . . . . . . . . . . . . . . 
Date:     30 May 1989. . . . . . . . . . . . . . . . . . . . . . . .  
 
GENERAL INFORMATION:  The following files have been uploaded into 
                      NOVUSER on NetWire into data library 17 the 
                      new upload library: 
  
                      ATT.ARC   - AT&T driver that has the ability to 
                      provide support for each of the AT&T adapters. 
                      (ie. 1MB StarLAN adapter, 10Mb StarLAN PC NAU, 
                      & 10MB EN100(Ethernet adapter).  
  
                      NP600W.ARC - Contains an update to Micom's 
                      NP600 2.1x Workstation Driver and an automated 
                      batch file for loading.  
  
                      PTF177.ARC - This is an update to the previously 
                      released PTF177.ARC. It applies to PCOX/ONE 
                      COAX v2.3 with COAX-P Board. Problem 
                      Description when downloading large host file using 
                      the RECEIVE command, the program terminates 
                      with a TR.  
  
                      PTF181.ARC  - Contains a fix for NetWare SNA 
                      Gateway v1.0.  The new NVLA.EXE and NVLG.EXE 
                      files in this PTF correct the problem of users  
                      getting a different LU than the one that was 
                      assigned on the Gateway config.  Also, NVLA.EXE  
                      fixes the workstation lock up that occurs with an 
                      X().  
  
                      PTF182.ARC - Contains remote products on a 
                      multidrop line.  It applies to: PCOX/TWO SDLC 
                      version 2.2, PCOX/MULTI SDLC version 2.1, 
                      PCOX/GW-3270 SDLC version 2.2, PCOX/GW-3270 
                      REMOTE-ASSIST version 1.2, and NetWare SNA/GW 
                      version 1.0.  
  
                      VADD1.ARC - Contains the most current Novell 
                      released and approved, disks and drivers. (Listed 
                      on VADD Certification Bulletins)  Also, listed on 
                      the bulletins are the limitations found while testing 
                      these drivers and disks.   
  
  
 
