Seems to only be Halo 2 so far
Is the error message displayed in a command-line screen?
You are not logged in. Please login or register.
Redump Forum → Posts by sarami
Seems to only be Halo 2 so far
Is the error message displayed in a command-line screen?
I always say.
Attention
1. Before you report a bug, could you try the latest test version http://www.mediafire.com/file/eq80y20l9 … r_test.7z.
Sorry, fixed it.
Updated test branch and test build http://www.mediafire.com/file/eq80y20l9 … st.7z/file
*2018-08-12
- added: xboxswap, xgd2swap, xgd3swap command
- added: Reading param.sfo
- added: makefile for linux (Thanks bparker)
- improved: Reading sub-channel (create QGenSector from QNextSector - 1 and QPrevSector + 1)
- fixed: _splitpath for linux (added null checking)
How to use of xboxswap, xgd2swap, xgd3swap (Thanks F1ReB4LL)
### Dumping Guide for XBOX/XBOX360 (XGD2)/XBOX360 (XGD3) on genaral drive
Prepare DVD-DL or create the DVD+R DL trap disc in advance.
#### How to prepare
You need a pressed DVD-DL disc with around 8.5GB data on it
XBOX: Layerbreak larger than 1913776 and the exact size needed (in sectors) is (your_disc_layerbreak - 1913776) * 2 + 3820880
XBOX360 (XGD2): Layerbreak larger than 1913760 and the exact size needed (in sectors) is (your_disc_layerbreak - 1913760) * 2 + 3825924
XBOX360 (XGD3): Layerbreak larger than 2133520 and the exact size needed (in sectors) is (your_disc_layerbreak - 2133520) * 2 + 4267015
#### How to create
XBOX: DVD (Length is 3820880 or larger, Layerbreak is 1913776 or larger)
XBOX360 (XGD2): DVD (Length is 3825924 or larger, Layerbreak is 1913760 or larger)
XBOX360 (XGD3): DVD (Length is 4267015 or larger, Layerbreak is 2133520 or larger)
1. Create image file of the above DVD using dumping tool (e.g. isobuster)
2. Run [ImgBurn](http://www.imgburn.com/)
3. Setting LayerBreak manually (L0 sector num is about a half size of DVD length)
e.g. If DVD length is 3900304, L0 sector num is about 1950160
4. Before burn the image file, you need to confirm the size is correct
e.g. (1950160 - 1913776) * 2 + 3820880 = 3893648 => 3893648 is smaller than 3900304, so the DVD+R DL this image is burnt can dump a XBOX disc
5. Burn image file to DVD+R DL
#### Dump the disc
1. Insert the DVD-DL or DVD+R DL trap disc to a general DVD drive.
2. Run below. (stop spinning disc)
DiscImageCreator.exe stop [DriveLetter]
3. Use a pin to press the escape eject button, so the tray will eject (or remove
the drive cover).
4. Insert the XBOX disc and run below. (close the drive tray)
DiscImageCreator.exe close [DriveLetter]
(or gently push the tray back or put the drive cover back on).
5. Run below.
e.g. Dead or Alive 3 http://redump.org/disc/27157/
DiscImageCreator.exe xboxswap [DriveLetter] foo.iso 292756 467910 686060 830074 999794 1212958 1579164 1719138 2010470 2372562 2527492 2682830 2915560 3065604 3219138 3455656
e.g. Blue Dragon http://redump.org/disc/27088/
DiscImageCreator.exe xgd2swap [DriveLetter] foo.iso 3825631 108976 3719856
e.g. Battlefield 3 (Disc 1) (Multiplayer/Co-Op) http://redump.org/disc/35131/
DiscImageCreator.exe xgd3swap [DriveLetter] foo.iso 4267015 12544 4246304
And if I build with ASAN enabled
I've not fixed yet.
http://forum.redump.org/post/62037/#p62037
I built it on WSL (Windows Subsystem for Linux) using ubuntu 18.04 LTS x64.
No makefile. If you want it, please make it yourself.
>andoryuu3
Only Halo2? or all xbox disc you have? or all DVD you have?
And please read 1st post. http://forum.redump.org/post/37654/#p37654
Attention
1. Before you report a bug, could you try the latest test version http://www.mediafire.com/file/eq80y20l9 … r_test.7z.
Nevertheless a bug exists, could you upload all created file except bin, iso, img and scm.
What is random padding?
Long vowels problem, it's difficult...
"Ou/Oo" is a native Japanese word? Or should it be treated as a borrowed word "Oh"?
http://www.pref.aichi.jp/soshiki/kenmin … 03567.html
Ou/Oo/Oh is all used in person's/character's name. If おーちゃん indicates おおちゃん, it should be Oo-chan or Oh-chan. If おーちゃん indicates おうちゃん, it should be Ou-chan or Oh-chan.
http://redump.org/discs/quicksearch/ボボボーボ/ -- these are "Boboboobo Boobobo", then?
http://redump.org/disc/42653/ -- and this one? Choukou Senki Kikaioo?
Same.
おー = oo http://redump.org/disc/28872/
イー = ii http://redump.org/disc/39860/
ゲー = Gee http://redump.org/disc/48795/
ケー = Kee http://redump.org/disc/46965/
http://redump.org/disc/24802/ -- Doubutsu Banchoo?
These aren't person's/character's name.
Why Japanese uses Katakana, though some words (ドーブツ, ケータイ) can represent by Kanji?
https://repository.kulib.kyoto-u.ac.jp/ … akiuti.pdf
Up http://www.mediafire.com/file/eq80y20l9 … r_test.7z.
> create QGenSector1 from QNextSector - 1
> create QGenSector2 from QPrevSector + 1
added.
Others haven't added yet.
maybe ISO Buster just keeps making the same mistakes and so the result is the same hashes...
How about other tool except DIC and IsoBuster?
1-bit errors are fixed automatically
if (these sectors have 1-bit error) {
QCurrentSector = QGenSector
}
Who fixes the 1-bit error of QCurrentSector? Isn't it fixed by changing each bit to opposite?
I can't understand how to use the FixLevel/[FixLevel] bits.
Like this?
if (Q-CRC of QCurrentSector is bad) {
create QGenSector from QNextSector - 1
compare 96bits of QCurrentSector and QGenSector
if (these sectors have 1-bit error) {
try to change each bit to opposite (Max 96 times?)
}
else if (these sectors have 2 or more bit errors) {
reread sector (*1)
}
}
Question
(*1). How many times subdump reread the sector? If it can't get the good Q-CRC, is the sector written to file with being bad?
Uploaded test version. http://www.mediafire.com/file/eq80y20l9 … r_test.7z.
added: Output PARAM.SFO into _disc.txt -> I only checked PS3 discs.
Official Kiosk discs are BD-Rs
Firstly, I want to know whether or not general BD-Rs output different checksums and sizes. (I can't test it because I don't have BD-R drive.)
Back to dumping PS4 official kiosk discs, which are on BD-Rs, different hashes and iso sizes are returned every dump.
I dumped with ISO Buster twice, different checksums and different sizes both times, discs are in flawless condition.
I have no idea about this problem now. Is the other general BD-Rs same result, not PS4 official kiosk discs?
added: Output PARAM.SFO into _disc.txt
https://github.com/saramibreak/UmdImageCreator/releases
At least, nulldc and reicast-emulator doesn't support the multi-bin of gdi. You can use the single-bin of gdi if you want to check the language.
Hi @sarami, could you push your current code with the linux support to github so I can take a look at some of the issues? Thanks!
Uploaded in test branch.
4.1. If Q-CRC of QCurrentSector doesn't match: QGenSector = QNextSector - 1 frame (MSF - 1, AMSF - 1, fix Q-CRC).
4.2. You do a binary compare (96 bits vs 96 bits) between QCurrentSector and QGenSector and count a number of bits that differ. If their count is <= FixLevel: QCurrentSector = QGenSector and go to p.5.
1. What FixLevel? Default of subdump is 96?
2. If QNextSector is 1st pregap sector, Is QGenSector really correct?
3. If QCurrentSector is track 1 and QNextSector is track 2, is QGenSector really correct?
4. If QCurrentSector is index 1 and QNextSector is index 2, is QGenSector really correct?
5. If QCurrentSector is ctl 0 and QNextSector is ctl 4, is QGenSector really correct?
4.3. If QEAN != null, you do a binary compare between QCurrentSector and QEAN and count a number of bits that differ. If their count is <= FixLevel: QCurrentSector = QEAN and go to p.5.
4.4. If QISRC != null, you do a binary compare between QCurrentSector and QISRC and count a number bits that differ. If their count is <= FixLevel: QCurrentSector = QISRC and go to p.5.
6. If adr of QCurrentSector is 1 but actually QCurrentSector is EAN sector, is the adr really fixed?
7. If adr of QCurrentSector is 3 but actually QCurrentSector is EAN sector, is the adr really fixed?
8. If adr of QCurrentSector is 2 but actually QCurrentSector is ISRC sector, is the adr really fixed?
9. If adr of QCurrentSector is 2 but actually QCurrentSector is normal sector, is the adr really fixed?
10. Does this algo support all SecuROM (at least 4 patterns) and Libcrypt?
one suffixed "(Subs indexes)"
It failed to get the correct subchannel. This suffix is only used by pce disc (1988 - 1989?).
I'll fix subchannel reading and don't output the suffix except pce.
DCDumper and CDTool to produce output tracks with identical checksums.
Your disc is 'light' damaged disc, and these tools run multiple reading by default to get the identical checksums. So, checksums match (by chance) but it is short of reliability.
If your disc is 'heavy' damaged disc, DCDumper and CDTool probably can't dump it because such disc possibly outputs identical bad checksums.
Xbox is same status as before
Please upload the log and tried windows build. I tried xbox/xbox360 dump and confirmed that it matched as the hash of db.
If the hash of linux build and windows build matched, please try freecell and/or XBC and compare which sectors differ.
I've dumped the game disc four times so far
Perhaps, your disc has c2 errors.
Lastly a general bug I found.
Uploaded.
Some updated. (added css authentication, scsi status)
----
PS2 games for DVD dumps
Invalid disc structure is outputted.
========== DiscStructure ==========
FormatCode: 00, Sendable: No, Readable: No, FormatLength: 0
Skiped because length is 0
FormatCode: 2a, Sendable: No, Readable: No, FormatLength: 7959
Unknown: 2a
FormatCode: f3, Sendable: No, Readable: Yes, FormatLength: 10531
Unknown: f3
:
:
How about other DVD except PS2? and how about other PS2 DVD?
SS.bin file will get dumped into the directory above where you specified.
Fixed.
Lastly a general bug I found.
What do you hope about this case?
sudo ./DiscImageCreator_linux.out xbox Halo_2.iso
/Halo_2.iso or /home/user/DIC/Halo_2.iso ?
sudo ./DiscImageCreator_linux.out xbox /Halo_2.iso
/Halo_2.iso or /home/user/DIC/Halo_2.iso ?
sudo ./DiscImageCreator_linux.out xbox Halo_2/Halo_2.iso
/Halo_2/Halo_2.iso or /home/user/DIC/Halo_2/Halo_2.iso ?
sudo ./DiscImageCreator_linux.out xbox /Halo_2/Halo_2.iso
/Halo_2/Halo_2.iso or /home/user/DIC/Halo_2/Halo_2.iso ?
----
the windows version of rhash
Perhaps, I think the algo of rhash is faster than that of RFC 1321, 1952, 3174.
some of the issues
What issues in detail?
Fixed ss sector ranges of xbox/xbox360.
I confirmed cd command and it seems working.
when the dump was finished they did not complete the hash check.
Windows build uses xmllite but there isn't it in linux, so it hasn't been supported yet.
EDIT
added: EccEdc_linux.out
http://www.mediafire.com/file/uw3e03kdk … t.tar/file
I confirmed only dvd command using knoppix 8.2 x64
Does your tool dump these properly? http://redump.org/discs/system/psp/status/3/
Perhaps yes. I think these dumps are good because there isn't a gap between GAME and VIDEO.
also, does your tool dump the same way as PSP Filer
I tested some discs by PSP Filer and my tool, and comfirmed same hash is outputted.
But problem is UMD VIDEO disc, not GAME VIDEO hybrid disc.
----
ACUM-34031 (Final Fantasy VII - Advent Children)
Log on GAME
pspUmdTypes: 0x60 (VIDEO AUDIO)
L0 length: 21504 (0x05400)
0x01F20014 is unknown: 05 80 00 32
0x01F200A0 is unknown: 01
Log on XMB
pspUmdTypes: 0x60 (VIDEO AUDIO)
L0 length: 421056 (0x66cc0)
L1 length: 264112 (0x407b0)
-----------------
Total: 685168 (0xa7470)
0x01F20014 is unknown: 05 80 00 32
0x01F200A0 is unknown: 01
21504 + 421056 = 442560 (layerbreak)
But as you know, UMD VIDEO can't dump on GAME. So, 21504 sectors are undumpable.
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.