nope https://drive.google.com/file/d/1h03hql … sp=sharing
Here is the disc for sale in Japan: https://www.ebay.com/itm/362614965991
I am happy to do more tests.
You are not logged in. Please login or register.
Redump Forum → General discussion → DiscImageCreator
nope https://drive.google.com/file/d/1h03hql … sp=sharing
Here is the disc for sale in Japan: https://www.ebay.com/itm/362614965991
I am happy to do more tests.
Here is the disc for sale in Japan: https://www.ebay.com/itm/362614965991
If tests are needed, I also have this disc.
Would you make ecc/edc checks be ignored on audio tracks, this should solve the false error problem.
Possible bug: a C2 error-filled disc eventually produced a Lead-in indicator somewhere in the middle of a field of errors. Don't know what could have triggered it or if it's reproducible at all, but logs and a screenshot are attached.
Logs: https://mega.nz/#!4JoF0aTZ!hQUyaIAzb9j4 … RzT5zVdxlA
disc eventually produced a Lead-in indicator
Uploaded http://www.mediafire.com/file/eq80y20l9 … st.7z/file
this should solve the false error problem.
I want to check these logs.
Here is the disc
I'm going to get it from an auction.
I'll post logs next time I run into that.
I made some tests with the enhanced CD.
I don't have the same errors as user7.
See logs: ENHANCED_CD-logs.rar
With 4012A drive:
DIC 20200203:
Uncomplete dump as it hangs.
The disc is clean, but a lot of c2 errors reported.
=================================================================================
[a lot of c2 errors before that]
...
Creating .scm (LBA) 22179/127337 LBA[022180, 0x056a4] Detected C2 error 8 bit
Creating .scm (LBA) 22484/127337 LBA[022485, 0x057d5] Detected C2 error 6 bit
Creating .scm (LBA) 23827/127337 LBA[023828, 0x05d14] Detected C2 error 12 bit
Creating .scm (LBA) 26172/127337 LBA[026173, 0x0663d] Detected C2 error 15 bit
Creating .scm (LBA) 30167/127337 End of readable sector
Sleep 20000 msec
LBA[035710, 0x08b7e] Detected C2 error 328 bit
LBA[035711, 0x08b7f]: [F:ProcessReadCD][L:280]
Opcode: 0xbe
ScsiStatus: 0x02 = CHECK_CONDITION
SenseData Key-Asc-Ascq: 06-29-00 = UNIT_ATTENTION - POWER ON, RESET, OR
BUS DEVICE RESET OCCURRED
Please wait for 40000 milliseconds until the device is returned
Creating .scm (LBA) 35711/127337
=================================================================================
And then it hangs forever.
It also hangs for some times on 7669/127337 (30 sec approx) and 7670/127337 (1-2 min), but continues, and no c2 error reported on these sectors.
DIC 20200209:
Complete dump but with too many c2 errors. Only 100 retries set, as it was a test to see if I will have the same error as user7.
I think most of them are not real errors, but I let you see if your disc will have the same patterns, sarami.
The disc is clean, but a lot of c2 errors reported.
=================================================================================
[a lot of c2 errors before that]
...
Creating .scm (LBA) 19009/127337 LBA[019010, 0x04a42] Detected C2 error 8 bit
Creating .scm (LBA) 19635/127337 LBA[019636, 0x04cb4] Detected C2 error 10 bit
Creating .scm (LBA) 19796/127337 LBA[019797, 0x04d55] Detected C2 error 7 bit
Creating .scm (LBA) 19996/127337 LBA[019997, 0x04e1d] Detected C2 error 8 bit
Creating .scm (LBA) 20978/127337 LBA[020979, 0x051f3] Detected C2 error 5 bit
Creating .scm (LBA) 22179/127337 LBA[022180, 0x056a4] Detected C2 error 12 bit
Creating .scm (LBA) 22798/127337 LBA[022799, 0x0590f] Detected C2 error 6 bit
Creating .scm (LBA) 23827/127337 LBA[023828, 0x05d14] Detected C2 error 12 bit
Creating .scm (LBA) 26172/127337 LBA[026173, 0x0663d] Detected C2 error 8 bit
Creating .scm (LBA) 26213/127337 LBA[026214, 0x06666] Detected C2 error 8 bit
Creating .scm (LBA) 31209/127337 Lead-out length of 1st session: 6750
Creating .scm (LBA) 31214/127337 End of readable sector
LBA[035711, 0x08b7f]: [F:ProcessReadCD][L:280]
Opcode: 0xbe
ScsiStatus: 0x02 = CHECK_CONDITION
SenseData Key-Asc-Ascq: 06-29-00 = UNIT_ATTENTION - POWER ON, RESET, OR
BUS DEVICE RESET OCCURRED
Please wait for 40000 milliseconds until the device is returned
Creating .scm (LBA) 35859/127337 Pregap length of 1st track of 2nd session: 358
60
Creating .scm (LBA) 127337/127337
Need to reread sector: 1 rereading times: 100/ 100
bad all. need to reread more
=================================================================================
It hangs for some times at 31209 > 31214 with a lot of noise from the lens.
As you see, the "End of readable sector" comes at 31214 (with test version 20200209) when it comes at 30167 (with DIC 20200203)
No more c2 error after 35860.
It also hangs for some times on 7669/127337 (30 sec approx) and 7670/127337 (1-2 min), but continues, and no c2 error reported on these sectors.
[same behavior as DIC 20200203]
With 716SA:
I stopped the dump, it was a test to see if there are also a lot of c2 errors. I added the partial logs to the file, just in case.
Hello. I've been using DIC to rip a number of old DOS and Windows games under Linux. I ran into a problem ripping one particular game - MegaRace. I can rip a copy with multiple other utilities from multiple drives with no error, but DIC always reports "[ERROR] Number of sector(s) where user data doesn't match the expected ECC/EDC: 2". No C2 errors reported, just that 2 errors described, regardless of how many times I try cleaning and resurfacing the disc.
Someone on Discord stated it's because of the large offset on the disk (1101 samples) and likely a bug in DIC. He suggested I report the issue here. The logs can be found here:
https://www.legroom.net/public/megarace.txz
Please let me know if any additional info is needed, or if I can do anything to help test.
Thanks.
Someone on Discord stated it's because of the large offset on the disk (1101 samples)
http://forum.redump.org/post/72760/#p72760
Complete dump but with too many c2 errors.
I also got this disc and a few of c2 errors occurred. c2 errors are the disc's problem, not dic.
Sarami,
Can you take a look at this dump.
http://forum.redump.org/topic/26627/fmt … nd-sarami/
LBA for some empty audio sectors is coming out as -150 tried a few recent DIC versions.
Hello,
I am dumping some games with my PX-708A, and if i use the /sf i get a error
[f:getfilename to fix error][l:171] getlasterror: 2
where F: is my drive, if i remove it, it works and i get a dump without any errors.
Am i missing a file?
I use an older version without the firmware check, because if i update my drive to anything above 1.04 it stops reading disk.
I've dowloaded your latest DIC build, and while trying to dump a PC game i obtain this error (taken from _mainError.txt)
nLBA 93, Directory Record is invalid
nLBA 178, Directory Record is invalid
and of course the copy is interrupting. What is happening here?
Updated test version. http://www.mediafire.com/file/eq80y20l9 … st.7z/file
@wiggy2k, @Lizard
Logs, please.
@Nextria
According to 5ch, it seems a lot of 708 users met with the same problem. So I changed it as 1.04 works.
Updated test version. http://www.mediafire.com/file/eq80y20l9 … st.7z/file
@wiggy2k, @Lizard
Logs, please.@Nextria
According to 5ch, it seems a lot of 708 users met with the same problem. So I changed it as 1.04 works.
Hey @sarami, thank you, i have been trying for hours to compile it
my self with visual studio 2019 only the get error upon error.
I tried the build but no i also get an error like Lizard
nLBA 20, Directory Record is invalid
nLBA 36, Directory Record is invalid
Updated test version. http://www.mediafire.com/file/eq80y20l9 … st.7z/file
@wiggy2k, @Lizard
Logs, please.
logs attached, similar problem:
nLBA 20, Directory Record is invalid
nLBA 100, Directory Record is invalid
nitro322 wrote:Someone on Discord stated it's because of the large offset on the disk (1101 samples)
0xF1 can support multiple sector overreads:
"F1 06 00 00 00 00 00 00 0b 00" = last read sector
"F1 06 00 00 0b 00 00 00 0b 00" = last read sector + 1
"F1 06 00 00 16 00 00 00 0b 00" = last read sector + 2
and so on.
Reuploaded http://www.mediafire.com/file/eq80y20l9 … st.7z/file
this fixed my problem. thanks!
Reuploaded http://www.mediafire.com/file/eq80y20l9 … st.7z/file
With me it’s also working !
Thank you !
Updated test version. http://www.mediafire.com/file/eq80y20l9 … st.7z/file
@wiggy2k, @Lizard
Logs, please.
looks good now, thank you
LBA[123395, 0x1e203], MSF[27:27:20], mode 1
LBA[123396, 0x1e204], MSF[27:27:21], mode 1 User data vs. ecc/edc doesn't match
LBA[123397, 0x1e205], MSF[00:00:00], zero sync
LBA[123398, 0x1e206], MSF[00:00:00], zero sync
LBA[123399, 0x1e207], audio
LBA[123400, 0x1e208], audio
New logs: https://mega.nz/#!2tdCnYIR!cRZvRGcKhkHV … ASF4uMfg0E
0xF1 can support multiple sector overreads:
"F1 06 00 00 00 00 00 00 0b 00" = last read sector
"F1 06 00 00 0b 00 00 00 0b 00" = last read sector + 1
"F1 06 00 00 16 00 00 00 0b 00" = last read sector + 2
and so on.
Then, how about the last read sector + 3, + 4, + 5 ...?
I tried "F1 06 00 00 21 00 00 00 0b 00", but it couldn't get the last read sector + 3.
+1764 is enough for 99.9% of discs if more won't work, there's only a few discs in db with larger offset.
I have read 30+ sectors into the lead out with 0xF1, not sure why you can't unless the lead out on your disc doesn't contain many sectors.
I have read 30+ sectors into the lead out with 0xF1, not sure why you can't unless the lead out on your disc doesn't contain many sectors.
30 would be +17640 ?
What insane discs are you dumping?
I have read 30+ sectors into the lead out with 0xF1, not sure why you can't unless the lead out on your disc doesn't contain many sectors.
Would you upload your code that can read 30+ sectors and upload the 30+ sectors?
Redump Forum → General discussion → DiscImageCreator
Powered by PunBB 1.4.4, supported by Informer Technologies, Inc.
Currently installed 6 official extensions. Copyright © 2003–2009 PunBB.