![[info]](http://l-stat.livejournal.com/img/userinfo.gif){kind=small}
I recently had a bit of a pain trying to run Oblivion Mod Manager ("OBMM" to those in the know). See, it needs a reasonably working .NET installation, which I don't have. I decided it was time to fix that.
The trouble I've been having is that it would error on me whenever I tried to install or upgrade or even repair .NET.
This came about because I deleted some files from C:\windows\install - don't do that, they look like they're just a bunch of .msi installers, and aren't needed for running anything, but they are sure useful when uninstalling, upgrading, or installing stuff.
Then, looking at the text of the error log that would be sent to MS when the programs crashed, I was able to find what file it was looking for, and where. I could also have used something like truss, I guess. I then downloaded and placed that one, and rinsed, and repeated.
I needed to download:
NDP20-KB917283-X86.msp,
NDP20-KB922770-X86.msp,
NDP20-KB928365-v2-X86.msp,
They needed to be downloaded from Microsoft. Searching for the KBnnnn bit on Microsoft.com usually gets you there. The download will be a compressed exe, so a quick unzip with winzip later and you have the .msp files.
It was looking on a drive that no longer existed for the old tmp folder that it had installed from. Oh fun. So dismount that drive (CD drive), and "subst D: C:\" to make D: a virtual drive pointing to C:, then create the folders it was looking for, each in turn, downloading each file as it complained about it being missing.
Once they were downloaded and placed in their respective correct random directories within C:\Documents and Settings\Administrator\Local Settings\Temp\, it installed fine, and a quick reboot later, I was able to run obmm again! :D
Others having the problem "oblivionmodmanager has encountered a problem and needs to close. we are sorry for the inconvenience." - this should hopefully help you. Most likely all you need to do is download and run the ".net framework" - Google for that and you should be fine. Apparently obmm requires 2.0 and above, and 2.0 is the last one to support Win95, Win98 or Win2k, so that's the one you'll need if you are using those OSs (as I am).
The trouble I've been having is that it would error on me whenever I tried to install or upgrade or even repair .NET.
This came about because I deleted some files from C:\windows\install - don't do that, they look like they're just a bunch of .msi installers, and aren't needed for running anything, but they are sure useful when uninstalling, upgrading, or installing stuff.
Then, looking at the text of the error log that would be sent to MS when the programs crashed, I was able to find what file it was looking for, and where. I could also have used something like truss, I guess. I then downloaded and placed that one, and rinsed, and repeated.
I needed to download:
NDP20-KB917283-X86.msp,
NDP20-KB922770-X86.msp,
NDP20-KB928365-v2-X86.msp,
They needed to be downloaded from Microsoft. Searching for the KBnnnn bit on Microsoft.com usually gets you there. The download will be a compressed exe, so a quick unzip with winzip later and you have the .msp files.
It was looking on a drive that no longer existed for the old tmp folder that it had installed from. Oh fun. So dismount that drive (CD drive), and "subst D: C:\" to make D: a virtual drive pointing to C:, then create the folders it was looking for, each in turn, downloading each file as it complained about it being missing.
Once they were downloaded and placed in their respective correct random directories within C:\Documents and Settings\Administrator\Local Settings\Temp\, it installed fine, and a quick reboot later, I was able to run obmm again! :D
Others having the problem "oblivionmodmanager has encountered a problem and needs to close. we are sorry for the inconvenience." - this should hopefully help you. Most likely all you need to do is download and run the ".net framework" - Google for that and you should be fine. Apparently obmm requires 2.0 and above, and 2.0 is the last one to support Win95, Win98 or Win2k, so that's the one you'll need if you are using those OSs (as I am).
OMOD Vista SP1
it.The only thing I know is this issue started about the time I
updated my Vista with Service Pack 1.Have you heard of the
same thing happening to anyone else?
Deman
Re: OMOD Vista SP1
Apparently you can run two versions of .NET side by side on the same machine, but I don't know how.
If you mean that the OMOD you created with OBMM is crashing, then no, I dunno. Is it crashing OBMM or Oblivion? What error messages? Does it stop crashing if you disable the OMOD?
Re: OMOD Vista SP1
Seriously, I've reinstalled Oblivion like 5 times, and reinstalled OBMM like 30 times, this is starting to get reaaally frustrating.
I tried installing .Net 3.5 and stuff, but that stuff for some reason wont install either.
This is about all my text error log says:
My temp text file:
Windows NT Version 6.0 Build: 6000
Product (0x6): Windows Vista (TM) Business
Edition: Business
BuildString: 6000.16514.amd64fre.vista_gdr.070627-150
Flavor: Multiprocessor Free
Architecture: X64
LCID: 1033
and my MDMP file when debugged:
Microsoft (R) Windows Debugger Version 6.9.0003.113 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Shane\AppData\Local\Temp\WER53
User Mini Dump File: Only registers, stack and portions of memory are available
Symbol search path is: *** Invalid ***
****************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************
Executable search path is:
Windows Vista Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: SingleUserTS
Debug session time: Thu Jul 10 18:07:19.000 2008 (GMT-6)
System Uptime: 0 days 10:55:43.135
Process Uptime: 0 days 0:00:13.000
............................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(b6c.e14): CLR exception - code e0434f4d (first/second chance not available)
eax=00000000 ebx=756d18d1 ecx=00000001 edx=00000000 esi=0042d468 edi=00000000
eip=772ca69d esp=0042d424 ebp=0042d490 iopl=0 nv up ei pl nz ac po nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000212
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -
ntdll!ZwWaitForSingleObject+0x15:
772ca69d c20c00 ret 0Ch
(END)
Im using the 64 bit version of Vista, and I have no clue what to do. Could you please help me on this? I'm not sure what my exact problem is here.
Re: OMOD Vista SP1
It's a pain in the arse to manage mods without it, though, so I hope you do find a solution. Make sure to post it to the obmm page if you do - I imagine other vista users will have the same problem.
Re: OMOD Vista SP1
I think some registry defragging program screwed it up.