Settings.xml

[bxela1]

So ive been playing a lot of fallout 3 recently and having modded oblivion before, I thought I would check out some mods for fallout 3. But when I downloaded the mod manager and tried to run it, it had issues saying that it didnt have write access to 'Settings.xml'. I run Windows 7, so I checked for any issues with privileges only to find that theres no settings.xml file at all for fallout. The game runs perfectly fine so I dont know what settings.xml actually does, but apparently I dont have one..

Also, if I try to add mods using the launcher, it can only locate my .esm files and as soon as I exit the Data Files screen, it unselects the mods again.

 

Does anyone know why this might be the case and if theres anyway I can fix this?

[nosisab]

So ive been playing a lot of fallout 3 recently and having modded oblivion before, I thought I would check out some mods for fallout 3. But when I downloaded the mod manager and tried to run it, it had issues saying that it didnt have write access to 'Settings.xml'. I run Windows 7, so I checked for any issues with privileges only to find that theres no settings.xml file at all for fallout. The game runs perfectly fine so I dont know what settings.xml actually does, but apparently I dont have one..

Also, if I try to add mods using the launcher, it can only locate my .esm files and as soon as I exit the Data Files screen, it unselects the mods again.

 

Does anyone know why this might be the case and if theres anyway I can fix this?

I think the problem being you installed the game in the default C:\Program Files folder, the better answer is, uninstall it and install somewhere else, maybe C:\Games

 

Many threads around here about this issue and explanations, enough to tell that is a blessed folder under increased MS security protection that forces disabling the UAC and run as administrator, go figure the MS concept of security.

 

Anyway, do it, install not only Fallout 3 as any other game far away from that folder and you'll not be sorry.

 

PS: xml is becoming a standard to control and settings that eventually will substitute the text based ini files over there. You should find several across the whole Windows installation. That from FOMM seems not even was created hence the message 3rd part applications can't write the (insert bad name here) inside 'that folder'

[bxela1]

That seems to have fixed the problem, thanks :smile: