On Tue, 28 Oct 2003 11:35:13 -0000 "Tony S. Sykes" <[EMAIL PROTECTED]> wrote:
> msec? > > -----Original Message----- > From: Lee Wiggers > [mailto:[EMAIL PROTECTED] Sent: Tuesday, > October 28, 2003 11:20 AM To: [EMAIL PROTECTED] > Subject: Re: [newbie] Gcombust Question > > > On Mon, 27 Oct 2003 12:33:47 +0000 > John Richard Smith <[EMAIL PROTECTED]> wrote: > > > Lee Wiggers wrote: > > > > >I tried to burn a few .mp3's this morning with Gcombust and got > > >the following: > > > > > >/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'. Make sure you are root. > > >/usr//bin/cdrecord: For possible transport specifiers try > > >'cdrecord dev=help'. > > > > > >After cdrecord -scanbus (which located my scsi emulation) I > > >tried again and got a burn, but unreadable. Drive just churns > > >on it. > > > > > But did you do anything with it, > > Somewhere in Gcombust there is a tab "locate device" which sets > > out to locate where your > > device is located on the bus and set that a default. One problem > > you may be experiencing, like me, is that depending how many USB > > devices I have plugged in at the time, the writer "goes walkies > > around the bus" each time you boot up, it's easy enough to > > rectify if you locate that tab I just mentioned. > > > > Alternatively you can use xcdroast (on you 3 CD's somewhere) > > which > > > > automatically detects when something has changed on the bus and > > gives you a warning message "something has changed on the bus" > > or some such warning, and you can reselect the correct device in > > settings. > > > > > > John > > > > -- > > John Richard Smith > > [EMAIL PROTECTED] > > > > > > > > > Thank you both. > > I burned with great success as root, then tried as user and got > the same as before. > > Simple. Forgot to check permissions on CDrom. Added user write > permission and it works fine. Probably didn't need to burn once > in root, but now I'll never know. > > It did point me where I should have been at the beginning though. > Could swear I checked permissions originally. Maybe checked file > and forgot dev. > > ...Dang it, I know I checked dev. Is there anything that would > change it back when I wasn't looking? Maybe I'm losing it? Early > senility? > > Destined to die a newbie. > > Thanks for the help. > > Lee > > -- > User #223705 Linux Counter, http://counter.li.org > > > -+-+-+-+-+-+-+- Business Computer Projects - Disclaimer > -+-+-+-+-+-+-+- > > This message, and any associated attachment is confidential. If > you have received it in error, please delete it from your system, > do not use or disclose the information in any way, and notify > either Tony S. Sykes or the postmaster > <mailto:[EMAIL PROTECTED]> immediately. > > The contents of this message may contain personal views which are > not necessarily the views of Business Computer Projects Ltd., > unless specifically stated. > > Whilst every effort has been made to ensure that emails and their > attachments are virus free, it is the responsibility of the > recipient(s) to verify the integrity of such emails. > > > Business Computer Projects Ltd > BCP House > 151 Charles Street > Stockport > Cheshire > SK1 3JY > > Tel: +44 (0)161 355-3000 > Fax: +44 (0)161 355-3001 > Web: http://www.bcpsoftware.com <http://www.bcpsoftware.com/> > > Must be msec. perms are back to root as we speak. Can anyone tell me how to make the changes stick? Lee -- User #223705 Linux Counter, http://counter.li.org
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
