Forum: multiMAN - Discussion related to the wonderful multiMan multifunctional tool for your PS3 by DeanK!


The above video goes away if you are a member and logged in, so log in now!




 
Would you like to get all the new info from
PSX-Scene in your email each day?




Want to learn more about the team keeping you up to date with the latest scene news?

Read about them now!

Check out our Developer bios, too!

 


User Tag List

Thread: Using all 3 managers installed Gaia 2.05 - Multiman 01.13.04 - Rogero 7.9c (READ INSIDE)
  

Results 1 to 2 of 2
  1. #1 Using all 3 managers installed Gaia 2.05 - Multiman 01.13.04 - Rogero 7.9c (READ INSIDE) 
    hanzy77 is offline Registered User
    Join Date
    Nov 2010
    Posts
    5
    Downloads
    0
    Uploads
    0
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Likes Given
    0
    Likes Received
    0
    I just noticed a bug (possible one) and would like to share it. My setup is a Phat 60GB PS3 - 3.55 Kmeaw's cfw. This will probably work with other setups. Anyway, here is what happens:-

    When booting up Gaia and Mulitiman, Gaia shows Discless as N/A which is correct since its not supported in 2.05 and using syscall36. Multiman shows PSgroove payload, which again is correct.

    However, if you boot up Rogero that shows the payload as PL3, which again is correct as its still using lv2 patcher if am correct, yet if you quit out to the xmb and boot up gaia again, the discless mode does not show N/A (L1) and you can enable it. Also, multiman will show PL3 instead of Psgroove.

    Am guessing that booting Rogero first is enabling the lv2 patch in RAM hence why the other two managers cancel out their options that they were originally programmed to do, as to rectify this, the user must reset the console.

    Just thought I'd share it with you guys and see what you think!!!
    Reply With Quote  

  2. #2  
    im bored is offline Member
    Join Date
    Oct 2010
    Posts
    20
    Downloads
    14
    Uploads
    0
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Likes Given
    0
    Likes Received
    0
    That's not a bug. I would make sense that it would do that you can achieve the same situation by loading OMG Lv2 Patcher, and also MM didn't get rid of that option PL3 can still be enabled in the .ini file.

    If you notice this is a portion of the .ini file

    # Option: load_custom_payload
    # Hint: Load payload (FW 3.55)
    # Valid Parameter: <option has no effect>
    # load_custom_payload=0

    To get PL3 working again all you have to do it this

    # Option: load_custom_payload
    # Hint: Load payload (FW 3.55)
    # Valid Parameter: <option has no effect>
    load_custom_payload=1
    Reply With Quote  

Posting Permissions
  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •