Can't burn with k3b

jeanfiga · 2006-12-08 01:43:38

Trying to burn a cd with K3B. It is not happening. Here is the debugging info:

System
-----------------------
K3b Version: 0.12.17

KDE Version: 3.5.5
QT Version: 3.3.6
Kernel: 2.6.18-ARCH
Devices
-----------------------
PHILIPS DVD+-RW SDVD8820 AD15 (/dev/sr0, ) at /mnt/cd [CD-R; CD-RW; CD-ROM; DVD-ROM; DVD-R; DVD-RW; DVD-R DL; DVD+R; DVD+RW; DVD+R DL] [DVD-ROM; DVD-R Sequential; DVD-R Dual Layer Sequential; DVD-R Dual Layer Jump; DVD-RW Restricted Overwrite; DVD-RW Sequential; DVD+RW; DVD+R; DVD+R Double Layer; CD-ROM; CD-R; CD-RW] [SAO; TAO; RAW; SAO/R96P; SAO/R96R; RAW/R16; RAW/R96P; RAW/R96R; Restricted Overwrite; Layer Jump]

Used versions
-----------------------
cdrecord: 2.1.1a06

cdrecord
-----------------------
WARNING ! Cannot gain SYS_RAWIO capability !
: Operation not permitted
WARNING ! Cannot gain SYS_RAWIO capability !
: Operation not permitted
/usr/bin/cdrecord: Warning: Running on Linux-2.6.18-ARCH
/usr/bin/cdrecord: There are unsettled issues with Linux-2.5 and newer.
/usr/bin/cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
WARNING ! Cannot gain SYS_RAWIO capability !
: Operation not permitted
scsidev: '1,0,0'
scsibus: 1 target: 0 lun: 0
/usr/bin/cdrecord: No such file or directory. Cannot open '/dev/sg*'. Cannot open SCSI driver.
/usr/bin/cdrecord: For possible targets try 'cdrecord -scanbus'.
/usr/bin/cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
Cdrecord-Clone 2.01.01a06 (i686-pc-linux-gnu) Copyright (C) 1995-2006 Jörg Schilling
NOTE: this is OSS DVD extensions for cdrtools and thus may have bugs
related to DVD issues that are not present in the original cdrtools. For
more information see http://crashrecovery.org/oss-dvd.html. The original
cdrtools author should not be bothered with problems in this version.
TOC Type: 1 = CD-ROM

cdrecord command:
-----------------------
/usr/bin/cdrecord -v gracetime=2 dev=1,0,0 speed=24 -dao driveropts=burnfree -eject -data /home/figa/en_office_pro_2003.iso

Any ides?

skottish · 2006-12-08 02:44:36

Did you run K3B setup to give regular users correct permissions?

jeanfiga · 2006-12-08 16:41:57

skottish wrote:

Did you run K3B setup to give regular users correct permissions?

Yes sir I did. I even created the burning group and ran k3b as a root, with the same error happening.

FYI. I am running on a dell XPSM1210

ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xBFA8 irq 15
scsi1 : ata_piix
ata2.00: ATAPI, max UDMA/33
ata2.00: configured for UDMA/33
  Vendor: PHILIPS   Model: DVD+-RW SDVD8820  Rev: AD15
  Type:   CD-ROM                             ANSI SCSI revision: 05
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
 sda: sda1 sda2 <sda5>
sd 0:0:0:0: Attached scsi disk sda
sr0: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 1:0:0:0: Attached scsi CD-ROM sr0

[/code]

Acid7711 · 2006-12-08 19:41:54

jeanfiga wrote:

/usr/bin/cdrecord: No such file or directory.

I'm sorry if I'm wayyyyyyy off here, but is cdrecord installed correctly? running 'cdrecord' if that works, then hmmmm.. Just an idea.

noriko · 2006-12-08 20:50:48

pata|k19?

did u modprobe sg?

chrismortimore · 2006-12-08 20:51:48

Acid7711: The error is actually from cdrecord itself.

jeanfiga: Check the output of "ls /dev/" for sg* devices. If they arn't there, try "modprobe sg" and see if it fixes your problem.

EDIT: Damnit, beaten!

noriko · 2006-12-08 20:59:36

lol

scarecrow · 2006-12-08 22:45:46

