Wed May 27 19:31:00 GMT 2015
On May 22, 2015, at 1:18 AM, Spet <email@example.com> wrote:
>> On May 21, 2015, at 1:03 AM, Spet <firstname.lastname@example.org> wrote:
>>> When i execute from dos console:
>> Why aren’t you using Cygwin Terminal instead?
> This is my first time.
> However I have to use it in windows console.
Again, *why*? If you can compile these programs in the Cygwin Terminal, you can run them there, too.
>> You’re trying to send *Cygwin’s* /etc/fstab to another box?
> *Cygwin’s* ???
> another box???
The asterisks (*) are a form of emphasis, created in the days before you could send italics and bold text formatting over email.
“Box” is a slang term for computer.
>>> generate.exe -b 25 -r 48000 -o "k:\TEMP\a.txt" c:\cygwin\etc\fstab
>> Are you sure you built it with the Cygwin C compiler, and not something else, like the MinGW or Visual Studio compilers? That’s the only explanation I can think of for why the POSIX path (/etc/fstab) would fail, but a DOS path would succeed.
> I've only done "makefile" in terminal.
That explains nothing. You can build programs with “make” using any compiler. It is not Cygwin-specific.
> But the transmission of the file fails because I get a bit sequence completely different from the original.
I can’t help you there. You’d need to examine the contents of the wave files and compare that to the known behavior of the algorithm.
A waveform editor like Audacity may help, but that’s way off topic here.
Brian is right: this set of programs is far from the best way to achieve your purpose.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin