|
|
Posted by Mike S. on 11/17/07 13:13
In article <473E25C1.77D0EE78@blueyonder.co.uk>,
Paul Heslop <paul.heslop@blueyonder.co.uk> wrote:
>Tarkus wrote:
>>
>> Paul Heslop wrote:
>> > dmcg wrote:
>> >> I recently purchased a spindle of TDK-R (16x) discs that are
>> >> unrecognizable on my PC and unburnable, using NERO, ROXIO and
>> >> imgburn. I'm running Windows XP, SP2. The discs work fine on my stand-
>> >> alone LITE-0N DVD recorder and I've since been able to burn TDK-R's,
>> >> from another spindle, on my PC.
>> >>
>> >> Has anyone else run across this kind of problem or know of a reason
>> >> why this phenomenon might exist. Thanks in advance to whomever can
>> >> offer some insight.
>> >>
>> >> D.
>> >
>> > your burner may be incompatible or may need a firmware upgrade. If
>> > it's an older one it may not be able to cope with the speed of the
>> > discs without an upgrade.
>>
>> Aren't all discs backwards compatible all the way to 1x? I don't see
>> where the speed of the discs is an issue. Their listed speeds are the
>> maximum, not the minimum.
>
>I am sure I have seen it mentioned that 16X speed discs may not be
>compatible with some drives which the firmware was not written for
>16X. I may be wrong, it wouldn't be the first time. :O)
>
>actually, on a little google I just found this and it's a bit scary,
>but hopefully doesn't apply in this case
>
>http://www.tiktak-it.co.uk/acatalog/Blank_DVD-R_Discs.html
>
>"TDK DVD-R - 4.7GB - 16x speed - box of 10 jewel cases. Ref: TDK-6153
>DVD-R47CBEC10: TDK high performance write once DVD minus discs
>(DVD-R). Box of 10 individual jewel cases. These single sided discs
>provide the standard 4.7GB data capacity and are rated 1x - 16x speed
>(ver 2.1 rev 6.0). It should be noted that use in incompatible
>recorders may lead to permanent damage to the recorder. The disc can
>store 4 hours of video capacity in EP mode (VHS quality) or 2 hours in
>SP mode (DVD quality)."
This comment refers to a particular ancient Pioneer DVD-R drive, as I
remember; and that issue had long since been addressed by a firmware
update.
[Back to original message]
|