On Sat November 27 2004 12:29 pm, Patrick Shanahan wrote:

* James Hatridge [11-27-04 12:24]:

...

OK, I have an old SCSI cd burner. SuSE 9.2 see it as /dev/sr0 and lists it as /media/cdrom2. I can read a cd with it, no problem. BUT k3b can not find it either as user or root. It worked fine under 9.1 and older.

/opt/kde3/bin/k3bsetup

No such file, Patrick and "-setup" isn't a viable command line option either. k3b works for me here, but I wanted to check out the file. 'Found it doesn't exist. Fred -- "As Internet technology itself vaults into new areas, so too does the Microsoft monopoly and its tried-and-true bag of tricks." -US Senator Orrin Hatch, (R) Utah

On Sat November 27 2004 3:43 pm, Patrick Shanahan wrote:

* Fred Miller [11-27-04 15:20]:

...

On Sat November 27 2004 12:29 pm, Patrick Shanahan wrote:

...

/opt/kde3/bin/k3bsetup

No such file, Patrick and "-setup" isn't a viable command line option either. k3b works for me here, but I wanted to check out the file. 'Found it doesn't exist.

locate k3b|grep bin note: still 9.0

look for a setup option on one of the drop down menu's available on k3b tool bar, ie: Settings -> k3b setup Settings -> Configure k3b ...

rpm -ql k3b|grep setup

skinning cats is fun if you don't do it the same way every time <grin>.

Hehehehe.....yes. The only way I could get k3b to "see" the hardware, was to change permissions on /dev/cdrom, /dev/cdreorder, and the cdrecord etc. files. Fred -- "As Internet technology itself vaults into new areas, so too does the Microsoft monopoly and its tried-and-true bag of tricks." -US Senator Orrin Hatch, (R) Utah

HI Pat & Fred, My /dev list looks like this below. But k3bsetup is not there and so on. Can one of you guys show me your fstab file for your burnner? This is starting to be a pain in the ass. When I try to use k3b's setup I get this error: Could not find an additional device at /dev/sr0 I get this error in both user and root. Any other ideas? Thanks, JIM On Saturday 27 November 2004 22:53, Patrick Shanahan wrote:

* Fred Miller [11-27-04 16:22]:

...

Hehehehe.....yes. The only way I could get k3b to "see" the hardware, was to change permissions on /dev/cdrom, /dev/cdreorder, and the cdrecord etc. files.

o:~> l /dev/cdrom /dev/cdrecorder /dev/sr0 /dev/sr1 lrwxrwxrwx 1 root root 3 2003-12-07 19:15 /dev/cdrecorder -> sr0 lrwxrwxrwx 1 root root 3 2003-12-20 22:15 /dev/cdrom -> sr1 brw------- 1 pat disk 11, 0 2003-10-02 15:45 /dev/sr0 brw------- 1 pat disk 11, 1 2003-10-02 15:45 /dev/sr1

-- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos

-- Jim Hatridge Linux User #88484 ------------------------------------------------------          WartHog Bulletin           Info about new German Stamps    http://www.fuzzybunnymilitia.org/~hatridge/bulletin             Viel Feind -- Viel Ehr'       Anti-US Propaganda stamp collection   http://www.fuzzybunnymilitia.org/~hatridge/collection

On Sunday 28 November 2004 01:52 pm, James Hatridge wrote:

HI Pat & Fred,

My /dev list looks like this below. But k3bsetup is not there and so on. Can one of you guys show me your fstab file for your burnner? This is starting to be a pain in the ass.

When I try to use k3b's setup I get this error:

Could not find an additional device at /dev/sr0

I get this error in both user and root. Any other ideas?

Thanks,

JIM [...] -- Jim Hatridge Linux User #88484 ------------------------------------------------------     

Jim, If memory serves me, you are running some SuSE 9.x version right now? I believe, since 9.0, the new cdrecord does not need scsi emulation. If you have it started in Grub or have changed or added symlinks to that effect, you are probably going to have problems with an IDE cdrw. I believe that is what you have? I have the IDE unit and k3b has not failed to work under any of the 9.x versions as user. I don't even recall the last time I ran k3bsetup. If you are indeed using a scsi cdrw, I can't lend much assistance with that, as normally they should just work correctly. The 2.6.8 kernel did not cause any problems here for user to burn, so I'm guessing SuSE fixed or someone else patched the necessary thing to allow that. good luck, Lee