🚀 go-pugleaf

I give in.  Please report us to the Better Business Bureau for Abuses
and Criminal Neglect of Hard-Disk Start-up Sequences. 

Yes, we could issue the "Test Unit Ready" command to the controller, and
if there's no response, then there's no controller.  If there is a
response, and it's negative, we can keep asking until it's positive. 
However, there's still a timeout -- it may be that the controller is
getting power but the drive unit is not, so it'll NEVER be ready.  How
long do you propose we wait?

At any rate, it's too late for TOS 1.4.  Sorry.  Use your "text file
causing reboot" trick.  Or, you can do it properly:

	; This program causes a warm boot.
	; Un-comment the clr.l for a cold(er) boot.

	move.l	#0,-(sp)	; get into supervisor mode
	move.w	#$20,-(sp)
	trap	#1

;	clr.l	$420
	move.l	$4f2,a0		; a0 -> OS header
	move.l	4(a0),a1	; a1 -> reset handler
	jmp	(a1)		; jump there.  That's a reset.

That's all there is to it.  No guessing, just a warm boot.  If you want
a cold boot, un-comment the clr.l instruction.  This will run in the
AUTO folder, as an accessory, or as something you can double-click from
the Desktop or start from a shell. 

============================================
Opinions expressed above do not necessarily	-- Allan Pratt, Atari Corp.
reflect those of Atari Corp. or anyone else.	  ...ames!atari!apratt