——————————————————————————————-

URL = http://alt-bin.com/index.php?pg=top20l&ch=alt.binaries.sounds.mp3.complete_cd
Server = EFNET
Channel = #Alt.Binaries.Sounds.Mp3.Complete_cd
NHH ADMiN = Error403

Whois Error403 ùùùùùùùùùùùù
Address: (anon@packet.me.you.shall.never.even.get.me.laggy.us)
Server: irc.blessed.net (Blessed.Net IRC Server)
Real Hostname: 64.32.21.14 (actually using host)

Whois Error403 ùùùùùùùùùùùù
Address: (Error403@LinkNet-0fdf7bd11d.fios.verizon.net)
Server: link-net.org (LinkNet IRC Network)

There releases are bull shit .. transcoded .. reencoded . the releases with scans are supplyed
by p2p members they affil ovh and rented .us locations . Error403 is a nuker for SHEEPNET
using the same nickname he uses for p2p. Obviously he thinks he is smarter than every 1 else
but he is just another insecure p2p piece of shit.

Try and tell every one now that this nfo is fake Error403.

You can not talk you’re way out of this one

Also if you are going to use a nfo do not steal the same template that FKK a real group! uses

——————————————————————————————–

Top 20 Fillers – Congrats!

Place Name Score Filled
————————————–
1 ^BaM^ 86884 3107
2 Error403 74110 3824
3 doodmangu 56916 3355
4 Wesley_89 46710 2445
5 ElusiveHa 37754 1878
6 Used-Rubb 32498 1732
7 tcharger 30000 1662
8 [Psycho] 26519 1057
9 KaPH33n 22508 1315
10 seraph47 22321 1100
11 Migs_ 22054 1137
12 laars 21596 1287
13 sysop_ 20960 1363
14 tokyojihe 20125 1362
15 TiNRiB 17993 1033
16 DaBigMang 16595 959
17 n0s- 16446 719
18 EvoIX9 15836 803
19 jake- 15808 1070
20 oshitson 15752 83
————————————–
Included are scans of the altbin website clearly showing about 80% of his uploads are NHH and NHH_INT
material.

EDIT:
AFTER THE LAST NFO RLS ABOUT US WITH SOME WEBSITE PROOFS(15 MINS AGO), WE WANT THE WRITERS OF THAT NFO TO GO TO WWW.MININOVA.ORG AND START PROVING THAT ALL THE RLS THAT SHOW UP THERE WITH GRP TAGS ARE LEAKED BY THEM…
OH AND SO THAT YOU KNOW, IF YOU CHECK KIMERA1.JPG IT TALKS ABOUT A GUY CALLED STOKP RELATED TO KIMERA, IF YOU FIND HIM LET US KNOW SINCE WE DONT KNOW HIM…
FURTHERMORE THAT SCREEN IS FROM 17 DECEMBER, AND IF YOU READ THROUGH IT IT SAYS, ART CHANGED HIS NAME TO KIMERA LIKE IF IT WAS THEIR NEW TAG OR SOMETHING, BUT IF YOU RESEARCH OUR GROUP INFO:
[23:53] Total: 1611 NUKED: 21 ( 1% ) INTERNAL: 4 FIXES: 20 Quality: 99%
[23:53] First Release: Pop.Star.DVD.XviD.MP3.2005.ES-KiMERA XVID @ 01.07.2006 17:02:32
[23:53] Last Release: Eureka.S03E04.2008.SPANISH.HDTV.XviD-KiMERA HDTV @ 08.02.2009 22:47:12
[23:53] Last Nuke: Eureka.S03E03.2008.SPANISH.HDTV.XviD-KiMERA HDTV @ 30.01.2009 16:21:52 NUKED: english.audio
WE STARTED 2 YEARS AGO, EITHER THE “BLOG” IS WRONG OR THE DUPENET IS FUCKED UP…
OH AND BEFORE ANYONE THINKS DIRTY OUR FIRST SCREENER RLS WAS PREED ON THE:
18-11-2008, 1 MONTH BEFORE THAT SCREEN… NICE
[23:57] !pre Las.Horas.Del.Verano.2008.SPANISH.DVDSCR.XViD-KiMERA
[23:57]  [XVID] Las.Horas.Del.Verano.2008.SPANISH.DVDSCR.XViD-KiMERA (49F/693.1MB of Drama) pred 11w 5d 22h 58m 44s ago. @ 18.11.2008 01:00:31

