1b6cee71dSXin LI 2b6cee71dSXin LI#------------------------------------------------------------------------------ 3*40427ccaSGordon Tetlow# $File: vms,v 1.10 2017/03/17 21:35:28 christos Exp $ 4b6cee71dSXin LI# vms: file(1) magic for VMS executables (experimental) 5b6cee71dSXin LI# 6b6cee71dSXin LI# VMS .exe formats, both VAX and AXP (Greg Roelofs, newt@uchicago.edu) 7b6cee71dSXin LI 8b6cee71dSXin LI# GRR 950122: I'm just guessing on these, based on inspection of the headers 9b6cee71dSXin LI# of three executables each for Alpha and VAX architectures. The VAX files 10b6cee71dSXin LI# all had headers similar to this: 11b6cee71dSXin LI# 12b6cee71dSXin LI# 00000 b0 00 30 00 44 00 60 00 00 00 00 00 30 32 30 35 ..0.D.`.....0205 13b6cee71dSXin LI# 00010 01 01 00 00 ff ff ff ff ff ff ff ff 00 00 00 00 ................ 14b6cee71dSXin LI# 15b6cee71dSXin LI0 string \xb0\0\x30\0 VMS VAX executable 16b6cee71dSXin LI>44032 string PK\003\004 \b, Info-ZIP SFX archive v5.12 w/decryption 17b6cee71dSXin LI# 18b6cee71dSXin LI# The AXP files all looked like this, except that the byte at offset 0x22 19b6cee71dSXin LI# was 06 in some of them and 07 in others: 20b6cee71dSXin LI# 21b6cee71dSXin LI# 00000 03 00 00 00 00 00 00 00 ec 02 00 00 10 01 00 00 ................ 22b6cee71dSXin LI# 00010 68 00 00 00 98 00 00 00 b8 00 00 00 00 00 00 00 h............... 23b6cee71dSXin LI# 00020 00 00 07 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 24b6cee71dSXin LI# 00030 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 ................ 25b6cee71dSXin LI# 00040 00 00 00 00 ff ff ff ff ff ff ff ff 02 00 00 00 ................ 26b6cee71dSXin LI# 27b6cee71dSXin LI# GRR this test is still too general as it catches example adressen.dbt 28b6cee71dSXin LI0 belong 0x03000000 29b6cee71dSXin LI>8 ubelong 0xec020000 VMS Alpha executable 30b6cee71dSXin LI>>75264 string PK\003\004 \b, Info-ZIP SFX archive v5.12 w/decryption 31