yeah offline renamer would solve a lot, i guess.
syntax i provided it's ok if you don't like it, it's just an example
but such concept would be much more useful imo.
serial in one case relates to title in the other to release.
in fact in both of those cases it's redundant.
i think i voted for inclusion of serials previously myself.
maybe i was wrong. i liked serials because of subjectivity of romanization but well, we could live with that.

currently as i see it database is getting corrupted. it will be difficult to correct it later.
exe names and developer serials should never have been on the same level as Sony assigned serials - it's just plain wrong.

also i don't think this should apply on other systems. for example PC hasn't got serials at all - that's fine.
in the same fashion PSX could have different syntax.

look:
Tomb Raider (U) (v1.0) [SLUS-00152]
Tomb Raider (U) (v1.1) [SLUS-00152]
Tomb Raider (U) (v1.2) [SLUS-00152]
Tomb Raider (U) (v1.3) [SLUS-00152]
serial=name. name is in english. what's the point?
ther's none.
all you see is that some images are newer than others.

but would it be like this for example:
Tomb Raider (U) (v1.0) [O]
Tomb Raider (U) (v1.1) [GH]
Tomb Raider (U) (v1.2) [GH]
Tomb Raider (U) (v1.3) [CE]
now you can see that ther's 3 releases indexed and besides ther's two possible versions in Greatest Hits.
that's much more descriptive.

Akumajou Dracula X - Gekka no Yasoukyoku (J) (v1.0) [SLPM-86023]
Akumajou Dracula X - Gekka no Yasoukyoku (J) (v1.1) [SLPM-86023]
Akumajou Dracula X - Gekka no Yasoukyoku (J) (v1.2) [SLPM-86023]
again - what's the point? it's unclear which releases were dumped, and which weren't.
in fact, seeing this, i would think either that this title is always associated with this single serial, which is wrong
or if i would know it's untrue (many don't), i would think the rest releases aren't dumped

Akumajou Dracula X - Gekka no Yasoukyoku (J) (v1.0) [O]
Akumajou Dracula X - Gekka no Yasoukyoku (J) (v1.1) [O]
Akumajou Dracula X - Gekka no Yasoukyoku (J) (v1.2) [PStB, PSOB]
two originals
and two other releases are in fact the same
so ther's actually four dumps, not three.
also you can see right away that v1.2 was dumped twice - people would trust us more.

would we handle Japanese serials correct and accept them as associated with releases it would be the same:
Akumajou Dracula X - Gekka no Yasoukyoku (J) (v1.0) [SLPM-86023]
Akumajou Dracula X - Gekka no Yasoukyoku (J) (v1.1) [SLPM-86023]
Akumajou Dracula X - Gekka no Yasoukyoku (J) (v1.2) [SLPM-86073, SLPM-87328]
but since it's different for rest of the regions those edition abbreviation would solve everything and there would be
one valid pattern at last that work for all regions, not like now.

offline renamer could be used to include or exclude certaint tags (like serial) but this concept i believe should be applied.
it's wrong to strech Japanese CDs to the USA indexing pattern - it will not work.

i've edited 1st post a lot, if you've read it on RSS please take a look at forum and write your thoughts, if you care
thanks

i don't know about those but it looks like E and U re-releases always keep the same serial as original.
ok, but J doesn't and now it's like this:
if re-release has same exe name as original - it will be with the same serial in .dat
if exe has different name - this new serial will go to .dat
if exe is PSX.EXE - serial from case will go to .dat
if exe has wrong name (there are few) - i don't know what will happen
that's wrong.
what has exe to do with anything? imo all release serials (from case. and only those) should be listed, like:
Fun Japanese Game (J) (v1.0) [ABCD-00000]
Fun Japanese Game (J) (v1.1) [ABCD-00001]
Fun Japanese Game (J) (v1.2) [ABCD-00001, ABCD-00002]
but not exe names, God forbid! - all CDs from example may have exe: ABCD_000.00
and not Konami or other internal serials.
it's the same as with languages. if languages would be listed - it wouldn't be only the 1st one from the list but all.
and would developer state language differently e.g. Deutsch instead of German - we would not care, would we?
it's the same with serials.

