Path: utzoo!attcan!uunet!cbmvax!jesup
From: jesup@cbmvax.UUCP (Randell Jesup)
Newsgroups: comp.sys.amiga
Subject: Re: 2090A problem
Message-ID: <5553@cbmvax.UUCP>
Date: 22 Dec 88 04:54:33 GMT
References: <2045@van-bc.UUCP>
Reply-To: jesup@cbmvax.UUCP (Randell Jesup)
Organization: Commodore Technology, West Chester, PA
Lines: 25

In article <2045@van-bc.UUCP> lphillips@lpami.wimsey.bc.ca (Larry Phillips) writes:
>In <5528@cbmvax.UUCP>, jesup@cbmvax.UUCP (Randell Jesup) writes:
>>	If you have 1.3 KS roms, then the driver in the expansion drawer isn't
>> needed, since it is auto-started from the ROM.
>
>Whoops! Are you saying that the driver itself is in the ROMs on the 2090A?
>Or is it that the driver icon only is not needed?

	I should have been more specific.  The driver is loaded from the ROM
ON THE 2090A.  If you have 1.3 KS roms, and a 2090A, and have the 2090A
roms in their sockets, then you don't need the driver (or icon) in the
expansion drawer.  If you have 1.2 KS, you need the driver in the expansion
drawer AND need to remove the roms from the 2090A.

>If the driver is loaded from the ROMs themselves, does this mean I should
>stop waiting for the next revision of the driver to start on a streaming tape
>handler, and just go for a different brand of controller with a driver that
>will handle the SCSI command passthrough?

	I have no idea what will be done about new roms/eproms for the 2090a
if/when we rev the driver.  Not my end of the business.  You can always remove
them and put the new driver in the expansion drawer, and boot from floppy/RAD.

-- 
Randell Jesup, Commodore Engineering {uunet|rutgers|allegra}!cbmvax!jesup