This is intended as an addendum to the existing 0day rules. All the old rules
are still valid, unless they have been altered or updated by this addendum.

The 0day scene has gone through major changes in this decade. As technologies
have changed, so have we, but our adaptations have left many grey areas in the
current rules. The last rules update was years ago when programs were much
smaller and transfer speeds much lower. The existing 0day rules did not address
problems of software encountered today, simply because at that date it did not
exist. These changes have led to a series of loopholes which groups have been
taking advantage of. The new rules we constructed aim to close these loopholes,
as well as increase the general quality level of releases in the scene.

This document covers a new ruleset for 0day. These rules and guidelines are
intended for release-groups in the first place, and sites secondary. We hope
that in time many sites will take over the majority of these rules. The
following groups have signed and committed to following these rules:

ACME AiR AGAiN ALiAS ARN BACKLASH BEAN BLiZZARD BRD CORE CRD
CROSSFiRE DIGERATI DVT EMBRACE FALLEN FAS iNViSiBLE LND
MESMERiZE NGEN NULL ORiON OUTLAWS RiTUEL ROGUE
SHOCK SSG TBE UNLEASHED VACE ZWT

These rules will go into effect starting January 31st, 2010.

* Release Name
~~~~~~~~~~~~~~

[.].v[.][.][.]
[.][.]-

Developer.Name is only mandatory if the application name is not unique enough
for duping. Groups should use some common sense to keep the directory name
reasonable length.

The program name should be the “official” name of the application. Do not omit
dashes, think of your dupe results.

The Language tag must be used only on NON english releases. Multilingual and
bilingual are optional.

Currently valid OS tags are:
– Win98, WinME, WinNT, Win2k, WinXP, Win2k3, Vista, Win2k8, Win7
(can have an optional tag for more specific edition)
– [Distribution.]Linux
– MacOSX
– [Free|Net|Open]BSD
– [Open]Solaris
– AIX
– HPUX
– Open.Enterprise.Server (NetWare)

The Operating.System tag should be omitted when WinAll (= NT5 based windows
and optionally earlier, always with latest official service pack). Using a
UnixAll (= all of the operating systems above, excluding Windows, Linux or
MacOSX) or a WinAll tag means your app *must* run on *all* of the operating
systems that fall under it.

CPU should be omitted when x86, must be x64 for x86_64/EM64T, but not IA64!
Currently valid CPU tags are:
– x86, x64, IA64, PPC, SPARC, SPARC64, RISC, Alpha

Release.Type can be omitted for Crack/Regged, but is mandatory for keygen
releases. Possible tags are:
– Keygen.Only Keymaker.Only
– Incl.Keygen Incl.Keymaker
– Incl.Keygen.and.Patch Incl.Keymaker.and.Patch
– Cracked
– Regged

Additional.Tags like READ.NFO, DIRFIX, NFOFIX.. must go as follows:
– DevelopersName.ProgramName.v1.2.Regged.READ.NFO-GROUP
– DevelopersName.ProgramName.v1.2.Regged.DIRFIX-GROUP

You can use underscores or dots as seperator in the releasename, but do not mix
them if there is no reason for it (e.g. a program name contains underscores and
your seperator is a dot is a valid reason to mix)

The lists in this section are by no means complete. They are here to serve as a
guideline for proper dirname construction.

