Strange error that prevent files to munge correctly [Solved]

[Indytotof]

Hello modders and mappers, here is Indytotof !

I've recently come accross a strange and unknow problem that prevent my files to munge correctly. Here is the error:

Code: Select all

'levelpack' is not recognized as an internal or external command,
operable program or batch file.
'levelpack' is not recognized as an internal or external command,
operable program or batch file.
'levelpack' is not recognized as an internal or external command,
operable program or batch file.
'levelpack' is not recognized as an internal or external command,
operable program or batch file.
'terrainmunge' is not recognized as an internal or external command,
operable program or batch file.
'worldmunge' is not recognized as an internal or external command,
operable program or batch file.
'worldmunge' is not recognized as an internal or external command,
operable program or batch file.
'pathplanningmunge' is not recognized as an internal or external command,
operable program or batch file.
'terrainmunge' is not recognized as an internal or external command,
operable program or batch file.
'worldmunge' is not recognized as an internal or external command,
operable program or batch file.
'worldmunge' is not recognized as an internal or external command,
operable program or batch file.
'pathplanningmunge' is not recognized as an internal or external command,
operable program or batch file.
'levelpack' is not recognized as an internal or external command,
operable program or batch file.
'levelpack' is not recognized as an internal or external command,
operable program or batch file.
'levelpack' is not recognized as an internal or external command,
operable program or batch file.
'levelpack' is not recognized as an internal or external command,
operable program or batch file.
'levelpack' is not recognized as an internal or external command,
operable program or batch file.

Just... what that means and why it happen (yes, the cause of this is totaly unknow to me).

Thanks, you're awesome guys !

[AceMastermind]

This could indicate a problem with your path environment variable, check and fix it if needed. Did you install any new software recently?

Similar problems:
search.php?keywords=%27levelpack%27+is+ ... mit=Search

^Suggestion by Zerted that resulted in a normal munge output:

Backup your mod map, uninstall the mod tools, then reinstall them in a better place. Copy your map back in. Do a full/manual clean and munge again (make sure to check Common only)

[Indytotof]

This could indicate a problem with your path environment variable, check and fix it if needed. Did you install any new software recently?

Apart TFU 2, 3D Ripper DX, Daemon's Tool lite and the last version of Sketchup... no I don't.

Where can I find the path environment variable ?

Is it can be linked that I don't have BF2 DVD inserted in the CD/DVD reader ?

[Anakin]

I just know the german words, so here is a pic. you need to browse the system settings and find system. klick on advanced settings.:

Hidden/Spoiler:

and then klick on "umgebungsvariablen" in this pic. (ignore the red arrow)

Hidden/Spoiler:

in the second list find PATH

Hidden/Spoiler:

klick on edit and the best way is to copy it in an new txt file.

or you simply open an cmd and type "echo %path%".

But i don'T know what you should find in there. for me there is nothing about SWBF Modtools

[Indytotof]

Similar problems:
search.php?keywords=%27levelpack%27+is+ ... mit=Search

^Suggestion by Zerted that resulted in a normal munge output:

Backup your mod map, uninstall the mod tools, then reinstall them in a better place. Copy your map back in. Do a full/manual clean and munge again (make sure to check Common only)

Not working for me.

I will see if TFU 2 is the problem, but first, I've to extract Juno Eclipse model from the game.

I just know the german words, so here is a pic. you need to browse the system settings and find system. klick on advanced settings.:

Hidden/Spoiler:

and then klick on "umgebungsvariablen" in this pic. (ignore the red arrow)

Hidden/Spoiler:

in the second list find PATH

Hidden/Spoiler:

klick on edit and the best way is to copy it in an new txt file.

or you simply open an cmd and type "echo %path%".

But i don'T know what you should find in there. for me there is nothing about SWBF Modtools

This giving nothing to me too....

TFU 2 seems to be the problem I think.... I will try after ripping of Juno Eclipse model from it and I will see...

EDIT : No, TFU 2 wasn't the cause of all this...

And I've come accross theses when trying re-install:

Code: Select all

The following error has occured on the file 'C:\BF2_ModTools\ToolsFL\bin\BinMunge.exe' The system cannot find the file specified (0x2)

All sort of the same kind of error, but with other files the system can't find...

Any though ?

[AceMastermind]

What did your path environment variable look like? Post it.
If anything, i'd say Daemon Tools lite corrupted it.
I don't know about other operating systems, but here's what it looks like on a fresh install of XP:

