Sigil not fully launching - Embedded Python error

[DiapDealer]

Originally Posted by BookWalker

When I perform 3. I get what's on the attached image.

Yowza.

On second thought... even if 'cd' couldn't be found, you'd never get a graphical error if you were entering it in a command prompt/window. Perhaps you typed it in a search box?

[BookWalker]

Originally Posted by DiapDealer

On Windows 7, one should be able to hold the Shift key down, then right-click with the mouse on a folder to bring up a context menu. That should make the "Open Command Window Here" item available in the resulting menu.

Just a quick tip/shortcut to be able to open a command prompt in the correct directory without needing to cd there.

Ok, now your tip opened what I believe should have. The screenshot is the result of inputting things as Doitsu directed.

[DiapDealer]

That's better. Thanks! Still not sure what the problem might be, but it's a base starting point anyway.

Can you possibly post a screenshot of the contents of the "C:\Program Files\Sigil" folder?

[BookWalker]

Originally Posted by DiapDealer

That's better. Thanks! Still not sure what the problem might be, but it's a base starting point anyway.

Can you possibly post a screenshot of the contents of the "C:\Program Files\Sigil" folder?

Sure! Anything you ask for, if I understand what you want, I'm more than happy to provide. I'm very appreciative of all the time that has been spent trying to figure this out.

Two screenshots attached.

[KevinH]

Sorry if this is a stupid question, could this be a 64 bit vs 32 bit mismatch issue with python?

On a working Windows build where would the unicodedata.so or unicodedata.dll be found?

[KevinH]

Your screenshot shows that your original error message was in fact correct. For some strange reason the DLL that is needed for the python3.8 unicodedata module can not be found.

One thing you could try is to download and install Python 3.8.3 from www.python.org and install it and then open a command prompt to fire up that just added version of Python 3.8.3 (not the one in the Sigil folder) and try the:

import unicodedata

test again and see if you get the same error message.

[DiapDealer]

Originally Posted by BookWalker

Sure! Anything you ask for, if I understand what you want, I'm more than happy to provide.

That's what I wanted, thanks.

Originally Posted by KevinH

Sorry if this is a stupid question, could this be a 64 bit vs 32 bit mismatch issue with python?

Doesn't seem to be. Sigil looks to be the 64-bit version (based on where it was installed by default) and the bundled python looks to be 64-bit as well

Originally Posted by KevinH

On a working Windows build where would the unicodedata.so or unicodedata.dll be found?

It should be in the Sigil/DLLs directory. It's definitely in the 1.4.3 installer and it functions as it should on my Win7 test machines.

@BookWalker : in the DLLs folder (found in the Program FIles/Sigil folder you posted the screenshot of), can you verify that a file named unicodedata.pyd is, in fact, there?

[BookWalker]

Originally Posted by DiapDealer

That's what I wanted, thanks.


Doesn't seem to be. Sigil looks to be the 64-bit version (based on where it was installed by default) and the bundled python looks to be 64-bit as well


It should be in the Sigil/DLLs directory. It's definitely in the 1.4.3 installer and it functions as it should on my Win7 test machines.

@BookWalker : in the DLLs folder (found in the Program FIles/Sigil folder you posted the screenshot of), can you verify that a file named unicodedata.pyd is, in fact, there?

Yes, it's there.

[DiapDealer]

OK. I may be onto something (at least I hope so!). In order to successfully install Python 3.8 on Windows 7. You need have SP1 for Windows 7 installed AND you need to have "Update for Windows 7 (KB2533623)" installed after that.

Since the Sigil installer checks for SP1 before installing, I'm beginning to suspect you don't have the KB2533623 update installed as well. Since we're not technically installing Python with the Sigil installer, it wouldn't know if that update was installed or not.

The lack of that Python 3.8 pre-requisite is what I'm hoping is causing the errors with Sigil's bundled Python on your system.

Unfortunately that standalone KB2533623 update isn't available from Microsoft's update servers for WIndows 7 any more, but it has been incorporated into one their "Monthly Security Rollup" updates. Namely the KB4457144 update. Windows update should be able to install that. If not you can download the standalone package from the Microsoft update catalog: https://www.catalog.update.microsoft...px?q=KB4457144. Make sure you download the one for 64-bit windows 7.

Might be a long shot, but it's all I've got at this time.

[BetterRed]

Added : Only if ↑ ↑ ↑ ↑ ↑ ↑ doesn't solve the problem.

@experts, it's odd that the Windows pop-up message posted in post #7 is blank.

Originally Posted by BookWalker

I see Python 3.0.1 installed. Should I uninstall it and download the 3.8.0 version and install?

@BookWalker - I assume you saw it in, and removed it via, Control Panel->Programs and Features. Do you know where that Python installation came from?

Suggest you restart Windows in Safe Mode and then try starting Sigil. If it works then it will probably be something in start up or a 3rd party shell extension.

BR

[BookWalker]

Originally Posted by DiapDealer

OK. I may be onto something (at least I hope so!). In order to successfully install Python 3.8 on Windows 7. You need have SP1 for Windows 7 installed AND you need to have "Update for Windows 7 (KB2533623)" installed after that.

Since the Sigil installer checks for SP1 before installing, I'm beginning to suspect you don't have the KB2533623 update installed as well. Since we're not technically installing Python with the Sigil installer, it wouldn't know if that update was installed or not.

The lack of that Python 3.8 pre-requisite is what I'm hoping is causing the errors with Sigil's bundled Python on your system.

Unfortunately that standalone KB2533623 update isn't available from Microsoft's update servers for WIndows 7 any more, but it has been incorporated into one their "Monthly Security Rollup" updates. Namely the KB4457144 update. Windows update should be able to install that. If not you can download the standalone package from the Microsoft update catalog: https://www.catalog.update.microsoft...px?q=KB4457144. Make sure you download the one for 64-bit windows 7.

Might be a long shot, but it's all I've got at this time.

Omg! I so hate Windblows! There's always something strange going on with it.... anyway, after ranting that you are not going to believe what I've run into. Went to the link, selected the correct download, a window pops up, and it won't download anything.

[BookWalker]

Originally Posted by BetterRed

@experts, it's odd that the Windows pop-up message posted in post #7 is blank.



@BookWalker - I assume you saw it in, and removed it via, Control Panel->Programs and Features. Do you know where that Python installation came from?

Suggest you restart Windows in Safe Mode and then try starting Sigil. If it works then it will probably be something in start up or a 3rd party shell extension.

BR

It was downloaded from python.org and removed as you stated above.

[BetterRed]

I was wondering why it was installed. If you didn't install it, then someone or something else must have installed it.

[BookWalker]

Originally Posted by BetterRed

I was wondering why it was installed. If you didn't install it, then someone or something else must have installed it.

I did install it based upon something I read in another thread a couple of days ago. Then I deleted it after posting this thread and getting actual input on my problem.

[DiapDealer]

Originally Posted by BookWalker

Omg! I so hate Windblows! There's always something strange going on with it.... anyway, after ranting that you are not going to believe what I've run into. Went to the link, selected the correct download, a window pops up, and it won't download anything.

That window that pops up offers me two links on it. One is to an exe that I have no idea about, and the other is the KB4457144 .msu update package which downloads ok for me when I click on it.