#SCSI Time-out
5 messages in this thread
I'm looking for information about the setting of the SCSI time-out on an
A3000 with OS3.1 installed and functioning. I needed to set,using BattMem,
the long SCSI time-out to 2 secs in-order for OS3.1 to boot my computer.
However, the time-out seems to be more like 20 secs before the boot begins
after a cold startup. I have the following hard drive on my system:
1.) The boot drive is a Quantum 40mb ProDrive model #313440-01.
2.) The other is a Maxtor 7245SR.
Under OS2.1 and earlier I had no problem with the default setting of the
short SCSI time-out of 128ms; and I think that the system only needs a
slight increase in the time-out to satisfy OS3.1 on cold startup.
Evidently OS3.1 is more sensitive about the stability of the drives before
it will initiate the boot operation.
Also, I would like some info concerning "asyncronous" compared to
"syncronous" SCSI operation. This switch is avail with BattMem and I
remember some-one talking about the requirement to set "syncronous"
operation for OS3.1. However, I have no problems with the default setting
with this switch OFF.
Thanks in advance for any info .
/ / Flying The A3000 on AutoPilot 1.74
\/\/ from Durham,Ontario.
Pete,
PD>However, the time-out seems to be more like 20 secs before the boot
PD>begins after a cold startup.
Yes, I have (or had) the same situation (A3K w/ 80MB Quantum and ADOS
3.1). For bootup, the long delay is ok, but I got tired of the wait when
using the three finger salute and changed back (via BattMem) to the 128 Ms
timeout. This means rebooting upon powerup, but I don't powerup very
often so that seemed the way to go. As far as I know, there is no in
between, i.e., there is only 128 Ms or 2 seconds. Maybe some enterprising
young Ami programer will write another BattMem utility with inbetween
choices.
PD>some info concerning "asyncronous" compared to "syncronous" SCSI
operation.
I tried asyncronous for awhile – all worked OK. Then one day, I threw
caution to the wind (after a lengthy floppy backup) and changed the
setting to syncronous. File transfers are snappier and everything seems
to work OK…
Hope this helps. Dickoux
Thanks Dick,Ed for the info but I think that until or if someone comes out
with a util with in between SCSI settings that I will leave my time-out
set to 2 secs. Async vs. Sync ? I'll leave that alone to for now.
/ / Flying The A3000 on AutoPilot 1.74
\/\/ from Durham,Ontario.
Pete,
I noticed that when I installed WB3.1 on my A3000, that the SCSI buss
device checking goes light-years faster. I used to get about 15 pulses to
my SyQuest drive (drive light flashes) but now only see one pulse before
Mr. SCSI passes it up looking for somebody else to pick on! I have done
what you are considering and have changed the time-out to 2 sec with no
problems.
The syncronous/asyncronous thing is there so you can get real ticked
off at Mr. SCSI when you play around with it <grin>. This flag is
something you would change if ALL your SCSI devices would support it and
then you would theoretically get more throughput on your buss. Of all the
hard drives I've played with, only the more expense, fast, large capacity
drives have supported this feature. I also remember some SuperInfoHwy
gossip about WB3.1 not liking this flag enabled but I don't know that as
fact since I didn't test it. I would recommend you leave this flag alone
if it is working the way it is set.
EdV
Pete, the Initiate Synchronous Transfers flag's effects may vary from
drive to drive, but my fast SCSI-2 drive definitely wants it on. I think
other people have experienced various degrees improvement or not. In my
case, it's all or nothing.
DJ
On AP from Queens, the thrill and excitement of the Big Apple
Where a little paranoia is always a healthy attitude …