bInvalidateOlderFiles=1 crash to desktop, please join in my march for

[darrell87]

Hello All,

 

I weep at your success and wish to the fiery pits my constant misfortune. There is nothing that makes my day better than reading in the Archiveinvalidation invalidated entry that I am simply BEAT. I offer this thread, in the heart of those discussions where an armor color is not right, a place for my fellow lepers to discuss and hopefully defeat their aliment . As only our generation can, we have created a bustling scene where bright minds can double the size of Fallout's install directory with modifications that stir the mind. All I ask, so humbly, is for an intuitive of like for those of us who have this real problem. I ask, why I am to be a paraplegic ADHD victim trapped in a candy store. I ask, cast me out or help me to victory.

 

Here's my story:

 

I run Vista Ultimate 32Bit

I have installed in the root of C:/

I have disabled UAC.

I have modified permissions of my install directory.

I have manually and with FOMM changed bInvalidateOlderFiles=1

I have tried with no mods activated.

I have verified it only and immediately crashes with this option set.

I run AVG 9.0

I run Daemon Tools

I run an Nvidia 9800 GTX+

I run an Asus Mobo with Nvdia chipset

 

The retail version appears to not be problematic, but, no good mods work with it anymore

 

I do not know how or where to get the the archiveinvalidation team to see if they have made any progress.

 

Thank You

[darrell87]

Update:

 

I have now Verified the problem does not exist in the retail version, so I believe it must have been introduced with a patch that conflicts with something in my configuration. I will now check each patch individually till I notice the problem.

 

Thank You

[darrell87]

Update:

 

I am happy to report the problem does not persist with patch 1.1, getting closer to running many mods. I am now trying 1.4... AND it is GOOD too.

 

Thank You

 

 

Update:

 

Thank you Mr. WoogieMonster, I do wish to comply. Good News! Problems did not persist through an individual application of each patch. I will now test each utility (e.g. FOMM, FOSE)

 

Thank You

 

Update:

 

All utilities and Unofficial Patch installed successfully! As is usually the case, it appears much of this issue has to do with how we do things. For those of you who stumble on this thread, remember these key things.

 

1. Delete all old files from your Fallout Directory BEFORE reinstalling. What we perceive as old, perhaps original, and what the Windows files system perceive as old, timestamps, can be two different things. Leave NO doubt!

 

2. Install things one at a time and immediately test. For the reason above and others, there is no reason to get carried away. This includes individual patches which can be gotten from StrategyInformer or possibly even here.

 

3. Anyone here or elsewhere will tell you, turn off all service type applications (antivirus, disk defrags). Also, apps written for Windows Vista and 7 LOVE to install as windows services, this new methodology can interfere with the internal workings of more traditionally written programs like FO3, so, check Administrator tools --> Services and turn off anything you know you installed and do not need.

 

4. Finally, Always stick to the diagnosis method. Test, change one thing and test again. Eliminate problems and use logic. Do all that and if all else fails... maybe you are beat, bu, do not believe everything you read.

 

Note: Search before posting or starting a new thread and get strong glases for the small parts of the forum you can not read, else the WoggieMonster will get you!

[WoogieMonster]

As a registered user, you have the ability to edit your posts. The way you are posting is going to get your thread locked.

[Rabbit1251]

Darrell87,

 

I am pleased to hear that your problems are now at an end. In regards to your manner of posting I hope that you will please accept a heartfelt kudo for your literary breath of fresh air in this stagnant pool of illiteracy that we call the World Wide Web. I can now sleep tonight knowing that I have at least enjoyed a good read today.

 

 

Rabbit

[darrell87]

Thank you, I really appreciate that. I guess you could say I am something of a new veteran. I have been running mods since Half-Life, but, I never got involved in the forums. To be honest, much of the enthusiasm came from the "cannot play ANY modified content" line of the archiveinvalidation invalidated listing. Something about a seemingly passing remark regarding a problem that has likely persisted since Oblivion, made me want to do something about it. It made me want to either find or make a solution, for which I am still committed. So that I may help anyone else who comes to feel claustrophobic about that line, I will man this thread as long as it exists.

 

Thank You and Have a nice night

[csb]

In case you ever have to re-install, the procedure goes something like this:

 

1. Uninstall Fallout 3 via the Control Panel and Add/Remove Programs. It's too easy to miss something doing it manually. You can opt to keep your previous save games.

2. Re-install. If you have Vista or Windows 7, disable UAC first ... it often clashes horribly with Bethesda's use of SecuROM.

3. Do not pass go, do not collect 200 Caps. Immediately install the 1.7 patch.

4. Install any DLC content.

5. Install Timeslip's Fallout Mod Manager.

6. Install FOSE (optional). Many mods use this script extender application, it's best to install it early on when the game is at its most stable (relatively speaking).

7. Check your My Games/Fallout3 folder to see if Fallout.ini exists. If not:

8. Start Fallout 3. Exit.

9. Start Fallout Mod Manager, click the "Toggle invalidation" button. There, now your bUseOlderArchives setting is set. You might as well click the "Tweaks" button and check the box to use the fake xlive.dll while you're at it. Seriously, does anyone past the age of ... oh, about age 11, use Games for Windows Live? (And why are they playing an "M" rated game?)

10. If you have a multi-core processor, check the Fallout3 guide on TweakGuides.com for the proper settings for multi-threading, etc. in your Fallout.ini file.

11. Download and install ElminsterAU's FO3Edit. Between FOMM and this utility, you'll get the most stable configuration of Fallout 3. Get Miax's great FO3Edit Guide - Web-enized to learn how to use FO3Edit to find and resolve mod conflicts.

12. Once the load order is set (using FOMM) and merge patch are done (using FO3Edit), run FO3Edit in Master Update mode. Your configuration is now about as stable as you can reasonably hope.

13. Start Fallout 3 and enjoy the game.

 

Added ps: While I enjoyed the literary tenor of the post (and subsequent ones), I join in with the others in saying that that "literary device" will most likely not endear you to the site's moderators. In the future, perhaps use that technique with an edit of the original post. Just a suggestion, however, Mr. Hemingway. :D