The FTYP (TK2) command should return zero for text files, data files,
S*Basic files, QSAVED files etc.
One is the value for executables, and two is for SROFF modules which are
used by the linker to assemble an executable file. 255 is for a Directory
Driver 2 (sub-) directory. I think THORs used
On Sun, Jul 01, 2001 at 05:21:47PM -0400, ZN wrote:
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,
At 12:54 ìì 2/7/2001 +0200, you wrote:
On Sun, Jul 01, 2001 at 05:21:47PM -0400, ZN wrote:
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
PROTECTED]]
Envoyé : dimanche 1 juillet 2001 23:22
À : [EMAIL PROTECTED]
Objet : Re: [ql-users] Program type Identification
(...)Pity the file type isn't used more often.
Nastac
Claude Mourier 00 wrote:
Yes : identifying files types by this way should be the only one on
all
platform rather than relying on extensions name (under W$, because
of that?,
you can mask it : and it's worts).
Alas there is only 3 files types used under QDOSSMS ;-(
Summary:
TYPE DETAILS
0
Executables can be tested via the FTYP function (type 1 is executable)
of Toolkit 2.
AFAIK you can't recognise Resident Extensions by file type, as they
are type 0 data files like text files, sbasic programs etc, although
some manage to mask themselves as 'executable type' - some versions of
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
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
At 10:59 ìì 1/7/2001 +0100, you 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
