Quote:
|
Originally Posted by Doitsu;34320 78
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.
|
What, you don't have all 3,221,225,781 error codes memorized? Gee!
That machine has no internet privileges, so it also has no antivirus installed. You know, we
could just be dealing with a factor of age. I built that machine about six or seven years ago, so it's getting a little long in the tooth. I don't remember the details of the CPU inside, but the motherboard is ASUS. Whereas "this" machine (my laptop) is an underpowered Lenovo, but it's fairly new. There could have been some arcane changes in the CPUs that just makes running FlightCrew impossible.
But I'll keep on messing with it, and if I ever discover the solution, I promise that I'll let you know what it is.
--add on: while I was contemplating this response, I decided to check the desktop to be sure the two machines were running the same version of Windows; indeed, both have Win 7 Ultimate, now with SP-1. So maybe there was a problem with memory? Nope. The desktop has 4 gb, this machine only has two.
But I'll keep going through this mental checklist. There's
something on that machine that sets the "FlightCrew? We don'
need no steenkin' FlightCrew!" flag to TRUE.