Zim won't start on Win2K - no GUI, nothing...

The error indicates python has a problem either finding or loading the Gtk
DLLs. So you might want to check the PATH. If it finds the DLL fine but has
an issue loading it I'm afraid I can't help you - out of my competency. Not
sure if the installer was ever tested in 2K, so might be some compatibility
issue.

If al fails you might try running from source as well. Just install the
python + Gtk bundle from pygtk.org and grab the source package for zim. From
a DOS prompt set the path pointing to the python + gtk install and run
"python .\zim.py" (no need to install zim, just run directly from the
unzipped sources).

Thanks so much for the amazingly prompt (and useful) reply!!!

I was guessing from "File "gtk\_gtk.pyo", line 10, in __load" that you were looking for gtk files in a dir named "gtk" that was in a dir in the path... I see that was probably silly.... I'll find the GTK dlls and add the containing dir to the path and let you know how it goes.

Zim is a great tool, btw - I'm really looking forward to getting more familiar with it if I can get all my boxes synced up via Ubuntu One.... it will solve a *lot* of problems for me.

Heartfelt Thanks....

I've tried adding gtk's bin dir to path, and no change.

Just to confirm - can you tell which DLL is not being loaded from the error message?

I ask because the GTK directory has several subdirs with DLLs in them. Is "bin" the correct one to add to the path?

Lastly - the dir structure of the most recent GTK version is completely different from the older version I had previously installed. The older version had dozens more files... I've tried both in the path, with no change in behavior.

I know I will need to go to GTK's support shortly, but thought I'd ask...

Thanks in advance,

Mike

Another quick thought - would it be necessary for GTK to be in the path at install time - or only at run time ???

On Wed, Apr 6, 2011 at 10:50 PM, Mike Morris <
<email address hidden>> wrote:

> Just to confirm - can you tell which DLL is not being loaded from the
> error message?
>
> I ask because the GTK directory has several subdirs with DLLs in them.
> Is "bin" the correct one to add to the path?
>

Not sure, I believe only the ones in "bin" need to be in the path and those
will link the rest when needed.

-- Jaap

On Wed, Apr 6, 2011 at 10:52 PM, Mike Morris <
<email address hidden>> wrote:

> Another quick thought - would it be necessary for GTK to be in the path
> at install time - or only at run time ???
>

Zim only uses gtk on run time. Zim doesn't have any real install code other
than copying some files.

-- Jaap

I've just tried running from source, and still no luck, I'm afraid.

I install Python 2.7, then pygtk "all in one" as suggested. Python runs, and doing a "modules" command lists "gtk" as an available module.

Running "python .\setup.py --requires" generates this output - the readme does not provide enough info to tell if this is correct or not:
--------------------------------------------------------------------------
C:\Software\zim>python .\setup.py --requires
gobject
gtk
xdg

C:\Software\zim>
--------------------------------------------------------------------------

I extracted the zim source, in cmd window went to zim dir, added my python dir to path, and tried "python .\zim.py", but still get a could not load DLL error, although it is slightly different, as shown below.

Are there any confirmed instances of Zim on Win2K, or am I in uncharted waters???

Thanks in advance,

MikeM

DEBUG:
--------------------------------------------------------------------------
C:\Software\zim>python .\zim.py -D
INFO: This is zim 0.50
DEBUG: Python version is sys.version_info(major=2, minor=7, micro=1, releaseleve
l='final', serial=0)
DEBUG: Platform is nt
DEBUG: Zim revision is:
        branch: pyzim-trunk
        revision: 350 <email address hidden>
        date: 2011-02-14 22:38:51 +0100

DEBUG: Running from a source dir: C:\Software\zim
DEBUG: Set XDG_DATA_HOME to C:\Documents and Settings\mikem\.local\share
DEBUG: Set XDG_DATA_DIRS to [<Dir: C:\usr\share>, <Dir: C:\usr\local\share>]
DEBUG: Set XDG_CONFIG_HOME to C:\Documents and Settings\mikem\.config
DEBUG: Set XDG_CONFIG_DIRS to [<Dir: C:\etc\xdg>]
DEBUG: Set XDG_CACHE_HOME to C:\Documents and Settings\mikem\.cache
DEBUG: Running command: gui
Traceback (most recent call last):
  File ".\zim.py", line 56, in <module>
    zim.main(argv)
  File "C:\Software\zim\zim\__init__.py", line 280, in main import zim.gui
  File "C:\Software\zim\zim\gui\__init__.py", line 30, in <module> import gtk
  File "c:\os\python\lib\site-packages\gtk-2.0\gtk\__init__.py", line 40, in <module> from gtk import _gtk
ImportError: DLL load failed: The specified procedure could not be found.

C:\Software\zim>
--------------------------------------------------------------------------

Rats... looks like this is a gtk problem on Win2K SP4.

From "http://osdir.com/ml/gtk-app-devel-list/2009-12/msg00016.html":

> have to consider GLib 2.22 being unsupported on Windows 2000 then, and
> known not to work.

Also, in python help(), doing a simple "pygtk" correctly produces some module info and basic help; doing "gtk" produces

help> gtk
problem in gtk - <type 'exceptions.ImportError'>: DLL load failed: The specified
 procedure could not be found.

help>

which is doubtless the genesis of the similar zim error.

Its been a long while since I've run cygwin for anything --- having mostly gone to Linux directly. But, that will be my next attempt... any advice there?

On Thu, Apr 14, 2011 at 8:34 AM, Mike Morris <
<email address hidden>> wrote:

> Its been a long while since I've run cygwin for anything --- having
> mostly gone to Linux directly. But, that will be my next attempt... any
> advice there?
>

Haven't tried that myself and didn't hear from anybody going that way to
install. You might want to ask on the mailing list instead of here, there
are mode people reading the list.

-- Jaap

I have a simillar issue but somehow be able with one version to start it and with the other not

With Version 54 I am not able to launch the application. It seems as with version 53 I do not have such problems.

running "tim -D" shows the printout is exactly the same as mentioned in the description above.