Page 1 of 1
SRO nguard error
Posted: Sat Mar 25, 2006 11:38 am
by ajb
Sigh !!! Hope they fix this soon
How long has this error been going on now?
Any ideas on how to update nguard?
I even went to INCA site no place to upgrade nguard
Posted: Sat Mar 25, 2006 11:41 am
by Demarthl
moved to technical help
can you describe the error, perhaps get a screenshot, and give us your system specs
would help greatly
npgl.Check() !=NPGAGAMEON.SUCCESS
Posted: Sat Mar 25, 2006 4:06 pm
by hyionno
As our mate haven't describe the game guard error, I must describe it for you in order to make you informed cause there are many other with same problem and this might be helpfull.
Wen the message "npgl.Check() !=NPGAGAMEON.SUCCESS" appears it instantly knocks down the game. I took a screen of my pc error:
I dont know if you guys have solutions for that of if we will have to report to silkroadonline GM...
Thank you for your attention
Andréa Hyionno >> Mizune (TROY)
Posted: Wed Mar 29, 2006 12:34 pm
by plkmplkm
i have had the exact same error, then that stopped and it says my gameguard is experiencing problems and to email the *.erl files to
game@inca.co.kr i cant get on silkroad at all!!!!!
Posted: Wed Mar 29, 2006 2:32 pm
by Ecanem
Posted: Thu Mar 30, 2006 2:03 am
by iluviya
Guys, I got a solution for you, I personally encountered that problem last night, here's how I fixed it.
This is for winxp
goto control panel selecet firewall, go to exceptions, and add silkroad as allowed programs. This in turn will let your gameguard for silkroad update and problm solved.
HTH
About firewall
Posted: Fri Mar 31, 2006 7:22 am
by hyionno
Sorry to tell you but it's not a firewall problem though... I made that, I totaly turned off the firewal, worked for the overtime but then... it just appeared again with actualy NO firewall!!! Sorry for taking off the shot pic from the last message but I couldnt keep the link up...
Anyways I sent a message to game guard Web master and they suddently three days after the message I sent contacted with SRO and they tryed to fix, anyways I still dont know if it worked off... My new comp is not even starting SRO. As said in my last topic here...