                      Troubleshooting Tips
                            Hardware



                             PM3011



1.  LEDS FLASH ALTERNATELY 1-4, THEN 5-8 (Fatal Trap)
A major component on the controller has failed.  First, disconnect
all memory expansion from the controller and retry.  If Fatal Trap
disappears, there may be a problem with the memory expansion
card(s).  If Fatal Trap still exists, make sure controller is
seated properly in the I/O slot or try another slot.  This failure
can be only DPT related.  Hard drives, drive cables, or
motherboards cannot cause this failure.  Make sure the correct
firmware is installed on the controller:

      /70A ESDI - FW-0019-xxx-xx   /75E ESDI - FW-0040-xxx-xx
      /60A RLL  - FW-0013-xxx-xx   /65E RLL  - FW-0044-xxx-xx
      /50A MFM  - FW-0013-xxx-xx   /55E MFM  - FW-0044-xxx-xx

NOTE:  If Fatal Trap exists with any ASIC (/75E, /65E, /55E) and an
8MB memory configuration, make sure that the MM3011/x is installed 
on the MX3011/x and not directly on the controller.  Updated
firmware to solve this anomaly is available from Technical Support,
or you can download the latest firmware from the Technical Support
BBS.  Firmware revision FW-00xx-006C or later is required to
support newer MM401x or MX401x memory cards.


2.  LEDS STAY ON SOLID AT POWER UP
Repeat steps shown in example 1.  Also, ensure that your power
supply is adequate enough.  A minimum recommended wattage rating
in a typical 386/486 with a DPT Controller and a few I/O boards is
230 watts.  If problem persists, the controller must be returned to
be checked out for possible defects.

NOTE:  Check the controller for two parts that can possibly cause
this problem:

     a. Saronix Crystal - Look for a "tin can" like part with the
        word "Saronix" and the rating of 16MHz on it.  This
        vendor crystal may be causing the problem....return to
        DPT for free upgrade.
     b. PAL Version 106B - In the bottom left hand corner of the
        disk controller, there will be a PAL chip in the second
        row labeled with white grease paint as "106x" where "x"
        can be the letters A through D.  If the PAL on your
        controller is labeled either "106A" or "106B", return to
        DPT for a free upgrade.


3.  NO LEDS AT POWER UP
Repeat steps shown in example 2.


4.  "ERROR INITIALIZING HARD DISK CONTROLLER" or "HDC ERROR"
This message comes from your system BIOS and usually means that the
controller was not recognized by the motherboard. 

                      Check Controller LED Display:

If the pattern of the LED Display is similar to any of the patterns
listed in the Troubleshooting Tips, proceed to that tip and follow
the instructions.


                     Other hardware in your system?

Make sure the DPT Controller is the only hard disk controller that
is in your system.  You may have another hard disk controller in
your system if it is disabled (in order to use another port on that
card).  This may not be possible on the Compaq
Hard/Floppy/Serial/Parallel card.  For information on Disk
Duplexing (two controllers working in the same system) please call
DPT Technical Support. 

5.  "HARD DISK 0 FAILURE"
This message comes from your system BIOS.  This is a normal message
during a new hard disk installation, or when installing the
PM3011/xx on a new or previously formatted hard disk.  The hard
disk must be low level formatted with the DPT format utility.  Hit
F1 to continue booting DOS from your floppy and proceed with
format.

6.  CONTROLLER WORKS, BUT NETWORK INTERFACE CARD NO LONGER WORKS
A common cause of this is a conflict of memory addresses between
the BE3011 BIOS Expansion ROM and another interface card occupying
address C8000.  Most interface cards that occupy memory address
ranges offer alternate choices such as C0000, C4000, D0000, etc. 
Consult your documentation on the interface card and change the
memory address to an alternate location.

              Changing the BE3011 address on the PM3011

On all ASIC (3011E/75/65/55) controllers an alternate address for
the BE3011 can be selected.  Place a jumper on location Y18 to
change the address from the default C8000 to the alternate D8000.

