how custom Disc number field is meant to be?

[themabus]

should Disc number be filled with 'A' and 'B' instead of '1' and '2', if that's how it's printed on media?
it's 0..3 instead of 1..4 for Enemy Zero after all

[provato]

should Disc number be filled with 'A' and 'B' instead of '1' and '2', if that's how it's printed on media?
it's 0..3 instead of 1..4 for Enemy Zero after all

I would try to see if the game itself would ask me for disc "B" or for disc "2" when swap is needed.
After all, we're dumping data/info (what the screen says) and not artwork...

P.S.: This is a good point to also talk about preserving covers-manuals here

[themabus]

ok, thank you provato, this is a good thought imho

game in question is Dracula Detective for Saturn

it indeed also internally refers to CDs by letters


which curiously enough isn't the case with PSX version

[Rocknroms]

Disk number field is not custom, it's only numerical. "Disc A" or "Disc B" are disk names but adding them in the appropriate field will be redundant.
About Enemy Zero it's quite obvious that naming disc in a different way will make confusion (it's the only exception until now).

[F1ReB4LL]

<Handrie> New dump(s) https://redump.info/rss/recentdumps : [PC CD][NEW] test (Asia) (Disc A) <https://redump.info/disc/8539/>

so looks like it's not only numerical.

[Rocknroms]

<Handrie> New dump(s) https://redump.info/rss/recentdumps : [PC CD][NEW] test (Asia) (Disc A) <https://redump.info/disc/8539/>

so looks like it's not only numerical.

So this disc is named wrong (disc name instead of disc number. I meant it's wrong not it's not possible), the field says "disc number" so it refers to progressive numbers.

[themabus]

in TOSEC it's alike to what Rocknroms suggests:

* (Disk/File/Tape x of y Side A/B)
This field is used if the game spans more than one disk, or is comprised of
multiple files. When there are 9 or less disks, the format of (Disk 1 of 3)
is used. If there are 10 or more disks, then the entry needs to change to
(Disk 01 of 13) to maintain consistency. In cases where double sided tapes
or disks are involved, the "Side A/B" entry is also included.
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(File 1 of 2)"
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(File 2 of 2)"
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(Side A)"
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(Side B)"
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(Disk 01 of 11)"
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(Disk 08 of 11)"
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(Disk 10 of 11)"
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(Disk 1 of 2 Side A)"
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(Disk 1 of 2 Side B)"
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(Disk 2 of 2 Side A)"
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(Disk 2 of 2 Side B)"
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(Tape 1 of 2 Side A)"
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(Tape 1 of 2 Side B)"
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(Tape 2 of 2 Side A)"
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(Tape 2 of 2 Side B)"

** NOTE: In cases where multi-file zips are used, the parent's zipname should
reflect the contents of the zip.
The files :
"Legend of TOSEC, The (1986)(DevStudio)(US)(Disk 1 of 2).bin"
"Legend of TOSEC, The (1986)(DevStudio)(US)(Disk 2 of 2).bin"
would be included in the zip called:
"Legend of TOSEC, The (1986)(DevStudio)(US)[2 Disks].zip"

* (disk label)
If the disk label is known, this field following the (Disk x of y) entry
should contain it. This is mainly used when save, program, install, or
other custom names might be requested by the game itself. (Disk 2 of 3) is
not useful by itself when the program asks you to "Insert Character Disk".
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(Disk 1 of 2)(Program)"
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(Disk 2 of 2)(Data)"
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(Disk 2 of 2)(Disk B)"

but it makes more sense there, since 1st field always denotes medium from a set - it has a different meanig
here it's only a counter: A, B, C or 0, 1, 2 or I, II, III can be a counters too
so in TOSEC also Enemy Zero would be with labels

(Disc 1)(Disc A) and (Disc 1)(Disc 0) overlap, but (Disc 1) does not express this situation fully, imho,
(Disc 1 of 2)(Disc A) would, as would (Disc A) <- not as complete as previous one though, but that's what we got
also it's the same with (Disc 1 of 4)(Disc 0) and (Disc 0), though 1st is more descriptive again, both are fine, imho

[Dremora]

"Disc 0 of 4" would look quite strange, but as we don't write total discs number to the filename, any custom numbering scheme can be used.

[Rocknroms]

I didn't suggest anything, I simply said that "Disc A", "Disc B", etc. are disc names / not disc numbers and I said that "adding them in the appropriate field will be redundant". So at least I suggest the opposite: - avoide tosec shitness -. It's quite obvious that Disc A is Disc 1 and so on.
Moreover tapes are not discs so you have to label "Side A" and "Side B", this are common names on every old tape.

[F1ReB4LL]

I'd vote for Disc A, Disc B, etc., but only when it's needed. If it's written on the CD - why not?