Might be an issue with the new cdrkit package, who has replaced cdrtools, and certain tyoes of burners. My internal IDE burner works well with it, but here we have some USB burner.

Acid7711 · 2006-12-09 05:10:07

chrismortimore wrote:

Acid7711: The error is actually from cdrecord itself.

Whooops. Just thought I'd throw it out there. I'm not the greatest at solving things or reading for that matter, but every little thing helps a bit

ronin · 2006-12-17 19:43:09

Hello,

I can't burn too since cdrkit, I tried k3b, xcdroast, graveman.
My burner works well under windows and I can use it to read any cd under Arch but I just can't use any software to burn.
when I try K3b I get this with dmesg:

hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
ide: failed opcode was: unknown
hdd: drive not ready for command

Xcdroast says there is no /usr/bin/cdrecord file or directory but it exists and this is a link to /usr/bin/wodim.

When I enter cdrecord:

[ronin@myhost ~]$ cdrecord
cdrecord: No CD/DVD-Recorder device specified.
Usage: cdrecord [options] track1...trackn

Use cdrecord -help
to get a list of valid options.

Use cdrecord blank=help
to get a list of valid blanking options.

Use cdrecord dev=b,t,l driveropts=help -checkdrive
to get a list of drive specific options.

Use cdrecord dev=help
to get a list of possible SCSI transport specifiers.

Same for wodim, same under root. Is it a bug? This is an IDE burner, not SCSI. I'm on current and up to date.

Thanks by advance

ronin · 2006-12-22 19:25:36

hello,

Now I can start my burning softwares (k3b, xcdroast, graveman) but none can detect my recording device /dev/hdd:

