imgburn - is this normal?

Discussion in 'Wii - Hacking' started by pottageb, Mar 18, 2007.

  1. pottageb
    OP

    pottageb GBAtemp Regular

    Member
    174
    0
    Aug 27, 2006
    heres my log from the wiikey confic disc:


    What's with all the waiting for buffers to recover etc...

    thanks
     
  2. thegame07

    thegame07 GBAtemp Psycho!

    Member
    3,860
    103
    Oct 16, 2006
    i keep getting that when i burn ps2 games [​IMG] no problems with any of my burns [​IMG]
     
  3. Pikachu025

    Pikachu025 GBAtemp Advanced Fan

    Member
    969
    29
    May 3, 2006
    Australia
    Austria
    Seems like your DVD-drive is requesting data faster than your HDD can provide it. Do you have anything that accesses the HDD running in the background?
     
  4. thegame07

    thegame07 GBAtemp Psycho!

    Member
    3,860
    103
    Oct 16, 2006
    it only started happening to me when i started using my sh** pc. :'(
     
  5. pottageb
    OP

    pottageb GBAtemp Regular

    Member
    174
    0
    Aug 27, 2006
    thanks, ill let you know if my burns work when my chip arrives
     
  6. thegame07

    thegame07 GBAtemp Psycho!

    Member
    3,860
    103
    Oct 16, 2006
    i think you will be ok. all of my burn are fine not had one bad burn yet. [​IMG]
     
  7. 111111111

    111111111 GBAtemp Advanced Fan

    Member
    516
    0
    Jan 8, 2007
    Your dvd drive is constantly buffer underrunning.

    16mins to write a dvd - with an average speed of 1x is terrible. The disc is going to be full of burnproof (or similar) links, which means the quality is not as high as a properly written disc.

    Make sure dma is enabled on the ide controller that the hard drive and the dvd drive are connected to. If they are on the same controller, put them on seperate controller. Add more ram as a buffer in the imgburn options (if you have a gig of ram or more set it to 256mb/the max it will go.

    Every 30 seconds your hard drive is churning and is unable to pass data to your dvd drive - you've obviously got something running that is accessing your hd (totally thrashing it too), for ~15 seconds.