arithon290 posted:
Oh i figured out what was wrong...
For some reason... the game.laa.dll was 1.109, but the game.dll was 1.110, and mojo wasn't updating game.laa.dll?...
I just had to delete game.laa.dll and mojo created a new one which was up to date... (guessing it's a copy of game.dll which gets the 2gb flag changed.
Oh i figured out what was wrong...
For some reason... the game.laa.dll was 1.109, but the game.dll was 1.110, and mojo wasn't updating game.laa.dll?...
I just had to delete game.laa.dll and mojo created a new one which was up to date... (guessing it's a copy of game.dll which gets the 2gb flag changed.
Excellent diagnosis! This is why I asked in the other thread if you had checked "large address aware." Like I said over there, this is the only possible reason I could imagine for what you reported, and now you've confirmed it. You may be the first person who tested Mojo's "large address aware" code during a patch.
arithon290 posted:
Dunno if it's some dodgey win7 permission problem stopping mojo from overwriting the existing game.laa.dll or something but yeah sorted now.
Dunno if it's some dodgey win7 permission problem stopping mojo from overwriting the existing game.laa.dll or something but yeah sorted now.
It's a bug in Mojo, even if you're right. Mojo runs with administrator privileges, so no matter what the operating system does with permissions, Mojo can and should keep its "laa" copy of game.dll updated. Permissions should be my problem, not the user's. But actually I doubt this bug has anything to do with permissions. I probably just made a mistake when I wrote the code that looks to see if game.dll is newer than the "laa" copy.
Thanks for letting me know. I'll fix it soon.
-----signature-----
Author of Mojo
www.mojoware.org
www.gaheris.net
www.daoc-trophy-mobs.com
Former PvE server team lead (2005)
www.mojoware.org
www.gaheris.net
www.daoc-trophy-mobs.com
Former PvE server team lead (2005)



Coreline 9l1 Ranger & Corlina 11l1 NS
Currently ~ Corella ~ 3l3 Bard