.adf syntax of the ending of games

[Daniele]

Does anyone of you know the exact meaning of the syntax ending of the .ADF collection games?

I mean:

gamename[a].adf
gamename[m].adf
gamename[m1].adf
gamename[m2].adf

what is the meaning of [m],[a],[m1],[m2] etc??

Thanks in Advance

Daniele wrote:
Does anyone of you know the exact meaning of the syntax ending of the .ADF collection games?

I mean:

gamename[a].adf
gamename[m].adf
gamename[m1].adf
gamename[m2].adf

what is the meaning of [m],[a],[m1],[m2] etc??

Thanks in Advance

You seem to refer to the information codes used in the TOSEC collections.

Look for TOSEC on google and wikipedia.

[McVenco]

what is the meaning of [m],[a],[m1],[m2] etc??

http://www.tosec.info/modules/wfsection/article.php?articleid=2

[Daniele]

I gave a look on the Wikipedia and Googled TOSEC but I cannot find the meaning of the .Adf files ending with
[m],[a],[m1],[m2] etc??


Any help?

[James]

It means you probably shouldn't be asking the question on this forums as TOSEC is generally frowned upon by the most hardcore members

However.. a (very very) quick web search returned me this:

Code: [Select]


This is the 'alphabet soup' used to describe the nature, quality and condition of the particular image of the software (not the software as a whole). This is where images that are bad, alternates, cracks, hacks, trainers, fixes, translations, etc. are noted.

Note: These flags use square brackets [ ]

[p]

Pirate version (non-licensed release)

[cr]


Cracked (copy protection removed)
[cr Cracker]

Cracked by Cracker (group or person)

[f]


Fixed (hack added for extra functionality)
[f Fix] Fix added
[f Fix Fixer] Fix added by Fixer (group or person)


Some examples of fixes:

NTSC = Fixed for NTSC
copier = Fixed for game-copiers
save = hiscore save function added

[h]


Hacked (general hack)
[h Hacker]

Hacked by Hacker (group or person)

[m]


Modified (general hack)
[m Modifier]

Modified by Modifier (group or person)

[t]


Trained
[t Trainer] Trained by Trainer (group or person)
[t +x] x denotes number of trainers added
[t +x Trainer]

Trained and x number of trainers added by Trainer (group or person)

[tr]


Translation
[tr Language] Translated to Language
[tr Language Translator]

Translated to Language by Translator (group or person)

[a]

Alternate version
[a Descriptor] Alternate (including reason)


Some examples of descriptors:

highscore = Only a highscore table entry is different from a non [a] image
readme = Only a readme file is different from a non [a] image

[o]


Overdump (too much data dumped)

[u]


Underdump (not enough data dumped)

[b]


Bad dump (incorrect data dumped)
[b Descriptor]

Bad dump (including reason)


Some examples of descriptors:

corrupt file = Image contains a corrupt file
read-write = Image has a read/write error

[v]


Virus (infected)
[v Virus] Infected with Virus
[v Virus Version]

Infected with Virus of Version

[!]


Verified good dump

Please note that wherever "Group" is used in the above table, the alteration could also be done by single persons, but renamers should be aware that taking the group they're in (if known) is always better.

    Ex: "Legend of TOSEC, The (1986)(Devstudio)(US)[a]"

    Ex: "Legend of TOSEC, The (1986)(Devstudio)(US)[b]"
    Ex: "Legend of TOSEC, The (1986)(Devstudio)(US)[cr]"
    Ex: "Legend of TOSEC, The (1986)(Devstudio)(US)[tr Fr]"
    Ex: "Legend of TOSEC, The (1986)(Devstudio)(US)[h Fairlight]"
    Ex: "Legend of TOSEC, The (1986)(Devstudio)(US)[o]"

In case where multiple images exist that need the same dump info flags, the flag is numbered as follows:

    Ex: "Legend of TOSEC, The (1986)(Devstudio)(US)[a]"
    Ex: "Legend of TOSEC, The (1986)(Devstudio)(US)[a2]"

    Ex: "Legend of TOSEC, The (1986)(Devstudio)(US)[a3]"
    Ex: "Legend of TOSEC, The (1986)(Devstudio)(US)[a4]"
    Ex: "Legend of TOSEC, The (1986)(Devstudio)(US)[b]"
    Ex: "Legend of TOSEC, The (1986)(Devstudio)(US)[b2]"
    Ex: "Legend of TOSEC, The (1986)(Devstudio)(US)[b3]"
    Ex: "Legend of TOSEC, The (1986)(Devstudio)(US)[cr]"
    Ex: "Legend of TOSEC, The (1986)(Devstudio)(US)[cr2]"

There is no [n1] , so, for example, you will need to have a [b] for a [b2] to exist.

When dealing with flags that can relay more information, be sure to not add numbers if it is not necessary to remain unique. If, for example, the Cracking Group can be used to distinguish between different files, use that instead:

    Ex: "Legend of TOSEC, The (1986)(Devstudio)(US)[cr]"
    Ex: "Legend of TOSEC, The (1986)(Devstudio)(US)[cr PDX]"
    Ex: "Legend of TOSEC, The (1986)(Devstudio)(US)[cr TRSi]"
    Ex: "Legend of TOSEC, The (1986)(Devstudio)(US)[cr2]"

    Instead of:

    Ex: "Legend of TOSEC, The (1986)(Devstudio)(US)[cr]"
    Ex: "Legend of TOSEC, The (1986)(Devstudio)(US)[cr2 PDX]"
    Ex: "Legend of TOSEC, The (1986)(Devstudio)(US)[cr3 TRSi]"
    Ex: "Legend of TOSEC, The (1986)(Devstudio)(US)[cr4]"

A dump info flag can only be used once (except in the case of compilations ). So, if something was hacked by PDX, then hacked again by TRSi, do not use:

    Ex: "Legend of TOSEC, The (1986)(Devstudio)(US)[h PDX][h TRSi]"

Instead, use one of the following, depending on how the program was altered.

    Ex: "Legend of TOSEC, The (1986)(Devstudio)(US)[cr PDX][h TRSi]"
    Ex: "Legend of TOSEC, The (1986)(Devstudio)(US)[h PDX - TRSi]"

For a co-operative crack from both Paradox and TRSI, use:

    Ex: "Legend of TOSEC, The (1986)(Devstudio)(US)[cr PDX + TRSi]"

For further information, read the section "When to use which Dump Info Flag".


[McVenco]

Any help?

Yes. Clicking on the link in my previous message may help. Explanation is all there.

[Daniele]

I readed all the explanation you kindly gave to me and I really appreciated it but I still don't understand only [m] and [m1],[m2] etc.

When I do ADF to Disk ore use the EasyADF PCMCIA Compact Flash Transfer Kit what adf is convenient to unpack the one missing m and ending only with .adf or the [m] or [m1] etc ones?

Thanks

[Piru]

I still don't understand

You'd better just stay away from pirating then.