Hi all - Right. Let's start again. Taking on board the valuable suggestions of Jason and Bandipat I've removed myself from "disk" and created a new group called "burning" I'm sorry if I've been slow but I'm only now beginning to understand the role and purpose of k3bsetup. Intuitive it aint. Anyway, I've used k3bsetup to create the necessary permissions for the "burning" group. If I run k3bsetup now - without going into administrator mode - k3bsetup gives the following information (and it seems spot on to me) : ================================== Use burning group : burning SAMSUNG CD-R/RW /dev/sr0 660 root.burning no change SAMSUNG DVD-ROM /dev/hdd 660 kmp.burning no change cdrdao /usr/bin/cdrdao 4710 root.burning no change cdrecord /usr/bin/cdrecord 4710 root.burning no change readcd /usr/bin/readcd 4710 root.burning no change ==================================== Note there's nothing for mkisofs - otherwise it seems perfect. I've logged out and back in. I'm definitely in the "burning" group. When I run k3b it gives the usual ATAPI message but otherwise seems happy. When it comes to burning though I still get a no permissions for /dev/pg0 and it stops. /dev/pg0 is set like this: crw-rw-rw- 1 root disk 97, 0 2003-09-23 19:01 /dev/pg0 Should I change its group to "burning"? Otherwise I'm all out of ideas. By the way cdrecord -scanbus as user still produces cdrecord: No such file or directory. Cannot open SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root. cdrecord: For possible transport specifiers try 'cdrecord dev=help'. If cdrecord is running suid, shouldn't it produce the same output as it does for root? Best wishes - Ken