edit:
in other words i believe that filename in .dat should identify:
1.game
2.region
3.version <| this could be a date, but it's better how it's now, imo - with those version numbers
4.release
example i provided above would not work for E and U region.
maybe we should change it at all then - besides serial add an edition, with letters
(or a short code for it, like PStB for PlayStation the Best).

obviously serials in non-Japan region fail to identify release and in Japan single serial fail to identify certain game.
currently it's wrong on that i'm certain.

edit:
why i think those 4 things should be in .dat? because this way files map back to original.
and we go for originals not vice versa so exe name - it doesn't make sense.
there is no way to trace 'Tekken (J) (v1.1) [SLPS-00040]' back to original without online-db.
imagine - db goes down and everyone is left with .dats. it will be the end.

edit:
how about this?:
Fun Japanese Game (J) (v1.0) [Original (ABCD-00000)]
Fun Japanese Game (J) (v1.1) [PStB (ABCD-00001)]
Fun Japanese Game (J) (v1.2) [PStB (ABCD-00001), PSOB (ABCD-00002)]

Fun Japanese Game Imported To USA (U) (v1.0) [Original (ABUD-00000)]
Fun Japanese Game Imported To USA (U) (v1.1) [BlaBla (ABUD-00000)]

Fun Japanese Game Imported To Europe (E) [Original, BlaBla, BlaBlaBla (ABED-00000)]

also this syntax might attract more people since it would demonstrate that many releases are really the same
majority still do not know that and to them files with current syntax do not seem different from everything else

for CD with ID SIPS-60008, when executed with data track file as parameter, it will only display this much:

psxt001z by Dremora, v0.21 beta 1

File: Track 01.bin
Size (bytes):   505941072 (OK)
Size (sectors): 215111 (OK)
EDC in Form 2 sectors: NO

then it terminates and output does not redirects to file

system.cnf:

BOOT = cdrom:\SIPS_600.08
TCB = 4
EVENT = 10
STACK = 801FFF00


for SIPS-60015 however it works fine:

psxt001z by Dremora, v0.21 beta 1

File: Track 01.bin
Size (bytes):   430411296 (OK)
Size (sectors): 182998 (OK)
EDC in Form 2 sectors: NO
ID: SIPS-60015
Date: 1997-04-17
System area: Jap NoEDC

system.cnf:

BOOT = cdrom:\SIPS_600.15;1
TCB = 4
EVENT = 10
STACK = 801FFF00

i guess it's .cnf

also it does not work, when exe is in subdirectory, like here:

psxt001z by Dremora, v0.21 beta 1

File: Track 01.bin
Size (bytes):   343787136 (OK)
Size (sectors): 146168 (OK)
EDC in Form 2 sectors: YES
ID: TLSE-T\SPS

system.cnf

BOOT = cdrom:\TLSEXT\SLPS_024.04;1
TCB = 4
EVENT = 16
STACK = 801fff00

also it does not work when exe is 'psx.exe' and there is no system.cnf:

psxt001z by Dremora, v0.21 beta 1

File: Track 01.bin
Size (bytes):   142281888 (OK)
Size (sectors): 60494 (OK)
EDC in Form 2 sectors: NO

i'll add, that you can see full final sizel here:
From image: 583331280
so 583331280-538655040=44676240 <| audio tracks should total to this. since ther's only one this is the size it should be.
it's great to verify yourself

sectors are indexed by M:S:F (minutes, seconds, frames) because of origin from Audio CD.
seconds: 0..59 (60)
frames: 0..74 (75)
so 2 seconds are 75 * 2 = 150 sectors; 1 second & 74 frames = 75 + 74 = 149.

EAC won't detect gap when ther's only one audio track on CD, it's a known bug.

