»

[Robert17]

Hey all, having trubs with the onboard scsi of the A3000, I only have one hard disk connected to it, and I've noticed that on powering up it works fine, but when you reset the machine via the keyboard it just stops... until you power down then up again, is this a common problem? And can it be fixed?

Robert

[amigagr]

the disk is not supplied with power so the amiga don't boot after the reset or it's boot ok but after this the disk become unusable and practicaly you can't do anything with the amiga?
have you check the termination?

[Robert17]

The disk is powered and it boots from the disk fine once the machine is powered on, however it will only boot from hdd once there's one plugged in.

Robert

[Mark]

If you have Kickstart 3.1, try disabling synchronous transfer with SCSIprefs. You'll need a working clock battery to retain the settings, of course.

[Amiga4k]

Mark,
SCSIPrefs was written for AmigaDOS 2.0 +. This is not a SCSI polling buss problem. Synchronous mode reduces transfer overhead by not requiring an acknowledge immediately after the transfer of each data word. It has no correlation to warm-boot. Good guess, but the wrong program.

Robert17,
What make, size, and vintage is this drive. This sounds like a timeout problem,(which was prevalent with older drives) whereas the SCSI buss searched while the drive was still spinning up, and not ready.
I would do the following:
(1) Re-configure the SCSI ID to 1. (if not already). The boot process scans from 0-6.
(2) If you have 3.1+ AmigaDOS, install Setbatt-1.2 The most prominent flag you may want to change is the SCSI scan timeout to make the SCSI controller recognize SCSI drives with a long select phase.

[Mark]

Amiga4k wrote:

SCSIPrefs was written for AmigaDOS 2.0 +.

That is correct. It also works perfectly with AmigaOS 3.1.
Kickstarts before v. 3.1 do not attempt to initiate synchronous transfer.

Synchronous mode reduces transfer overhead by not requiring an acknowledge immediately after the transfer of each data word. It has no correlation to warm-boot.

Incorrect. The A3000 does not attempt synchronous transfer on cold boot, only after a warm reboot. Try it for yourself, as I have done, with an A3000 that has KS 3.1 and an Iomega SCSI Zip or Jaz drive, which do not do sync transfers.

(2) If you have 3.1+ AmigaDOS, install Setbatt-1.2 The most prominent flag you may want to change is the SCSI scan timeout to make the SCSI controller recognize SCSI drives with a long select phase.

Do you have a personal grudge against SCSIPrefs or are you just trying to start an argument? :-)
SCSIPrefs, which you call "the wrong program," also sets scan timeout.

[Amiga4k]

No affront on you or your choice of SCSI-Pref. Your quote: "If you have Kickstart 3.1, try disabling synchronous transfer with SCSIprefs." You neglected to say "Kickstart 2.+" from the start.

(During my 14 years as a BBS SYsOp I had occasion to used both programs). You are right about synchronous _IF_ you have multiple drives.
Robert17 has only 1 drive. I am overly cautious about my replys on this forum, and the answer was correct in relation to a single drive, he needs to set "timeout". It is a matter of preference on the file, and I do prefer SetBatt for this purpose. If I had other problems, I would use SCSI-Pref.

(When you have worked an Amiga 3000 with 5.25" full HT drives spin up in 30 sec, and then add (10secx7CDx4changers) to initialize, let's discuss synchronous access on the buss). Now that takes a lot of patience and practice.