Excpt. Code 0xc000005 now in win10

[oncewas]

I just grabbed them with FOMM BSA Browser and moved them to a flash drive them moved them back and forth. I saw they were in folders when I moved them. I'll play around with that later and see what I come up with.

 

FO3 has been removed through windows and I went in and deleted everything left behind. I now have a blank Bethesda Softworks folder on D:

 

So I should go ahead and reinstall from the disk and then load a saved game and then stop as soon as I exit the Vault or should I just let the game p[lay out until I exit the Vault?

[Purr4me]

ok so you do have a retail disc?

let me post a screen shot of that discs reconfigureations using the imaging softwares.

 

you mught consider this because I did some things to fix the installer graphics bugs....understand in 2009, the systems diod not have this hardware or drivers, nor did we have TV set's with these pixel settings.

 

Fo3 is so easy to fix...LOL, I am sorry. "for me" to fix this is easy.

 

pop in the 1rst disc. don't let it run, but open it up in windows explorer.

view the contents. if your disc shows ini files? more than one?

you can do what I can teach you...The GOTY version has two discs, we do NOT want to install that second disc...please avoid that , it will corrupt the system and the games software...that's why we zipped up the DLC's...

 

catching on yet?

one moment.

[oncewas]

Well I see MO 2.9, 2.14, 2.7, 2.18,and a bunch of 3.x's all the way up to 3.8 but no 2.12 so I guess I'll just go with 2.18 unless there is a reason I need to go with one of the 3.x's

Edited August 8, 2015 by oncewas

[oncewas]

there is only one ini file that I see a setup.ini

[Purr4me]

there are 4 ini files you need to make in order to make this game comply with new Operating systems.

these files only show up during graphics setups when the game is launched for the first time.

 

once this takes place that game will forever use these settings, and so on goes the fight...with windows verses games.

so, in order to grant the user more power over what graphics settings are allowed, a way was required to come up with a better Graphics rendering seario.

 

Beat the Devil at his own game.

there are choices in the games launcher for Low, medium, high, and very high....these are ini files, these only get extracted during this process so they are never really seen.

 

how we do all of this is in preparations of the installed processes.

Note: current systems do not support the old version of VISUAL Basics and SecureRom DRM controls. .NET was really a bad point too, it get's installed and will corrupt the system.

 

windows 10 will not allow this to take place any more...in that process, windows will kill some things this game needs...regardless of compatibility, the game flat need xlive controls to even work.

 

XNA .NET does not contain this, .NET 2.0 does, and that is part of all systems...but is being removed as the game installs. In favor of .NET 4.0

they are in control now, don't be fooled.

 

the second disc installs the malware, don't use it.

The updated launcher comes from the processes for custom Fo3, those processes are from here, the nexus and use of them thru Bethesda retail patched process in combinations.

 

what takes place is an out come of accelerated graphics and permanent game place.

 

I can not stress this enough...we, you I or any one here can not make room for bad mods, made on bad software...your going to have that no matter what.

-----------------

The very high.ini...all of it's internal data is copied into the other 3 ..."replacing a;; settings " so the only possible choice the software is "given" is to give the user...that's you...all graphics abilities the system or hardware has available.

 

this is OUR scripted workaround to by pass ignorance...It is our "force ware".

3 ini files are seen on the back up imaged copy of the CD.

the launcher seen is the product of the process to yet come to pass. It can not be steam, it must be retail. the patches are designed for retail versions of the game...the patch is 52.mb downloaded. it does a ton of stuff.

things are confusing because it's meant to be.

 

so...4 files are created By you... and an install of just the first dics...and what ever crappy graphics..mostly low is chosen going all out vanilla...you have a default saved game on code designed in 2008 sitting there to be used on what's yet to come.

 

the site here Fo3 side in mods, search term is "fake"

look for JustinOthers fake patch.

Download the steam item. this is used after you have cleared the DRM training scripts.."exited vault 101, not before.

hard save. exit the game copy steam application exe into the games folder, overwrite when asked, run the game.

wait in game to 3 minutes and hard save the game.

 

IF....IF you plan on making any mods or using the Creation kit, you need to download that program and it's updating application at this time..because you can't return here later. It won't let you.

 

update after installing the geck....the GECK installer WILL be checking for the OLDER version of Fo3...Run the GECKS' 1.9 update program. now.

once you have updated the GECK and opened it up , it has now been implemented into the system Windows 10.

 

you Reboot that PC or laptop HERE.

 

now you can update Fo3 with Bethesda s patch...the launcher will be updated...when it's done the game should auto launch and very fast.

the file size of that launcher will have changed because the updates needed were from this process.

 

It's called backwards compatibility..so there it is written out by a girl.

At this point in time you stand to have The geck 1.5 patched too 1.9 and the Fo3 patched to 1.7 and can now run data meant for other additions , DLC content.

( Down loadable content ) Xlive hammered this game from the second disc .but you have all of that already so it's interferences will not be there causing problems with that OS. your still going to need all the assets from this "xlive" for special things built into the games Engine or you will never see things as they can be.

 

The error codes are Directly related to all of this text...explained as best I can as simple as I can.

OS violations traced brought all of this out. Fose users broke open a Pandora box, from it, the devil is seen. MS...and you are running in his Domain.

Flashy exit.

[Purr4me]

there is only one ini file that I see a setup.ini

read the above.

[oncewas]

I found and downloaded the "fake" file but I'm not sure what this

"Download the steam item. this is used after you have cleared the DRM training scripts..." is. I really don't use Steam for any of my FO3 games, it doesn't even show up in my steam account.

[Purr4me]

I found and downloaded the "fake" file but I'm not sure what this

"Download the steam item. this is used after you have cleared the DRM training scripts..." is. I really don't use Steam for any of my FO3 games, it doesn't even show up in my steam account.

Don't make the mistake of language here, the reason are so stated above.

You want Fo3 to run on 64bit and run flat out?

Do as I tell you.

research took a long time to compile, you have the benifit of that here.

I know you don't understand simply by the reply....and you have no game here which is a good thing because things need to be in place in order for them to work.

 

"steam users can not use the patches for retailers for the conversion processes and update the Garden of Creation kit because the Garden of creation kit REQUIRES the older Original version of Retail to update the games editing software"

 

AKA---Backwards compatibility "executable "...It's a custom fallout3.exe...it's an engine...sitting right here....in front of you. for this use ..explicitly to allow steam users to update the geck to 1.5....because DLC released For steam lack xlive data so it is not installed on steam games...so they can not update the geck.

 

 

the process it's self has Benefits for retail games....Get it now?

 

the patches has code in it looking for qualifiers..as best I can describe. to qualify some things and "re-write" the code so you can have the correct Direct-x dynamics available in the games launcher for that gecks editing window.

 

It's all about fixing a problem that permits this. Other wise That would not be allowed here period.

[Purr4me]

the site caters to both worlds at the same time, the nexus is a central hub for modding.

Beth has no servers to place data on.

Steam has no use for it...so there is the " large gap " between these two games and the mods made.

 

A steam mod is not the same as a retail mod and knowing the difference is the most important thing to know. That's why there are bugs galore.

 

The geck produced Steam version of fallout3 mods will not work on retail without patches or Bug fixit mods.

 

retail versions work no matter what.

 

the fix is above...it makes it possible for the code to be the exact same...no matter what ,or i would not waste my time posting all of this.

 

why it's important here is windows 10...that's why.

[Purr4me]

know about FOIP ?

Know about any other older mods, and all that came after them?

 

know what a patch is used for?

 

these things all come to bare all at once. IF you know about them

 

If you don't ?...your in for a world of hurt.