<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
 <!-- Generated by Ektron CMS400.NET -->
 <channel>
  <title>LightScribe Forum : Getting Started : Error 4224 on Mac OS X</title>
  <description></description>
 <item>
  <title></title>
  <description><![CDATA[<p>Hello,</p>
<p>I recently got a LightScribe drive, and I'm not able to burn labels under Mac OS X 10.6.8. Every time I try burning a label, using LightScribe Simple Labeler, I get the communication error 4224.</p>
<p>I tested the drive under Windows XP and it worked fine when burning a label. Also, it burns CD and DVD data perfectly on both, Mac OS X and Windows XP.</p>
<p>Can someone help me with this?</p>
<br />]]></description>
  <pubDate>Sat, 21 Apr 2012 05:38:14 GMT</pubDate>
 </item>
 <item>
  <title></title>
  <description><![CDATA[<p> I'm using an HP Pavillion dv9825nr Notebook PC, running Windows Vista Home Premium SP2.<br />I also have an HP Pavilion dv6-2155dx Notebook PC, running Windows 7 Home Premium.<br />I also have an HP PhotoSmart C8180 All-In-One Printer.  Both have built-in LS Drives.<br />Each has a built-in LS Drive.<br />Everything has been running LSS fine since 4/08.</p>
<p>I use Memorex disks and also HP disks almost all the time, because they are the only ones I seem to find.</p>
<p>If I have any problems with labeling a disk, I clean the center (hub) of the disk before burning the LABEL side first.</p>
<p>I use the LS Template Labeler for the LABEL side and NERO 10 for the DATA side.</p>
<p>I had trouble with the first two spindles I bought.</p>
<p>One disk had a bad DATA side and another (Memorex) had to be re-cleaned in the center (hub) of the disk 3 times of 20 turns of the cleaner, but it burned successfully.</p>
<p>I've also fooled around a little with the LS Simple Labeler.</p>
<p>I've developed 507 Custom Templates (in 80 Collections + 10 Private Ones), 108 Images (in 12 Collections), 174 Icons, and 4 Test Background Images for the LS SL, and have shared them with 377 Forum Users.</p>
<p>Rev. 2012-04-07 1400 EDT </p>
<hr />
<p>I know OS X &amp; Win 7 Users have reported this problem, but a Comm Error is a Comm Error.</p>
<p>Somehow the Connection is different &amp; you should look at that.</p>
<p>Be as sure as you can be that you are using the same type of connection.</p>
<br />]]></description>
  <pubDate>Sun, 22 Apr 2012 21:14:17 GMT</pubDate>
 </item>
 </channel>
</rss>
