Mark0's software support board
November 19, 2017, 11:38:43 am *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: Welcome to the new forum! Guests can posts without registration.
 
   Home   Help Search Login Register  
Pages: [1] 2 3 ... 10
 1 
 on: November 18, 2017, 05:27:14 pm 
Started by Mark0 - Last post by Mark0
Updated:
  • Universal Hint System (old 88a format) (UHS)
Added:
  • RapidFile Memo (MMO)
  • Protected Interoperable File Format (PIFF)
  • RapidFile Data (RPD)
  • TASM instructions definition Table (TAB)
  • Universal Hint System (newer format) (UHS)

 2 
 on: November 16, 2017, 10:13:48 pm 
Started by Mark0 - Last post by Mark0
Updated:
  • Virtual MC-10/Alice tape image (C10)
Added:
  • Panasonic JR Cassette image (CJR)
  • VZ200 Cassette image (CVZ)
  • Print / Instant Artist for DOS Graphics (GFX)
  • DCAlice tape image (K7)
  • TNTmips Project (Windows) (RVC)
  • DCAlice snapshot (MRX)

 3 
 on: November 14, 2017, 08:57:48 pm 
Started by jenderek - Last post by Mark0
Good! I will try to collect some more .ja file to further refine the definition, if possible.
Thanks Joerg!

 4 
 on: November 14, 2017, 06:38:14 pm 
Started by jenderek - Last post by jenderek
Hello,

when i run trid in Mozilla Firefox and Thunderbird program directory on
different OS there i found dozen of files with name omni.ja which are not
recognized (see appended output/trid-old.txt).

Some Information about such archives is found on Wikipedia page about newer
firefox browser. So i use this as reference URL by line:
   <RefURL>https://en.wikipedia.org/wiki/Firefox_4</RefURL>

After searching on the net i found a site explaining some facts:
https://sourceforge.net/p/sevenzip/discussion/45798/thread/411a70b3/?limit=25

This kind of archive has the central directory ( start with magic
PK\001\002) at the beginning ( offset 4), where real ZIP files has central
directory at the end and start with file header ( magic PK\003\004). Mention
this fact in remark line. So this is not strict ZIP file format. So instead
mime type application/zip use an other one by line:
   <Mime>application/x-zip</Mime>

Because it is a kind of zip archive name trid definition file
zip-ja.trid.xml. Most ZIP unpacker are able to extract such archives maybe
only partly or after some warnings. An example is command line like
zip -FF omni.ja --out omni.zip
So mention this also in remark line.

To understand pattern of definition file look at ZIP specification in
APPNOTE.TXT found at https://pkware.cachefly.net/webdocs/casestudies/ .

The main and first pattern is magic of file header by XML construct:
   <Bytes>504B0102</Bytes>
   <ASCII> P K</ASCII>
   <Pos>4</Pos>

The remaining pattern are determined by meta information of first file etc.
( look also at output\7z-l.txt). Version made was always found
2.0~2*10+0=20=14h. This is expressed by
   <Bytes>1400</Bytes>
   <Pos>8</Pos>
Unused upper byte of version needed to extract is expressed by:
   <Bytes>00</Bytes>
   <Pos>11</Pos>

Unused upper byte of general purpose bit flag is expressed by:
   <Bytes>00</Bytes>
   <Pos>13</Pos>
Unused upper byte of compression method and time and date of 1st file found
is 1 Jan 2010 00:00. This is expressed by:
   <Bytes>000000213C</Bytes>
   <Pos>15</Pos>
Upper byte of compressed size is null if first file is small.  This is
expressed by:
   <Bytes>0000</Bytes>
   <Pos>26</Pos>
Upper byte of uncompressed size is null if first file is small. This is
expressed by:
   <Bytes>0000</Bytes>
   <Pos>30</Pos>
Upper byte of file name length size is null if first file is like
"chrome.manifest". Then followed by Extra field, file comment, disk number,
file attributes are null. This is expressed by:
   <Bytes>00000000000000000000000000</Bytes>
   <Pos>33</Pos>
Upper byte of file offset size is null. This is expressed by:
   <Bytes>00</Bytes>
   <Pos>49</Pos>
More null pattern are part of 1st file content or by next file stuff.

If central directory contains a file name like appstrings.properties and no
extra field and file comment are used then next file header (magic
PK\001\002) immediately follows. This is expressed by global string like
   <String>APPSTRINGS.PROPERTIESPK</String>

I keep all found patterns, even if some occur by lucky circumstances,
because the file format of omni.ja is not official commentated. This is
very annoying that widely used web browser like firefox claiming to be open
source use undocumented file format to store data.

With new trid definition files now all inspected omni.js archive are now
recognized (see appended output/trid-new.txt). TrID definition, and output
are stored in archive ja.zip. I hope that the XML file can be used in
future version of triddefs.

With best wishes
Jörg Jenderek

 5 
 on: November 13, 2017, 02:12:35 am 
Started by Mark0 - Last post by Mark0
Updated:
  • LEGO Mindstorms EV3 project (EV3)
