Post by Krusty on Sept 6, 2011 23:38:37 GMT -5
The purpose of this post is to explain what files are needed to install Python for a Windows user. This will allow executing a customized MAMEHub.py instead of using the official static mamehub.exe.
Note: This procedure is not needed for Windows users to use MAMEHub. This procedure is intended only for advanced users who want to be able to customize their MAMEHub.py or to be able to use someone elses customized MAMEHub.py.
Files Needed:
(stick with unicode over ansi, 32-bit over 64-bit)
Python 2.6.6 - Home Page - Direct Download (14.5 MB)
wxPython - Home Page - Direct Download (10.8 MB)
Twisted - Home Page - Direct Download (2.49 MB)
Directions:
1. Install Python 2.6.X
2. Install wxPython and Twisted. If you get an error about PYTHONPATH variable then cancel the installation and create the environment variable*. Below is an example illustration of what the PYTHONPATH environment variable should look like when configuring it.
3. Ensure that your installed python directory is part of your PATH environment variable. Below is an example illustration of what the PATH environment variable should look like when configuring it.
4. Copy the files from mamehub\src into mamehub\dist. (No need to overwrite anything. Just the files that are missing are needed).
5. Open a command prompt. Navigate to your mamehub\dist directory and execute python.exe mamehub.py --alright
* Step 2 may not be needed in some cases.
Notes:
1. Here is Digitalghost's original guidance on this topic from April of 2011. Text is taken from the MAMEHub chat lobby and through a follow-up message.
2. This procedure was authored by me (a MAMEHub tester) using Digitalghosts guidance linked above. I found which python files worked and validated this procedure on multiple computers.
3. The --alright parameter is neccessary to prevent users from launching MAMEHub.exe and forces them to launch the mamehub.bat instead. Reviewing mamehub.bat will make this more clear.
4. So far as I know, Digitalghost would welcome MAMEHub.py submissions if you can add or modify features. Please be clear in your submission what it was you changed and why. I would recommend e-mailing the submission to Digitalghost but also feel free to post your modified MAMEHub.py here as well.
5. Linux/Mac users need only replace their MAMEHub.py to run a customized MAMEHub.py. This is not an option for Windows users who use the static mamehub.exe as per the mamehub.bat
6. Command prompts that were opened before changes to environment variables were made will not recognize those new changes. Open a new command prompt in that scenario.
7. If you have any suggestions on the recommended files to install in this procedure or about this procedure in general please feel free to add your reply.
8. The difference in functionality when executing MAMEHub.py versus using mamehub.exe (via mamehub.bat) is that when you launch or join a game, there will not be the extra command prompt that normally launched in conjunction with a game. This extra command prompt can be helpful because it's a little easier to terminate a session that is 'not responding' by closing the extra command prompt (a rare scenario).
Note: This procedure is not needed for Windows users to use MAMEHub. This procedure is intended only for advanced users who want to be able to customize their MAMEHub.py or to be able to use someone elses customized MAMEHub.py.
Files Needed:
(stick with unicode over ansi, 32-bit over 64-bit)
Python 2.6.6 - Home Page - Direct Download (14.5 MB)
wxPython - Home Page - Direct Download (10.8 MB)
Twisted - Home Page - Direct Download (2.49 MB)
Directions:
1. Install Python 2.6.X
2. Install wxPython and Twisted. If you get an error about PYTHONPATH variable then cancel the installation and create the environment variable*. Below is an example illustration of what the PYTHONPATH environment variable should look like when configuring it.
3. Ensure that your installed python directory is part of your PATH environment variable. Below is an example illustration of what the PATH environment variable should look like when configuring it.
4. Copy the files from mamehub\src into mamehub\dist. (No need to overwrite anything. Just the files that are missing are needed).
5. Open a command prompt. Navigate to your mamehub\dist directory and execute python.exe mamehub.py --alright
* Step 2 may not be needed in some cases.
Notes:
1. Here is Digitalghost's original guidance on this topic from April of 2011. Text is taken from the MAMEHub chat lobby and through a follow-up message.
2. This procedure was authored by me (a MAMEHub tester) using Digitalghosts guidance linked above. I found which python files worked and validated this procedure on multiple computers.
3. The --alright parameter is neccessary to prevent users from launching MAMEHub.exe and forces them to launch the mamehub.bat instead. Reviewing mamehub.bat will make this more clear.
4. So far as I know, Digitalghost would welcome MAMEHub.py submissions if you can add or modify features. Please be clear in your submission what it was you changed and why. I would recommend e-mailing the submission to Digitalghost but also feel free to post your modified MAMEHub.py here as well.
5. Linux/Mac users need only replace their MAMEHub.py to run a customized MAMEHub.py. This is not an option for Windows users who use the static mamehub.exe as per the mamehub.bat
6. Command prompts that were opened before changes to environment variables were made will not recognize those new changes. Open a new command prompt in that scenario.
7. If you have any suggestions on the recommended files to install in this procedure or about this procedure in general please feel free to add your reply.
8. The difference in functionality when executing MAMEHub.py versus using mamehub.exe (via mamehub.bat) is that when you launch or join a game, there will not be the extra command prompt that normally launched in conjunction with a game. This extra command prompt can be helpful because it's a little easier to terminate a session that is 'not responding' by closing the extra command prompt (a rare scenario).
