iR0b0t wrote:

A separator is not really needed. Anything between "REM" and traling "START LBA NUMBER" is to be treated as a plain comment or a COMMAND, which will be recognized if its called "SESSION NUMBER" or "LEAD-IN" or "LEAD-OUT" or whatever commands you want to have there.

I think it should start with a real command and require input of a number, for uniformity and to allow other uses besides dreamcast.

REM <COMMAND> <OPTIONAL DESCRIPTION> <START LBA NUMBER>

REM AREA "SINGLE-DENSITY" 45150

or

REM START "SINGLE-DENSITY AREA" 45150

Where the " " are optional and the last number is assumed to be the start address?

F1ReB4LL wrote:

SINGLE-DENSITY AREA always starts at 0, HIGH-DENSITY AREA always starts at 45150, additional commands aren't needed here. These are to be discussed later for the multisessional discs (though, even they should have REM LEAD-OUT and REM LEAD-IN generating commands, not that LBA thing).

iR0b0t wrote:

You know that they start there because you are aware of that, but mounting tools do not know it.

Yeah, but anyway: REM NAME / START LBA  is also a new implementation that isn't supported yet by any software.

If you want to assign a unique command for dreamcast discs that assumes fixed starting positions, then maybe 'LDA' and 'HDA' are better names.

I like this solution:

iR0b0t wrote:

REM SINGLE-DENSITY AREA START LBA *here number*
FILE "Official Sega Dreamcast Magazine Vol. 11 - February 2001 (USA) (Track 1).bin" BINARY
  TRACK 01 MODE1/2352
    INDEX 01 00:00:00
FILE "Official Sega Dreamcast Magazine Vol. 11 - February 2001 (USA) (Track 2).bin" BINARY
  TRACK 02 AUDIO
    INDEX 00 00:00:00
    INDEX 01 00:02:00
REM HIGH-DENSITY AREA START LBA *here number*
FILE "Official Sega Dreamcast Magazine Vol. 11 - February 2001 (USA) (Track 3).bin" BINARY
  TRACK 03 MODE1/2352
    INDEX 01 00:00:00
FILE "Official Sega Dreamcast Magazine Vol. 11 - February 2001 (USA) (Track 4).bin" BINARY
  TRACK 04 AUDIO
    INDEX 00 00:00:00
    INDEX 01 00:02:00
FILE "Official Sega Dreamcast Magazine Vol. 11 - February 2001 (USA) (Track 5).bin" BINARY
  TRACK 05 MODE1/2352
    INDEX 00 00:00:00
    INDEX 01 00:03:00

As long as the start address of a track can be specified, there is no more need for PREGAP.

Maybe add a separator between the data area description and the start address, e.g. like this:

REM HIGH-DENSITY AREA ; START LBA 45150

and should we use LBA or MSF?

REM HIGH-DENSITY AREA ; START MSF 10:02:00

or a more abbreviated (but less descriptive) alternative, where the second part value is assumed to be the start address:

REM HDA 45150

Or a description with spaces would require " "

REM "HIGH-DENSITY AREA" 45150

And yes, this standard could be used for other disc types, e.g. multi session, and more data areas could be added when needed.

F1ReB4LL wrote:

I've already mentioned such a solution. The problem is that such a cue is only "correct" for isobuster, other tools will "see" this track 9+ minutes longer than it should be.

Actually, Track03 is shown with the correct size and starting address.

The only problem is that the Track02 end address aligns with Track03, but when you browse outside of the data range, it gives read errors.

I don't think this is a problem, it's merely a restriction of the .cue standard.

REM SESSION 01 and REM SESSION 02 are also wrong, these commands generate a multisessional disc TOC, while GDs aren't multisessional, those are 2 separate images written on the same media (or 3, if to count the security ring area).

I only suggested it because it's the only way to make IsoBuster detect the filesystem of Track03. But for emulators etc. we could stick to REM SINGLE-DENSITY AREA and REM HIGH-DENSITY AREA.

that's why I've offered to do separate cues, so you could load them independently, just like a real thing. You either load and work with the LD area with 2 tracks or with the HD area with the track 3 and beyond (if any), not both.

You still need the PREGAP line, even with separate cue's, because otherwise you would be pointing Track03 to start at sector 150 instead of 45.150.

