-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Registration Account wrote: > Thank you all for your support and I am very pleased > that mostly all user have no issues with KB3... > > I would like someone to try something out for me on > another KB3 install that has no problems. > > This is going to sound really weird please bear with me > > 1. Can someone try to burn a Data CD and burn only > MS-Windows .EXE files > > 2. Can someone who has XP burn some files - any type > onto a CD....Then remove the CD from XP session and > then use KB3 to erase the disk. > > > Right now I cannot get KB3 to erase a CD let alone burn > an iso image!!!!!!!!!!!!! > > There are irregularities away from CUA with selection > of files in the top window (directory/files listing) > using SHIFT+CLICK....I have written a bug report for > this. I am amazed that some one has not done this. AND > Konqueror has bizarre handling using SHIFT + CLICK. > > There were a number of other issues I noted with the > usability that I thought were very limiting. To > suddenly find a Linux application presenting a Dialogue > box is very strange. The one thing I first loved about > Linux was the absence of dialogue boxes that locked you > out of the application until the Dialogue was satisfied. > > There were a few other issues I also noted, but as I > cannot even erase a CD at the moment without a debug or > attempt to burn without a debug I am sort of stopped in > my tracks. > > I know what you are probably thinking that Scott's gone > mad about the 1 and 2 scenario, however I have a > suspicion as to what's happening. > > I await our next therapy appointment > > cheers to all > > Scott 0-) > <snip>
I know you are not a CLI fan but if all else fails :-) try wodim dev=<your cdwriter name> blank=all with the cd to erase in drive, at the CLI and look at response. This should tell you if you have an issue with wodim (or the drive configuration). As K3B frontends for wodim/cdrecord this will hopefully narrow your problem down. This should zap everything on CD ... may take some time. K3B actually is a bit lax on error reporting so command line should get more detail ... If this works then try .... wodim -v dev=<your cdwriter name> <iso_name> to burn an extant iso.image <iso name>... The output here may be a bit obscure if things go wrong but can be used diagnose some hardware issues... You may also gets some clues as whether you need to tweak the write speed or buffer size. K3B takes care of the complicated bit (creating an iso image) very effectively, but really does make the burning a bit unclear. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGdmEFasN0sSnLmgIRAqJqAJ9L65EwVxffP09Lr8xGu6cZXLWWKACfZ02g 9Mg4C3hITSK0g8SzP2UWt9I= =qV5P -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
