thanks sir makim.. working in GCPH ^^,
I finished checking it but still it won't work,Quote:
There are some precautions that you have to check.
The obvious ones as vista and 7:
Run as administrator via right click (or shortcut)
Unblock downloaded file before using.
Avoid running from the root folder (C:\, D:\, etc.), and try running it from the other folders (For example, inside grand chase folder, but can be inside any other folder as well)
More general ones:
Make sure the hack exe file is not compressed.
Your account has administrator rights (applies to xp, vista and 7)
Never run inside zip file. Extract beforehand.
Add your stage folder to your antivirus real-time scan exception, or just a:bandit:dd kom file extension to the exception list.
Nevertheless, I'll do some approach to try and get rid of the message. If this approach doesn't work, it means there's something wrong on your side, such as not having enough rights.
That's really odd, it seems to mean that your GameGuard files are being dled somewhere else that is not in your installation folder. This hack doesn't have any commands to delete or even access a file in GameGuard folder.Quote:
I finished checking it but still it won't work,
also I just noticed that whenever I get that error, if I start my GC client without the hack it always updates the gameguard about 39 files,
thanks for being concerned sir,
Does it mean like I have a virus or something?Quote:
That's really odd, it seems to mean that your GameGuard files are being dled somewhere else that is not in your installation folder. This hack doesn't have any commands to delete or even access a file in GameGuard folder.
The gameguard didn't download the files again,Quote:
No, virus wouldn't delete inactive GameGuard files.
Try running GC without hack (not even using 'run without hack' button in the program, but double clicking grandchase.exe), turn it off at log-in screen, and try running GC without hack again and see if GameGuard still downloads.
@Musha
As I stated in previous posts, I uploaded a new version (1.03) which includes an approach to fix it. If you cant make that version work either, then I likely don't have a solution.
Btw, I want to give thanks to the mod for sticking this.