OS/2 Shareware BBS: 36 Tips/36-Tips.zip/alltips.zip/MKCM04.FAX

Text File | 1994-12-10 | 5KB | 227 lines

Covers common problems and fixes         8/12/94

file name

OSMKCM04.FAX




TITLE

Common Problems and Solutions

(make sure the latest com.sys and vcom.sys are installed)



DESCRIPTION OF SYMPTOMS

1.sys1201    driver not installed

2. "comport not available" or "IRQ not available"

3. Can not open a DOS or Windows application.

4. sys3175 and sys3176

5. sys0049

6. sys0099 or sys1798

7. application does not recognize com port

8. mode command causes session to hang



SUMMARY OF RESOLUTION

1. Path statements & physical devices

2. IRQ conflict or incorrect hardware configuration

3. Check path commands

4. DOS settings and apars.

5. An attached device problem

6. The port is being used by another application

7. aplication settings, configuration

8.  IRQ conflict or apar



DETAILS OF RESOLUTION

1.sys1201 driver not installed error can be caused by a number
of problems.

    A. the path statement for the driver in the "CONFIG.SYS" file
may be incorrect.

    B. when com.sys does not install

        a. it may indicate that the physical ports do not exist.

        b. physical ports are not configured correctly in bios
(reference configuration for             MCA) .

        c. physical ports may be defective or incorrectly setup.

    C. the driver specified is defective or non existant.



2. IRQ conflict or incorrect hardware configuration

    IRQ conflicts may be the cause of many mysterious problems,
they have been known to         result in problems unrelated to the
immediate point of conflict. Eliminating IRQ conflicts         can be
acomplished by creating a table of rows and columns. The rows
represent each slot         of the machine and the columns can be
represented by "Card Type"  "IRQ Level"   "I/O         Address"  "DMA
Address"    "Manufacturer Info". This information can be
entered, saved     and later updated as the configuration cahnges.
This technique will save time and ensure         configuration
integrity. The actual settins must be obtained from analyzing
the switch         settings on the adapter, the use of the adapter's
manual is required. Each adapter must be         assigned to a unique
IRQ level and I/O port address. DMA address' should be unique
also.



3. Can not open a DOS or Windows application.

    1. Make sure that the latest communications drivers have been
installed.

    2. Make sure the application has been installed correctly.

        A. Path commands may be incorrect.

        B. Applications installed under real DOS may need to be
rinstalled under OS/2.



4. sys3175 and sys3176

    1. If the application is an OS/2 application contact the vendor
of the application.

    2. Sometimes adjusting the DOS_HIGH and DOS_UMB adjustments
remedy this             problem.

    3. Running the application in full screen can also help.

    4. Slowing down the processor and disableing external cashe on
some fast machines has         also been known to help.

    5. XR6200 includes fixes for computers with pentium, DX,
processors exhibiting this         problem. Check to see current apars
listed for specific applications and the error message.



5. sys0049

This error normally indicates a non functional attached device.
Make sure the port is correctly installed by issuing the MODE
command to the port in question. If the mode command functions
normally use the use the "spurious interrupt" which is passed on
the command line of the com.sys device driver in the
"config.sys". Also make sure the hardware is configured
correctly and functioning optimally.



6. sys0099 or sys1798

This normally means the port requested is being accessed by
another application. Some applications automatically take all
available system resources that are available. If the problem
occurs, view the task list and note applications rthat are
running. Verify that these applications are not or should not
have the port in use. OS/2 provides a DOS property in the DOS
settings to hide com ports from applications. Set the COM_SELECT
property to none or the specific port being used; eg: COM_SELECT
= COM1.



7. Application does not recognize com port

    1. Rule out the posibility of IRQ conflicts. (When in doubt,
check again!)

    2. Make sure the application port and line settings are
configured correctly.

    3. If using com3 and com4 or com1 and com2 with non default
configuration settings on         an ISA machine, check the following:

        a. verify the command line parameters on the "COM.SYS" device
driver in the             "CONFIG.SYS" file are correct.

    4. For MS Windows applications make sure the Windows port setup
is correct.



8. Mode command causes session to hang

    1.This can be caused by IRQ conflicts (see sections on IRQ
conflict and resolution).

    2. Also check the APAR data base, there have been instances of
defective hardware that         may result in similar results.















LIMITATIONS



























12/31/99