when gap is attached to the end of datatrack it's not unusual to get different crcs because of different offsets of each drive.

if you removed 352800 sectors from the end of data track manually, you need to add the same amount to the start of audio track.

about gap size, you could check it with hex editor, generally it will be either all 0x00 sectors or scrambled 0x00 sectors (looking like junk) - remove all that until last valid data sector.
commonly on PSX all gaps are 2 seconds large, there are some rare exceptions tho.

232

(12 replies, posted in General discussion)

new version:
http://www.mediafire.com/?gnc2zyddi1n
everything's better now

gap size can be redefined by 3rd parameter in form 'xx-yy'
default is set to 150-150
'225-150' means 3 seconds for data, 2 for audio
'0-0' cuts by TOC - no gaps at all
it's a simple parameter - there is no distinction between data following audio or data
and similarly it does not matter what track precedes audio.

ice.exe "E:\!dc\dreamon\CD Segment.bin" 45000 0-0

ice @20090110 / bill.gates@microsoft.com
---------------------------------
E:\!dc\dreamon\CD Segment.bin
---------------------------------
Accessing                       : ok
Seeking valid Mode1 sector      : ok
 Offset                         : $0000004C
 Scrambled                      : TRUE
 LBA                            : 45000
Seeking LBA 45000               : ok
 Combined offset (samples)      : 19
Parsing IP.BIN                  : ok
 Writting 'ip.txt'              : ok
Parsing TOC                     : ok
 TOC entries                    : 9
 Writting 'redump.cue'          : ok
---------------------------------
03  Data    45000   59896   14897 ok (150)
04  Audio   59897   63612    3716 ok
05  Audio   63613   68847    5235 ok
06  Audio   68848   76246    7399 ok
07  Audio   76247   90700   14454 ok (150)
08  Data    90701  549149  458449 ok
---------------------------------
done

in brackets after 'ok' is amount of foreign sectors - ones that don't pass ecc for data,
and those that do for audio. its for self control - to see if gaps were predicted correct
also if there are ecc errors in data track program will not abort now but add those here

.dll is still required, it would take me longer than a day to rewrite that.
edit: ImgBurn use ElbyCDIO... i guess it's ok.

about those gaps i promised to test today, i'm sorry - i couldn't.
i haven't used xcdtool since autumn when i switched pc and it turns out it does not work now sad
errors i get are: Win32 DeviceIOCTL with SCSI_PASS_THROUGH command failed. (SPT)
and: Invalid Host Adapter ID:0 (ASPI)
strange, though all rest cd programs work fine

edit:
i've tested some applications to see what differences would 2 <-> 3 second audio->data gap change yield
on recorded media or virtual drive and it does not really seem to matter from this point of view.
though the way i tested was kind of indirect since currently only Lite-On works on this system
and it can not fully read sectors when this area is 3 seconds large (like on PCE - i tested with PCE CD).
it would return sense 05/64/00 - ILLEGAL MODE FOR THIS TRACK on Mode1 part of gap (150 sectors)
so this is what i was looking for.


Record:

Alcohol 1.9.8 (7117)
Messes up TOC

AV Burning Studio v1.1.0
Does not support cue

BlindWrite 6.2.0.3
in both cases return sense 05/64/00 on 150 data sectors, like original
2 second gaps - 75 audio sectors are left intact
3 second gaps - replaces 75 audio silence sectors with empty Mode1 sectors

CDBurnerXP 4.2.3.1110
Does not support cue

CDRWIN 4.0G
2 second gaps - return no errors and gap size now is different from original
3 second gaps - return sense 05/64/00 on those 150 sectors, like original

CloneCD 5.3.1.3
Does not support cue

DeepBurner Pro 1.9.0.228
Does not support cue

DiscJuggler V6.00.1400
Does not support cue

ImgBurn 2.4.2.0
2 second gaps - return no errors and gap size now is different from original
3 second gaps - replaces 75 audio silence sectors with empty Mode1 sectors, does not return errors tho

