Liteon burner problem.

leishi85leishi85 Grand Rapids, MI Icrontian
edited October 2003 in Hardware
i have the liteon 52x24x52 burner

whenever i try to bur anything, the buffer goes up and down, and the whole computer feels very sluggish. i check teh task manager, it shows that nero is uing about 80mb of ram, and i still have like 300mb ram free, and with folding disabled, nero uses about 50% CPU usage, it varies

what could be causing this??

Comments

  • Straight_ManStraight_Man Geeky, in my own way Naples, FL Icrontian
    edited October 2003
    Normal if you are burning with anything less than a 1.6 GHz box at over 30X to 40x depending on how fragged the HD is.

    Baicly, can tell you this:

    A 223 MHZ computer can burn at 8X with lots of memory.

    A 600 MHz computer can burn at 12x to 16x with lots of memory.

    A 1.3 GHz Durnon with 256-512 MB can burn at 20-38x depending on RAM speed and whether it is 1\4 to 1\2 Gig of RAM.

    A Barton can burn at 32-36x LIVE relaibly with Nero 6.

    A P4 2.26 GHz running Linux with a GIG of RAM can burn at 24x-28x.

    Burner is burning faster than computer can feed if you are getting coasters, and many computers do not have the other resources in RAM and CPU speed and HD spare space that is defragged to burn as fast as CD-RW can take data. Then you get wild buffers as you apporach the edge of what the computer can do to support burning OTHER than have a CD-RW installed.

    Let's say your buffer is going to 80% or better and then suddenly appearing full. What happened is the data feed was slower for a bit of time than the CD-RW could burn and was set to burn as far as rate goes. Anything over 80% minimum buffer full in a burn is normal, lots less and you are buring too fast or with media the burner does not like, or the HD needs defragging so windows does not have to hunt image pieces, or the RAM available is not enough and Windows is using the HD a lot.

    SO, if the HD is constantly churning during burning try defragmenting it before next burn and see if you can burn at same rate more stably. If not, look into more RAM or change brands of blank CDs and get better quality CD blanks and consider cleaning the lense of the CD-RW especially if you got it used or refurbed.

    Nero 6 is better than Nero 5 on fast computers, and is better on most modern burners than Nero 5.5+ also. I have had issues with Nero 5.5 that vaporized when switching to Nero 6 on same boxes (plural, all faster computers).

    John.
  • JBJB Carlsbad, CA
    edited October 2003
    is this a direct cd to cd copy? if so you could try having it image to the HD first, which may lower the load on the CPU.
  • WuGgaRoOWuGgaRoO Not in the shower Icrontian
    edited October 2003
    hmm..i used to have a 12x burner with a 450mhz machine and i didnt have ne problems
  • EnverexEnverex Worcester, UK Icrontian
    edited October 2003
    I have a Yamaha that works fine at 40x on an old Athlon 500mhz with 192MB RAM.

    NS
  • leishi85leishi85 Grand Rapids, MI Icrontian
    edited October 2003
    not direct cd or cd copy, just burning cd images and movies and what not.

    i ask this is because it never happened beofre, it just started doing this recently, and i'm sure my computer can handle 52x burning speed.

    2.5gh athlon xp. 512mb ram
    and etc.
  • leishi85leishi85 Grand Rapids, MI Icrontian
    edited October 2003
    forgot to add, all teh games i burned it works, but when u install them about half way through, it says data corrputed.

    but the image works fine if u use daemon tools to load it.
  • Geeky1Geeky1 University of the Pacific (Stockton, CA, USA)
    edited October 2003
    Sounds like a software problem to me. Try uninstalling and reinstalling the burning software, patching it, and if all else fails, the usual solution (format & reinstall) may be the only solution.
  • leishi85leishi85 Grand Rapids, MI Icrontian
    edited October 2003
    ok i think i found the problem, my burner was in PIO mode, but i try to change it it wouldn't work, and i already tried reinstalling the driver, it didn't work either, here is a screenshot.
    ide.jpg 31.4K
  • EnverexEnverex Worcester, UK Icrontian
    edited October 2003
    Check your BIOS and make sure DMA mode is enabled under advanced options.

    NS
  • leishi85leishi85 Grand Rapids, MI Icrontian
    edited October 2003
    it was enabled.
    ahh:mad: stupid burner.
  • leishi85leishi85 Grand Rapids, MI Icrontian
    edited October 2003
    BUMP<

    i think this is a driver problem, soneone got a fic or idea for this??
  • leishi85leishi85 Grand Rapids, MI Icrontian
    edited October 2003
    for anyone that cared, i fixed it

    here is what i did.
    i opened my case and switch the dvd to ide 1, and burner to ide1, and booted into windows, and windows detected new drives, and loaded them up correctly, and now both of them are running UDMA2 instead of fugly PIO. yah!!
  • JBJB Carlsbad, CA
    edited October 2003
    good to hear!
  • LeonardoLeonardo Wake up and smell the glaciers Eagle River, Alaska Icrontian
    edited October 2003
    Good! :thumbsup:
  • ThraxThrax 🐌 Austin, TX Icrontian
    edited October 2003
    I knew it was DMA.
  • profdlpprofdlp The Holy City Of Westlake, Ohio
    edited October 2003
    If Windows encounters a problem reading a CD more than a couple of times (even if it's just a screwed-up disc) it will switch the drive to PIO mode. The easiest way to correct it is to boot into safe mode, delete your CD drives, then let Windows find them again. What you did accomplishes the same thing, but this way you don't have to open the case and fiddle with the cables.

    This is a sore spot for me. :werr: I thought I was on the way to 1337 geekhood by being the first guy to come up with a registry patch to do it instantly. (Windows just flat-out won't let you just re-enable DMA in this case.) I did a registry backup, then inserted a coaster (hey, we all have a few of those lying around...). The drive thrashed around for a while trying to read the bum disc. Then, voila - PIO mode! I then did another registry scan and compared the before and after scans. I figured I could just export the key that changed from the before (DMA enabled) registry and have a quick hot-fix to do it painlessly.

    Didn't find jack... :shakehead

    Maybe I'll try it again with a different registry comparison program.
Sign In or Register to comment.