[filebravo]

Yes, I have different version of Python already installed on my machines.

[filebravo]

This is the line I get in the log file

# Python version 2.7.4 (default, Apr 6 2013, 19:54:46) [MSC v.1500 32 bit (Intel)] for win32

Thank you so much for your effort supporting me.

[filebravo]

Ok! Glade starts! And it is very amazing…

The problem is that I was using the python27.dll provided with glade installation.
I just copied the file FROM C:WindowsSystem32python27.dll TO <pathToGlade>.

Glade starts! I will let you notice in case of issues.

P.S.: I have a 32bit Windows7

[filebravo]

1) No popup dialogs

2) When Glade starts, the first thing it does after setting up the logfile is to initialise Python using Py_Initialize. If Python fails to initialise, it will exit with no warning. Unable to understand this step.

3) I can't see the app at all.

4) Even from cmd.exe I can't see any log/output err

5) Yes, dependencywalker shows me that the python27.dll file is pointing to the one in the installation directory

6) I unzipped the package and double-clicked on glade. No results. At the second try, I installed the vcredist_x86.exe and double-clicked on glade. Non results again. At the third chance, I read the README file and setup the environment variables. No success again.

[/quote]

[filebravo]

I am sorry but it's not working yet.
Python27.dll is the correct one.

Sorry for let you lose time.

I am attaching the dwi file from dependencywalker if it can help.

I will try with a Linux distro.

Thank you.

[filebravo]

They are both 32bit systems.

I am interested in solving the issue on Windows7 seen that it is newer PC.

[filebravo]

Trust me, both my Windows are highly updated.
I've done the same searches on Google.
If I am posting it is because I am not able to solve the problem by myself.

Is there any software that is "strongly recommended" to install before trying launching Glade?

(I can't stand the empty log file!)

Thank you so much…

[filebravo]

Hi All

I am totally unable to run Glade on both Windows7 and WindowsXP.

Inspecting the *.exe with DependencyWalker I found that are a lot of missing DLLs.
I guess it is caused by missing dependencies.
Obviously the log file is empty.

Please, give me some hints.

Below the list of missing DLLs:
API-MS-WIN-CORE-COM-L1-1-0.DLL
API-MS-WIN-CORE-DEBUG-L1-1-1.DLL
API-MS-WIN-CORE-DELAYLOAD-L1-1-1.DLL
API-MS-WIN-CORE-ERRORHANDLING-L1-1-1.DLL
API-MS-WIN-CORE-HEAP-L1-2-0.DLL
API-MS-WIN-CORE-INTERLOCKED-L1-2-0.DLL
API-MS-WIN-CORE-LIBRARYLOADER-L1-1-1.DLL
API-MS-WIN-CORE-MEMORY-L1-1-1.DLL
API-MS-WIN-CORE-PROCESSTHREADS-L1-1-1.DLL
API-MS-WIN-CORE-REGISTRY-L1-1-0.DLL
API-MS-WIN-CORE-RTLSUPPORT-L1-2-0.DLL
API-MS-WIN-CORE-SYNCH-L1-2-0.DLL
API-MS-WIN-CORE-SYSINFO-L1-2-0.DLL
API-MS-WIN-CORE-THREADPOOL-L1-2-0.DLL
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-EVENTING-PROVIDER-L1-1-0.DLL
API-MS-WIN-SHCORE-SCALING-L1-1-0.DLL

[Author]

Posts