sarami wrote:Try to use su or sudo.
That fixed it. Thanks.
But why does DIC require root privileges?
Many SCSI commands require it.
You are not logged in. Please login or register.
Redump Forum → Posts by FatArnold
Pages 1
sarami wrote:Try to use su or sudo.
That fixed it. Thanks.
But why does DIC require root privileges?
Many SCSI commands require it.
I have a GD that seem to be impossible to dump. Promo version of Tom Clancy's Rainbow Six incl. Eagle Watch Missions.
Disc is like new.
This is what my 708 gives me: https://mega.nz/#!rgJEFYpK!_ipAJ19QpHFp … FHYzjGi3xk
Other drives give similar results.
FatArnold wrote:I tried dumping some gd-rom today with my PX-708. Unfortunately I get a segfault as soon as I enable /c2. Without /c2 the dump starts. Happens both on linux and the latest windows release.
Uploaded test version.
Thank you so much for everything! Tried reading a GD-ROM just now and the dump went just as it should.
However, now it segfaults after the dump. But all the data seem to be dumped correctly
AppVersion
x86, AnsiBuild, 20180923 110347
/c2 val1 is omitted. set [4000]
/c2 val2 is omitted. set [0]
/home/rebecca/Desktop/DiscImageCreator_linux_test/4Wheel/ doesn't exist, so create.
CurrentDirectory
/home/rebecca/Desktop/DiscImageCreator_linux_test
WorkingPath
Argument: 4Wheel/4Wheel.bin
FullPath: /home/rebecca/Desktop/DiscImageCreator_linux_test/4Wheel/4Wheel.bin
Drive: /
Directory: home/rebecca/Desktop/DiscImageCreator_linux_test/4Wheel/
Filename: 4Wheel
Extension: .bin
StartTime: 2018/09/23(Sun) 11:16:05
Set the drive speed: 2822KB/sec
This drive supports [OpCode: 0xd8, SubCode: 0]
This drive supports [OpCode: 0xd8, SubCode: 1]
This drive supports [OpCode: 0xd8, SubCode: 2]
This drive supports [OpCode: 0xd8, SubCode: 8]
Checking SubQ adr (Track) 18/18
Checking SubRtoW (Track) 18/18
Reading DirectoryRecord 1/ 1
Set OpCode: 0xd8, SubCode: 8(Raw)
Creating .scm from 45000 to 549151 (LBA) 549150
No C2 errors
Descrambling img (LBA) 504149/504150
Exec /home/rebecca/Desktop/DiscImageCreator_linux_test/./EccEdc_linux.out check /home/rebecca/Desktop/DiscImageCreator_linux_test/4Wheel/4Wheel.img
FILE: /home/rebecca/Desktop/DiscImageCreator_linux_test/4Wheel/4Wheel.img
Checking sectors (LBA) 504149/504149
[NO ERROR] User data vs. ecc/edc match all
Segmentation fault
I tried dumping some gd-rom today with my PX-708. Unfortunately I get a segfault as soon as I enable /c2. Without /c2 the dump starts. Happens both on linux and the latest windows release.
I don't know much about copy protections. Wouldn't it be a good idea to make a wiki page listing some basic known facts about the copy protections we know about? Things like how they work, how to identify them and how to deal with them when dumping.
Thanks. download link is same.
- fixed: disc speed changing doesn't work for linux.
- fixed: increased memory allocation for double pointer (subchannel, cd-text)
- deleted: some warning when used Wextra
Wow, it works absolutely great! Thank you so much for the Linux version.
Uploaded test version.
win: http://www.mediafire.com/file/eq80y20l9 … st.7z/file
linux: http://www.mediafire.com/file/uw3e03kdk … t.tar/file
Linux build works great, but seem to fail at .bin creation with Audio CDs.
Logs:
https://mega.nz/#!eghiiQLB!B4smJK10MAWx … boCdMvjQcM
https://mega.nz/#!X4hAgQwT!U7cYJQI6Qokx … 5W4_vK6Gxs
Updated makefile. Please pull the test branch.
Lovely <3
Thank you so much!
Have anybody had any luck building DIC from the make-file?
I dumped an audio CD and got a regular .cue file but also one suffixed "(Subs indexes)".
What's the subs indexes version and how is it calculated differently?
It's on Linux now? Thank you so much <3
Thank you!
It's already on github but the code is quite terrible as I'm a horrible coder and have so little time to work on it right now.
The flag system info is very useful, thanks.
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.
I agree.
BUT, we have 13297 existing PC dumps.
Who's going to fill in that info for all those discs?
The dumpers probably. Shouldn't be much different from other additions and fixes
I personally think an OS tag would be a thing to introduce. It would absolutely benefit macOS and PC.
Just to give a quick update. I've been working some on the GUI but I have very limited time to do so
It works, you can dump discs with it and it supports various profiles. But it still has some bugs and missing features and needs some more work.
Just making a gui shouldn't be much too hard to make. I'll see if I can get something done.
What exactly is stopping us from switching over to cue files?
I'm basically referring to all guides, but relevant to me right now is the GD-ROM guide which I think is overly verbose for beginners. It's not like I feel they're incomprehensible or anything, but as someone coming back to dumping after many years there are some things I think can be made more clear. Specifically with clear-cut examples, especially for most systems/discs we know need special treatment.
While the dumping guides are generally really good, I think I could maybe make them a little bit more noob-friendly.
Could I please have wiki-access so that I can work a bit on them? I'll of course not change anything in the guides directly, but work on a temporary page and then we can discuss the changes
I'm very much for the switch. Actually, I'm very much for a switch to any kind of (documented) format, no matter if it is usable by current burning programs or not, if it helps to preserve the discs more accurately.
Granted I'm no expert on the subject, but sub-channel and scrambled support seems to me to be the only direction to go. Whether the data is relevant or necessary is one thing, but it is a part of the discs and IMO ought to be preserved. I've always thought cue-files seemed like a kind of a hack-job anyway.
As stated, I'm no expert, so I have a few dumb questions.
Nexy commented that there are limitations to the ccd format too. I'm not really read-up on the format. Could someone fill me in on what the actual limitations are?
And what about DVDs, BDs, GDs and such? Gigadiscs, as far as I understand it, is CD based and as such would have both subs and scrambled data. DVDs and such I have no idea as to how they're structured. Would the ccd format be used only for CDs or would GDs, DVDs, BDs etc. also use it?
Pages 1
Redump Forum → Posts by FatArnold
Powered by PunBB 1.4.4, supported by Informer Technologies, Inc.
Currently installed 6 official extensions. Copyright © 2003–2009 PunBB.