7.  DPTFMT REPORTS THAT THE DISK IS NOT ATTACHED CORRECTLY
Make sure that the ribbon cables attached to the controller are all
red stripe up.  If your control cable (34 pins) has a twist, make
sure the end with a twist is connected to the hard disk and that
the hard disk is set for drive select 2.  If the control cable is
a straight cable (no twist), the hard disk should be set for drive
select 1.  If there is only one hard disk in the system, it must
have a terminating resistor.

For a two hard disk installation with a twist cable, set both
drives for drive select 2, and install a terminating resistor on
the hard disk at the end of the chain (the one connected to the
twisted connector).  The resistor on the disk on the middle
connector (no twist) must be removed.  Make sure the twist cable
you are using has the twist located on the opposite end of the red
strip (pin 1).  If the twist is close to the red stripe (pin 1),
then it will not work as this is a floppy drive cable.

For a two hard disk installation with a straight cable, the hard
disk on the end of the chain must be set for drive select 1, and
the hard disk on the middle connector must be set for drive select
two.  Again, the hard disk on the end of the chain must be
terminated, and the hard disk on the middle connector must not be
terminated.


NOTE: Some ESDI hard drives have a "spin up on command" option. 
This option is jumper or switch oriented and must be set to "spin
up on powerup".  On the HP 97548E drive, this is done by switching
switch 1 to off (0).

8.  HARD DISK IN YOUR SYSTEM IS NOT ON DPTFMT LIST
This may occur when a new model hard disk is released and the
software has not be updated or you have an older release of the DPT
Format Utility.  You can download a current version of DPTFMT.EXE
from the DPT BBS, or to format the drive using the software you
have, hit ESC until you are back at the DOS prompt.  Start the
format utility by entering DPTFMT /CUSTOM.  When you get to the
drive manufacturers list, hit F8 for CUSTOM PARAMETERS.  The
controller will go out to the drive and read the parameters (heads,
cylinders, and sectors) and you will be prompted to enter in two
fields of information, depending on whether you are using MFM, RLL,
or ESDI.  These two parameters may be found in your hard disk
reference guide or you can call DPT Technical Support for
assistance.

9.  FLOPPY ACCESS LIGHT STAYS ON CONTINUOUSLY
Floppy drive will still operate normally.  To get the access light
to function properly, remove the jumper labeled I/U (in use) from
the floppy drive.  This procedure is not possible on the TEAC 3.5
inch 1.44MB drive as there is no I/U jumper.  This procedure should
work on most other floppy drives.

10. DRIVE CAPACITY LESS THAN EXPECTED
BE3011 BIOS Expansion Chip may be required.  If you are installing
an operating system that is BIOS dependant for disk parameters, and
your setup does not contain parameters for your drive in the
standard 1-47 drive type range, a BE3011 must be installed.  Find
your operating system on the chart below to see if a BE3011 is
needed:

Operating System             Needs BIOS Expansion
-------------------------------------------------
Interactive                        YES
MS/PC DOS                          YES
Novell 2.1x, 386                   YES
OS/2                               YES
PCMOS                              YES
Concurrent DOS                     YES
PICK                               YES
Microport UNIX                      NO
SCO UNIX                            NO
Xenix                               NO
QNX                                 NO
THEOS                               NO
Novell 2.0x                          *

* Novell 2.0x will not operate with the BE3011.  The DUB14 from
Golden Bow Systems is recommended and like the BE3011, will socket
directly onto the PM3011 controller.

If your BIOS has User Definable Parameters, you can use this
function instead of the BE3011 chip.  User Definable Parameters are
usually drive type 47, 48, or 49 in your setup and the drive
cylinders, heads, and sectors per track can be manually entered by
the user.  If your BIOS has this feature, follow these steps:

    a.  Format the drive with DPTFMT or, if already formatted
        with DPTFMT, run Calculate Best Drive Parameters.
    b.  Select your operating system from the list.
    c.  If your operating system is one of those that requires a
        BIOS expansion and your system BIOS has User Definable
        Parameters, select F10 on the Drive Type Screen following
        the selection of the operating system.  If F10 does not
        appear on screen, call DPT Support.
    d.  Write down the BEST CONFIGURATION parameters shown on the
        next screen.
    e.  The system will then reboot.  Enter your system setup
        mode.
    f.  Select your User Definable Drive type, and enter in the
        parameters
        given to you from DPTFMT (BEST CONFIGURATION).
    g.  Save your setup, and reboot system.
    h.  Proceed with operating system installation.


