One SMALL(?) wish for TC6

[(john)]

Ability to 'background' SFV/CRC/MD5 creation and verify..

[Sam York]

Ability to 'background' SFV/CRC/MD5 creation and verify..

Yes, this function(background) would be very useful applied for plug-ins(like unpack) and also for ace/rar unpacking and so on ... And I don't think that any of these functions would be such small requests. However, I'd like to be wrong ...

[CoolWater]

well, in an other thread, it was mentioned, that rar is not thread-safe, so performing an unrar action in the background might be difficult...

[chea]

Ok, if it's not impossible to do...

I second the 'unpack .rar in background' suggestion... that is: to make it work like with the .zip files.


Cheers!

[gigaman]

I'm not sure about RAR (the sources for unrar are available, so it is possible to build own, thread-safe unrar library), but ACE is certainly not thread safe - most stuff is performed in global variables. Not that it would be impossible to fix (without having to make the ACE author do it), but requires a lot of nasty hacking...

[DarkRuleR]

Ability to 'background' SFV/CRC/MD5 creation and verify..

To go OT.
I support this feature too.

When I do a sfv check on a large number off files I start another TC session to continue working in the mean time.
Ability to do a check / creation in the background will solve this.

[Sheepdog]

Ability to do a check / creation in the background will solve this.

That would require the improvement of the current Chechk routine too.

As you probably know the CRC -check windows has the limitation that it can only display less than about 5000 lines (it's 4700 anything IIRC). So if you check a really large directory with more than 5000 lines youi will not be able to display the results for the very first files.

sheepdog

[DarkRuleR]

A possible solution for the CRC -check window could be:

You see this on alot of ftp-server with sfv check scripts.

Start the check.

- when a file is bad rename it to *.bad (test.r01 to test.r01.bad)
- when a file is missing rename it to *.missing (test.r01 to test.r01.missing)
- create a directory with the stats reported in the CRC -check window.
something like: [20 files - 100% ok]

DR...

[DarkRuleR]

2Sheepdog
I agree that its unfortunate that the CRC -check windows has the limitation you talked about.

But is there really somebody who wants to do a CRC -check on more then 5000 files?

And for the few people that do, a "save output window to file" option could solve this.
With 5000 lines of logging information I don't think a CRC -check window is the most sutable?

DR...

[majkinetor]

Thread related problems can be solved creating application with separte process space on every background request.

[Sheepdog]

2Sheepdog
I agree that its unfortunate that the CRC -check windows has the limitation you talked about.

But is there really somebody who wants to do a CRC -check on more then 5000 files?

I stumbled over this limitation. When you want to check the quality of a CD-RW or DVD-RW it is very convenient to do this by CRC. And then youll have easily much more than those 5000 files (even the "i386" folder of XP will exceed this limit).

And for the few people that do, a "save output window to file" option could solve this.
With 5000 lines of logging information I don't think a CRC -check window is the most sutable?

Output to file would be fine. And I agree that the small windows is not very suitable. I do copy the output manually to a textfile to find the errors in my editor.


sheepdog

[frenky]

A possible solution for the CRC -check window could be:

You see this on alot of ftp-server with sfv check scripts.

Start the check.

- when a file is bad rename it to *.bad (test.r01 to test.r01.bad)
- when a file is missing rename it to *.missing (test.r01 to test.r01.missing)
- create a directory with the stats reported in the CRC -check window.
something like: [20 files - 100% ok]

I think it would not be good to rename files on file system automaticaly. But, IMHO, nice point there.
Let's say TC v7 -> Use new Temp pannel functionality for this report? Maybe also mark files in alternate colors, depending on status...

[DarkRuleR]

I found a other downside.

When I start a CRC -check I often switch to another program to continue working.
Or start a new TC session.

The CRC -check will continue in the background.
But when the CRC -check is finished it's status windows prevents windows from "minimizing all windows".
(windows button + m)

I guess you could say this is "handy" b'coz you are reminded about the CRC -check status.

But I like it more that everytime I press "minimize all windows" it does just that.

A other background CRC -check solution could fix this as well.

DR...