Exclude File & Folder help!!!

[a1pcfixer]

Something that badly needs done is to make these image programs to have
'Basic' and 'Advanced' tabs. Basic for standard imaging, and Advanced
to those wanting the full capabilities.

Might go far in getting users of other imaging software to migrate to
these. Currently, the more capabilities these have, the more daunting
they appear to some users.
--

Jim L.
Using - Virtual Access(OLR)
http://www.virtual-access.org
6.3.0.5 Windows Vista Service Pack 2 build 6002

[DrTeeth]

On Sat, 20 Apr 2013 10:10:42 PDT, just as I was about to take a herb,
a1pcfixer disturbed my reverie and wrote:

>Something that badly needs done is to make these image programs to have
> 'Basic' and 'Advanced' tabs. Basic for standard imaging, and Advanced
>to those wanting the full capabilities.

Sounds like a great idea. Then WW 3 will start as we will all want our
'favourite/most wanted' items to appear in the GUI, LOL.

Seriously, IfW is spookily powerful. There are too many things on my
'to-do/to-learn' list because something that I want to achieve is only
accessible via the command line and not the GUI.

I would suggest a major GUI overhaul, call it v3 and charge for it.
I'd buy.
--

Cheers,

DrT

** Stress - the condition brought about by having to
** resist the temptation to beat the living daylights
** out of someone who richly deserves it.

[userX]

DrTeeth wrote:
> Can this functionality be included in the GUI?
> --
>
One thing that comes to mind about such functionality generally (i.e., command line options without GUI equivalents) is that the GUI procedure can be set up completely with all the options made in it and then the corresponding command line equivalent can be shown within the GUI, and it can be saved in a batch file right then from within the GUI as well.

At this point the actual backup could be stopped from proceeding. The user could open up the batch file and add the one missing option (or more) to the command, and then the batch file could be saved and even run. It's not ideal, but it might suffice in many cases.

[userX]

TeraByte Support(PP) wrote:

[snip]

> The contents of the "myexcludes.txt" file would need to be the following to
> exclude everything in the Music folder (including sub-folders):
> [k]\Users\Andrew\Documents\Music\ >

I am not getting this "[k]" meaning. What does it represent or what would replace it?

[TeraByte Support(PP)]

The "k" option will keep the base folder when restored. In the above example, the "\Users\Andrew\Documents\Music\" folder would remain after restoring the partition (the folder would be empty).

Options exist for excluding files only (f) or truncating files (t) instead of deleting. Several examples are shown in the manual (search for /exlist).

[userX]

> "(the folder would be empty)."

So during the restoration procedure by IFL the excluded folder gets replaced empty under an assumption that the user would then add back in the original excluded contents from a different location?

[rseiler]

Can this feature be changed, perhaps optionally, so that it doesn't write a warning to the application log? I'd still like to be able to get legitimate warnings so I'd rather not disable it globally.

[TeraByte Support(PP)]

userX wrote:
> > "(the folder would be empty)."
>
> So during the restoration procedure by IFL the excluded folder gets replaced empty
> under an assumption that the user would then add back in the original excluded
> contents from a different location?

The excluded folder remains on the restored partition (it isn't removed/deleted). If you specify to keep the base folder it could be because you want to place contents back into it or it may be just that you want the folder to exist (e.g. there may be references to it by programs).

[DrTeeth]

TeraByte Support(PP) wrote:
> <snip> Several examples are shown in the manual (search for /exlist).

OT: Sorry, but you did mention using the manual.I would really like TBU to give the documentation to a user who is familiar with your products, but not too familiar. I have offered my services, IIRC I asked for some freebee licences. I am trying to find the time to get to grips with the batch facilities of IfW. Another user here has very kindly offered to help via email. I thought it courteous to look at the manual. I have levelled this criticism at other sections of you manuals but can now level it at the CLI guide too.

Basically, you say what an option will or will not do, but very rarely actually explain why one would use one over the other. For example, the first two boxes on page 111. Also the parameters "'/logmax:n' and 'LogMaxSize=n'
Ensures the log file doesn't grow beyond the size n given. Once n is reached the data from the top of the file is purged. Because of this, you typically don't want a large n value.
Default if omitted: There is no size limit on the log file" - but does not say what units are valid or how they should be formatted. The documentation is obviously written by somebody intimately familiar with the program, but it is not good if one wants to learn more about it. It needs to be proof read by a customer - my offer's still open.

[Brian K]

DrT,

Good luck. I think the final edition would be larger than the Encyclopaedia Britannica.