* Packaging:
~~~~~~~~~~~~

Filenames must be named up to a maximum of 8.3 characters (filename/extension).

Acceptable compression format at this time is any compression method that
supports multiple volumes and long file names, followed by the traditional
PKZIPing. Compressions other than RAR should include an extract utility or be a
self-extracting archive.

The traditional packaging methods (zip/diz) shall be maintained, with a diz
file being present in each zip. The diz file should contain as a bare minimum
the number of the current disk and the maximum number of disks.

Suggested file_id.diz layout is as follows:
[xx/??], where ?? is the total nr of disks in the release. The total number
of lines of your diz should not exceed 30.

On a side note: using ridiculous compressions that will save 10 disks but takes
10 hours to unpack are not an acceptable solution.

* Release Size:
~~~~~~~~~~~~~~~

Allowed split volume sizes are:
– 1,444,000 bytes
– 2,888,000 bytes
– 5,000,000 bytes
– 10,000,000 bytes
– 50,000,000 bytes

The utils disk limit is as of now 70 x 5,000,000 bytes or 35 x 10,000,000 bytes.
This equates to a total of 350,000,000 bytes of compressed data. Oversize
releases are allowed when no ISO release exists and the group (or an iso group
they work with) is not in possession of the iso to release. In other words,
there is NO size limit for 0day apps, except when an iso exists!

The games disk limit is as of now 80 x 5,000,000 bytes or 40 x 10,000,000 bytes.
This equates to a total of 400,000,000 bytes of compressed data.

Any release should have less than 100 volumes. In case 10,000,000 bytes do not
suffice, you are allowed to use volumes of larger size; up to 50,000,000 bytes.

A size proper is valid when a group manages to reduce the size of the original
release by at least 30% without sacrificing essential content:

– Documentation, help files, and other non functional items can be ripped from
a release to decrease size. No functional parts of an application may be
ripped.
– C++ redistributables, .NET framework, and other common operating system
components may be ripped. The nfo should note what has been ripped and
optionally include an url where it can be downloaded.
– A documentation addon is only allowed if the documentation cannot be
downloaded freely and publicly (without registration) from the developer’s
website.

* Specific Release Type:
~~~~~~~~~~~~~~~~~~~~~~~~

All of these releases should provide functionality identical to that of a fully
licensed copy.

- Cracked: The program file has been altered to register the program. Any
nags/trial limitations should be removed. Any remnants of “Trial” in the app
need to be removed. Any “phone-home” checks should be disabled!

- Regged: Any way to make an application “registered” without requiring
modification of any of the applications executables/libraries. Must include
a text file with the required information, serials should not be put in the
release nfo. Please name this file carefully, as to deter possible
webspiders looking for serial information.

- Keygen: A small standalone program which generates valid serials/keyfiles
which are based on user input or hardware id.

Keygens can be written in any language but they should be native executables
for the OS the application is meant for: Linux keygens for Linux applications,
Mac keygens for Mac applications, etc. This means that if you do not follow
this suggestion, you could get propered. However, you won’t be nuked if there
is no native keygen available.

A keygen that generates a system-dependant serial must explicitly warn the
user of this fact, either in the nfo OR at runtime.

Windows keygens in java are allowed if the the program is coded in java or
uses java. Same with any other interpreter language. If a library is included
with the latest windows install, as is the case for VB6/.NET/VBScript
currently, then keygens written in these languages are allowed without
question. The motivation here is that a scene release should run on a clean
OS install, introducing no additional dependencies other than those imposed
by the application being released.

A console-based application that usually runs on headless systems (servers,
etc) requires a console-based keygen.

Generic Keygens (All.Products) are allowed and dupe full releases for as long
as the generic keygen continues to work for *every* application it was
intended for.

Keygen.Only releases are releases that only contain the actual keygen, no
installation files. They are meant as an addition to previous Crack/Regged
releases.

