>From: "netslider N" <[EMAIL PROTECTED]>

>> >> >  Cdrecord 1.11a05 (alphaev56-unknown-linux-gnu) Copyright (C) 
>>1995-2001
>> >> >J�rg Schilling
>> >> >  scsidev: '1,4,0'
>> >> >  scsibus: 1 target: 4 lun: 0
>> >> >  Linux sg driver version: 2.1.39
>> >> >  Using libscg version 'schily-0.5'
>> >> >  Device type    : Removable WORM
>> >> >  Version        : 2
>> >> >  Response Format: 2
>> >> >  Capabilities   : SYNC LINKED
>> >> >  Vendor_info    : 'T.YUDEN '
>> >> >  Identifikation : 'CD-WO EW-50     '
>> >> >  Revision       : '2.16'
>> >> >  Device seems to be: Philips CDD-521.
>> >> >Perhaps the Philips CDD-521 does require byteswab and my t.yuden 
>>doesn't

>>Mmmm it looks as if you don't have a intel based system. Where did you test 
>>your
>>wav files?

>I've made the wav files on Win2k on Intel. I've tried to play them on Intel 
>and also on Linux for Alpha. On both platforms they play correct. The 
>cdwriter is located on the Alpha platform.

OK accepted.

>>
>> >PS: this drive also has a problem with telling which speed it is, i get 
>>the
>> >following warning with cdrecord. I have to manually set the speed to 2.

How did you do this?

>> >Using driver for Philips CDD-521 (philips_cdd521).
>> >Driver flags   :
>> >Supported modes: TAO
>> >cdrecord: Warning: blockdesc secsize 2048 differs from cap secsize 0
>> >Disk bar code: 00 00 00 0A F1 00 00 00 00 00 00 00 00 00
>> >cdrecord: Warning: controller returns zero sized Speed/Dummy information
>> >page.
>> >cdrecord: Warning: controller returns wrong size for Speed/Dummy 
>>information
>> >page.
>> >cdrecord: Warning: controller returns wrong page 0 for Speed/Dummy
>> >information page (23).
>>
>>Interesting! There is a bar code so it loos as if this is a CDD-521.
>>Why should Tayo Yuden modify the firmware to have a different audio
>>byte order?

>I have no idea, could it be because it's a very old drive? Perhaps back 
>then, there weren't any standards on the byte order?

Old Philips drives _use_ standard byte order which is motorola byte order.

If you are right, then your drive uses intel byte order which has been
used for MMC drives too and is a break of the SCSI standard which also defines
Motorola byte order for all structured data (except now digital audio :-()

>>Are you sure that the drive was not hung when you tested?

>What do you mean with "hung"?
>The writing proces finishes normally after fixating the disc.

Why do you have problems with the mode pages?

J�rg

 EMail:[EMAIL PROTECTED] (home) J�rg Schilling D-13353 Berlin
       [EMAIL PROTECTED]               (uni)  If you don't have iso-8859-1
       [EMAIL PROTECTED]           (work) chars I am J"org Schilling
 URL:  http://www.fokus.gmd.de/usr/schilling   ftp://ftp.fokus.gmd.de/pub/unix


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to