InfraRecorder 0.46.2.0 (cdrtools/cdrkit 2.01.01)
Unsupported sector size 2352...

MagicISO 5.5 (0273)
Does not support cue

PowerISO 4.3
Does not support cue

UltraISO 9.3.2.2656
Does not support cue

Mount:

Alcohol 1.9.8 (7117)
2 second gaps - TOC is fine, return no errors, didn't check subcode
3 second gaps - return sense 03/02/00 - NO SEEK COMPLETE on 75 audio silence sectors forming gap

DaemonTools Lite 4.30.3
2 second gaps - TOC is fine, return no errors, didn't check subcode
3 second gaps - return sense 03/02/00 - NO SEEK COMPLETE on 75 audio silence sectors forming gap

so it's about the same. closest to original PCE probably are BlindWrite 6.2.0.3 with 2sec (weird..) or CDRWIN with 3sec
but i don't think those differences matter at all.

233

(12 replies, posted in General discussion)

thanks! smile

Combined offset (samples)      : -23813975

yeah, it does looks wrong big_smile

I don't know about this.. perhaps you could check the subchannels.. it's propably just a postgap and not really part of the last data track.

ok. i got ill in last days, but tomorrow i'll check it.
the way i understand it - it's always about 3 seconds but in case when audio follows data only 2 are set as pause,
if data follows audio - everything is. but i'll check on that.
also i've made a mistake and currently gd with only one hd track won't work.
and i want to include TOC as cue sheet comments and add ability to set gap size with parameter.
so i'll fix all that and upload new version tomorrow.

Don't forget that the total size in db also includes track 1 and 2 wink

oh i did forgot that smile

ps. I added the elbyecc.dll to the download in the dumping guide.. I hope that doesn't get us into trouble?

i hope not. it's available for download on mayny sites after all.
but in any case i only use it for ecc checking and i think i had code of my own for this somewhere.
i'll try to find it and so maybe this dll will not be needed anymore.

234

(12 replies, posted in General discussion)

conspiracy tongue

ok, i'm done (or so i think smile )
http://www.mediafire.com/?mznzwfynnun
(also you'll need ElbyECC.dll
it comes with CloneCD or just can be downloaded somewhere
mine is v4.0.0.0; crc32: 0d00ed6a)

it is small and simple
i've left those two TOC fields out for now and some other things too
so it could be fairly easy to confuse
in such case, when something strange occurs, it should bail out then
this will probably happen a lot, since i could not really test it myself.
so i don't think it will screw up anything, it should just stop.

syntax is 'ice.exe FileName StartLBAUsedToDumpData'

all gaps are assumed 2sec, so it's better to verify them manually at the start & end of each file.
also i'm not sure if shown offset is correct, i've forgotten quite a lot about those things.
and it could be, that last sector of last data track is missing.
so it would be better to try it out on some known gd-s at first.

and please let me know what could be just different.