k3b: (K3bExternalBinManager) Cdrecord 2.1.1a03 features: dvd-patch, gracetime, overburn, cdtext, clone, tao, cuefile, xamix, suidroot, plain-atapi, hacked-atapi, short-track-raw
k3b: (K3bExternalBinManager) 2 1 1 a03 seems to be cdrecord version >= 1.11a02, using burnfree instead of burnproof
k3b: (K3bExternalBinManager) seems to be cdrecord version >= 1.11a31, support for Just Link via burnfree driveroption
k3b: (K3bDevice::HalConnection) initializing HAL >= 0.5
k3b: /dev/hdb resolved to /dev/hdb
k3b: /dev/hdb is block device (64)
k3b: /dev/hdb seems to be cdrom
k3b: (K3bDevice::Device) /dev/hdb: init()
k3b: (K3bDevice::Device) /dev/hdb feature: DVD Read
k3b: (K3bDevice::Device) /dev/hdb unknown profile: 17224
k3b: (K3bDevice::Device) /dev/hdb unknown profile: 0
k3b: (K3bDevice::ScsiCommand) failed:
k3b: command: MODE SENSE (5a)
k3b: errorcode: 70
k3b: sense key: ILLEGAL REQUEST (5)
k3b: asc: 24
k3b: ascq: 0
k3b: (K3bDevice::Device) /dev/hdb: MODE SENSE length det failed.
k3b: (K3bDevice::Device) /dev/hdb: modeSense 0x05 failed!
k3b: (K3bDevice::Device) /dev/hdb: Cannot check write modes.
k3b: (K3bDevice::ScsiCommand) failed:
k3b: command: MODE SENSE (5a)
k3b: errorcode: 70
k3b: sense key: ILLEGAL REQUEST (5)
k3b: asc: 24
k3b: ascq: 0
k3b: (K3bDevice::Device) /dev/hdb: MODE SENSE length det failed.
k3b: /dev/hdd resolved to /dev/hdd
k3b: /dev/hdd is block device (64)
k3b: /dev/hdd seems not to be a cdrom device: 0
k3b: /dev/hdd resolved to /dev/hdd
k3b: /dev/hdd is block device (64)
k3b: /dev/hdd seems not to be a cdrom device: 0
k3b: /dev/hdb resolved to /dev/hdb
k3b: /dev/hdb is block device (64)
k3b: /dev/hdb seems to be cdrom
k3b: (K3bDevice::DeviceManager) dev /dev/hdb already found
k3b: (K3bDevice::DeviceManager) Link: /dev/dvd0 -> /dev/hdb
k3b: (K3bDevice::DeviceManager) Link: /dev/dvd -> /dev/hdb
k3b: (K3bDevice::DeviceManager) Link: /dev/cdrom0 -> /dev/hdb
k3b: (K3bDevice::DeviceManager) Link: /dev/cdrom -> /dev/hdb
k3b: (K3bDevice::DeviceManager) Link: /dev/cd/dvd-hdb -> /dev/hdb
k3b: (K3bDevice::DeviceManager) Link: /dev/cd/cdrom-hdb -> /dev/hdb
k3b: (K3bDevice::DeviceManager) SCANNING FOR GENERIC DEVICES.
k3b: Could not resolve /dev/sg0
k3b: (K3bDevice::Device) Error: could not open device /dev/sg0for reading
k3b: could not open device /dev/sg0 (Aucun fichier ou r??pertoire de ce type)
k3b: Could not resolve /dev/sg1
k3b: (K3bDevice::Device) Error: could not open device /dev/sg1for reading
k3b: could not open device /dev/sg1 (Aucun fichier ou r??pertoire de ce type)
k3b: Could not resolve /dev/sg2
k3b: (K3bDevice::Device) Error: could not open device /dev/sg2for reading
k3b: could not open device /dev/sg2 (Aucun fichier ou r??pertoire de ce type)
k3b: Could not resolve /dev/sg3
k3b: (K3bDevice::Device) Error: could not open device /dev/sg3for reading
k3b: could not open device /dev/sg3 (Aucun fichier ou r??pertoire de ce type)
k3b: Could not resolve /dev/sg4
k3b: (K3bDevice::Device) Error: could not open device /dev/sg4for reading
k3b: could not open device /dev/sg4 (Aucun fichier ou r??pertoire de ce type)
k3b: Could not resolve /dev/sg5
k3b: (K3bDevice::Device) Error: could not open device /dev/sg5for reading
k3b: could not open device /dev/sg5 (Aucun fichier ou r??pertoire de ce type)
k3b: Could not resolve /dev/sg6
k3b: (K3bDevice::Device) Error: could not open device /dev/sg6for reading
k3b: could not open device /dev/sg6 (Aucun fichier ou r??pertoire de ce type)
k3b: Could not resolve /dev/sg7
k3b: (K3bDevice::Device) Error: could not open device /dev/sg7for reading
k3b: could not open device /dev/sg7 (Aucun fichier ou r??pertoire de ce type)
k3b: Could not resolve /dev/sg8
k3b: (K3bDevice::Device) Error: could not open device /dev/sg8for reading
k3b: could not open device /dev/sg8 (Aucun fichier ou r??pertoire de ce type)
k3b: Could not resolve /dev/sg9
k3b: (K3bDevice::Device) Error: could not open device /dev/sg9for reading
k3b: could not open device /dev/sg9 (Aucun fichier ou r??pertoire de ce type)
k3b: Could not resolve /dev/sg10
k3b: (K3bDevice::Device) Error: could not open device /dev/sg10for reading
k3b: could not open device /dev/sg10 (Aucun fichier ou r??pertoire de ce type)
k3b: Could not resolve /dev/sg11
k3b: (K3bDevice::Device) Error: could not open device /dev/sg11for reading
k3b: could not open device /dev/sg11 (Aucun fichier ou r??pertoire de ce type)
k3b: Could not resolve /dev/sg12
k3b: (K3bDevice::Device) Error: could not open device /dev/sg12for reading
k3b: could not open device /dev/sg12 (Aucun fichier ou r??pertoire de ce type)
k3b: Could not resolve /dev/sg13
k3b: (K3bDevice::Device) Error: could not open device /dev/sg13for reading
k3b: could not open device /dev/sg13 (Aucun fichier ou r??pertoire de ce type)
k3b: Could not resolve /dev/sg14
k3b: (K3bDevice::Device) Error: could not open device /dev/sg14for reading
k3b: could not open device /dev/sg14 (Aucun fichier ou r??pertoire de ce type)
k3b: Could not resolve /dev/sg15
k3b: (K3bDevice::Device) Error: could not open device /dev/sg15for reading
k3b: could not open device /dev/sg15 (Aucun fichier ou r??pertoire de ce type)
k3b: (K3bDevice::DeviceManager) scanning fstab: /dev/cdrom
k3b: (K3bDevice::DeviceManager) found device for /dev/cdrom: /dev/hdb
k3b: (K3bDevice::DeviceManager) scanning fstab: /dev/dvd
k3b: (K3bDevice::DeviceManager) found device for /dev/dvd: /dev/hdb
k3b: (K3bDevice::DeviceManager) scanning fstab: /dev/fd0
k3b: /dev/fd0 resolved to /dev/fd0
k3b: /dev/fd0 is block device (0)
k3b: (K3bDevice::ScsiCommand) failed:
k3b: command: INQUIRY (12)
k3b: errorcode: 0
k3b: sense key: NO SENSE (2)
k3b: asc: 0
k3b: ascq: 0
k3b: (K3bDevice::Device) Unable to do inquiry. /dev/fd0 is not a cdrom device
k3b: (K3bDevice::DeviceManager) scanning fstab: /dev/hda8
k3b: (K3bDevice::Device) Error: could not open device /dev/hda8for reading
k3b: could not open device /dev/hda8 (Permission non accord??e)
k3b: /dev/hda8 resolved to /dev/hda8
k3b: (K3bDevice::Device) Error: could not open device /dev/hda8for reading
k3b: could not open device /dev/hda8 (Permission non accord??e)
k3b: (K3bDevice::DeviceManager) scanning fstab: /dev/hda7
k3b: (K3bDevice::Device) Error: could not open device /dev/hda7for reading
k3b: could not open device /dev/hda7 (Permission non accord??e)
k3b: /dev/hda7 resolved to /dev/hda7
k3b: (K3bDevice::Device) Error: could not open device /dev/hda7for reading
k3b: could not open device /dev/hda7 (Permission non accord??e)
k3b: (K3bDevice::DeviceManager) scanning fstab: /dev/hda6
k3b: (K3bDevice::Device) Error: could not open device /dev/hda6for reading
k3b: could not open device /dev/hda6 (Permission non accord??e)
k3b: /dev/hda6 resolved to /dev/hda6
k3b: (K3bDevice::Device) Error: could not open device /dev/hda6for reading
k3b: could not open device /dev/hda6 (Permission non accord??e)
k3b: No Devices found!
k3b: /dev/hdb resolved to /dev/hdb
k3b: /dev/hdb is block device (64)
k3b: /dev/hdb seems to be cdrom
k3b: (K3bDevice::DeviceManager) dev /dev/hdb already found
k3b: (K3bDevice::DeviceManager) found config entry for devicetype: HITACHI DVD-ROM GD-8000
k3b: (K3bDevice::DeviceManager) scanning fstab: /dev/cdrom
k3b: (K3bDevice::DeviceManager) found device for /dev/cdrom: /dev/hdb
k3b: (K3bDevice::DeviceManager) scanning fstab: /dev/dvd
k3b: (K3bDevice::DeviceManager) found device for /dev/dvd: /dev/hdb
k3b: (K3bDevice::DeviceManager) scanning fstab: /dev/fd0
k3b: /dev/fd0 resolved to /dev/fd0
k3b: /dev/fd0 is block device (0)
k3b: (K3bDevice::ScsiCommand) failed:
k3b: command: INQUIRY (12)
k3b: errorcode: 0
k3b: sense key: NO SENSE (2)
k3b: asc: 0
k3b: ascq: 0
k3b: (K3bDevice::Device) Unable to do inquiry. /dev/fd0 is not a cdrom device
k3b: (K3bDevice::DeviceManager) scanning fstab: /dev/hda8
k3b: (K3bDevice::Device) Error: could not open device /dev/hda8for reading
k3b: could not open device /dev/hda8 (Permission non accord??e)
k3b: /dev/hda8 resolved to /dev/hda8
k3b: (K3bDevice::Device) Error: could not open device /dev/hda8for reading
k3b: could not open device /dev/hda8 (Permission non accord??e)
k3b: (K3bDevice::DeviceManager) scanning fstab: /dev/hda7
k3b: (K3bDevice::Device) Error: could not open device /dev/hda7for reading
k3b: could not open device /dev/hda7 (Permission non accord??e)
k3b: /dev/hda7 resolved to /dev/hda7
k3b: (K3bDevice::Device) Error: could not open device /dev/hda7for reading
k3b: could not open device /dev/hda7 (Permission non accord??e)
k3b: (K3bDevice::DeviceManager) scanning fstab: /dev/hda6
k3b: (K3bDevice::Device) Error: could not open device /dev/hda6for reading
k3b: could not open device /dev/hda6 (Permission non accord??e)
k3b: /dev/hda6 resolved to /dev/hda6
k3b: (K3bDevice::Device) Error: could not open device /dev/hda6for reading
k3b: could not open device /dev/hda6 (Permission non accord??e)
k3b: (K3bExternalBinManager) Cdrecord 2.1.1a03 features: dvd-patch, gracetime, overburn, cdtext, clone, tao, cuefile, xamix, suidroot, plain-atapi, hacked-atapi, short-track-raw
k3b: (K3bExternalBinManager) 2 1 1 a03 seems to be cdrecord version >= 1.11a02, using burnfree instead of burnproof
k3b: (K3bExternalBinManager) seems to be cdrecord version >= 1.11a31, support for Just Link via burnfree driveroption
k3b: Devices:
k3b: ------------------------------
k3b: Blockdevice: /dev/hdb
k3b: Generic device:
k3b: Vendor: HITACHI
k3b: Description: DVD-ROM GD-8000
k3b: Version: 0005
k3b: MountDevice: /dev/cdrom
k3b: Mountpoint: /mnt/cd
k3b: Write speed: 0
k3b: Profiles: Error
k3b: Devicetype: CD-ROM; DVD-ROM
k3b: Writing modes: None
k3b: Reader aliases: /dev/hdb, /dev/dvd0, /dev/dvd, /dev/cdrom0, /dev/cdrom, /dev/cd/dvd-hdb, /dev/cd/cdrom-hdb
k3b: ------------------------------
k3b: (K3bFileTreeView::addCdDeviceBranches)
k3b: (K3bFileTreeView::addCdDeviceBranches) done
k3b: (K3bFileTreeView::addCdDeviceBranches)
k3b: (K3bFileTreeView::addCdDeviceBranches) done
k3b: (K3b::cutToWidth) not able to cut text to 36!
k3b: linux kernel version: 2.6.19-ARCH
k3b: (K3bCore) System problems:
k3b: - none -

