1,101

(3 replies, posted in General discussion)

MrX_Cuci, can you notify me if it has been resolved please, i want to finish this topic off.

1,102

(3 replies, posted in General discussion)

tossEAC wrote:

do you want me to make a list of all the XGD3 dumps and then note the database ID, and just keep the list handy so if or when I manage to dump  the ss.bin I can then make sure it ends up with the correct dump, if so that wont be a problem.

Yes smile

1,103

(3 replies, posted in General discussion)

You can do that, no problem.

The only thing i would like to ask you, is, to make notes of database ID to your discs, so that you can't mistake stuff later.

1,104

(3,536 replies, posted in General discussion)

The one from hard drive external enclosure, i don't have the exact name as i don't have it anymore, just the adapter.

Board is named: HD338-U2-AT2 ver 2.0

Edit:
One of those SanMax HD338 enclosures http://www.microlight.com.tw/pr0484.htm
http://forums.techguy.org/attachments/71304d1136817227/hd-338.jpg

1,105

(3,536 replies, posted in General discussion)

iR0b0t wrote:
Creating img (LBA)   2129/327442

Beginning from LBA 2120 it does not show any reading status messages and is only updating LBA numbers++
"Creating img (LBA)   2129/327442"

Just a note: the same thing happens on SafeDisc when using 0xBE parameter, and sector IDs are also repeated after that!!!

1,106

(3,536 replies, posted in General discussion)

Creating img (LBA)   2103/327442[F:ProcessReadCD][L:210] OperationCode: 0xd8
ScsiStatus: 02, CHECK_CONDITION
SenseData Key-Asc-Ascq: 03-02-8d, MEDIUM_ERROR - OTHER
Creating img (LBA)   2104/327442[F:ProcessReadCD][L:192] OperationCode: 0xd8
ScsiStatus: 02, CHECK_CONDITION
SenseData Key-Asc-Ascq: 03-02-8d, MEDIUM_ERROR - OTHER
LBA[002106, 0x0083a] Read error. padding 0x55 [2336byte]
Creating img (LBA)   2105/327442[F:ProcessReadCD][L:192] OperationCode: 0xd8
ScsiStatus: 02, CHECK_CONDITION
SenseData Key-Asc-Ascq: 03-02-8d, MEDIUM_ERROR - OTHER
LBA[002107, 0x0083b] Read error. padding 0x55 [2336byte]
Creating img (LBA)   2106/327442[F:ProcessReadCD][L:192] OperationCode: 0xd8
ScsiStatus: 02, CHECK_CONDITION
SenseData Key-Asc-Ascq: 03-02-8d, MEDIUM_ERROR - OTHER
LBA[002108, 0x0083c] Read error. padding 0x55 [2336byte]
Creating img (LBA)   2107/327442[F:ProcessReadCD][L:192] OperationCode: 0xd8
ScsiStatus: 02, CHECK_CONDITION
SenseData Key-Asc-Ascq: 03-02-8d, MEDIUM_ERROR - OTHER
LBA[002109, 0x0083d] Read error. padding 0x55 [2336byte]
Creating img (LBA)   2108/327442[F:ProcessReadCD][L:192] OperationCode: 0xd8
ScsiStatus: 02, CHECK_CONDITION
SenseData Key-Asc-Ascq: 03-02-8d, MEDIUM_ERROR - OTHER
LBA[002110, 0x0083e] Read error. padding 0x55 [2336byte]
Creating img (LBA)   2109/327442[F:ProcessReadCD][L:192] OperationCode: 0xd8
ScsiStatus: 02, CHECK_CONDITION
SenseData Key-Asc-Ascq: 03-02-8d, MEDIUM_ERROR - OTHER
LBA[002111, 0x0083f] Read error. padding 0x55 [2336byte]
Creating img (LBA)   2110/327442[F:ProcessReadCD][L:192] OperationCode: 0xd8
ScsiStatus: 02, CHECK_CONDITION
SenseData Key-Asc-Ascq: 03-02-8d, MEDIUM_ERROR - OTHER
LBA[002112, 0x00840] Read error. padding 0x55 [2336byte]
Creating img (LBA)   2111/327442[F:ProcessReadCD][L:192] OperationCode: 0xd8
ScsiStatus: 02, CHECK_CONDITION
SenseData Key-Asc-Ascq: 03-02-8d, MEDIUM_ERROR - OTHER
LBA[002113, 0x00841] Read error. padding 0x55 [2336byte]
Creating img (LBA)   2112/327442[F:ProcessReadCD][L:192] OperationCode: 0xd8
ScsiStatus: 02, CHECK_CONDITION
SenseData Key-Asc-Ascq: 03-02-8d, MEDIUM_ERROR - OTHER
LBA[002114, 0x00842] Read error. padding 0x55 [2336byte]
Creating img (LBA)   2113/327442[F:ProcessReadCD][L:192] OperationCode: 0xd8
ScsiStatus: 02, CHECK_CONDITION
SenseData Key-Asc-Ascq: 03-02-8d, MEDIUM_ERROR - OTHER
LBA[002115, 0x00843] Read error. padding 0x55 [2336byte]
Creating img (LBA)   2114/327442[F:ProcessReadCD][L:192] OperationCode: 0xd8
ScsiStatus: 02, CHECK_CONDITION
SenseData Key-Asc-Ascq: 03-02-8d, MEDIUM_ERROR - OTHER
LBA[002116, 0x00844] Read error. padding 0x55 [2336byte]
Creating img (LBA)   2115/327442[F:ProcessReadCD][L:192] OperationCode: 0xd8
ScsiStatus: 02, CHECK_CONDITION
SenseData Key-Asc-Ascq: 03-02-8d, MEDIUM_ERROR - OTHER
LBA[002117, 0x00845] Read error. padding 0x55 [2336byte]
Creating img (LBA)   2116/327442[F:ProcessReadCD][L:192] OperationCode: 0xd8
ScsiStatus: 02, CHECK_CONDITION
SenseData Key-Asc-Ascq: 03-02-8d, MEDIUM_ERROR - OTHER
LBA[002118, 0x00846] Read error. padding 0x55 [2336byte]
Creating img (LBA)   2117/327442[F:ProcessReadCD][L:192] OperationCode: 0xd8
ScsiStatus: 02, CHECK_CONDITION
SenseData Key-Asc-Ascq: 03-02-8d, MEDIUM_ERROR - OTHER
LBA[002119, 0x00847] Read error. padding 0x55 [2336byte]
Creating img (LBA)   2118/327442[F:ProcessReadCD][L:192] OperationCode: 0xd8
ScsiStatus: 02, CHECK_CONDITION
SenseData Key-Asc-Ascq: 03-02-8d, MEDIUM_ERROR - OTHER
LBA[002120, 0x00848] Read error. padding 0x55 [2336byte]
Creating img (LBA)   2119/327442[F:ProcessReadCD][L:192] OperationCode: 0xd8
ScsiStatus: 02, CHECK_CONDITION
SenseData Key-Asc-Ascq: 03-02-8d, MEDIUM_ERROR - OTHER
LBA[002121, 0x00849] Read error. padding 0x55 [2336byte]
Creating img (LBA)   2129/327442

