Author Topic: ISO files  (Read 17697 times)

viva_emptiness

  • Newbie
  • *
  • Posts: 1
ISO files
« on: October 28, 2006, 07:09:05 PM »
hi:
see this TrID report about ISO file format:
*****************************************************
C:\>trid e:\bootable.iso -v -d:c:\windows\system32\TrIDDefs.TRD

TrID/32 - File Identifier v2.00 - (C) 2003-06 By M.Pontello
Definitions found:  2279
Analyzing...

Collecting data from file: e:\Bootable.iso

Warning: file seems to be plain text/ASCII
         TrID is best suited to analyze binary files!

 91.3% (.SPU) Spectrum 512 bitmap (160000/1)
       Definition   : bitmap-spu.trid.xml
         Files      : 4
       Author       : Marco Pontello
         E-Mail     : marcopon@nospam@myrealbox.com
         Home Page  : http://mark0.ngi.it

  2.2% (.GRA) OpenGL object (4003/2)
       Definition   : gra.trid.xml
         Files      : 5
       Author       : Marco Pontello
         E-Mail     : marcopon@nospam@myrealbox.com
         Home Page  : http://mark0.ngi.it
************************************************
Thanks.

Mark0

  • Administrator
  • Hero Member
  • *****
  • Posts: 2743
    • Mark0's Home Page
ISO files
« Reply #1 on: October 28, 2006, 07:38:52 PM »
Unfortunately ISO (like many other type of images files) haven't enough "structure" / patterns to be recognized correctly.

Bye!

Mark0

  • Administrator
  • Hero Member
  • *****
  • Posts: 2743
    • Mark0's Home Page
Re: ISO files
« Reply #2 on: October 29, 2006, 02:29:12 AM »
To expand my post, it's better to say that it isn't possible to create a generic ISO definition; you can have two images, one entirely full of 0 bytes, and one with random bytes, and the two would have nothing in common, but still be valid images.

But, it is probably possible to create some new defs dealing with specific images subtypes / categories; for example, if you scan with TrIDScan various bootable Windows images, you may be able to create a working defs that should recognize them.

Bye!
« Last Edit: October 29, 2006, 11:14:28 AM by Mark0 »

bobsool

  • Guest
Re: ISO files
« Reply #3 on: May 07, 2007, 10:05:20 PM »
I would think you could identify the file system of the image. For example ISO1660, CDDA, CD Extra, UDF etc... Of course it's possible to have bootable CDs with hard drive images on them... they may have ISO extension, but in fact be FAT,hpfs,ntfs,ffs,bfs(quite common with BeOS 5 Live discs),hfs or hfs/iso(very common for discs written with a Classic Mac) or ext2fs images... this too should be identifiable, as the file system has as unique a property as a file. However, identifying such sub types is rather like identifying IFF files... an IFF file could be a sound, movie, picture, text, hypertext or anything else... Windows WAV files are IFF compliant, but so are AIFF Apple files, Quick Time Mov files and Amiga IFF/LBM files.

For me, this is where TrID becomes interesting... because LBM, ILBM or IFF would be valid extensions for an Amiga bitmap graphic... but, especially if the extension where IFF, that would still be valid for Quick Time MOV or QT file, an AIFF file, a IFF/SND file... but which is it? Just as an ISO could be a Audio CD image, a bootable Windows, Linux or BeOS image, a DVD/VideoCD/SVCD or many other things. Having definitions for the sub types is what is important.

As stated on Mark0 site, please classify what kind of ISO you are looking at, as though they were different versions of Word .DOC files. ;)

TippeX

  • Newbie
  • *
  • Posts: 2
Re: ISO files
« Reply #4 on: May 24, 2009, 12:18:49 AM »
i think you'll find some common patterns if you look at sector 16 (file offset 0x8000) if its an iso file...
it should begin with a noticable tag :) unsure if trid seeks that far though

Mark0

  • Administrator
  • Hero Member
  • *****
  • Posts: 2743
    • Mark0's Home Page
Re: ISO files
« Reply #5 on: May 24, 2009, 01:06:59 AM »
Hi TippeX!

Indeed, TrID doesn't look that far (at least in the present version).

Bye!