For information, I can mount /dev/hdd and use any audio-cd view any data-cd with this device without problem... Strange :s

noriko · 2006-12-23 13:24:46

umm .. i dunno what's happening hre ....
what do u get from ..

cdrecord dev=help

ls -l /dev/hdd

u might also wanna re-run k3bsetup ...i'm sure the device is /dev/sr0 ... all cdrom* inc. /dev/cd/cdrom-sr0 points to /dev/sr0 .. on my system anyways ...

i also had add scsi to the hooks array on /etc/mkinitcpio.conf ...
i just had to cos i wanted to test this out, i never use the cd or floppy .. so i dunno if they were supposed to work with scsi out of it....

ronin · 2006-12-23 13:55:21

Thanks for answering,

Here is what I get:

[ronin@myhost ~]$ cdrecord dev=help
Supported SCSI transports for this platform:

Transport name: sg
Transport descr.: Generic transport independent SCSI
Transp. layer ind.:
Target specifier: bus,target,lun
Target example: 1,2,0
SCSI Bus scanning: supported
Open via UNIX device: not supported

Transport name: ATA
Transport descr.: ATA Packet specific SCSI transport
Transp. layer ind.: ATAPI:
Target specifier: bus,target,lun
Target example: ATAPI:1,2,0
SCSI Bus scanning: supported
Open via UNIX device: not supported

