
ķ

ذ  Moscow 1995  
ذذ
ذذذذ
ذذذذذ
ذذذذ
ذذذذذذ
ذذذذذذذ
ذذذذذذذذ
ذذذذذذذ
ذذذذذ
ذذذذ
ذذذ
ذ
ذ
(c) Dmitry Mostovoy  ذ


ͼ



	                INCOMPATABILITY REPORT

  The following is a list of equipment and programs which have been
found to be incompatible with ADinf. It also recommends ways to come
round such problems.

1.
  ASPI2DOS.SYS DRIVER

SYMPTOM       ADinf versions earlier than 9.25 hang up on starting.

CAUSE         Due to the bug in Int 13h handler in ASPI2DOS.SYS,
              on machines with one physical disk, in attempting to
              execute Int 13h for the second disk, the driver hangs up
              instead of normal returning with Carry Flag.

REMEDY        Use ADinf version 9.25 or higher.

2.
  SCSI-DISKS WITH LOADABLE DRIVERS

SYMPTOM       After scanning the disk,  ADinf hangs up while writing the
              diskinfo tables and reports `10% written'.

CAUSE         When the SCSI-hard disk is managed by its loadable
              driver, ADinf cannot access the disk directly via BIOS.

REMEDY        In the ADinf menu, specify Int 13h as the ACCESS TYPE for
              all drives (though virus protection is less reliable) or
              disable the SCSI-hard disk driver, if this is possible.

3.
   ADinf 9.12 AND HIGHER VERSIONS

SYMPTON       On certain machines with rare types of BIOS, ADinf may hang 
              up, printing "OPENING DRIVE C" in the message box at the 
              screen bottom, or display false alarms. 
              
CAUSE         Beginning from version 9.12, ADinf uses a special mechanism 
              to trap the viruses hiding at the hard disk controller level.  
              This mechanism may conflict with certain, particularly, older 
              BIOS versions.

REMEDY        Run ADinf with the command switch -76.  Please inform us the
              version number of your BIOS (8 bytes at the address F000:FFF5)
              for updating the ADinf internal incompatiblity table to avoid
              conflicts with such a BIOS.


