Quote:
Originally Posted by niyghtell
Simple way to do this is...
[Only registered and activated users can see links. Click Here To Register...]
READ ONLY
when you do normal exit cabal will stuck, solution is to end task
I mean like this
[Only registered and activated users can see links. Click Here To Register...] |
Just wondering, has anyone tried this... And does it work?
Seems like a sure-fire way to block any new information from being added to the file, so all they should get is a bunch of old data from before you started using any cheats.
I think i can write a program that monitors the cabal_main.exe file, constantly.
When it detects that the process is no longer active, it can, immediately, perform the steps from Inssider's script, automatically:
Code:
@echo off
echo running......
CD D:\Games\CABAL Online (Europe)\GameGuard
ECHO Y | DEL *.erl
attrib -h -r -s /s /d D:\*.dat
CD D:\Games\CABAL Online (Europe)\Data\UserData
ECHO Y | DEL *.dat
del /f /s /q %systemdrive%\*.erl
del /f /s /q %systemdrive%\*.log
del /f /s /q %windir%\prefetch\*.pf
del /f /s /q "%userprofile%\Local Settings\Temporary Internet Files\*.*"
echo. & pause & press any key to exit!
exit
A built-in check can see if CABAL is installed into the default install location, in which case the user doesn't need to enter anything at all.
However, if it's NOT in the default location, the only thing a user would need to do, is enter the PATH location of the CABAL main folder, i.e.: "D:\Games\CABAL Online (Europe)".
Since the folders in the "CABAL Online (Europe)" folder won't change, there is no need for them to enter the rest, i can program that right into the application.
Also, they would have to enter the location, only at first start of the program, after that it will be stored in an "ini" file, for future startups.
I could, probably, also write in a "dlog.dat" file check, to see if it exists.
If so, delete the file, write an empty "dlog.dat" and make it "read-only".
That way, no information can be added to the "dlog.dat" and all that the GM's get, is an empty file. CABAL might "hang" while closing, but that can be solved with the "Windows Taskmanager". This should also prevent an "accidental" normal closure of the game.
Perhaps that would be an even better option, since it doesn't require any further steps to ensure that no information is sent to the GM's.
Unless the "dlog.dat" is just 1 of many built-in security/log checks of CABAL.
If anyone knows if "dlog.dat" is the only thing that needs to be blocked, or not... Please let me know.
Also, if a program, like i just described, is wanted... Let me know (send me a PM, or something), so i can start building it. I'm not going to do it if nobody gives a cr*p! ;)
Edit:
I could probably build in a "launcher" routine, which launches the "cabal_main.exe" file upon the start of my application. That way, the game starts automatically when my application is launched, monitor the "cabal_main.exe", perform the necessary actions (or edit the "dlog.dat" file, which i described above) when the "cabal _main.exe" is no longer active (or, in case of the "dlog.dat" file, perform them BEFORE it's terminated), give a popup message, informing you whether the actions have been succesful, or not... And finally close itself.
In simple words... 1 doubleclick on the application, should be enough to do everything! :)