edit:
from only gd-rom i could test it looks like gap preceding last data track is 3sec long:
75audio/150data, a lot like PCE (from sector content - i haven't checked subcode)
in database currently ther's either 2 or 0 sec gaps at this position.
this program will go for 2 and will freak out if ther's less than 150 data sectors there.

edit:
those two fields hold first/last track no., alike to real TOC.
what's strange: i've dumped my GD completely
and program seems to work fine - cutting everything as intended.
so total size of tracks should always stay constant: 1,185,760,800
since first/last LBA appears to be fixed: 45000; 549149
but in db every game has different size, hmm

235

(12 replies, posted in General discussion)

at the end of TOC ther's 3 UInt32 values
does anyone know what first two mean?
i thought those are LBA for single-density area tracks, but it doesn't look so.

236

(12 replies, posted in General discussion)

hi, Jackal.

yes, basically the same, except it's not automated in any way. 
i used it to experiment with that scrambled data inbetween tracks.

thanks, i'll try to.

hello, starlord!

i guess nobody here have that experience too...
though from what little info i could gather i'd guess it could very well be just like any other psx cd when written to cd-r.
(video you provided, it looks pretty playable after all, so i guess project was mature.)
probably there would be some difficulties with audio tracks (providing there's any at all) but data track should be with license, system.cnf and all, lacking only that special SCEx wobble @leadin.

or in other case it could be something, only development system can run... (not even a cd, files for emulator, maybe)

The majority of PlayStation development is centred around a standard PC. The recommended minimum is a 488/66 with 16Mb RAM, CD-ROM Drive and a half a gigabyte of local disk space (with a great deal more disk space, either local or accessible via a network, depending on the complexity of your game).   
There are two forms of development systems - one with an ISA interface (the DTL-H2000, requiring a PC with 2 full length ISA slots)), and the newer PCI based version (the DTL-H2500 requires one full length PCI slots, and one other slot ).  The DTL-H2000 system includes two special controllers, for the DTL-H2500 you will need to purchase a DTL-H2080 and some standard controllers.  Both systems have and video and audio out (via composite and S-video cables), connection for an optional PS CD-ROM drive (an external DTL-H2010 for the DTL-H2000 or the internal DTL-H2510 for the DTL-H2500)  and a serial communications port for use with a Link Cable.)
If you are doing a lot of work with both PAL and NTSC, we recommend an RGB SCART cable that can be acquired from Lightwave Cables.  (The part number is SP198, and the cable costs £5.08. Lightwave may be contacted on +44 (0)151-630-5003).
In addition, your PC should have room for at least one additional ISA board - for the CD-ROM Emulator Board (DTL-H2020) ISA Card which itself  requires an additional dedicated SCSI AV hard disk.  (Any good quality, recent (1995+) disk should be acceptable - we’ve  had good experiences with  IBM, Micropolis and Fireball drives).
You also require a television or colour monitor (ideally both PAL and NTSC compatible).
At the moment, SCEE support standard DOS/Windows, but are moving towards Windows ‘95 support.
In the latter stages of development (if not before), you also need to start writing PlayStation format CD-ROMS - this requires the CD Write Once Drive (CDW-900E or the newer CDU921S) unit, which is connected to your PC via a SCSI interface (you will need to buy an additional Adaptec AHA-154x  SCSI card).
Test PlayStation CD-ROM “Gold” discs with either a PlayStation CD-ROM Drive (DTL-H2010)  which attaches to the DTL-H2000, and/or one or more Debugging Stations.  There are three types  Debugging Stations: Japanese NTSC (DTL-H1000), US NTSC (DTL-H1001) or UK PAL (DTL-H1002) to use according to your target markets, and are similar to commercially available machines (with the exception that they allow Gold discs to be run from any territory).
(Note that the internal ROM varies slightly from territory to territory - which is why there are three types of debugging stations.)
You can use any good quality write-once Gold discs for development, but we supply a range of Write Once Mastering Discs (CDR-71PBS) for creating high quality masters to be used for submission to QA and Approvals.
For development of games that  support connected PlayStations playing together, you can buy either a standard Link Cable (SCP-H1040) to connect Debugging Stations together, or a Link Cable for DTL-H2000/H2500 (DTL-H2060) that will allow two Development Board Sets to be linked (but will not connect to a PlayStation).
The Development Board Set’s default Controllers and ISA Board have different plugs and sockets from commercially available Controllers - if you wish to test memory cards or use standard Controllers, then you need to buy from us a Controller Box (DTL-H2080) adapter.

EAC won't overread with some drives.
i don't quite remember, but i think it was so that even more data could end up being replaced with 0x00 in those cases.
IIRC, when OR. is enabled on such drive, it was as if EAC would ignore offset, and cut there.
you might try to go at the very end of last track with IsoBuster or such program, that allow sector view, and see if it returns more data than EAC does.

thanks!
i've borrowed brother's USB adapter 'Gembird UAI001' and it seems to be working just fine.
i think i'll go for those.

