Re: [osgeo4w-dev] Problems re-installing on WinXP 64
Lucena, Ivan
ivan.lucena at pmldnet.com
Wed Jan 14 14:24:28 EST 2009
Hi Matt, Frank,
So in ideal situation, if I delete my one and only "E:/OSGeo4W" and run the installer again I should be able to select
for example
- \Desktop\OpenEV
The installer should take care of the dependencies. I can see that GDAL command line tools is automatically selected
in that case. But the package:
- \Libs\OGDI
Is not automatically select and when I run gdalinfo for the first time on the OSGeo shell it crash because of
ogdi_32b1.dll not found. I can see on the process monitor the loading sequence:
E:\OSGeo4w\bin\gdalinfo.exe SUCCESS
E:\OSGeo4W\bin\gdal15.dll SUCCESS
E:\OSGeo4W\bin\ogdi_32b1 NAME NOT FOUND
That means to me two things:
- GDAL15 was build with OGDI dependence.
- The installer is failing to auto select the OGDI package.
I run again and install OGDI then the problem is zlib_osgeo.dll
By the way, I follow you advise and check the environment variables. Actually that is what I did with the PATH:
set PATH=E:\OSGeo4w\bin
So that there is no way to get the wrong dll loaded. I guess.
Then I added zlib package and the problem now is proj_fw.dll.
I don't know what is the package that contains pro_fw.dll in fact I can't even find it on another win32 computer
that has OSGeo4W working fine with OpenEV, GDAL15 and GDAL16.
That is it, I am done. There is nothing else that I can do. I need to continue my work with the GDAL Java API so I
will build it from GDAL trunk and forget about OSGeo4w on that machine for a while.
Thank you both very much,
Ivan
> -------Original Message-------
> From: Matt Wilkie <matt.wilkie at gov.yk.ca>
> Subject: Re: [osgeo4w-dev] Problems re-installing on WinXP 64
> Sent: Jan 14 '09 17:50
>
> Hi Ivan,
>
> I use osgeo4w on win64 and have had different versions of gdal installed
> at the same time. In my experience so far as long as I start from the
> osgeo4w shell everything works, though I've not tried any java. Perhaps
> in your uninstall/reinstall the osgeo4w command shell link was not
> updated to the new location?
>
> I do have to be careful that there are no gdal/python settings in the
> permanent environment pointing to the wrong version. Run "set" with no
> parameters from the shell. Settings to watch for cross contamination
> include:
>
> FWTOOLS_ROOT
> GDAL_DATA
> GEOTIFF_CSV
> OSGEO4W_ROOT
> PATH
> PROJ_LIB
> PYTHONPATH
> PYTHON_INCLUDE
> PYTHON_LIB
>
>
>
> matt wilkie
> --------------------------------------------
> Geographic Information,
> Information Management and Technology,
> Yukon Department of Environment
> 10 Burns Road * Whitehorse, Yukon * Y1A 4Y9
> 867-667-8133 Tel * 867-393-7003 Fax
> http://environmentyukon.gov.yk.ca/geomatics/
> --------------------------------------------
>
>
> Lucena, Ivan wrote:
> > Hi there,
> >
> > I stalled OSGeo4W using "advanced install" so that I could select
> > driver E: as the OSGeo4W root and select just some packages like:
> >
> > GDAL 1.5 Proj.4 OpenEV GDAL-Java
> >
> > I was able to use GDAL command line tools and OpenEV from that
> > installation for a while.
> >
> > Later I setup a Java Web App from scratch in order to use the GDAL
> > Java wrapper. That worked OK until I've got this error:
> >
> > --- GDALOpen failed - This is a BigTIFF file. BigTIFF is not
> > supported by this version of GDAL and libtiff. ---
> >
> > Generated by this piece of code on my JSP class:
> >
> > {{{
> >
> > dataset = gdal.Open( fileName, gdalconstConstants.GA_ReadOnly );
> >
> > if (dataset == null) { result = "GDALOpen failed - " +
> > gdal.GetLastErrorMsg(); }
> >
> > }}}}
> >
> > I checked if the GTIFF driver was supporting BIGTiff by running
> > gdalinfo and it looks like it was.
> >
> > I have several other GDAL environment on that machine so I decided to
> > clean up a little bit and start from scratch the OSGeo4W
> > installation.
> >
> > Now I can't get it to work anymore. Nothing. gdal tools, OpenEV and I
> > also tried to install GRASS and QGIS each one of then complain about
> > one dll or another.
> >
> > OpenEV:
> >
> > --------------------------- python.exe - Unable To Locate Component
> > --------------------------- This application has failed to start
> > because ogdi_32b1.dll was not found. Re-installing the application
> > may fix this problem. --------------------------- OK
> > ---------------------------
> >
> > Quantum GIS
> >
> > --------------------------- qgis.exe - Unable To Locate Component
> > --------------------------- This application has failed to start
> > because QtCore4.dll was not found. Re-installing the application may
> > fix this problem. --------------------------- OK
> > ---------------------------
> >
> > GRASS:
> >
> > --------------------------- g.dirseps.exe - Unable To Locate
> > Component --------------------------- This application has failed to
> > start because zlib_osgeo.dll was not found. Re-installing the
> > application may fix this problem. --------------------------- OK
> > ---------------------------
> >
> > gdalinfo:
> >
> > --------------------------- gdalinfo.exe - Unable To Locate Component
> > --------------------------- This application has failed to start
> > because ogdi_32b1.dll was not found. Re-installing the application
> > may fix this problem. --------------------------- OK
> > ---------------------------
> >
> > I tried to run the OSGeo4W again installing each one of the missing
> > dll to the resolve those issues but it doesn't work. There is always
> > something wrong or missing. I waste the last two days doing that.
> >
> > Does anybody has ever got in to that mess before? Any hint on how to
> > get out of it? Was OSGeo4W installer tested on Win64 before? Is there
> > a better way to uninstall and start from scratch then deleting the
> > folder?
> >
> > Thank you so very much for any attempt to help.
> >
> > Ivan
> >
> >
> >
> >
> > _______________________________________________ osgeo4w-dev mailing
> > list osgeo4w-dev at lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/osgeo4w-dev
> >
>
More information about the osgeo4w-dev
mailing list