It's a command-line utility, which means it doesn't have a graphical-user-interface. In simple terms, think "DOS application". I'm still slightly surprised people don't know what these are. These were all the rage a few years ago, and now, it seems as though no ones heard of them!
Basically, you need to open the command prompt. This is done by clicking the Start button > Programs > Accessories > Command Prompt. I'm going to essentially quote HCS at this point, rather than rewriting everything:
"Once in the command prompt, you navigate to the directory that contains the exe and the *.XA files. The beginning of the line tells you the current directory; you can go to a subdirectory by typing "cd DirectoryName" and you can go up to the containing directory by typing "cd ..". The easiest thing to do is to just say "cd \the\full\path" where "\the\full\path" is the whole path to the directory that contains your file. If you have different drives you may have to switch to the right drive letter first, by typing "C:" to get to the C: drive, or whatever drive it may happen to be on.
"Once you're in the right directory, typing "test" should run the program, it will give you an "Argument error" but that will at least confirm that you can run it."
You'll need the external DLLs in the same directory as test.exe (did you read the readme? It's there for a reason) for it to run. It will give you a list of options/arguments that VGMstream (aka test.exe) needs to know to process the file. To simply convert XA to WAV you should be able to type "test -o OutPutFileName.WAV InputFileName.XA" where "OutPutFileName.WAV" is the name of the WAV you want to create, and "InputFileName.WAV" is the XA you want to convert. To convert an entire directory of XA files to WAV files, you should be able to type:
for %A in (*.xa) do test -o "%A.wav" "%A"
^ In the above, if your files have spaces, the " marks are probably required, otherwise leave them out.
That should work for you, and convert all your XA files to waves. Good luck, and if that still doesn't work, I messed up. Come back, ask again, and I'm sure someone will answer correctly. Mouser X over and out.
According to Google's translator, the error message says:
---------------- C:\Program Files\foobar2000\components\test.exe was loaded but the DllRegisterServer entry point not found
C:\Program Files\foobar2000\components\test.exe is not a DLL or. Ocx file ----------------
What are you trying to do, and how are you trying to do it? Test.exe is a program, not a foobar2000 plugin/component. If you follow the process I went through in my last post, test.exe should convert the XA files to WAVs. You do not need foobar2000, or any other program, (except Windows, the OS) to run test.exe (but you do need the appropriate DLLs, as you've noticed). As such, I'm confused as to how this error message occurred, and from where it originated.
Did you try running test.exe from the command prompt as mentioned in my last post? If yes, I am thoroughly at a loss as to what's going on. What I interpret from the error message is that you attempted to "force" foobar2000 (or some other program) to load test.exe as a component/plugin, and that failed (which it should). I can't see how you could even get that kind of error message when running test.exe properly (from the command-prompt). Since HCS wrote it (well, with help from others to figure out various formats), maybe he'd have some better idea as to what's going on. Mouser X over and out.
I'm pretty old skool, but I still have "PSMPlay" and I use that to load up XAs (off an ISO, not the disc) and then convert them to wavs and that's all there is to it..
Here is my attempt to clarify the process the best I possibly can. I have uploaded a step-by-step process, in picture form, in the hopes that this will clear up any issues you're having. If it doesn't, I can't help you, as the problems you're describing do not match any experience I have ever had with this sort of thing.
You should now have a black box/window open that looks like this (specifically, I'm using Windows 7. The only real difference between Windows OS versions is the directory it opens to):
Step 03 - running VGMstream (aka, "test.exe") * Now push "enter" and type "test" (this is to make sure that test.exe is running properly) * It will look like this * Push "enter" to run "test". This will run "test.exe with no arguments/options. Test.exe will display what options are available to you. * Type the commands/options you want to get test.exe to decode the files. Specifically, here I've typed:
for %i in (*.xa) do test.exe -o "%i.wav" "%i"
This tells VGMstream (aka test.exe) to decode "%i" to "%i.wav" with no extra options. Windows/DOS will replace the %i with the appropriate file name automatically.