VisualMunge Copying Problem: Path Vars and "xcopy" [Solved]

[CressAlbane]

I've got a strange bug with Visual Munge. Even though the program was working superbly a few months ago (and I've got maps to prove it), recently a strange problem has occured. When munging COMMON, SIDES, or (I assume, I've only tested COMMON and SIDES) any of the other check-able boxes, I get an odd error message in the Munge output box. Note that this is not an error log, just something in the munging. (for example where it writes Copying files from MUNGED...)
Here is the error message:

Code: Select all

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

The results I've seen of this are that the localized files do not appear in game. I see no proper localization where it was before. (sadly my only backup was, unaware, saved with this problem.)The sides and files called are all stock game files. This map has no custom sides so I haven't been able to assess the effects of the SIDES error.

Here's the question: How can I fix this? I tried changing "xcopy" to "copy" in the munge.bat for COMMON, but that wasn't a valid command. Is this a Windows Update problem? I'm assuming that it is because it only occured recently. If you could help me out, I would be very appreciative!

EDIT: Forgot to try Search, and I found this topic:
forums/viewtopic.php?f=27&t=20993&hilit ... al+command
The problem here is exactly what I have! I read something about PATH variables. What are those?
EDIT2: Read the topic again, more closely. I downloaded fixpath2, but I ran it and VisualMunge still seems to have a problem. Biohazard wasn't very specific on what worked...

[AceMastermind]

Did you install any new software recently?
What operating system do you use?
You may need to reboot after fixing the PATH environment variable.
Did you check your PATH environment variable to verify that is was fixed?

The default PATH environment variable for a fresh install of XP looks like this:

Code: Select all

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

other installed programs usually come after. I think this is the same for Vista and Windows 7 but I don't know for sure since I use XP.

EDIT:
This should help explain it a bit better:
http://www.annoyances.org/exec/forum/winxp/1111086907

I'll copy the important parts to this post in case that web page disappears:

Hidden/Spoiler:

It's probably the PATH environment variable. Open a command prompt and type "path" (no quotes). You will see PATH= followed by a list of directories separated with semicolons. Is c:\windows\system32 there?

If not, go to Control Panel -> System -> Advanced -> Environment variables. Scroll the 'system variables' to find PATH, select it and click Edit. Copy its contents to a notepad window, it's much harder to edit a very long string in that little box.

When windows is first installed that variable is:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem

Put these at the beginning. Delete from anywhere else. Copy back to the little box, click OK twice. You will need to restart running applications to apply the new path to them, not the system.

[CressAlbane]

I'll try this out ASAP; I'm not at the computer at the moment. I recently added a PATH variable for java. Could that be what caused this?

EDIT: Yahoo! You were correct - I did have a problem with the Path variable. This was messing up some other functions of my computer, and without your example, I don't think I would have been able to fix it. The problem was that the path variable for java somehow merged with the default one.

[THEWULFMAN]

lol, Acemastermind is never wrong, seriously, go through his posts, I defy you to find one that didnt sound well educated.