Memory overlap error

Discussion in 'Wii - Backup Loaders' started by wii_newbie, May 27, 2013.

  1. wii_newbie
    OP

    wii_newbie Member

    Newcomer
    18
    0
    May 7, 2013
    Canada
    Hi. I had an issue with new wiimote. I was advised to update cfg usb loader to r51; and it fixed wiimote issue. You can follow my wiimote issue(now resolved) here.

    http://gbatemp.net/threads/cfg-usb-loader-and-wiimote-issue.348507/

    Now, when I try to launch a game, I get "memory overlap" error.
    When I just press any wiimote button(instead of home button to exit) and go through the error 3 times, the game then launches. Prior to the update(r51), I never got an error. Is there any way to fix this issue?
    Again, games do launch after going through 3 error messages, but it is kind of annoying this way. Thanks

    Update: If it helps, this is exact error message that I am getting

    Booting game, please wait...
    IOS(249)
    IOS Reload: Blocked
    Loading....ERROR: memory overlap!
    dest: 0x812019c0 - 0x812019e0
    used: 0x80a8000 - 0x8132d160
    Press Home button to exit.
    Press any button to continue.

    So after pressing any button and go through the error 3 times, the game launches.
     
  2. icebrg5

    icebrg5 GBAtemp Addict

    Member
    2,326
    41
    Apr 1, 2007
    United States
  3. wii_newbie
    OP

    wii_newbie Member

    Newcomer
    18
    0
    May 7, 2013
    Canada
    Hi icebrg5
    Here is my syscheck

    Edit: syscheck edited out for privacy, since the problem is resolved now.
     
  4. icebrg5

    icebrg5 GBAtemp Addict

    Member
    2,326
    41
    Apr 1, 2007
    United States
    I know cfg loader has auto load cios feature which uses the best cios based on what the game normally uses.

    You only have cios 249 and 250.

    This is what i use these are all d2x v8 final.You can get them with modmii.

    245(37)
    246(38)
    247(53)
    248(55)
    249(56)
    250(57)
    251(58)

    I also use

    202(60) v.51R
    222(38)v4
    223(37-38)v4
    224(57)V5.1R

    You can get those with modmii as well.


    Try installing those and see if you still get the memory errors.
    I'm thinking it could be trying to auto load a cios with a base of an ios that you don't have a cios for.
     
  5. wii_newbie
    OP

    wii_newbie Member

    Newcomer
    18
    0
    May 7, 2013
    Canada
    Hi icebrg5.
    I configured my cfg usb loader to start from 249.
    The installation guide said I can do this by adding <arguments><arg>ios=249</arg></arguments> to meta.xlm.
    I can confirm this by looking at the lower right corner while cfg usb loader loads. Because prior to adding above line to meta.xlm, it displayed "auto". But ever since adding that line, it explicitly displays "249".

    I had no error prior to using r51, so I am sure that I have all required cIOSs.
    Like I mentioned earlier, games still work, but it is just that I have to go through the error message 3 times before games launch. So it is strange.
     
  6. wii_newbie
    OP

    wii_newbie Member

    Newcomer
    18
    0
    May 7, 2013
    Canada
    I think I got very lucky. Since many people have been very helpful, I thought I can contribute back by sharing what I have just found.
    While looking at the installation manual, I added these lines(thought it could be useful feature) since I am tinkering with config.txt anyways.

    music = 0
    write_playlog = 1

    Now, the problem is gone :)
    Everything working perfectly without error message again.

    So, if anyone else is having a similar problem, try adding those lines.
    Thanks everyone :)
     
  7. icebrg5

    icebrg5 GBAtemp Addict

    Member
    2,326
    41
    Apr 1, 2007
    United States
    Glad you got it worked out.
     
  8. SpewHole

    SpewHole Newbie

    Newcomer
    5
    0
    Jan 23, 2013
    United States
    Sorry, old thread, but were you by any chance using a 3 TB hard-drive when you were experiencing the issue? I am experiencing the same issue and I believe it may be related to 3 TB HDDs.

    I tried your suggested solution, but adding those commands did not eliminate the error messages for me. Would you mind copying and pasting the entire contents of your config.txt into the thread? I'd like to compare your settings to mine to see if there is something else unique that might be responsible for preventing that error message. Thank you.