11.  DPTFMT CANNOT SEE BE3011 DRIVE TYPES
Check the revision of DPTFMT, located in the upper right hand
corner of the screen.  If it is revision 3C, download a new version
from the BBS.  If the revision number is anything else besides 3C,
check for:

    a.  Proper jumper installation at location Y7.
    b.  BE3011 installation message w/ diagnostics.  If this
        message does not appear during POST, the BE3011 may be
        bad or Y7 not installed.
    c.  Conflicts at the BE3011 address range of C8000.  This
        address can be taken up by network interface cards, tape
        backup cards, VGA video boards, etc.  If you have one of
        these boards, try removing all of them to confirm a
        conflict, then readdress the offending board around the
        BE3011 address.
    d.  If you cannot readdress the offending board, or if you
        are running Shadow BIOS on your motherboard, relocate the
        BE3011 address to D8000.  This can only be done on the
        PM3011E/xx series controllers.

12.  CONTROLLER LEDS LOCK UP WITH LEDS 1, 2, 4, AND 7 ON SOLID
This failure, or a similar LED display failure under heavy I/O, may
be due to downlevel firmware.  Firmware revision FW-004x-006A
exhibited this problem frequently.  Contact DPT Technical Support
for a free upgrade or download the firmware from the Technical
Support BBS.

13.  CONTROLLER LEDS 1 AND 2, OR 1 AND 3 BLINK ON AND OFF
This indicates a Bus Address Failure and the controller may be
faulty.  Hard drives and motherboards can cause this failure, but
the controller should be checked out by DPT.

14.  DPTFMT SAYS NO CONTROLLER FOUND, LEDS 1 AND 7 OR 1,7,8 SOLID
This usually indicates a conflict at IRQ14, which is reserved for
hard disk controllers.  Ensure that there are no other disk
controllers installed in the system.  This error can occur even if
there is a "disabled" controller in the system as some disk
controllers only disabled the base address, and not the IRQ.




                             PM2001


1.  DPTFMT REPORTS THAT THERE IS NO DRIVE ATTACHED
Ensure the SCSI cable is good and correctly installed.  Make sure
the drive is spinning and that the SCSI bus is properly terminated. 
If you unsure about termination, contact DPT Technical Support.

2.  DPTFMT SAYS THERE ARE 7 DRIVES ATTACHED, BUT ONLY 1 IS.
There is a SCSI ID conflict somewhere on the bus.  The PM2001 is
shipped from DPT default at SCSI ID 7.....make sure that there are
no hard drives at this SCSI ID number.

NOTE: Most Fujitsu hard disks come set for SCSI ID7 as default. 
The default SCSI ID for the DPT controller is also 7.  Make sure
the drive gets reset to SCSI ID0 (standard for first bootable hard
disk on the SCSI bus).

3.  DPTFMT REPORTS DRIVE NOT READY TRYING TO CONFIGURE DRIVE 0
    OR 1.
The drive may not appear to be emulated.  In order to configure
drive 0 or drive 1, the drive must be emulated.  In order for the
drive to be emulated, the controller must be at address 1F0 and
IRQ14 (default).  If the controller is at an alternate address or
interrupt, you must hit F3 and enter the actual SCSI ID number of
the drive you are trying to configure as "emulation"is not possible
of the controller is set for an address or interrupt other than
Base I/O 1F0 or IRQ14.  One other possibility (PM2012 only) is that
the SCSI ID number defined in the EISA configuration does not match
the actual SCSI ID number of the  drive.  Make sure that it does. 
Lastly, the drive just may be off line.  The hard disk can be
identified in the SCSI DRIVE ROSTER SCREEN in DPTFMT even if the
drive is off line or not spinning.

