DiscImageCreator

[iR0b0t]

sarami, i was testing the dvd command and faced some problems with /c parameter. While dumping CMI for this dump DIC aborts reading as soon as it reaches the unreadable area. Is there any way those sectors can be ignored and possibly flagged somehow?

Logs attached:

[F1ReB4LL]

I think it's better to generate the .cue variant as well.

I'll code it in the future.

Technically, you can't add a DC dump into db without the .cue So, it's an important feature.

[sarami]

in the last 2 Dreamcast dumps that I have tried, the DIC shows this error:

Fixed. This had occurred only GD-ROM and minus offset disc.

sarami, i was testing the dvd command and faced some problems with /c parameter. While dumping CMI for this dump DIC aborts reading as soon as it reaches the unreadable area. Is there any way those sectors can be ignored and possibly flagged somehow?

Skipped returning error.

it's an important feature.

I make an effort to be able to code it this month.

[ajshell1]

sarami

I'd like to ask why DIC is licensed with Microsoft Public License. Is it dependent on a piece of code that uses the MS-PL, or would it be feasible to change the license to the GPL?

https://github.com/saramibreak/DiscImag … er/LICENSE

[sarami]

Is it dependent on a piece of code that uses the MS-PL

No.

would it be feasible to change the license to the GPL?

I don't like strong copyleft. Is MS-PL awkward for you (or in general)? I don't know much about licence.

[ajshell1]

Is it dependent on a piece of code that uses the MS-PL

No.

would it be feasible to change the license to the GPL?

I don't like strong copyleft. Is MS-PL awkward for you (or in general)? I don't know much about licence.

Thanks for considering me. I had a pipe dream of getting DIC ported to Linux at some point, either by you or someone else. Licensing it under the GPL would probably make that slightly more feasible.

However, if you don't like a strong copyleft, can I ask you to use the MIT License? While it is compatible with the GPL, it doesn't have a strong copyleft.

I'm also concerned that the MS-PL is a rather obscure license. In my experience, people prefer to work with projects with more common licenses. And as far as common licenses go, 44.69% of Github projects used it in 2015 (https://blog.github.com/2015-03-09-open … ithub-com/).

I appreciate the fact that you were willing to consider this. This is ultimately your project, so you can do what you want with it.

[FatArnold]

Thanks for considering me. I had a pipe dream of getting DIC ported to Linux at some point, either by you or someone else. Licensing it under the GPL would probably make that slightly more feasible.

However, if you don't like a strong copyleft, can I ask you to use the MIT License? While it is compatible with the GPL, it doesn't have a strong copyleft.

I'm also concerned that the MS-PL is a rather obscure license. In my experience, pepple prefer to work with projects with more common licenses. And as far as common licenses go, 44.69% of Github projects used it in 2015 (https://blog.github.com/2015-03-09-open … ithub-com/).

I appreciate the fact that you were willing to consider this. This is ultimately your project, so you can do what you want with it.

The MS-PL is very permissive, why would it cause any issues with porting to Linux? Especially compared to the GPL which isn't very permissive at all.

[jhmiller]

in the last 2 Dreamcast dumps that I have tried, the DIC shows this error:

Fixed. This had occurred only GD-ROM and minus offset disc.

Thanks, sarami.
Now it works perfectly.

[ajshell1]

The MS-PL is very permissive, why would it cause any issues with porting to Linux? Especially compared to the GPL which isn't very permissive at all.

According to http://directory.fsf.org/wiki/License:MsPL
"This is a free software license; it has a copyleft that is not strong, but incompatible with the GNU GPL. We urge you not to use the Ms-PL for this reason."

That incompatiblity with the GPL is my main concern. MANY programs on Linux use the GPL, including the Linux kernel itself. From what I understand, license incompatibilities can cause problems when trying to port software to Linux. For example, ZFS was released under the CDDL. While this is a free software license, it is not compatible with the GPL, and implementations of ZFS have suffered as a result of this. (See here for more info: https://www.fsf.org/licensing/zfs-and-linux)

I just want to try and avoid any such situations IF I can ever get DIC ported to Linux. That's a big "if", but I'd honestly be willing to pay someone to handle the port.

EDIT:
And if sarami doesn't like the MIT license, there are plenty of other GPL compatible llicenses without a strong copyleft, such as the Apache 2.0 License and the Modified BSD License. More can be found here https://www.gnu.org/licenses/license-li … leLicenses

[darksabre76]

I have one possible suggestion: Every time my drive overheats, it starts throwing the "COMM" errors, which are hardware issues. If at all possible, can those be treated like C2 errors? I'd like for those sectors to be rescanned at the end just like that, since right now, if my drive decides to crap out like that in the middle of a dump, I have to stop it and start all over, since it won't be caught as an error until the very end.