serillel2, that came with my old mb, never quite worked...
5 years old now, it was one of first. anything changed?

i got it somewhat unpacked with ollydbg
http://www.mediafire.com/?ijwmgwmtrhl
most likely it will not run properly, but text strings are readable at least.
there doesn't seem to be any references to securom though, but cdcheck is indeed present:
"Unable to find Turok2 CD, Verify CD is in drive and no other application is using CDROM Drive."
"Turok2 requires a CDROM Drive to run!"

ok, thanks

was something wrong with this?

244

(50 replies, posted in General discussion)

ther's an easy way to tell CAV/CLV data aligment apart by measuring time it takes for optics to position from one sector to another.
i guess this is about what Alcohol does with DPM on. maybe it could be used to get characteristics of spiral from CD-Rs
but probably it's too rough. i haven't got much time to test it myself and i'll be away for about 2 weeks, so i've included sources too:
http://www.mediafire.com/?0joblmsqvl1

for example Dreamcast GD-ROM: (didn't know much about it but being described as CAV on wiki, i thought it's curious)

1st area - regular CLV
http://img529.imageshack.us/img529/378/fd0030001501dreamcasteh9.png
linear decrease in delay is clearly visible here (jump @7000, it's drive dropping speed)
this happens, because same amount of sectors in CLV take more revolutions at the center and less towards the outside of CD,
so less mechanical movement is involved to skip same distance (measured in sectors) as radius increases.

2nd area - logo
http://img228.imageshack.us/img228/7517/fd0260001501dreamcastke1.png
for CAV it's constant.

3rd area - high density
http://img228.imageshack.us/img228/5563/fd3100001501dreamcastby0.png
here change of delay is a lot less obvious than in 1st area, but still present.

it's possible to keep one of sectors fixed instead of distance, so now revolutions become visible:
@the beginning of  3rd area
http://img228.imageshack.us/img228/9222/ffs0600001501dreamcastnj6.png

towards the end
http://img375.imageshack.us/img375/2701/ffs3100001501dreamcastuv4.png

from last two images it's apparent, that sectors per track in this area aren't nowhere close to being constant.
so even though pitch or T is modified, essentially it's CLV.

edit:
fixed download link

245

(50 replies, posted in General discussion)

thank you very, very much, RPS!

after seeing your reply, to actually grasp what you said, i had to read through whole book i had. smile
though, i have to admit, i'm still not exactly sure about fully reflective area,
i think i do have basic understanding now of how this would work in regard of CAV area.
those signals, that could possibly be used for authentication, they can originate in these stages:
1.Focusing - but it's unlikely, i guess. there is no relief changes.
and would there be, they'd have to be distinguished from disc vibration.
2.Autotracking - could be used for reflective area. for CAV it's less feasible,
though a lot would depend on exact implementation.
3.High-Frequency Information Signal decoding - on this stage, when it's being transformed into binary signal,
certain frequency would directly depend on channel bit size, making CAV/CLV differentce unambiguous.
4.EFM demodulation - drive rotation speed is constantly corrected depending on subccode block frequency.
so again CAV/CLV difference manifests in a very blatant way.

so thank you again. though yet lacking confidence to experiment with a hardware,
(still have to read much more...) i do have a clear vision of what to do now smile

246

(50 replies, posted in General discussion)

hello, RPS! i'm very glad you're here
actually every tidbit of information would be welcome smile

but so, to be more specific:
basically as i understand this ring with copyright/logo essentially is an area recorded in CAV.
so, how i see it, on ordinary CLV CD pit/land length (T) would stay fixed (with insignificant deviations)
and hence every revolution, from center to outside, would increase in data capacity (by ~35 channel bits).
in CAV on the other hand T is variable that changes so all revolutions hold same amount of data
and pit/land length increases in direction from center to outside.
is this what you meant when you referred to an area with no EFM?
or was it perhaps this transition area (empty zone on microscope image) from ordinary data to ring?
this is what i'm most puzzled about.
also from my understanding, to simulate this CAV layout one would need to keep spindle motor @fixed RPM
(or RPS smile i can't stop to think your nick actually being a tongue in cheek like humor, excue me if i'm wrong)
maybe you have performed such experiments before?
i'm currently reading book on cd circuits but it's probably years until i get there.
so the plan is to hack drive and get this ring on CD-R in CAV. and in case of positive result proceed further
from there. this ability to recreate ring at will would allow necessary flexibility for experimentation
and improving method and making it more user friendly and possibly simplify it to level
where drive hacking would not be required at all.
other possible outcome - ring recreated in CAV would not work. then i guess nothing would.
but we would have done all we could, at least.

as i understand you have a lot of experience with hardware hacking, maybe you are interested in this yourself?
but if not, could you, please, point in direction, where to look to get it done eg. from firmware, circuit?...

247

(50 replies, posted in General discussion)

i finally rewrote those programs. i'm glad i could keep the promise but i'm very sorry it took me so long.

everything is combined in 2 exes: one for interleaving and the other one for recalculating CAV->CLV
http://www.mediafire.com/?nryjjzwv9yx
(please let me know it ther's any problems - still havent tested them much, but i think their fine.)

previously i've tried doing visualisation (on 486 dos machine in vesa smile ) but it's inaccurate.
either you see very small section of cd close or about 4% approximation. neither is very useful imho.
so instead i've changed algorithm for how spiral is broken into tracks from circles to smaller Archimedes' spirals.
this way parameters tie together much better and deviation on whole spiral length is only few bytes.
so generally no visualisation is required. to calculate arc length i use 1st formula given below,
but it's also possible to use 2nd, it's much smaller and very precise also - only differs by 1..2 bytes from 1st one.

1)
s(r₂) - s(r₁)
              _________                 _________
s = ½ r √1 + (r/a)² + ½ a ln (√1 + (r/a)² + r/a)

2)
s ≈ π (r₂² - r₁² ) / ε