4.  DPTFMT REPORTS DRIVE 4 NOT READY.
This is a bug in DPTFMT.  Instead of entering in the SCSI ID number
at the ENTER THE NUMBER OF DRIVE TO CONFIGURE screen, select drive
0 or drive 1.  Or, download the latest DPTFMT.EXE from the
Technical Support BBS.

5.  DPTFMT SEES TAPE AND CDROM DRIVE, BUT OS CANNOT ACCESS IT
The PM2001 controller and DPTFMT can will identify and standard
SCSI device that is properly attached to it, however, getting your
operating system to recognize is another thing entirely.  Download
SUPDEV.TXT or read Bulletin 24 on the Technical Support BBS for a
list of non-hard disk devices and the drivers needed to support
them on your operating system.

6.  SCSI CABLE SMOKES AND BURNS RIGHT DOWN THE MIDDLE
The SCSI cable was installed backwards.  Most drives and disk
controllers have variable resistors (DPT controllers use a
thermistor) to prevent this from happening when a SCSI cable is
incorrectly installed.  However, some hard drives do not have this
feature and the +5 volt line on the SCSI cables just gets hot and
melts the plastic around it.

7.  SMARTROM MESSAGE SHOWS DURING POST, FDISK SEES SMALL DRIVE
Make sure current firmware is installed on the PM2001.  Minimum
firmware requirement for SmartROM support is FW-0062-003F.



                             PM2011


1.  DPTFMT REPORTS THAT THERE IS NO DRIVE ATTACHED
Ensure the SCSI cable is good and correctly installed.  Make sure
the drive is spinning and that the SCSI bus is properly terminated. 
If you unsure about termination, contact DPT Technical Support.

2.  DPTFMT SAYS THERE ARE 7 DRIVES ATTACHED, BUT ONLY 1 IS.
There is a SCSI ID conflict somewhere on the bus.  The PM2011 is
shipped from DPT default at SCSI ID 7.....make sure that there are
no hard drives at this SCSI ID number.
NOTE: Most Fujitsu hard disks come set for SCSI ID7 as default. 
The default SCSI ID for the DPT controller is also 7.  Make sure
the drive gets reset to SCSI ID0 (standard for first bootable hard
disk on the SCSI bus).

3.  DPTFMT REPORTS DRIVE NOT READY TRYING TO CONFIGURE DRIVE 0
    OR 1.
The drive may not appear to be emulated.  In order to configure
drive 0 or drive 1, the drive must be emulated.  In order for the
drive to be emulated, the controller must be at address 1F0 and
IRQ14 (default).  If the controller is at an alternate address or
interrupt, you must hit F3 and enter the actual SCSI ID number of
the drive you are trying to configure as "emulation"is not possible
of the controller is set for an address or interrupt other than
Base I/O 1F0 or IRQ14.  One other possibility (PM2012 only) is that
the SCSI ID number defined in the EISA configuration does not match
the actual SCSI ID number of the  drive.  Make sure that it does. 
Lastly, the drive just may be off line.  The hard disk can be
identified in the SCSI DRIVE ROSTER SCREEN in DPTFMT even if the
drive is off line or not spinning.

4.  DPTFMT SEES TAPE AND CDROM DRIVE, BUT OS CANNOT ACCESS IT
The PM2001 controller and DPTFMT can will identify and standard
SCSI device that is properly attached to it, however, getting your
operating system to recognize is another thing entirely.  Download
SUPDEV.TXT or read Bulletin 24 on the Technical Support BBS for a
list of non-hard disk devices and the drivers needed to support
them on your operating system.

5.  SCSI CABLE SMOKES AND BURNS RIGHT DOWN THE MIDDLE
The SCSI cable was installed backwards.  Most drives and disk
controllers have variable resistors (DPT controllers use a
thermistor) to prevent this from happening when a SCSI cable is
incorrectly installed.  However, some hard drives do not have this
feature and the +5 volt line on the SCSI cables just gets hot and
melts the plastic around it.

