Full and Incremental backups take the same amount of time

If you are performing disk backup, and you have the option "Fast incremental/differential backup" off, it will compare the whole content of backed up files with files on the disk. Are incrementals created of normal size, not the same as full?

I have "use fast incremental/differential backup" checked. I'm not sure what you mean by normal size, but I'll assume you mean the size of the backup - no, the incremental seems to take up about as much space as the data it contains. Oddly, though, it contains folder listings for folders (directories) that haven't been touched since the last full system. I can't see the logic behind it unless it's basing the incremental on a last access stamp which to me shouldn't be a suitable measure of whether to backup a file - last modified should be the criteria.

I'll append my earlier question to say that the process doesn't take as long as a full backup, but it certainly takes longer then what a read on a date and time stamp should take (IMO). Additionally, I've noticed that the progress indicator (time left) is often askew, even when doing a full backup. It will almost immediately jump to 50 percent completed. I'm going to load up the latest build when I run my next full system and see what else I can see. Thanks for taking the time to respond.

Oddly, though, it contains folder listings for folders (directories) that haven't been touched since the last full system.

It's normal. If you explore incremental backup in any way, it will show the exact content of backed up data at the moment of backup execution, no matter if it physically resides in this incremental or previous backups. If the .tib file of the incremental backup is itself as large as the full, it is most likely full. It may help if you post your backup settings (what, where, is 'simplified naming' checked, backup scheme (simple/custom/etc)