___ ___ _ ___ _ _ ___ ____ ___ _ ___| __| __(_)/ __(_)__ _| | | _ \ _ \ / _ \ _ _ _ _| |___ ___ / _ \ _|| _|| | (__| / _` | |__ | _/ |_) | _ | '_| || | / -_|_-< \___/_| |_| |_|\___|_\__,_|____| |_| |____/|_| |_|_| \_,_|_\___/__/ cREATION dATE : [14]-[APR]-[2002] ____/\_____/\_____/\_____/\_____/\_____/\_____/\_____/\_____/\_____/\____ |___> <___> <___> <___> <___> <___> <___> <___> <___> <___> <___| \/ \/ \/ \/ \/ \/ \/ \/ \/ \/ RELEASE-NAME-CREATION : *********************** l .vX.xx..PalmOS.- l l l .vX.xx..Machine-Type.SymbianOS.- l l Machine-Type : e.g. N9210 or N9210i (Nokia Communikator) l l l .vX.xx..CPU.OP-SYS.- l l OP-SYS can be l l CE that is CE 2.0 l PPC that is for WinCE 3.0 but its not called CE, 99% runs also on new ARM l machines with PPC2002 l HPC2000 that is a HandheldPC with keyboard (no pen) only ONE from HP existing l PPC2002 that is successor of PPC now most common and runs only on ARM machines l l CPU types can be l l SH3 is SH3 CPU l MIPS is MIPS CPU l ARM is STRONG ARM CPU l IPAQ is NOT a cpu but runs ARM , there are progs that run only on IPAQ so IPAQ has l to be named as CPU l l For future extensions : l If there is a program version for a special machine then name the machine type l instead of the cpu ( see the IPAQ example above ! ) l l l or use underscores if you like: l l _vX.xx__PalmOS_- l _vX.xx__ALL_OP-SYS_- l _vX.xx__SymbianOS_- l l l has to be pda to part the pda section !!! l l l Examples: WOMAN.v1.4.JAPANESE.PalmOS.Regged-GROUPpda l WOMAN_v1.4_JAPANESE_PalmOS_Regged-GROUPpda l WOMAN.v1.4.JAPANESE.ARM.PPC2002.Regged-GROUPpda l WOMAN_v1.4_JAPANESE_ARM_PPC_Regged-GROUPpda l WOMAN_v1.4_JAPANESE_SymbianOS_Regged-GROUPpda l l optional language tag should only be used on NON english releases... l l l l EBOOKS : l ******** l l ...OP-SYS.- l l Edition : Bookversion or Edition l OP-SYS : OperatingSystems eg. PalmOS, PPC l l l l l CRACKTYPES : l ************ l l can be : l l Regged serial data is included in nfo l Cracked the program file has been altered to register the l proggy. The program is then "Preregistered", "any l name and/or serial can be entered" or "nags/trials l removed" l Incl.Keymaker if keymaker is included in package l Incl.Keymaker.Patch if program is patched and shows correct l serial relating to the hotsyncname(palmos,ppc) after l program start or after entering any serial l Incl.PalmOS.Keymaker if keymaker for PalmOS is in the package (if you wanna l use some kind of plugin system for your keygen you HAVE l to incl. the plugin-proggy too (not only the plugin)) l Incl.WinCE.Keymaker if keymaker for WinCE is in the package (if you wanna l use some kind of plugin system for your keygen you HAVE l to incl. the plugin-proggy too (not only the plugin)) l Incl.Java.Keymaker if keymaker comes via java applet, the java applet has l to be delivered with a name.html file that loads the l java app. l l if a Keymaker is only in the package then a url to get the prg has to be l included in nfo ! l l if a Serial (HOTSYNC independent!) is only in the package then a url to get the prg l has to be included in nfo ! l l l l l Allowed are : l l Keymaker.Only l JAVA.Keymaker.Only l PalmOS.Keymaker.Only l OPL.Keymaker.Only (Epoc16) l OP32.Keymaker.Only (Epoc32) l CPU.OP-SYS.Keymaker.Only l l l Keymakers can be written in : l l Dos, Win32, PalmOS, WinCE, Java ( with start.html ) l l RELEASE RULES : l *************** l l Release format/size : l l If a release is bigger than 1.44 mb then it has to be parted in 1.44/2.88 MB l packages ( ISO can be packed with rar (most common) ) l l l l Keygens: A keymaker is allowed to be only (re-)released l 1) when a major version hop of the application occurs i.e. l 1.xx -> 2.xx l 2) when the key algo changes. An algo-change has to be announced l by including READ.NFO in dirname AND a short l description in the nfo (for example: "Keygenalgo changed ...") l 3) when there has not been a re-release within a 1/2 year. l l Example(1) : Keymaker released first time for v1.43 . l The first time it can be replaced for not being a dupe is when l the version changes to v2.xx or if the keyalgo changes. So also l in v1.44 ;) l Example(2): Prog.v1.1.incl.Keymaker-GRP released 01/01/2000 l the next allowed release date for Prog.v1.11.incl.Keymaker-GRP l would be 01/01/2001. Its (of course) not allowed to release the l SAME version again after a 1 year :P l l Keymaker.Only releases are allowed, but then include the url where l where to download the program in the nfo. l l Keygenpatch: A Keygenpatch is a patch that alters the program that it shows the l right serial for the actual hotsync (and which regs it of course). l Keygenpatches are like Keygens (same rules here) with one difference: l Its allowed to release a Keygen after a Keygenpatch l (even for the same version) l l Cracks: Cracks in form of patched programs can be released for every l version UNTIL they got keygened or a serial is released. l If a keygen or serial gets invalid for some reason a new crack l can be released. l l Regged: Can be a serial or name + serial. (hotsync id independent) l (Serial) Same rules as for keygens apply here (major version hops, serial l change, 1 year rule...) l l Retail: A retail is treated like a crack with these exceptions: l - You are allowed to release a retail after l a serial/crack/keygen/keygenpatch IF (!) there's something special l added (some kind of extra stuff that you dont have in the shareware/ l demo version). If thats the case you have to add a READ.NFO to the l dirname and list whats the additional stuff. l l Normally retails should be released when its not possible to download l an uncrippled version which can be regged/keygenned. l l l All releases must be (zip-)packed with the necessary files for the release and l a .nfo and .diz from the group. IMPORTANT INFO TO SITEOPs : *************************** l As we have seen in the past, there are some rules which prevent groups l releases being nuked on an affiliate site. We think that if a valid nuke l reason applies to any release, it should be nuked on all sites - affil or l not. l l ->>> AFFIL PREVENTS NOT FROM BEEING NUKED !!! << l RULES SIGNED BY l -+-+-+-+-+-+-+-+- l l APR 2002 -- COREpda l APR 2002 -- UFCpda l APR 2002 -- BLZpda Ok there is 2 main changes to this set of rules.. 1) The 1yr rule listed above has now been changed to 6mths 2) The filesize can now be a MAX of 5mb parts