From owner-freebsd-questions Sat Apr 22 14: 6:48 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mail1.noc0.hsacorp.net (mail1.noc0.hsacorp.net [208.247.171.140]) by hub.freebsd.org (Postfix) with ESMTP id 77F9237B589 for ; Sat, 22 Apr 2000 14:06:36 -0700 (PDT) (envelope-from jconner@enterit.com) Received: from [24.216.177.146] (HELO default.enterit.com) by mail1.noc0.hsacorp.net (CommuniGate Pro SMTP 3.2.4) with ESMTP id 10927375; Sat, 22 Apr 2000 17:05:09 -0400 Message-Id: <4.3.1.2.20000422171041.01f57320@pseudonet.org> X-Sender: jconner@mail.enterit.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Sat, 22 Apr 2000 17:10:46 -0400 To: Salvo Bartolotta , Jim Conner , freebsd-questions@FreeBSD.ORG From: Jim Conner Subject: Re: how to burn Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 07:22 PM 4/22/00 +0000, Salvo Bartolotta wrote: > >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< > >On 4/22/00, 4:11:36 PM, Jim Conner wrote regarding >Re: how to burn: > > > > > I have never had a problem with mkisofs, but have had nothing but >problems > > with cdrecord. > > > > > - Jim > > >Dear Jim Conner, > >My experience is quite different. > >I have used cdrecord to backup data, to burn my releases etc. Also, I >have recently installed (yet) another 4.0-S system from a CD I had >burnt with cdrecord. > >In particular, I succedeed in burning a couple of "impossible" CD-RW >via cdrecord, as I posted a few weeks ago. "Impossible" was the term >used by a Winblows guy who had been trying every possible Winblows >program to burn them > >My hardware: >bartequi /kernel: cd0: Removable CD-ROM SCSI-2 >device >bartequi /kernel: cd0: 8.333MB/s transfers (8.333MHz, offset 15) > >My software: cdrecord-1.8 > >N.B. The SCSI device I currently use is neither *expensive* nor >particularly *professional* albeit it IS a SCSI device. Well, then perhaps you could help me. I have posted the question many a=20 time here and no one has ever responded. (hist 528)# cdrecord -version Cdrecord release 1.8a21 Copyright (C) 1995-1999 J=F6rg Schilling (hist 529)# uname -v FreeBSD 3.4-RELEASE #5: Wed Feb 2 12:02:10 EST=20 2000 root@localhost:/usr/src/sys/compile/nj cd0: Removable Worm SCSI-2 device cd0: 4.032MB/s transfers (4.032MHz, offset 15) cd0: cd present [316269 x 2048 byte records] cdrecord: No such file or directory. WARNING: RR-scheduler not available,=20 disabling. fs: 4194304 buflen: 4198400 cdrecord: shared memory segment attached: 2810c000 buf: 2810C000 bufend: 2850D000, buflen: 4198400 buf: 2810C000 bufend: 2850D000, buflen: 4198400 (align 0) File: '/services/etc_bak.iso' tracksize: 1089536 secsize: 2048 tracktype: 3= =20 =3D CD-ROM XA mode 2 sectype: 2 =3D CD-ROM mode 2 dbtype: CD-ROM XA mod e 2 form 1 flags 10C0 dev: 1,6,0 speed: -1 fs: -1 Cdrecord release 1.8a21 Copyright (C) 1995-1999 J^vrg Schilling TOC Type: 3 =3D CD-ROM XA mode 2 scsidev: '1,6,0' scsibus: 1 target: 6 lun: 0 scsi_getbuf: 64512 bytes atapi: 0 Device type : Removable WORM Version : 2 Response Format: 2 Capabilities : SYNC LINKED Vendor_info : 'SONY ' Identifikation : 'CD-R CDU920S ' Revision : '2.0c' Device seems to be: Sony CDU-924S. Using driver for Sony CDU-924 (sony_cdu924). Driver flags : SWABAUDIO Drive buf size : 1048576 =3D 1024 KB FIFO size : 4194304 =3D 4096 KB bufsize: 65536 buffers: 64 hdrsize 1024 bufsize: 65536 buffers: 64 hdrsize 1024 cdrecord: Undefined error: 0. WARNING: RR-scheduler not available,= disabling. Track 01: data 1 MB Total size: 1 MB (00:07.12) =3D 534 sectors Lout start: 1 MB (00:09/09) =3D 534 sectors Pages: 0x1 0x2 0x8 0xd 0xe 0x20 0x22 0x23 0x31 Density: 0x0 Blocks: 0 Blocklen:2048 Current Secsize: 2048 ATIP info from disk: Indicated writing power: 4 Is not unrestricted Disk application code: 0 ATIP start of lead in: -11320 (97:31/05) ATIP start of lead out: 336225 (74:45/00) ATIP start of lead out: 336225 (74:45/00) Disk type: Phthalocyanine or similar Manuf. index: 22 Manufacturer: Ritek Co. Blocks total: 336225 Blocks current: 336225 Blocks remaining: 335691 Using 64 buffers of 64512 bytes. Starting to write CD/DVD at speed 1 in write mode for single session. Last chance to quit, starting real write in 1 seconds. Waiting for reader process to fill input-buffer ... cdrecord: Input/output= =20 error. write_track: scsi sendcmd: retryable error status: 0x2 (CHECK CONDITION) input-buffer ready. CDB: F5 00 00 00 00 00 00 00 00 00 Sense Bytes: 70 00 05 00 00 00 00 12 00 00 00 00 C9 00 00 00 00 00 00 00 20= =20 06 00 00 00 00 Sense Key: 0x5 Illegal Request, Segment 0 Sense Code: 0xC9 Qual 0x00 (illegal block length for write command) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 0.018s timeout 40s Writing time: 0.186s Fixating... cdrecord: Input/output error. finalize: scsi sendcmd: retryable error status: 0x2 (CHECK CONDITION) CDB: F1 00 00 00 00 00 00 00 00 00 Sense Bytes: 70 00 05 00 00 00 00 12 00 00 00 00 89 00 00 00 00 00 00 00 02= =20 06 00 00 00 00 Sense Key: 0x5 Illegal Request, Segment 0 Sense Code: 0x89 Qual 0x00 (inappropriate command) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 0.023s timeout 480s cdrecord: fifo had 18 puts and 0 gets. cdrecord: fifo was 0 times empty and 0 times full, min fill was 100%. Fixating time: 0.023s That is the .out that Igot the last time I tried to burn an image to=20 cdr. Any thoughts and ides would be nice. I've been attempting to burn=20 for about a year now. TIA - Jim >Best regards, >Salvo > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Today's errors, in contrast: Windows - "Invalid page fault in module kernel32.dll at 0032:A16F2935" UNIX - "segmentation fault - core dumped" Humanous Beingsus - "OOPS, I've fallen and I can't get up" ------------------------------- Jim Conner NOTJames jconner@enterit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message