public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Spet <spora@email.it>
To: cygwin@cygwin.com
Subject: Re: file-transfer-over-soundcard
Date: Fri, 22 May 2015 07:52:00 -0000	[thread overview]
Message-ID: <mjml8i$ckt$1@ger.gmane.org> (raw)
In-Reply-To: <EA5E51E0-2160-4830-A9D2-B52804CAD0CE@etr-usa.com>

-------- Original Message --------
> On May 21, 2015, at 1:03 AM, Spet <spora@email.it> 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.

>
> The Cygwin Terminal has a huge number of features missing from the Windows console, some of which allow it to work better with Cygwin programs.  (UTF-8 support, for example.)
>
> Meanwhile, the DOS console offers zero advantage over the Cygwin Terminal when it comes to running Cygwin executables.
Ok
>
>> ./generate.exe -b 25 -r 48000 -o out.data /etc/fstab
>
> You’re trying to send *Cygwin’s* /etc/fstab to another box?
*Cygwin’s* ???
another box???

> Why?  Typically the contents of that file are so trivial that it’s faster to just transcribe any changes in it when setting up a new box.
>
> Does "cat /etc/fstab" show something from the Cygwin Terminal?
Yes, text file
>
> Anyway, it works here.  I get a 25 MiB sound output file for a 531 byte /etc/fstab.
Now here, I understood better how it works.
>
>> 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.
>
> I have to ask: Why do you even want this software?
Just a curiosity to transmit files via audio and compile a C source 
Linux in Windows.

Finally, the compilation work.  The sound file is recorded and the audio 
capture works.
But the transmission of the file fails because I get a bit sequence 
completely different from the original.

Ty :)


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2015-05-22  7:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20 19:50 file-transfer-over-soundcard Spet
2015-05-20 20:11 ` file-transfer-over-soundcard Warren Young
2015-05-20 22:14   ` file-transfer-over-soundcard Spet
2015-05-20 22:25     ` file-transfer-over-soundcard Ken Brown
2015-05-20 22:38       ` file-transfer-over-soundcard Warren Young
2015-05-21  7:05   ` file-transfer-over-soundcard Spet
2015-05-21 19:22     ` file-transfer-over-soundcard Warren Young
2015-05-22  7:52       ` Spet [this message]
2015-05-22 13:50         ` file-transfer-over-soundcard Brian Inglis
2015-05-27 19:31         ` file-transfer-over-soundcard Warren Young

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='mjml8i$ckt$1@ger.gmane.org' \
    --to=spora@email.it \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).