Actually what i was trying to do is this. I want to install/copy an aeroplane for my flightsim from the original directory say dir c:\origdirplane to d:/flightsim. In the future if I don't like it I'd have to remove the files I copied so I'd go to my original directory and compare the files I installed into d:flightsim and remove them with diropus ?
I think the idea is like a reverse sync... So the source is left alone, but anything in the destination that is also in the source gets deleted (recursively).
There are a few ways you could do this, but maybe it's not needed: Do you try out the new plane in the flightsim straight away, and then decide if you want to keep it or not? If so, and if you don't shutdown Opus or reboot between the two things, then you can probably use the Undo List in Opus to undo the file copy and delete anything that was copied across. (The only thing it won't undo is restore the original versions of files which were replaced by other files.)
you taking a snapshot/image with imaging software right ? If yes I know but I was looking to see if i could do things with dopus.I have the feeling it can be done as leo suggested but I need him to tell me how
You wouldn't need to use imaging software if it's something which can be undone by simply deleting some files. Just copy the directory to somewhere else, then when you're done sync it back with the option turned on to delete files from the destination that are not in the source. (Assuming there are no unusual file permissions or alternate-data-streams on the files in that folder. If there are then they might be lost in the process.)
But I'm assuming you wouldn't want to do that because it would involve copying a lot of extra data, given the size of games/sims these days.
The solutions I had in mind are a bit klunky but would work. For example, it'd be fairly easy to write a small vbscript which takes the two directories and then goes through the source directory making a list of everything in it, while deleting those things from the destination directory. Or, if you wanted to check what was going to be deleted before going ahead, the vbscript could generate a .bat file which would delete the files when run and which could be viewed first in a text editor. (Assuming none of the filenames have non-ascii characters which would cause problems in a .bat file. If they do then it could make a list of files that a second vbscript could delete.)
If it was me personally, I'd launch Beyond Compare (or a similar tool) from Opus and click its button which shows only files which are in both the left and right sides, then delete the ones on the right.
If it was me personally, I'd launch Beyond Compare (or a similar tool) from Opus and click its button which shows only files which are in both the left and right sides, then delete the ones on the right.[/quote]
I donloaded beyond compare and it looks a bit confusing to me.How would I launch the software from OPUS ? Would you mind giving me some fool-proof instructions ? Thanks
You can easily do that by adding a DOpus command that starts xxcopy.exe (free for private usage):
The following command recursively (!) removes all files from the destination directory that exist in the source directory and look identical (file/size). In other words you can rollback a copy operation that was done from source to destination without any conflicts occurred.
Thanks for your instructions. I made it I'd have another question: Beyond compare does not seem to always search subfolders. Sometimes files appear and then disappear right away tooo.is there also a way to let it compare the entire hard drive ?
When comparing folders, BC initially shows everything below the initial folder, including files it has not yet compared, and then updates the list as it goes along, potentially hiding files it was initially showing if the comparison result means they should not be visible according to the mode you have BC in.