Yeah, that's exactly what I thought would happen...
"it wouldn't surprise me if some people might have trouble from running a batch file" because they tried to run it from a GUI and don't know how to interact with command line programs well.
I thought to myself that there would probably be somebody that would just download the *.BAT file and not know what they're doing, and double-click the batch file hoping that it would magically work. The batch file, which has a lot of copy commands, would try to copy a file that doesn't exist, because the person running the batch file didn't read the batch file. In this case, the batch file gives instructions on what file to download and rename so the batch file would work, but on many Windows systems, Windows is set up to just close a command prompt session as soon as it is over, so the user won't see the instructions given by the batch file. So, since the person isn't following the instructions, they assume the batch file doesn't work. Not that I blame the person: Windows very well might be configured so that the directions aren't easy to see.
If the DOS session ends extremely quick, that is most likely because the batch file's copy commands are all completed unsuccessfully rather instantly, and the reason the copy commands fail so quickly is because the file to be copied doesn't exist, because whoever ran the batch file didn't put the to-be-copied file where it needs to go. (Some subdirectories (a.k.a. "folders") should have been created under where the batch file was run, unless they pre-existed.)
The solutions are: A) End user learns how to use a command prompt well. B) Installation is made more user friendly. C) End user tries to open the batch file in Notepad, and reads the directions at the top, and tries successfully to follow them.
The best long term solution for helping the most users would be option B), and I thought that somebody out there might want to convert the graphics to affect the "base models" (instead of altering the versions wearing underwear) and then release a package that is easier to install Although I figured some people unfamiliar with the command line would have troubles, I decided to post my "unfriendly" batch file anyway so that those who can benefit from it can start doing so.
Now if somebody tells me that the copy commands failed using CMD.EXE due to spaces in the filenames or something like that, I might look at fixing it. I don't want to invest a lot of effort in trying to test this batch file on lots of systems (like trying to find access to a Windows XP system with WoW to test this batch file on), as I'm leaning more towards the direction of this batch file being replaced or intellegently merged into a more elaborate package that also includes modification of the base models. So when a report comes in that a command prompt disappears rather instantly and things don't work, I'm inclined to think that's user error.