Search options (Page 3 of 3)

I seem to be getting a different error:

After doing: sudo mount /dev/sr1 /mnt/d

[aj@Canopus test]$ ./DiscImageCreator_linux.out cd d SC3K.bin 8 /c2 /d8 /sf /ns
AppVersion
        x86, AnsiBuild, 20180711 160517
/c2 val1 is omitted. set [4000]
/c2 val2 is omitted. set [0]
/sf val is omitted. set [60]
CurrentDirectory
        /home/aj/games/test
WorkingPath
         Argument: SC3K.bin
         FullPath: /home/aj/games/test/SC3K.bin
            Drive: 
        Directory: /home/aj/games/test/
         Filename: SC3K
        Extension: .bin
StartTime: 2018/07/11(Wed) 11:02:05
[F:TestUnitReady][L:44] GetLastError: 25, Inappropriate ioctl for device

I seem to be getting that error regardless of whether I have a disc mounted to that point or not.

Honestly, I'm not sure if you are going about it the right way. The way Windows and Linux handle mounting of drives is fundamentally different. I think it would be smarter to have us select the device name (e.g. /dev/sr0 or /dev/cdrom) rather than a mount point. I know that you might not like that since it'll make your programming experience harder and your code messier, but I think the way it is now is only going to lead to more problems. However, that's just my opinion.

I'm not sure what exactly you'll need for full Linux support in the future, but I'm willing to help you in any way that I can. Including financially.

Also, if you could run "lsblk" in WSL, that might help us out.

My position on this issue:
For most consoles: Meh, go ahead. Nintendo and Sony make sure version info is consistent. Don't do this for the GameWave though.

For PC: NO NO NO NO NO NO!

Version info is FAR too messy on PC for this to be in the filename. It doesn't belong there.

If you disagree, look at these and consider what the revised filename would be:
http://redump.org/disc/21147/
http://redump.org/disc/45369/
http://redump.org/disc/49850/

And I believe putting the version information for http://redump.org/disc/11223/ in the filename will break stuff since slashes aren't allowed on Windows files.  Yes, that game has two versions. Running sshock.exe gives a version of F1.6S, and running cdshock.exe gives a version of F1.6C.

Besides, I doubt Jackal will ever agree to this change.

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

I agree.

BUT, we have 13297 existing PC dumps.

Who's going to fill in that info for all those discs?

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

No. You need a Plextor and DIC for CD dumps.

You can use DIC to dump DVDs with any normal DVD drive, so I suggest dumping those while you wait for a new Plextor.

I've noticed a problem with DIC.

I recently got a copy of Madden 2005 Collector's Edition http://redump.org/disc/20599/

This is a dual-layer disc.

However, DIC doesn't recognize this, and only dumps one layer.

This isn't a problem with the disc, as Isobuster can extract an .iso that matches the database.

I've tried it with my TSST TS-H353B and my ASUS BW-12B1ST a, with identical results.

I have some original Xbox discs. This is what appears on LBA 16 of Halo CE 1.02:

0320 : 00 00 00 00 00 00 00 00  00 00 00 00 00 32 30 30   .............200
0330 : 31 30 39 31 33 31 30 34  32 35 35 30 30 30 30 30   1091310425500000
0340 : 30 30 30 30 30 30 30 30  30 30 30 30 30 30 30 30   0000000000000000
0350 : 30 30 30 30 30 30 30 30  30 30 30 30 30 30 30 30   0000000000000000
0360 : 30 30 30 30 30 30 30 30  30 30 30 30 30 30 30 30   0000000000000000
0370 : 30 01 00 53 65 63 44 75  61 6C 4C 61 79 65 72 53   0..SecDualLayerS
0380 : 74 61 72 74 3D 30 30 30  30 36 38 33 32 00 00 00   tart=00006832...

That looks like a PVD to me.