Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!sun-barr!cs.utexas.edu!csd4.milw.wisc.edu!srcsip!coltrane!carpent
From: carpent@coltrane.SRC.Honeywell.COM (Todd Carpenter)
Newsgroups: comp.sys.amiga.tech
Subject: Re: A2090A autoboot
Message-ID: <26457@srcsip.UUCP>
Date: 27 Jul 89 12:56:01 GMT
References: <11327@mcdphx.phx.mcd.mot.com>
Sender: news@src.honeywell.COM
Lines: 24
In-reply-to: stan@teroach.phx.mcd.mot.com's message of 26 Jul 89 16:07:01 GMT


In article <11327@mcdphx.phx.mcd.mot.com> stan@teroach.phx.mcd.mot.com (Stan Fisher) writes:

!  I have the 2090A timeout problem on boot up, my Micropolis 158meg SCSI drive
!  isn't quite done initializing when the 2090A times out and want to boot
!  something.  I know if I could find the right location(s) in the firmware on
!  the 2090A, I could patch them on the Data I/O and burn a new Eprom.
 
  Here, here!  No offense, but I wasn't impressed with the programmer who
  limited the A2090a so much...

  Another thing that would be nice is for it to poll successive devices until
  it *does* find something to boot from - I detest having to boot from my ST506
  when I have a fast SCSI available, and only use the ST506 for archival
  purposes.  However, I bet this is a *bit* more complicated than changing a
  couple delay values.  Ah well, I can dream on about a new release of ROMs
  that fix these ailments...

  (however, aside from a retarded programmer (or whoever wrote the specs), I am
  very pleased.  I *can* plug in my ST506 drives, plus the SCSI, I have
  incredible performance (once it finally gets up), and I have the option of
  unix, once it is released.)

-Todd C.