[aries2k]

Originally Posted by Mistawes True, noticed a few games that seem to have that check alright. But if we burn to disk, doesn't that negate that side effect? Just curious, because it'd hardly give that error if it's reading from disk, or would it end up as a signing error because it only expects Fself's to be on there? Gonna see if any of the lads have a BR burner to test it out (I presume I'm wrong and it's already been tried 100 times, but better than nothing).

I´ve tried burning to disc a couple of times but had no luck. The ps3 would not recognize the disc as a game disc.
I was told that only works on a real DEX machine or I would have to remarry my BD drive.?
truthfully I don´t understand that bit to much. A real DEX machine has a different BD drive or a different BD firmware?

I was kind of bummed out about this because one of the reasons I converted was because I heard that DEX machines could read PS3 and PS2 games burnt as a master disc.
a little off topic, I was never able to get my ps3 to read different region ps1 and ps2 games either, I´m assuming that´s because of the same reason as not reading burnt discs.?

[Mistawes]

Cheers @aries2k it must be the BCA or something then as ryant001 suggested, because retail disks work fine without updates. BCA seemed to be side stepped in 360 and Wii scenes by relocating it.. Wonder if anything like that's possible in our situation.

[Cheesethief]

Originally Posted by Mistawes True, noticed a few games that seem to have that check alright. But if we burn to disk, doesn't that negate that side effect? Just curious, because it'd hardly give that error if it's reading from disk, or would it end up as a signing error because it only expects Fself's to be on there? Gonna see if any of the lads have a BR burner to test it out (I presume I'm wrong and it's already been tried 100 times, but better than nothing).

Going a tad technical: Retail game discs are "stamped" and have sectors on them that a regular BD-R writer cannot write to on a BD-R. No matter how many times you try, you will never get a 1:1 match to a BD game disc.

Writable blank discs have a "dye/solution" that imitates lands and grooves. Retail "stamped" discs have actual lands and grooves etched into the disc itself. (Hence the color differences between a writable disc and a regular retail disc. Reflective foil and plastic Vs. Reflective foil, dye, and plastic. Retail discs are also a bit more reflective, because they do not have a dye, which keeps the laser alive a little longer. Poor quality dyes make reflection more difficult which makes the laser work harder). Cheaper dyes also have a higher chance of a bad write (coaster).

[Mistawes]

Originally Posted by Cheesethief Going a tad technical: Retail game discs are "stamped" and have sectors on them that a regular BD-R writer cannot write to on a BD-R. No matter how many times you try, you will never get a 1:1 match to a BD game disc.

I'm well aware, but that's why I was wondering about relocating it, so it's still found when the PS3 is looking for it. Although 3.56+ DEX OFW means not much allowance for messing like that I suppose.

[Cheesethief]

Originally Posted by Mistawes I'm well aware, but that's why I was wondering about relocating it, so it's still found when the PS3 is looking for it. Although 3.56+ DEX OFW means not much allowance for messing like that I suppose.

I am pretty sure it would look for the data in the sector that it is supposed to be and not somewhere else.

This is why XGD3 discs on the Xbox 360 requires a special DVD-DL writer with custom firmware in order to write to usually unwritable sectors. (Lite-On iHAS124 to iHAS624 with hardware Rev. B flashed with iXtreme Burner Max firmware).

There is a work around for XGD3 without having iXtreme Burner Max compatible drive, but it will be instantly noticed the Microsoft if you go online and the discs don't always work without error.

[Mistawes]

But isn't that for the extra space they now need for the bigger capacity XGD3 games? I can't remember where I read it (I think they were explaining the whole "it's detected as a video" thing), but I was sure the BCA for XGDs was moved to an area where standard drives could write to, **and was dumped from disks and maintained by the likes of ABGX.** When the disks increased in capacity, boom: we need iHAS (which I do indeed have! )

I was thinking if hypothetically E3 wanted to get a load of disks pressed, could they not re-create the originals, but after reading the ps3devwiki it seems the PIC zone is gonna be a problem. Ah well, was interesting to think about!

** Not 100% sure about this part, just assumed.

I'll stop spamming this thread now, I promise! lol

[Warrorar]

my idea was it to change the version number of the hdd game to 0.99 and use the real eboot with version id 1.00 as update eboot.

so the ps3 is thinking "okay, gamedisc 0.99, update version 1.00, this is an update, i let it pass and they can play".

but i wasnt succsessfull.

[doggie721]

Here how the BD Emulaor-Patch Boot games Work

Patch-Overview_e.pdf



Processing of the Patch Program
The processing performed by EBOOT.BIN from the patch package, which is booted as a patch, is usually
very similar to that of EBOOT.BIN booted from a disc.
Program files other than data files or EBOOT.BIN can be read from a disc, in the same manner as when
EBOOT.BIN is started up directly from the disc. If a revised version of these files is included in the patch,
they should be accessed using the pathname (usrdirPath) passed from the game content utility (in other
words, when revising data files or program files other than EBOOT.BIN, the patch package must be
distributed with a revised EBOOT.BIN as well, to ensure that the revised data files in the game data
directory are read).

[Warrorar]

thakns for the link doggie,

i was now able to unpack the eboot.bin of facebreaker and repack it with an npdrm signing.

but when i install the fake update on my debug ps3, i get this error

ErrorName: SCE_NP_DRM_ERROR_FILENAME
ErrorCode: 0x80029533
ErrorDescription: Extension of the NPDRM file is invalid, or filename was changed after installation (only encoded NPDRM files)

can someone tell me whats exactly wrong? because i didnt changed any filename.