guilherme
guycanella@gmail.com
>this is really strange!
>What is the build number of the Firefly binaries you are using?
>Kind regards,
>Alex Granovsky
>
>
>On Thu Nov 28 '13 1:56pm, guilherme wrote
>-----------------------------------------
>>Hi Alexander,
>>Sorry to answer your question just today! Well, I'm using the Firefly 8.0.0, but when I try to run Firefly in other folders it's doesn't work. Maybe it's related with the permissions of the folder but none of the folders that I tried to run Firefly had the permissions modified.
>>
>>
>>----------------------------------------------
>>>Hi,
>>>what is the Firefly version you are using?
>>>Firefly versions 7.1.G and below interpret relative paths as
>>>the paths relative to the folder where the Firefly binaries reside.
>>>Firefly version 8.0.0 and up interprets relative paths as relative
>>>to the Firefly's initial working directory.
>>>With Firefly versions 7.1.G and below you may encounter the problem
>>>you have described. The workaround is to use absolute paths.
>>>The better workaround is to upgrade to Firefly v. 8.0.0
>>>Kind regards,
>>>Alex Granovsky
>>>
>>>
>>>On Fri Nov 22 '13 7:44pm, guilherme wrote
>>>-----------------------------------------
>>>>Hi guys, thank you for the help! Finally I solved my problem!
>>>>After erase the "semaphores" I ran the firefly and got that error. Then I tried to move my input to the firefly's folder and the problem stopped. I just don't know why rs
>>>>But thank you Pedro and Alexander!
>>>>
>>>>
>>>>
>>>>
>>>>-----------------------------------------
>>>>>Yeah, everything is correct! I checked. I created another folder with a simple input e then I ran
>>>>>>firefly8 -i scan-opt.inp -o scan-opt.log
>>>>>and that error appear again.
>>>>>
>>>>>
>>>>>
>>>>>-------------------------------------------
>>>>>>>You must be sure that the output file you want to create does not exist, and that you have invoked the correct input file. the proper syntax is
>>>>>>firefly -i input_filename -o output_filename
>>>>>>Check the tutorial/getting started pages for other command line options.
>>>>>>Pedro S.