The echos and the pause are so u can view the results easily.
This way presents a problem as some sytems default to the root of a drive and usually not where xbedump is actually located.
C:\ and C:\WINDOWS are both valid paths but the \ at the end of C: will cause problems when refering to files such as "%truepath%\xbedump.exe" (it will become C:\\xbedump.exe). It can however, be used to "CD" to the directories fine. I used truename instead of CD as truename will return valid 8.3 (DOS) names while CD uses long filenames.
Once you're in the same dir as xbedump, out.xbe is easy to find and copy back to the original: "copy out.xbe %1 > nul" should do it.
Backups can be as simple as "copy %1 %1.bak".
Version 3 of EZ-xbedump? Probrably not... I intend to fix the one issue I know exists and any others that may pop up, but version 2 will probrably be the last. I do plan on adding a "fast" option that will skip the verification and naming of the target XBE for advanced users only.
I can see a few things that would be useful in your next versions
1) custom install directory (the user picks where it's installed)
2) preferences saved to and read from an ini file. (for those who don't want shell intergration)
3) colored menus
4) ftp functionability
5) recursive signing (of course)
6) custom icons for XBE files
7) identification and/or archiving of XBE's (including zip or cab support if desired)
references:
http://www.microsoff...help/ntcmds.htmhttp://home7.inet.tele.dk/batfiles/http://home7.inet.te...atfiles/msdos7/well that's stupid, why don't we change all "microsofft" references to "MS"
remove the extra "f" to reach the URL