A Keygen.and.Patch release combines a keygen with a crack to enable full
functionality. You are still allowed to release a keygen.only for these
releases.

- Retail: A store-bought supply is included in this release. You are allowed to
release a retail after a previous release if there is an added benefit to
using the retail version. In this case you are required to add a READ.NFO tag
to your dirname and list the benefits when compared to the previous release.

- PROPER/WORKING: a proper of a previous scene-release that was not fully
working should always include adequate proof and information for nukers to
test and confirm the validity of the proper. This means including screenshots,
pieces of code, or clear steps to reproduce the problems that occur with
the release you are propering.

- READ.NFO: If you label a release READ.NFO, please have a clearly stated
section in your nfo on what the READ.NFO is all about, dont make people guess.
If you want people to read it for a certain reason, make sure they can.

* Operating Systems:
~~~~~~~~~~~~~~~~~~~~

If a developer has not mentioned default or minimum requirements for operating
system, the default is Windows XP, which is also a minimum.

If a program supports Windows Operating Systems before WinXP, then your crack
*should* work on them aswell.

Optional: combine multiple operating system versions for the same CPU in 1
release if it remains within size limits, for example:
- FreeBSD5,6,7 x86 can be in a single release tagged FreeBSD
If the installers are freely downloadable (available without registration) and
the same keygen/crack works for every version, consider only including the
latest version of the OS.

Please keep in mind that the contents of .tar.gz, .rpm, .deb and any other
packaging system are generally identical. Please make a note in your nfo in
case of exceptions.

* Minor Updates:
~~~~~~~~~~~~~~~~

MU stands for Minor Update. This term denotes an update of a previously
released application within a certain time-period, the MU-period. Major updates
are allowed regardless of the last time a previous version was released. In
this case, the nfo should include some motivation for considering this a major
update (security- and stability-critical hotfixes for instance)

MU-period of 1 month, disregarding the number of days in a month. Examples:

- a release on 2010-01-01 will be out of mu on 2010-02-01
- a release on 2010-01-15 will be out of mu on 2010-02-15
- a release on 2010-01-29 will be out of mu on 2010-02-28
- a release on 2010-01-31 will be out of mu on 2010-02-28
- a release on 2010-02-28 will be out of mu on 2010-03-28
- a release on 2010-03-31 will be out of mu on 2010-04-30

This ensures no more than a single release of the same application per month,
while keeping duping simple.

The minor update period is counted from the last valid release which contained
the software itself. In other words, keymaker.only releases are not considered.

* General Rules:
~~~~~~~~~~~~~~~~

- If the age of the last modified file of an installed program is older than
one (1) year it is not allowed to pre it without a READ.NFO or INTERNAL tag.

- A group should release the newest version of the software available.

Exceptions are possible when the software is not available publicly, or if
it was never released before, which *must* be mentioned in the nfo-file.
This means you can release an older version of an application, but *only* if
it is newer than any existing release of the same app, and you have a valid
reason for not releasing the latest version (for instance, it is very hard
to get the supply, or the application takes months to crack).

There is a grace-period of 3 days: if a new version came out in the last 3
days before your release, you will not get nuked if you release the older
one.

- Releases should provide the same functionality as a retail copy of the
application (where possible and reasonable). Examples:
– a virus scanner must be able to update
– a flexlm application should include every useful feature
– a keygen should provide either all, or the best license (watermarks are
still allowed)

- Your nfo should provide a minimum of useful information, including:
– (complete) application name
– (complete) version, including if it is a beta version
– the release date
– type of crack included
– short description of the application/game
– description on how to use the crack (important!)
– operating systems this release will work on
– pre-requisites for the application/game
– url to the application’s website

- If you do not want your work to be used by other groups (be it documents,
cracking methods, tools, or similar), then make sure you don’t give it out
to anyone you can’t trust. It is deemed public property as soon as it is
publicly available, and you lose any exclusive rights to it.

