1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

PS3 Browsing

Discussion in 'Troubleshooting and Problems' started by stevieboy, Mar 14, 2011.

  1. stevieboy

    stevieboy New Member

    HI there, we have a ps3 gaming forum oldskoolgamers.co.uk however a few members can't use our site on their ps3, as all they get is errors. We can get the forum up but look at a post but if you try post, it comes up with errors or just a blank page.

    Any help would be much appreciated

    cheers stevie
  2. Brogan

    Brogan XenForo Moderator Staff Member

    Are they able to get the user agent string of the browser?
    That might help to isolate the problem.

    Is there anything in common with the affected consoles?
    Firmware version, software version, cracked, etc?
  3. stevieboy

    stevieboy New Member

    looks look its a Sony issue, being rather outdated

    The PS3 uses the NetFront browser from Access and as stated, it can only be upgraded by Sony in a Firmware update.
    Based on the "X_PS3_BROWSER" http header ("3.10 (WP; system=3.56)", which the browser sends to web sites when you request a page, it is most likely using version 3.1. The curernt version of the NetFront browser is 4.1, which has 20x faster JavaScript.
    ThinkPad T61 (2GB / 2.4GhZ dual core),
    PS3 (256MB), PS2 (32MB), PS1 (2MB)
    Commodore Amiga (512k), Amstrad PC-1512 (512k --> 640k + Nec-v30),
    Atari 800XL (64k), Atari 400 (16k), Commodore Vic-20 (3k).
  4. Brogan

    Brogan XenForo Moderator Staff Member

    Considering the PS3 was designed to be used online, you'd think they'd make the effort to at least make it usable.
  5. stevieboy

    stevieboy New Member

    Exactly, just have to wait and see if Sony gives us a upgrade at some point in the future.
  6. Luke F

    Luke F Well-Known Member

    Might be an idea for XenForo to automatically disable Javascript when the PS3 browser is detected (or any other NetFront browser, such as on the PSP).

    Assuming the problem is Javascript-related and not some rendering quirk.

Share This Page