CDVD issues

[TnA]

@nodge:

DVDELF.BIN = Dump of DVD-Driver
BOOT.ELF=The ELF, which get's embedded, if it is in the same dir, as the installer, this is the ELF, which gets embedded.

Btw.: The embedder is working properly, but it is an issue of load-address.

[Billkwando]

I've read this thread 3 or 4 times and I'm still not sure I understand it.

If I have the newest version of Free MC Boot (1.3c), do I need that "runme" file?

I haven't had any problems running any elfs.

I'm just wondering if I'm missing out on something useful.



Edit: Oh wow, that was my first post here and I sound like a douche.

[slicer74]

Nope, the latest runme is in v1.3 of mcboot.

[TnA]

Need an info about.

sceCdBootCertify

Don't exactly know, what it is for.

[coolaan]

My best guess is that you are really impatient to wait for ffg's tool

My 2nd guess is that it might be a function call which checks the dvd/cd we put in the drive and check whether it is original/backup/video etc. May be some unlocking mechanisms also???? .. not sure just guessing...

[TnA]

Maybe both.

AFAIK, PS2 tests CDVD for ID, after it gets the name of the CDVD-Boot-ELF from SYSTEM.CNF
If the Subchannel/ECC-ID isn't there, it rejects the Disc as invalid.
Or does it recognize it as invalid, before any file is accessed?
(Checking for an ID and then compare it with CDVD-BOOT-ELF?)
Correct me, if I'm wrong and give me more info about this.
I got my info from ZoneLoader-SRC (+pdf).

[coolaan]

Ok my 3rd best guess:-

Each time when a cd/dvd is inserted or when a cd intialization function is called, some sort of checking might be performed to know whether it is an original PS1/PS2/DVDV etc etc. Now If this procedure is interpreted by some memory resident program, then that program checks the dvdv disc, validates and sends the necessary values to the calling program expecting the value to be an original or PS2-DVD .

So ffg's program might actually validate/unlock the disk when a DVDV disc is inserted and stays in the memory watching out for all calls for the cddvdinit or other calls and interprets it appropriately for the program calling the fucntion.

ffg mentioned some problems with homebrew regarding memory rt? This might be bacause some hombrew clear off the user memory space before doing something thus might remove ffg's memory resident program also..

Sorry to bother you ffg if something is wrong and you are really upset about our wild guesses... but we a poor people who cant hide their anxieties you know....

[Billkwando]

Thanks slicer!

Originally Posted by coolaan

Ok my 3rd best guess:-

Each time when a cd/dvd is inserted or when a cd intialization function is called, some sort of checking might be performed to know whether it is an original PS1/PS2/DVDV etc etc. Now If this procedure is interpreted by some memory resident program, then that program checks the dvdv disc, validates and sends the necessary values to the calling program expecting the value to be an original or PS2-DVD .

So ffg's program might actually validate/unlock the disk when a DVDV disc is inserted and stays in the memory watching out for all calls for the cddvdinit or other calls and interprets it appropriately for the program calling the fucntion.

ffg mentioned some problems with homebrew regarding memory rt? This might be bacause some hombrew clear off the user memory space before doing something thus might remove ffg's memory resident program also..

Sorry to bother you ffg if something is wrong and you are really upset about our wild guesses... but we a poor people who cant hide their anxieties you know....

I like you, good sir.

Your guesses sound much more educated than mine, but yeah, that's what I hoped they were talking about.

[nodge]

I bought a chunky PS2 yesterday but only started testing it today. All I gotta do is add the BOOT.ELF to dir and away I am.

I still will mess around with the slim version. Got myself a crossover ethernet cable yesterday also.

