50+ views, no one has suggestions ???
Is this the same burner that you said was working so well in Stomp RecordNOW Max? (Or maybe you are using Prassi PrimoDVD which is basically the same as RecordNOW.) Remember how we discussed the fact that the LTR-48125W isn’t supported in the Prassi engine of RecordNOW?
I wonder if there’s even the slightest chance that RecordNOW caused a LiteON failure since the drive isn’t supported in that software? I realize this is an extremely remote possibility. But, I will always wonder, nevertheless.
But, let’s move onward …
If I read your post correctly, you are talking about failures using a “cue” image and a failure burning a VCD. Looks like you tried Nero and CloneCD for the image and looks like you used Nero for the VCD.
Maybe the image is corrupt? Maybe there’s an encoding fault in the video files that cause Nero to stop writing properly?
How does the drive work when you master a data CD? How does the drive work when you master an audio CD? Does it work okay in those instances? Maybe you just have a corrupt disc image and some corrupt video files?
Let’s exclude CloneCD for the moment because it could just be a bad image you are trying to burn.
Does this burner work okay for data and audio burns using other software instead of Nero? If the LTR-48125W only fails in Nero, I would suspect a corrupt installation of Nero.
If the LTR-48125W fails to burn properly when using several different CD mastering software packages, I would certainly consider the LiteON drive as possibly the failed component.
First I would try different software packages to write a disc. If the burner writes properly using software other than Nero, I would consider the LiteON has possibly failed.
But, you say you use Windows XP Pro? I have XP Pro, but, I dont’ use it. XP Pro seems to cause a number of problems with CD burning and I don’t want to deal with those problems.
Adaptec built the CD burning engine of Windows XP Pro and I think they have caused more problems than they know how to fix. Each update for the CD Burning engine of XP Pro just seems to send more users to forums looking for new fixes for new problems. Each time I read the sad posts from XP Pro users, I decide that Windows XP Pro is not yet ready for me.
So, let’s eliminate XP Pro from this equation for the moment because there could be so many problems in XP Pro. XP Pro could suffer from ASPI problems, and burning engine problems. I’m hearing of both in newsgroups and forums.
Guess what? Adaptec/Roxio wrote the ASPI engine and the CD Burning engine of XP Pro. See the common denominator? Adaptec/Roxio is ruining CD burning fun for lots of people.
So, let’s eliminate XP Pro from the equation. You specify Windows ME as one of the operating systems that you can use.
I don’t use Windows ME either, so, I can’t remember: Does Windows ME include an ASPI layer? Or do you have to install one?
If Windows ME includes its own ASPI layer, that’s a good thing. Maybe it’s the trusty and reliable version 4.60?
Nero has its own engine, but, conflicts can arise.
If you can verify that ASPI 4.60 is installed in Windows ME (or whichever ASPI version is appropriate for Windows ME), then I would turn off AIN (Auto Insert Notification) [also known as “autoplay”]. Then reboot.
Now, with AIN turned off in Windows ME, try burning with Nero. If it now fails, you could strongly consider the LiteON drive as failed.
But, go one step further. Try other CD mastering software packages in WindowsME.
Now, if the LiteON fails to burn properly using software other than Nero in Windows ME, my opinion is that the LiteON has certainly failed and it’s time to exchange it for a new one as soon as you can.
One last thing you could try: Re-flash the LiteON drive with the latest approved firmware available from the LiteON web site. I would guess that there’s a chance that the firmware instructions on the chip in the LiteON could be corrupt. Before I went to the trouble of returning the drive, I would try one properly executed flash procedure to see if things improve.
If you insist on using WindowsXP Pro, try turning off all the automatic stuff for the LiteON drive where XP Pro will automatically do this and that for images, audio, data, video, and so forth. Essentially, you will be turning off “autoplay” for all situations for the LiteON drive.
Or, better yet, search the web (Google is good) to find out how to truly disable the built-in CD burning engine of Windows XP Pro. This must be accomplished from the Registry and/or from the Policy manager and/or from the Services manager.
If you simply turn off the “automatic stuff” for each drive, you have only disabled the features. The “engine” still exists as a troublesome component. You must modify the registry, the policies (which will alter available services), and you must also delete some core Windows files in order to truly disable the built-in CD burning engine of Windows XP Pro.
Once you truly disable the CD engine of XP Pro, I think you will find that all of your 3rd party CD mastering software willl perform better.
(As I remember, you can’t disable the engine if you plan to use Roxio softare. But, if you use any other 3rd party software other than Roxio, you can disable the built-in CD burning engine of XP Pro with great results.)
It’s a rather simple procedure, but, the procedure must be followed accurately. It’s not an appropriate topic for this forum. But, if you will search the web, you’ll find many expert solutions for this common problem.
Me? I find it much easier to just use Windows 2000. Some day I hope an XP Pro service pack will eliminate the conflicts with my 3rd party software. But, Windows XP is not ready for me yet. XP Pro still tries to force my 3rd party software into failure.
With XP Pro, I find that even my flatbed scanner software is sabotaged by the built-in Windows XP graphics imaging engine. I have to disable that “built-in feature” as well.
The list goes on and on. Windows XP Pro just seems to degrade 3rd party software performance when it should be enhancing 3rd party software performance.
But, that’s just my silly little opinion. I’m sure I’ll get some flames on this XP issue. But, while the XP Pro people are constantly installing updates, hotfixes, and work-arounds, I am just happily burning, imaging, and getting work done in Windows 98SE and Windows 2000. I don’t have to spend my time looking for fixes to make a $200 XP-Pro operating system support my 3rd party software.