Hi Cambridge Chris !

Some of the threads I've read seem to point to the way a drive is connected.

For Internal Drives, it seems to be the Master/Slave Jumper and/or the Position on the Cable.

For External Drives, it may be the USB Port used.

One of my Flash Drives had a program that ran when it was connected and it recommended using a different USB Port.

When I connected the Flash Drive to a different USB Port, the program ran again and said this was a better port!?!?!

One Forum User thought he had an HP LS Drive because it had the LS "swoosh" on the front of the tray, but when he popped the tray out it didn't have the LS Sensor near the hub.

It took about 6 months for HP to send him a good replacement because their Database was wrong.  Once they sent him the same model drive again.

This LS Sensor is what looks like a fixed LED Block that reads the LS Marks on the LS Disks.

These Marks are used for Media Detection, Positioning, and Timing.

So pop the tray out and make sure it has the LS Sensor.

There's a picture in the "Knowledge Base" under the "LightScribe Toolbox."

Only LightScribe drives sold as a complete external drive are currently qualified and supported.
Many third party external drive cases have not been tested and may work normally for data but not for LightScribe labeling due to communication protocol conflicts with some interface hardware sets.

Still, your drive is made by HP, and LightScribe is an HP subsidiary!

So it should work!

Except for the one drive I mentioned, I've only seen one or two problems with HP drives!

Hi Hagrid !

I worked my way through 2 - 4231 Error after over a year without any problems.

Here are the steps I had to take.

Maybe the can help you find your problem.

I'm using an HP Pavillion dv9825nr Notebook PC, running Windows Vista Home Premium SP1+.
I also have an HP PhotoSmart C8180 All-In-One Printer.  Both have built-in LS Drives.
Everything has been running LSS fine since 4/08.

I had 2 Instances of the LS TL running;
The one which had the highest percent done got a 4231 Error;
Both labeling processes stopped;
I rebooted the system several times;
I ran both the LS_Update and the Diagnostic Install in repair mode and rebooted the system again;
The DU would "Not Respond" until I popped the tray in my system out and pushed it back in;
The DU would not recognize the media in my printer's drive until I popped the tray out and pushed it back in;
The DU would not recognize the drive in my system until I told it to "Scan for LightScribe drives and media" again;
I tried to restart the First Instance (the one in my system)  and got a "(520)" Error saying there might be dirt or a smudge on the disk and to wipe it;
It gave me the options "Help" "Cancel Print" "Try Again";
The "Help" option brought up the "Troubleshooting" webpage;
I wiped the LABEL side (nothing had been burnt) and selected "Try Again";
The burning process started again;
I waited until the First Instance finished;
It finished successfully;
I restarted the Second Instance;
I got a "(4225)" Error;
It gave me the options "Help" "Cancel Print";
I selected "Cancel Print";
I restarted the Second Instance again;
It restarted successfully;
I waited until the Second Instance finished;
It finished successfully;
I started 2 new Instance again both running at the same time;
They both finished successfully;
I started a new First Instance when the Second Instance was at 40%;
The Second Instance finished successfully and was shut down;
The First Instance got another 4231 Error, but was left up until the Second Instance finished successfully;
Only a small portion (about 10%) of the label had been burned;
I rebooted the system and wiped the LABEL side surface;
I restarted the LS TL and selected the same LSL File and restarted the burning process;
It started burning and got beyond 10%;
It finished successfully.

CONCLUSION:
The effected disks were Memorex LightScribe V1.2;
The drives got "hung-up" possibly due to dirt or a smudge on the LABEL side surface;
Wiping the LABEL side surface with a dry cloth helped "fix" the burning problem;
As several Users on the Forum attest, it appears most of the problems in the LightScribe Template Labeler seem to happen in the burn process.

REV. 2009-11-30 0850 EST

I'm using an HP Pavillion dv9825nr Notebook PC, running Windows Vista Home Premium SP1+.
I also have an HP PhotoSmart C8180 All-In-One Printer.  Both have built-in LS Drives.
Everything has been running LSS fine since 4/08.

I was attempting to burn a simple 2 Arc Text Item Label.
I received a 4231 Error at 37% and had to "Cancel Print."
The "Simulated Visual Label Progress (estimate)" showed approx. 50%.
The process started again.
The process completed successfully and the label was OK.

REV. 2009-12-17 1235 EST

Good day,

I had the same error, tried everything suggested, i resolved my problem by: i had a lexmark printer connected that was on, i simply swithed the printer off while doing the lightscribe burning process since then did not had the problem again. Worth a try

cheers

I have to agree with you totally. I have never been so disappointed in an HP product as I have this lightscribe that came with my HP Pavilion a6400z desktop, running WindowsVISTA, which I positively hate even worse then the lightscribe drive.  I made sure and bought the correct discs as I bought them through the HP.shopping.com site. And, I"ve not been able to make a single label. And when I tried to get HP to help me, the tech told me that this was a third party item and they couldn't help me.  BS.

GOD BLESS TO ALL