corrupt .exe's on sf

danx0r

05-09-2008 07:45:29

not sure what's up with this, but I tried all 3 releases on my Vista machine, and the most recent on an old Win2K machine, and in all cases I could not run the self-extracting archive. In every case, I get messages like this:

Runtime Error (at 7:738):

Out Of Range


looks like a VB/missing DLL thing -- what installer did you guys use?

andy

05-09-2008 08:06:40

What version of python do you have installed??

And did you use the standard windows installer to install it - and what path is it in?

Thanks
Andy

danx0r

05-09-2008 19:07:31

What version of python do you have installed??

And did you use the standard windows installer to install it - and what path is it in?

Thanks
Andy


I don't have the machine in front of me, but I'm 95% sure it's standard Python 2.5, installed in c:\python25. It was installed using the installer from python.org. Please inform exactly what I need to install if it's different than this (and you should have a comment on the Wiki if there's a prereq for the installer)

Out of curiosity, why not have a standard distutils install (python setup.py)? It makes me a bit queasy to run an .exe, especially when it starts doing funky stuff. Sourceforge doesn't even have checksums, so my paranoid fantasy was that sourceforge got hacked and I'm installing deadly spambots.

Anyway, looking forward to doing some ogre coding rather than dealing with installers - danx0r

andy

05-09-2008 23:58:54

Well there's nothing "wrong" with the exe's on SouceForge in so much as they have been stable up there for some time and hundred's of people have downloaded and installed with them successfully..

So either you have a download issue (they are actually being corrupted either on the SF server or as you download them), which I doubt, or there is something unique about your setup that causes the installer code to break (there are built with iss).

The reason for the installer is that we need to do much more than the Pytho Installer is capable of and I needed to make it 'user friendly' (which clearly it isn't in your case)...

If you give things a few days I'm putting up a new release and will put it up there as both an installer and as a standard 'zip' which should at least give you options..

regards
Andy

danx0r

06-09-2008 05:55:15

Well there's nothing "wrong" with the exe's on SouceForge in so much as they have been stable up there for some time and hundred's of people have downloaded and installed with them successfully..


This is very disconcerting -- I just tried yet another machine (winXP this time), same exact behavior. I think it's highly unlikely that all three of my machines, running different OS's, have something wrong with them. I strongly suggest that someone else please download something from the sourceforge page and make sure it still works. I run other python .exe installers (such as pyopenGL, older pyogre) and they work fine -- bring up an installation screen and so on.

On this machine, attempting to install PythonOgre 1.1.exe gets me this dialog:

Runtime Error (at 7:738)

Out Of Range.

The other 2 machines give similar errors. The only thing I can think of is that I have installed something on all 3 machines that conflicts with what your installer creates. .NET 2.0 runtime perhaps?

Sorry to bother you with this, and yes, a .zip file will probably avoid the issue, but I was really hoping to start on this project this weekend.

andy

06-09-2008 10:10:15

Do you have anything unusual about your machines (a particular language version of XP, no administrator rights, security software related to the registry etc)

I've just done a fresh download of 1.2 RC1 from sourceforge and tested the install on a machine with and without Python installed and it seems to work OK.

The only registry entries I look for are:
HKEY_LOCAL_MACHINE, SOFTWARE\Python\PythonCore
and HKEY_CURRENT_USER, SOFTWARE\Python\PythonCore

I expect there to be (possibly) entries under these -- can you run regedit on a machine to see if you have access to these and wether they exist..

Thanks
Andy

danx0r

06-09-2008 18:51:45


The only registry entries I look for are:
HKEY_LOCAL_MACHINE, SOFTWARE\Python\PythonCore
and HKEY_CURRENT_USER, SOFTWARE\Python\PythonCore

I expect there to be (possibly) entries under these -- can you run regedit on a machine to see if you have access to these and wether they exist..

Thanks
Andy


CURRENT_USER has 2.5, LOCAL_MACHINE has 2.3, 2.4, and 2.5 (on this Vista laptop)

Please note I tried two other machines, both of which have Python installed. One was XP, the other Win2K.

I am now trying to work through compiling everything from source. I'll post another message about my compile problem.

andy

07-09-2008 00:35:18

Looks like a bug in the installer code..

Either uninstall Python 2.3, or change the value of
HKEY_LOCAL_MACHINE, SOFTWARE\Python\PythonCore\2.3\InstallPath
to point to a path that doesn't have a python.exe in it

Then rerun the Python-Ogre installer and change the regkey back again..

Regards
Andy

danx0r

07-09-2008 11:22:58

removing python 2.3 indeed solved the problem. Thanks for your timely support!

I'll post compile issues on the google group. Frankly I'd just as soon not compile it if I can avoid it (it isn't looking like much fun). However we *must* have OSX, so I guess I'll be building it there at least (and possibly ubuntu if the alpha binary isn't full-featured enough)

-danx0r