EMBseries sucks.

[Anthin]

I was wrong about Steves latest fixer not having problems.
Emb Keeps turning itself on,so after five minutes flying,CTD!
Still can't find the two files in FSX root directory or anywhere else
so I was wondering if I ran FSX repair would it get rid of them?
Also what gets removed when repair is complete? Have not done this
in a very long time. The only other option is to do a new install. AARGGG!

I am really hacked off as the sim was running silk smooth.
Living in hope.
regards Anthin.

[TheFamilyMan]

If the .dll file modded by the ENB mod is not in your main FSX directory, the same named .dll file which resides in C:\windows\system32 must have been replaced by the ENB modded file. If you have the original ENB zip file (or whatever it was packaged into) which you once installed, take a look into it to get the .dll file name, date and size and compare that info with the like named file in system32. If the info matches, you've found where your ENB problems exist. Hopefully a backup of that .dll file exists in system32 such that you can rename that backup to is original name and be done with it. Otherwise you must find a trusted version of that .dll to replace the ENB modded file. Hopefully this will solve your problems. BTW, I am assuming you're running Windows 7.

[ncooper]

I would strongly advise against running an FSX repair to address
this problem, as the repair only replaces default FSX files, which
ENB series are not.

If you still have the ENB series files, you can try to copy and paste them
into your FSX root folder but once done and while they are still highlighted,
select delete and remove them.
This will ensure that all the correctly placed files have been removed.

In the case of .dll files, the way that ENB series, SweetFX and the Dx10 fixer work is to place modofied
Direct X .dll files into the FSX root folder because FSX looks there first and if it find the
required file, it does not use the Windows\system version(s) which are often incompatible.

If, as TheFamilyMan suspects, at some stage you put the modified .dll files into your Windows\System
you will need to find replacements either by repairing Windows itself or searching the internet
for replacements.

[Anthin]

Thank you very much. I will try these suggestions today after
I get home from Physiotherapy.
Will let you know results.
Regards Anthin.

[Anthin]

Thank you to the Family Man and ncooper.
Did as you suggested. Found the file in C:\windows\system32.
I then copied that file from my old computer where I thanklfully
still have FSX installed. Tried to replace the file but was not allowed.
I then tried to install ENB again hoping it would be highlighted as
you suggested and file vanished telling me it was already installed
and did I want to overwrite.Yes and pop vanish.
I then tried installing the d3d9.dd file from old computer and tried DX9
again. Start up FSX screen had no bright flash or red lettering. Yea! with
nobs on!

Uninstalled Steves fixer as suggested and installed newest fixer and got
the warning that the offending file could cause DX10 to crash the flight sim.
Went ahead anyway and took a flight with in the Chipee. Mini stutters but
no CTD. Will try tomorrow with a heavy from seatac on a longer flight.

I want to thank you guys for your help and SOH for being the friendliest
FS site.
Many regards Anthin.

PS. How do you repair Windows?

[ncooper]

It seems that you have somehow replaced the d3d9.dll and d3d8.dll files in your Windows
system.
By using a default version from your other PC and placing it into your FSX root folder,
you have successfully made FSX use that version instead of the now corrupt Windows version.

You should be able to repair your system files as follows, I am assuming you have Windows 7.


First, open Task Manager and then from the drop down menu select File\Run new Task.
In the box that appears, type cmd and tick the Create this task with administrative priviledges
box.

Click on OK, you will then see a "DOS" window, black with white writing.

Copy this text

sfc.exe /scannow

and paste it into the black box where it will appear after...system32>

Once you have done this, press Enter and Windows will scan and repair all your system files.
It takes a few minutes and at the end you may see a report when it found corrupt files.
When it has finished, close the "DOS" box.

To test the result, temporarily remove or rename the .dll file(s) you added to the FSX folder,
run FSX and see if the error returns.
If it does not, you can then permanently delete the file(s) from the FSX folder as your system will have been repaired.