Beginning from LBA 2120 it does not show any reading status messages and is only updating LBA numbers++
"Creating img (LBA)   2129/327442"



Besides of this, what can cause LBA number being shifted by 2 ?
Creating img (LBA)   2119/327442[F:ProcessReadCD][L:192] OperationCode: 0xd8
LBA[002121, 0x00849] Read error. padding 0x55 [2336byte]

1,107

(3,536 replies, posted in General discussion)

Here are your requested logs, sarami.

1,108

(3 replies, posted in General discussion)

I have tried to download and decompress it right after uploading and it worked.
But i packed it as a solid archive and maybe it does not work with newer versions.

Please try to decompress this > http://redump.org/download/ss_sector_range_1.0e.rar > if it works for you?

You don't have to use WinRAR for decompression, any other tool supporting rar archives (like 7z manager or similar) should do that too.

1,109

(4 replies, posted in General discussion)

There is NO need for other stuff !

sarami did a great work, and is constantly updating his tool.

DIC is the only tool you will need for dumping CD-based discs,
and of course "subdump" for subchannel dumping, if you want to have it dumped too, which is advisable.

1,110

(3,536 replies, posted in General discussion)

sarami, there still is issue with sector IDs

1,111

(3,536 replies, posted in General discussion)

sarami wrote:

I have thought that those error sector should be replaced at 0x55.
If you right, it's difficult for me to recognize whether it is an error sector...

I have investigated into this and found out that there are repeated sector IDs.
All 12 sector groups of:

Number of sector(s) where user data doesn't match the expected ECC/EDC: 12
    Sector: 2105, 2405, 2778, 3155, 3455, 3754, 4054, 4427, 4803, 5178, 5479, 6230, 
Number of sector(s) where reserved byte doesn't zero: 12
    Sector: 2196, 2496, 2872, 3246, 3546, 3845, 4148, 4522, 4899, 5273, 5570, 6322, 

2105-2196
2405-2496
...
have the same pattern.
They begin with an incomplete sector (due to combined offset of +18 in this case),
the next sector has a repeated sector ID, i will make an example of the first group:
2105-2196
Sector 2105 has a correct header ID.
Sector 2106 has a repeated sector ID from sector 2105.
Sector 2107 has a repeated sector ID from sector 2106.
...
Sector 2121 has a repeated sector ID from sector 2120.
Beginning by sector 2121 and ending at sector 2196 all sectors have a repeated sector ID from sector 2120.
The last sector of this group = 2196 is not completelly replaced by 0x55.
From next sector 2197 there is everything fine again until the next group.

I am not sure if that even will work out to get equal hashes after replacing the whole incomplete sectors with 0x55 and on different drives with large positive or negative read offset numbers.

