| WIKI | FAQ | Tech FAQ | |
 http://csua.com/feed/ | |
| ||||||
| 5/24 |
| 2004/8/10-11 [Computer/SW/OS/Windows, Computer/HW/Drives] UID:32812 Activity:moderate |
8/10 What command line tool exist for windows to create an iso image
from a directory structure? or from a set of files specified
on the cmd line or a input file? thanks.
\_ mkisofs. oh wait, you said "command line tool ... windows"
\_ Uhm, cdr-tools (where mkisofs comes from) has been
ported to Windows for quite some time now. Just google
it (some german guys wrote this). Oh wait, you're a moron...
\_ I am a moron who doesn't use Windows.
\_ despite your deleting this there is still mkisofs for windows:
http://www.dimensional.com/~sitaram/CD-R-for-CLUEd-in-Windows-users.html
http://tinyurl.com/4vm69
\_ Try daemontools but I haven't tried it in a looong time.
\_ Daemon Tools mounts ISo images, not creates them, yes?
\_ Daemon Tools mounts ISO images, not creates them, yes?
\_ I really don't remember. Like I said its been a long time.
Maybe their site will point you to writing tools if they
don't have them. |
| 5/24 |
|
| www.dimensional.com/~sitaram/CD-R-for-CLUEd-in-Windows-users.html Thanks The command line way to burn CDs in Windows Why command line CD-R? I wrote this for a friend who just couldn't get the CD-R software on his machine to write to 700 MB (80 minute) blanks. I have also seen software that will not let you burn from ISO images, nor burn files coming off a network share, etc. Since the hardware can do it, I can only imagine that the software that comes free with it is intentionally crippled, perhaps to force you to shell out for a "full" version. Anyway, I was burned (pun intended) by one such piece of software once, so I decided to explore alternatives. I very quickly found that the cdrecord toolset that I knew from Linux had been ported to Windows! I have been using this Windows port for some time now, whenever I had to use a CD burner hooked to a Windows machine. I have now decided to write up this little document to help people like the friend I mentioned above. This document will help you use command line CD-R tools on a Windows machine. I am only going to talk about the simplest cases, like burning the contents of one complete directory, or burning from an ISO image you downloaded, etc. Incidentally, that site is full of interesting software, much that Linux people will be already familiar with, and some that they may not be. It's worth a visit or two, and in fact is in my permanent bookmarks. If you are familiar with the command line CD-R tools on Linux, you can skip the rest of this document. Maybe all you needed then was to know that they are available on Windows, and the URL above. Contents of the toolkit The ZIP file mentioned above contains the following programs. I have marked with an arrow the 3 files we really need for this short tutorial. Also note that this ZIP file does not have any documentation. This is fine, since any Linux machine will have the manpages (usually) and I presume the website also has documentation somewhere. ppt Step 1 - make an ISO image CDs use a filesystem called ISO9660. Burning a CD involves two distinct steps -- creating the filesystem and allocating the files on it, and then writing out the filesystem to the CD. The corresponding commands (see above) are mkisofs and cdrecord. The problem is, once the burn starts, it should NOT be interrupted for any reason. unless it's a CD-RW disk you may as well use it for a coaster. Hence it is important to "feed" the CD Writer as fast as it can gobble up the data! A really fast system can actually do both steps together, piping the result of mkisofs into cdrecord. However, I would not advice this on Windows, where the simplest things can load the system unexpectedly and piping may not work as reliably as it does on Unix. I strongly suggest you use both the "-J" and the "-R" flags. Read the manpages for cdrecord :-) Also note the FORWARD slashes on the file paths I gave. This is because the command is actually processed by cygwin (so it's sort of like you typed it at a Unix prompt, in some ways). Vicky is the guy I wrote this for, so the subdirectory has his name. Step 2 - Find out where your CD Writer is The CD-R tools assume that the CD writer is a SCSI device sitting on a SCSI bus. They need to be given a SCSI "target", which is 3 numbers separated by commas. The magic of this port of the CD-R tools is that, somehow, any Windows CD Writer looks like a SCSI drive. Anyway, you start by "scanning" the "SCSI bus", looking for SCSI devices. Anyway, as you can see, my CD writer is denoted by "1,0,0". All you have to do is visually identify (from the description) your CD Writer, and note down the three numbers corresponding to it. In the commands that follow, please change 1,0,0 to whatever you get when you run cdrecord -scanbus! Driver flags : SWABAUDIO Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R Starting to write CD/DVD at speed 2 in write mode for single session. You'll see the line above, counting down from 10 seconds, then, when the countdown expires, you see: Last chance to quit, starting real write in 0 seconds. and finally it comes back to the command prompt if there were no errors. C:\vicky> Step 3 - make a dummy run This is not strictly needed if you followed my recommendation and created the ISO image already. But if you're paranoid, or your system is kind of slow or loaded, or you want to record at higher speeds, you should make a dummy run to see if the real burn will have any problems. index: 11 Manufacturer: Mitsubishi Chemical Corporation Blocks total: 336075 Blocks current: 336075 Blocks remaining: 329609 Starting to write CD/DVD at speed 4 in dummy mode for single session. Starting new track at sector: 0 Track 01: 12 of 12 MB written (fifo 100%). Track 01: Total bytes read/written: 13238272/13238272 (6464 sectors). cdrecord: fifo was 0 times empty and 78 times full, min fill was 89%. The thing to look for in this output is the line that says cdrecord: fifo was 0 times empty and 78 times full, min fill was 8 9%. If it says anything other than "0 times empty" you're in trouble. If the "min fill" was anything less then 75% you may want to consider reducing the speed. It's a memory area, 4 MB by default, that the cdrecord program maintains. Should the system that is feeding "cdrecord" become slow, it would still have 4 MB of data to send to the writer, and hopefully in that time the input process would be able to catch up. index: 11 Manufacturer: Mitsubishi Chemical Corporation Blocks total: 336075 Blocks current: 336075 Blocks remaining: 329609 Starting to write CD/DVD at speed 4 in write mode for single session. Starting new track at sector: 0 Track 01: 12 of 12 MB written (fifo 100%). Track 01: Total bytes read/written: 13238272/13238272 (6464 sectors). cdrecord: fifo was 0 times empty and 77 times full, min fill was 89%. However the 4 PPTs, since they were explicitly named, made it into the disk as is. This is an important point to remember: if any of the parameters you give are directories, they won't make it to the CD -- only their contents will make it. |
| tinyurl.com/4vm69 -> www.dimensional.com/~sitaram/CD-R-for-CLUEd-in-Windows-users.html Thanks The command line way to burn CDs in Windows Why command line CD-R? I wrote this for a friend who just couldn't get the CD-R software on his machine to write to 700 MB (80 minute) blanks. I have also seen software that will not let you burn from ISO images, nor burn files coming off a network share, etc. Since the hardware can do it, I can only imagine that the software that comes free with it is intentionally crippled, perhaps to force you to shell out for a "full" version. Anyway, I was burned (pun intended) by one such piece of software once, so I decided to explore alternatives. I very quickly found that the cdrecord toolset that I knew from Linux had been ported to Windows! I have been using this Windows port for some time now, whenever I had to use a CD burner hooked to a Windows machine. I have now decided to write up this little document to help people like the friend I mentioned above. This document will help you use command line CD-R tools on a Windows machine. I am only going to talk about the simplest cases, like burning the contents of one complete directory, or burning from an ISO image you downloaded, etc. Incidentally, that site is full of interesting software, much that Linux people will be already familiar with, and some that they may not be. It's worth a visit or two, and in fact is in my permanent bookmarks. If you are familiar with the command line CD-R tools on Linux, you can skip the rest of this document. Maybe all you needed then was to know that they are available on Windows, and the URL above. Contents of the toolkit The ZIP file mentioned above contains the following programs. I have marked with an arrow the 3 files we really need for this short tutorial. Also note that this ZIP file does not have any documentation. This is fine, since any Linux machine will have the manpages (usually) and I presume the website also has documentation somewhere. ppt Step 1 - make an ISO image CDs use a filesystem called ISO9660. Burning a CD involves two distinct steps -- creating the filesystem and allocating the files on it, and then writing out the filesystem to the CD. The corresponding commands (see above) are mkisofs and cdrecord. The problem is, once the burn starts, it should NOT be interrupted for any reason. unless it's a CD-RW disk you may as well use it for a coaster. Hence it is important to "feed" the CD Writer as fast as it can gobble up the data! A really fast system can actually do both steps together, piping the result of mkisofs into cdrecord. However, I would not advice this on Windows, where the simplest things can load the system unexpectedly and piping may not work as reliably as it does on Unix. I strongly suggest you use both the "-J" and the "-R" flags. Read the manpages for cdrecord :-) Also note the FORWARD slashes on the file paths I gave. This is because the command is actually processed by cygwin (so it's sort of like you typed it at a Unix prompt, in some ways). Vicky is the guy I wrote this for, so the subdirectory has his name. Step 2 - Find out where your CD Writer is The CD-R tools assume that the CD writer is a SCSI device sitting on a SCSI bus. They need to be given a SCSI "target", which is 3 numbers separated by commas. The magic of this port of the CD-R tools is that, somehow, any Windows CD Writer looks like a SCSI drive. Anyway, you start by "scanning" the "SCSI bus", looking for SCSI devices. Anyway, as you can see, my CD writer is denoted by "1,0,0". All you have to do is visually identify (from the description) your CD Writer, and note down the three numbers corresponding to it. In the commands that follow, please change 1,0,0 to whatever you get when you run cdrecord -scanbus! Driver flags : SWABAUDIO Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R Starting to write CD/DVD at speed 2 in write mode for single session. You'll see the line above, counting down from 10 seconds, then, when the countdown expires, you see: Last chance to quit, starting real write in 0 seconds. and finally it comes back to the command prompt if there were no errors. C:\vicky> Step 3 - make a dummy run This is not strictly needed if you followed my recommendation and created the ISO image already. But if you're paranoid, or your system is kind of slow or loaded, or you want to record at higher speeds, you should make a dummy run to see if the real burn will have any problems. index: 11 Manufacturer: Mitsubishi Chemical Corporation Blocks total: 336075 Blocks current: 336075 Blocks remaining: 329609 Starting to write CD/DVD at speed 4 in dummy mode for single session. Starting new track at sector: 0 Track 01: 12 of 12 MB written (fifo 100%). Track 01: Total bytes read/written: 13238272/13238272 (6464 sectors). cdrecord: fifo was 0 times empty and 78 times full, min fill was 89%. The thing to look for in this output is the line that says cdrecord: fifo was 0 times empty and 78 times full, min fill was 8 9%. If it says anything other than "0 times empty" you're in trouble. If the "min fill" was anything less then 75% you may want to consider reducing the speed. It's a memory area, 4 MB by default, that the cdrecord program maintains. Should the system that is feeding "cdrecord" become slow, it would still have 4 MB of data to send to the writer, and hopefully in that time the input process would be able to catch up. index: 11 Manufacturer: Mitsubishi Chemical Corporation Blocks total: 336075 Blocks current: 336075 Blocks remaining: 329609 Starting to write CD/DVD at speed 4 in write mode for single session. Starting new track at sector: 0 Track 01: 12 of 12 MB written (fifo 100%). Track 01: Total bytes read/written: 13238272/13238272 (6464 sectors). cdrecord: fifo was 0 times empty and 77 times full, min fill was 89%. However the 4 PPTs, since they were explicitly named, made it into the disk as is. This is an important point to remember: if any of the parameters you give are directories, they won't make it to the CD -- only their contents will make it. |