Transport name: ATA
Transport descr.: ATA Packet specific SCSI transport using sg interface
Transp. layer ind.: ATA:
Target specifier: bus,target,lun
Target example: 1,2,0
SCSI Bus scanning: supported
Open via UNIX device: not supported

Transport name: RSCSI
Transport descr.: Remote SCSI
Transp. layer ind.: REMOTE:
Target specifier: rscsi@host:bus,target,lun
Target example: REMOTE:rscsi@host:1,2,0
SCSI Bus scanning: supported
Open via UNIX device: not supported
[ronin@myhost ~]$ ls -l /dev/hdd
brw-rw---- 1 root optical 22, 64 déc 23 2006 /dev/hdd
[ronin@myhost ~]$ ls -l /dev/sr0
ls: ne peut accéder /dev/sr0: Aucun fichier ou répertoire de ce type
[ronin@myhost ~]$

I do not use scsi device so there is nothing for /dev/sr0

noriko · 2006-12-23 17:37:07

ahh.. that explains y it's at hdd ...
i got a few ?s ..

did it work before the kernel upgrade?
what did u change after/during upgrade?

also, it might be useful to revert to cdrecord pkg... if it worked before;

ls /var/cache/pacman/pkg/cdrecord*

should give u list of previous pks if they r still cached ...

