On Fri, 20 Nov 1998, Nestor Soriano wrote:
> >>              LD A,drivenumber
> >>              SET 7,A
> >>              LD DE,pointer to 32-bit sectornumber
> >>              CALL DSKIO
> >> I challenge you to come up with a better way.
> >DISKIO #4010:
> >-------------
> >A: bit 7: 1= >16bit handling
> >HL: DTA
> >B: number of sectors
> >C: mediabyte
> >DE: sectornumber lowword (both old and new type of DISKIO)
> 
> In the case that you want to create own code and put in a RAM segment
> (patching #F252 then) instead of modifying kernel, I propose the following:
> 
> Parameters for current sector I/O DOS functions (#2F and #30):
> 
> C = #2F or #30
> DE = Sector number
> L = Drive number
> H = Number of sectors to read/write to/from DTA space
> 
> New parameters for same functions after patching:
> 
> C = #2F or #30
> DE = Sector number, low part
> B = Sector number, high part
> L = Drive number
> bit 7 of L = 0 --> Ignore B (for keep compatibility)
> H = Number of sectors to read/write to/from DTA space
> 
> I won! X-)
> 
> 
For all clarity: you're talking about msxdos.sys(0005)/f37d. That also has to
be changed. Nevertheless also our diskroms need modification (even when
intercepting #f252, unless you make another patch for each interface :-( )
and that was the thing we were talking about.

Your proposal seems ok to me.

Does everyone agree on the fact of using 24bit sectornumbers instead
of 32?
I do


greetz,
jon



****
MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put
in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the
quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
****

Reply via email to