<br><br><div class="gmail_quote">2009/9/6 Martin Hvidberg <span dir="ltr"><<a href="mailto:Martin@hvidberg.net">Martin@hvidberg.net</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I got my GDAL from <a href="http://gdal.org" target="_blank">gdal.org</a> <<a href="http://gdal.org" target="_blank">http://gdal.org</a>> (gdalwin32exe160.zip)<div class="im"><br>
<br>
It works on my XP nootebook but not on our 'Window Server 2003'<br>
<br>
<br>
<br>
Hmmm... Just by looking into this package (<a href="http://download.osgeo.org/gdal/win32/1.6/gdalwin32exe160.zip" target="_blank">http://download.osgeo.org/gdal/win32/1.6/gdalwin32exe160.zip</a>) I don't see any dependencies to msvcr80.dll. Looks like most of the dlls have been build with MSVC2003 (msvcrt71) and geos have been build with MSVC2008 (msvcr90)<br>
<br>
Best regards,<br>
<br>
Tamas<br>
</div></blockquote>
<br>
I wouldn't know... But every time I run a Python script that has the line 'import gdal' or more exactly, the following block.<br>
<br>
------8<--------------<br>
try:<br>
from osgeo import gdal<br>
from osgeo.gdalconst import *<br>
gdal.TermProgress = gdal.TermProgress_nocb<br>
except ImportError:<br>
import gdal<br>
from gdalconst import *<br>
------8<--------------<br>
<br>
it generates a popup window that states:<br>
<br>
"Python.exe - Unable To Locate Component<br>
This application has failed to start because MSVCR80.dll was not found. Re-installing the application may fix this problem."<br>
<br>
The exact same python script, runs like a dream, from the same directory , when I execute it from the FWtools.<br>
<br>
This tells me that all the needed files are on the machine, but someting is not linked together or referenced correct from the ordinary command line.</blockquote><div><br><br>Martin,<br><br>The package you've mentioned above doesn't contain python bindings (<a href="http://download.osgeo.org/gdal/win32/1.6/gdalwin32exe160.zip" target="_blank">http://download.osgeo.org/gdal/win32/1.6/gdalwin32exe160.zip</a>) so I wonder how it would ever work in a particular machine. If you install FWTools and you run the application from the FWTools command prompt you pick up the related files from the FWTools installation not from the gdalwin32 package.<br>
I admit I'm a bit lost what's the issue here as you mention your FWTools package is working correctly. In any case, I would not recommend you to use this one of gdalwin32, since it looks pretty old (2008-12-30) and not well maintained.<br>
<br>Best regards,<br><br>Tamas<br><br></div></div><br>