Grognak's Mod Manager v1.7 (Updated March 6, 2013!)

[Ghostneedle1]

I reinstalled Python 3.3 and it worked! There was something automatically unselected when I was asked what to install so I selected it this time, maybe it had something to do with that.

[speedoflight]

I get the msg "python is not recognized as an external or internal command, program or exe not executable" (is something like that, i am translating from spanish... ).

Its like python is not installed correctly?? i uninstalled all my previous python versions and installed only 2.7.3...

That's a good translation... and a likely interpretation (or at least not installed where you thought it was).

Make sure you do in fact have the folder you installed python to, and that it does contain python.exe.
If you give the complete path to it in a prompt (something like "c:\Python27\python.exe") you should not be seeing that error. It's getting in the way of other more interesting errors.

The path is c:\Python27 and yes, there is a python.exe inside

Im running it as administrator , i tried the SET commands you posted before, nothing works lol.

Any other ideas?

[Vhati]

I get the msg "python is not recognized as an external or internal command, program or exe not executable" (is something like that, i am translating from spanish... ).

Make sure you do in fact have the folder you installed python to, and that it does contain python.exe.
If you give the complete path to it in a prompt (something like "c:\Python27\python.exe") you should not be seeing that error.

The path is c:\Python27 and yes, there is a python.exe inside

Sanity Check:
You create a prompt, cd to GMM's folder, and type this - without typos or quotes.

Code: Select all

c:\Python27\python.exe main.py

And you get this!?

Code: Select all

"python.exe" no se reconoce como un comando interno o externo, programa o archivo por lotes ejecutable.

I can't fathom how that could happen, but here's another way.
What if you just type this in the prompt?

Code: Select all

main.py

(Let Windows figure out where python is, the way it does when double-clicking.)

[speedoflight]

I get the same result.

It doesnt matter where i open the command prompt, i always get the same message.

The thing is, the previous version of gmm works pefect.. so the python installation is recognized, but not with the last update..

[sanmonku]

hey, the info about a mod is handled by GMM right?

i just upgraded to 1.7 and saw that my mod "better planets and backgrounds" now has an info text.

with version 1.2 the description is right.
with version 1.3 it claims that only 3 backgrounds are taken from hubble, which is not true. i used a lot in that version.

i just looked in to the file "default_moddb.py" and saw how GMM puts it together.

so if you release the next version i would be pleased if you could delete this line: Only 3 of the backgrounds are taken from Hubble, rest were done by me.

don't like to take credit for stuff i didn't make

[Vhati]

hey, the info about a mod is handled by GMM right?

i would be pleased if you could delete this line: Only 3 of the backgrounds are taken from Hubble, rest were done by me.

Will do. All versions get the same description, so I try to edit them to be generic.

[Vhati]

The path is c:\Python27 and yes, there is a python.exe inside

Sanity Check:
You create a prompt, cd to GMM's folder, and type this - without typos or quotes.

Code: Select all

c:\Python27\python.exe main.py

And you get this!?

Code: Select all

"python.exe" no se reconoce como un comando interno o externo, programa o archivo por lotes ejecutable.

I get the same result.

Oh-kaaay, go to where python is. Leave it no excuse...

Code: Select all

cd c:\Python27
python.exe --version
python.exe "c:\wherever\GMM\is\main.py"

(Type "py", then hit tab to make the prompt type "Python27" and "python.exe" and acknowledge their existence.)

It's either going to choke on the first line at cd (Silly typo after all? yay),
or the second line (One of us is having a recurring nightmare about tech support, or you've got some overprotective security getting in the way? Need to install python for "all users"? No idea.).

The thing is, the previous version of gmm works pefect. so the python installation is recognized.

Previous versions of modman.exe actually contained a copy of python. Grognak's handling that, but I get the impression packaging that way has grown too quirky for the near future (The virus false positives, and now straddling Python 2.x/3.x compatibility).

The current modman.exe just runs whatever python is installed against main.py. A minor oversight in its design for 1.7 prevented it from finding python is all (though not in the way you've got going on ).

[Galgersha]

I'm having trouble getting it to work. For starters, is it because I'm on windows 8? But anyways, I installed Python 2.7.3, and modman.exe says that there is no supported version of Python. If I run the main.py, it starts and runs all fine but when I try to patch in a mod it says that it doesn't have permission to and shuts down. Anything that I could do to fix it?

[Vhati]

when I try to patch in a mod it says that it doesn't have permission to and shuts down.
Anything that I could do to fix it?

Yep.

• Start Menu -> Programs -> Accessories.
• Right-click "Command Prompt" to run as an admin.
• Type this, then hit enter: cd "c:\wherever\GMM\is"
• Type this, then hit enter: main.py

Windows Vista/7/8 insist on only letting admin-apps modify what's in important locations like Program Files.

If modman.exe hadn't been glitched, you could've right-clicked that to run as an admin.

[Galgersha]

• Start Menu -> Programs -> Accessories.
• Right-click "Command Prompt" to run as an admin.
• Type this, then hit enter: cd "c:\wherever\GMM\is"
• Type this, then hit enter: main.py

Windows Vista/7/8 insist on only letting admin-apps modify what's in important locations like Program Files.

If modman.exe hadn't been glitched, you could've right-clicked that to run as an admin.

modman.exe doesn't detect python, that's the problem. main.py does, but doesn't have permission to edit it says. I never said anything about modman.exe not having permission.