install with

pacman -U /var/cache/pacman/pkg/[cdrecord]

ronin · 2006-12-23 19:00:46

It worked well before upgrade.

Unfortunately, cdrecord is not in cache anymore:

[ronin@myhost ~]$ ls /var/cache/pacman/pkg/cdr*
/var/cache/pacman/pkg/cdrdao-1.2.1-1.pkg.tar.gz
/var/cache/pacman/pkg/cdrdao-1.2.2-1.pkg.tar.gz
/var/cache/pacman/pkg/cdrkit-1.1.0-1.pkg.tar.gz
/var/cache/pacman/pkg/cdrtools-2.01.01a07-1.pkg.tar.gz
[ronin@myhost ~]$

I didn't change anything during or after upgrade, I just wanted to burn something after upgrade and then the problem came up...

:cry: For info, I tried pata driver whithout success so I'm still with ide driver.. :?

noriko · 2006-12-23 21:54:48

this is baffling xS ..
the only thing i cn suggest now is to

pacman -U var/cache/pacman/pkg/cdrtools-2.01.01a07-1.pkg.tar.gz

i think i got the pkg name wrong last time .. it's cdrtools ....

ronin · 2006-12-26 12:06:01

Thank you noriko,

It didn't help me but the problem is now solved, I did a fresh install with the 0.8 alpha release and everything is alright now

dedhart · 2007-01-16 03:29:53

Well between the new udev and cdrkit replacing cdrtools, I've had some trouble with my CD drives as well. I was about to post all "OMGWTF" in here when I saw another thread where a poster claimed to have errors in Graveman, but the CD still burned. I get the same:

Communication error with cdrecord. Check that you have access to cdrecord release 2.0 !

but then I checked my CD and lo and behold my data was burned, just a communication error at the end of the process I guess, but it seems that graveman still works despite the errors.

Romashka · 2007-01-16 09:47:19

I remember similar report about k3b and cdrkit.
It seems that k3b doesn't follow cdrkit's symlinks.
Just copy woodim to cdrecord. It should work.

Arch Linux

#1 2006-12-08 01:43:38

Can't burn with k3b

#2 2006-12-08 02:44:36

Re: Can't burn with k3b

#3 2006-12-08 16:41:57

Re: Can't burn with k3b

#4 2006-12-08 19:41:54

Re: Can't burn with k3b

#5 2006-12-08 20:50:48

Re: Can't burn with k3b

#6 2006-12-08 20:51:48

Re: Can't burn with k3b

#7 2006-12-08 20:59:36

Re: Can't burn with k3b

#8 2006-12-08 22:45:46

Re: Can't burn with k3b

#9 2006-12-09 05:10:07

Re: Can't burn with k3b

#10 2006-12-17 19:43:09

Re: Can't burn with k3b

#11 2006-12-22 19:25:36

Re: Can't burn with k3b

#12 2006-12-23 13:24:46

Re: Can't burn with k3b

#13 2006-12-23 13:55:21

Re: Can't burn with k3b

#14 2006-12-23 17:37:07

Re: Can't burn with k3b

#15 2006-12-23 19:00:46

Re: Can't burn with k3b

#16 2006-12-23 21:54:48

Re: Can't burn with k3b

#17 2006-12-26 12:06:01

Re: Can't burn with k3b

#18 2007-01-16 03:29:53

Re: Can't burn with k3b

#19 2007-01-16 09:47:19

Re: Can't burn with k3b

Board footer