All Things Microsoft > Microsoft Software

Windows operating system...

<< < (3/3)

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.

--- End quote ---


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: ---
--- End code ---

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 ]

Navigation

[0] Message Index

[*] Previous page