Release Gray Hackerz Team HackPack 6.1

[Unkindness]

Lol i dont play runescape just cause it was boreing but know i see this shit ill play =)

[ZonChau]

Thanks again orik hey you quoted my thanks from the other release going test this out now :D

[blackrock]

For the error thing, iv'ed searched google for it but i cant seem to find what im lookin for.. in fact i have no clue what im looking for!

I try not to leech, I scanned the file useing live onecare and it detected nothing harmful.

It would be helpful if someone could post a link for me to the site w.e cause again no clue what im lookin for 0_o

[divine_vengeance]

ok this hack pack seems finr. Its working grat for me.

[pimpjon]

please help i keep gettin an error

Run-time error 339

Component "MCIWNDX.ocx" or on of its dependencies not correctly registered: a file is missing or invalid

i used alll of ur links, i extracted using winrar, what else is needed?

[oriks]

Originally Posted by pimpjon

please help i keep gettin an error

Run-time error 339

Component "MCIWNDX.ocx" or on of its dependencies not correctly registered: a file is missing or invalid

i used alll of ur links, i extracted using winrar, what else is needed?

Listen theres a guide stickyed so people that can't figure this stuff out can follow the guide and then make it work, If you can't figure it out you might as well wait for my next release witch i will make with a Vista since that's what my new computer will be...Once it comes out it should work...Sorry for the wait the estimated time can be from 2-6 weeks. I'm very busy with almost no help and the next pack will be big and only have bots that work and work good, I hope this helps and I will post the new release on this site and the GHT site the day i finish it.

Your friendly over worked hacker,
Oriks

[fairtrade]

well it most certainly is clean Thanks

Originally Posted by oriks

Listen theres a guide stickyed so people that can't figure this stuff out can follow the guide and then make it work, If you can't figure it out you might as well wait for my next release witch i will make with a Vista since that's what my new computer will be...Once it comes out it should work...Sorry for the wait the estimated time can be from 2-6 weeks. I'm very busy with almost no help and the next pack will be big and only have bots that work and work good, I hope this helps and I will post the new release on this site and the GHT site the day i finish it.

Your friendly over worked hacker,
Oriks

and maybe if you search on google u can find the missing component :) thank me if it helped

[flameguardian]

this bots amazing thx oriks =]

[Cruzle]

bot is amazing with couple trojans inside.. Dont worry guys just dont make him piss off and maybe he dont steal your acc lol? 8DD
Malware name: Win32:Stealer-J [Trj]
Malware type: Trojan Horse
VPS version: 080708-0, 08.07.2008

[oriks]

Originally Posted by Cruzle

bot is amazing with couple trojans inside.. Dont worry guys just dont make him piss off and maybe he dont steal your acc lol? 8DD
Malware name: Win32:Stealer-J [Trj]
Malware type: Trojan Horse
VPS version: 080708-0, 08.07.2008

hey idiot i already explained this but since your such a retard let me help you out a bit....Copy and pasted from the autoit v3 forums...

If you have been using AutoIt for any length of time you will know that it is a great, and powerful scripting language. As with all powerful languages there comes a downside. Virus creation by those that are malicious.

AutoIt has no virii installed on your system, and if a script you have created has been marked as a virus, (and you're not malicious) then this is a [Only registered and activated users can see links. ]. They found a set of instructions in an AutoIt EXE out there somewhere, took the general signature of the file, and now all AutoIt EXE's are marked (or most of them). This can be due to several reasons.

1. AutoIt is packed with UPX. UPX is an open source software compression packer. It is used with many virii (to make them smaller).
2. Malicious scripter got the AutoIt script engine recognized as a virus.

And I am sure there are more ways your executable could be marked, but that covers the basics.

Now I am sure you are wanting to know what you can do to get back up and running without being recognized as a virus. You have to send in a report to the offending AV company alerting them to the false positive they have made. It never hurts to send in your source code along with a compiled exe, to help them realize their mistake.

You may have to wait up to 24 hours for them to release an update. The time it takes really depends on the offending AV company.