bbarr97

I think all of this brought up a good point. I didn't support Steam and Bethesda's methodolgy. But as a community we obviously suck at donating. My gaming in Skyrim improved immensely with mods and yet I have not donated. That changes today and all modders can expect some contributions as income allows. This has been a strong community and it is time for us to support modders as a community. And if we donate simply one buck to a modder each they can recoup some beer for their time and it is 100% theirs! They deserve it through our appreciation and it may prevent another corporation from coming in and trying to ruin it.

I have that set and have tried several different versions of windows to run it on on compatibility.

Absolutely bizarre, By using pythonw.exe to run it I will get the following error when I try to install a mod on the Installers tab Traceback (most recent call last): File "C:\games\oblivion\Mopy\basher.py", line 6936, in Execute self.data.install(self.filterInstallables(),progress,last,override) File "C:\games\oblivion\Mopy\bosh.py", line 11501, in install installer.install(archive,destFiles,self.data_sizeCrcDate,SubProgress(progress,index,index+1)) File "C:\games\oblivion\Mopy\bosh.py", line 10688, in install self.unpackToTemp(archive,dest_src.values(),SubProgress(progress,0,0.9)) File "C:\games\oblivion\Mopy\bosh.py", line 10656, in unpackToTemp ins = Popen(command, stdout=PIPE, startupinfo=startupinfo).stdout File "c:\python26\lib\subprocess.py", line 614, in __init__ errread, errwrite) = self._get_handles(stdin, stdout, stderr) File "c:\python26\lib\subprocess.py", line 722, in _get_handles p2cread = self._make_inheritable(p2cread) File "c:\python26\lib\subprocess.py", line 761, in _make_inheritable DUPLICATE_SAME_ACCESS) WindowsError: [Error 6] The handle is invalid If I use python.exe it works fine except for the darn command window staying open. At least I can run it but there is some oddity going on and I have this obsessive need to solve iit.

That helped narrow down the problem some. I checked the file association and it was set to pythonw.exe in the properties for the file. To experiment I changed it to python.exe and it started up but the CMD window was still up. I closed it down and then tried starting it again with no luck. I changed the association back to pythonw.exe and it will not start that way either now. So I got it to start once by changing the association but after that no dice. If I go to the CMD prompt and type c:\python26\pythonw.exe bash.py it will start with no CMD window left open which is nice. Still, a pain in the but to do that each time. Any ideas?

Howdy, I am having trouble getting Wrye Bash to start using the Wrye Bash Launcher.pyw file in the Mopy directory. Some quick specs: Windows 7 64 bit (Home Premium) 6gb ram Got Wrye Python v02 installed Got Wrye Bash 290 installed I am able to get Wrye Bash started but the only way I can do it is by typing c:\python26\python.exe bash.py in the c:\games\oblivion\mopy directory. (The d command doesn't help because there is no log file because it doesn't crash) Unfortunately, this leaves the CMD window open which is somewhat annoying. Any idea why I cannot use the Wrye Bash Launcher.pyw file? I have already tried modifying the bash_default.ini file with the actual directory to no avail. Appreciate the help, bbarr97