On 09/10/2007, Geert Uytterhoeven <[EMAIL PROTECTED]> wrote:
>
> On Mon, 8 Oct 2007, Ranulf Doswell wrote:
> > However, in this case the only data required is a single identifier used
> to
> > identify one PS3 from another, and in fact this single 64-bit token can
&
On 08/10/2007, Geoff Levand <[EMAIL PROTECTED]> wrote:
>
> > How do we go about claiming one of these OS_AREA_DB_OWNER_ keys? I'd
> > very much like to use this functionality in my python-ps3 games library.
>
> It sounds like you should be storing your info in the file system like
> all other appli
On 08/10/2007, Geoff Levand <[EMAIL PROTECTED]> wrote:
>
> Ranulf Doswell wrote:
> >
> > As these values are correctly populated by the hypervisor from the
> > preferences on the standard PS3 OS, it is incredibly useful to have this
> > information available.
use DHCP, which may well not be
available in every case.
Please can we have these fields back? They don't actually take up all that
much room, yet they are incredibly useful.
--
Ranulf Doswell
One of the major reasons for the downfall of the Roman Empire was, lacking
zero
On 06/10/2007, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
wrote:
> enum os_area_db_owner {
> OS_AREA_DB_OWNER_ANY = -1,
> OS_AREA_DB_OWNER_NONE = 0,
> OS_AREA_DB_OWNER_PROTOTYPE = 1,
> OS_AREA_DB_OWNER_LINUX = 2,
> OS_AREA_DB_OWNER_PETITBOOT = 3,
> OS_AREA_DB_OWNER_M
> > Since 720p is a broadcast mode, I can't make it default to fullscreen,
as a
> > part of the image will fall off on most monitors.
> Do you have any info from the EDID block that would tell you whether the
> monitor displays the full picture (typical of flat panels) or not ?
That's not alw
