[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss-gnuradio] Re: Finally compiled USRP2 code works finewithUDPimag

From: Patrick Strasser
Subject: [Discuss-gnuradio] Re: Finally compiled USRP2 code works finewithUDPimage ...but not with compiled Raw Ethernet Image
Date: Tue, 18 Jan 2011 19:11:17 +0100
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv: Gecko/20101207 Lightning/1.0b3pre Mnenhy/0.8.3 Thunderbird/3.1.7

schrieb Gabriel Morel am 2011-01-17 23:39:
> Do you know how can we share some MS Office files.  

That's not so good. First, MS Office files may be practical for you, but
most people in GNU land (and GNU Radio is really GNU) do not have MS
Office or prefer free software alternatives.
Second, MS Office records a lot more information in the document than it
shows when you print it. For privacy reasons, do not share your
documents in this formats in public.

If you need to do it in this form, convert to a more common and privacy
friendly format, like PDF.

> It's easier to
> understand if we can see some commented screenshot in the same document?

Is it really need to take screenshots?

If you have pictures, use a picture format. Add marks for things you
want to show, send the picture with the comments explaining the picture.
Do not forget the comments, a picture alone says nothing.

If you did something on the console, you can copy all input and output
and send it by mail. No need to convert that to any other format.

Tell _exactly_ what you did. If you do not know any more exactly what
you did, try to produce your problem again, this time take notes.

I you used some command on command line ("DOS box"), tell us the exact
command with all parameter, exactly as you entered it. Add the output.
If the output is too long, remove obvious irrelevant parts. You can
replace the removed parts by [...], this makes clear that things where

If your detailed data is too much for the list (>100 lines or so), put
it at some exchange service. To keep your request understandable in the
future, choose a service which keeps this information for long time.
Then we can still read the thread in 3 years or more.
One suggestion:
Other ideas anyone?

Take a look at http://gnuradio.org/redmine/wiki/gnuradio/ReportingErrors


Engineers motto: cheap, good, fast: choose any two
Patrick Strasser <patrick dot strasser at student dot tugraz dot at>
Student of Telemati_cs_, Techn. University Graz, Austria

reply via email to

[Prev in Thread] Current Thread [Next in Thread]