![]() |
|
#1
|
||||
|
![]() Quote:
| |||
#2
|
||||
|
![]() Quote:
2. It causes an overflow on third-party programs, when you D/C it flags you because it sends out bad packets that the server then collects from your client; since MQ2 can't function well when the dsetup.dll is running at x100000 as opposed to the normal x0200 of eqgame.exe it disconnects the moment your character hits the world and reads the very first packet. | |||
#3
|
||||
|
![]() Quote:
__________________
https://www.asgardguild.net Whoever wields this hammer, if he be worthy, shall possess the power of Thor! -Odin
https://www.twitch.tv/artaenc I stream other games on here also like Monster Hunter World Guild Leader of <Asgard> The home of the gods! Lightyear/Artah | |||
#4
|
||||
|
![]() Quote:
| |||
#5
|
||||
|
![]() Quote:
I guess there's a way to tell Comodo to allow this seemingly malicious file to continue unmolested?
__________________
Catterine - 60 Druidess
Kattarina - 60 Shaman Angellus - 60 Cleric Pickahippy - 52 Druid ******************* All priest, all the time. | |||
#6
|
|||
|
![]() yes tell comodo to ignore your EQ directory
| ||
#7
|
|||
|
![]() Whatever was happening that caused severe mouse lag while p99 was open seems to have stopped recently, perhaps with this latest patch.
Has anybody else who was formerly having these very very strange mouse lag issues noticed that the problem recently went away? I have noted that this mouse lag was exactly the same as the kind of lag that occurs when broadcasting my screen via OBS to twitch, which is unsettling to say the least, and unfortunately leads me to the following question: Can someone in a position of knowledge tell us definitively that p99 does not in any way allow remote observation of our displays or logging of our keystrokes, either inside or outside of the client? -your Tingrocer | ||
#8
|
|||
|
![]() Granted this is my own issue -- but I play on a system where I cannot remove McAfee. This never used to be a problem until the last patch. McAfee is calling DSETUP.DLL "Artemis!" threat.
Although -- since the patch came out a week ago, and McAfee is just now calling it one -- it's probably a McAfee update. Still though -- might be something for Devs to look into. I can't imagine there's only a few people with this issue.. probably going to be more widespread soon as all the other anti virus software gets their updates. ~phiren | ||
Last edited by phiren; 07-03-2014 at 05:06 PM..
Reason: additional info
|
#9
|
|||
|
![]() if u punch Artemis into google, you would see that McAfee actively scans for new threats, and when it finds them it calls them Artemis (the name of McAfee's system that is searching your PC for these threats).
That's why it's called Artemis, because it doesn't know what virus it is, it just thinks it might be a virus. Also, it looks like the P99 developers can put in a request with McAfee to have the file white-listed: https://secure.mcafee.com/apps/mcafe...aspx?region=us | ||
#10
|
|||
|
![]() MQ2 reads 0x02 as that is what the client normally pushes, since p99 puts out 0x10 MQ2 cannot handle it and disconnects, thus the flagging occurs.
| ||
![]() |
|
|