Re: cdrecord 2.01 do READ_BUFFER and crashes drive.

2005-05-09 Thread Joerg Schilling
Hin-Tak Leung [EMAIL PROTECTED] wrote:

  Are you sure that this is a firmware bug?
  
  This may also be a bug in the kernel usb driver.

 I cannot tell whether it is firmware or kernel driver bug, but the
 verdict is that on exactly the same system+hardware combination,
 cdrecord 2.00.3 works and 2.01 does not. Some change between the two
 is not working, and it is the new READ_BUFFER. BTW, what's the purpose
 of it? cdrecord 2.00.3 does not have it (and also seem to do things
 quite differently), so the READ_BUFFER seem to be optional.




Older cdrecord versions did not do a sped test.

Cdrecord asumes either a working drive or at least a kernel that returns correct
error information so cdrecord will know that a specific command does not work.


 snipped
  
  BTW: if the kernel would return a _correct_ error indication to cdrecord,
  cdrecord would stop to repeat this command

 Actually if I don't press cntl-C, after a while when the device disappears,
 cdrecord goes into a fast infinite loop spilling out message
 'scsi ioctl failed' many times per second.

Which OS?


  My advise to you is to try Solaris 10.
  
  It is free and it seems that USB on Solaris 10 is better than the 
  implementation
  on Linux. If you get similar problems with the same hardware, it makes sense
  to discuss the problem to approach a workaround

 As it happens, this same system had Solaris 7 which I installed 5 years ago.
 Xsun only runs at 16-color at 600x480, and I tried Xfree 3, then Xfree 4.
 (the video module kit from xfree only comes in at Solaris 8). It is a laptop
 and the internal cd drive had been replaced and failed again already. Hence
 the external CD writer. So I don't have any way of installing Solaris 10
 without a working internal cd drive. Besides, I reckon Xsun won't work
 on Solaris 10 either... not very funny running X at 16-color at 600x480,
 however much I like to use Solaris 10!

?

Are you going to write FUD against Solaris?

Solaris 7 is 8 years old now! 

Solaris 10 is the recent version.


Jörg