1,112

(3,536 replies, posted in General discussion)

Number of sector(s) where user data doesn't match the expected ECC/EDC: 12
    Sector: 2105, 2405, 2778, 3155, 3455, 3754, 4054, 4427, 4803, 5178, 5479, 6230, 
Number of sector(s) where reserved byte doesn't zero: 12
    Sector: 2196, 2496, 2872, 3246, 3546, 3845, 4148, 4522, 4899, 5273, 5570, 6322, 
All unmatch sector replace 0x55 except header

sarami, back then, when i dumped a LaserLock disc with /rc parameter, those sectors listed above were also replaced by '55'.
I used to dump it with the following release:

        Windows 7 Home Premium Service Pack 1 32bit
AppVersion
        x86, AnsiBuild, Jun 14 2015 17:40:27

Did you by the chance fix that in the meanwhile?
Those sectors should not have been replaced i think.
I don't want to dump it again just yet, because this disc took me 11 hours to dump.

You can identify laserlock discs by a file called "LASERLOK.IN", but i think you already have it set.

Below is a full dumping log if you need it:

1,113

(4 replies, posted in News)

Yes, i noticed that too, some days ago smile
Still, i won't update it just now to make sure there are no bugs, and update it later. There is no time pressure.

1,114

(0 replies, posted in News)

Guys, please use the newest version of ss_sector_range: 1.0e.
It will release a second security sector ranges on xbox360 ss.bin, which we would like to preserve as well.
Download link is available in the guide.

I think that Steam DRM can be considered as physical protection because it requires an input which is not hard coded into a disc and is not made available within a package, not like serials for example.

One media which "cannot" be run without an other media.

1,116

(3,536 replies, posted in General discussion)

sarami, it should be okay now for SafeDisc 3.15.XXX

My disc does return 1 error more, but its due to a scratch.

I do believe this issue is fixed now, thanks for that.

1,117

(3,536 replies, posted in General discussion)

sarami, it worked now :thumbs up:

There is another SafeDisc game which doesn't work as expected, i guess it will be the same for all SafeDisc 3.15.XXX

Log files attached:

As you can see there are extra 68 sectors which are getting replaced, they are out of safedisc ranges and should probably not be replaced.

I used to dump this game with previous test version, not the latest one you just uploaded yesterday.

1,118

(6 replies, posted in General discussion)

Text is in priority, i think.

1,119

(6 replies, posted in General discussion)

Language selector is only available for a few consoles (incl. PS2) when you boot up the game, and comes if available at all befor the main game screen.

By "options menu main" I meant if there is no selectable split between speech and text.

1,120

(6 replies, posted in General discussion)

Listing all options would be the best thing, i guess.

Bios: lang1,2,...
Selector: lang1,2,...
Options menu (main): lang1,2,...
Options menu (text): lang1,2,...
Options menu (speech): lang1,2,...

And so on...

1,121

(3,536 replies, posted in General discussion)

By the way sarami, one of my SafeDisc 1.35.000 games crashes on DIC if used /rc parameter.

Console output:

OS
        Windows 7 Home Premium Service Pack 1 32bit
AppVersion
        x86, AnsiBuild, Jun 14 2015 17:40:27
/rc val is omitted. set [60]
CurrentDir
        C:\Users\user\Desktop\folder
InputPath
         path: dic_PX-760A
        drive:
          dir:
        fname: dic_PX-760A
          ext:
Start: 2015-07-05(Sun) 12:10:57
Checking reading lead-out
Read command: 0xd8, Subcode reading mode: Pack
Creating bin from 335414 to 335414 (LBA) 335414
Reading lead-out: OK
[F:ReadCDForVolumeDescriptor][L:880] GetLastError: 8, F³r diesen Befehl ist nich
t gen³gend Speicher verf³gbar.

Log files below:

1,122

(3,536 replies, posted in General discussion)

sarami wrote:
iR0b0t wrote:

CodeLock   http://redump.org/discs/quicksearch/cod … ction/only
and other discs which use intentional c2 errors in combination with any other protections.
You could set this custom command in priority to EccEdc, which is "/rc" i think.

I don't have these protect disc. plz wait.

The range which is protected has no allocated file, just to let you know, sarami.

1,123

(3,536 replies, posted in General discussion)

Jackal wrote:

But the CD.idx file is oversized so I don't know if that will work.

The first allocated sector of this file should be known and if there is for any reason a faked file end sector it can be calculated = next allocated file/folder start sector - 1. It should work.

1,124

(3,536 replies, posted in General discussion)

CodeLock   http://redump.org/discs/quicksearch/cod … ction/only

and other discs which use intentional c2 errors in combination with any other protections.

You could set this custom command in priority to EccEdc, which is "/rc" i think.

1,125

(3,536 replies, posted in General discussion)

sarami, any chance you can add command line support for replacing ALL sectors with C2 errors by '55' pattern?