JoeK's Project Central

Quote:

Originally Posted by cyberside0 turn off and restart co2m8 and it should work.

have tried that over and over again .... well im posting a screenie .... i rly want to make this work ^^ so a help would be great :o

Quote:

Originally Posted by TopOne have tried that over and over again .... well im posting a screenie .... i rly want to make this work ^^ so a help would be great :o

On the L screen is memory Table set to v5022.r9-DMAd and is DMS Defeats ticked?
If so show me the screenie of the L screen.

1. hit the S-button to enter mem config menu (memory)
2. check "Use DMA defeats"
3. hit "Update to table"
4. OK+OK
5. close the mem config menu and enter the char config menu again (s-button)

tried it, it works :D

Yep gta's method works for forcing individual memory tables to a client,
the settings I outlined for L menu are the default setting for all detected clients.

Be aware that a popup occurrences shortly before patching each client,
it needs to be confirmed in order for the DMA patching to happen,

Note: In some situations this popup gets hidden behind other screens,
use the alt+tab keys to locate it.

Quote:

Originally Posted by joek I had a look at the code and it looks ok, the problem may be rubbish data in the HP values, I've seen that in the past but the current location seemed stable on my tests, it could also be other tools you may be using(eg SV) What you can do is view the HP amount in the co2m8 memory screen and keep pushing the refresh button checking to see if you get a value thats not your real HP.

well, i did as you said, and it turns out, that i actually AM getting wrong HP values. im not using SV, or any other programs should interfere (bots are the only other things i use). so is there a way to repair CO2m8 so i dont get incorrect HP values?

Did you check, that you use the corresponding mem-table to your client? :confused:

Quote:

Originally Posted by TopOne uhmm i cant check the mp/hp opt its grey ... not white like the others .. so what should i do ?

When you start a client, there's a little window that pop ups and asks if you want to DMA patch the client ... did you see this and click ok?

The problem could also be that the co2m8 SC buttons for starting clients have memory table version overrides available when you right click on the SC button, set to default so it uses the main memory table set in the L menu.

If you had the wrong table though nothing would be working, e.g the name of your logged in character would not even be right.

Lastly the issue could be your not using the english client, not every memory location is the same in the non-english clients.

Quote:

Originally Posted by joek Correct me if I'm wrong, but I think your saying that nod32 the virus scanner found a threat in the 1.44 update? The co2m8 exe is now packed and encrypted so some scanners may get false positives. Both AVG and viruschief give it a clean bill of health, if anyone wants to scan it and post the results here then please do so. @everyone, thank you all for your kind words and encouragements :)

yes that's what i mean but after i unpatch the file it was clean no viruse detacted by NOD32

WEB SITE = [Only registered and activated users can see links. Click Here To Register...]

Antivirus Version Last Update Result
AhnLab-V3 2008.5.3.0 2008.05.02 -
AntiVir 7.8.0.11 2008.05.05 -
Authentium 4.93.8 2008.05.05 -
Avast 4.8.1169.0 2008.05.04 -
AVG 7.5.0.516 2008.05.05 -
BitDefender 7.2 2008.05.05 -
CAT-QuickHeal 9.50 2008.05.05 Win32.Backdoor.IRCBot.cgu.4
ClamAV 0.92.1 2008.05.05 PUA.Packed.Themida
DrWeb 4.44.0.09170 2008.05.05 -
eSafe 7.0.15.0 2008.04.28 -
eTrust-Vet 31.3.5760 2008.05.05 -
Ewido 4.0 2008.05.05 -
F-Prot 4.4.2.54 2008.05.04 -
F-Secure 6.70.13260.0 2008.05.05 -
Fortinet 3.14.0.0 2008.05.05 -
Ikarus T3.1.1.26 2008.05.05 BehavesLikeWin32.ExplorerHijack
Kaspersky 7.0.0.125 2008.05.05 -
McAfee 5288 2008.05.05 -
Microsoft 1.3408 2008.04.22 -
NOD32v2 3076 2008.05.05 -
Norman 5.80.02 2008.05.02 -
Panda 9.0.0.4 2008.05.05 -
Prevx1 V2 2008.05.05 Malicious Software
Rising 20.43.01.00 2008.05.05 -
Sophos 4.29.0 2008.05.05 Sus/ComPack
Sunbelt 3.0.1097.0 2008.05.03 -
Symantec 10 2008.05.05 -
TheHacker 6.2.92.300 2008.05.03 -
VBA32 3.12.6.5 2008.05.05 -
VirusBuster 4.3.26:9 2008.05.05 Packed/Themida
Webwasher-Gateway 6.6.2 2008.05.05 -

Ty alan77 :eek:
that scan is always very critical and perhaps just a touch over enthusiastic(but thats all good too in some cases).

Yes as already stated code packaging and protection will show some discrepancies with some scanners.

The new co2m8 package(1.44) is packed using some aspects of the Themida style protection system.

I had no choice as some individuals were re-releasing m8 on other sites after doing all sorts of things to it.
Sorry guys I will not have my code and my reputation clouded in that way and
so certain measures had to be taken to protect both myself and the m8 users.

It fully passes the boards recommended scanner and the moderators don't have a problem with it so I'm not gonna change it.

allan77... look, if ya dont trust him dont use his software. it is that simple.

as for me, rock on joek! i know its clean :D

its not about trust, just being careful. Appreciate all his contributions for the program of CO2m8, i've been a loyal users of all the previous versions. But in this case, its too risky. i've give up using, Its up to individual.

Quote:

Originally Posted by alan77 its not about trust, just being careful. Appreciate all his contributions for the program of CO2m8, i've been a loyal users of all the previous versions. But in this case, its too risky. i've give up using, Its up to individual.

It only failed 4 out of the 41 scanners it was tested on,
so thats clearly a problem with the scanner not the program.
But as you say its the individuals choice to run or not to run.

On top of what joek said, I'd also add that usually any XP user has a firewall which alerts when an application attempts to create an outward/inward socket (even the XP builtin firewall does that), so in case you really decide to be cautious, since the firewall does not alert of open sockets from the app, I'd say it's not calling home ;)