DiskSpan GUI

[Cesar82]

Originally Posted by wareck

hello
I found a very small bug in the last release (64bit mode, I do not use 32bit)

If you start to compress then click on abord, then retry, diskpan can't restart
I need to exit and start again

(sometime during test, I do this kind of think several time to find the best compression method)

Best regards

There are no errors here.
see the attached video.

[wareck]

I found the issue
It's when I use parallel tool, like mpz_mtx.
when I click on abort , there is some threads still running.
Because of that, temporay folder and archive are still in use.
So when I click on retry, diskspan can't delete conversion temporay file and make some error code.

I just need to check is there is no anymore process still runing...
was my bad

thanks !
best regards

[Cesar82]

Originally Posted by pcblizzard

Has the feature ‘Component=1,3’ been removed? As soon as I exit DiskSpan GUI (I have saved the settings I made) and restart DiskSpan GUI in dev mode, the setting I made previously is missing (in this case ‘1,2,3,4’ - in ‘Tasks’, for example, the entry ‘1,2,3,4’ remains after a restart).

I noticed this in version 2.0.1.7 and in the latest version (2.0.2.0).


KR pcblizzard

Until the current version of the DiskSpan GUI, it is only possible to configure components when there are 2 or more GAMES tabs.
The components function was inherited from CIU in which each component is a game and is only validated if there are 2 or more games.
In other words, components are only used to create a collection of games.
For additional packages, use task settings.

In the next version of DSG it will be supported to use multiple components even if you only have a single game configured.

Originally Posted by wareck

I found the issue
It's when I use parallel tool, like mpz_mtx.
when I click on abort , there is some threads still running.
Because of that, temporay folder and archive are still in use.
So when I click on retry, diskspan can't delete conversion temporay file and make some error code.

I just need to check is there is no anymore process still runing...
was my bad

thanks !
best regards

I did a test here using mpz_mtx with random files and everything seems to be ok...
See the test in the attached video.

[KaktoR]

Originally Posted by wareck

I found the issue
It's when I use parallel tool, like mpz_mtx.
when I click on abort , there is some threads still running.
Because of that, temporay folder and archive are still in use.
So when I click on retry, diskspan can't delete conversion temporay file and make some error code.

I just need to check is there is no anymore process still runing...
was my bad

thanks !
best regards

This is because mtx using chunks to process data. Each chunk (x MB) needs to finish before anything else happens. The more chunks you have (x cpu threads) and how big the chunks are (x MB) the more time it takes.

One solution is to taskkill all mtx processes if click on "Abort" button.