boi@richsun.cpg.trs.reuter.com (Ken Boi) (03/22/91)
The setup:: My brother has the following - Amiga 500, Bodega Bay Expansion Unit from California Access, 1.3 Autoboot ROM, 1M CHIP, Supra 2M memory board, Xetec Fastrack hard drive controller board, and a Quantum 105M HD. The problem: Upon power up or warm reboot, the startup-sequence code does not start executing until after about a 40 second delay, then there is the 30-40 second startup-sequence period. What is occuring is about a 80-90 second autoboot period with no special startup-sequence entries. The question is why the initial 40 second period is occurring? I have an A2000 and after the system does its hardware checks, the startup sequence begins. On my system, the initial check is maybe 10 seconds and then a 30 second startup (i.e. approximately 40 second total autoboot period). If he boots off of a Workbench disk (instead of from the HD) the same initial delay occurs. After the autoboot is finished, everything works fine and disk accesses are fast. He got the Xetec controller from me and I can vouch that it worked fine for me in the A2000. One point worth mentioning, is that he has only one SCSI HD attached (i.e. the Quantum), and it is set to Unit 6. A call to California Access failed to give a real solid answer. They said it may be that the system is performing autoconfigurations or something like that. Could this initial delay be something to do with the Bodega Bay, or possibly something improperly setup such as using unit 6 instead of unit 1? Thanks in advance for any help.