Kerry's post looks very promising: | It can but is probably not as nice as you would like.
It's a huge improvement over what I can do now. Thank you! | flac -t *.flac Now, that doesn't work for me. I know that command.com doesn't glob wildcards but rather expects the application to do it, and apparently flac.exe doesn't. Under a real shell that wouldn't be a problem, because the shell would glob the asterisk. | if errorlevel 1 goto fail | goto exit | :fail | echo Danger Will Robinson! Flac files failed integrity check. | :exit OK then, would this work: flac -t somefile.flac if errorlevel 1 goto fail echo "somefile.flac verified" >> results.txt goto exit :fail echo "somefile.flac did not verify" >> results.txt :exit for each flac file? | This method won't tell you which files passed or failed. It doesn't need to. Since the wildcard isn't globbed, and since I'd start with the batch file that Speek's front-end would write, I'd be invoking flac -t separately on each file anyway. Now, could I do this for two or more flac files (using two as an example) in one batch file ... flac -t file01.flac if errorlevel 1 goto fail echo "file01.flac verified" >> results.txt goto exit :fail echo "file01.flac did not verify" >> results.txt :exit flac -t file02.flac if errorlevel 1 goto fail echo "file02.flac verified" >> results.txt goto exit :fail echo "file02.flac did not verify" >> results.txt :exit or would the duplicate labels cause a problem? If they would, what about this? flac -t file01.flac if errorlevel 1 goto fail01 echo "file01.flac verified" >> results.txt goto continue02 :fail01 echo "file01.flac did not verify" >> results.txt :continue02 flac -t file02.flac if errorlevel 1 goto fail02 echo "file02.flac verified" >> results.txt goto exit :fail02 echo "file02.flac did not verify" >> results.txt :exit or maybe this, verifyfile01.bat verifyfile02.bat where verifyfile01.bat contains this, flac -t file01.flac if errorlevel 1 goto fail echo "file01.flac verified" >> results.txt goto exit :fail echo "file01.flac did not verify" >> results.txt :exit and verifyfile02.bat contains this: flac -t file02.flac if errorlevel 1 goto fail echo "file02.flac verified" >> results.txt goto exit :fail echo "file02.flac did not verify" >> results.txt :exit At this point I wouldn't mind uploading the filenames of the flac files to one of my Unix shell accounts, using shell or sed scripts there to prepare the batch files, and downloading the batch files to run under command.com on my own machine. On the surface it might seem more straightforward to compile flac on one of the Unix boxes (that's possible, right?), upload flac files there, and do the testing there, but my upload throughput is in the range of 1 Mb per minute and the most generous storage quota I have is 50 Mb, so the dance of uploading filenames and downloading batch files would take much less time. | Cygwin will let you do it and there might be a wrapper utility somewhere | on the simtel repository to do it as well; I think | it is in sysutils or textutils in the msdos section. Cygwin looks like way too much for me to tackle and may be too much for my underpowered computer. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Flac-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/flac-users
