If Bash Crashes on Start
• Typically this will be signified by a small text window opening and closing in a fraction of a second.
• Open a command shell (Start: Programs: Accessories: Command Prompt).
• chdir to the Mopy directory
• Type: python Bash.py 0
• If Windows does not know where python is, you may have to enter the full path. E.g., C
python24\python.exe.
• That's the number zero at the not the letter 'o'.
• Doing this will cause error messages to spew to the command shell, helping you (and/or your friendly Internet neighborhood Wrye Bash debugger person!) to locate and fix the problem.
• Undefined Home Directory
• If see the above message at the bottom of the error dump, it means that Bash can't figure out what your user home directory is. You'll need to help Bash a little bit...
• Add the following to the end of the target for the shortcut...
-u "[full path of your user directory]"
Your user directory is the parent of your "My Documents" directory. For English systems, it's usually something like:
"C
Documents and Settings\Wrye".
When done, the target for your shortcut will look something like this:
C
Python24\pythonw.exe "C
Program Files\Bethesda Softworks\Oblivion\Mopy\bash.py" -u "c
Documents and Settings\Wrye"
• Alternatively If you're using Windows XP, make sure that it's upgraded to SP2. From what I've heard, the problem is restricted to XP machines that are below SP2. (If you're not sure that you're at SP2, right click on the "My Computer" icon, and select Properties. If you're at SP2, it will be listed under "System" on the General tab.
...
Zitat
If Bash Crashes on Start
Zitieren