So, I think this solution still stands?

Demolition Racer - No Exit (USA).cue wrote:

REM SINGLE-DENSITY AREA
FILE "Demolition Racer - No Exit (USA) (Track 1).bin" BINARY
  TRACK 01 MODE1/2352
    INDEX 01 00:00:00
FILE "Demolition Racer - No Exit (USA) (Track 2).bin" BINARY
  TRACK 02 AUDIO
    INDEX 00 00:00:00
    INDEX 01 00:02:00
REM HIGH-DENSITY AREA
FILE "Demolition Racer - No Exit (USA) (Track 3).bin" BINARY
  TRACK 03 MODE1/2352
    PREGAP 09:42:68
    INDEX 01 00:00:00
FILE "Demolition Racer - No Exit (USA) (Track 4).bin" BINARY
  TRACK 04 AUDIO
    INDEX 00 00:00:00
    INDEX 01 00:02:00
FILE "Demolition Racer - No Exit (USA) (Track 5).bin" BINARY
  TRACK 05 MODE1/2352
    INDEX 00 00:00:00
    INDEX 01 00:03:00

Or tell us what the benefit would be of having 2 .cue's, like this?

Demolition Racer - No Exit (USA) (LD).cue wrote:

REM SINGLE-DENSITY AREA
FILE "Demolition Racer - No Exit (USA) (Track 1).bin" BINARY
  TRACK 01 MODE1/2352
    INDEX 01 00:00:00
FILE "Demolition Racer - No Exit (USA) (Track 2).bin" BINARY
  TRACK 02 AUDIO
    INDEX 00 00:00:00
    INDEX 01 00:02:00

Demolition Racer - No Exit (USA) (HD).cue wrote:

REM HIGH-DENSITY AREA
FILE "Demolition Racer - No Exit (USA) (Track 3).bin" BINARY
  TRACK 03 MODE1/2352
    PREGAP 10:02:00
    INDEX 01 00:00:00
FILE "Demolition Racer - No Exit (USA) (Track 4).bin" BINARY
  TRACK 04 AUDIO
    INDEX 00 00:00:00
    INDEX 01 00:02:00
FILE "Demolition Racer - No Exit (USA) (Track 5).bin" BINARY
  TRACK 05 MODE1/2352
    INDEX 00 00:00:00
    INDEX 01 00:03:00

The start address of the first Track03 sector is 10:02:00.

When we use a normal single cuesheet (with or without REM), the problem is that normal applications place the Track03 start time relative to the previous tracks.

So in order to get the correct sector addressing, a PREGAP will needs to be calculated based on the length of the previous 2 tracks.

Example: http://redump.org/disc/52815/

10:02:00 minus the combined length of the LD tracks (17:07) = 09:42:68

With this cuesheet, IsoBuster correctly loads the Track03 filesystem and other applications like CDmage have the correct sector addressing:

REM SESSION 01 ; SINGLE-DENSITY AREA
FILE "Demolition Racer - No Exit (USA) (Track 1).bin" BINARY
  TRACK 01 MODE1/2352
    INDEX 01 00:00:00
FILE "Demolition Racer - No Exit (USA) (Track 2).bin" BINARY
  TRACK 02 AUDIO
    INDEX 00 00:00:00
    INDEX 01 00:02:00
REM SESSION 02 ; HIGH-DENSITY AREA
FILE "Demolition Racer - No Exit (USA) (Track 3).bin" BINARY
  TRACK 03 MODE1/2352
    PREGAP 09:42:68
    INDEX 01 00:00:00
FILE "Demolition Racer - No Exit (USA) (Track 4).bin" BINARY
  TRACK 04 AUDIO
    INDEX 00 00:00:00
    INDEX 01 00:02:00
FILE "Demolition Racer - No Exit (USA) (Track 5).bin" BINARY
  TRACK 05 MODE1/2352
    INDEX 00 00:00:00
    INDEX 01 00:03:00

What do you guys think about this implementation?

It would require some extra coding, but it maintains the existing "standards" for .cue.

If you want to conform to the standards that are already set by IsoBuster with multisession discs, and have the best compatibility with other tools, the cuesheet should be like this:

