Try running your command again and use 2>&1 | tee -a errorzip.log where errorzip.log is the file to check then send with wc -lwc errorzip.log if the three numbers you get are greater than 0 then the file has contents that may be useful.
Jude <jdashiel at panix dot com> "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) . On Sat, 11 Mar 2023, K0LNY_Glenn wrote: > Well I updated the zip file from github, and unzipped it, and did the chmod > +x thing, and got three different errors, > One said something about gnu not found > and another said elf not found, and the third said: > syntax error, unterminated string. > I tried to direct it to a txt file to send here, but trying the command and > a greater sign or a pipe only gives me a blank txt file. > > Glenn > and > ----- Original Message ----- > From: "K0LNY_Glenn" <[email protected]> > To: <[email protected]> > Sent: Saturday, March 11, 2023 12:13 PM > Subject: executable trouble > > > Hi All, > I am still trying to get nanovna-saver to work on Debian bullseye. > I don't know if this computer is an i386, and maybe this program is 64 bit, > but it has both for windows, but only one file for Linux. > The instructions say to: > list of 1 items > . If using binaries on Mac or Linux you have to chmod +x nanovna-saver after > unzipping as executable flags get lost with zip. > list end > So I did that, then I ran: > sudo updatedb > Then I ran sudo /home/lenny/./nanovna-saver > and I get the error: > -bash nanovna-saver cannot execute binary file exec format error > > Does anyone have an idea about the error? > Thanks. > >