Added:
  • LEGO Mindstorms EV3 Block (EV3B)
  • FOnline Engine GUI (FOGUI)
  • FOnline Engine GUI Scheme (FOGUISCHEME)
  • LEGO Mindstorms EV3 brick executable code (RBF)
  • FOnline Engine Tile set (TIL)
  • Torsion project (TORSION)
  • 3 Step Studio Project (TSSPROJ)

 6 
 on: November 12, 2017, 02:25:42 am 
Started by Mark0 - Last post by Mark0
Updated:
  • Microsoft KWAJ compressed (generic) (EX_)
  • Microsoft SZDD compressed (Haruhiko Okumura's LZSS) (EX_)
  • AngelCode Bitmap Font (text) (FNT)
  • Visual Studio Natvis visualization (NATVIS)
  • Visual Studio Natvis visualization (UTF-8) (NATVIS)
Added:
  • Microsoft SZ compressed (EX$)
  • Microsoft KWAJ compressed (Phil Katz's 'deflate') (EX_)
  • Microsoft KWAJ compressed (MS-ZIP) (EX_)
  • AngelCode Bitmap Font (XML) (FNT)
  • AngelCode Bitmap Font (binary) (FNT)
  • Torque animation asset (XML) (TAML)
  • Torque audio asset (XML) (TAML)
  • Torque font asset (XML) (TAML)
  • Torque GUI control (XML) (TAML)
  • Torque image asset (XML) (TAML)
  • Torque module definition (XML) (TAML)
  • Torque particle asset (XML) (TAML)
  • Torque skeleton asset (XML) (TAML)
  • Torque sprite asset (XML) (TAML)

 7 
 on: November 11, 2017, 06:23:10 pm 
Started by jenderek - Last post by Mark0
Many thanks!
P.S.
For the extension I have to avoid to use wildcards because it's simply added to a filename when renaming (at least for the moment).
So either I put there a sample/typical extension (like EX_) or maybe I'll leave it empty.

 8 
 on: November 11, 2017, 02:17:35 am 
Started by jenderek - Last post by jenderek
Hello,

when i run trid on hundreds of old Microsoft compressed files some are not
recognized (see appended output/trid-old.txt).

Information about MS-DOS installation compression files is found at
http://fileformats.archiveteam.org. So i add this page as reference URL to
trid definition files by line:
<RefURL>
http://fileformats.archiveteam.org/wiki/MS-DOS_installation_compression
</RefURL>

The link about SZDD and KWAJ formats description as szdd_kwaj_format.html is
dead. But found this document at
https://hwiegman.home.xs4all.nl/fileformats/compress/

According to documentation examples with names *$ are a third variant of MS
Compressed archives. Examples for third variant can be found at
http://www.qbasic.net/de/qbasic-downloads/compiler/qbasic-compiler.htm for
example.


The shared characteristic pattern '88F027' is not found at offset 4 but at
offset 3. So such examples are not recognized by trid. Furthermore the
start pattern is now string "SZ ". This is expressed by XML construct
   <Bytes>535A2088F02733D1</Bytes>
   <ASCII> S Z   . . ' 3</ASCII>
   <Pos>0</Pos>
in new sz.trid.xml. File name extension is expressed by line
   <Ext>??$</Ext>

The extracting tools are problematic. An universal unpacker does not
exist. EXPAND does not work for such case. Extracting succeeds with
UNPACK.EXE which i found on first Qbasis installation floppy. So mention
this fact in remark line. As help for user also add a specific user defined
mime type by line:

   <Mime>application/x-ms-compress-sz</Mime>

In tridscan generated definition file at offset 11 byte was null, because the
inspected original files are not so big. So mention this fact in remark line.

By new sz.trid.xml now examples like PWBBASIC.MX$ or RAMDRIVE.SY$ are
recognized (see appended output/trid-new.txt).

The second variant with starting "SZDD" string is detected by
szdd.trid.xml. Add also reference URL.

At offset 9 sometimes last character of original file name extension is
stored if not null. So mention this fact in remark line. So we can easily
see that ARIAL.TT_ is the MS compressed truetype font ARIAL.TTf.

For compressed archives name has an underscore as last character in file
name extension. This is now expressed by line
   <Ext>??_</Ext>
instead non preciously expression:
   <Ext>EX_</Ext>

The size of original uncompressed file is store as little endian long value
at offset 10. So mention this also in remark line.

It is very annoying to install and run an emulator like DOSBox in order to
extract then by DOS expand tool such compressed archives. The 7z can extract
such archive by MsLZ type format. So mention this fact also in remark line.
Therefor add a specific user defined mime type by line:
   <Mime>application/x-ms-compress-szdd</Mime>

At offset 8 used compression i stored. In most cases this is "A" (0x41).
According to https://www.betaarchive.com/forum/viewtopic.php?t=26161 "B" is
found in Windows 3.1 builds 026 and 034e. So such archive are not detected
by szdd.trid.xml. So mention fact about compression method in remark line.


The remaining variant starts with string "KWAJ". Unfortunately some archives
like WINWORD6.IN_ are not recognized by kwaj.trid.xml but are described
correctly by newest file(1) command (see appended output/file.txt).

According to documents for this variant compression method (range 0-4) is
stored at offset 8. That means that by construct

   <Bytes>4B57414A88F027D10300</Bytes>
   <ASCII> K W A J . . '</ASCII>
   <Pos>0</Pos>

only variant with method number 3 (that is LZ+Huffman) is recognized. So
current trid definition now becomes kwaj-v3.trid.xml. Again add mentioned
reference URL. Also add a specific user defined mime type by line:
   <Mime>application/x-ms-compress-kwaj</Mime>

At offset 12 header flags are stored as little endian short value. If this
is 0 like in example CORELSHW.RE_ then compressed data immediately starts
afterwards at offset 0xe, which is stored as LE short at offset 10.  For
examples with flag 0x19 like AEGYPTEN.BM_ original file size (4 bytes),
original filename with extension ( 13 Bytes AEGYPTEN.BMP with trailing \0 )
is stored afterwards, which gives now offset value 0x1f. So mentioned this
facts in remark line.

For examples like WINWORD6.IN_ create kwaj-v4.trid.xml . Pattern now looks like
   <Bytes>4B57414A88F027D10400</Bytes>
   <ASCII> K W A J . . '</ASCII>
   <Pos>0</Pos>

That means here compression method number 4 (tat is MS-ZIP) is used. So
mentioned this fact in remark line.

I found no examples for methods 0, 1 and 2. Could create 3 more trid
kwaj-v?.trid.xml. Finally i create kwaj.trid.xml generic for all KWAJ
variants with pattern construct like:

   <Bytes>4B57414A88F027D1</Bytes>
   <ASCII> K W A J . . '</ASCII>
   <Pos>0</Pos>
   
   <Bytes>00</Bytes>
   <Pos>9</Pos>
   
With new trid definitions files now all inspected Microsoft compressed
archive are now recognized (see appended output/trid-new.txt).  TrID
definition, some examples and output are stored in archive XY_.zip . I hope
that the 5 XML files can be used in future version of triddefs.

With best wishes
Jörg Jenderek

 9 
 on: November 09, 2017, 11:08:48 pm 
Started by Mark0 - Last post by Mark0
Updated:
Added:
  • KiCad Module (KICAD_MOD)
  • Levelogger Software Data (LEV)
  • KiCad EESchema Netlist (NET)
  • 6502 binary relocation format (O65)
  • KiCad Project (PRO)
  • KiCad Project (updated) (PRO)
  • Levelogger Software XML data Log (XLE)
Deleted:
  • Baldur's Gate character (CHR)

 10 
 on: November 07, 2017, 09:42:00 pm 
Started by Mark0 - Last post by Mark0
Updated:
  • Interplay Compressed Audio Format (ACM)
  • Infinity Engine exported player Character (v1.0) (CHR)
  • Infinity Engine Creature (generic) (CRE)
  • Infinity Engine creature (v1.0) (CRE)
  • Infinity Engine creature (v1.2) (CRE)
  • Infinity Engine save Game (v1.1) (GAM)
  • Infinity Engine World Map (v1.0) (WMP/WMAP)
Added:
  • Infinity Engine Animation (v2) (BAM)
  • Infinity Engine exported player Character (v1.2) (CHR)
  • Infinity Engine exported player Character (v2.0) (CHR)
  • Infinity Engine exported player Character (v2.2) (CHR)
  • Infinity Engine exported player Character (v9.0) (CHR)
  • Infinity Engine exported player Character (generic) (CHR)
  • Infinity Engine creature (v2.2) (CRE)
  • Infinity Engine creature (v9.0) (CRE)
  • DOS Executable (alternate ZM id) (EXE)
  • Infinity Engine save Game (generic) (GAM)
  • Infinity Engine save Game (v2.0) (GAM)
  • Infinity Engine save Game (v2.2) (GAM)
  • Infinity Engine Automatic Installation Package (v1) (IAP)
  • Actor Library Definition (LDL)
  • Actor ObjectGraphics (OGL)
  • Infinity Engine Store (v1.1) (STO)
  • TeamBG Infinity Engine data format (v3) (TBG)
  • TeamBG Infinity Engine data format (v4) (TBG)
  • TeamBG New Infinity Engine data format (v1) (TBGN)
  • Infinity Engine Translation (TRA)
  • Infinity Engine Translation (with rem) (TRA)
  • Infinity Engine Variables (VAR)
  • Infinity Engine Visual Effect (VEF)
Deleted:
  • Interplay ACM audio (ACM)
  • Infinity Engine Music (ACM)
  • Infinity Engine Character (v2.x) (CHR)
  • Infinity Engine save Game (v2.x) (GAM)
  • BioWare Talk Table (TLK)

Pages: [1] 2 3 ... 10
Powered by MySQL Powered by PHP Powered by SMF | SMF © 2001-2010, Lewis Media Valid XHTML 1.0! Valid CSS!
Page created in 0.411 seconds with 14 queries.