ε = pitch

i've tested about 20 patterns on console (different scaling, sector headers on/off, different sector sizes by headers and so on),
with no results. they all act the same: check boot code, go to ring, return to center, return to ring, fail.
altrough they all were written to same 650mb rw @10x and subcode were not modified, i don't think it would change anything.
it's either just too rough or will not work at all because of different sector amount.

also what's interesting, to do more precise scaling, i've tried to clean up ring data by mapping everything to $59/$a8 patterns,
and it's not possible actually. the thing is - every character in copyright message, it's little different.  similar letters - they just look the same
but are not. so when you have eg. byte $ff right between $59 and $a8: ..$59 $59 $ff $a8 $a8.. you can not tell, should it be $59 or $a8.

OO     OO    OO      O?
OO     OO    OO      O?
OO     OO    OO      O?
OO     OO    OO      O?
OOOOOO    OOOOOO?

this adds yet more variables to the equation...
still i've uploaded it anyway here:
http://www.mediafire.com/?na6oybjaam8
(all non dual pattern bytes were mapped to $ff)

so i think only rational way to recreate this data would be by actually writting it in CAV with constant RPM.
but i don't know is this possible at all. i think it should be, by modding firmware or connecting to spindle motor controller probably.

i'll post on cdfreaks what we have, and will try to ask there. somebody should know.

edit:
i've changed one program a little today. and added brief tutorial.
so now it's very easy to output basic shapes and forms to cd. eg it's possible to draw something simple, like this even in notepad.

..............0
.000000000000.0
.0..........0.0
.0.00000000.0.0
.0.0......0.0.0
.0.0.0000.0.0.0
.0.0.0....0.0.0
.0.0.000000.0.0
.0.0........0.0
.0.0000000000.0
.0............0
.00000000000000

and you just need to specify how many times to repeat pattern.
but still you need to know parameters of given CD - it's a huge drawback.

http://img136.imageshack.us/img136/9738/img0095lb9.jpg

248

