oops, just saw this. actually, I don't know where this is documented, I was
only able to see a brief blow-by mention of the function.
does anyone know where documentation on int21h function 7303h is, since it is
apparently publicly available somewhere?
________________________________
From: Christian Masloch <c...@bttr-software.de>
To: Jim Michaels <jmich...@yahoo.com>; freedos-devel@lists.sourceforge.net
Sent: Sun, February 13, 2011 4:44:16 AM
Subject: Re: [Freedos-devel] documentation for FreeDOS filesystem or other
programming functions/interfaces?
> I am possibly going to rewrite my df utility to work with freeDOS' FAT32
> filesystem (DJGPP uses int21h function 36h which is 16-bit FAT16 and 16-bit
> regs).
>
> I cannot find any documentation on the functions that freedos uses for its
> filesystem functions, like getting filesystem volume space calculations
> (total
>&
> available).
>
> can anyone help me?
Yes.
Refer to Ralf Brown's Interrupt List's description of interrupt 21h function
7303h. (This is also referenced in the SeeAlso section of the description of
interrupt 21h function 36h.) The data returned into your buffer by this
function
is partially different to that returned by function 36h, but testing this on a
FAT32 file system and verifying whether the results match your expectations
should work. I think to recall that on DOS versions that support function 7303h
you can usually obtain information about FAT12 and FAT16 file systems using
this
function too.
As to your exact request for a FreeDOS function, FreeDOS kernels with FAT32
support provide function 7303h. They also allow retrieving information about
non-FAT32 file systems this way.
Note that RBIL says:
> on DOS versions which do not support the FAT32 calls, this function
> returns CF clear/AL=00h (which is the DOS v1+ method for reporting
> unimplemented functions)
You have to be careful about this criterion. My observations indicate that DOS
versions that do not support interrupt 21h function 73h indeed return with an
MS-DOS v1 style error, but that does _not_ mean CF clear and AL zero. It means
AL zero and CF unchanged.
Regards,
Christian
____________________________________________________________________________________
Need Mail bonding?
Go to the Yahoo! Mail Q&A for great tips from Yahoo! Answers users.
http://answers.yahoo.com/dir/?link=list&sid=396546091
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
