<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
 <!-- Generated by Ektron CMS400.NET -->
 <channel>
  <title>LightScribe Forum : Drives : Need help with lightscribe engine</title>
  <description></description>
 <item>
  <title></title>
  <description><![CDATA[<P>Hi, I was able to make one lightscribe disc.&nbsp; Then I tried again to burn another one and it told me to place a lightscribe disc in which there was one in the computer.</P> <P>So I tried upgrading the software and Now when I try and burn an image on to the &nbsp;lightscribe disc, I keep getting an error that says there is a problem with the lightscribe engine.&nbsp;&nbsp; </P> <P>I don't know what else to do can someone help please..</P> <P>&nbsp;</P>
<br />]]></description>
  <pubDate>Sun, 29 Nov 2009 21:47:36 GMT</pubDate>
 </item>
 <item>
  <title></title>
  <description><![CDATA[<p>Hi <a href="http://www.lightscribe.com/discussionBoards/index.aspx?g=profile&amp;u=9802"><strong>latinlady910</strong></a> <img src="/WorkArea/threadeddisc/emoticons/cool.png" /> !</p>
<p>I've been labeling since 04/08, but my system started acting funny a few days ago.  I basically worked through a bunch of Errors and now when I labeled a few more disks everything is working fine.</p>
<p>Here is what I went through and the steps I took.</p>
<hr />
<p>I'm using an HP Pavillion dv9825nr Notebook PC, running Windows Vista Home Premium SP1+.<br />
I also have an HP PhotoSmart C8180 All-In-One Printer.  Both have built-in LS Drives.<br />
Everything has been running LSS fine since 4/08.</p>
<p>I had 2 Instances of the LS TL running;<br />
The one which had the highest percent done got a 4231 Error;<br />
Both labeling processes stopped;<br />
I rebooted the system several times;<br />
I ran both the LS_Update and the Diagnostic Install in repair mode and rebooted the system again;<br />
The DU would "Not Respond" until I popped the tray in my system out and pushed it back in;<br />
The DU would not recognize the media in my printer's drive until I popped the tray out and pushed it back in;<br />
The DU would not recognize the drive in my system until I told it to "Scan for LightScribe drives and media" again;<br />
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;<br />
It gave me the options "Help" "Cancel Print" "Try Again";<br />
The "Help" option brought up the "Troubleshooting" webpage;<br />
I wiped the LABEL side (nothing had been burnt) and selected "Try Again";<br />
The burning process started again;<br />
I waited until the First Instance finished;<br />
It finished successfully;<br />
I restarted the Second Instance;<br />
I got a "(4225)" Error;<br />
It gave me the options "Help" "Cancel Print";<br />
I selected "Cancel Print";<br />
I restarted the Second Instance again;<br />
It restarted successfully;<br />
I waited until the Second Instance finished;<br />
It finished successfully;<br />
I started 2 new Instance again both running at the same time;<br />
They both finished successfully;<br />
I started a new First Instance when the Second Instance was at 40%;<br />
The Second Instance finished successfully and was shut down;<br />
The First Instance got another 4231 Error, but was left up until the Second Instance finished successfully;<br />
Only a small portion (about 10%) of the label had been burned;<br />
I rebooted the system and wiped the LABL side surface;<br />
I restarted the LS TL and selected the same LSL File and restarted the burning process;<br />
It started burning and got beyond 10%;<br />
It finished successfully.</p>
<p>CONCLUSION:<br />
The effected disks were Memorex LightScribe V1.2;<br />
The drives got "hung-up" possibly due to dirt or a smudge on the LABEL side surface;<br />
Wiping the LABEL side surface with a dry cloth helped "fix" the burning problem;<br />
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.</p>
<p>REV. 2009-11-23 1650 EST</p>
<br />]]></description>
  <pubDate>Sun, 29 Nov 2009 22:30:17 GMT</pubDate>
 </item>
 </channel>
</rss>