6.  LEDS FLASH ALTERNATELY 1-4, THEN 5-8 (Fatal Trap)
A major component on the controller has failed.  First, disconnect
all memory expansion if there is any installed including the CM401x
from the controller and retry.  If Fatal Trap disappears, there may
be a problem with the memory expansion card(s)or the Cache Module
itself or possibly the memory expansion card(s) or Cache Module
were not properly seated on the PM2011 controller.  If the Fatal
Trap still exists, make sure controller is seated properly in the
I/O slot or try another slot.  This failure can be only DPT
related.  Hard drives, drive cables, or motherboards cannot cause
this failure.  Make sure the correct firmware is installed on the
controller (FW-0082-00xx-xx).

7.  LEDS STAY ON SOLID AT POWER UP
Repeat steps shown in example 6.  Also, ensure that your power
supply is adequate enough.  A minimum recommended wattage rating
in a typical 386/486 with a DPT Controller and a few I/O boards is
230 watts.  If problem persists, the controller must be returned to
be checked out for possible defects.


8.  "ERROR INITIALIZING HARD DISK CONTROLLER" or "HDC ERROR"
This message comes from your system BIOS and usually means that
the controller was not recognized by the motherboard. 

                      Check Controller LED Display:

If the pattern of the LED Display is similar to any of the
patterns listed in the Troubleshooting Tips, proceed to that tip
and follow the instructions.


                     Other hardware in your system?

Make sure the DPT Controller is not conflicting with any other disk
controller that is in your system.  You may have another hard disk
controller in your system if it is disabled (in order to use
another port on that card) or enabled at secondary addresses,
IRQ's, and DMA channels provided your operating system and/or
software driver supports multiple disk controllers.  For
information on Disk Duplexing (two controllers working in the same
system) please call DPT Technical Support. 


9.  "HARD DISK 0 FAILURE"
This message comes from your system BIOS.  This is a normal
message during a new hard disk installation and will disappear
after running the DPTFMT program to set up the disk drive.

10.  CONTROLLER LEDS 1 AND 2, OR 1 AND 3 BLINK ON AND OFF
This indicates a Bus Address Failure and the controller may be
faulty.  Hard drives and motherboards can cause this failure, but
the controller should be checked out by DPT.

11.  DPTFMT SAYS NO CONTROLLER FOUND, LEDS 1 AND 7 OR 1,7,8 SOLID
This usually indicates a conflict at IRQ14, which is reserved for
hard disk controllers.  Ensure that there are no other disk
controllers installed in the system or make sure the other disk
controllers are at different addresses, interrupts, and DMA
channels.  This error can occur even if there is a "disabled"
controller in the system as some disk controllers only disabled the
base address, and not the IRQ.

12.  DATA CORRUPTION OCCURS ONLY WHEN MEMORY IS INSTALLED ON 2011
Make sure current firmware is installed on the controller card. 
Firmware revision FW-0082-002B exhibited data corruption problems
when cache memory was installed.

13.  CONTROLLER LOCKS WITH DIFFERENT LEDS SOLID IN DPTFMT 
The motherboard that the PM2011 controller is installed in my not
support ISA Bus Mastering (data transfer to and from disk
controller via a motherboard DMA channel).  There is no industry
specification that defines ISA Bus Mastering (unlike EISA),
therefore different motherboards do it differently which can cause
problem.  Try putting the PM2011 in PIO non-Bus Master mode by
removing Y24.

14.  WHENEVER A KEY IS HIT DURING "WAITING FOR DEVICE TO SPIN UP"
     THE MACHINE NEVER BOOTS YET IF THE MESSAGE TIMESOUT, IT WILL
A key is being hit too quickly.  The SmartROM is waiting for the
SCSI device to go ready, and is also negotiating for ASYNC or SYNC
transfers.  If the device is consistently booting after the
standard 30 second timeout, but not when a key is pressed, then the
device is slow to go ready.

15.  DPTFMT DOES NOT SEE THE PM2011 CONTROLLER AT IRQ15
Download the latest DPTFMT.EXE from the Technical Support BBS. 
Versions of DPTFMT prior to 3K would not see IRQ15 disk
controllers.



                             PM2012


1.  DPTFMT REPORTS THAT THERE IS NO DRIVE ATTACHED
Ensure the SCSI cable is good and correctly installed.  Make sure
the drive is spinning and that the SCSI bus is properly terminated. 
If you unsure about termination, contact DPT Technical Support.

