[XAD]

Originally Posted by CroniK )I make this error with / to show what the server tell went it start....

CroniK, I have hardly seen so many responses totally of from the question...

I have had the same problem and it's within Metamod's code. As far as I know (but I could be wrong as I only spend little time in the source code)you can't do what you want to do as it expects the file to be called metamod_i386.so, metamod.so, and some more variants but no other metamod_iNNN.so (unless you change the source code).

To fix this, the only solution I came up with, is either to rename the metamod_i686.so to metamod_i386.so (I know it's pretty stupid but heyI didn't code it ) or to rename the original file to metamod_i386_orig.so and then make a softlink metamod_i386.so to whatever metamod module you want.

/X

[DopeFish]

Originally Posted by CroniK /cstrike//addons/metamod/dlls/metamod_i386.so witch , I know, is not valid.

// is perfectly valid, just not common or clean, but it works just fine. it's the same as having e.g. a /./ in the path.

Originally Posted by CroniK What is "simlink"

symlinks ar symbolic links (linux command is "ln -s"), do a "man ln" for more info.

[CroniK]

thx XAD, that is what I was expected

So I rename 686 with 386 ans it works.

Thx Dope, for the infos

[MagicShot]

Originally Posted by CroniK thx XAD, that is what I was expected So I rename 686 with 386 ans it works. Thx Dope, for the infos

Hmm thats strange.. I wonder why it works that way and not the other?

[CroniK]

I get the same problem on amxx1.5 using i686 binaries.
amxx....i686 load well but I have to rename my metamod to i386 and load it in my liblist.gam....

So it is not a problem if it works, but really strange...

[XAD]

Originally Posted by CroniK So it is not a problem if it works, but really strange...

Not really, as I said, check the source code of MetaMod for the detailed reason...

/X