Code: Select all

%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem

those are at the beginning.


EDIT
Moving this thread to Technical Advice and Tutorials

[Anakin]

It doesn't matter at what position the entries are. On windows 7 or 8 it will look defently different.

Are there some files in the ToolsFL\bin folder?? If not that's the problem. If there are all files in there and Ace's about the enviroment variables is right try to add
"C:\BF2_ModTools\ToolsFL\bin;" at the beginning(!) of the path variable. Best would be to restart the system after you did that and try again to munge.

To post the path variable here you can use this in cmd
echo %path% > path.txt
It will write the entries in the txt file. That will be located at the position you are at the moment. Best would be to browse to your user folder.

[Indytotof]

To post the path variable here you can use this in cmd
echo %path% > path.txt
It will write the entries in the txt file.

Gave me nothing....

I've uninstalled Daemon's Tool Lite before TFU 2 and nothing had change.

And I've abord Mod Tools' installation.

EDIT : It's seems that avast messed up with again for some of the errors, exept for BinMunge and SpriteMunge.exe things...

[AceMastermind]

Simply uninstalling software will not fix a corrupt path environment variable, you must inspect it and fix it manually.

EDIT : It's seems that avast messed up with again for some of the errors, exept for BinMunge and SpriteMunge.exe things...

I don't know what this means, can you rephrase this or just post in your native language and we'll translate it?

Have you checked to see if the exe files are actually in your BF2_ModTools\ToolsFL\bin folder?
Has Avast updated recently? Do you think Avast quarantined them as false positives?
Have you tried munging with Avast temporarily disabled?

I don't know what else to tell you, I have no other suggestions based on the information you provided.

[Indytotof]

"Il semblerai qu'Avast ai encore prit certains logiciels du Mod Tool comme des faux positifs".

For the first question: No, I haven't I'll do that immediatly
For the second question: Apparently, yes.
For the third: No. I will try it.

Sorry to be not able to give to you more information, I just don't know myself what's going on and so, I cannot give as many infos as I want.

EDIT : Yes, all the .exe files actually are on my BF2_ModTools\ToolsFL\bin folder.

EDIT 2: It was avast the problem. It munge perfectly when disable temporaly.

Here is my Munge log:

Code: Select all

'terrainmunge' is not recognized as an internal or external command,
operable program or batch file.
'worldmunge' is not recognized as an internal or external command,
operable program or batch file.
'worldmunge' is not recognized as an internal or external command,
operable program or batch file.
'terrainmunge' is not recognized as an internal or external command,
operable program or batch file.
'worldmunge' is not recognized as an internal or external command,
operable program or batch file.
'worldmunge' is not recognized as an internal or external command,
operable program or batch file.

I will try re-install the Mod Tool without avast activated to see if something change.

Avast must have updated himself automatically....

[Anakin]

Contact avast and tell them from your problem. When i had problems with gdata they always could help me with an personal update

[Havoc 526]

Has this been solved? I was having the same issue recently, I'm wondering if Avast was the problem.

[AceMastermind]

Folks should be marking their own threads when solved, but i'm going to mark this as [Solved] based on this:

It was avast the problem. It munge perfectly when disable temporaly.

Solution: Temporarily disable your AntiVirus if you encounter similar *.exe errors when munging.
Adding trustworthy executables to the exclusion list should prevent you having to disable your AV.

[Indytotof]

@Havoc 526
For the most parts, yes it is. I've just some tests to do before this be completly resolved. Yes avast is the problem.

@AceMastermind
I simply not marking it "Solved" because I wanted to do a simple test before. So no, it isn't yet solved but it is close to be.

And no, this solution doesn't work (and it's quite odd) because avast (without telling me) see those .exe files as false positive and go to quarantine...

After reinstall the mod Tool without avast activated (to see if I get some trouble), if the installation goes correctly, this thread can be marked as solved. Not before.

[AceMastermind]

Right, but you know the cause of the problem is your AV of which there is really only 2 ways to fix it. Get a better AV program or add the modtools to the exclusion list. It only takes a few minutes to reinstall the modtools with your AV disabled to conclude your test.

EDIT
Most AV programs allow you to restore quarantined files, did you try this before reinstalling?

[Indytotof]

Yes but I had to "réviser pour les partiels" (english isn't my natural language, sorry) first. This test is now done. Installation done perfectly without avast activated.

This thread can now be marked [Solved] !