View Single Post
Old 11-23-2016, 09:20 AM   #21
Doitsu
Grand Sorcerer
Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.
 
Doitsu's Avatar
 
Posts: 5,732
Karma: 24031401
Join Date: Dec 2010
Device: Kindle PW2
Quote:
Originally Posted by JustinThought View Post
So I implemented the changes you suggested, ran FlightCrew against my sample file, as well as a different file which, as far as I know, has no problems, on the problematic machine, and here's what came back on both files:

Status: failed

Running FlightCrew ... please wait
res_out: b'' res_err: b'' retcode: 3221225781

I hope that means something to you.
Unfortunately, I don't know what that specific return code means, but it looks like Sigil and/or Python can't run the FlightCrew binary in the background.

Try to temporarily disable any antivirus/malware apps with real-time scanning features before running FlightCrew. If FlightCrew works, you might have accidentally blacklisted the FlightCrew binary (flightcrew-plugin.exe).

Hopefully, KevinH, who wrote the FlightCrew plugin will know more about this return code.
Doitsu is offline   Reply With Quote