Windows operating system...

[pkd_lives]

Is not on my computeer anymore. Well technically it is, but what happens is a black screen starts up when I select it and in white text the message Loading Windows appears. My hardrive seems to be permanently addressed and nothing else happens.

Now last night I figured out CDrecord (or rather the X-cd-roast graphical face anyway). Which meant that only one item on my must be able to do list is uncompleted. I want Linux so I can do other stuff without paying thousands of dollars for something I used to be able to do as part of the operating system (programming for instance).

So the only thing I can't do is scanning, and I am going to find a Linux compatable scanner, and I'm in no rush, as I don't use scanning much. So I'm gonna run Diskdrake and remove the fat partition. I think I can say I'm Linux now. Not claiming to know anything about it yet (but then what did I ever know about Windows from official courses?)

To anyone else considering the switch...It is really easy with the Noob distros. Just remember how you learnt Windows. You kept doing stuff until it crashed again, and learnt your lessons. I lost count of how many times I've installed Windows over the years, always learnt something new, well Linux is like that too, just a slightly steeper learning curve.

[ October 08, 2002: Message edited by: pkd ]

[voidmain]

Speaking of CD burning, have you tried "koncd"? It's a new command in KDE 3.x (you can use it under gnome as well if it is installed). I personally haven't because I like plain old "cdrecord" on the command line or a script that I have written that uses "cdrecord". I just ran "koncd" and it looks pretty cool. Haven't tried to burn anything with it.

[Pantso]

I've tried koncd in KDE 3.0 I think to burn some CD's. Cool little app and very stable but I liked cdrecord more. Everything works faster when you know how to use the console    

[ October 08, 2002: Message edited by: Panos ]

[pkd_lives]

Wohoa there.

Hey I'm just figuring this stuff out. I got cdrecord under GUI configured.

Now I can do the stuff I did on windows (mostly), I can now start to LEARN my OS.

[Ice-9]

quote: Speaking of CD burning, have you tried "koncd"? It's a new command in KDE 3.x (you can use it under gnome as well if it is installed). I personally haven't because I like plain old "cdrecord" on the command line or a script that I have written that uses "cdrecord". I just ran "koncd" and it looks pretty cool. Haven't tried to burn anything with it.

void main, have you tried it under SuSE?
Xcdroast works fine (except that the version I have doesn't support multisession) but I never could make Koncd work, I get "mkisoff not installed" while it is installed, 100% sure since I checked 3 times for the packages.

[ October 09, 2002: Message edited by: Ice9 ]

[Calum]

hey, this is interesting, is this koncd thing a totally new program? that doesn't require cdrecord?

the thing i have with cdrecord is that i have a cantankerous cdwriter (here is the link to the exact specifications of my cdrw) and while theoretically it is recognised by the kernel, i don't think cdrecord supports it.

Maybe i could get this new cdwriting program and actually use my cdrw? it used to work in windows only, but has now stopped doing even that, and i really need to burn a few gigs of stuff...

[ October 09, 2002: Message edited by: Calum ]

[voidmain]

quote:Originally posted by Calum:
hey, this is interesting, is this koncd thing a totally new program? that doesn't require cdrecord?

the thing i have with cdrecord is that i have a cantankerous cdwriter (here is the link to the exact specifications of my cdrw) and while theoretically it is recognised by the kernel, i don't think cdrecord supports it.

Maybe i could get this new cdwriting program and actually use my cdrw? it used to work in windows only, but has now stopped doing even that, and i really need to burn a few gigs of stuff...

It uses "cdrecord" as do all CD burning apps for Linux that I am aware of. If the kernel recognizes the drive then cdrecord should be able to use it. However, cdrecord only can access SCSI burners. That's not a problem because the ide-scsi module will make your IDE CD burner show up to Linux as a SCSI device. Do an "ls -alp /dev/cdrom". This should be a sybolic link to a real device file. If your installation has the ide-scsi module properly configured the link will point to "/dev/scd0" which is the first SCSI CD-ROM. If it is not using the ide-scsi module it will probably be pointing to "/dev/hdc" which is an IDE device.

The newer RedHats detect and set this up automatically, it was something that had to be set up manually in the old days. Now it appears that yours is a USB drive, in which case I think you are out of luck, at least for the time being. It supports most IDE and SCSI burners that I am aware of.

[Calum]

isn't there some hack i can apply in order to use my usb drive as a scsi drive? if i recall, nero in windows thinks the usb drive is a scsi one.

[voidmain]

quote:Originally posted by Calum:
isn't there some hack i can apply in order to use my usb drive as a scsi drive? if i recall, nero in windows thinks the usb drive is a scsi one.

Just because someone wrote a Windows driver (probably the CD manufacturer or Nero themselves) doesn't mean that someone wrote a Linux driver. As far as I know this drive is not currently supported. But then I don't have one and haven't done a lot of research on the matter. I would search google and if nothing comes up then you would either have to write your own driver or get a different drive. I know you didn't start using Linux until after you had your hardware but this is why I always do the research before purchasing the equipment. I don't support manufacturers that do not support Linux.

[ October 09, 2002: Message edited by: void main ]

[mobrien_12]

I use a USB CD burner.  It works automatically as a SCSI drive.  It works very well in Linux, but I had to DL and compile recent versions of cdrecord and XCDroast.   Before I did this, CD burning under linux was unreliable and could lock the system up.

Check your boot logs.  They will tell you if the drive is recognized as a SCSI drive.

[beltorak0]

[probably off topic] I use x-cd-roast whenever i burn cd's.  my problem is i can't seem to remember all the command line switches for mkisofs and cdrecord, so everytime I use the console to do it, i end up spending 15 to 20 minutes in the man pages.

I also wrote a small perl script to take a playlist generated by music match (my wife still uses W98 exclusivly) and transfer them over to the linux partition, reformatting the file path so it will play in xmms.

And I wrote one other small perl script, because x-cd-roast doesn't have the option to grab the filenames to include in the cd from a file (the [consulting man page; please wait] mkisofs -path-list option).  It creates a directory specified by the user in /usr/local/cdimg/ and adds a symlink for each song specified in the playlist.  I can then use xcdroast to burn the cd, setting the "options" tab option to "follow symlinks".  This sure beats the way I did it at first -- i copied each song to a new directory, then made the iso, the burnt the cd.  in effect I had two duplications of each song until I got around to clearing the directories and cdimages.  ack.

I plan to write a front end, or maybe the entire thing, in a tcl/tk script when I get the time to learn tcl/tk.

-t.

[voidmain]

quote:Originally posted by beltorak0:
[probably off topic] I use x-cd-roast whenever i burn cd's.  my problem is i can't seem to remember all the command line switches for mkisofs and cdrecord, so everytime I use the console to do it, i end up spending 15 to 20 minutes in the man pages.

So you wrote all those other scripts, why didn't you just write a simple script to wrap around "cdrecord" so you don't have to look up the options all the time? For instance, I just type "mkcd filename.iso" to burn an ISO image. "mkcd" is a simple little bash script I wrote:

Code: [Select]

Basically it takes your "filename.iso" and starts a burn in the background so you can even log off if you want and come back later to check on it. If you want to watch the progress just do a "tail -f /tmp/mkcd.log".

Also, if you set up your /etc/cdrecord.conf properly you don't need to give most of the device parameters on the command line. Then, if you want to blank a disk it would be a simple as:

cdrecord blank=fast

Of course you could always put that in it's own script and call it "blankcd" if that will stick in your memory better.

[ October 10, 2002: Message edited by: void main ]