I have found the declarations in a C header file.
Anyway thank you very much for answering.
I will post the declaration here, maybe other peoples are interested:
(*
FindFiles
File attribute constants - There are quite a number of attributes
that Borland's routines do not support. Those are compressed,
encrypted, offline, reparse point, sparse file, temporary, device, and
not content indexed.
______________________________________________________________________________
| | | |
| Name | HEX | DEC | BIN | Comment
|______________________|________|______|_________|_____________________________
faReadOnly | $0001 | | |
faHidden | $0002 | | |
faSysFile | $0004 | | |
faVolumeID | $0008 | | | NEVER USE THIS
CONSTANT! See http://qc.borland.com/wc/qcmain.aspx?d=6003
faDirectory | $0010 | | |
faArchive | $0020 | 32 | 00100000|
faSymLink | $0040 | | | Also known as:
INROM/ENCRYPTED
faAnyFile | $003F | 63 | 00111111|
----------------------|--------|----------------| The following are
not defined in Delphi:
faNORMAL | $0080 | | |
faTEMPORARY | $0100 | | |
faSPARSE_FILE | $0200 | | |
faREPARSE_POINT | $0400 | | |
faCompressed | $0800 | 2048 | 10000000|
faOFFLINE | $1000 | | | Not immediately
available, the file data has been physically moved To offline storage
faROMSTATICREF | $1000 | | |
faNOT_CONTENT_INDEXED| $2000 | | |
faROMMODULE | $2000 | | |
------------------------------------------------------------------------------
*)
PS: use a monospatiate font to see the table right.
[EMAIL PROTECTED] wrote:
>> There are quite a number of attributes that Borland's routines do not
>> support. Those are compressed, encrypted, offline, reparse point,
>> sparse file, temporary, device, and not content indexed.
>>
>
> In the windows SDK help is the function FindFirstFile which Delphi wraps.
> That returns a WIN32_FIND_DATA structure and gives the complete definition
> for it. In Delphi 7 those are all defined in windows.pas so even the
> cheap versions of Delphi should have them accessible, even if you can't
> see the source code.
>
> I suspect you could call the SDK function directly, otherwise loading the
> dll yourself and writing a wrapper is always an option.
>
> Moz
> __________________________________________________
> Delphi-Talk mailing list -> Delphi-Talk@elists.org
> http://www.elists.org/mailman/listinfo/delphi-talk
>
>
__________________________________________________
Delphi-Talk mailing list -> Delphi-Talk@elists.org
http://www.elists.org/mailman/listinfo/delphi-talk
