RSS Feed Print
Error 4231 -- HP tech support unable to help
josiecat65
Posted: Wednesday, December 9, 2009 6:57 PM
User Rank: Newbie
Joined: 12/8/2009
Posts: 2


I bought an HP 311 Mini netbook running XP with an external lightscribe CD/DVD drive.  I have been trying to print a label for 3 days.  I have researched this issue on this website, Hp's website and the internet and found no solution that works for me. 

I have uploaded (from Lightscribe and HP)and removed the lightscribe software many times and continue to get the same error. And re-booted like the error messages states.  It has yet to work even once.  I am using HP lightscribe CD-R discs.  I even tried a different disc and cleaned it off as one user did.

I was on the phone with HP technical support for 3 1/2 hours last night and they had no idea what the problem was.  She did everything several times like I had done.  She also updated my operating system (I just bought it 2 weeks ago!)

It surprises me that there is so little information about this problem. 

 

 


cimofj2
Posted: Wednesday, December 9, 2009 7:06 PM
User Rank: Power User
Joined: 8/3/2008
Posts: 1570


Hi josiecat65 !

I don't know if you've seen this or not.


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


josiecat65
Posted: Thursday, December 10, 2009 4:09 PM
User Rank: Newbie
Joined: 12/8/2009
Posts: 2


I did see that post. My computer is not having any problems detecting the drive.  I tried wiping the disc and even tried a different disc.  My labeler does not even get through any percentage of labeling before I get the 4231 error.

I tried the diganostic tool and it didn't detect any problems. 

There seems to be very little support beyond forums for this product.