-- 
 EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
   [EMAIL PROTECTED](uni)  
   [EMAIL PROTECTED](work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily


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



Re: How to identify the DVD device for recording data

2005-05-09 Thread Joerg Schilling
Graham Freeman [EMAIL PROTECTED] wrote:

 I am trying to use growisofs to backup data to DVD-R on my Fedora FC3 
 IBM ThinkCentre machine, running Gnome.  I have successfully used 
 cdrecord with the command
mkisofs -hide-joliet-trans-tbl -R -d -allow-leading-dots -l  . | 
 cdrecord -dev=/dev/hdc -v --eject - 
^^
Wrong usage RTFM

 to record to CD-Rs.

 When I try
growisofs -J -R -Z /dev/hdc -speed=2 -graft-points /src=/src 
 /local=/home/usr/local /etc=/etc
 as root, I get the response
:-( /dev/hdc: media is not recognized as recordable DVD: 0

 There is no device /dev/scd0 on the machine or anything similar.  When I 
 try
cdrecord -scanbus
 I get the response
Cdrecord-Clone 2.01-dvd (i686-pc-linux-gnu) Copyright (C) 1995-2004 
 Jörg Schilling
Note: This version is an unofficial (modified) version with DVD support
Note: and therefore may have bugs that are not present in the original.
Note: Please send bug reports or support requests to 
 http://bugzilla.redhat.com/bugzilla
Note: The author of cdrecord should not be bothered with problems in 
 this version.

This is _not_ cdrecord.

If you like to use cdrecord, check ftp://ftp.berlios.de/pub/cdrecord/ProDVD/

Jörg

-- 
 EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
   [EMAIL PROTECTED](uni)  
   [EMAIL PROTECTED](work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily


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



The thing is that a great errrect1on is provided for you exactly when you want.

2005-05-09 Thread Rosa
Than you cannot even imagine what it is like to be a real man in bed!
http://imprints.longpleasure.info/?humorsxtvuylegumezcthordes
Extra power. Don't think. Just act.

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


Need a pill for your ailment?

2005-05-09 Thread Nathaniel Purvis
We have a Pill 4 Everything 
http://www.uidm.com/p/coupon/abdata   


End all future transmissions uidm.comz.php

Gentlemen prefer blondes. 


Re: cdrecord 2.01 do READ_BUFFER and crashes drive.

2005-05-09 Thread Hin-Tak Leung
Joerg Schilling wrote:
Hin-Tak Leung [EMAIL PROTECTED] wrote:

Are you sure that this is a firmware bug?
This may also be a bug in the kernel usb driver.
I cannot tell whether it is firmware or kernel driver bug, but the
verdict is that on exactly the same system+hardware combination,
cdrecord 2.00.3 works and 2.01 does not. Some change between the two
is not working, and it is the new READ_BUFFER. BTW, what's the purpose
of it? cdrecord 2.00.3 does not have it (and also seem to do things
quite differently), so the READ_BUFFER seem to be optional.


Older cdrecord versions did not do a sped test.
Cdrecord asumes either a working drive or at least a kernel that returns correct
error information so cdrecord will know that a specific command does not work.
In this case, the newly introduced speed test seems to cause more problem
than it tries to solve. I would suggest making it optional?
Also, using a new and previously not-used scsi command seems to be an
important enough change that probably should have been mentioned
in the change log?
Actually if I don't press cntl-C, after a while when the device disappears,
cdrecord goes into a fast infinite loop spilling out message
'scsi ioctl failed' many times per second.

Which OS?
Linux, as explained below, I had no way of installing Solaris 10.
My advise to you is to try Solaris 10.
It is free and it seems that USB on Solaris 10 is better than the implementation
on Linux. If you get similar problems with the same hardware, it makes sense
to discuss the problem to approach a workaround
As it happens, this same system had Solaris 7 which I installed 5 years ago.
Xsun only runs at 16-color at 600x480, and I tried Xfree 3, then Xfree 4.
(the video module kit from xfree only comes in at Solaris 8). It is a laptop
and the internal cd drive had been replaced and failed again already. Hence
the external CD writer. So I don't have any way of installing Solaris 10
without a working internal cd drive. Besides, I reckon Xsun won't work
on Solaris 10 either... not very funny running X at 16-color at 600x480,
however much I like to use Solaris 10!

?
Are you going to write FUD against Solaris?
Solaris 7 is 8 years old now! 

Solaris 10 is the recent version.
This is a fairly old system, and as I stated, have Solaris 7 and linux
installed a long time ago, simultaneously. Since then, the internal
CD drive had already broken down twice (it is a laptop) and replaced once,
and currently had no internal CD drive, hence the enternal USB CD writer,
and I have no way of installing/upgrading to Solaris 10. I can continue
to upgrade linux for the last 8 years, because every version
of linux for the last 8 years was useful for all the important
hardwares. I have no continuity and upgrade path between Solaris 7 and
Solaris 10. (I have Solaris 8 CDs as well, if that helps).
To upgrade to Solaris 10, I need at least the ethernet (pcmcia) or
internal cd drive (broken, my fault) working under solaris 7, and neither
are. This is not FUD - it is a known fact that Solaris supports a
smaller set of hardware than linux; this is a laptop.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]


Re: cdrecord 2.01 do READ_BUFFER and crashes drive.

2005-05-09 Thread Joerg Schilling
Hin-Tak Leung [EMAIL PROTECTED] wrote:

  Older cdrecord versions did not do a sped test.
  
  Cdrecord asumes either a working drive or at least a kernel that returns 
  correct
  error information so cdrecord will know that a specific command does not 
  work.

 In this case, the newly introduced speed test seems to cause more problem
 than it tries to solve. I would suggest making it optional?

Sorry, I can only see that the linux kernel causes problems because it 
does not return useful error information.


 Also, using a new and previously not-used scsi command seems to be an
 important enough change that probably should have been mentioned
 in the change log?


Just read the changelog. This has been changed 10 months ago...and tested for 3 
months. Nobody did complain. BTW: the read buffer command was in use since
July 1999 (but transferring only 4 bytes).



  Which OS?

 Linux, as explained below, I had no way of installing Solaris 10.


Q: If you find that the Linux kernel is broken, how about making it optional?

A: Well, I know for a long time and cdrtools was developed on Solaris since
the beginning for exactly this reason.

Jörg

-- 
 EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
   [EMAIL PROTECTED](uni)  
   [EMAIL PROTECTED](work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily


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



Re: cdrecord 2.01 do READ_BUFFER and crashes drive.

2005-05-09 Thread Hin-Tak Leung
Joerg Schilling wrote:
snipped
Which OS?
Linux, as explained below, I had no way of installing Solaris 10.

Q: If you find that the Linux kernel is broken, how about making it 
optional?
A: Well, I know for a long time and cdrtools was developed on Solaris since
the beginning for exactly this reason.
I don't want to turn this into a Linux versus Solaris flame-match; for me,
I did have both as optional - I had Solaris 7 and Linux installed
simultaneously about 6 years ago, on a *Sony Vaio laptop*; I had both, and
if they both work, I would probably continue to use both and switch
where appropriate, and there would have been no need to choose. Linux
was optional, and still is. Solaris 7 still resides in my 2nd partition, now.
I am willing to believe you that Solaris 10 is a much better OS than Linux;
I have heard a lot of good things about Solaris, and my laptop dual-boots
linux and Solaris 7, even now. I want to have both. There is no need
to choose.
6 years ago, linux supported all the hardware I had then on the laptop,
Solaris 7 did not (pcmcia did not work so I had no network connectivity,
Xsun only did 480 x 640 at 4-bit/16-color color, Xfree did 1024x768 x 24-bit).
I have tried to make Xfree work under Solaris 7, and I have tried to make
the video porting kit work as well. I don't think Solaris 10 substantially 
improved hardware support on heavily OEM'ed laptops like a Sony Vaio.
I want to believe you, and when I have a *desktop* system with fairly
standard *mainstream* hardware, I will give Solaris 10 a try, *again*,
I promise.

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


Re: Why actual speed is slower than nominal? (2.6x vs 4x)

2005-05-09 Thread Konstantin Kudin
 I tried this pipebuf2 program with 128MB buffer, and it seems like
things did not improve. The speed I get is still way below the nominal,
and when the writing stalled because of the Knoppix CD access, a
visible track on the DVD(+RW) was formed. Previously with such stalls I
did not see any visible tracks in the recorded data.

 Thus pipebuf2 does not improve things in my case, and even seems to
make them worse ...

 The issue then must be something else ...

 Konstantin

--- Peter Osterlund [EMAIL PROTECTED] wrote:
 Konstantin Kudin [EMAIL PROTECTED] writes:
 
   I am curious as to why the actual speed I get happens to be a lot
  slower than the nominal one. I am using Knoppix 3.8.1 with 2.6.11
  kernel in /dev/hdc, and the DVD writer is /dev/hdd
  
   If I do not use hdparm to set the speed of /dev/hdd to udma2,
 then
  actual speed happens to be even slower. 
  
   I am creating the image on the fly, could that make things go
 slower?
 
 Yes it could. See this link:
 
 http://lists.debian.org/cdwrite/2003/12/msg00226.html
 
 -- 
 Peter Osterlund - [EMAIL PROTECTED]
 http://web.telia.com/~u89404340
 



__ 
Do you Yahoo!? 
Make Yahoo! your home page 
http://www.yahoo.com/r/hs


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



Re: cdrecord-prodvd also fails to write Moviestyle dvd

2005-05-09 Thread Dominique Dumont
Dominique Dumont [EMAIL PROTECTED] writes:

 In dummy mode everything looks fine. But, dvd-record failed to write
 in readl mode: I ended with a mountable dvd with no data ?!?!?!

I have to add a small correction: cdrecord has written the beginning
of the iso image: I have the directory content and a small part of the
first file. The other files are empty:

Cheers



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



cdrecord-prodvd also fails to write Moviestyle dvd (was: Cannot read anymore dvd after eject and re-load)

2005-05-09 Thread Dominique Dumont

Hello

Following the problems I got with Moviestyles DVD+R, I've tried
cdrecord-pro.

In dummy mode everything looks fine. But, dvd-record failed to write
in readl mode: I ended with a mountable dvd with no data ?!?!?!

Here's the output of the dummy mode.

$ sudo cdrecord -v -dummy -dao ghibli-1.iso 
Cdrecord-ProDVD-Clone 2.01b31 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg 
Schilling
Unlocked features: ProDVD Clone 
Limited  features: 
This copy of cdrecord is licensed for: 
private/research/educational_non-commercial_use
TOC Type: 1 = CD-ROM
scsidev: 'ATAPI:0,0,0'
devname: 'ATAPI'
scsibus: 0 target: 0 lun: 0
Warning: Using ATA Packet interface.
Warning: The related Linux kernel interface code seems to be unmaintained.
Warning: There is absolutely NO DMA, operations thus are slow.
Using libscg version 'schily-0.8'.
SCSI buffer size: 64512
atapi: 1
Device type: Removable CD-ROM
Version: 0
Response Format: 2
Capabilities   : 
Vendor_info: 'PIONEER '
Identifikation : 'DVD-RW  DVR-106D'
Revision   : '1.07'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: DVD+R
Profile: DVD+R (current)
Profile: DVD+RW 
Profile: DVD-RW sequential overwrite 
Profile: DVD-RW restricted overwrite 
Profile: DVD-R sequential recording 
Profile: DVD-ROM 
Profile: CD-RW 
Profile: CD-R 
Profile: CD-ROM 
Using generic SCSI-3/mmc-3 DVD+R driver (mmc_dvdplusr).
Driver flags   : DVD MMC-3 SWABAUDIO BURNFREE 
Supported modes: PACKET SAO
Drive buf size : 1605632 = 1568 KB
FIFO size  : 4194304 = 4096 KB
Track 01: data  4108 MB
Total size: 4108 MB = 2103369 sectors
Current Secsize: 2048
Blocks total: 2295104 Blocks current: 2295104 Blocks remaining: 191735
Starting to write CD/DVD at speed 4 in dummy SAO mode for single session.
Last chance to quit, starting dummy write0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
Starting new track at sector: 0
Track 01:   70 of 4108 MB written (fifo  98%) [buf  66%]   
4.2x./home/domi/freeware/cdrecord-pro-dvd/cdrecord-pro-dv
d: Caught interrupt.
Writing  time:   27.435s
Min drive buffer fill was 61%

I interrupted the dummy to try the real write:

$ sudo cdrecord -v -dao ghibli-1.iso 
Cdrecord-ProDVD-Clone 2.01b31 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg 
Schilling
Unlocked features: ProDVD Clone 
Limited  features: 
This copy of cdrecord is licensed for: 
private/research/educational_non-commercial_use
TOC Type: 1 = CD-ROM
scsidev: 'ATAPI:0,0,0'
devname: 'ATAPI'
scsibus: 0 target: 0 lun: 0
Warning: Using ATA Packet interface.
Warning: The related Linux kernel interface code seems to be unmaintained.
Warning: There is absolutely NO DMA, operations thus are slow.
Using libscg version 'schily-0.8'.
SCSI buffer size: 64512
atapi: 1
Device type: Removable CD-ROM
Version: 0
Response Format: 2
Capabilities   : 
Vendor_info: 'PIONEER '
Identifikation : 'DVD-RW  DVR-106D'
Revision   : '1.07'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: DVD+R
Profile: DVD+R (current)
Profile: DVD+RW 
Profile: DVD-RW sequential overwrite 
Profile: DVD-RW restricted overwrite 
Profile: DVD-R sequential recording 
Profile: DVD-ROM 
Profile: CD-RW 
Profile: CD-R 
Profile: CD-ROM 
Using generic SCSI-3/mmc-3 DVD+R driver (mmc_dvdplusr).
Driver flags   : DVD MMC-3 SWABAUDIO BURNFREE 
Supported modes: PACKET SAO
Drive buf size : 1605632 = 1568 KB
FIFO size  : 4194304 = 4096 KB
Track 01: data  4108 MB
Total size: 4108 MB = 2103369 sectors
Current Secsize: 2048
WARNING: Phys disk size 2295104 differs from rzone size 2331264! Prerecorded 
disk?
WARNING: Phys start: 196608 Phys end 2491711
Blocks total: 2331264 Blocks current: 2295104 Blocks remaining: 191735
Starting to write CD/DVD at speed 4 in real SAO mode for single session.
Last chance to quit, starting real write0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
Starting new track at sector: 0
Track 01:0 of 4108 MB 
written./home/domi/freeware/cdrecord-pro-dvd/cdrecord-pro-dvd: Input/output 
error. write_g
1: scsi sendcmd: no error
CDB:  2A 00 00 00 00 00 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 00 00 00 00 0E 00 00 00 00 21 02 00 00 00 00 00 00 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x21 Qual 0x02 (invalid address for write) Fru 0x0
Sense flags: Blk 0 (not valid) 
cmd finished after 0.005s timeout 100s

write track data: error after 0 bytes
/home/domi/freeware/cdrecord-pro-dvd/cdrecord-pro-dvd: The current problem 
looks like a buffer underrun.
/home/domi/freeware/cdrecord-pro-dvd/cdrecord-pro-dvd: Try to use 
'driveropts=burnfree'.
/home/domi/freeware/cdrecord-pro-dvd/cdrecord-pro-dvd: Make sure that you are 
root, enable DMA and check your HW/OS 
set up.
Writing  time:5.041s
Average write speed 617.7x.
Fixating...
Fixating time:0.471s
/home/domi/freeware/cdrecord-pro-dvd/cdrecord-pro-dvd: fifo had 64 puts and 1