"Tony Sperling"
Usenet Poster
tony.sperling@dbREMOVEmail.dk
Posted on:
Dec 8, 2007, 3:11 PM
Post #12 of 16
(28 views)
Shortcut
|
Well, it is not easy to make guesses without a minimum of information. I
would try and contact MS Support to see if they have something to say about
Message Filters in general - and this errorID, in particular. Perhaps this
link is appropriate?
http://support.microsoft.com/directory/onlinesr.asp.
And, no - I have no personal contacts behind the scenes, unfortunately. Most
everything I know has been picked up from right here, actually. How old is
the machine, and are you sure the Power Supply is GOOD?
Tony. . .
"Algy" <Algy@discussions.microsoft.com> wrote in message
news:905AE7C3-7DDC-4606-85FB-C729D769E529@microsoft.com...
> Tony,
> Have done un&re-install on diff. part/disk/directories, but the problem
> persists. This is a very strange error(and btw I have run MS FS since the
> early FS2 days ane this is the first release causing me this kind of
> trouble). As I wrote, I have saved an image from a fresh install where FSX
> did work(as for your suggestion on reinst OS), and as I restored it, I
> thought that it would be a stable FSX but the problem still comes back
> after
> a couple of weeks/FSX-sessions. I suppose that as long as there is no hint
> on
> why this error id turns up(or what modules are involved) it will be very
> difficult to resolve. If I understand you correctly, you have no contacts
> that might be helpfull with this?
> --
> Pull up
>
>
> "Tony Sperling" wrote:
>
>> Some of the few and 'vague' suggestions I've seen, so far, seem to hover
>> around the Registry (?) and/or Message *.DLL's that cannot be found, (!).
>>
>> Depending on what other work you are doing on your machine, I would
>> suggest
>> un-installing FS completely - including all the stuff that the installer
>> doesn't remove on it's own. If this is a new system, you might even
>> consider
>> re-installing the OS, from scratch?
>>
>> Remember to reboot between every major step of the operation. When it's
>> clean install it again. The important step now, is to install to a
>> different
>> location than the former. My own preference is to install to a different
>> drive (partition), and to use a directory that you create yourself (I use
>> E:\FS9, for my 2004 installation - it doesn't have to be the Program
>> Files
>> 'thing') now, som parts will land on the system drive (C:\) anyhow, but
>> you'll end up with your new location being written to your registry, and
>> any
>> possible errors from the earlier installation, still residing in the
>> Registry should never have to be referenced again.
>>
>> Make sure that your optical drives are cleaned, and the media too, do not
>> forget to defragment your drive(s) before installing FSX and once more
>> after
>> the installation completes as well! It's a sad thing, but running FS has
>> been a hit and miss game for all of us over the course of many years, and
>> all of us are alone, unless the MS KB lists the EventID. Which is why we
>> congregate in this place, singing our misfortune. I still cannot find
>> anything sensible for ID=28. But then, just because FSX triggers the
>> error,
>> doesn't mean the error isn't soemwhere else entirely, which is why the
>> Event
>> Viewer is sometimes useful, just by whatching the time stamps.
>>
>>
>> Tony. . .
>>
>>
>>
>> "Algy" <Algy@discussions.microsoft.com> wrote in message
>> news:33B24D6D-07EB-4799-8C74-7715EE6CCF35@microsoft.com...
>> > Thanks for coming back Tony!
>> > Well I tried with disabling Norton but the problem is still there - And
>> > I
>> > must admit that I would be rather surprised if it had worked since I
>> > was
>> > able
>> > to run FSX for a couple of weeks before this error, and that was with
>> > Norton
>> > enabled all the time. Don't know what "connections" you might have, but
>> > I
>> > sure would like to know what the FSX coding people(and/or maybe XP)
>> > know
>> > about this message...?
>> > --
>> > Pull up
>> >
>> >
>> > "Tony Sperling" wrote:
>> >
>> >> Sorry, my attention is all over the place at the moment, and i forgot
>> >> to
>> >> ask
>> >> you to disable your Anti-Virus and see how it reacts.
>> >>
>> >> Most professionals in this business don't want to have anything to do
>> >> with
>> >> Norton and/or McAfee. Apart from slowing down your machine, much of
>> >> the
>> >> real
>> >> work they do concist of creating havoc between events of finding the
>> >> odd
>> >> virus as well.
>> >>
>> >> Personally, I am running Avast - the 'Home' version is free for a
>> >> registration, when the period transpires you just register again.
>> >> There
>> >> are
>> >> other alternatives, AVG and NOD32, comes to mind, but don't rush out
>> >> and
>> >> make important changes all at once - just disable the AV for a start
>> >> and
>> >> see
>> >> what happens.
>> >>
>> >>
>> >> Tony. . .
>> >>
>> >>
>> >> "Algy" <Algy@discussions.microsoft.com> wrote in message
>> >> news:DCAD9235-7EDD-44EA-8509-34215DFBB022@microsoft.com...
>> >> > No new suggestions and/or possible tracing-tips - Very frustrating
>> >> > not
>> >> > being
>> >> > able to fly!
>> >> > --
>> >> > Pull up
>> >> >
>> >> >
>> >> > "Algy" wrote:
>> >> >
>> >> >> Thanks Tony!
>> >> >> Actually I found the E-V yesterday but did not at first hand find
>> >> >> anything
>> >> >> directly helpfull - Will do a new research based on your addtl
>> >> >> info.
>> >> >> I should also have mentioned that the obvious(?) solution of
>> >> >> uninstall
>> >> >> and
>> >> >> then reinstall (both FSX-SP1 and FSX) did not work - The error is
>> >> >> still
>> >> >> there.
>> >> >> Also: I have now for some time an image where I know FSX is working
>> >> >> and
>> >> >> after the last restore of this, FSX worked(as always) and I did not
>> >> >> install
>> >> >> anything new, I ran FSX a couple of times with other
>> >> >> applications(Office,IE,Some video/photo editing,...I think) with
>> >> >> shutdowns in
>> >> >> between(this was for maybe 14 days). But then suddenly when I fire
>> >> >> up
>> >> >> FSX, I
>> >> >> get this msg. And I have Norton AV enabled.
>> >> >> --
>> >> >> Pull up
>> >> >>
>> >> >>
>> >> >> "Tony Sperling" wrote:
>> >> >>
>> >> >> > To see the E-V you'll have to activate the Administrative Tools.
>> >> >> > You
>> >> >> > do
>> >> >> > this
>> >> >> > by right-clicking the task bar and go to Properties, there you
>> >> >> > find
>> >> >> > an
>> >> >> > option to make this visible. First item I think?
>> >> >> >
>> >> >> > Having done this, you'll find the Administrative Tools as an item
>> >> >> > in
>> >> >> > your
>> >> >> > Programs menu, or from the Control Panel, and the Event Viewer is
>> >> >> > one
>> >> >> > of
>> >> >> > those tools. You may need to familiarize yourself with this one,
>> >> >> > it
>> >> >> > doesn't
>> >> >> > do anything really magic, but it will usually reveal a lot of
>> >> >> > interesting
>> >> >> > things from out of the underworld, and you can see the exact time
>> >> >> > that
>> >> >> > a
>> >> >> > particular event occurred. Events are usually divided into Errors
>> >> >> > and
>> >> >> > Warnings and they have particular ID's - the most severe messages
>> >> >> > are
>> >> >> > Stop
>> >> >> > Codes that you see when the machine Blue Screens on you. You can
>> >> >> > search
>> >> >> > the
>> >> >> > Windows Knowledgebase for these ID's, but do note that the event
>> >> >> > viewer
>> >> >> > isn't revealing everything that goes bad and a lot of the things
>> >> >> > it
>> >> >> > does
>> >> >> > tell you about may just be where the error surfaced - not where
>> >> >> > it
>> >> >> > actually
>> >> >> > happened!
>> >> >> >
>> >> >> >
>> >> >> > Tony. . .
>> >> >> >
>> >> >> >
>> >> >> > "Algy" <Algy@discussions.microsoft.com> wrote in message
>> >> >> > news:B6CED1AF-0ACD-47AE-96A1-949698AC4D5E@microsoft.com...
>> >> >> > > Tony,
>> >> >> > > Sorry; It is FSX(SP1) and XP(SP2).
>> >> >> > > I have also searched "everywhere" for this and I see some
>> >> >> > > people
>> >> >> > > on
>> >> >> > > the
>> >> >> > > net
>> >> >> > > mentioning this problem, but no suggested solutions.
>> >> >> > >
>> >> >> > > It is hard to remember exact what I run just before
>> >> >> > > (unfortunately
>> >> >> > > I'm not
>> >> >> > > able to run FSX as often as I would like to....). However this
>> >> >> > > has
>> >> >> > > happened a
>> >> >> > > number of times with probably very different "just-before"
>> >> >> > > application
>> >> >> > > mixes(if you know what I mean). I haven't looked in the event
>> >> >> > > viewer,
>> >> >> > > where/how do I find that?
>> >> >> > >
>> >> >> > > --
>> >> >> > > Pull up
>> >> >> > >
>> >> >> > >
>> >> >> > > "Tony Sperling" wrote:
>> >> >> > >
>> >> >> > >> There is nothing in microsoft knowledgebase that I could find
>> >> >> > >> that
>> >> >> > >> matches
>> >> >> > >> this error. I found at least one other poster with this issue
>> >> >> > >> but
>> >> >> > >> no
>> >> >> > >> answer
>> >> >> > >> yet.
>> >> >> > >>
>> >> >> > >> Can you remember the last thing you did on the machine before
>> >> >> > >> the
>> >> >> > >> error?
>> >> >> > >>
>> >> >> > >> Have you looked in your 'Event Viewer'?
>> >> >> > >>
>> >> >> > >> Is this FSX?
>> >> >> > >>
>> >> >> > >> Your OS is XP or Vista?
>> >> >> > >>
>> >> >> > >>
>> >> >> > >> Tony. . .
>> >> >> > >>
>> >> >> > >>
>> >> >> > >>
>> >> >> > >> "Algy" <Algy@discussions.microsoft.com> wrote in message
>> >> >> > >> news:670AFE46-8AE8-4726-A492-6D1470FF1C13@microsoft.com...
>> >> >> > >> >I suddenly got the error "Error ID = 28. Unable to install
>> >> >> > >> >Message
>> >> >> > >> >Filter"
>> >> >> > >> > This is in the very start off start-up, before
>> >> >> > >> > splash-screen.
>> >> >> > >> > Uninstall + re-install doesn't help !! Anyone know something
>> >> >> > >> > about
>> >> >> > >> > this
>> >> >> > >> > ?!?
>> >> >> > >> > --
>> >> >> > >> > Pull up
>> >> >> > >>
>> >> >> > >>
>> >> >> > >>
>> >> >> >
>> >> >> >
>> >> >> >
>> >>
>> >>
>> >>
>>
>>
>>
|
