MobileRead Forums - View Single Post - Sigil won't start on new Windows 10 laptop

Marg1780 · 05-25-2021, 12:14 AM

Many thanks, all, for the feedback and information.

DiapDealer: Yes, it does seem strange that I'm getting no rebuild on the .ini file, since that seems to be such a common fix. I get the one during install, and nothing further.

I run Sigil and Calibre separately. Occasionally when I want to make a change to something within Calibre, I just use their editor.

I've excluded Sigil from Norton scans to see if that makes a difference. I've had problems with 360 deleting old exe files, but never this set of behaviors. I do know that it isn't actually deleting Sigil.exe but it may be messing with it otherwise.

Speaking of behaviors, I've got a new oddity to add to my list. Last night, I did another reinstall (overtop of what was already in), based on another discussion I found online. I put the 32bit version of 0.9.10 in, tried to open a file, and it worked just fine. So, I installed the 64bit to see what would happen - and again the ePub opened just fine. So for the rest of the evening, I used Sigil as normal... Didn't understand why, but was happy to have it back.

This morning, it was back to not starting. In between, I'd done nothing at all on the user level aside from leaving a long backup running. The laptop wasn't even rebooted, though it went to sleep after 5 hours. So, that symptom might match with an issue related somehow to a Norton idle-time scan. I did the reinstall again, and again it got the package back into functional shape. Right at the moment, it's working fine.

When I rooted around in the Apps event log, sure enough, I'm getting some error entries from Sigil, all of which seem to relate to a DLL called _ssl.pyd. Black box for me; I really am 100% Python illiterate, so I've no guesses on whether or not that's a useful revelation. I'm not sure there's a 1-1 relationship between those entries and it not working at all; the times don't seem to match up with when I was seeing it dead, but I could be wrong on that since I wasn't making immediate checks.

Turtle91: Thanks for all the info. I normally work with Book browser, the main window and a very-very skinny version of the ToC window. I've certainly used the code/preview split in html editors and so on, so I understand the advantages. Still plan to checkout the new version eventually, but I've been saying that for a while...

05-25-2021, 12:14 AM	#9
Marg1780 Enthusiast Posts: 29 Karma: 10 Join Date: Nov 2018 Location: Ontario, Canada Device: Kobo Clara	Many thanks, all, for the feedback and information. DiapDealer: Yes, it does seem strange that I'm getting no rebuild on the .ini file, since that seems to be such a common fix. I get the one during install, and nothing further. I run Sigil and Calibre separately. Occasionally when I want to make a change to something within Calibre, I just use their editor. I've excluded Sigil from Norton scans to see if that makes a difference. I've had problems with 360 deleting old exe files, but never this set of behaviors. I do know that it isn't actually deleting Sigil.exe but it may be messing with it otherwise. Speaking of behaviors, I've got a new oddity to add to my list. Last night, I did another reinstall (overtop of what was already in), based on another discussion I found online. I put the 32bit version of 0.9.10 in, tried to open a file, and it worked just fine. So, I installed the 64bit to see what would happen - and again the ePub opened just fine. So for the rest of the evening, I used Sigil as normal... Didn't understand why, but was happy to have it back. This morning, it was back to not starting. In between, I'd done nothing at all on the user level aside from leaving a long backup running. The laptop wasn't even rebooted, though it went to sleep after 5 hours. So, that symptom might match with an issue related somehow to a Norton idle-time scan. I did the reinstall again, and again it got the package back into functional shape. Right at the moment, it's working fine. When I rooted around in the Apps event log, sure enough, I'm getting some error entries from Sigil, all of which seem to relate to a DLL called _ssl.pyd. Black box for me; I really am 100% Python illiterate, so I've no guesses on whether or not that's a useful revelation. I'm not sure there's a 1-1 relationship between those entries and it not working at all; the times don't seem to match up with when I was seeing it dead, but I could be wrong on that since I wasn't making immediate checks. Turtle91: Thanks for all the info. I normally work with Book browser, the main window and a very-very skinny version of the ToC window. I've certainly used the code/preview split in html editors and so on, so I understand the advantages. Still plan to checkout the new version eventually, but I've been saying that for a while...