On 7/1/01 at 7:15 PM Dilwyn Jones wrote: >Executables can be tested via the FTYP function (type 1 is executable) >of Toolkit 2. Yes, they could also be identified (and some more interesting info gleaned) from the first couple of bytes, the executable header. Don't remember the definition of the top of my head, but I know hex 4AFB appears in it :-) Resident extensions cannot be recognized as they are just pieces of code, they are called after they are loaded (LRESPR), but don't have any defined headers etc. There is also file type 2 (or was it -1?) for linker files. Pity the file type isn't used more often. Nastac
- [ql-users] Program type Identification Phoebus Dokos
- Re: [ql-users] Program type Identification Joachim Van der Auwera
- Re: [ql-users] Program type Identification Dilwyn Jones
- Re: [ql-users] Program type Identification ZN
- Re: [ql-users] Program type Identification Marcel Kilgus
- Re: [ql-users] Program type Identification Robert Newson
- Re: [ql-users] Program type Identification Phoebus Dokos
- Re: [ql-users] Program type Identification Joachim Van der Auwera
- RE: [ql-users] Program type Identification Norman Dunbar
- Re: [ql-users] Program type Identification Richard Zidlicky
- Re: [ql-users] Program type Identification Phoebus Dokos
- RE: [ql-users] Program type Identification Claude Mourier 00
- Re: [ql-users] Program type Identification Dilwyn Jones
