Re: solaris cdrecord BH08LS20 drive BD-R problems

2009-10-13 Thread Rob W
>>> The iso file has size of 15635996672 bytes >> Can you read all 7634768 blocks? > Wow, dd is really slow # date Tue Oct 13 16:18:12 EDT 2009 # dd bs=2048 if=/dev/dsk/c3t0d0s0 of=/dev/null 11826176+0 records in 11826176+0 records out # date # Tue Oct 13 17:43:11 EDT 2009 That would be 242200084

Re: cdrtools-2.01.01a66 ready

2009-10-13 Thread Joerg Schilling
Bill Davidsen wrote: > Joerg Schilling wrote: > > NEW features of cdrtools-2.01.01a66: > > > > *** > > NOTE: cdrtools is currently in a state just before a new major release. > > > > > > > You have been saying this for several years, it has less meaning than > "have a nice day," so e

Re: solaris cdrecord BH08LS20 drive BD-R problems

2009-10-13 Thread Andy Polyakov
>> USB1 full-speed is 12Mbps or 1.5MBps, right? > I am using USB 2.0 ports - 480 Mbps or 60 MBps. I unfortunately have no personal experience with USB storage on SPARC Solaris and can't advice on how to verify if system actually negotiated USB2 Hi-speed for unit in question. My comment was merely

Re: solaris cdrecord BH08LS20 drive BD-R problems

2009-10-13 Thread Thomas Schmitt
Hi, Andy Polyakov wrote: > USB1 full-speed is 12Mbps or 1.5MBps, right? 0.2x4390KBps is around half > the speed... Yes. But 0.2x was the average. At the end the run was around 0.35x. Given a certain overhead in the USB bit stream this is slightly too much. But i just read from Rob, 5 Oct 2009:

Re: solaris cdrecord BH08LS20 drive BD-R problems

2009-10-13 Thread Andy Polyakov
>> When it comes to accuracy of information meant for general public, it's >> difference between implying things and spelling them in manner that >> can't be interpreted differently by different people. >> 1. According to 'man ata' DMA is enabled by default on Solaris 10. To my experience

Re: solaris cdrecord BH08LS20 drive BD-R problems

2009-10-13 Thread Rob W
> USB1 full-speed is 12Mbps or 1.5MBps, right? I am using USB 2.0 ports - 480 Mbps or 60 MBps. Burning DVDs on the Plextor PX-716UF drive using cdrecord from my Solaris10 (sparc) machine is pretty fast.

Re: Announcing cdrskin-0.7.2

2009-10-13 Thread Bill Davidsen
Thomas Schmitt wrote: Hi, Then please inform your users that you cannot grant correctly written CDs on Lite-ON drives and libburn works fine with my olde LITE-ON LTR-48125S CD-RW burner. that you will not be able to write SVCDs on Pioneer drives. (Harrumph) Users ! You m

Re: cdrtools-2.01.01a66 ready

2009-10-13 Thread Bill Davidsen
Joerg Schilling wrote: NEW features of cdrtools-2.01.01a66: *** NOTE: cdrtools is currently in a state just before a new major release. You have been saying this for several years, it has less meaning than "have a nice day," so either release a new beta or release candidate, or

Re: Announcing cdrskin-0.7.2

2009-10-13 Thread Thomas Schmitt
Hi, Bill Davidsen wrote: > The usual programs to generate the info create multiple files and a cuefile > (see the cdrecord man page). Real cdrecord uses this cuefile to write the > SVCD media, It would be interesting to see the cuefile and a ls -l of the track source files. I will probably not be

Re: solaris cdrecord BH08LS20 drive BD-R problems

2009-10-13 Thread Rob W
Thank you Thomas for suggesting things to try. > ... spoil your joy of success Let us not digress too much - remember my definition of success: # cdrecord dev=3,0,0 speed=2 driveropts=burnfree image.iso >>> try to burn it via growisofs >> I have no idea how long it took > Probably rather 4 to 5 h

Re: solaris cdrecord BH08LS20 drive BD-R problems

2009-10-13 Thread Andy Polyakov
>> Checked it this morning, seems to have finished, >> and I have no idea how long it took. >> builtin_dd: 7634768*2KB out @ average 0.2x4390KBps > > Not faster than 7634768*2/(0.3*4390) seconds. > 3 hours 13 minutes at least. Probably rather > 4 to 5 hours. > > Very slow. But at the end a bit to

Re: solaris cdrecord BH08LS20 drive BD-R problems

2009-10-13 Thread Thomas Schmitt
Hi, Rob W: > Checked it this morning, seems to have finished, > and I have no idea how long it took. > builtin_dd: 7634768*2KB out @ average 0.2x4390KBps Not faster than 7634768*2/(0.3*4390) seconds. 3 hours 13 minutes at least. Probably rather 4 to 5 hours. Very slow. But at the end a bit too f

Re: solaris cdrecord BH08LS20 drive BD-R problems

2009-10-13 Thread Rob W
>> try to burn it via growisofs > Seems to be working for growisofs > started it tonight with a 15+ GB iso Checked it this morning, seems to have finished, and I have no idea how long it took. The iso file has size of 15635996672 bytes. 15577645056/15635996672 (99.6%) @0.3x, remaining 1:05 RBU 10

