A quick way to find the actual mod that conflicts with one that wish to install

[aegersz]

in Linux anyway. Windows method may be possible if you read on.

this may not be the best place for this advice and it's very simple advice at that but it still may help someone ...

I must have too many mods on because i'm always running into patch or mod installation conflicts/errors so what i do is:

zgrep try_a_bit_of_the_code_that_failed_to_be_located /var/www/html/Packages/* (or wherever your compressed downloaded mods live).

a bit of trial and error may be involved.

[Shambles]

Can you explain what zgrep is and how to run it from Windows?

[aegersz]

sorry but I just changed the post as it's a Linux thing (in CentOS, anyway).

zgrep searches for character strings in compressed/zipped files.

this may help though:

http://www.fileseek.ca/Discussions/View/search-inside-zip-files/?ID=d54a533c-7bf0-4979-ae3c-5d0713108877

[Shambles]

I've no idea how to use Linux but thanks for the grep explanation anyway.

[aegersz]

neither did I until I built my forum.

you are welcome ... the link I posted tells you how to search for such strings in Windows using winrar.

[Gluz]

You want a way to search through the compressed MOD files searching for a bit of code into the files in those MODs?

I think that zgrep as you say is the way to go, in any SO, even in Windows, you only need to download WinGNU32, that contains a lot of the GNU utilities that are available in Linux/Unix like grep and zgrep.

[aegersz]

rough and ready but for zipped files change the grep string that you are looking for and try this as I have had some success with it searching through the Packages directory on CentOS:

Code Select Expand

for file in *.zip; do unzip -c "$file" | grep "ts=%4$d"; echo "---> last file read was $file"; done | less