.. --------------------------------------
Mike Richter, were you born with
"Scam Artist" emblazoned on your face?
--------------------------------------
(Mike Richter, any Material Connection w/ Roxio?)

http://groups.google.com/groups?selm...mindspring.com
(Messages 10, 12 -- 34, 54 -- 69)

( No pipsqueaks have been able to prove ANY of the above is a libel )
( -- despite Mikey's supposed to have proof of misquotes! )


mike wrote:
smh wrote:
mike wrote:

Strange Error Behavior LiteON LTR5237S

I just upgraded to a new Liteon LTR5237S.
I tried burning a CDRW with one big backup file on it.
It burns and verifies ok, but I always run cdspeed99
to check for C2 errors. CDSPEED99 claims that the length
of the data is 58:50:01. The cdspeed99 cd quality check runs
and gives a read error at 58:49:60 and aborts. Is that even a legal
time signature? This is repeatable across different media.
If I add a file to the compilation and reburn same media,
the problem goes away. But comes back if I reburn without the
added file.
When I run cdspeed99 on another drive with this media, it does
not give a read error or any C2 errors.
Nero cdspeed that came with the drive shows 35280 errors at
the end of the file, but there's no time signature shown.
The program does not abort.

I flashed the firmware to VQS0C. No change.

File size reported by windows is 541,839,964, 541,851,648 bytes used.
Nero 5.5.10.13
Windows 98SE.

Should I be worried about this?


That's normal. The error shows up only with the first and only
session. If you add sessions, the first session's error disappears and
the subsequent sessions don't exhibit the error. Again, the error shows
up only with one and only session. (Other burn softwares exhibit the
same behavior, not just Nero.)

I'm confused. ALL my burns are single session and closed. I've burned
hundreds of CD and CDRW. I've run CDSPEED cd quality check on all of
them. I have NEVER seen this problem before. This appears to happen
only with this particular file size, although I've
not done exhaustive tests to see if other sizes are affected.
I've always used Nero. The problem seems to go with the drive, not
the software.

Now you confuse me as I have seen this NON-Problem whenever I do surface
scan on single session cd's. Don't know why you didn't see it when I
did. Perhaps do more testing and post the results?