REM SINGLE-DENSITY AREA
FILE "Official Sega Dreamcast Magazine Vol. 11 - February 2001 (USA) (Track 1).bin" BINARY
  TRACK 01 MODE1/2352
    INDEX 01 00:00:00
FILE "Official Sega Dreamcast Magazine Vol. 11 - February 2001 (USA) (Track 2).bin" BINARY
  TRACK 02 AUDIO
    INDEX 00 00:00:00
    INDEX 01 00:02:00
REM HIGH-DENSITY AREA
FILE "Official Sega Dreamcast Magazine Vol. 11 - February 2001 (USA) (Track 3).bin" BINARY
  TRACK 03 MODE1/2352
    INDEX 01 00:00:00
FILE "Official Sega Dreamcast Magazine Vol. 11 - February 2001 (USA) (Track 4).bin" BINARY
  TRACK 04 AUDIO
    INDEX 00 00:00:00
    INDEX 01 00:02:00
FILE "Official Sega Dreamcast Magazine Vol. 11 - February 2001 (USA) (Track 5).bin" BINARY
  TRACK 05 MODE1/2352
    INDEX 00 00:00:00
    INDEX 01 00:03:00

edit: Because the HD area apparently starts with Track03, we no longer need to think about Multi-Cue or other alternatives.

32

(1,730 replies, posted in General discussion)

Here's a type of SecuROM that seems to be different from all previous types:

http://redump.org/disc/45559/

http://redump.org/disc/58232/

The things that are unclear to me:

- For Diablo II: Lord of Destruction, SecuROM sector 157 was not included in the SubIntention. What was causing this?

- Could the write offset of +576 be wrong? it's -12 plus 588 samples (1 sector). I've never seen this offset before.

- Can you plz double check if the SecuROM data is correct and if there are really 99 "modified" sectors for this SecuROM version?

Here are the log files for Diablo, and also an unmodified CloneCD.sub from another drive:
https://www50.zippyshare.com/v/jUraqxWb/file.html
https://www50.zippyshare.com/v/dVsXalzo/file.html

Thx for your help smile

Unless, there's a language selector or English voice option, it's probably best to only list the foreign language?

I think it would be better to skip dual cuesheets completely and stick to the single cue with the proposed improvements? It's just way more practical. Multi session discs should have a similar solution.

HTTPS should be the next priority... Dreamcast cuesheet is not iR0b0t's fault. We didn't exactly come to an agreement yet on a standard? And multi session support doesn't really exist for cuesheets (except for REM comments which don't really do anything AFAIK)

ajshell1 didn't have permissions yet for the dumps forum yet, but now he does. There were 5 other moderarors and 2 admins who could have cleaned it up, but apparently nobody has time for it.

The only thing you can really blame the staff for is lack of time. ajshell1 is the first staff member who's consistently putting in some serious time since he was promoted, but still there are tons of Chinese dumps being submitted that nobody feels comfortable checking/adding. I don't know how we can solve that matter.

As for having more developers working on the site or access to backups, I think this issue was thoroughly addressed before. I guess iR0b0t is too paranoid about security and he would only give backups access to Dremora or F1reb4ll and not give anybody direct access anymore to the server.

36

(0 replies, posted in News)

The Video Game Preservation Collective (VGPC) is holding a fundraiser to help preserve more games. More info here.

Why do we have both (Asia, USA) + (USA, Asia) regions?
and also (Asia, Europe) + (Europe, Asia)

@iR0b0t, plz remove the (Asia, USA) + (Asia, Europe) regions. They are useless and not used by any dump.

Could we decide with a poll which cue gets chosen?

And if 2 .cue's becomes the standard, the disc page should be modified to split the 2 areas?

Also, regardless of how many .cue's are chosen, we need to discuss the HD data track pregap. The sector address never starts at 02:00 IIRC, so there should be an INDEX, so that this track will load (and show contents) properly in tools like cdmage?

F1ReB4LL wrote:

Both sessions are independent and not connected with each other. Dreamcast also has 2 indendent "read TOC" commands for LD and HD areas. These are 2 separated images, need 2 cues.

That's just a technicality. If you create 2 different sets of dump files with different .cue and filenames, and 2 archives for a single disc, this will be a bigger issue than what we have now.

