Mark0's software support board
May 26, 2017, 01:51:57 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: May 23, 2017, 04:27:48 pm 
Started by Mark0 - Last post by Mark0
Added:
  • DOS 2.0-3.2 backup ()
  • DOS 2.0-3.2 backup part ()
  • Ultimate Stunts 3D-editor texture (DAT)
  • DaVinci Resolve eXchange data (DRX)
  • Embird Cross stitch Format (ECF)
  • Simplify3D profile (FFF)
  • Garmin Zipped geocache (GGZ)
  • Ultimate Stunts binary 3D geometry (GLB)
  • Windows LM data (LM)
  • Ultimate Stunts Replay (REPL)
  • Ultimate Stunts Track (TRACK)
Deleted:
  • Spectrum 512 Anispec animation (SPS)

 2 
 on: May 23, 2017, 03:55:00 pm 
Started by jenderek - Last post by Mark0
Thanks as usual!

 3 
 on: May 22, 2017, 12:57:22 am 
Started by jenderek - Last post by jenderek
Hello,

when i run trid on some old DOS backup files (see backup.lst) these
are misidentified as "MP3 audio", "MacBinary 1 header", "MacBinary 2
header", "DEGAS med-res bitmap", "TTComp archive compressed" or
others ( see appended output/trid-old.txt )

