Lines Matching refs:offset
26 # RISC OS AIF, contains "SWI OS_Exit" at offset 16.
515 #>>-0 offset x \b, %lld bytes
517 #>>-0 offset 901120 (DD 880 KiB floppy)
1707 # \003. Most of them start with non-null values at hex offset 0x34 or so.
2164 # Detect Volume Directory block ($02) + 2mg header offset
3296 # offset of compressed data
3297 >>10 uleshort x \b, %#x offset
3547 >12 ulelong !0x200 \b, offset %#x
3686 >>4 ulelong x \b, offset %#x
3766 #>8 byte &0x08 \b, file-offset
5484 #>-0 offset <0xffff
6116 # FIXME: Replace 0x48 with HEAD offset plus 8.
7639 # The long at offset 4 in a Mach-O universal binary tells the number of
7640 # architectures; the short at offset 4 in a Java bytecode file is the JVM minor
7641 # version and the short at offset 6 is the JVM major version. Since there are only
7709 # for debugging purpose print offset to 1st mach_header like:
7711 #>8 ubelong x at %#x offset
8180 >>>>8 ulelong >0 \b, symbol offset=%#x
8188 # at offset 20 can be optional header, extra bytes FILHSZ-20 because
8437 # * Original filename is only at offset 10 if "extra field" absent
8478 >>-0 offset >48
8480 >>-0 offset <48 \b, truncated
8503 >>-0 offset >48
8505 >>-0 offset <48 \b, truncated
8537 #ERROR: line 114: non zero offset 1048572 at level 1
9523 # is the offset 12 or the offset 16 correct?
10492 # 1st record offset + 1 = header size
10495 >>>>>>>>>>>>>8 uleshort >0 \b, at offset %d
12283 # remaining settings normally 0x5A+offset XORed; free_1D5[20] empty since 5.12.0e
12599 #offset is 128
12669 # where nn is string offset varying for different languages
12677 >>>>>0x49 ubyte >0 at offset %#x
12685 >>>>>0x74 ubyte >0 at offset %#x
12693 >>>>>0x79 ubyte >0 at offset %#x
12708 >>>>0x3C ubyte x at offset %#x+0xFF
12714 >>>>0xBD ubyte x at offset 0x1%x
12720 >>>>0xA9 ubyte x at offset 0x1%x
12730 >>>>0x1b5 ubyte >0 at offset 0x1%x
12734 >>>>0x1b6 ubyte >0 at offset 0x1%x
12738 >>>>0x1b7 ubyte >0 at offset 0x1%x
12751 >>>>0x1b5 ubyte >0 at offset 0x1%x
12755 >>>>0x1b6 ubyte >0 at offset 0x1%x
12759 >>>>0x1b7 ubyte >0 at offset 0x1%x
12769 >>>>0x1b5 ubyte >0 at offset 0x1%x
12773 >>>>0x1b6 ubyte >0 at offset 0x1%x
12777 >>>>0x1b7 ubyte >0 at offset 0x1%x
12963 # updated by Joerg Jenderek at Nov 2012. Use search directive with offset instead of string
12978 # message offset found at (1.b+5) is 0x77 for FAT32 or 0x5b for others
13056 # offset variant
13746 >>>>>>1 ubyte x \b, code offset %#x+2
13748 >>>>>>1 uleshort x \b, code offset %#x+3
13810 # there exist some old floppies without word FAT at offset 54
14322 #>>>>1 ubyte x \b, code offset %#x+2
14853 # offset to comment string like: 28h=40
14857 # offset to the first sector like: 0 (If this is 0, assume it is 0x200) 29h=41 (DISPLAY3.DSK) 31h 4…
15377 # skip Microsoft WinWord 2.0 ./msdos by looking for positive offset to font data
15403 # offset to optional horizontal offset table 0 58h~88 5eh 252h
15404 #>68 ulelong x \b, %#x horizontal table offset
15405 # offset of character offset table 54h for many *.GFT 55h 58h 5Eh 120h 1D4h 202h 220h
15407 # offset to font data like 116h 118h 158 20Ah 20Eh
15481 # biggest offset 0x0100bd28 like Windows10 Fonts\simsunb.ttf
15484 # offset of name table
15485 >>>&-4 ubelong x \b, name offset %#x
15486 # GRR: pointer to name table only works if offset ~< FILE_BYTES_MAX = 100000h defined in src\file.h
15498 # offset to start of string storage from start of table
15499 #>>>>>&-4 ubeshort x \b, record offset %d
15501 # string offset from start of storage area
15502 #>>>>>&8 ubeshort x \b, string offset %d
15524 # handle only name string offset 0 because do not know how to add 2 relative offsets
15566 # array offset size = fonts * offsetsize = fonts * 4
15570 # offset to 1st font
16122 # offset ~< FILE_BYTES_MAX = 1 MB defined in ../../src/file.h
16130 # offset to the beginning of the file table
16131 >>>4 ulelong x \b, offset %#x
16135 #>>>4 ulelong+64 x \b, offset %#x
16140 # normally entry start after header which implies offset 12 or higher
16142 # the offset from the beginning of pak to beginning of this entry file contents
16148 # inspect entry content by jumping to entry offset
17051 # for revision x.0 offset of table with originals is 1Ch if directly after header
17054 # but for x.1 table offset i found is 30h. That means directly after bigger header
17061 # offset of table describing system dependent segments
17066 # offset of table with start offsets of original sysdep strings
17068 # offset of table with start offsets of translated sysdep strings
17079 # if 1st string length positive inspect offset and string
17082 # if 2nd string length positive inspect offset and string
17090 # offset of table with translation strings
17092 # check translation 0 length and offset
18326 #>>>136 ubelong x %#x offset
18541 # extension area offset if not 0
18593 #>>>>&480 ulelong x - col offset %#8.8x
18595 #>>>>&484 ulelong x - stamp offset %#8.8x
18597 #>>>>&488 ulelong x - scan offset %#8.8x
18681 # at offset 2 a New Line character (0xA) should appear
18682 >>>2 ubyte !0x0A \b, %#x at offset 2 instead new line
19031 # 4 byte magic is assumed to be always at offset 0 and
19139 # at offset 8 starts imagedata followed by "RGB " marker
19240 # offBits; offset to bitmap data like:
19241 >>10 ulelong x \b, bits offset %u
19264 # offBits; offset to bitmap data like: 41E
19265 >>10 ulelong x \b, bits offset %u
19266 #>>10 ulelong x \b, bits offset 0x%x
19284 # offBits; offset to bitmap data like 56h 5Eh 8Eh 43Eh
19285 >>10 ulelong x \b, bits offset %u
19286 #>>10 ulelong x \b, bits offset %#x
19303 # offBits; offset to bitmap data like: 42h
19304 >>10 ulelong x \b, bits offset %u
19305 #>>10 ulelong x \b, bits offset 0x%x
19321 # offBits; offset to bitmap data like: 46h
19322 >>10 ulelong x \b, bits offset %u
19323 #>>10 ulelong x \b, bits offset 0x%x
19373 # offBits; offset to bitmap data like 36h 76h BEh 236h 406h 436h 4E6h
19374 >>>10 ulelong x \b, bits offset %u
19375 #>>>10 ulelong x \b, bits offset %#x
19392 # offBits; offset to bitmap data like: 8A 47A ABABABAB (fmt-119-signature-id-121.bmp)
19393 >>10 ulelong x \b, bits offset %u
19394 #>>10 ulelong x \b, bits offset 0x%x
19408 # offBits; offset to bitmap data like: 7A 7E 46A
19409 >>10 ulelong x \b, bits offset %u
19410 #>>10 ulelong x \b, bits offset 0x%x
19428 # offBits; offset in bytes to the beginning of the bit-map pel data like 20h
19429 >>10 ulelong x \b, bits offset %u
19466 # offBits; offset to bitmap data (pixel array) like E4h 3Ah 66h 6Ah 33Ah 4A4h
19467 >>10 ulelong x \b, bits offset %u
19468 #>>10 ulelong x \b, bits offset %#x
19476 # skip many Corel Photo-Paint image "CPT9FILE" by checking for positive bits offset
19515 # offBits; offset to bitmap data (pixel array) like 6Ah A4h E4h 4A4h
19516 >>10 ulelong x \b, bits offset %u
19517 #>>10 ulelong x \b, bits offset %#x
19533 # offNext; offset to data like 0 48h F2h 4Eh 64h C6h D2h D6h DAh E6h EAh 348h
19534 >>6 ulelong >0 \b, data offset %u
19535 #>>6 ulelong >0 \b, data offset %#x
19721 # of the header, which is at least 25 4-byte longs, and the one at offset 8
19753 # XOffset; Bitmap X offset; pixel numbers to ignore at the beginning of each scan-line
19888 >>>-0 offset x FILE_SIZE=%lld
19890 >>>-0 offset =32034 VARIANT_STANDARD
19895 >>>-0 offset =32066 VARIANT_ELITE
19899 >>>-0 offset =32128 VARIANT_3
19903 >>>-0 offset =44834 VARIANT_4
20166 >>6 bequad&0xFFffFFffFFff0000 !0 \b, at offset 6
20372 # The first file offset usually starts at file offset 0x1004
20373 # print 1 space after 0x100? offset and then handles PCX images by ./images
20510 # 64-bit offset netcdf Classic https://www.unidata.ucar.edu/software/netcdf/docs/file_format_specif…
20514 >3 uleshort >0 NetCDF Data Format data (64-bit offset)
22137 >>0x34 ulelong x \b, array offset %#x
22417 # no hint found, that at offset 22 is version
22507 # jmp offset like: 008fh 0093h 009fh 00afh 0143h 3ad7h 5417h 54ech 594dh 895fh
22525 # at 1Ah possible offset to expansion header structure; new for Plug aNd Play
22542 # offset to next header; 0 if none
22576 # boot connection vector; an offset to a routine that hook into INT 9h, INT 10h, or INT 13h
22578 >>(26.s+0x16) uleshort !0 \b, boot vector offset %#x
22579 # disconnect vector; offset to routine that do cleanup from an unsuccessful boot attempt
22580 >>(26.s+0x18) uleshort !0 \b, disconnect offset %#x
22581 # bootstrap entry point/vector (BEV); offset to a routine (like RPL) that hook into INT 19h
22583 >>(26.s+0x1A) uleshort !0 \b, bootstrap offset %#x
22587 >>(26.s+0x1E) uleshort !0 \b, static offset %#4.4x
22609 # Apparently this gives the same information as given by byte at offset 2 but as 16-bit
23064 # delete from ./animation (version 1.87) with jP (=6A50h) magic at offset 4
23257 # [${counter}--] in the offset of the entries
23258 # - Provide a way to round the next offset
23259 # Add [R:4] after the offset?
23874 # read the offset to add to the start of the header, and the header
24055 >>48 lelong&1 0 lacks filesystem offset
24056 >>48 lelong&1 1 has filesystem offset
24263 # payload-offset; start offset of the bulk data
24322 # hdr_offset; offset from device start [ bytes ] like: 0
24323 >256 ubequad !0 \b, offset %llx
24350 >40 ubelong x \b, %#x material offset
24867 # print 1 space and then at offset 128 inspect data fork content if it has one
24872 # calculate resource fork offset
25442 # First sub-file offset (absolute); sometimes NO/UNKNOWN sub file!
26158 >13 lefloat x \b, calibration: offset %f,
26999 # educated guess since indirection is still not capable enough for complex offset
27229 # leading/trailing nulls, zeros or non ASCII characters in 8-byte name field at offset 10 are skipp…
27254 # they have their real name at offset 22
27327 # check for probably nil padding til offset 64 of Lotus driver name
27378 # that offset must be accessible
27440 # 16-bit offset; for DEBUGGING!; can be negative like: USBDRIVE.COM
27444 # that offset must be accessible
27467 # negative offset, must not lead into PSP
27471 # that offset must be accessible
27472 # add 10000h to jump at end of 64 KiB segment, add 1 for jump instruction and 2 for 16-bit offset
27549 # assembler instructions: cmp sp, offset sp_limit
27552 # assembler instructions: jump above +2; int 0x20; mov cx, offset bytes_to_copy
27977 # 1st data offset = dir header size + n * dir entry size = 6 + n * 10h = ?6h
28026 # offset of PNG or DIB image
28027 #>12 ulelong x \b, offset %#x
28109 #>0x181 leshort x \b, offset %x
28149 # only value 0x100 found at offset 2
28385 # offset of the first CFFILE entry coffFiles: minimal 2Ch
28451 # offset of the CFDATA block in this folder
28465 # uoffFolderStart is uncompressed offset of file in folder
28762 # test for RecordType~LibraryHeaderRecord=0xF0 + RecordLength=???Dh + dictionary offset is multiple…
28784 # dictionary offset like: 400h 600h a00h c00h 1200h 1800h 2400h 5600h 12800h 19200h 28a00h
30031 # in 5.37 only true for offset ~< FILE_BYTES_MAX=7 MiB defined in ../../src/file.h
30864 # indextaboffset; offset of index table: 1F~after header 0~no index table for version 0?
30867 # 32-bit offset
30869 # offset with message table
30876 # 16-bit offset
30880 # msgindex; offset of message from begin of file
30889 # for version 0 index table apparently at offset 1F
30919 # countryinfo; offset of country info block: 0 for version 0
31163 # MobiPocket stores a full title, pointed at by the belong at offset
31165 # offset 0x58.
32593 # offset = ((offset[0] - 192) << 8) + offset[1] + 192 (for the length header)
32704 # offset = ((offset[0] - 192) << 8) + offset[1] + 192 + 1 (for the length header)
32766 # offset = ((offset[0] - 192) << 8) + offset[1] + 192 + 1 (for the length header)
33501 # those have a little-endian offset immediately following the magic 'PACK',
34472 # a 32 bit offset to the next section like: 000184d4 000184c8 00018534 ... 0000bb84 0000bbd4 0000bb…
34473 >4 ubelong x \b, offset %8.8x
36117 # number in the database at offset 60. Later, SQLite added an "application id"
36118 # at offset 68 that is preferred over "user version" for indicating the
36611 # GRR: original 1 byte test at offset was too general as it catches also many FATs of DOS filesyste…
36612 # where real SYStem EXclusive messages at offset 1 are limited to seven bits
37141 # Although we may know the offset of certain text fields in TeX DVI
37621 # kernel data offset. 200h means direct after header
37627 # root file system data offset
37632 # in 5.32 only true for offset ~< FILE_BYTES_MAX=9 MB defined in ../../src/file.h
37637 # bootloader data offset
37639 # bootloader data length only reasonable if bootloader offset not null
38189 # VHDX_HEADER signature. 1 header is stored at offset 64KB and the other at 128KB
38243 # VHDX_REGION_TABLE_HEADER Signature 0x69676572~regi at offset 192 KB and 256 KB
38367 # .Q modifier, we just use the bottom four bytes as an offset. Note that if
38382 # .Q modifier, we just use the bottom four bytes as an offset. Note that if
38475 # The AXP files all looked like this, except that the byte at offset 0x22
38588 # in a different place, so we must use an indirect offset.
38776 # index pointer; file offset pointing to a page of Data Indexes
39291 # ibAMapLast; offset to the last AMap page
39356 # relative offset not working
39763 #>>>>>8 uleshort x \b, event offset %4.4x
39781 # offset of Media Name (5Eh)
39792 # offset of Media Label (C4h,C6h,CCh)
39805 # offset of Software Name (1C8h,1CAh,1D0h)
40017 # data offset with 1 space at end
41195 # offset of central directory
41196 #>16 ulelong x \b, central directory offset %#x