(As the .dlls are part of Direct X the Scan and Repair might not pick them up, I don't know everything but in the event
of the above steps not working, it is possible to reinstall Direct X. Let's try this first.)

[JoeW]

What is ENB? I DO NOT want to install that on my computer.

[Anthin]

Thanks for the help ncooper I will give it a go.
Anthin.
JoeW. ENBseries changes lighting effects. Turned
out to be nasty for me.
Regards Anthin

[Anthin]

OK I completed the scan and no corrupt files were found.
Is it possible to reinstall Direct X ?
Thanks in advance.
Anthin

[Adamski_NZ]

OK I completed the scan and no corrupt files were found.
Is it possible to reinstall Direct X ?

Easily done. Just find the link on the Microsoft site. It's not a big deal (!).

http://support.microsoft.com/kb/179113

http://support.microsoft.com/kb/1791...on%20installed

I reinstall mine quite often - not because there's anything wrong - just a preventative/precaution thing.

Adam.

[Anthin]

Thanks Adam I will try that. Fingers crossed that this might
solve my problem.
Anthin.

[Anthin]

Did as you said Adam but no luck. I think I am looking down the barell
of the dreaded FSX reinstall. Hopefully that will work. If you can think of
any alternative I would appreciate it. Another question, where can I find
pilot records as in logbook/rewards?

Anthin

[TheFamilyMan]

(snip)

I then tried to install ENB again hoping it would be highlighted as
you suggested and file vanished telling me it was already installed
and did I want to overwrite.Yes and pop vanish.

(snip)

If you did the above to install the ENB file in the FSX directory, it appears that the ENB modded .dll really is in the FSX directory and your folder viewing privileges won't let you see it. You can change folder viewing settings using the control panel's ' Folder Options' and make sure "View->Hidden files and folders->Show hidden files, folders, and drives" is checked. Definitely delete that .dll if it then magically appears in the FSX directory. If is does not appear (which I think would be very weird; are you running with UAC enabled and with non admin privileges?), try copying the liked named .dll file from system32 into the FSX folder. I was wondering if this was your problem all along, and what you described above points to this, but then again...Good Luck!

[ncooper]

I agree entirely with The FamilyMan.
If you go to the view options as he suggests,
make sure also that the
"Hide extensions for known file types" box is NOT ticked.

By default it is and can very easily lead to both confusion,
as in this case and error because without being able to see the extension,
filename.dll looks exactly like filename.bgl, .exe etc etc,

ie,

filename
filename
filename

instead of

filename.dll
filename.bgl
filename.exe

so one can be faced with numerous different files
which all look exactly the same.

[Anthin]

Thanks I will try this.
Anthin

[Anthin]

Found the offending files!
File extensions was ticked,so I unticked them and
all the file extensions appeared. Bingo. there they were.
I then uninstalled steves fixer and reinstalled and no
warning. So they are gone. Just have to try a long flight now.
Thank you guys for solving the problem. Do not have to
reinstall FSX now. Finally solved.

Many thanks Anthin.

[Adamski_NZ]

Yay! That's great news after all this grief!

I wouldn't recommend messing with your pilot/log files. I seem to remember that causing problems - but I could be wrong (Google it). Don't break your FSX after all this :lol:!

Adam.

[noddy]

Great news, what a great community we have here.

[Anthin]

I agree noddy. It sure is a great community. The
guys kept with me and finally found the answer. Just
saying thank you doesn't seem enough. Back to flying DX10.

Thanks everyone.
Anthin.

[TheFamilyMan]

All's well that ends well (especially when one is of saved of an FSX or even an OS reinstall). I can image your relief Anthin (been there, done that in different matters). Now to get onto the goodness the DX10 fixer brings along with it; definitely look into enabling cockpit shadows for your add on aircraft that don't have them. The later releases allows fine tuning of the effects (shadows and bloom) and it is stunning when you get it dialed in to your preferences.

Though my post count here is quite low, I've been a lurker here for years. PaulJ gave me some encouragement to get more active here before he decided to step down. Since I tire of the tubeliner stuckup-ness of the majority of what goes on over at AVSIM (where I've been active for a few years), this place is a most welcomed relief. BTW, Thanks for the feedback Anthin.

[Anthin]

Thank you to TheFamilyman.

Your help was greatly appreciated. Yes a great sigh of relief as
I was dreading a reinstall. Will look at the new features in Steves
Fixer. Wow I can't believe it is fixed. Bye the way I agree with the
tubeliner comment. So many different planes to fly both freeware and
payware.

Thanks again.
Anthin.