M3/Sakura help

Discussion in 'M3 Adapter' started by albel005, Sep 2, 2008.

  1. albel005
    OP

    albel005 GBAtemp Regular

    Member
    173
    0
    Dec 21, 2007
    United States
    when i load up my cart now i get

    An error was dectected while trying to access the disc or file please confirm the following

    and then it gives a list how am i suposed to find out which file is the problem
     
  2. Toni Plutonij

    Toni Plutonij *has TrolleyDave & tiny p1ngy on moderating shelf!

    Former Staff
    8,153
    314
    Dec 22, 2007
    Croatia
    Depths of Nuclear powerplant
    You're not supposed to find anything..
    Just backup your data on PC, format card, copy SYSTEM folder back, then other stuff (be sure to copy Sakura firmware first!!)..And that'll probably fix your problem.. [​IMG]
     
  3. albel005
    OP

    albel005 GBAtemp Regular

    Member
    173
    0
    Dec 21, 2007
    United States
    nope didn't help
     
  4. albel005
    OP

    albel005 GBAtemp Regular

    Member
    173
    0
    Dec 21, 2007
    United States
    that list reads

    Was the rom of a correct DLDI patch started
    Please reformat the media and try again
    Please try with different media from another manufacturer
     
  5. Toni Plutonij

    Toni Plutonij *has TrolleyDave & tiny p1ngy on moderating shelf!

    Former Staff
    8,153
    314
    Dec 22, 2007
    Croatia
    Depths of Nuclear powerplant
    Do you have some homebrew on?
    It seems that some files you copy are fragmented..

    Try to check your microSD with Disk Defragmenter on PC....
    Click right button on microSD>Properties>Tools>Defragment Now, Choose your microSD and click Analyze..
    If everything's blue, then something is wrong either with Sakura firmware, or M3 Real..If you have red parts, that means you've got fragmented files on, and you have to format your card, and copy one file at the time, checking with Disk Defragmenter if everything is OK, once you get everything blue....You'll probably be set to go..
     
  6. cflemin301

    cflemin301 Member

    Newcomer
    33
    0
    Jul 21, 2006
    United States
    I read on a forum somewhere that
    Disk Defragmenter drastically
    decreases the lifespan of a microsd
    (or any Memory Card, for that
    matter). copy over the homebrew and roms
    to hard drive, format, copy SYSTEM folder
    to microsd, recopy roms/homebrew to
    microsd, then play. i tried to use Disk
    Defragmenter but it corrupted my
    microsd sooooo bad it became completely
    useless. STAY AWAY FROM DISK DEFRAGMENTER
    ON MEMORY CARDS!
     
  7. Toni Plutonij

    Toni Plutonij *has TrolleyDave & tiny p1ngy on moderating shelf!

    Former Staff
    8,153
    314
    Dec 22, 2007
    Croatia
    Depths of Nuclear powerplant
    No man.....I didn't want you to defragment your card..I wanted you to ANALYZE it..I'm doing it all the time, it won't do anything but read it and display the result.....but don't defragment it.....if it's red, format the card!!

    I never said to defragment card.. [​IMG]

    Sorry if you messed badly....but you could probably format it with mobilephone, or some other OS if windows can't read it anymore.. [​IMG]
     
  8. 11gardir

    11gardir GBAtemp Regular

    Member
    150
    0
    Feb 2, 2008
    Interestingly, I always get the

    Was the rom of a correct DLDI patch started
    Please reformat the media and try again
    Please try with different media from another manufacturer

    message, but my card works fine.
     
  9. thedicemaster

    thedicemaster GBAtemp Addict

    Member
    2,428
    15
    Apr 26, 2008
    Netherlands
    that message is there because a dldi error causes a full freeze.
    if the dldi system works fine it flashes into the screen for a sec and then continues booting m3sakura.
    if the dldi system encounters a problem the software crashes while it's on that screen, causing it to be frozen on that error screen.
    the software simply isn't capable of generating an error message on screen is a dldi error occurs, so it generates the screen before the error can occur, and then removes the screen when it passed the point that can cause problems.