[Freemint-list] XHDOSLimits

Alan Hourihane alanh at fairlite.co.uk
Tue Oct 4 11:32:58 MSD 2016


On 04/10/16 08:11, Miro Kropáček wrote:
>
> On 4 October 2016 at 16:38, Alan Hourihane <alanh at fairlite.co.uk
> <mailto:alanh at fairlite.co.uk>> wrote:
>
>     But I really don't know why this would be needed, seems a strange
>     thing to do.
>
>
> Well, it was news to me as well but it does make sense -- harddisk
> driver reads this information to determine the number of possible
> drives available, number of fats and similar stuff. I'm no expert on
> this but I assume that's the agreement enforced by the XHDI protocol.
> CBHD and HD Driver rely on this, from the other side, Big DOS is an
> example which does set this function so there's a real world example
> to compare.

Right. I'm sure there are examples, but if the last XHDI handler
installed handles the XHDOSLimits() call, why do the underlying ones
need to know ?

I'd expect the newly installed XHDI driver to query the last installed
driver, and do some level of cross examination of those details before
it exposes the new set of DOSLimits to the new callers.

Alan.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.atariforge.org/pipermail/freemint-list/attachments/20161004/34508513/attachment.html 


More information about the Freemint-list mailing list