Announcement

Collapse
No announcement yet.

Problems with 48x burning

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Problems with 48x burning

    Hey...

    I'm having problems lately with burning CDs with 48x speed. Both DiscJuggler and Alcohol 120% will always suffer from an empty buffer and pause burning (burn-proof);
    INSERT INTO `portal_posts_text` VALUES
    and then either continue with max speed or sometimes with only 24x.

    Can anyone confirm these problems? It can definitely not be my hardware as I haven't changed anything lately and I was able to perfectly burn with max speed (48x) from the first to the last sector some time ago...

    Now I get buffer underruns over and over when trying to copy on-the-fly, and sometimes during the burning process from HDD. If not when burning from HDD, DiscJuggler will always have problems when finishing the disc - while finishing it will pause burning like when it has a buffer underrun.

    My system specs:

    AMD Athlon XP 1800+
    ASUS A7V333 (VIA KT333)
    512MB RAM 266MHz
    Seagate ST380021A (80GB 7200rpm) primary master
    Toshiba SD-M1612 secondary master
    Lite-On LTR48125W secondary slave

    Windows XP Pro SP1
    VIA Hyperion 4in1 v4.45v (all DMA enabled)

    No firewall/antivirus installed

    Hope I haven't forgotten anything...


    Sergei
    "I was inappropriately blunt, wasn't I? Sorry, I do that a lot."

  • #2
    Check if you have MS Office installed, if the idiotic indexing option fucks up your writing ...
    also check the media you are using ... SMART-BURN will lower the write speed with buffer-underrun-symptoms (yellow LED) in case of bad media ...
    Everybody be cool! You, be cool!
    They'll keep fighting! And they'll win!

    Comment


    • #3
      Nope

      indexing is the very first thing I kick outta autorun after having installed Office, but I don't have it installed anyway

      concerning media:

      TDK Speed-X CD-R80 48x, TDK's so-called "reference CD-R" (0,69)
      Octron 700MB 40x speed (bought at LIDL in germany, 0,39)

      all the same
      "I was inappropriately blunt, wasn't I? Sorry, I do that a lot."

      Comment


      • #4
        Which firmware do you use for the 48125W?
        Do you also get buffer-underruns-symptoms while write simulation/test?
        Everybody be cool! You, be cool!
        They'll keep fighting! And they'll win!

        Comment


        • #5
          firmware vs08

          haven't tried simulating, I'll check it out after a dog-walk
          "I was inappropriately blunt, wasn't I? Sorry, I do that a lot."

          Comment


          • #6
            I tried simulating an on-the-fly-copy of WarCraft III, still got pauses during the burning process - although the Memory Buffer Usage in Alcohol was at >90% at all times, CPU usage <15%...
            "I was inappropriately blunt, wasn't I? Sorry, I do that a lot."

            Comment


            • #7
              Try to disable the Hyperion-Via-Drivers and use default drivers instead (and enable DMA there, too, of course)

              Comment


              • #8
                by the way...

                I installed DirectX 9, is it possible that this causes problems too? Does anyone already know?

                Sorry, I only just remembered, didn't think of it before...
                "I was inappropriately blunt, wasn't I? Sorry, I do that a lot."

                Comment


                • #9
                  New Windows XP installation, no Direct X 9, VIA 4in1 v4.43v, same problem. When trying to burn an Aquanox 2 image Alcohol (1.4.0) paused burning when it had reached about 25x, then continued with 20x until the disc was finished. This SUCKS. :evil: I have not bought a fast computer and a 48x burner and 48x media to burn with 20x.


                  Sergei


                  P.S.: I've made a screenshot of the Performance Graphic (slightly manipulated);
                  INSERT INTO `portal_posts_text` VALUES
                  you can have a look at it here (~36kb). The CPU usage being at 100% is caused by a running SETI@home client I shut down then.
                  "I was inappropriately blunt, wasn't I? Sorry, I do that a lot."

                  Comment


                  • #10
                    Strange ... looks like SMART-BURN thinks bad media detected and reduces write speed ... you have DMA enabled?
                    Everybody be cool! You, be cool!
                    They'll keep fighting! And they'll win!

                    Comment


                    • #11
                      yup... and as I said, I'm using TDK's reference media - have tried with cheapest discount media as well, cannot be that, I guess... Or let's say it can't be the media, it's possible that SmartBurn's f*cked up...


                      ...just checked, DMA mode 2 activated automatically by OS. By the way, the burner's jumpered as slave although there's no master, but that shouldn't make a difference in this case, should it?
                      "I was inappropriately blunt, wasn't I? Sorry, I do that a lot."

                      Comment


                      • #12
                        Well, disable SMART-BURN and try again ... since the 32x drives buffer underrun protection is always enabled, so donґt worry
                        Everybody be cool! You, be cool!
                        They'll keep fighting! And they'll win!

                        Comment


                        • #13
                          oh, cool to know - i will...
                          "I was inappropriately blunt, wasn't I? Sorry, I do that a lot."

                          Comment


                          • #14
                            Hmm...

                            this is all very, very mysterious...

                            I burned Aquanox 2 CD2 with BURN-Free deactivated, and it burned the ~45min without pause. Fine.

                            Then I took a big image (Max Payne, 80min);
                            INSERT INTO `portal_posts_text` VALUES
                            burned it with BURN-Free activated, yet it burned without pause.

                            After that I was confused, but thought it might be the copy protection - SafeDisc 2 is burned without problems, SecuROM not (Subchannel Data!)?

                            So I tried Aquanox 2 CD1 (again only simulated) which is about 70min long, again with BURN-Free activated - still no problems.

                            I have not changed anything, haven't even rebooted since the last tests (today in the morning);
                            INSERT INTO `portal_posts_text` VALUES
                            yet it seems to work again after I had disabled BURN-Free only once.


                            You see me very confused. I'll try it with DiscJuggler too (which always seemed to be more irritable concerning those problems) and report later, but so far it looks like the problem's solved. I don't get it. :?

                            Thanks for your help, looks like your idea did the trick, Copytrooper - although I bet you didn't think of it as a repair method. :mrgreen:


                            Although this might be slightly off-topic, I gotta say I love this forum, and I am really proud to have the great honor of being a moderator here. You guys are great, all of you! *applause*


                            Sergei
                            "I was inappropriately blunt, wasn't I? Sorry, I do that a lot."

                            Comment


                            • #15
                              Thanks for your help, looks like your idea did the trick, Copytrooper - although I bet you didn't think of it as a repair method.
                              I thought about it as evaluation method, ґcause SMART-BRUN off will disable the media check, so the drive will write with maximum speed even if the media is somehow bad - so if SMART-BURN would cause trouble this should give some info whether it does or not, and if DMA really works, ґcause drive would write slower, if DMA wouldnґt work (thatґs the problem with Win2k/XP btw -> setting is "DMA if possible" only, so you donґt know really if OS thinks itґs not possible).
                              Everybody be cool! You, be cool!
                              They'll keep fighting! And they'll win!

                              Comment

                              Working...
                              X