This little tutorial will be for PDA releases of course
According to release standards dated 2002 (bit old) Release names should be created in such way:
PPC/Smartphones/HPC
<program name>.vX.xx.<optional Language>.CPU.OP-SYS.<cracktype>-<groupname>
Palm
<program name>.vX.xx.<optional Language>.PalmOS.<cracktype>-<groupname>
(now after PalmOS also can be version i.e. PalmOS5)
Symbian
<program name>.vX.xx.<optional Language>.Machine-Type.SymbianOS.<cracktype>-<groupname>
Java
<program name>.vX.xx.<optional Language>.Resolution.Machine-Type.J2ME.<cracktype>-<groupname>
In names can be used "." or "_"
Program name: Producer.Program name i.e. "Gameloft.Las.Vegas.Nights"
vX.xx stands for exact version of software
In Symbian for Machine-Type are used
For nokia phones:
S60
S60v2
S60v3
For Sony Ericsson:
UIQ
UIQv3
SymbianOS now also with version i.e. SymbianOS9.1
PPC/Smartphones/HPC
OP-SYS can be
CE that is CE 2.0
PPC that is for WinCE 3.0 but its not called CE, 99runs also on new ARM
machines with PPC2002
HPC2000 that is a HandheldPC with keyboard (no pen) only ONE from HP existing
PPC2002 that is successor of PPC now most common and runs only on ARM machines
Now are also used tags WM2003 for Windows Mobile 2003 WM2005, WM6 as for WM2003.
For Smartphones it can be Smartphone200x for all smartphones, Smartphone2005 for Windows Mobile 5.0 smartphones, etc.
CPU types can be
SH3 is SH3 CPU
MIPS is MIPS CPU
ARM is STRONG ARM CPU
IPAQ is NOT a cpu but runs ARM , there are progs that run only on IPAQ so IPAQ has to be named as CPU
XScale is Intel XScale CPU (used now, in 2002 there wasn't such CPU)
Java
Resolution and machine type is obvious I guess (they stand for resolution of app and machine it was tested on) i.e. 176x220.SE.K750
CRACKTYPES :
************
can be :
Regged serial data is included in nfo
Cracked the program file has been altered to register the
proggy. The program is then "Preregistered", "any
name and/or serial can be entered" or "nags/trials
removed"
Incl.Keymaker if keymaker is included in package
Incl.Keymaker.Patch if program is patched and shows correct
serial relating to the hotsyncname(palmos,ppc) after
program start or after entering any serial
Incl.PalmOS.Keymaker if keymaker for PalmOS is in the package (if you wanna
use some kind of plugin system for your keygen you HAVE
to incl. the plugin-proggy too (not only the plugin))
Incl.WinCE.Keymaker if keymaker for WinCE is in the package (if you wanna
use some kind of plugin system for your keygen you HAVE
to incl. the plugin-proggy too (not only the plugin))
Incl.Java.Keymaker if keymaker comes via java applet, the java applet has
to be delivered with a name.html file that loads the
java app.
From important releasing rules there is also 'cracktype' called:
Retail: A retail is treated like a crack with these exceptions:
- You are allowed to release a retail after
a serial/crack/keygen/keygenpatch IF (!) there's something special
added (some kind of extra stuff that you dont have in the shareware/
demo version). If thats the case you have to add a READ.NFO to the
dirname and list whats the additional stuff.
All releases must be (zip-)packed with the necessary files for the release and
a .nfo and .diz from the group.
In .nfo are informations about release like release date, operating system, protection, description, optional or obligatory (if i.e. keygen.only) site where to download etc. So read it :!: To read .nfo you can use any ANSI editor like notepad or specialized like DAMN NFO Viewer. .diz file contains only basic information about release, all is also in .nfo
BTW release can also be NUKED in the pre channel if violating scene rules: is DUPE (duplicate), bad crack, etc. Only several people can nuke a release, they are called nukers, all nukes will include reason.
Final Notes
Hope I explained a little code used on warez scene and you'll know how to use release
Any comments, questions are welcome. I missed some parts. Sorry if this isn't appropriate section (I didn't know where to put it).
