Those error codes are for all file streaming functions.  If FileDmRead can
generate all of that, I will be surprised.  And they all (except eof) seems not
relavent to that shortened return case.

So I am specifically asking this: if I pass everything correct to the
FileDmRead and the FS is good, should I have problem reading less than I
specified except in the case of EOF error?

The error hasn't happened. Even if I catch the error and it won't be obvious
why the error is generated, and why that error cause the shortened read.  For
example, when I get FileErrIOError (generic IO error), what caused that?

Max
--- Joe Programmer <[EMAIL PROTECTED]> wrote:
> --- Max Bian wrote:
> > If I use FileDmRead to read a file stream, 
> > which is a "good" file stream, what are the 
> > possible reasons that the actually read (the
> > return) bytes are smaller than specified 
> > other than the case when EOF is encountered?
> 
> The FileDmRead docs say: "When the number of objects
> actually read is less than the number requested, you
> may be able to determine the cause of this result by
> examining the return value of the errP parameter or by
> calling the FileGetLastError function."
> 
> So, I think you should look at the "File Streaming
> Error Codes" section of the "Palm OS � Programmer�s
> API Reference".
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Check out Yahoo! Shopping and Yahoo! Auctions for all of
> your unique holiday gifts! Buy at http://shopping.yahoo.com
> or bid at http://auctions.yahoo.com
> 
> -- 
> For information on using the Palm Developer Forums, or to unsubscribe, please
> see http://www.palmos.com/dev/tech/support/forums/


__________________________________________________
Do You Yahoo!?
Check out Yahoo! Shopping and Yahoo! Auctions for all of
your unique holiday gifts! Buy at http://shopping.yahoo.com
or bid at http://auctions.yahoo.com

-- 
For information on using the Palm Developer Forums, or to unsubscribe, please see 
http://www.palmos.com/dev/tech/support/forums/

Reply via email to