Just incase anyone else is as far as I am/was, you need to use PS2Link for the slim version because this one does not use DVDELF as it uses DVDPLX instead (based on another guy's post on this message board). Because of this, you cannot use dvdversioncheck to extract DVDELF.bin. Although, someone in another post did mention that you can use a DVDELF.bin from an old BIOS. Not sure if that works because I have not tested it.

My thoughts on this are that if you do not have access to a chunky PS2, you could use an emulator with v3 BIOS and do it that way. Don't quote me on this though.

PS2Link can copy the necessary files from erom0 but I don't know what comes after that atm.

[TnA]

Why don't you use the Mini-DVDPLxs provided by l.oliveira?
There is one for any region.

[yoshi314]

Each time when a cd/dvd is inserted or when a cd intialization function is called, some sort of checking might be performed to know whether it is an original PS1/PS2/DVDV etc etc. Now If this procedure is interpreted by some memory resident program, then that program checks the dvdv disc, validates and sends the necessary values to the calling program expecting the value to be an original or PS2-DVD .

actually no.

disc is validated by the mechacon chip - psx/ps2 disks contain some data in pre-data ring on the disk, which is impossible to replicate by burning the disk, and is accessible only by ps2 drive hardware. if the disc is invalid the drive will reject the disk, at hardware level (supposedly).

also mechacon decrypts some portions of the disk, e.g. playstation2 logo that appears on disk start.

[ffgriever]

@coolaan
What you described is impossible. You cannot do it with any software solution. So, unfortunately, yoshi is right.

But you can tell mechacon to restrict access to all media or just some special types of media. You can also remove this restriction. But take a note, that it actually has nothing to do with telling mechacon what it should authorize or not. It's just matter of restricting user access to already authorized media. Thus it's rather useless for the cases you described (but is quite usefull in removing one restriction that OSDSYS does on dvdv media).

[coolaan]

Originally Posted by ffgriever

@coolaan
What you described is impossible. You cannot do it with any software solution. So, unfortunately, yoshi is right.

But you can tell mechacon to restrict access to all media or just some special types of media. You can also remove this restriction. But take a note, that it actually has nothing to do with telling mechacon what it should authorize or not. It's just matter of restricting user access to already authorized media. Thus it's rather useless for the cases you described (but is quite usefull in removing one restriction that OSDSYS does on dvdv media).

ffg, Yoshi ,

I wasnt telling about a software solution to authorize the dvd backups. I was telling that if a patched disk was inserted, the mechacon validates it and that it. If normally read, this is is read as a DVDV, but maybe your pgm just interprets it as a normal DVD to the calling pgms.... this is what i meant...

Maybe yoshi interpreted it wrongly and that gave you also the wrong idea!!
Or yet still my english is veryyyyy confusing... even my frnds tell me that sorry for the confusion.

It doesnt matter if I am right or worng, u can leave off my guesses . We are eagerly waiting for your release (revealings) ..

PS : I did read ur earlier posts telling that now matter how hard u tried u couldnt get it to read burned backups .

[yoshi314]

If normally read, this is is read as a DVDV, but maybe your pgm just interprets it as a normal DVD to the calling pgms.... this is what i meant...

that's implemented in SMS - you can access data on fake video dvd's normally in it, if that's what you mean.

[coolaan]

ya yoshi, something of that sort ....

Sorry for the confusion guys!!!

[ffgriever]

In my case it's absolutely different than in SMS. In SMS there is implemented additional driver that replaces the popular cdfs device driver (well, it's based on it, just UDF support is added). It works just as the old one for the cases that cdvdman's cdrom device can handle easily (ISO, but the cdfs driver also recognizes joliet names).

I, on the other hand, didn't implement any new device drivers (that would require much more of valuable IOP memory and would be much less compatible).

Oh, I've seen somewhere a question about FMV stuttering in some games with memento. I'm not that much into it, but it seems that at least in some cases they've made streams synchronous (the amount of stuttering should vary from "none" to "very freaking big", depending on the way the application handles FMVs).

In my case everything stays as it was intended. So streams (as well as anything else) are asynchronous (until application will make it synchronous by cdsync or simply waiting for 4e) and handled the way they was meant... by the original modules.

PS. Just polishing details, making sure there won't be any obvious bugs, cleaning the code for public beta release.

[coolaan]

Originally Posted by ffgriever

In my case it's absolutely different than in SMS. In SMS there is implemented additional driver that replaces the popular cdfs device driver (well, it's based on it, just UDF support is added). It works just as the old one for the cases that cdvdman's cdrom device can handle easily (ISO, but the cdfs driver also recognizes joliet names).

I, on the other hand, didn't implement any new device drivers (that would require much more of valuable IOP memory and would be much less compatible).

Oh, I've seen somewhere a question about FMV stuttering in some games with memento. I'm not that much into it, but it seems that at least in some cases they've made streams synchronous (the amount of stuttering should vary from "none" to "very freaking big", depending on the way the application handles FMVs).

In my case everything stays as it was intended. So streams (as well as anything else) are asynchronous (until application will make it synchronous by cdsync or simply waiting for 4e) and handled the way they was meant... by the original modules.

PS. Just polishing details, making sure there won't be any obvious bugs, cleaning the code for public beta release.

Wow... I cant waitt!!!. From now on no more guesses!!!!

[matteogeniaccio]

please, tell us what ESR stands for

[Bootlegninja]

People, please keep ESR name guessing and questioning out of legit working threads. It does nothing but clutter them up and bury useful information, not to mention it makes you sound like a complete n00b regardless of how long you've been here.