Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!wuarchive!uunet!cbmvax!jesup
From: jesup@cbmvax.commodore.com (Randell Jesup)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Should CrossDos/MSH work on my 3000?
Message-ID: <15704@cbmvax.commodore.com>
Date: 8 Nov 90 04:42:14 GMT
References: <08Oct90.151432.944@ckctpa.UUCP> <7811@ucdavis.ucdavis.edu> <2286@wn1.sci.kun.nl>
Reply-To: jesup@cbmvax.commodore.com (Randell Jesup)
Organization: Commodore, West Chester, PA
Lines: 28

In article <2286@wn1.sci.kun.nl> rhialto@cs.kun.nl (Olaf Seibert) writes:
>>>[MSH does not work on a 3000]

>I think that the messydisk.device indefinitely waits for an index
>interrupt. The way these things are installed is not really documented,
>as far as I know, except by suggestive names in a structure.  What
>usually is the problem when messydisk can't write, is that the
>IndexIntCode doesn't get called for some reason. (Usually these are
>hardware problems, so not my problem ;-) The ~~~ marked part is what is
>questionable. But if it can read, the block interrupt works, so why
>doesn't the index interrupt work?  Specifically, what I do is the
>following: (file devio.c excerpted)

	I've verified at the hardware level that the index signal occurs
(at least going into the 8520).

	I didn't see anything obviously wrong with your code, but nothing that
affects such things should have changed.  Note that timing may be different,
for example from the 32-bit chip memory access, processor speed, etc.  However,
properly written code shouldn't care.

	Does it work on an A3000 under 1.3, or is it broken on both 1.3 and
2.0?

-- 
Randell Jesup, Keeper of AmigaDos, Commodore Engineering.
{uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.cbm.commodore.com  BIX: rjesup  
Common phrase heard at Amiga Devcon '89: "It's in there!"