- Stealing cracks/keygens from P2P, WEB, or other scene groups is clearly not
allowed!

- Security should be everyone’s primary concern. Including nicknames or
identities of people that have not given explicit permission in your nfo’s
is absolutely not allowed, and may result in severe repercussions.

A big thanks to everyone involved in creating this document!

Last modified: 10 January 2010

——–======== October 3rd, 2009 ========——–

Introduction:

WMV is equal in quality to x264. Many people feel as if WMV-HD is redundant because of
the x264 scene. This simply is not true because of the compatibility of WMV-HD. It can be
played on the X360 and HTPC’s; x264 is restricted to HTPC’s. The only reason many people are
against WMV-HD is because it’s Microsoft. Fact is, many movie studios utilize the VC-1 codec
for their retail BD-ROMs.

SECTION I: Video

Video size is determined by Minimum Bitrates

101: Source must be HDDVD or Blu-Ray.
No re-encoding of any other source is allowed, i.e. x264!
102: 720p must have a minimum bitrate of 4000 kbps.
103: 1080p must have a minimum bitrate of 9000 kbps.
104: Resolution must be no less then 720p and NO GREATER then 1080
If source is 1088, it must be cropped to 1080 due to known 360 problem with 1088 resolution.
105: Custom resolution is allowed, either OAR or MOD 16 is acceptable.
106: Video codec MUST be Windows Media 9 Advanced Profile (VC-1).
107: All releases must be encoded with 2-pass VBR.
108: Intro and credits are to be kept intact; removing them is grounds for a proper.
109: Resolution dupe rules are as follows:
720p dupes 1080p
1080p does not dupe 720p
110: Intros and watermarks are NOT allowed.
111: Interlaced source video is NOT required to be deinterlaced.
112. There is NO MINIMUM and NO MAXIMUM filesize requirement for the final WMV file.
WMV-HD is now purely quality driven by minimum bitrate.

SECTION II: Audio

201: Audio must be a minimum of 640 kbps WMA3 Pro 5.1.
The only excpetion is if the source kbps is lower than 640 kbps
or the source contains only 2.0 or mono audio tracks.
202: Encoded audio channels must match source with correct channels mapped.
Upmixing is prohibited, the only excpetion is rule 203.
203: If there is only MONO on the source, upmixing to 2.0 is allowed.
204: Must be 24bit or 16bit audio unless source is less.
205: English audio is to be use if it’s the native language on the disc.
206: If English is not the native audio on the disc do A or B and always C:
A: Add hardcoded English subs and native audio.
B: Use dubbed English audio track.
C: Follow directory naming rule 408.
207: Audio can be either CBR or VBR and 1 Pass is sufficient.

SECTION III: Subtitles

301: Subtitles are NOT required if audio is English.
302: English subtitles are suggested for titles that contain non-English audio segments when
English is the primary audio language.

SECTION IV: Packaging

401: WMV must be in RAR.
402: Recovery record must be used when RARing.
403: SFV, NFO, and Sample are required for all releases.
404: Sample must be at least 60 seconds in duration.
405: NFO MUST state the following information:
VIDEO bitrate
AUDIO bitrate
VIDEO resolution
AUDIO language
If Subs are HARDCODED.
URL to movie.
406: RAR filesizes to be used:
50 mb  or 50,000,000 bytes
100 mb or 100,000,000 bytes
150 mb or 150,000,000 bytes
407: 2 X DVD5 is not allowed as DVD9 WMV can be split very easily by the end user.
408: If audio is not English, audio language MUST be specified in dir name.
409: Directory format suggestion:
Movie.Title.Year.<BluRay/HDDVD>.VC1.<720p/1080p>.<AUDIO CHANNELS>.WMV-GROUP

SECTION V: NUKES