2.  DPTFMT SAYS THERE ARE 7 DRIVES ATTACHED, BUT ONLY 1 IS.
There is a SCSI ID conflict somewhere on the bus.  The PM2012 is
shipped from DPT default at SCSI ID 7.....make sure that there are
no hard drives at this SCSI ID number.

NOTE: Most Fujitsu hard disks come set for SCSI ID7 as default. 
The default SCSI ID for the DPT controller is also 7.  Make sure
the drive gets reset to SCSI ID0 (standard for first bootable hard
disk on the SCSI bus).

3.  DPTFMT REPORTS DRIVE NOT READY TRYING TO CONFIGURE DRIVE 0
    OR 1.
The drive may not appear to be emulated.  In order to configure
drive 0 or drive 1, the drive must be emulated.  In order for the
drive to be emulated, the controller must be at address 1F0 and
IRQ14 (default).  If the controller is at an alternate address or
interrupt, you must hit F3 and enter the actual SCSI ID number of
the drive you are trying to configure as "emulation"is not possible
of the controller is set for an address or interrupt other than
Base I/O 1F0 or IRQ14.  One other possibility is that the SCSI ID
number defined in the EISA configuration does not match the actual
SCSI ID number of the  drive.  Make sure that it does if you want
an emulated drive.  Lastly, the drive just may be off line.  The
hard disk can be identified in the SCSI DRIVE ROSTER SCREEN in
DPTFMT even if the drive is off line or not spinning.
4.  DPTFMT SEES TAPE AND CDROM DRIVE, BUT OS CANNOT ACCESS IT
The PM2001 controller and DPTFMT can will identify and standard
SCSI device that is properly attached to it, however, getting your
operating system to recognize is another thing entirely.  Download
SUPDEV.TXT or read Bulletin 24 on the Technical Support BBS for a
list of non-hard disk devices and the drivers needed to support
them on your operating system.

5.  SCSI CABLE SMOKES AND BURNS RIGHT DOWN THE MIDDLE
The SCSI cable was installed backwards.  Most drives and disk
controllers have variable resistors (DPT controllers use a
thermistor) to prevent this from happening when a SCSI cable is
incorrectly installed.  However, some hard drives do not have this
feature and the +5 volt line on the SCSI cables just gets hot and
melts the plastic around it.

6.  LEDS FLASH ALTERNATELY 1-4, THEN 5-8 (Fatal Trap)
A major component on the controller has failed.  First, disconnect
all memory expansion if there is any installed including the CM401x
from the controller and retry.  If Fatal Trap disappears, there may
be a problem with the memory expansion card(s)or the Cache Module
itself or possibly the memory expansion card(s) or Cache Module
were not properly seated on the PM2012 controller.  If the Fatal
Trap still exists, make sure controller is seated properly in the
I/O slot or try another slot.  This failure can be only DPT
related.  Hard drives, drive cables, or motherboards cannot cause
this failure.  Make sure the correct firmware is installed on the
controller:

       PM2012A: FW-0055-00xx-xx   PM2012B: FW-0068-00xx-xx


7.  LEDS STAY ON SOLID AT POWER UP
Repeat steps shown in example 6.  Also, ensure that your power
supply is adequate enough.  A minimum recommended wattage rating
in a typical EISA 486 with a PM2012 and a few I/O boards is 265
watts.  If problem persists, the controller must be returned to be
checked out for possible defects.

8.  LEDS MOVE BACK AND FORTH IN A FAST SWEEPING MOTION
The PM2012 controller has not been initialized by the EISA
motherboard.  Run the motherboard EISA Configuration Utility and
install the .CFG file for your appropriate EISA cards.

9.  "ERROR INITIALIZING HARD DISK CONTROLLER" or "HDC ERROR"
This message comes from your system BIOS and usually means that
the controller was not recognized by the motherboard. 

                      Check Controller LED Display:

If the pattern of the LED Display is similar to any of the
patterns listed in the Troubleshooting Tips, proceed to that tip
and follow the instructions.

                     Other hardware in your system?

