Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!snorkelwacker.mit.edu!ira.uka.de!math.fu-berlin.de!fub!tmpmbx!netmbx!herbing
From: herbing@netmbx.UUCP (Uwe Herbing)
Newsgroups: comp.periphs.scsi
Subject: Re: <12788@xstor.com>
Message-ID: <2400@netmbx.UUCP>
Date: 13 Jun 91 20:45:16 GMT
References: <12788@xstor.com> <283400137@adaptx1> <1123@venice.SEDD.TRW.COM>
Organization: netmbx, Berlin, Germany
Lines: 23

press@venice.SEDD.TRW.COM (Barry Press) writes:

>In article <283400137@adaptx1> neese@adaptx1.UUCP writes:
>>I wrote SETSCSI just for this purpose.  I put it in a batch file before
>>calling FASTBACK and then call SETSCSI with no arguments afterwards to reset

[stuff deleted]
 
>2.  It looks like SETSCSI conflicts with ASPI4DOS.SYS -- it simply wouldn't
>run reliably unless I removed the device driver.  I suspect that the driver
>was fielding an interrupt that SETSCSI wanted.

[stuff deleted]

>Is there another way to solve these problems I've overlooked?

According to my manual for ASPI4DOS Version 2.1 Rev B, you can give the
ASPI4DOS.SYS driver a /N switch to set the bus on time, e.g.
DEVICE=ASPI4DOS.SYS /N7 should solve your problem.

Greetings Kai
-- 
------------------------------------------------------------------------------- Kai-Uwe Herbing       |   phone 49-30-3126145             |   I don't claim any Weimarer Strasse 28   |                                   |   warranty for tips D-1000 Berlin 12      |   herbing@netmbx                  |   tricks, hints and Fed.Rep.of Germany    |   herbing%netmbx@db0tui6.bitnet   |   suggestions given -------------------------------------------------------------------------------