501: These rules govern the WMV-HD section, NO OTHER RULES APPLY!
This means all nukes based on any other rules, implied or written, are INVALID NUKES and are
UNACCEPTABLE. All groups releasing WMV-HD have agreed to and signed this rule set. As such,
we are the only ones who will develop, implement, and mandate the rules governing the WMV-HD
section.
502: These rules do not apply to any release pre’d prior to this rule set. Any and all nukes are
INVALID if these rules are applied to releases that came out prior to this rule set.
503: If a group wants to redo a title that was done before the WMVS v4.0 rules were released, it must be
labeled INTERNAL.
504: Propers are valid if rule 405 is not strictly adhered to.
505: HDDVD and Blu-Ray sources dupe each other.
INTERNAL tag is required if one is already released.
506: Propers or nukes are NOT VALID if 302 is not followed as this is only a suggestions and NOT A RULE.
507: An EXACT timecode must be specified and screen shot of issue is required in order to nuke a
release for video “glitches” or other picture qualtiy problems. Without a the EXACT timecode and
screenshot, any nuke for picture quailty is INVALID.
508: An EXACT timecode is required to nuke a release for audio problems such as out-of-sync.
509: Nukes for any flaw in the release directory name are INVALID, no matter what it is or how bad.
This means if anything listed in the directory name is wrong, you still cannot nuke it.
i.e.: If the year is wrong, if there is a typo in the movie title, or anything else
not correct.. IT CANNOT BE NUKED.

——–========  The Windows Media Video Releasing Standards v4.0 for Blu-Ray and HDDVD ========——–
——–========                  Signed by IGUANA, NOVO, INSECTS, SMeG           ========——–

###########################################################################################

!p2p! [14:59:37] Dear P2P-Network users: recently some of our voluntary funding sources unfortunately went away. What this means is that we now have to pay approximately $300 a month to maintain all our servers. We kindly ask you to help us support these costs by donating whatever funds you have available via http://www.p2p-network.net/ or directly to donate@p2p-network.net via PayPal. Please be aware that this is purely voluntary.

!p2p! [14:59:43] Also, some of you may have noticed that we currently do not have any European-based servers, we are working on getting some running soon. If you have a European-based dedicated server that is capable of supporting an IRC server and which we can use, please join #routing and explain what you have to offer in detail, this would be a big help as well.

###########################################################################################

p2p was ~djgrrr@staff.p2p-network.net * djGrrr
p2p using citadel.us.p2p-network.net Sun Dec 20 14:00:56 2009

p2p was ~djgrrr@staff.p2p-network.net * djGrrr
p2p using citadel.us.p2p-network.net Sun Dec 20 13:57:43 2009

###########################################################################################

* Dns resolved area51.us.p2p-network.net to 66.252.30.123

network:IP-Network-Block:66.252.30.0 – 66.252.30.127 (123 is area51 of course)
network:Org-Name:Shellfx

ShellFX is Xzibition also goes under the company name OutCast, area51 has about 550 users average, a 500 user shell is 9.95 but lets say P2P-Network.net bought a 800 user ircd for 14.95. According to the owner of ShellFX/Xzibition/Outcast LazyKat, djGrrr has free ircds and shells on every server run by the company for helping out so true cost: $0.00

###########################################################################################

* Dns resolved moo.us.p2p-network.net to 69.30.232.148

69.30.232.148 resolves to moo2.jchost.net

so JCHost is a company owned by corNIC so technically moo.us is paid for because what kind of an oper donates a server and then
accepts donations to pay for the server he donated, so $0.00 goes to that.

###########################################################################################

* Dns resolved mars.ca.p2p-network.net to 204.16.200.180 aka the old tank.ca.p2p-network.net

Mars is a colo’d server owned by Spike who works for the datacenter wheres its hosted. So cost, well all its running is an ircd from the looks of it, and an overkill spec is 100Mbit w/ 1000 GB which is about $49.99 CAD/month. So thats the first total 49.99

###########################################################################################

