

NOVELL TECHNICAL INFORMATION DOCUMENT

DOCUMENT PROCESSING INFO:  THIS DOCUMENT REPLACES FYI-M-1602
TITLE:  WINDOWS 3.1 ISSUES:  TROUBLESHOOTING
DOCUMENT ID:  TID800068
DOCUMENT REVISION:  A
DATE:  18AUG94
AUTHOR:  CEREKSON;DPARTRID
ALERT STATUS:  Yellow
DISTRIBUTION:  Public
INFORMATION TYPE:  Symptom Solution
README FOR:  NA
NOVELL PRODUCT CLASS:

Desktop Products

NOVELL PRODUCT and VERSION:

DR DOS 6.0

CATEGORY:

Installation

ABSTRACT:

NA

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

SYMPTOM

DOS applications lock up when attached to a network.  If network drivers
are not loaded everything works fine.

SOLUTION

Machines that have LPT1 ports and are using NE2000 network cards
configured for I/O address 360 have occasionally hung  or had trouble
running DOS applications under Windows 3.1. If this is encountered, try
setting the NE2000 for a lower I/O address.

SYMPTOM

Windows 3.1 will not run after installation.

SOLUTION

There are two different solutions:

1.   Windows 3.1 was installed over a Windows 3.0.  A check of
     IBMDOS.COM and EMM386.SYS show April 1992 file dates.
     During installation the Windows 3.1 setup program will
     actually load Windows 3.1 in Standard Mode.  However, when

     running from the hard disk Windows 3.1 will use the old
     WIN.INI file from Windows 3.0.

     The WIN.INI options LOAD and RUN may affecting performance.
     These two lines tell Windows to execute an application on
     startup in much the same way that an AUTOEXEC.BAT works for
     DR DOS.  Not all old Windows 3.0 applications are compatible
     with Windows 3.1.

     Place a semicolon ";" at the beginning of the RUN and LOAD
     lines of the WIN.INI.  If this does not work rename WIN.INI
     and SYSTEM.INI and reinstall Windows 3.1.  Windows will then
     create new INI files.  You should then be able to compare
     the old and new .INI files.


2.   Any SCSI Busmaster controller that does not support VDS
     (Virtual DMA Services) needs to use SMARTDrive.  If you are
     using SuperPCK remove it with the command "SUPERPCK /U".
     Start SMARTDrive with the command "SMARTDRV".  Information
     similar to the following is displayed:

     Microsoft SMARTDrive Disk Cache version 4.0
     Copyright 1991, 1992 Microsoft Corp.
     Cache size: 1,048,576 bytes
     Cache size while running Windows: 1,048,576 bytes

         Disk Caching Status
     drive     read cache     write cache    buffering
     ----------------------------------------------------------
     A:        yes            no             no
     B:        yes            no             no
     C:        yes            yes            yes
     D:        yes            yes            ---
     For help, type "Smartdrv /?".


     Notice the column labeled buffering.  For each drive that is
     being cached, one of three values is displayed - yes,
     indicating that double buffering is needed; no, indicating
     that double buffering is not needed; or ---, indicating that
     SMARTDrive has not yet determined the necessity of double
     buffering.  If buffering is yes then SMARTDrive should be
     run and the following line should be added to the
     CONFIG.SYS:

     DEVICE=C:\WINDOWS\SMARTDRV.EXE /DOUBLE_BUFFER


SYMTPOM

Windows 3.1 displays an error indicating that the SYSTEM.INI could not
load EMM386.SYS.  The system then returns to DOS.

SOLUTION

The system has a pre - 4/92 EMM386 driver.  If SuperStor is involved make
sure that all copies of EMM386 are the April version.  This includes any
copies that maybe on the uncompressed drive.


SYMPTOM

DOS applications that require LIM/EMS memory do not find any when running
under Windows in Enhanced Mode.

SOLUTION

If DR DOS EMM386.SYS is being used a page frame must be created to enable
Windows to provide EMS support.  To create a page frame with EMM386.SYS
change the /F parameter to /F=AUTO or /F=address.

SYMPTOM

Windows begins but not in Enhanced Mode

SOLUTION

First check available memory with the MEM command.  Windows in Enhanced
Mode will require a minimum of 1024K (1 Megabyte) of available XMS memory
to run. If you are using SuperPCK, the command "SUPERPCK /P" will give you
a listing of the parameters that are currently in use.  The line with /L
indicates the total amount of memory available for lending, the amount
currently lent and the amount remaining to be lent. The available XMS plus
the leding amount should be greater than 1024K. Also make sure that
SUPERPCK is using XMS memory.  This will be indicated by the /EM option.

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