The newest file(1) command version (http://darwinsys.com/file/)
identifies such examples correct as "DOS 2.0-3.2 backed up" ( see
appended output/file-new.txt )

The format of such files is described in BACKUP & RESTORE document for
the Free DOS project found for example at
http://www.ibiblio.org
/pub/micro/pc-stuff/freedos/files/dos/restore/brtecdoc.htm
So i add to new trid definition files this URL as reference.

According to Free DOS documentation test for padding 44 unused bytes
in header which seem to be nulls by XML construct like
<Pattern>
   <Bytes>0000000000000000000000000000000000000000000000</Bytes>
   <Pos>84</Pos>
</Pattern>

At offset 5 a string field with size 78 starts containing full pathname
of the backed-up file. This string is zero terminated. This means last
byte of this field is null. This is now described by construct
   <Pattern>
      <Bytes>00</Bytes>
      <Pos>82</Pos>
   </Pattern>

The pathname of the backed-up file is stored without drive letter and
colon part ( like C: ). That means file name string starts with path
separator.
I found only real world examples that start with DOS path separator
( 5Ch = backslash = "\"). But according to V32SLASH.TXT in archive
PD0315.EXE UNIX variant (2Fh = slash= "/") can also occur.

Together with test of some other unknown bytes (that are also null
bytes) test for DOS path separator is expressed by construct
   <Pattern>
      <Bytes>0000005C</Bytes>
      <ASCII> . . . \</ASCII>
      <Pos>2</Pos>
   </Pattern>

At the beginning a flag byte is stored, where FFh means complete file
process and 00h means split file. So i create 2 variant definition files.

The first is msbackup-v2.trid.xml with additional XML construct
      <Pattern>
         <Bytes>FF</Bytes>
         <Pos>0</Pos>
      </Pattern>


The second is msbackup-v2part.trid.xml describes backup parts where
sequence number is stored at offset 1 by additional XML construct
      <Pattern>
         <Bytes>00</Bytes>
         <Pos>0</Pos>
      </Pattern>

According to Free Dos documentation Microsoft and IBM use different
backup file format in different DOS versions. The format described by
above patterns is used in version 2.0 till 3.2. So such files are
described as "DOS 2.0-3.2 backup file"

The backup filename is the same as original filename. So if you backup
an DOS executable file name extension is "EXE". Backup of Word
documents have "DOC" extension and so on. So all allowed DOS extension
can occur. I do not know if this 100% valid but describes this fact by
construct:
   <Ext>*</Ext>

With these 2 new definition files finally all my DOS BACKUP files
are now recognized ( see appended output\trid-new.txt ).

trid definitions and output are stored in archive backup.zip.
I hope that my XML files can be used in future version of triddefs.

With best wishes
Jörg Jenderek

 4 
 on: May 19, 2017, 03:49:59 pm 
Started by Mark0 - Last post by Mark0
Added:
  • Gherkin Feature (FEATURE)
  • Natron Node Preset (NPS)
  • Origin Function Plot (OFP)
  • Spectrum 512 Anispec animation (SPS)
  • Spectrum 512 Extended bitmap (SPX)

 5 
 on: May 16, 2017, 10:55:17 pm 
Started by Mark0 - Last post by Mark0
Added:

 6 
 on: May 15, 2017, 06:45:30 pm 
Started by Mark0 - Last post by Mark0
Updated:
  • FreeMind mind map (MM)
  • Portable Arbitrary Map bitmap (PAM)
Added:
  • ADInstruments compound file format ()
  • Device Tree Blob/Overlay (DTB/DTBO)
  • Molden Format (MOLDEN)
  • Molden OpenGL model (OGL)
  • Linux perf file format (PERF)

 7 
 on: May 12, 2017, 03:44:28 pm 
Started by Mark0 - Last post by Mark0
Added:
  • JPC snapsot ()
  • Altirra save state (ALTSTATE)
  • BlockHashLoc data (BHL)
  • Prescription Drug Event format (PDE)
  • Dioscuri config (XML)

 8 
 on: May 09, 2017, 04:27:45 pm 
Started by Mark0 - Last post by Mark0
Added:
  • NeXT typedstream serialized data (BE) ()
  • NeXT typedstream serialized data (LE) ()
  • DOS 2.0-3.2 Backup control info (@@@)
  • DOS 2.0-3.2 Backup control info (lastdisk) (@@@)
  • SeeYou Raster Map (CMR)
  • ArcView World File (TFW)

 9 
 on: May 08, 2017, 02:16:28 am 
Started by jenderek - Last post by Mark0
Will add on the next update!
Thanks!

 10 
 on: May 08, 2017, 12:53:38 am 
Started by jenderek - Last post by jenderek
Hello,
when i run trid on some old DOS backup files like BACKUPID*.@@@ these
are misidentified as "MP3 audio", "MacBinary 1 header", "Adobe PhotoShop Brush",
"DEGAS med-res bitmap", "Sybase iAnywhere database files" or others ( see
appended @@@-old.txt )

A good starting point for such files is archiveteam org website
So i add to new trid definition files this URL as reference by line
   <RefURL>http://fileformats.archiveteam.org/wiki/BACKUP_(MS-DOS)</RefURL>

The format of such files is described in BACKUP & RESTORE document for
the Free DOS project found for example at
http://www.ibiblio.org
/pub/micro/pc-stuff/freedos/files/dos/restore/brtecdoc.htm

According to Free DOS documentation test for padding 121 nul bytes by XML
construct like
   <Pattern>
      <Bytes>0000000000000000000000000000000000000000</Bytes>
      <Pos>7</Pos>
   </Pattern>

Unfortunately this file format has no characteristic magic pattern. The backup
sequence id is stored offset 1, year at offset 3, day at 5 and month at 6.

Real world examples are dated about 1983 and little later according to
https://en.wikipedia.org/wiki/Timeline_of_DOS_operating_systems.
So it is sufficient to test year in range from 1792 till 2047 (0700h-07FFh) or
expressed as XML construct:
      <Pattern>
         <Bytes>07</Bytes>
         <Pos>4</Pos>
      </Pattern>

At the beginning a flag byte is stored, where FFh means last file of backup
process and 00h means not last. So i create 2 variant definition file.

The first is @@@.trid.xml with XML construct
      <Pattern>
         <Bytes>00</Bytes>
         <Pos>0</Pos>
      </Pattern>
The second is @@@-last.trid.xml with lines
      <Pattern>
         <Bytes>FF</Bytes>
         <Pos>0</Pos>
      </Pattern>

According to Free Dos documentation Microsoft and IBM use different backup file
format in different DOS versions. The format described by above patterns is used
in version 2.0 till 3.2. So such files are described as "DOS 2.0-3.2 backup
control file"

With these 2 new definition files finally all my BACKUPID.@@@ files
are now recognized ( see appended output @@@-new.txt ).

trid definitions and output are stored in archive backupid.zip.
I hope that my XML files can be used in future version of triddefs.

With best wishes
Jörg Jenderek

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.322 seconds with 14 queries.