redump.info Forum

user7 wrote:>Preservation enthusiasts will do the needed dumps sooner or later, but there should be a proper software for that.

Ha. HAHAHAHAHAHA!!

Not everyone wants to waste time and cash for pointless, unverifiable sectors.

There are yellow Xbox 360 dumps that nobody cares to fix, and many Xbox NTSC discs that nobody wants to buy - https://wiki.redump.info/index.php?title= … sing_Dumps (because the PAL discs are already dumped). So, don't expect anyone to to buy and redump 4.000 discs, even if it's confirmed that the missing data can be dumped/verified.

As I've said, there should be a mechanism to dump and add the discs properly for those who want it so. Nobody says about marking the existing ones as bad.

I tend to be in the camp of "scan everything with an electron microscope and simulate lasers", but honestly there is a point where a decision has to be made.

Now, it's important to be _sure_ there isn't any useful data, even just silly intentional data, in that space… but from what I've learnt reading around, it would seem that its genuinely "useless" and unused. As long as the beginning and end of these sectors are well known are documented, I see no harm with the current method which ignores those bits.

emuLOAD wrote:As long as the beginning and end of these sectors are well known are documented, I see no harm with the current method which ignores those bits.

If these sectors are somehow generatable, then, yes (and even then it's better not to ignore them, but to generate, similar to how the "injected" last sector was added on PSX NoEDC images back in the days) otherwise - no, these bits shouldn't be ignored, if they contain unique data.

Did a first test on Kreon drive today with CloneCD. It would skip through the first couple error sectors, but would stop reading and start making noises as soon as it reached the first ring. So a different drive or custom tools would be needed to dump this data. Will try some other drives later with disc swap.

Jackal wrote:Did a first test on Kreon drive today with CloneCD. It would skip through the first couple error sectors, but would stop reading and start making noises as soon as it reached the first ring. So a different drive or custom tools would be needed to dump this data. Will try some other drives later with disc swap.

I'd recommend to try IsoBuster to manually find the truly unreadable ranges and to dump everything else skipping those sections. The logic is described above (to skip around 300 sectors after the first 1-2 unreadable ones, then to search for the first readable one after the skipped ones).

F1ReB4LL wrote:have you tried to implement that?

http://www.mediafire.com/file/eq80y20l9 … st.7z/file
- added: /nss flag in xbox, xboxswap and xgd2swap

DiscImageCreator.exe xbox <drive> <filename> <speed> /nss 10
'10' is a max rereading value per sector
DiscImageCreator.exe xbox <drive> <filename> <speed> /nss
If value is omitted, '100' is set automatically.

I've not tested yet xboxswap and xgd2swap
Give me a comment, plz.

Doesn't work?

DiscImageCreator.exe xboxswap F: dump 8 /nss 2
AppVersion
        x86, AnsiBuild, 20190407 215226
Invalid argument
Usage
        cd <DriveLetter> <Filename> <DriveSpeed(0-72)> [/q] [/a (val)]
...

DiscImageCreator.exe xboxswap F: dump 8 /nss 2
AppVersion
        x86, AnsiBuild, 20190413 103735
Invalid argument
Usage
        cd <DriveLetter> <Filename> <DriveSpeed(0-72)> [/q] [/a (val)]
...

16 ss is needed.

But if it reads all the sectors, why does it need the SS ranges?

DiscImageCreator.exe xboxswap F: dump 8 290540 445728 603308 759356 912208 1298824 1449692 1610286 1979736 2289920 2448012 2601336 2836428 2990638 3298528 3456316 /nss 2
AppVersion
        x86, AnsiBuild, 20190413 103735
/nss val is omitted. set [100]
Unknown option: [2]
Usage
        cd <DriveLetter> <Filename> <DriveSpeed(0-72)> [/q] [/a (val)]
...

DiscImageCreator.exe xboxswap F: dump 8 /nss 2 290540 445728 603308 759356 912208 1298824 1449692 1610286 1979736 2289920 2448012 2601336 2836428 2990638 3298528 3456316
AppVersion
        x86, AnsiBuild, 20190413 103735
[/nss] is invalid argument. Please input integer.
Usage
        cd <DriveLetter> <Filename> <DriveSpeed(0-72)> [/q] [/a (val)]
...

Still doesn't work.