3) With the ide-scsi.o driver, make sure that you don't have the ide-cd.o driver loaded, only the scsi-cd.o module loaded. If your kernel has UDMA support for you controller, make sure that is compile in too. I've got UDMA support for my motherboard compiled in and it seems as if I am getting better performance with the ide-scsi.o driver that with the native drivers for my motherboard as far as the CDROM is concerned... I'll need to do actual test to back this statement. mmm... a new lead! I'll check this one out.
Since the IDE driver loads first, if the ide-cd.o sees the CDROMs then the scsi-cd.o won't under the scsi-emulation. You'll also know if ide-scsi.o driver sees the CDRW because it will print the device info once it finds it... but it seems like you know that. :)
4) If you are using a old, slow computer, you may experience problems. The documentation for xcdrgtk talks about this a little. My Beast is a 1GHz Athlon with 512MB of RAM... neither old nor slow! Thanks JLK
I have the exact same setup but I own one of the cheaper Lite-On 8x4x32x CDRW. Under xcdrgtk, I've also setup my burner buffer to be 8Megs since the on board buffer is 2megs, if figure that this would solve any underrun issues. My MB has the VIA chipset which the 2.4.x kernel has good UDMA support for... If you're MB chipset is supported, I would compile it in for the performance increase and agp support. :) -- =========== =========== Jonathan Paul Cowherd jpcowh01@slug.louisville.edu http://www.slug.louisville.edu/~jpcowh01 This is my world and I am... World Leader Pretend =========== ===========