bikerspade wrote:
Ok, it was fixed as I expected.
102 2022-12-20 04:41:22
Re: DiscImageCreator (3,521 replies, posted in General discussion)
bikerspade wrote:
That fixed the problem with this disc. Thank you!
Do you upload logs if possible? I want to see if it's fixed as I expected.
103 2022-12-17 10:45:34
Re: DiscImageCreator (3,521 replies, posted in General discussion)
bikerspade wrote:
LBA 10714 belongs to the track 2 but I think DIC takes it as a part of track 1
Uploaded test version.
https://www.mediafire.com/file/eq80y20l … st.7z/file
user7 wrote:
Can't help at all? Not in any circumstances?
I'm not sure because I don't have GD-R. Can dump GD-R without /be?
104 2022-12-15 14:38:54
Re: DiscImageCreator (3,521 replies, posted in General discussion)
user7 wrote:
Sarami, is there any downside to adding the "/be pack" command when dumping DC HD Area?
Due to "/be pack", _mainError.txt is so big size. This option is not need for Plextor.
105 2022-12-01 10:00:12
Re: DiscImageCreator (3,521 replies, posted in General discussion)
MrPepka wrote:
Sarami is it possible for DIC to properly dump DVDs that have data in two layers?
Perhaps, it's not possible due to the filesystem problem.
106 2022-11-18 07:42:34
Re: DiscImageCreator (3,521 replies, posted in General discussion)
MrPepka wrote:
when I do, DIC dumps the disk, and then hangs on the headquarters
"Rewrited img (LBA) 248676/299058"
And I don't know if I'm doing it right or wrong. This is how I set up this command
/c2 5000 1 248676 252396
Try to reduce the retry count from 5000 to 20 if the app really hangs.
107 2022-11-18 04:03:40
Re: DiscImageCreator (3,521 replies, posted in General discussion)
TonyLizard wrote:
all the dumps have 49 errors
It's weird. Your disc is no c2 and no mainError.
TonyLizard wrote:
Let me know if you need something more
Is there executable binary in disc 2? If there is not, it's difficult to find its protection.
108 2022-11-03 12:56:45
Re: DiscImageCreator (3,521 replies, posted in General discussion)
MrPepka wrote:
Sarami, would you look at one of my disks?
There are c2 errors. You need to get another disc or polish it.
109 2022-11-01 13:31:22
Re: DiscImageCreator (3,521 replies, posted in General discussion)
MrPepka wrote:
I cannot dump one disc, namely the CD from the "newspaper" (actually a cardboard) Kinderland Extra 4/2006. I have strange errors when trying to dump my disk
Sarami, would you look at this?
If it's not the protected disc, do not use /sf and /ns.
110 2022-10-22 02:35:55
Re: DiscImageCreator (3,521 replies, posted in General discussion)
NumberOfDIUnits are not Number of layers.
Number of layers of your disc is 1.
DIUnitFormatDependentContents
NumberOfLayers: 01
LayerType: 02 (Writable)
ChannelBit: 01 (74.5 nm)111 2022-10-21 17:39:40
Re: DiscImageCreator (3,521 replies, posted in General discussion)
Foxhack wrote:
I noticed that the _disc.txt file seems to have four times the information
NumberOfDIUnitsInEachDIBlock: 04Foxhack wrote:
I'm not sure where this information is being derived from
PIC.bin
112 2022-10-19 14:48:45
Re: DiscImageCreator (3,521 replies, posted in General discussion)
MrPepka wrote:
both are SafeDisc protected
I don't know the detail about the SafeDisc DVD.
user7 wrote:
the latest build is not dumping Xbox beta discs
The reason is unknown. Try to use 'dvd' command.
user7 wrote:
however IsoBuster is dumping them fine
Can IsoBuster dump the xbox disc? I didn't know it.
113 2022-08-24 01:58:58
Re: DiscImageCreator (3,521 replies, posted in General discussion)
ehw wrote:
Is there something we can do?
You can use /f flag. This is used to control "FlushDriveCache" function.
/f Use 'Force Unit Access' flag to delete the drive cache
val delete per specified value (default: 1)If you use "/f" (no value), app call "FlushDriveCache" per sector.
If you use "/f 1", app calls "FlushDriveCache" per sector.
If you use "/f 2", app calls "FlushDriveCache" per 2 sectors.
If you use "/f 3", app calls "FlushDriveCache" per 3 sectors.
:
:
If you use "/f 10000", app calls "FlushDriveCache" per 10000 sectors.
ehw wrote:
Couldn't DIC compensate by rereading sectors that spawn an error for sanity checks?
I'll consider it. But sync is corrupt for some protection and bad mastering discs. App can controls rereading when the protection flag (/sf /ns) is used, but it can't judge if the disc is bad mastering or not.
114 2022-08-21 09:46:23
Re: DiscImageCreator (3,521 replies, posted in General discussion)
user7 wrote:
see
Lizard wrote:
probably the dump is not correct.
I don't know why Lizard thinks of it.
115 2022-08-20 15:18:05
Re: DiscImageCreator (3,521 replies, posted in General discussion)
user7 wrote:
Interestingly, the hashes are different than those of the redumper app (logs for which are also present in this archive entry).
Mastering Code is different. Simply, it's another version? I'm not sure.
116 2022-08-12 13:41:26
Re: DiscImageCreator (3,521 replies, posted in General discussion)
bikerspade wrote:
If a track has an invalid ISRC code (example: "0@4010000000"), will that mean DiscImageCreator will not add it to the cuesheet?
Yes. I check it by the "IsValidSubQAdrISRC" function.
117 2022-08-11 12:52:50
Re: DiscImageCreator (3,521 replies, posted in General discussion)
bikerspade wrote:
If a track has an invalid ISRC code (example: "0@4010000000")
Does it means you have the weird disc? If yes, upload logs plz.
118 2022-08-09 01:13:21
Re: DiscImageCreator (3,521 replies, posted in General discussion)
bikerspade wrote:
perhaps it is hard-coded to always attempt no more than 5 retries?
119 2022-08-07 02:22:42
Re: DiscImageCreator (3,521 replies, posted in General discussion)
bikerspade wrote:
Should support for the /rr flag be added for dumping xbox and xbox 360 discs?
Added. Not test.
https://www.mediafire.com/file/eq80y20l … st.7z/file
120 2022-07-24 02:23:16
Re: DiscImageCreator (3,521 replies, posted in General discussion)
More changed.
https://www.mediafire.com/file/eq80y20l … st.7z/file
121 2022-07-23 13:22:55
Re: DiscImageCreator (3,521 replies, posted in General discussion)
Sorry, fixed typo.
https://www.mediafire.com/file/eq80y20l … st.7z/file
122 2022-07-23 10:58:43
Re: DiscImageCreator (3,521 replies, posted in General discussion)
Novicami wrote:
Fixed, thank you!
Thanks, but misdetection still exists.
LBA 357, Check if the directory record length (114) is really correct -> incorrect. Fixed it to 54
LBA 1690, Check if the directory record length (128) is really correct -> incorrect. Fixed it to 67
LBA 1142, Check if the directory record length (112) is really correct -> incorrect. Fixed it to 51
LBA 1369, Check if the directory record length (114) is really correct -> incorrect. Fixed it to 54
LBA 1480, Check if the directory record length (152) is really correct -> incorrect. Fixed it to 91
LBA 3352, Check if the directory record length (128) is really correct -> incorrect. Fixed it to 67
LBA 523, Check if the directory record length (102) is really correct -> incorrect. Fixed it to 41
LBA 2219, Check if the directory record length (132) is really correct -> incorrect. Fixed it to 71
More test please if possilble.
https://www.mediafire.com/file/eq80y20l … st.7z/file
123 2022-07-22 12:45:52
Re: DiscImageCreator (3,521 replies, posted in General discussion)
Novicami wrote:
It's a empty file
Test build
https://www.mediafire.com/file/eq80y20l … st.7z/file
124 2022-07-21 13:18:44
Re: DiscImageCreator (3,521 replies, posted in General discussion)
MrTikki wrote:
but rather than exporting all of the data dumps into a flat, text file...it seems like it would be more beneficial if the data were also exported in a supplemental CSV format. This way we could eventually use the CSV format to streamline disc uploads by auto-populating the data fields by uploading the CSV directly.
It's impossible to replace all of the data to the csv.
Novicami wrote:
New little problem with a Amiga stuff...
There is a irregular? record in LBA 910.
0140 : 76 00 00 00 00 00 00 00 ._....,.v.......
0150 : 00 00 00 00 00 00 00 00 00 00 5F 03 1E 11 12 2C .........._....,
0160 : 00 00 00 00 01 00 00 01 07 46 49 58 45 44 3B 31 .........FIXED;1
0170 : 52 52 05 01 89 4E 4D 0A 01 00 66 69 78 65 64 50 RR...NM...fixedP
0180 : 58 24 01 FF 81 00 00 00 00 81 FF 01 00 00 00 00 X$..............
0190 : 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
01A0 : 00 00 00 54 46 1A 01 0E 5F 03 1E 11 12 2C 00 5F ...TF..._....,._
01B0 : 03 1E 11 12 2C 00 5F 03 1E 11 12 2C 00 00What is the "FIXED"?
125 2022-07-10 03:06:39
Re: DiscImageCreator (3,521 replies, posted in General discussion)
Neon Beast wrote:
CD-TEXT not showing correctly, is this normal?
I tested it using same CD-TEXT data, and it's no problem. I'm not sure why the string is not showed correctly.
========== CDTEXT ==========
Entry 0 crc[0657] is good
Entry 1 crc[315e] is good
Entry 2 crc[7786] is good
Entry 3 crc[e163] is good
Entry 4 crc[9205] is good
Entry 5 crc[bc6b] is good
Entry 6 crc[bf6d] is good
Entry 7 crc[2729] is good
Entry 8 crc[3b44] is good
Entry 9 crc[23ae] is good
Entry 10 crc[4a86] is good
Entry 11 crc[d75d] is good
Entry 12 crc[828e] is good
Entry 13 crc[5537] is good
Entry 14 crc[9619] is good
Entry 15 crc[6544] is good
Entry 16 crc[db0b] is good
Entry 17 crc[94d5] is good
Entry 18 crc[a4af] is good
Entry 19 crc[d9d4] is good
Entry 20 crc[e416] is good
Entry 21 crc[6e59] is good
Entry 22 crc[c7ec] is good
Entry 23 crc[ffb4] is good
Entry 24 crc[c835] is good
Entry 25 crc[bf60] is good
Entry 26 crc[bace] is good
Entry 27 crc[a5a8] is good
Entry 28 crc[3176] is good
Entry 29 crc[bca4] is good
Album Name: 新しいタイトル (7)
Song Name[1]: トラック 01
Song Name[2]: トラック 02
Song Name[3]: トラック 03
Song Name[4]: トラック 04
Song Name[5]: トラック 05
Song Name[6]: トラック 06
Song Name[7]: トラック 07
Song Name[8]: トラック 08
Song Name[9]: トラック 09
Song Name[10]: トラック 10
Album Performer: 新しいアーティスト (7)
First track number: 1
Last track number: 10
Lead-out(msf): 44:04:61
Track 1(msf): 00:02:00
Track 2(msf): 04:15:27
Track 3(msf): 08:23:64
Track 4(msf): 12:50:19
Track 5(msf): 17:07:59
Track 6(msf): 21:30:44
Track 7(msf): 25:54:34
Track 8(msf): 30:08:20
Track 9(msf): 34:48:37
Track 10(msf): 39:36:00
Character code for this BLOCK: 0x00 (ISO/IEC 8859-1 [Latin-1])
First track Number: 1
Last track Number: 20
Mode2 PACKETs: No
Program area copy protection: No
Copyright asserted for $85: Yes
Copyright asserted for $81-$84: Yes
Copyright asserted for $80: Yes
Number of PACKS with $80 (ALBUM_NAME) : 17
Number of PACKS with $81 (PERFORMER) : 6
Number of PACKS with $82 (SONGWRITER) : 0
Number of PACKS with $83 (COMPOSER) : 0
Number of PACKS with $84 (ARRANGER) : 0
Number of PACKS with $85 (MESSAGES) : 0
Number of PACKS with $86 (DISC_ID) : 0
Number of PACKS with $87 (GENRE) : 0
Number of PACKS with $88 (TOC_INFO) : 4
Number of PACKS with $89 (TOC_INFO2) : 0
Number of PACKS with $8a : 0
Number of PACKS with $8b : 0
Number of PACKS with $8c : 0
Number of PACKS with $8d (CLOSED_INFO): 0
Number of PACKS with $8e (UPC_EAN) : 0
Number of PACKS with $8f (SIZE_INFO) : 3
Last Sequence number of BLOCK 0: 29
Last Sequence number of BLOCK 1: 0
Last Sequence number of BLOCK 2: 0
Last Sequence number of BLOCK 3: 0
Last Sequence number of BLOCK 4: 0
Last Sequence number of BLOCK 5: 0
Last Sequence number of BLOCK 6: 0
Last Sequence number of BLOCK 7: 0
Language code BLOCK 0: 0x69 (Japanese)
Language code BLOCK 1: 0x00 (not applicable)
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)