IPC@CHIP Documentation - SC12 @CHIP-RTOS V1.10

CX
BX:SI
ES:DI
Must be 0x28.
File attribute
Null terminated file specification
Pointer to filefind structure
Return Value
Comments
AL= 1 DX=0: Success
AL= 0 DX=0: No file found
DX= -1: Findfirst already active
The three filefind functions (0x28 - 0x30) provide a faster Findfirst/next access than the DOS compatible functions at INT 21h. They
work in a manner similar to the INT 21h Findfirst/next functions. You must first call Findfirst (0x28). After that call, you can call
Findnext (0x29) as much as you need. To get the entire directory call repeatedly until Findnext returns an error. The directory
being searched will be locked for exclusive access by the calling task. To unlock the directory you have to call Finddone (0x30).
Note: Only a successful call of this function (file found) must be later terminated by a call of the Fast Finddone function!
These functions (0x28 - 0x30) are not reentrant, do not call findfirst/findnext sequences from different tasks without semaphore
protection.
The filefind structure is defined as follows:
typedef struct filefind
{
char filename[12]; // Null terminated filename
char fileext[4]; // and extension
unsigned short int fileattr; // MS-DOS file attributes
short int reserved; // Reserved
struct tag_filetimestamp
{
unsigned short int filedate; // Date = ((year - 80) shl 9) or (month shl 5)) or day
unsigned short int filetime; // Time = (hour shl 11) or (min shl 5)) or (sec / 2)
} filetimestamp; // Time & date last modified
unsigned long filesize; // File size
char private_field[180]; // Reserved, used internal
}
Related Topics
Top of list
Index page
Fast Findnext
Fast Finddone must be called at end of the search
Interrupt 0xA0 service 0x29: Fast Findnext
Parameters
AH
ES:DI
Continues a search which was started by Fast Findfirst (0x28)
Must be 0x29.
Pointer to filefind structure
Page 94 / 400