(50 replies, posted in General discussion)

my pc died today... sad
it was having problems for about last half month.
would not start often and when it did, was going on defaults only - cmos would hang on save.
the week i didn't wrote 15..24 i was replacing cpu, i thought it was l2 cache, but it didn't help.
so finaly today it's stone cold. even bios doesn't beep.
and i can't afford repair or a new one now.

so i won't be able to do anything for a while.
i'm sorry i couldn't finish those programs.

i was writing simulation on pc. the ray, when you supply wrong parameters form curve what's essentially archimedean spiral.
so i thought that would be interesting to experiment with it on pc screen, rather than reburn cds all the time.

to form a ray - it's not hard. all you need is to take start / end radius, track pitch and channel bit size as variables
(width of ray optionally - it's better to start with at least one sector wide and decrease it gradually, as it gets straighter)
and calc rings with incremental circumference from 2*Pi*r. that's what i did, but maybe ther's a better way.

when parameters of given cd are determined you can draw whatever you like in this model, (or realign data / pad / add headers...)
and then run it through deinterleave routine to form an image,
thogh it will always be distorted by some amount, i guess, because it's an approximation after all
and because of the nature how cds work.

i never tested those images on saturn, myself... i sincerely hope somebody will.

249

(50 replies, posted in General discussion)

ther's another guy: ProgrammingAce @SegaKatana forum
the site is dead now, so i'll repost here, what he wrote:

ProgrammingAce          Post subject:
Posted: Sat Apr 21, 2007 12:12 am
Joined: Thu Jul 20, 2006 1:14 am
Posts: 14        

Grr... my RSS feed here was damaged (i forgot to update, even though mark specifically warned me).

I know quite a bit about copy protections (and saturn specifically). I can tell you that not only is it possible to burned self booting Saturn games, but that it has already been done.

It looks like you're on the right track. If you have any questions, let me know.

ProgrammingAce          Post subject:
Posted: Sat Apr 21, 2007 12:53 am
Joined: Thu Jul 20, 2006 1:14 am
Posts: 14        

Alright, to be a bit more helpful i read through what pinchy said on the cd forums.

Although they're arrogant, they're also right. The pre-ring data is irrelevant, or to be more accurate, non existant. The CD-ROM drive in the saturn isn't any more advanced then what you use in your PC. If you can't force a drive to do a raw read of the sectors, chances are they're no good.

Quote:
I tried to test the counter that is supposed to increment when reading actaul ring data by moving it down to the pre ring area but it still didnt increment.


This confuses me. The check is hard coded to the address location. You're missing the cause and effect. The seek doesn't start the check, the check is a result of the copy protection function.

Save the cheerleader, save the world.

ProgrammingAce          Post subject:
Posted: Fri Apr 27, 2007 5:00 am
Joined: Thu Jul 20, 2006 1:14 am
Posts: 14        

-=FamilyGuy=- wrote:

I noticed that the data seems to be audio, and I don't think it as something to do with any knid of refraction like some are saying .. it makes no sense.

The ring, to me, looks like this : weird sector + a8 59 pattern + weird sectors


The ring data is audio, it's a tone.

The weird sectors are markers, not readable data. Reproducing them would be futile (if even possible without stamping equipment).

it's about the same what Bexster/RPS wrote @cdfreaks

edit:
here, he says more @gamerhistory forum
http://gamerhistory.com/forum/viewtopic.php?t=661

250

(50 replies, posted in General discussion)

it might, the thing is - i don't know tongue, closer it is to original the better

honestly, i haven't noticed, but yeah, looks like ring.
it's d ~44 mm..~46 mm for 'inner buffer zone' and ~46 mm..~50 mm for lead in, i think.
but what makes this thin stripe, i don't know. maybe you can compare it with other pressed cds - pc, audio... (better older)?
i only have those few from saturn atm.

edit:
got my saturn now, tried swapping and it can be done so, that only outer part from the original cd is read.
whatever there is @center, it doesn't matter.