Šta je novo?

KaKve su to oznake za .adf fajlove na planetemu..?

dusxan

Slavan
Učlanjen(a)
04.06.2007
Poruke
979
Poena
330
Uz neke diskete stoji npr [a] ili ili ne stoji nista.
Oznaka stoji npr uz drugu disketu dok uz ostale ne stoji nikakva.

Konkretno, pokusavam da upalim ovu igru :

Goblins 3 (1993)(Coktel Vision)[cr FLT](Disk 1 of 6) 378 Ko
Goblins 3 (1993)(Coktel Vision)[cr FLT](Disk 1 of 6)[a] 378 Ko
Goblins 3 (1993)(Coktel Vision)[cr FLT](Disk 2 of 6)[a] 309 Ko
Goblins 3 (1993)(Coktel Vision)[cr FLT](Disk 2 of 6)[b disk label] 691 Ko
Goblins 3 (1993)(Coktel Vision)[cr FLT](Disk 3 of 6)

http://planetemu.net/index.php?section=roms&dat=754&page=g

Pa ako neko ima snage i volje da pripomogne.
Problem nastaje prilikom ubacivanja druge diskete
Probao sam u DFO , u DF1 , pa da u DF0 stoji prva , u DF1 sve verzije druge,
cak sam postavio i [fr] verziju , sistem je ne prepoznaje. Ne razumem u cemu je stvar.
 
Probaj ovako

Gobliiins (1991)(Coktel Vision)(M5)[cr CSL](Disk 1 of 3)

Gobliiins (1991)(Coktel Vision)(M5)[cr CSL](Disk 2 of 3)

Gobliiins (1991)(Coktel Vision)(M5)[cr CSL](Disk 3 of 3)

moraju biti iste u nazivu,ako si primetio nisam ti stavio ni jednu sa a ili b,ako se odlucis za neku sa Goblins 3 (1993)(Coktel Vision)[cr FLT](Disk 1 of 6)[a] 378 Ko onda i druga i treca i deseta disketa moraju biti [a]

Koliko sam ja shvatio ti prefiksi [a],.[a2] i ne znam ti sta jos su u stvari krekovane igre od stane tima razor,skidrow i ostalih iz tih vremena ako ne gresim,konkretno da bi razumeo,kad pokrenes igru ako ti na pocetku izbaci da mozes da podesis od kog levela kreces itd tj naknadno u igru su ubacivali treninge...bar sam ja shvatio to tako

Ja sam imao problem kad sam hteo moonstone da pustim preko emulatora i ako su svi isti u nazivu ili imaju te dodatke...
 
Konkrento za igricu koju sam hteo da ucitam u emulator : disketa 2 ima oznaku [a]
ne znam gde bih mogao da nadjem te diskete bez te oznake.
A nisam bas potpuno siguran da si u pravu. Jer sam dosad radio sa [x] bez problema.
 
evo objašnjenja za te oznake
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)




Underdump (not enough data dumped)




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)"
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)"
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 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".


 
Hvala marti ;
Evo ako nekome treba, za igru Goblins 3 ovako je radilo (jedino je mali smor jer uopste nema podrsku za df1)

poceti sa 1 i 2b
u igri 1a i 2a

(zasto mora bas ovako - nemam pojma)
 
A ko bas ne zeli da se smara ode na : http://www.whdownload.com/ odaberes G i imas sve gobline dole skines goblins3 raspakujes arhivu i uzivas u whdload preinstaliranoj igri i ne menjas diskete.
 
evo objašnjenja za te oznake
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)




Underdump (not enough data dumped)




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)"
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)"
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 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".




http://www.tosecdev.org/
 
Vrh Dno