Xref: utzoo comp.sys.amiga:68367 comp.sys.amiga.tech:14995
Path: utzoo!attcan!uunet!mcsun!hp4nl!sci.kun.nl!cs.kun.nl!rhialto
From: rhialto@cs.kun.nl (Olaf Seibert)
Newsgroups: comp.sys.amiga,comp.sys.amiga.tech
Subject: Re: Should CrossDos/MSH work on my 3000?
Message-ID: <2278@wn1.sci.kun.nl>
Date: 10 Oct 90 16:38:00 GMT
References: <08Oct90.151432.944@ckctpa.UUCP>
Sender: root@sci.kun.nl
Followup-To: comp.sys.amiga
Organization: University of Nijmegen, The Netherlands
Lines: 25

In article <08Oct90.151432.944@ckctpa.UUCP> crash@ckctpa.UUCP (Frank J. Edwards) writes:
>I'm not sure where the problem with this is, but the MSDOS-compatibility
>programs don't like my 3000.  I presume its due to CPU timing loops which
>are being thrown off by the '030.  Does anyone know of fixes/patches/etc
>to either CrossDos or MSH that would fix the problem?

I can't speak for CrossDOS, only for MSH since I wrote it. There are
certainly no timing loops in MSH. In fact, there is no timing in MSH at
all. (There is only a case of please-start-the-dma-as-soon-after-an-
index-interrupt, and onviously the faster this goes the better). The
problem might be that MSH uses some disk custom registers directly
(though as little as possible) instead of through trackdisk.device.
Furthermore it only supports 1.3-type packets, though I don't think
this should really matter. It also installs disk index and disk block
interrupt handlers though a not-really documented way.

If you find out what the problem is, please let me know.

>Frank J. Edwards		ComputerKnowledge Corp
--
Olaf 'Rhialto' Seibert                               rhialto@cs.kun.nl
How can you be so stupid if you're identical to me? -Robert Silverberg
--
Olaf 'Rhialto' Seibert                               rhialto@cs.kun.nl
How can you be so stupid if you're identical to me? -Robert Silverberg