Jump to content

The woes of a WryeBash


Aryeonos

Recommended Posts

Okay, so I've gotten some support on Wrye bash in another thread, but I figured I'd make a thread actually about Wrye bash.

 

So far I've been told to remove every trace of Python and reinstall, that might work for someone who doesn't use other programs reliant on Python. I use Blender and Maya, along with other programs that use Python code. I have tried uninstalling and reinstalling python to those of you who think I should try anyway. But unfortunately, something as vague as "Remove everything pertaining to python" is very vague and ultimately not very good advice.

 

Other suggestions I've received include using the Command Shell to get debug information, which so far I've only been given information of how Wrye bash can't access a folder because "Access is Denied", in reality the folder just doesn't exist.

 

Right now I'm trying to get This version to work, but previously I had Wrye Bash 275 working, I don't know why, but it just up and stopped working.

 

I'll answer any questions you've got, right now I've only got so many ideas as to why it won't work, but I'd rather answer questions that will get us closer to fixing the problem.

 

Thanks people.

Link to comment
Share on other sites

By your very vague description of the problem, and the information you have given, it sounds like you either don't have the proper Python version and/or components or do in fact have permissions problems. What folder was listed when you received a Access Denied error? Next, what operating system are you running and where did you install Oblivion and Wrye Bash to? Also, you do need to include the bugdump information regardless of how unimportant you may think it is. Then we may be able to offers some advice.

 

As far as the following...

"Remove everything pertaining to python" is very vague and ultimately not very good advice.

If you're referring to some steps that I actually wrote up, it's not vague when taken in context and with consideration of the other steps. Plus it's very good advice when we're talking about getting Wrye Bash to run. Why? Because in order to ensure you have the proper Python components for Wrye Bash, Wrye Python 03a, going to the control panel and removing every trace of any previous Python installs and then only installing the proper version is exactly what you should do to get Wrye Bash to function properly.

Link to comment
Share on other sites

By your very vague description of the problem, and the information you have given, it sounds like you either don't have the proper Python version and/or components or do in fact have permissions problems. What folder was listed when you received a Access Denied error? Next, what operating system are you running and where did you install Oblivion and Wrye Bash to? Also, you do need to include the bugdump information regardless of how unimportant you may think it is. Then we may be able to offers some advice.

 

As far as the following...

"Remove everything pertaining to python" is very vague and ultimately not very good advice.

If you're referring to some steps that I actually wrote up, it's not vague when taken in context and with consideration of the other steps. Plus it's very good advice when we're talking about getting Wrye Bash to run. Why? Because in order to ensure you have the proper Python components for Wrye Bash, Wrye Python 03a, going to the control panel and removing every trace of any previous Python installs and then only installing the proper version is exactly what you should do to get Wrye Bash to function properly.

 

Uh huh, and I uninstalled/reinstalled python. Low and behold nothing changed, the problem arose to the best of my knowledge spontaneously. With a once working version of wryebash, that no longer works now.

 

I'm pretty sure you can see my whole system by clicking my name. But I'm running Windows 7 64 bit.

 

3. I fixed it...

Link to comment
Share on other sites

I fixed it...

 

Would it really hurt to say how? Surely you would have been glad of an explanation if somebody else had the same problem and "fixed it".

Link to comment
Share on other sites

I fixed it...

 

Would it really hurt to say how? Surely you would have been glad of an explanation if somebody else had the same problem and "fixed it".

 

Ah, but that would take the mystery away, you wouldn't want to spoil that now would you?

Link to comment
Share on other sites

I fixed it...

 

Would it really hurt to say how? Surely you would have been glad of an explanation if somebody else had the same problem and "fixed it".

 

Ah, but that would take the mystery away, you wouldn't want to spoil that now would you?

 

It has nothing to do with mystery; more to do with user greed -- all take, and no give.

Link to comment
Share on other sites

I fixed it...

 

Would it really hurt to say how? Surely you would have been glad of an explanation if somebody else had the same problem and "fixed it".

 

Ah, but that would take the mystery away, you wouldn't want to spoil that now would you?

 

It has nothing to do with mystery; more to do with user greed -- all take, and no give.

 

The answer was sickeningly simple. Move oblivion out of (X86) Program files, and into a new folder, in this case "C:\Games\Bethesda Softworks".

Because of windows 7's overzealous limitation of program action, all applications inside of of program files were halted, which prevented programs like WryeBash and BOSS from working. It just stopped them without a moments consent, which is why I was unable to ascertain any debugging information.

Moving Bethesda Softworks, and by extension Oblivion and WryeBash, was one of the last actions I hadn't taken yet, and incidentally yielded a solution.

Link to comment
Share on other sites

The answer was sickeningly simple. Move oblivion out of (X86) Program files, and into a new folder, in this case "C:\Games\Bethesda Softworks".

Because of windows 7's overzealous limitation of program action, all applications inside of of program files were halted, which prevented programs like WryeBash and BOSS from working. It just stopped them without a moments consent, which is why I was unable to ascertain any debugging information.

Moving Bethesda Softworks, and by extension Oblivion and WryeBash, was one of the last actions I hadn't taken yet, and incidentally yielded a solution.

 

Which is exactly what Smooth613 alluded to:

 

"or do in fact have permissions problems. What folder was listed when you received a Access Denied error? Next, what operating system are you running and where did you install Oblivion and Wrye Bash to?"

Link to comment
Share on other sites

I fixed it...

 

Would it really hurt to say how? Surely you would have been glad of an explanation if somebody else had the same problem and "fixed it".

 

Ah, but that would take the mystery away, you wouldn't want to spoil that now would you?

 

It has nothing to do with mystery; more to do with user greed -- all take, and no give.

 

The answer was sickeningly simple. Move oblivion out of (X86) Program files, and into a new folder, in this case "C:\Games\Bethesda Softworks".

Because of windows 7's overzealous limitation of program action, all applications inside of of program files were halted, which prevented programs like WryeBash and BOSS from working. It just stopped them without a moments consent, which is why I was unable to ascertain any debugging information.

Moving Bethesda Softworks, and by extension Oblivion and WryeBash, was one of the last actions I hadn't taken yet, and incidentally yielded a solution.

 

Are you saying that you used windows "move" function; as opposed to uninstalling and reinstalling?

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...