Suggestion

[pic]

With backups, Make a directory for ALL backups or something. Because, if you want to uninstall a mod that you have installed earlier, and you installed another mod after that mod, all mods you installed after the one your installing can be messed up. I have to redo my WHOLE forum now

[Nightrider]

I'm not sure what good an All backups folder would do. If you mix the various backups into one folder, then you will only be able to uninstall the last MOD installed and none of the others...

Even if you made the mistake of restoring backups in the wrong order, you have all the modified files in the processed folder that you could restore to bring your board back to where it was before you screwed it up. So there is no need to start over...

[pic]

With the all backups folder, it could have every file edited, and then a file with what's changed in each mod. Then if you unistall a mod, it will just go in and undo what it did.

And for the re-install by redoing them, I really can't. Some mods don't work at first, and I usually have to edit the installation file. So now they won't install properly.

[Nightrider]

Perhaps if you know how to code a MOD that can correctly do as you are suggesting, that would be a nice contribution to the community. But you should underestand that it isn't going to be an easy task. Think of the problem...

If you install several MODs that do a REPLACE WITH on the same line of code and you modified the code to work correctly during the install, then how is your utility going to know how to correctly undo the changes if you restore the MOD out of sequence? Your utility wouldn't be able to restore the code from the FIND command because that code had been modified in MODs added after the fact. So then your utility would have to go through every MOD file to try to figure out how to restore the code from a REPLACE WITH command. That really isn't feasible and wouldn't likely work well, especially if you also manually modify your files from time to time...

If you want to write a utility that can correctly do as you are suggesting, that would be a monumental undertaking. Once you start working on it, you might realize that it isn't nearly as easy as you might think. I wouldn't mind if someone could develop a better utility than what we have now, but I don't imagine it is going to become a reality any time soon...

[pic]

I highly doubt I would be able to code something. But the current one is just not functional. If you restore the backups, then other mods that you installed after it that also edited that file are gone for good and errors galore pop up.

[Nightrider]

Actually EM's Restore Backups utility works very well. If you install a MOD, then 5 more, then you have to restore the 5 MODs before you can restore the first. You remove MODs in a FILO (First in, Last out) process. I once had to restore backups for 20 MODs to find a weird problem caused by one of the MODs but I wasn't sure which. So by restoring the MODs in reverse order that they were installed, I was able to pin-point the problem after restoring backups for 20 MODs...

If you Restore Backups in the proper reverse order that they were installed, you won't have any problems either. Your problem was caused by restoring backups in the wrong order. If you install some MODs with EM and some manually, then EM won't have backups of the files that were manually modified, so that would cause a problem too if you later decided to restore backups using EM's Restore Backups utility. It is best to install all of your MODs using EM so that there are complete backups of all modified files for each and every MOD installed on your board...

[pic]

Thanks. I figured that out now.

[Nightrider]

Good deal. Once you understand the process, it makes a whole lot more sense...