* Dns resolved afk.us.p2p-network.net to 66.154.99.150

afk.us is also the server for the official QuadraNet.com website. Official Website Server = Paid for by QuadraNet, cost to P2P-Network
= $0.00

###########################################################################################

* Dns resolved juggernaut.us.p2p-network.net to 72.20.48.95

juggernaut = 72.20.48.95 and 72.20.48.95 is owned by Xzibition.com again, so cost $0.00 at most $14.95/month.

###########################################################################################

* Dns resolved citadel.us.p2p-network.net to 72.20.40.52

72.20.40.49 = P2P-Network.net official website
72.20.40.50 = LinuxHosted.ca LinuxHosted.net GenerationTrance.com
72.20.40.51 = proxy scanner for users connecting to the network
72.20.40.52 = citadel
72.20.40.53 = Originally used as server for running nginx proxy for SceneTorrents.org (SSL is even still active for this domain/ip)

So if GenerationTrance and LinuxHosted (the company used to funnel donations from SceneTorrents to private paypal accounts) doesnt pay for the server they are using ill be nice and let them rent a P4 for 109.00 USD.

###########################################################################################

* Dns resolved chaos.us.p2p-network.net to 66.252.11.9

network:IP-Network-Block:66.252.11.0 – 66.252.11.63
network:Org-Name:Shellfx

again most likely free as its owned by Xzibition.com, if not 14.95/month

###########################################################################################

* Dns resolved gige.us.p2p-network.net to 63.251.179.17

Surprisingly the only one i couldnt trace down.

############################################################################################

P2P-Network.net asked for: $300.00 USD/month

Potential Real Cost: $203.~~/month

Probable Real Cost: $109/month

Why the all of a sudden need for donations after four and a half years of not asking for donations? Thats right its pretty obvious, SceneTorrents had their own network, but djGrrr used money from SceneTorrents users that was meant for SceneTorrents on his other network P2P-Network.net.

Should you donate? probably not, the servers existing now are more than capable of handling several thousand more users without an issue, if anything they should drop a few and add more .EU as grass.nl (LeaseWeb/Nforce) and the netdirekt server was also paid for by SceneTorrents donations.

#############################################################################################

asxSAC

FAREWELL v1.0 (c) VRL
Retail

Supplier : ………………………………. TEAM ViRiLiTY
Cracker : ………………………………. TEAM ViRiLiTY
Packager : ………………………………. TEAM ViRiLiTY
Release Date : ………………………………. 26th Oct 2009
Disks : ………………………………… 01 x 2.88mb
Protection : …………………………………….. Serial
Requirements : …………………………….. Windows (32bit)
Language : ……………………………………. English

RELEASE NOTES

After more than seven years and over 8000 releases the time has
come, so that we are going to close the curtain now.

We would like to thank everyone who supported us in the last years
and especially those who have been loyal for years! Thank you for
the nice friendships and the fun we had with all of you.

A big sorry to the high quality software developers who have been
defeated by us. But you can relax now, because the real competition
is gone )

Its quite sad to see that 0DAYs today dir is getting more and more
empty. We hope the future will bring some new talents to make the
scene what it was a few years ago. Highlighy active, talented and
with a strong competition between the groups.

I would like to thank the group, active and former members, for the
nice time we had and the more fun we are going to have as being
part of the scenes history ViRiLiTY has always been a small but
very strong group, which made ViRiLiTY the way it was.

This is the the final release that has been dropped under the label
of ViRiLiTY. So please shut down any types of open positions that
are running under the name of ViRiLiTY. Otherwise we are going to
hunt you down and cut your penix off.

Good Bye
ViRiLiTY 2002-2009

INSTALL NOTES

GREETiNGS!

We dont greet. We get greeted.

NFO by asphyxSAC – Updated on 2007-06-14 by TEAM ViRiLiTY

IF YOU USE THIS SOFTWARE, BUY IT!