When I use GRC 3792 , 'C:\\Work\\GRC_Work\\goodbin' works and
'C:\\Work\\GRC_Work\\badbin' fail
But after I install GRC 37111, both works well
------------Original Message------------
Subject : Re: [Discuss-gnuradio] FW: Re: File sink permission error on
Windows
Date : 2017-08-09 18:03:00
From : Marcus Müller <mueller@kitedu>
To : 김태영 <duck@radarnspacekr>
Cc :
How?
On 08/09/2017 04:31 AM, 김태영 wrote:
Thanks
Anyway I solve this issue with GRC 37111
Regards
Kim taeyeong
------------Original Message------------
Subject : Re: Re: [Discuss-gnuradio] FW: Re: File sink permission error on
Windows
Date : 2017-08-09 00:17:28
From : Geof Nieboer <gnieboer@corpcommnet>
To : 김태영 <duck@radarnspacekr>
Cc : Geof Nieboer <gnieboer@corpcommnet>,
"Discuss-gnuradio@gnuorg" <discuss-gnuradio@gnuorg>
Kim,
Ok, I'm feeling somewhat confident that this is a unicode or slash issue
The character you said is your path separator appears in my email client as
a W with a horizontal line through it, but when I cut/pasted that character,
it became a back slash Interesting
But I think that fact it ends up as a back slash is the more important part,
So try using forward slashes instead of back slashes as a workaround
It's possible the file path parser is treating the back slash as a
character escape in Windows python, which might indicate why \\badbin
doesn't work but \\goodbin does, since \\b is a backspace escape
character
I will take a closer look later on, but try that to keep moving forward
Geof
On Tue, Aug 8, 2017 at 2:35 AM, 김태영 <duck@radarnspacekr> wrote:
Geof
'goodbin' exist and no 'badbin'
The separator is \\ I confirm that by selecting some file on file sink block
file menu
How can I check if any unicode?
Regards
Kim taeyeong
------------Original Message------------
Subject : Re: [Discuss-gnuradio] FW: Re: File sink permission error on
Windows
Date : 2017-08-08 12:30:52
From : Geof Nieboer <gnieboer@corpcommnet>
To : 김태영 <duck@radarnspacekr>
Cc : "Discuss-gnuradio@gnuorg" <discuss-gnuradio@gnuorg>
Kim,
That's a very odd error Can you confirm that neither goodbin or badbin
existed in that folder? Are there any unicode characters in the filename?
Your path separators were copied as \\ Can you confirm which direction
slashes you were using?
Geof
On Mon, Aug 7, 2017 at 11:16 PM, 김태영 <duck@radarnspacekr> wrote:
Thanks
But I still have problem Some file name works good, but not the another
For ex 'C:\\Work\\GRC_Work\\goodbin' whithout error,
But 'C:\\Work\\GRC_Work\\badbin' fail
It looks like some kind of bug
Regards
Kim taeyeong
------------Original Message------------
Subject : Re: [Discuss-gnuradio] File sink permission error on Windows
Date : 2017-08-07 17:17:57
From : Marcus Müller <mueller@kitedu>
To : <discuss-gnuradio@gnuorg>
Cc :
Hi Kim,
can you try to select an absolute file name rather then just
"newbin", in a directory that you definitely can generate new
files in?
To me, this looks like the reason really is that you're not allowed to
create or write to newbin
Best regards,
Marcus
On 08/07/2017 09:31 AM, 김태영 wrote:
Hi all
When I test file sink block on Windows 10 platform, I got permission error
GRC version is 3792
This flowgraph works well on Ubuntu environment
How can I overcome this issue
One more issue is the deference before "Stream to tagged stream"
and after
I want to know what this block meaning
Regards
Kim taeyeong
==== Error message ====
Executing: C:\\Program Files\\GNURadio-37\\gr-python27\\pythonexe -u
C:\\Work\\GRC_Work\\file_sinkpy
Using Volk machine: avx2
newbin: Permission denied
Traceback (most recent call last):
File "C:\\Work\\GRC_Work\\file_sinkpy", line 82, in
<module>
main()
File "C:\\Work\\GRC_Work\\file_sinkpy", line 76, in main
tb = top_block_cls()
File "C:\\Work\\GRC_Work\\file_sinkpy", line 37, in __init__
selfblocks_file_sink_0_1 = blocksfile_sink(grsizeof_int*1,
"newbin", False)
File "C:\\Program
Files\\GNURadio-37\\lib\\site-packages\\gnuradio\\blocks\\blocks_swig0py&qu
ot;,
line 1016, in make
return _blocks_swig0file_sink_make(itemsize, filename, append)
RuntimeError: can't open file
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnuorg
https://listsgnuorg/mailman/listinfo/discuss-gnuradio
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnuorg
https://listsgnuorg/mailman/listinfo/discuss-gnuradio
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnuorg
https://listsgnuorg/mailman/listinfo/discuss-gnuradio
_______________________________________________
Discuss-gnuradio mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
