Jerry, what speed do you try to record at? My drive is 6x capable (according to docs) but in reality I am able to record at 4x maximum. When I specify 6x speed in cdrecord command it works for some times and then breaks with some error from the drive. -Kastus On Thu, Mar 29, 2001 at 12:48:26PM -0600, jerrykreps wrote:
On Thursday 29 March 2001 11:13 am, you wrote:
On Thu, Mar 29, 2001 at 09:26:58AM -0600, Jerry Kreps wrote:
On Thursday 29 March 2001 03:04, Dunphy Richard-rdunph01 wrote:
Just curious as to which version of xcdroast you are using, and how you are using it?
When I had my IDE CDRW I found that all versions after 0.98d freeze if you do a direct CD to CDR copy. Even trying to create the images on the fly from the harddisk failed.
My beast is in pieces right now, but the version of xcdroast is what ever came on the SuSE CDs.
I had to create the image first, then burn. Worked everytime although annoying, and tedious. Hence the move to a SCSI CDRW which I was moving to anyway!
Tried that. The image creation process never gets past about 8-14% before dying. But, I agree with your assessment that moving to scsi is the way to go. I've had too many irq conflict problems, along with PCI cards being too smart for their own good. I had my beast configured with two parallel cards so I could run the printer on one and the parallel zip250 on the other, which is a config that works on my Sony. But, it wouldn't go. Imm wouldn't connect. It turns out that lp1 was a PCI card that either intialized on boot to 278-irq5 or it wouldn't connect at all. I was always getting a device is busy error. So, I took out the second parallel card and plugged the zip250 into lp0 and the lexmarkz52 into the zip drive. Now both work great. I am removing the scsi emulation and booting the CDR as hdd, since it is IDE. I will be getting a scsi card to hook a second CDR to, and will probably swap my parallel zip250 for a scsi one. In fact, from now on I am going to leave my HDs as IDE and all other peripherals as scsi. I have used a usb CDR at work (HP 8200i) and when it is buring a CD you can't do anything else or you'll blow the burn. (Win98SE). So I am not convienced that usb technology is there yet.
As for error message when mounting. This usually indicates that the media you have in the drive is not what you think it is. vfat won't work as it should be iso9660, although some CDRWs are written with udf so you may need to specify this instead!
Someone said they were creating an iso9660 partition in which to store the image. I looked into that and found that the iso9660 type is not an option in fdisk or yast, so I have no idea how they plan to create one.
Maybe the word ``partition'' is not correct. Actually, burning a CD is a two-step process. First, one creates an image of iso9660 file system in a plain file. This part is performed by mkisofs command. You may even mount this image using loopback device to test that nothing was left out.
Second, this image (plain file) is blindly copied onto a CD by cdrecord.
So far, I've always been following this two-step process when creating my CDs.
That I tried too. Same result.
-Kastus
JLK
participants (1)
-
Konstantin (Kastus) Shchuka