Make sure the DPT Controller is not conflicting with any other disk
controller that is in your system.  You may have another hard disk
controller in your system if it is disabled (in order to use
another port on that card) or enabled at secondary addresses an
IRQ's provided your operating system and/or software driver
supports multiple disk controllers.  For information on Disk
Duplexing (two controllers working in the same system) please call
DPT Technical Support. 

10.  "HARD DISK 0 FAILURE"
This message comes from your system BIOS.  This is a normal
message during a new hard disk installation and will disappear
after running the DPTFMT program to set up the disk drive.

11.  CONTROLLER LEDS 1 AND 2, OR 1 AND 3 BLINK ON AND OFF
This indicates a Bus Address Failure and the controller may be
faulty.  Hard drives and motherboards can cause this failure, but
the controller should be checked out by DPT.

12.  DPTFMT SAYS NO CONTROLLER FOUND, LEDS 1 AND 7 OR 1,7,8 SOLID
This usually indicates a conflict at IRQ14, which is reserved for
hard disk controllers.  Ensure that there are no other disk
controllers installed in the system or make sure the other disk
controllers are at different addresses, interrupts, and DMA
channels.  This error can occur even if there is a "disabled"
controller in the system as some disk controllers only disabled the
base address, and not the IRQ.  This problem is frequently seen on
embedded IDE and SCSI controllers built into the motherboard.

13.  DATA CORRUPTION OCCURS ONLY WHEN MEMORY IS INSTALLED ON 2012
     (PM2012B CONTROLLER ONLY)
Make sure current firmware is installed on the controller card. 
Firmware revision FW-0068-002B exhibited data corruption problems
when cache memory was installed.

14.  WHENEVER A KEY IS HIT DURING "WAITING FOR DEVICE TO SPIN UP"
     THE MACHINE NEVER BOOTS YET IF THE MESSAGE TIMESOUT, IT WILL
A key is being hit too quickly.  The SmartROM is waiting for the
SCSI device to go ready, and is also negotiating for ASYNC or SYNC
transfers.  If the device is consistently booting after the
standard 30 second timeout, but not when a key is pressed, then the
device is slow to go ready.

17.  DPTFMT DOES NOT SEE THE PM2012 CONTROLLER AT IRQ15
Download the latest DPTFMT.EXE from the Technical Support BBS. 
Versions of DPTFMT prior to 3K would not see IRQ15 disk
controllers.

18.  SMARTROM MESSAGE SHOWS DURING POST, FDISK SEES SMALL DRIVE
     (PM2012A ONLY)
Make sure current firmware is installed on the PM2012A.  Minimum
firmware requirement for SmartROM support is FW-0055-003F.
19.  ECU ALWAYS PUTS 2012 AT SECONDARY ADDRESS AND IRQ
Most EISA Configuration Utilities were designed not to allow
address and IRQ conflicts.  If the ECU is always putting the 2012
controller at secondary addresses and IRQs, that means that the ECU
is seeing another disk controller installed.

NOTE: Some ECU's will not look for a controller IRQ conflict if the
base address is disabled, which can cause some problems outlined in
Tip 12 above.

20.  SMARTROM MESSAGE APPEARS TWICE WITH 2 2012'S INSTALLED
Disable the SmartROM on either controller....one SmartROM can
handle multiple DPT controllers.

21.  SECONDARY 2012 HANGS WITH LED 8 SOLID DURING POST (COMPAQ
     MACHINE ONLY, PM2012B CONTROLLER ONLY)
A new EISA Configuration File for the PM2012B is needed.  Download
the latest one from the Technical Support BBS.

22.  ECU WARNS THAT THE 2012 IS CONSUMING TOO MUCH POWER
     (MICRONICS MOTHERBOARD ONLY)
This is a bug in the Micronics motherboard EISA Configuration File. 
The motherboard .CFG reports that the motherboard has a maximum
support of 2000 milliamps, which equates to 2 amps.  Most EISA
motherboards have a maximum support for up to 20000 milliamps,
which equates to 20 amps.  Since most EISA cards consume up to 5
amps each, this must be an error in the motherboard configuration
file as 2 amps is just way to low.
