DIC crashes when "checking EXEs" :
It's invalid report.
See, please. https://github.com/saramibreak/DiscImag … _report.md
You are not logged in. Please login or register.
Redump Forum → Posts by sarami
DIC crashes when "checking EXEs" :
It's invalid report.
See, please. https://github.com/saramibreak/DiscImag … _report.md
Updated 2022-02-01 version
https://github.com/saramibreak/DiscImag … g/20220201
*2022-02-01
- added: /vrfy flag for checking non-zero byte of audio CD
- added: buffer size check when IMAGE_EXPORT_DIRECTORY is outputted
- added: support for reading cache via 0xF1 on HL-DT-ST BD-RE WH14NS48 v.1.D3
- changed: "DATE" to "wmic os get LocalDateTime" when createBuildDateTime.bat is created
- changed: check disk free space
- changed: Hash image while dumping (DVD, BD)
- fixed: trim the string of i6comp.exe
- fixed: string (x86 -> 32 bit)
- fixed: ARccOS is checked by DVD-Video
- fixed: cue file when /p is used
- fixed: disk space checking for linux
- fixed: when used .petite, it's skipped reading Export, Import, Resource data due to the compressed data
- fixed: dumping of "Star Wars - Shadows of the Empire Soundtrack"
Is it just max speed
Yes.
I'm told by some people on Discord that ARccOS is detected by looking for files in a certain area of the disc that is normally blank. This actually caused some older and non-Sony DVDs to be falsely flagged as having ARccOS, which is why this came up.
Yes, https://github.com/saramibreak/DiscImag … issues/100 https://github.com/saramibreak/DiscImag … issues/102
I've searched for the magic string like MVSNRGFP, but couldn't find it.
what is RGFP?
RG is RipGuard? FP... I don't know. File? Flag? Pointer? Position?
Are there any other methods of anti-ripping protection (besides the CSS/CPPM encryption that's been standard since DVD's inception) on DVD-Video discs besides "MVSNRGFP" and ARccOS that you are aware of?
Not yet.
No PVD is detected on this disc, but sector 16 has a normal PVD, so I wonder what the problem is?
It's a known issue.
http://forum.redump.org/post/94542/#p94542
I have no idea about it now.
here's another disc you might want to snag for study
I have already another one.
http://forum.redump.org/post/84421/#p84421
I redumped it, but it generated the same hash.
Something weird is going on on my side. In your logs it seems the protected sectors are handled correctly but on my side it tries to reread some of the sectors despite being already detected as protected.
My disc doesn't have an intentional C2 error. It seems several versions(?) exist in this protection.
@sarami: I wanted to know how you did dumped that disc: http://redump.org/disc/45814/
Did you just used the /sf command for Bitpool?
Redumped it. https://www.mediafire.com/file/7r5xtssh … og.7z/file
Why is it counting 150 sectors as part of write offset? Is it a bug?
As it is written in the comment of http://redump.org/disc/77974/ , these discs start AMSF 00:00:00, not 00:02:00. Due to this problem, there is not the sync in the last 150 data sectors. EccEdc judges it as error.
Here is my proposed method for automatic offset detection for Audio CD's:
I translate the src I already coded to English. Thanks to Intothisworld, perhaps it's almost coded except -10.000 to +10.000 samples you say.
I hope to test the latest version of the https://github.com/saramibreak/DiscImag … /issues/95 to more people.
1. Check the non-zero byte position from last - 75 to last + 75.
2. Check the non-zero byte position from LBA 0 - 75 to LBA 0 + 75.
3-1. If the difference of the last non-zero byte position and 1st non-zero byte position are bigger than 0 sample and smaller than 588 samples...
3-1-1. If the last non-zero byte position is equal to the 1st non-zero byte position, Set the custom offset.
3-1-2. If the last non-zero byte position is bigger than the 1st non-zero byte position, It can't set the custom offset.
3-1-3. If the last non-zero byte position is smaller than the 1st non-zero byte position.
3-1-3-1. If the 1st non-zero byte position is smaller than the combined offset, Set the custom offset.
3-1-3-2. If not 3-1-3-1, it's no need to fix the combined offset.
3-2. If the difference of the last non-zero byte position and 1st non-zero byte position are bigger than 588 samples... (last < 1st)
3-2-1. If the last non-zero byte exists in the last sector or lead-out and the 1st non-zero byte exists in the LBA 0 or backward.
3-2-1-1. If the last non-zero byte position exists in the last sector and its position is smaller than the combined offset, it's no need to fix the combined offset.
3-2-1-2. If not 3-2-1-1, set the custom offset.
3-2-2. If the last non-zero byte exists in the forward than the last sector and the 1st non-zero byte exists in the LBA 0 or backward.
3-2-2-1. If the 1st non-zero byte exists in the LBA 0 and the 1st non-zero byte position is smaller than the combined offset, Set the custom offset.
3-2-2-2. If not 3-2-2-1, it's no need to fix the combined offset.
3-2-3. If the last non-zero byte exists in the forward than the last sector and the 1st non-zero byte exists in the pregap sector, Set the custom offset.
3-3. If the difference of the last non-zero byte position and 1st non-zero byte position are bigger than 588 samples... (1st < last)
3-3-1. If the 1st non-zero byte exists in the LBA 0 or backward and the last non-zero byte exists in the last sector or lead-out, it can't set the custom offset.
3-3-2. If the 1st non-zero byte exists in the pregap and the last non-zero byte exists in the last sector or lead-out, it can't set the custom offset.
3-3-3. If the last non-zero byte exists in the last sector and the last non-zero byte position is smaller than the combined offset, it's no need to fix the combined offset.
3-3-4. if not 3-3-3, set the custom offset.
3-3-5. If the 1st non-zero byte exists in the pregap and the last non-zero byte exists in the forward than the last sector, it can't set the custom offset.
3-3-6. If not 3-3-5, it's no need to fix the combined offset.
sarami if you're still looking for this VCD http://redump.org/disc/74810/ which gives wonky errors, there's one in this pack that ships worldwide: https://www.ebay.nl/itm/265429499035
Ordered it.
I managed to grab another copy, same ringcode and all... and this time it worked without issues.
So likely something bad going on with the discs themselves even if they don't look visually bad.
It's weird... Do you upload these logs? Generally, "MEDIUM_ERROR - NO SEEK COMPLETE" is a drive problem.
I've been tired to say "Please use the latest version" every time, especially MPF users.
I recommend github issue from now on when the bug is reported.
If it is reported in this forum, see the bug_report.md.
Tried to dump PS2 cheat discs with big data protection, always getting different hashes with newest versions of DIC, DICUI and DIC_test.
statiomaster_032002_20210701T212154.txt --> It's old version. Typically, the bug report of the old version is meaningless.
And it's a known issue. http://forum.redump.org/post/96246/#p96246 http://forum.redump.org/post/96445/#p96445
Please check which bytes of the img of the latest DIC are different using fc command by the command prompt.
fc /b statiomaster_022002.img statiomaster_032002.img
I'm trying to dump one of the missing XBOX games ("Scarface") that DIC seems to have an issue with right at the start.
Same problem. http://forum.redump.org/post/97197/#p97197
Scarface is http://redump.org/disc/60487/ ? or http://redump.org/disc/36869/ ?
Tell me Amazon or eBay link, plz.
Is it correct?
SubQ indicates it is correct.
LBA[000000, 0000000]: P[ff], Q[410100000005000002004cb6]{ Data, Copy NG, Track[01], Idx[00], RMSF[00:00:05], AMSF[00:02:00]}, RtoW[0, 0, 0, 0]
LBA[000001, 0x00001]: P[ff], Q[41010000000400000201f6c6]{ Data, Copy NG, Track[01], Idx[00], RMSF[00:00:04], AMSF[00:02:01]}, RtoW[0, 0, 0, 0]
LBA[000002, 0x00002]: P[ff], Q[41010000000300000202a171]{ Data, Copy NG, Track[01], Idx[00], RMSF[00:00:03], AMSF[00:02:02]}, RtoW[0, 0, 0, 0]
LBA[000003, 0x00003]: P[ff], Q[410100000002000002031b01]{ Data, Copy NG, Track[01], Idx[00], RMSF[00:00:02], AMSF[00:02:03]}, RtoW[0, 0, 0, 0]
LBA[000004, 0x00004]: P[ff], Q[410100000001000002048534]{ Data, Copy NG, Track[01], Idx[00], RMSF[00:00:01], AMSF[00:02:04]}, RtoW[0, 0, 0, 0]
LBA[000005, 0x00005]: P[ff], Q[410101000000000002057897]{ Data, Copy NG, Track[01], Idx[01], RMSF[00:00:00], AMSF[00:02:05]}, RtoW[0, 0, 0, 0]
LBA[000006, 0x00006]: P[00], Q[41010100000100000206e2a5]{ Data, Copy NG, Track[01], Idx[01], RMSF[00:00:01], AMSF[00:02:06]}, RtoW[0, 0, 0, 0]
LBA[000007, 0x00007]: P[00], Q[410101000002000002071c56]{ Data, Copy NG, Track[01], Idx[01], RMSF[00:00:02], AMSF[00:02:07]}, RtoW[0, 0, 0, 0]
I got "_alt.cue" and "_imgAlt.cue"
CD-TEXT can store 8 languages.
Language code BLOCK 0: 0x09 (English)
Language code BLOCK 1: 0x69 (Japanese)
Language code BLOCK 2: 0x00 (not applicable)
Language code BLOCK 3: 0x00 (not applicable)
Language code BLOCK 4: 0x00 (not applicable)
Language code BLOCK 5: 0x00 (not applicable)
Language code BLOCK 6: 0x00 (not applicable)
Language code BLOCK 7: 0x00 (not applicable)
BLOCK 1 language uses _alt.cue, BLOCK 2 language uses _alt2.cue ... BLOCK 7 language uses _alt7.cue
I don't have ARM machine, so I can't test.
I now get another compilation error
fixed typo (off_t -> off64_t)
I get the following errors when attempting to build from source with GNU Make 4.2.1 on ARM, default settings. Am I missing deps? Or some environment variable?
removed _W64
https://github.com/saramibreak/DiscImageCreator
Also the feature to calculate enough free space is broken. I tried dumping a PS3 disc with 119GB free on my hard drive and I got an error.
'bd' command supposes BDXL-R QL.
Old and new DIC builds, I'm getting an error with a particular disc in good-enough condition. It's a later Xbox (OG) kiosk disc.
LBA[1913094, 0x1d3106]: [F:ReadXBOXDirectoryRecord][L:1192]
Opcode: 0xa8
ScsiStatus: 0x02 = CHECK_CONDITION
SenseData Key-Asc-Ascq: 03-02-00 = MEDIUM_ERROR - NO SEEK COMPLETE
Kreon does not support this disc?
scanning the .img instead of the .bin files, resulting in an incorrect error count for multisession discs.
https://www.mediafire.com/file/eq80y20l … st.7z/file
- changed: do not check 11400 sectors of lead-in and lead-out
https://github.com/saramibreak/DiscImag … /issues/95
If non-zero byte exists in the 1st lead-out, fix the combined offset.
If non-zero byte exists in LBA -1, check only.
https://github.com/saramibreak/DiscImag … g/20211101
*2021-11-01
- fixed: ReadErrorProtect
but .010 and .011 files are still skipped
(link is same)
- fixed: check string length
There is no extension
https://www.mediafire.com/file/eq80y20l … st.7z/file
- fixed:
Only check files.
Is there a way to better define which file to skip so it only skips "/SNGM/SNGM"?
Define only filename and extension.
Redump Forum → Posts by sarami
Powered by PunBB 1.4.4, supported by Informer Technologies, Inc.
Currently installed 6 official extensions. Copyright © 2003–2009 PunBB.