OK, so I was trying to make my own version of Kamino, but when I try to build the level, ModTools doesn't want to actually munge or copy anything into the addon folder. What could be wrong?

Edit: OK, so I was looking at a couple of things around the board, and it brought up a question for me: Do I have to manually munge the separate parts of the level in order for "VisualMunge" to do its thing?

Did you check Common when you munged?

As for question #2, no you don't.

Well, yeah, I checked everything. And, just now, I tried to make a second one and it still didn't do anything.

Edit: OK, so, completely truthfully, I'm trying to make a copy of the shipped Kamino, and I'm trying to follow the directions from the tut linked to in the "everything you need" post, but I did everything it said and I get this problem. Just for some background.

What happens when you try to munge, exactly?

OK, so I go to the BUILD folder and open the ModTools there. When it's open, I choose EVERYTHING in sides, and I check every option. When I click Clean, I get a whole list of Call paths, half of which get the "system cannot find specified path" error. Then, when I click Munge (and this happenes whether I clean first or not), I get this listing: When I go to the Addon folder in the BF2 directory, nothing is in the data folder, and the only file in the entire Addon directory is the addme script.
And I don't get how or where it copying the "mission.lvl" and "core.lvl" because it's not munging those files, and there aren't any files in the ModTools directory for it to copy.

What folder are your mod tools saved in?

The path for the ModTools is C:\BF2_ModTools.

are you munging from the data folder or the data_abc folder?

Besides the fact that you can't munge from the data folder, I am in fact munging from the data_abc folder.

PS I just did a fresh install of ModTools, didn't add any of the custom sides released in the Conversion pack forum, and did a straight creation-munge process, and still nothing ended up in the ADDON folder for ABC, except the addme.script.

Weird.
Is there a process running called x86, or an .exe that looks like that in C:\BF2_ModTools\ToolsFL\bin . That could be an exception 86 coming from one of those exes (Sub Programs that visual munge calls to munge certain things).

Wait...x86, like 486, 386. Maybe your command prompt, or DOS-y thing, is running in some sort of compatibly mode. Or just not the right mode and the programmers assume that x86 was the only wrong mode.

Basically, what OS are you running?

So you think the fact that I'm doing this in Vista is the problem? Great, now I have to try to figure out a way to get on my Mom's new computer after it's set up on Christmas...

One note, you never need to select anything under the sides box, unless you have custom sides.

That wouldn't cause this, but still.

Well, I am wanting to put in one of the other legions, whichever has the "Boss" or "Fixer", so eventually, I will need that. I'll probably need help with that, too, because I can't seem to find those in the legion sides that Teancum released...

Do you have the modtools intstalled int the Program Files(x86) directory? They need to be in a directory path with no spaces.

Try running the munger in XP compatibility mode, although I'm not sure if that will effect the munge tools themselves. You'll probably have to go through the Tools folder and set all of them to run in compatibility mode, but I don't think that will be necessary.

@Ace- Vista differentiates install paths between 32-bit(Run on the x86 processor family) and 64-bit executables.

Well, I don't have the 64-bit Vista. I have 32-bit. And, like I mentioned in an earlier post, it's in my HD's root directory (C:), so that's not the problem. And I've been running it in compatibility mode from the beginning, and since my last reinstall, I wasn't running it in compatibility mode, so either way, it doesn't work. However, we got my Mom's computer today, so sometime I'm gonna be able to sneak on there and find out if it'll work on there. And if not, I'll know it's something wrong with the modtools I downloaded (I hope that's not the case, because I don't know of any place to download it other than SWBFfiles...)

Ah, you have Vista. Some people seem to be able to get it to work on Vista, but I can't do it on my Vista machine. I don't get that error, but... In any case--I'm thinking it's Vista's problem.

Indeed, I just confirmed it by installing it on my new XP (so glad we didn't do Vista on that one )
So yeah, for me, ModTools won't work on Vista.
Someone can probably close this topic now, if they want.