Re: Announcing cdrskin-0.7.2

2009-10-13 Thread Thomas Schmitt
Hi, > Then please inform your users that you cannot grant correctly written > CDs on Lite-ON drives and libburn works fine with my olde LITE-ON LTR-48125S CD-RW burner. > that you will not be able to write SVCDs on Pioneer drives. (Harrumph) Users ! You might not be able to write SVCDs on Pio

Re: solaris cdrecord BH08LS20 drive BD-R problems

2009-10-13 Thread Joerg Schilling
Norbert Preining wrote: > On Di, 13 Okt 2009, Joerg Schilling wrote: > > As I already mentioned: the SCSI error message above was caused by a > > defective > > Solaris kernel module and is not a result from a problem in cdrecord. > > No WHAT? Solaris has a defective kernel module? Incredible!

Re: Announcing cdrskin-0.7.2

2009-10-13 Thread Joerg Schilling
"Thomas Schmitt" wrote: > Hi, > > > When will you correct your wrong claim that states you did not copy any byte > > from cdrecord's sources? > > The claim is uphold. > > > > Note that we did already discuss this some time ago and it is obvious that > > you _did_ copy sources from an older versio

Re: solaris cdrecord BH08LS20 drive BD-R problems

2009-10-13 Thread Joerg Schilling
Rob W wrote: > > try to burn it via growisofs > > Seems to be working for growisofs. > I started it tonight with a 15+ GB iso file. > Will follow up with error messages, if any. > Got to go now ... Please note: the fact that this works does not verfiy that it will always work. It seems that gro

Re: solaris cdrecord BH08LS20 drive BD-R problems

2009-10-13 Thread Norbert Preining
On Di, 13 Okt 2009, Joerg Schilling wrote: > As I already mentioned: the SCSI error message above was caused by a > defective > Solaris kernel module and is not a result from a problem in cdrecord. No WHAT? Solaris has a defective kernel module? Incredible! Wow ... I have to post that on lkml,

Re: solaris cdrecord BH08LS20 drive BD-R problems

2009-10-13 Thread Joerg Schilling
Andy Polyakov wrote: > >>> cdrecord: I/O error. read disk info: scsi sendcmd: no error > >>> CDB: 51 00 00 00 00 00 00 00 04 00 > >>> status: 0x0 (GOOD STATUS) > >>> resid: 4 > >> on Fri, 9 Oct 2009 22:12:35 -0400: > >>> # dvd+rw-mediainfo /dev/rdsk/c3t0d0s0 > >>> ... > >>> READ DISC INFORMATION

Re: solaris cdrecord BH08LS20 drive BD-R problems

2009-10-13 Thread Joerg Schilling
Andy Polyakov wrote: > When it comes to accuracy of information meant for general public, it's > difference between implying things and spelling them in manner that > can't be interpreted differently by different people. > > >> 1. According to 'man ata' DMA is enabled by default on Solaris 10. To

Re: growisofs burns dvd successfully, but

2009-10-13 Thread Joerg Schilling
Ingo Krabbe wrote: > On Mon, Oct 12, 2009 at 02:47:11PM +0200, Joerg Schilling wrote: > > Ingo Krabbe wrote: > > > > > As you recommended I changed my usage of growisofs/genisoimage into > > > mkisofs/cdrecord. > > > > > I see no crash and everything is OK, you may verify this by e.g. calling:

Re: Announcing cdrskin-0.7.2

2009-10-13 Thread Thomas Schmitt
Hi, > When will you correct your wrong claim that states you did not copy any byte > from cdrecord's sources? The claim is uphold. > Note that we did already discuss this some time ago and it is obvious that > you _did_ copy sources from an older version. I removed the code which was labeled a

Re: Announcing cdrskin-0.7.2

2009-10-13 Thread Norbert Preining
On Di, 13 Okt 2009, Joerg Schilling wrote: > No, the announced code contains (different from that the project itself > claims) code > parts from an older version of the cdrtools source. Claiming that there was > no such > code move is a missinformation. Whether this has been done directly or >

Re: Announcing cdrskin-0.7.2

2009-10-13 Thread Joerg Schilling
Mario ??ani?? wrote: > > Note that we did already discuss this some time ago and it is obvious that > > you > > _did_ copy sources from an older version. > > You discussed it with yourself. That's way different, don't you think? :) No, the announced code contains (different from that the projec

Re: Announcing cdrskin-0.7.2

2009-10-13 Thread Joerg Schilling
"Thomas Schmitt" wrote: > be invited to try the new version 0.7.2 of my program cdrskin, > a burn backend for CD, DVD and BD with a command line interface > compatible to cdrecord. When will you correct your wrong claim that states you did not copy any byte from cdrecord's sources? Note that w

Re: Announcing cdrskin-0.7.2

2009-10-13 Thread Mario Đanić
> Note that we did already discuss this some time ago and it is obvious that you > _did_ copy sources from an older version. You discussed it with yourself. That's way different, don't you think? :) > > Jörg > > -- Cheers, Mario -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with