Schrodinger wrote:

Multi cue as one for LD area and one for HD area.

What's the benefit of that? 2 cue's are a nuisance. Can't we just have a single .cue with the HD area starting at Track 03?

"multi-cue" is a cuesheet with multiple binary tracks, like we have already for the other systems? Multi session PC discs also have a "normal" cuesheet. So all that is needed is to replace the gdi download with .cue?

42

(1,730 replies, posted in General discussion)

Rib Today at 5:44 PM
it works

43

(1,730 replies, posted in General discussion)

@sarami, DIC doesnt detect SecuROM for this disc and gives empty subIntention: http://redump.org/disc/57096/

the sector -1 is apparently different from newer (4.68.00 and higher) SecuROM versions: http://redump.org/disc/37956/

RibShark wrote:

How many read retries are required on average?

You could try with a max of 50 retries. Also be sure first to set the read speed to 4x, by starting a dump at 4x and then retrying cdarchive. If it still wont read so many sectors, I guess you have a wrong model.

RibShark wrote:

Optiarc AD-7170S does not appear to be able to read every sector. When attempting to dump http://redump.org/disc/43106/, the drive fails to read sectors 2178-2184. So not all Optiarc drives are good for dumping physical ring protection.

Did you use cdarchive to read backwards with enough read retries?

46

(9 replies, posted in General discussion)

sarami wrote:
Jackal wrote:

Fair Strike + HellForces + Cold War Conflicts are newer titles with a different type of LaserLock "Star", which has the error sectors at the end of the disc.
For Cold War Conflicts, the redump image seems to work.
Fair Strike + HellForces seem to need DPM/RPMS. A CloneCD image alone wasn't sufficient.

Good works. Btw, is LaserLock "Star" different from LaserLock MARATHON? https://www.cdmediaworld.com/hardware/c … thon.shtml

No idea, I just found the name "LaserLock Star" somewhere, maybe we should just call it LaserLock NEW? tongue

47

(9 replies, posted in General discussion)

https://img-16.ccm2.net/cPafcOLIJof7F1ucGLdYP-BRtXQ=/3da041f562bd4ff9b8a3f9f8586eb88f/ccm-faq/AlGX0Jra-cohol5-s-.png

It's strange that they are listing it separately, so maybe subchannels aren't used but something else. I also read in other places that "with a 1:1 image, emulation isn't needed".

Does it mean cue+bin (no sub) image can't run?

Asghan and V2000 are crashing at startup (and Asghan somehow works with emulation enabled), but it could be because of other issues or compatibility problems.

I tested some other games (Icewind Dale + Spec Ops + Evolva, and before also other games) with normal redump images without without subchannels, and they worked.

Fair Strike + HellForces + Cold War Conflicts are newer titles with a different type of LaserLock "Star", which has the error sectors at the end of the disc.
For Cold War Conflicts, the redump image seems to work.
Fair Strike + HellForces seem to need DPM/RPMS. A CloneCD image alone wasn't sufficient.

So I'm giving up for now. There is no evidence that any LaserLock games are using subchannels. Maybe reentrant can also double check his Fallout 2 disc to be sure.

Did you check the pregap of track1 and lead-in and lead-out?

Pregap yes, lead-in and lead-out no.

48

(9 replies, posted in General discussion)

sarami wrote:

http://www.laserlock.com/faq.html#canLLProtectMixed
Official site says

Can LaserLock protect Mixed Mode CDs?
LaserLock can protect the PC part of mixed mode CDs. Audio tracks cannot be protected and are not affected by the protection.

They must be talking about the bad sectors, not the subchannels.

After rereading some sectors, it seems obvious that the 1-bit crc errors are normal read errors and not part of the protection.
I'm still checking, but so far I haven't found any obvious protection data on any of the discs.
Or is it possible that drives modify the data and correct the crc bytes when they shouldn't?

49

(9 replies, posted in General discussion)

edit: It turned out to be a wild goose chase

50

(1,730 replies, posted in General discussion)

Here a dump with CATALOG 000000000000 (one 0 less than normal): http://redump.org/disc/55821/

Logs: https://mega.nz/#!T1gSQS6Q!L-frCQXIBkqX … fy3Pf41Fo8

DIC bug?